Check the model
Cross-examine the model the way an auditor or a reviewer would, and get the findings ranked by how badly they would land.
16 workflows
The Auditor SimulationRehearse an audit against your model, one clause at a time.
Requirements coverage reportWhat the model is actually missing, triaged, before any of it becomes a ticket.
Polarion traceability gap reportRequirement to architecture to verification to result, with every break in the chain named.
Compare your model against a counterparty ICDCharacteristic by characteristic against their document, with how each match was made.
Simulink interfaces against the architectureWhere the block diagram and the architecture disagree about a signal, before integration finds it.
Fusion structure against the architectureWhere the physical build and the architecture have diverged, with the naming noise stripped out.
Onshape Part Studio against the architectureDivergences within the Part Studio scope, led by requirements the geometry violates.
Altium schematic against the electrical interfacesNets and connectors against the architecture, led by rail voltages a requirement forbids.
Teamcenter change impact on the modelWhat a change board is about to decide without knowing which requirements it breaks.
Cycle readinessWhat the current cycle leaves unverified, which Linear cannot see because it does not know the requirements exist.
Safety case readinessWhat the safety argument rests on, sorted into verified, implemented, asserted and absent, before any ticket is filed.
Annex III requirement gap auditorFor each applicable Annex III clause: does a requirement in this model satisfy it, and is it verified.
Annex IV readiness auditWhich Annex IV items the model can already support, which need a few additions, and which live elsewhere.
Hazard register integrity auditEvery hazard followed outward to its requirements, tests and residual risk. Every broken link is a finding.
Verification coverage auditWhich requirements have no evidence, from both directions, with safety requirements first.
Architecture and interface completeness auditThe holes in structure and behaviour, found before the operating description is generated around them.
Simulink interfaces against the architectureWhere the block diagram and the architecture disagree about a signal, before integration finds it.
Altium schematic against the electrical interfacesNets and connectors against the architecture, led by rail voltages a requirement forbids.
Let’s discuss your
systems engineering challenges
Tell us what you’re building, and we’ll show you how Dalus can help.
30-minute discovery call with Sebastian
Co-founder, Dalus
No time that works? Send us a message and we’ll find one.





