Workflows for aerospace and space

Space and aviation programmes carry the densest documentation load of any domain: certification bases, technical specifications, review packages and safety assessments, all held to a standard someone else wrote. These run against your live model instead of a folder of stale Word files.

20 workflows

Requirement specification documentTurn your requirements into a Word spec, grouped by subsystem, with a traceability appendix.Preliminary Design Review (PDR) deckPreliminary Design Review deck with mission context, architecture, and open items.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.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.Jama baseline migrationA whole baseline across, with the trace links, and a list of every edge it had to cut.Jama drift reportWhere Jama and the model disagree, established before anyone decides what to do.Jama suspect link triageThe suspect backlog sorted into safe to clear, genuinely broken, and needs a human.Polarion requirements to architectureGive Polarion requirements an architecture to point at, one accepted link at a time.Polarion traceability gap reportRequirement to architecture to verification to result, with every break in the chain named.Polarion round trip that respects frozen workChanges come across into In Work requirements. Frozen ones get a change request instead.Confluence hazard log mirrorThe hazard picture published for people outside the safety team, with implemented kept apart from verified.Verify mission requirements in Ansys STKAccess, coverage, link and lifetime computed against the limit, with the scenario recorded in full.Teamcenter change impact on the modelWhat a change board is about to decide without knowing which requirements it breaks.
Engineers working around a jet engine on a workbench

Let’s discuss your systems engineering challenges

Tell us what you’re building, and we’ll show you how Dalus can help.

Sebastian Völkl

30-minute discovery call with Sebastian

Co-founder, Dalus

No time that works? Send us a message and we’ll find one.