Workflows for robotics programmes
Robotics teams ship fast and still owe a safety argument and a specification. These generate both from the model, and say plainly which parts the model cannot yet support.
11 workflows
The Auditor SimulationRehearse an audit against your model, one clause at a time.
Design FMEA from architectureDraft a Design FMEA from your architecture and export it to Excel.
Requirement specification documentTurn your requirements into a Word spec, grouped by subsystem, with a traceability appendix.
Excel requirements importImport every row of your spreadsheet as a requirement, with your IDs kept exactly.
Requirements coverage reportWhat the model is actually missing, triaged, before any of it becomes a ticket.
Requirements reconciliation with JiraFour difference lists between the model and Jira. Read-only in both systems.
Requirement change impact analysisThe full blast radius of a requirement change, drafted as a Jira change request.
Pull request interface checkComment on a pull request only where it contradicts the documented interface.
Requirement IDs with no implementationCode claiming requirements that no longer exist, and the reverse, held apart.
Model change to code impactWhat in the codebase now contradicts a model change, opened as linked issues.
Confluence hazard log mirrorThe hazard picture published for people outside the safety team, with implemented kept apart from verified.
Other industries

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.
