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 Simulation
Rehearse an audit against your model, one clause at a time.
Design FMEA from architecture
Draft a Design FMEA from your architecture and export it to Excel.
Requirement specification document
Turn your requirements into a Word spec, grouped by subsystem, with a traceability appendix.
Excel requirements import
Import every row of your spreadsheet as a requirement, with your IDs kept exactly.
Requirements coverage report
What the model is actually missing, triaged, before any of it becomes a ticket.
Requirements reconciliation with Jira
Four difference lists between the model and Jira. Read-only in both systems.
Requirement change impact analysis
The full blast radius of a requirement change, drafted as a Jira change request.
Pull request interface check
Comment on a pull request only where it contradicts the documented interface.
Requirement IDs with no implementation
Code claiming requirements that no longer exist, and the reverse, held apart.
Model change to code impact
What in the codebase now contradicts a model change, opened as linked issues.
Confluence hazard log mirror
The hazard picture published for people outside the safety team, with implemented kept apart from verified.
Other industries