Skip to main content

​
What aerospace standards does the Aerospace Safety Solution support?

The Aerospace Safety Solution provides structured compliance tracking for seven major aerospace standards: ARP 4754A, ARP 4761, DO-178C, DO-254, DO-160G, MIL-STD-882E, and DO-326A. Each standard is covered by dedicated risksheet configurations and live compliance dashboards. The Standards Compliance Overview dashboard shows a real-time coverage matrix across all seven standards.

​
What is a Design Assurance Level (DAL) and how is it assigned?

A Design Assurance Level (DAL) is a classification that defines the rigor of certification objectives required for software (DO-178C) and hardware (DO-254) development. The Aerospace Safety Solution defines five DAL levels — A through E — automatically derived from the ARP 4761 failure condition classification:
DALFailure Condition ClassificationProbability Target
ACatastrophic10⁻⁹ per flight hour
BHazardous10⁻⁷ per flight hour
CMajor10⁻⁵ per flight hour
DMinorReasonably Probable
ENo Safety EffectNo certification required
DAL E items have no associated certification objectives. See the Reference section for data model details.

​
How do I track DO-178C and DO-254 compliance objectives?

Compliance objectives use the complianceObjective work item type and are tracked per-DAL with five status values: Satisfied, In Progress, Not Started, Not Applicable, and Waived. Each objective records the applicable standard (DO-178C or DO-254), the table reference from the standard (for example, Table A-1), the applicable process, and a pointer to supporting evidence. The Compliance Matrix Dashboard displays all objectives with color-coded status columns for DAL A through DAL D.
Not Applicable means the objective does not apply to the DAL level for this item. Waived indicates an approved deviation — use evidenceReference to link the waiver document to maintain a traceable audit trail.

​
Can I track compliance with standards other than DO-178C and DO-254?

Yes. The complianceRequirement work item type supports free-text standard names, making it suitable for ARP 4754A, ARP 4761, DO-326A, DO-160G, MIL-STD-882E, or any other standard. Unlike compliance objectives (which have per-DAL status columns), compliance requirements use a simpler four-state status: Compliant, Partial, Non-Compliant, or Not Applicable. The evidenceType field categorises supporting artifacts as Document, Test Result, Analysis, Review Record, Inspection, or Demonstration.

​
How does the Certification Readiness Scorecard work?

The Certification Readiness Scorecard computes five real-time metrics per standard using live work item counts from Polarion: diagram Traffic-light coloring is applied automatically: green ≥ 80%, orange 50–79%, red < 50%, grey not applicable. Access the scorecard from the Cert. Readiness entry in the sidebar navigation.

​
Is compliance tracking per system element or across the whole project?

Compliance tracking is project-scoped, not element-scoped. A single compliance document (such as COMPLIANCE-001) covers all objectives for the entire project. This differs from safety analysis documents like SFMEA and DFMEA, which are scoped to individual system elements. This design reflects how certification authorities expect a unified compliance record for the program rather than per-component objective matrices.
UI navigation paths for creating or editing compliance documents, and options for filtering the compliance matrix by DAL level, are not captured in this source briefing. Verify exact procedures in the live Polarion application.

​
How are traceability gaps surfaced during certification reviews?

The Requirements Traceability report and the Certification Readiness Scorecard both highlight gaps — requirements without classification, without decomposition links, or without linked test cases. The FMEA Coverage Gaps report identifies characteristics that have not been analysed in any failure mode analysis. Together these reports provide the evidence basis for an audit or DER review.

​
What security compliance support is included?

The Aerospace Safety Solution includes a Security Threat Assessment document type aligned to DO-326A, using STRIDE threat modelling with Security Assurance Level (SAL) tracking. The Standards Compliance Overview covers DO-326A alongside the safety standards, and a dedicated Security Threat Assessment report is available in the Reports section.
Specific DO-326A objective tables and SAL enumeration values are not fully captured in this source briefing. Verify the security risksheet configuration in your project instance.
Code: .polarion/nextedy/models/rtm.yaml (0.53) · .polarion/tracker/fields/complianceObjective-custom-fields.xml (0.52) · .polarion/pages/spaces/_default/Standards Compliance Overview/page.xml, Certification Readiness Scorecard/page.xml, Compliance Matrix/page.xml (0.48) · .polarion/tracker/fields/dal-enum.xml (0.45) · .polarion/tracker/fields/complianceRequirement-custom-fields.xml (0.45) · .polarion/tracker/fields/complianceObjective-standard-enum.xml, complianceObjective-status-enum.xml, complianceRequirement-complianceStatus-enum.xml, complianceRequirement-evidenceType-enum.xml (0.45) · 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.43) · .polarion/nextedy/sheet-configurations/DO-178C Objectives Compliance Matrix.yaml (0.43) · modules/RiskTemplates/ComplianceTemplate/attachments/risksheet.json (0.42) · 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.42)