Skip to main content

Prerequisites

How the Allocation Works

The link between a failure condition and a safety requirement uses the allocatesTo link role. This is a bidirectional relationship: the FHA failure condition allocates to the safety requirement, and the PSSA row surfaces the source failure condition through a back-link column called Failure Condition Link. diagram The PSSA row inherits the ARP 4761 classification from the linked failure condition automatically — you do not need to re-enter severity.

Steps

1. Open the PSSA document

Navigate to Risks > FCC Preliminary System Safety Assessment (ARP 4761) and open it in Risksheet view. Switch to the Full Analysis view to see all 10 columns.

2. Create a new safety requirement row

In the PSSA risksheet, add a new row. The item type is safetyRequirement. Enter the:
  • Safety Requirement ID — a unique identifier (e.g. SR-FCC-001)
  • Safety Requirement Title — a concise, verifiable objective (e.g. “The FCC shall detect loss of sensor input within 50 ms”)
In the Failure Condition Link column, click the link picker and search for the source failure condition from the FHA. Select the matching failureCondition item. Once linked:
  • The Failure Condition Link column displays the source FHA entry, colored by its ARP 4761 classification
  • The DAL Level column auto-populates (A through E) based on inherited classification
The DAL Level column in PSSA is derived from the linked failure condition’s classification. Do not attempt to override it manually. If the DAL appears incorrect, correct the classification in the FHA first, then verify the PSSA row updates.

4. Assign subsystem ownership

In the Subsystem Allocation column, select the subsystem responsible for implementing this safety requirement (e.g. Sensor Interface Module, Processing Core Module).
The subsystem allocation picklist is constrained to system elements defined in your project. Verify the available entries match your system hierarchy in a live Aero1 PSSA module.

5. Record contributing failure modes

In the Contributing Failure Modes column, note any upstream failureMode items from DFMEA analyses that contribute to this failure condition. This completes the DFMEA→FHA→PSSA chain.

6. Add a risk control task (optional)

If this safety requirement has an associated mitigation action, link a riskControl item in the Risk Control Tracking column. Risk control items are managed in the Risk Control Plan document.
Switch to the Traceability view in the PSSA risksheet to see the complete FHA → Safety Requirement → Risk Control chain in a single layout. This view is useful for certification audits.

Classification Inheritance Reference

FHA ClassificationARP 4761 LevelInherited DALColor
CatastrophicCatARed
HazardousHazBOrange
MajorMajCYellow
MinorMinDGreen
No Safety EffectNSEEGrey

Verification

You should now see the PSSA row showing the linked failure condition in the Failure Condition Link column with its colored classification badge, and the DAL Level column automatically displaying the corresponding assurance level. The Requirements View will list the safety requirement ID and title with its DAL. Check the Traceability view to confirm the allocatesTo link is active between the FHA failure condition and the PSSA safety requirement.

See Also

Code: modules/RiskTemplates/PSSATemplate/attachments/risksheet.json (0.68) · .polarion/tracker/fields/workitem-link-role-enum.xml (0.64) · modules/RiskTemplates/FHATemplate/attachments/risksheet.json (0.64) · 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.60) · modules/RiskTemplates/SSATemplate/attachments/risksheet.json (0.58) · .polarion/tracker/fields/workitem-type-enum.xml (0.58) · .polarion/nextedy/models/rtm.yaml (0.58) · .polarion/nextedy/sheet-configurations/ARP 4761 Safety Assessment Traceability.yaml (0.58) · modules/RiskTemplates/System-FMEATemplate/attachments/risksheet.json (0.57) · .polarion/tracker/fields/failureCondition-classification-enum.xml (0.56)