Skip to content
Concept · Engineering Collaboration Proposal
Official website (opens in a new tab)
Official APEX website (opens in a new tab)Discuss collaboration

Concept · Engineering Collaboration Proposal

Build & Validate

From mission to flight

One continuous engineering lifecycle in 24 stages — and back again. Each stage names what happens, what it delivers, the evidence it leaves, and the capabilities and partners it needs.

APEX propulsion development hardware standing on a workshop floor, with tubing, cabling and a spherical vessel above a large conical section.
Fig. 01APEX propulsion development hardware in the workshop.

Development flow

The lifecycle

Select a stage. Capabilities open their detail; partners are those proposed today.

  1. 01Engineer

    Mission need

    What happens
    The customer and mission problem the vehicle must solve is defined.
    Deliverable
    Mission need statement
    Evidence
    Reviewed mission concept
    Capabilities needed
    Partners
    APEX · open to more
01Engineer

Mission need

What happens
The customer and mission problem the vehicle must solve is defined.
Deliverable
Mission need statement
Evidence
Reviewed mission concept
Capabilities needed
Partners
APEX · open to more

Core engineering philosophy

Engineer , then Build , then Prove , then Improve

Confidence is earned in a fixed order. What is learned in each pass becomes the next baseline.

  1. 01

    Engineer

    Decide what must be true.

    • Requirements
    • Architecture
    • Interfaces
    • Analysis
    • Simulation
  2. 02

    Build

    Make it, and record what was made.

    • Detailed design
    • Manufacturing
    • Assembly
    • Firmware
    • Software
    • Instrumentation
  3. 03

    Prove

    Show it with evidence.

    • Inspection
    • Component testing
    • Subsystem testing
    • Engine testing
    • HIL
    • Integrated testing
  4. 04

    Improve

    Learn, and change the baseline.

    • Compare
    • Investigate
    • Update model
    • Update hardware
    • Retest
Back to EngineerImprove feeds the next design

Testing strategy

The confidence ladder

  1. 08FlightThe final, most expensive evidence.
  2. 07Vehicle systemThe integrated vehicle passes system-level tests.
  3. 06Propulsion systemEngine, feed system and control work together.
  4. 05EngineOperates as an integrated engine to a written objective.
  5. 04SubsystemWorks with its neighbours across real interfaces.
  6. 03ComponentPerforms its function on its own.
  7. 02PartMatches its drawing, with inspection evidence.
  8. 01MaterialSpecified, characterised and traceable to its certificate.

Confidence should be accumulated progressively through evidence rather than assumed at the final integrated level.

Each rung is cheaper to test than the one above it, and a problem found low on the ladder costs far less to fix. Flight is the last and most expensive evidence, not the first.

Test categories

Eight kinds of evidence

Major categories only. Detailed procedures stay with APEX.

  • 01

    Component Testing

    Individual parts and assemblies against their own requirements.

  • 02

    Subsystem Testing

    Assemblies working together across real interfaces.

  • 03

    Propulsion Testing

    Engine and propulsion-system tests on a qualified stand.

  • 04

    Hardware-in-the-Loop

    Real controllers and firmware against simulated hardware.

  • 05

    Integrated System Testing

    The vehicle tested as one system.

  • 06

    Ground-System Testing

    GSE, ground software and communications end to end.

  • 07

    Mission Simulation

    The full mission rehearsed with people and software.

  • 08

    Flight Readiness

    Evidence reviewed against flight criteria.

Hardware-in-the-loop

Real controllers, simulated world

Firmware and controller hardware can be tested against a Digital Twin or simulator before full-vehicle integration.

  1. 01Digital Twin / simulatorSimulated
  2. 02Simulated vehicleSimulated
  3. 03Sensor / environment simulationSimulated
  4. 04Real controller hardwareReal hardware / firmware
  5. 05Real firmwareReal hardware / firmware
  6. 06Command outputsReal hardware / firmware
  7. 07Simulated / physical responseSimulated

The response feeds back into the simulator, closing the loop. Controllers and firmware are exercised against faults and edge cases long before they meet an engine or a vehicle.

Virtual to physical

From 100% simulation to flight

  1. 01100% simulationEverything is a model.
  2. 02Software-in-the-loopReal flight or control software against models.
  3. 03Processor-in-the-loopSoftware on the target processor.
  4. 04Hardware-in-the-loopReal controller hardware and firmware.
  5. 05Subsystem hardwareReal subsystems on the bench.
  6. 06Integrated propulsion systemEngine, feed and control together.
  7. 07Integrated vehicleThe vehicle as one system.
  8. 08FlightEverything is real.
Physical evidence ↑Model confidence ↑System confidence ↑
ApproachNot every step is implemented today. Each will be marked when APEX confirms it.

Digital quality thread

Every part needs evidence.

An unbroken record from requirement to acceptance, so any test result can be tied to exactly what was built. Proposed capability: Gamyaa Aerospace — aerospace quality intelligence, manufacturing quality, First Article Inspection and the digital quality thread. No certification is claimed.

  1. Requirement
  2. Design
  3. Drawing
  4. BOM
  5. Material
  6. Part
  7. Serial number
  8. Manufacturing
  9. Inspection
  10. Assembly
  11. Software / firmware
  12. Test configuration
  13. Test result
  14. Acceptance
NextDigital Twin