However, to gain the maximum benefit for the program, the SSM should occur early enough in the process to schedule SRM documentation development, review, coordination, and necessary approvals prior to the PO’s next investment milestone decision point. SRM is a required checklist item for the Investment Analysis Readiness Decision (IARD), the Initial Investment Decision (IID), the Final Investment Decision, and the In-Service Decision. 

In addition to the overall safety strategy, the Program Safety Plan (PSP) and any other SRM products (e.g., Operational Safety Assessment and Comparative Safety Assessment) may be discussed. For each SSM, AJI must prepare meeting notes documenting the strategy agreed upon by attendees to satisfy acquisition SRM requirements. The Enterprise Safety and Information Security Division, ANG-B3, should be invited to participate in all SSMs. For SSMs held for programs in or about to enter the Concept and Requirements Definition (CRD) phase, the POs must consult with the ANG CRD lead before the SSM convenes. The SSM discussion must also include the ramifications of implementing Appendices J, K, L, and M of the Safety Risk Management Guidance for System Acquisitions (SRMGSA) and any requirements that need to be included in the PSP. 

Sometimes, acquisition strategies change or there is not enough information available to determine the SRM documentation requirements for the entire acquisition lifecycle. If so, additional SSMs may be scheduled as often as necessary. 

The PO must use the results of the SSM to develop a program-specific PSP, which must be approved by the ATO Chief Safety Engineer. A PSP must be approved before the IARD, if feasible, but no later than the IID. The PSP defines which safety analyses/assessments must be conducted during a system acquisition and which safety requirements must be fulfilled before system deployment. If documented in an approved PSP, the PO may use alternative methods other than those described in the SRMGSA’s appendices to capture required information. Also, if documented in an approved PSP, the PO may prepare a combined analysis (i.e., a combined System Hazard Analysis / Sub-System Hazard Analysis) or bypass analyses entirely to meet AMS requirements. 

## 5.2.1 Consistency with the Implementation Strategy and Planning Document 

As stated in Sections 2.3.3.1.4 and 2.3.4.1.5, the PO is responsible for preparing an Implementation Strategy and Planning Document (ISPD). Section 7.1 of the ISPD specifically addresses the program’s system safety plans. This section must be approved by the ATO Chief Safety Engineer. At the SSM, the AJI SCL must work with the PO to ensure that the safety strategy that is or will be delineated in the ISPD is consistent with that in the PSP. 

## 5.2.2 Technology Refreshment Portfolio 

For a Technology Refreshment (TR) portfolio, the TR Portfolio Manager must contact the AJI SCL and conduct an SSM prior to developing the portfolio PSP to assist in tailoring any safety documentation requirements. It is possible that the complexity of some sub–Acquisition Category (ACAT) 1 TR projects may warrant the development of project-specific PSPs to supplement the portfolio PSP; this need must be detailed in the approved portfolio PSP. There is no need to develop project-specific PSPs for sub-ACAT 2 TR projects because the portfolio PSP would outline the SRM and development assurance requirements for these projects. 

