Create PSSA and SSA Documents

​

PSSA: Allocate Safety Requirements

​

Create the PSSA Document

1. Navigate to Risks space in the Polarion sidebar.
2. Select Create Document and choose the PSSATemplate from RiskTemplates.
3. Name the document (for example, FCC Preliminary System Safety Assessment (ARP 4761)).
4. Open the document — the risksheet loads with 10 columns across 4 views.

​

Populate Safety Requirements

5. For each failure condition in your FHA, add a safetyRequirement row to the PSSA.
6. Set the failureCondLink field to link back to the source failure condition using the allocatesTo link role (back-direction). The classification and dalLevel fields inherit automatically from the linked failure condition.
7. Complete the verificationMethod field — specify how the requirement will be verified (analysis, test, inspection, or review).
8. Set subsystemAllocation to assign the requirement to the responsible subsystem.

9. Link contributing failure modes via the causes relationship to downstream SFMEA/DFMEA items.
10. Use the Allocation Summary view to review DAL distribution across subsystems before proceeding.

​

PSSA Views

​

SSA: Verify Compliance Evidence

​

Create the SSA Document

1. Navigate to Risks space and create a new document from SSATemplate in RiskTemplates.
2. Name the document (for example, FCC System Safety Assessment (ARP 4761)).
3. The risksheet opens with 9 columns across 3 views.

​

Review Failure Conditions and Evidence

4. Each row represents a failureCondition work item reviewed from the FHA. Confirm that classification, probabilityTarget, and dalAllocation are set correctly on each row.
5. Link riskControl evidence records in the Evidence Records column. These records document objective completion — analyses performed, tests executed, reviews conducted.
6. Monitor the Verification Status column, which tracks evidence record completion percentage per failure condition.
7. Use the Compliance Status view to identify failure conditions where DAL objectives remain unmet.

​

SSA Views

​

Traceability Flow

​

Classification-to-DAL Mapping

​

Verification

• A PSSA document with safetyRequirement rows, each linked to a source failure condition via allocatesTo, with dalLevel and classification inherited and subsystem allocation set
• An SSA document with failureCondition rows showing evidence records linked and a non-zero Verification Status percentage in the Compliance Status view

​

See Also

• Identify Failure Conditions — source failure conditions for PSSA input
• Assign DAL to Failure Conditions — DAL classification before PSSA allocation
• Create a Fault Tree Analysis (FTA) — supporting quantitative safety assessment
• Create a Common Cause Analysis (CCA) — independent failure assumption verification
• Read the Certification Readiness Scorecard — track PSSA/SSA completion status