Skip to main content

What You Will Configure

The Compliance Matrix system has two components that work together:
  • Compliance Risksheet (COMPLIANCE-001) — tracks individual compliance requirements and evidence references
  • DO-178C / DO-254 Objective PowerSheets — track per-DAL objective status across software and hardware assurance levels
The document type is riskSpecification using the ComplianceTemplate under RiskTemplates.

Step 1: Understand the Document Scope

Unlike SFMEA and DFMEA documents, the Compliance Matrix is not scoped to a system element. Do not set systemElementId on compliance documents. Compliance tracking is project-wide. The COMPLIANCE-001 module contains complianceObjective work items (for DO-178C/DO-254) and complianceRequirement work items (for other standards). Evidence is linked via task work items using the implements link role — not riskControl.
Linking evidence tasks with riskControl instead of implements will cause those items to appear in FMEA risk control reports rather than the compliance matrix. Always use implements for compliance evidence tasks.

Step 2: Configure the Compliance Risksheet Columns

The Compliance Risksheet has 9 columns organized into 4 header groups:
GroupColumns
StandardStandard name, Section/table reference
RequirementRequirement title, Full requirement text
ComplianceCompliance status, Evidence type
EvidenceEvidence ID, Evidence item reference, Evidence status
Compliance status values and their row header colors:
StatusColor
CompliantGreen
PartialYellow
Non-CompliantRed
Not ApplicableGrey
Evidence type options: Document, Test Result, Analysis, Review Record, Inspection, Demonstration. Row header coloring is applied automatically based on the compliance status field, enabling rapid visual scanning of gaps.

Step 3: Configure the DO-178C and DO-254 Objective PowerSheets

Each objective PowerSheet has 3 column groups and 4 views. Column groups:
GroupColorContents
Compliance ObjectivePurpleObjective title, standard, table reference, applicable process
DAL StatusOrangedalAStatus, dalBStatus, dalCStatus, dalDStatus
EvidenceGreenevidenceReference
DAL status values (5-state enum, same for all four DAL columns):
ValueColor
SatisfiedGreen
In ProgressOrange
Not StartedRed
Not ApplicableGrey
WaivedBlue
The DO-178C PowerSheet includes dalAStatus through dalDStatus only. There is no dalEStatus field — DAL E objectives do not require the same level of assurance evidence. Do not add a fifth DAL column.
Views available in both the DO-178C and DO-254 objective PowerSheets:
  • Full Matrix — all objectives and all DAL columns
  • DAL A Only — filter to DAL A objectives only (for Level A software/hardware reviews)
  • DAL A + B — filter to DAL A and B (covers most critical systems)
  • Summary — condensed view for management reporting
Use the DAL-filtered views when preparing for Stage of Involvement (SOI) audits. Showing only the DAL level under review reduces noise and focuses reviewer attention on the applicable objectives.
Binding the PowerSheet to the document: Set applyCurrentDocumentTo on each PowerSheet configuration to bind it to COMPLIANCE-001. Without this constraint, the PowerSheet will not resolve work items correctly.

Step 4: Populate complianceObjective Fields

Each complianceObjective work item in COMPLIANCE-001 uses these custom fields:
FieldTypeDescription
standardenumDO-178C or DO-254
tableReferencestringStandard table/section (e.g., Table A-1)
dalAStatusenumPer-DAL compliance status
dalBStatusenumPer-DAL compliance status
dalCStatusenumPer-DAL compliance status
dalDStatusenumPer-DAL compliance status
evidenceReferencestringLink or reference to supporting evidence
applicableProcessstringProcess or activity name
Per-DAL fields allow one objective to carry different status values at each assurance level — for example, Satisfied at DAL A but In Progress at DAL C during early program phases.

Step 5: Configure the Four Risksheet Views

Add these four views to the Compliance Risksheet configuration:
  • Full Matrix — all 9 columns visible
  • Compliance Overview — aggregated status summary columns only
  • Evidence Tracking — Evidence ID and Evidence status columns focused
  • Gaps Only — filtered to Non-Compliant rows, showing full requirement text for gap closure
Share the Gaps Only view with the certification authority liaison during closure meetings. It surfaces only open items without exposing the full matrix, reducing review time.

Verification

After configuration, open the Standards Compliance page from the sidebar. You should see:
  • Live compliance cards for all 7 standards with current status percentages
  • The COMPLIANCE-001 Risksheet rendering all 9 columns with colored row headers
  • The DO-178C and DO-254 PowerSheets displaying objective status per DAL level with color-coded cells
The Certification Readiness Scorecard should also reflect updated compliance data using traffic-light coloring: green ≥ 80%, orange 50–79%, red < 50%.
Step-by-step UI interactions for creating and binding the COMPLIANCE-001 document and configuring the PowerSheet applyCurrentDocumentTo constraint should be verified in the live Polarion application.

See Also

Code: .polarion/pages/spaces/_default/Standards Compliance Overview/page.xml, Certification Readiness Scorecard/page.xml, Compliance Matrix/page.xml (0.62) · .polarion/nextedy/sheet-configurations/DO-178C Objectives Compliance Matrix.yaml (0.61) · .polarion/nextedy/sheet-configurations/DO-254 Objectives Compliance Matrix.yaml (0.57) · modules/RiskTemplates/ComplianceTemplate/attachments/risksheet.json (0.57) · 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.55) · 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.54) · .polarion/nextedy/sheet-configurations/ARP 4754A System Development Assurance.yaml (0.54) · .polarion/tracker/fields/complianceObjective-custom-fields.xml (0.49) · .polarion/tracker/fields/complianceObjective-standard-enum.xml, complianceObjective-status-enum.xml, complianceRequirement-complianceStatus-enum.xml, complianceRequirement-evidenceType-enum.xml (0.47) · .polarion/nextedy/models/rtm.yaml (0.46)