Skip to main content
From the project sidebar, select Cert. Readiness. The scorecard loads as a live dashboard — all percentages reflect current work item data in the project.

​
Understanding the Scorecard Layout

The scorecard displays one row per standard with five metric columns:
ColumnWhat it measures
Classification %Requirements with the classification field set (SC/CC/DAL-A–D)
Decomposition %Requirements with parent-child refines links — coverage across all three levels (customer, system, design)
Test Coverage %Requirements with a linked testCase work item
RPN Scored %Failure modes with postmitigationRPN value set — FMEA completeness indicator
Doc InventoryCount of specification documents registered under this standard’s scope

​
Traffic Light Color Coding

diagram Gray / N/A means the metric does not apply to that standard — for example, DO-326A has no RPN scoring.

​
Reading Each Standard

​
Step 1 — Identify red metrics first

Scan the Classification % and Test Coverage % columns for red cells. These represent the largest compliance gaps. Red metrics require active remediation before a certification audit.

​
Step 2 — Assess orange metrics

Orange metrics (50–79%) indicate work in progress. Use the Related Tool Links on each standard card to open the corresponding risksheet or compliance matrix and review item-by-item status.

​
Step 3 — Verify document inventory

Check the Doc Inventory count for each standard. A low count means required specification documents have not been created or linked to the correct standard scope.
If all design requirements are typed as electrical or mechanical subType rather than software, the DO-178C classification query returns 0% because there are no software design requirements to classify. This is a correct reflection of the project state, not a data error.

​
Step 4 — Drill into detail for DO-178C and DO-254

The scorecard shows aggregate percentages. For objective-by-objective DAL status, open the Compliance Matrix Dashboard instead — it lists each standard objective with per-DAL (A/B/C/D) completion status.
The SecurityThreat work item type exists in the data model but the Security Threat Assessment document and related risksheets must be created before any DO-326A metrics become active. Until then, all five DO-326A columns display N/A regardless of project progress.

​
Step 5 — Verify SC/CC classification consistency

For ARP 4754A, the Classification % metric alone is not sufficient. Open the Classification Consistency Report from the project reports section to confirm that Safety-Critical (SC) and Common Cause (CC) classifications flow correctly through the requirement decomposition chain — every child requirement of an SC parent must also carry SC classification.
The Decomposition % uses backward-link counting — a requirement that has no refines parent link reduces this metric. After importing or creating new requirements, always verify that parent-child links are established before reading the scorecard.

​
Live Query Behavior

All metrics are recomputed on page load using live Lucene queries against current work item data. The scorecard does not cache results — refreshing the page always reflects the latest project state.
Metric thresholds, standard-specific formulas, and scoring behavior should be verified in the live Certification Readiness Scorecard page within Polarion before making compliance decisions.

​
Verification

You should now see a table with one row per active aerospace standard, color-coded metric cells, and document inventory counts. Red cells identify standards requiring immediate action; N/A cells indicate standards not yet populated in the project.

​
See also

Code: 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.68) · .polarion/pages/spaces/_default/Standards Compliance Overview/page.xml, Certification Readiness Scorecard/page.xml, Compliance Matrix/page.xml (0.63) · .polarion/pages/spaces/_default/Requirements Traceability Summary/page.xml, Verification Validation Summary/page.xml, Risk Control Effectiveness Report/page.xml, System Decomposition Report/page.xml, FMEA Coverage Report/page.xml, Classification Consistency Report/page.xml, System FMEA Report/page.xml, System Structure Navigator/page.xml (0.46) · .polarion/tracker/fields/dal-enum.xml (0.43) · .polarion/pages/spaces/_default/Program Manager Dashboard/page.xml, Safety Engineer Dashboard/page.xml, Design Engineer Dashboard/page.xml, VandV Engineer Dashboard/page.xml, Config Manager Dashboard/page.xml (0.43) · .polarion/tracker/fields/complianceObjective-custom-fields.xml (0.41) · .polarion/nextedy/models/rtm.yaml (0.41) · .polarion/nextedy/sheet-configurations/DO-160G Environmental Qualification.yaml, Component RTM.yaml, Configuration Index.yaml, Design Verification Sheet.yaml, Interface Control Matrix.yaml, Problem Report Tracker.yaml, Process Steps.yaml, Review Action Item Tracker.yaml, SOI Stage Gate Dashboard.yaml, Use Steps Specification.yaml, User Need Validation Sheet.yaml, characteristics.yaml, component-characteristics.yaml, customer-requirements.yaml, design-requirements.yaml, subsystem-functions.yaml, subsystem-verification.yaml, system-elements.yaml, test-verification.yaml (0.41) · .polarion/nextedy/sheet-configurations/DO-178C Objectives Compliance Matrix.yaml (0.40) · .polarion/tracker/fields/designRequirement-subType-enum.xml, environmentalCategory-enum.xml, fta-gateType-enum.xml, cca-analysisType-enum.xml, controlType-enum.xml, riskControlType-enum.xml, verificationMethod-enum.xml, testLevel-enum.xml (0.40)