Before You Begin
Confirm you have theproject_approver role or at minimum write access to the target space. Documents start in Draft status — only users with the project_approver role can advance them through the approval workflow.
Step 1: Navigate to the Risks Space
- Open the project sidebar and select Risks from the navigation favorites.
- The Risks space dashboard shows the document inventory with all existing risk analysis documents organized by type.
Step 2: Select the Document Type
Choose the document type that matches your analysis scope:| Analysis | Document Type | Scope | Standard |
|---|---|---|---|
| Functional Hazard Assessment | FHA | System-level failure conditions | ARP 4761 |
| Preliminary System Safety Assessment | PSSA | System-level safety requirements | ARP 4761 |
| System Safety Assessment | SSA | Final compliance evidence | ARP 4761 |
| System-level failure modes | SFMEA | System element | ARP 4761 |
| Subsystem-level failure modes | SubSystem FMEA | Subsystem element | ARP 4761 |
| Component-level failure modes | DFMEA | Component element | ARP 4761 / DO-254 |
| Fault Tree Analysis | FTA | Boolean logic tree | ARP 4761 |
| Common Cause Analysis | CCA | Zonal / PRA / CMA | ARP 4761 |
| Security threats | Security Threat | Project-wide (DO-326A) | DO-326A |
| Hazard tracking | Hazard Tracking | System-level hazards | MIL-STD-882E |
| Standards compliance | Compliance Matrix | Project-wide objectives | DO-178C / DO-254 / ARP 4754A |
Step 3: Create the Document
- Click New Document (or the equivalent create action in the Risks space).
- Select the document type from the template list.
- Enter a descriptive document title following the project naming convention, for example:
Air Data Computer Interface (ADCI) - Component DFMEAFCC System Functional Hazard Assessment (ARP 4761)
- Set the version field to match your project baseline (e.g.,
1.0). - Assign team members who will work on and review this document.
Step 4: Bind to a System Element (Component, Subsystem, and System Documents)
For DFMEA, SubSystem FMEA, SFMEA, FHA, PSSA, SSA, and FTA documents, set the systemElementId field to link the document to its system element in the hierarchy.
- The 3-level breadcrumb navigation (System → Subsystem → Component) in risksheet panels
- Auto-display of associated requirement documents matched by name pattern (
DRS-*,CHARS-*,SUBRS-*) - Filtering in the System Structure Navigator report
Compliance Matrix and Hazard Tracking documents have no
systemElementId — they are project-scoped, not element-scoped. Leave this field blank for those document types.Step 5: Save and Open in Risksheet
After creating the document, open it in the Risksheet view to begin entering risk analysis rows. The risksheet columns available depend on the document type — DFMEA shows severity/occurrence/detection RPN columns, while FHA shows failure condition classification and DAL columns.
Step 6: Set Initial Status
New documents are created in Draft status. The full lifecycle is: Draft → In Review → Approved → Published Leave the document in Draft while populating risk analysis rows. Advance to In Review only when the analysis is complete and ready for peer review.Verification
You should now see the new risk analysis document listed in the Risks space document inventory, with status Draft, the correct document type label, and — for element-scoped documents — the associated system element name displayed in the breadcrumb. Opening the document should load the Risksheet view with the column configuration for that document type.See Also
- Create System Elements — set up the system hierarchy before creating element-scoped documents
- Create a Component DFMEA — detailed walkthrough for DFMEA analysis
- Create PSSA and SSA Documents — safety assessment document creation
- Review and Approve a Risk Document — advance a document through the approval workflow
- Solution Setup and Configuration — full setup guide index
Source References (dev)
Source References (dev)
Code:
modules/Risks/COMPLIANCE-001/module.xml, modules/Risks/MIL-STD-882E-HTS-001/module.xml, modules/Risks/SEC-THREAT-001/module.xml, modules/Risks/SFMEA-SUB-001/module.xml, modules/Risks/SFMEA-SUB-002/module.xml, modules/Risks/SFMEA-SUB-003/module.xml (0.58) · .polarion/documents/workflow/riskSpecification-workflow.xml (0.56) · .polarion/tracker/fields/severity-enum.xml, status-enum.xml, priority-enum.xml, implementationStatus-enum.xml, riskSpecification-document-status-enum.xml (0.54) · modules/RiskTemplates/PSSATemplate/attachments/risksheet.json (0.53) · modules/RiskTemplates/RiskControlPlanTemplate/attachments/risksheet.json (0.53) · .polarion/polarion-project.xml, .polarion/context.properties, .polarion/security/user-roles.xml, .claude/PROJECT.md, TODO.md (0.52) · .polarion/tracker/fields/riskRecord-custom-fields.xml (0.52) · .polarion/pages/spaces/Requirements/Home/page.xml, Design/Home/page.xml, Risks/Home/page.xml, Testing/Home/page.xml, Risks/FMEA Reports/page.xml, Documentation/Home/page.xml, Documentation/Powersheet Help Redirect/page.xml, RiskTemplates/Home/page.xml (0.51) · modules/RiskTemplates/CCATemplate/attachments/risksheet.json (0.51) · modules/RiskTemplates/DFMEATemplate/attachments/risksheetTopPanel.vm, SubSystem-FMEATemplate/attachments/risksheetTopPanel.vm, System-FMEATemplate/attachments/risksheetTopPanel.vm, PFMEATemplate/attachments/risksheetTopPanel.vm, HazardTrackingTemplate/attachments/risksheetTopPanel.vm, DFMEATemplate/attachments/risksheetPdfExport.vm, SubSystem-FMEATemplate/attachments/risksheetPdfExport.vm, System-FMEATemplate/attachments/risksheetPdfExport.vm, PFMEATemplate/attachments/risksheetPdfExport.vm (0.50)