Skip to content
Concept · Engineering Collaboration Proposal

Digital Twin

Digital Twin + physical testing

A Digital Twin increases the value of physical testing by helping engineers predict expected behaviour, compare measured results, investigate deviations and improve the next engineering baseline.

Proposed approachNever a replacement for physical testing.
Close-up of APEX propulsion development hardware with flanged metal sections, fluid fittings, yellow connectors and cabling.
Fig. 03APEX propulsion development hardware: close-up of cabling and fluid fittings.

What the twin does

Nine responsibilities

  • 01Pre-test prediction
  • 02Simulation
  • 03Expected response
  • 04Scenario exploration
  • 05Test planning
  • 06Predicted vs measured comparison
  • 07Anomaly investigation
  • 08Model updating
  • 09Design feedback

The twin loop

Predict. Test. Compare. Decide.

The loop runs once per test. Each pass leaves a prediction, a measurement and a decision on record.

  1. 01Engineering model
  2. 02Prediction
  3. 03Physical test
  4. 04Measured data
  5. 05Predicted vs measured
  6. 06Engineering review
  7. 07Model update or hardware updateThe review decides which: the model was wrong, or the hardware needs to change.
  8. 08Retest
↺ Retest returns to the engineering model
Predicted vs measured
Illustrative — not APEX test data
Predicted (model) Measured (test) Agreement band
0.00.51.00.000.250.500.751.00NORMALISED TIMEDeviation → engineering reviewPredictedMeasured
Show values as a table
Illustrative predicted and measured values, normalised
TimePredictedMeasured
0.000.000.00
0.100.510.44
0.200.760.73
0.300.880.85
0.400.940.94
0.500.971.07
0.600.991.01
0.700.991.00
0.801.000.99
0.901.000.99
1.001.001.01

Digital Twin maturity

Five potential levels

Confidence in a twin is earned the same way as confidence in hardware: by evidence, within defined limits.

  1. Level 1ModelAn engineering representation of the hardware.
  2. Level 2Simulated systemSubsystem interactions represented.
  3. Level 3Correlated modelCompared with test measurements.
  4. Level 4Validated operating regionUseful agreement demonstrated within defined limits.
  5. Level 5Operational engineering twinContinuously updated where appropriate.
APEX level: owner confirmation requiredNo maturity level is claimed for an APEX twin.

Configuration-aware twin

Same configuration, or no comparison.

Predicted-versus-measured comparisons are meaningful only when the digital and physical configurations correspond.

Engine configurationPhysical
APEX-ENG-001Revision C
  • Hardware baselinelinked
  • Firmware baselinelinked
  • Software baselinelinked
  • Sensor packagelinked
  • Calibration setlinked
  • Test configurationlinked
Corresponds ⇄
Twin modelDigital
DT-ENG-001Revision 08
  • Model geometry baselinelinked
  • Controller model versionlinked
  • Sensor model maplinked
  • Calibration importlinked
  • Prediction setlinked
  • Correlation reportlinked
Illustrative record formatIdentifiers are examples of structure, not APEX records.

Instrumentation

If you cannot measure it, you cannot correlate it.

  • 01Pressure
  • 02Temperature
  • 03Force / thrust
  • 04Vibration
  • 05Strain
  • 06Acceleration
  • 07Rotational speed
  • 08Position
  • 09Timing
  • 10Flow-related measurements
  • 11Controller states
  • 12Electrical measurements

Sensor to correlation — and who can contribute at each stage

  1. 01Sensor
  2. 02Signal conditioning
  3. 03DAQ
  4. 04Time synchronisation
  5. 05Test data
  6. 06Engineering analysis
  7. 07Digital Twin correlation

Engineering test data

Every test, a traceable record

Each physical test becomes a digital record tied to its configuration. Proposed capability partner: Gamyaa Aerospace — digital engineering, test-data platform, model correlation and engineering evidence.

Identity
  • Test ID
  • Test objective
  • Procedure
Configuration
  • Hardware configuration
  • Serial numbers
  • Software version
  • Firmware version
  • Sensor configuration
  • Calibration references
  • Model revision
Results
  • Recorded data
  • Events
  • Observations
  • Anomalies
Decision
  • Analysis
  • Disposition
  • Approval
Record structureFields only. No APEX test data is shown.