B2 · Proof · ADAS central compute Input swap
500+ safety mechanisms.
One graph that proves them.
Central compute unit, L2, 15 sensors: the digital twin runs scenarios in CARLA — and the graph links every mechanism to its requirement. The assessor's question becomes a traversal.
500+ safety mechanisms — without Excel maintenance.
500+ safety mechanisms, 15 sensors, target ASIL-D: traceability between goal, requirement, mechanism and test decays into Excel links and manual upkeep.
Scenarios from OpenSCENARIO run in the twin; the graph links every scenario to its requirement and every mechanism to its report.
The assessor's question becomes a traversal: ISM-042 fails → backup ISM-043 takes over — the chain answers instead of a spreadsheet.
Scenario swap instead of one-off sign-offs: new cases run through the same chain, traceability stays closed.
The scenario runs. The trace holds.
OpenSCENARIO 2.0 — lane change with pedestrian. The recording shows the simulation; the graph carries the proof: every scenario mapped to a requirement, every requirement to a report.
▸ Input swap: the recording stands in for the live twin connection
From safety goal to mechanism — every edge named.
No spreadsheets, no manual linking: the chain is the graph. Impact analysis included — if ISM-042 fails, the graph shows the diverse backup ISM-043.
“How do you guarantee the system is ASIL-D-safe when the performance cluster fails completely?”
Redundancy model 1oo2D with diverse implementations. For every mechanism the graph shows the path: ISM-042 fails → backup ISM-043 takes over — FMEA coverage 92.5%.
The twin feeds on scenarios.
Reads
OpenSCENARIO scenarios · CARLA recordings · test artifacts via defined interfaces
Transforms
Scenario → twin instance · sensors & mechanisms → nodes + edges
Writes back
Test report · DC 99.8% · verdict per requirement
Honest status.
What is a recording — and what still needs a connection.