Skip to main content

What You Will Achieve

After completing this tutorial, your Polarion project will contain:
  • A 3-level system decomposition structure (System → Subsystems → Components)
  • All 22 work item types for safety and security analysis
  • Risksheet templates for FHA, PSSA, SFMEA, DFMEA, CCA, and Hazard Tracking
  • A Compliance Matrix covering 7 aerospace standards
  • Role-specific dashboards for Program Managers, Safety Engineers, and V&V Engineers

Prerequisites

Before you begin, confirm the following:
  • Polarion ALM version 2304 or later is installed and accessible
  • Nextedy Risksheet and Nextedy Powersheet extensions are licensed and active on your Polarion server
  • You have Project Administrator rights in Polarion
  • Your Polarion administrator has granted you access to project templates
Confirm your Nextedy licenses are active before proceeding. Navigate to Administration → Extensions in Polarion and verify both Risksheet and Powersheet appear with a valid status. Without active licenses, the risksheet columns and powersheet views will not render.

Step 1: Create the Project from the Aerospace Safety Template

  1. Open the Polarion administration panel at Administration → Projects → Create Project.
  2. Select Aerospace Safety Solution from the template list.
  3. Enter your project details:
Project ID:   AERO-001          (use uppercase, no spaces)
Project Name: Flight Control Computer Safety Analysis
Project Lead: (your username)
Prefix:       TA                (used for all work item IDs)
  1. Click Create. Polarion will provision the project and copy all configuration files.
What you should see: A new project appears in your project list. The left sidebar shows 10 preset navigation favorites: Home, Standards Compliance, Risksheets, PowerSheets, RTM, Requirements, Design, Risks, V&V, and Cert. Readiness.

Step 2: Verify the Work Item Type Configuration

  1. Navigate to Administration → Work Item Types within your new project.
  2. Confirm the following key types are present (22 types total):
Work Item TypeSort OrderPurpose
customerRequirement0Stakeholder needs
sysReq1System-level requirements
desReq2Implementation requirements
systemElement3Architecture components
failureMode6FMEA analysis items
failureCondition15ARP 4761 FHA items
hazard14MIL-STD-882E hazard tracking
securityThreat19DO-326A security analysis
safetyRequirement16DAL-allocated safety requirements
What you should see: All 22 types appear in the list. Each type displays the type_risk.gif icon.
The template also installs 20 link roles, including refines, assesses, allocatesTo, mitigates, verifies, and hasCause. These roles enforce traceability discipline across the V-Model chain and do not require manual configuration.

Step 3: Confirm the System Element Hierarchy

  1. Open the Design space from the sidebar.
  2. Navigate to the system element structure. You should see the reference architecture for the Flight Control Computer (FCC):
diagram What you should see: 12 system elements total — 1 system, 3 subsystems, and 8 components. Each component has linked documents for design requirements, characteristics, and design FMEA.

Step 4: Open the Safety Assessment Documents

  1. Click Risks in the sidebar to open the safety documents space.
  2. Confirm the following documents are present:
DocumentTemplatePurpose
FHA RisksheetRiskTemplates/FHATemplateARP 4761 failure conditions
PSSA RisksheetRiskTemplates/PSSATemplateSafety requirements allocation
Hazard Tracking DocumentRiskTemplates/HazardTrackingTemplateMIL-STD-882E hazards
Security Threat DocumentRiskTemplates/SecurityThreatTemplateDO-326A threats
Compliance MatrixRiskTemplates/ComplianceTemplate7-standard compliance tracking
What you should see: The FHA document opens with a Risksheet grid showing columns for failure condition classification, DAL level, and effects. The Compliance Matrix lists 48 compliance objectives across DO-178C, DO-254, ARP 4754A, ARP 4761, DO-326A, DO-160G, and MIL-STD-882E.
The reference project ships with pre-populated sample data: 18 failure conditions, 260 failure modes, 33 test cases, and 214 risk controls. This data illustrates correct configuration and can be cleared before live project work begins.

Step 5: Verify the Certification Readiness Dashboard

  1. Click Cert. Readiness in the sidebar.
  2. The dashboard displays live compliance metrics for each standard using traffic-light indicators:
    • Green — ≥ 80% complete
    • Orange — 50–79% complete
    • Red — < 50% complete
What you should see: Seven standard cards appear, each showing readiness percentages for classification, decomposition, test coverage, and RPN scoring.

Next Steps

With the Aerospace Safety Solution installed, you are ready to begin your first safety analysis: For Risksheet column configuration and template customization, see the companion documentation:
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.50) · .polarion/tracker/fields/workitem-type-enum.xml (0.48) · .polarion/tracker/fields/workitem-link-role-enum.xml (0.45) · modules/RiskTemplates/PSSATemplate/attachments/risksheet.json (0.40) · datasets/sol-aero-ui-walkthrough/summary.md, navigation.md, dashboards/home-dashboard.md, dashboards/role-dashboards.md, dashboards/standards-compliance.md, risksheet-views/risksheet-views.md, work-item-types/data-model.md (0.39) · .polarion/pages/spaces/_default/Standards Compliance Overview/page.xml, Certification Readiness Scorecard/page.xml, Compliance Matrix/page.xml (0.39) · .polarion/nextedy/models/rtm.yaml (0.39) · .polarion/pages/spaces/_default/Safety Assessment Summary/page.xml, Common Cause Analysis Report/page.xml, Security Threat Assessment/page.xml, Hara Risk Matrix Report/page.xml (0.38) · .polarion/polarion-project.xml, .polarion/context.properties, .polarion/security/user-roles.xml, .claude/PROJECT.md, TODO.md (0.38) · modules/RiskTemplates/ComplianceTemplate/attachments/risksheet.json (0.38)