## 4.5.2.1 PST 

A PST is a resource provided by the PO to support the safety efforts of an acquisition throughout the AMS lifecycle. The composition of the PST depends on the size and complexity of the program under consideration. 

The PST, in conjunction with the AJI Safety Case Lead (SCL), defines the planned safety effort and ensures that the required safety products are prepared to support the JRC decision process. 

The PST must: 

• Provide a central Point of Contact (POC) to coordinate all safety analyses throughout the program’s lifecycle; 

• Participate in Safety Strategy Meetings (SSMs) to determine the safety effort required in support of the AMS milestone decisions; 

• Support the safety analyses in accordance with the guidelines in the AMS FAST, the SMS Manual, ATO Safety Guidance (ATO-SG) documents, and the SRMGSA; 

• Submit the proposed Program Safety Plan (PSP) and completed SRM documents to the AJI SCL for review and coordination to ensure timely decisions in support of JRC milestone decisions; 

• Ensure the developer’s contract includes provisions to support AMS development assurance safety requirements; 

• Review all development assurance documents to include RTCA 10  DO-278A, Software Integrity Assurance Considerations for Communication, Navigation, Surveillance and Air Traffic Management (CNS/ATM) Systems , (or equivalent document) lifecycle data; 

• Enter required safety documentation into the Safety Management Tracking System (see Section 8.5 for more information); 

• Address any safety analysis and assessment results in program planning and requirements documents; 

• Incorporate any safety issues identified by the SCT or ANG EST into program safety efforts; 

• Include any requirements developed as a result of the safety analyses as discrete requirements in the preliminary Program Requirements Document (PRD), the initial PRD, or the final PRD; 

• Trace the safety requirements back to identified safety hazards; 

• Verify that the mitigations identified to reduce safety risk are included as validated and verified safety requirements in the final SRM document; 

• Support the establishment of traceability between safety analysis results and the NAS EA; 

• Maintain safety documentation throughout the system lifecycle; 

