Reference scenario
A constellation of 24 satellites built on one shared platform
- 1
- platform model that every satellite inherits
- 24
- satellites, each carrying only its own deltas
Space
Launchers and satellites, designed and verified on one model.
Koddex links mission requirements, the spacecraft or launcher architecture, the BOM and the verification plan. When a subsystem changes, you see which requirements, interfaces and tests it affects before the next review.
1 day
for a change impact analysis, instead of 2 weeks of meetings and spreadsheets
10 s
to find the right information, instead of 45 min across many tools
Measured at our reference customer after a year in use. Your first scope measures them on your own programme. Reference customer: Exotec, with more than 1,000 users and 20 partner organisations in Koddex.
01
Space programmes now move at NewSpace pace, and verification still cannot be skipped.
Today
Mission requirements
Interface control documents
BOM spreadsheets
Verification matrices
Before each review, engineers reconcile the requirements, the interface documents and the verification matrix by hand.
With Koddex
Mission requirements
Interface control documents
BOM spreadsheets
Verification matrices
Requirements, interfaces, parts and tests are linked in one model, and the verification matrix is generated from it for each review.
Questions from the field, and how Koddex answers them
Each review, from PDR to CDR, needs a consistent set of evidence.
Koddex freezes the configuration as a baseline at each review, with the requirements, design and verification status of that date.
Verification follows ECSS-E-ST-10-02C.
Each requirement carries its verification method, and the verification matrix is a live view of the model.
The satellites of a constellation share most of their parts.
Variants inherit the common platform, so a change to a shared part shows every satellite it affects.
Subsystem suppliers each build part of the spacecraft.
Access rights are set per partner on the same model, so each supplier sees only its own subsystem.
ECSS-E-ST-10CECSS-E-ST-10-02CECSS-M-ST-40CECSS-Q-ST-80CPDRCDR
With Koddex agents
Assign an interface change to an agent. It lists the requirements and tests the change reopens, comments on each one and passes the review to the engineers concerned.
Teams that work with Koddex agents spend up to 50% less time on repetitive engineering tasks.
02
Use cases for space
Every phase of the V-model on one model
Reference scenarios
Reference scenario
A launcher upper stage taken through PDR and CDR
- 4
- subsystem suppliers, each working in its own scope
- 2
- baselines frozen, one at each review
Event
Koddex at SIANE 2026, Toulouse
Booth E15, October 13 to 15. We run live demos on a real engineering project.
A 20-min demo. Your first use case live in 1 month.
Bring one subsystem and its requirements. In the demo, we show an interface change on a satellite like yours in Koddex. Your first use case is live within a month.