Generate a deliverable
Specs, review packages and safety analyses that read the current model and come out as the file your process already uses. Re-run them and the document is current again.
14 workflows
Requirement specification document
Turn your requirements into a Word spec, grouped by subsystem, with a traceability appendix.
Preliminary Design Review (PDR) deck
Preliminary Design Review deck with mission context, architecture, and open items.
Design FMEA from architecture
Draft a Design FMEA from your architecture and export it to Excel.
Publish a spec to Google Docs for review
The specification where reviewers can comment in place, formatted so the comments can be read back.
Bill of materials from the architecture
An engineering BOM out of the part hierarchy, with every empty field counted rather than filled.
Budget and margin report
Any resource rolled up the hierarchy, with the margin stated against how real the data underneath is.
Interface Requirements Document (IRD)
The obligations on an interface, stated per end, including the interfaces that have none.
Interface Control Document (ICD)
The agreed interface design, with a coverage table saying which sections the model could not fill.
Trade study from a Notion option list
Criteria from the requirements, not the columns, and a sensitivity finding that says how much the ranking is worth.
FeatureScript feature from model requirements
The model states the constraint, the generated feature enforces it in CAD.
Risk assessment documentation, Annex IV (b)
The hazard register rebuilt as the clause-ordered table the Regulation indexes the file by.
Machine description and operating description
The machine as it is now, subsystem by subsystem and interface by interface, in the order an assessor reads it.
Verification evidence index
Which report proves which requirement, and which requirements have none, current at every re-run.
Technical file skeleton
The binder in Annex IV order: model-derived sections filled, the rest stubbed, a completeness table on page one.
