PSP. In addition, the timing of the required safety analyses must be consistent with the  engineering milestones outlined in the  FAA Systems Engineering Manual (SEM). A Data Item  Description (DID) describes the SSPP requirements to be placed on contract. (DIDs are  available in the DID Library.) These DIDs may be tailored by the PO as necessary. The  specific delivery timeframes and review processes for each DID must be included in the  Contract Data Requirements List.  In addition:  • Any SRM panel facilitated or conducted by the developer (i.e., to develop a Sub-System  Hazard Analysis or a System Hazard Analysis) must include Subject Matter  Experts (SMEs), particularly those with an operational perspective. This must be  reflected in both the PSP and the SSPP and within the developer’s contract.  • The government must actively review and be able to modify/comment upon the safety  analysis documentation as it is being prepared by the developer (i.e., not just at its final  delivery). This must be reflected in both the PSP and the SSPP and within the  developer’s contract.  • An AJI-approved PSP must be in place prior to any Joint Resources Council (JRC)  milestone decision or In-Service Decision (ISD), per AMS policy. As system functionality  is often operationally released in segments or phases, there may be multiple ISDs for an  acquisition or modification to an existing NAS system. The PSP to support the Final  Investment Decision (FID) must discuss ISD strategy (i.e., required number of ISDs)  documented in the Implementation Strategy and Planning Document (ISPD)). It is  possible that separate PSPs may be required for each segment/phase.  • If the deployment strategy is not well-defined at the FID, the ISD strategy may simply  state that the entrance criteria for an ISD (i.e., test, security, safety, and Independent  Operational Assessment (IOA)) will be met for each release/phase of the deployment. In  this situation, the PSP may need to be updated during Solution Implementation to  accurately reflect the final ISD strategy. In addition, if the deployment strategy changes,  the JRC requires that the ISPD be updated to incorporate the changes; the PSP may  also need to be updated if these changes affect the ISD and/or safety strategy.  • The PSP must reference the version (i.e., the publication date) of the SRMGSA / SMS  Manual in effect when the PSP was prepared. Upon PSP approval, the applicable  versions of the SRMGSA / SMS Manual will become the operative documents that the  PO must follow for the remainder of the program unless the program is restructured via a  change in scope, segmentation, or rebaselining. The PO should consult with the AJI  Safety Case Lead (SCL) for advice when this has occurred because the approved PSP  may no longer apply, and the PSP may have to be updated. The PSP must summarize  or reference the PSAA when it is finalized.  1) Identify the SSP requirements;  2) Develop a safety strategy based on these requirements;  3) Translate the developed safety strategy into a PSP;  4) Submit the PSP for approval and signature;  5) Implement the SSP in accordance with the PSP;  5  Procedures  There are seven key steps in preparing/implementing a PSP:  A_SRMGSA_202003 Originally published March 2020  Uncontrolled copy when downloaded  A-2 