Integrated Safety Management represents a more robust, holistic, and integrated approach to  performing safety analyses. It uses existing safety policy and methodologies as well as  Systems Engineering processes. It is a critical component not only for successfully achieving  the NextGen vision, but also for implementing all enhancements to the NAS.  Directionality is a critical aspect of Integrated Safety Management. Safety assessments using  Integrated Safety Management principles must be conducted in three “directions”:  Identifying hazards and assessing safety risk remains the basis of all safety management efforts  for FAA programs. Integrated Safety Management does not change the basic SRM process; it  expands the perspective of the required analysis and uses existing elements of the FAA’s  Systems Engineering process to ensure that no safety gaps occur as aviation capabilities are  developed and implemented in the NAS.  The PO is responsible for conducting a robust system safety effort for any ongoing system  development, which entails conducting and approving required safety analyses. However, due  to the technical nature of most systems, the FAA typically cannot conduct such an effort without  extensive coordination/cooperation with the system developer during the Solution  Implementation phase. Details on this coordination/cooperation must be clearly defined in the  Statement of Work (SOW) contained in the contract between the FAA and the system  developer. The SOW should be supplemented by Data Item Descriptions (DIDs). ( Note : DIDs  are available on the FAST website. The PO may tailor any DID to reflect the requirements of a  particular program.)  Consider the following while developing contractual requirements for a system safety effort:  • Vertical integration  ensures the consistency of safety assessments across hierarchical levels from the program or system level up to the NAS level. It essentially is a look “up” the NAS at enterprise-level / project-level architectural alignment. • Horizontal integration  ensures that the interactions and interdependencies across organizations, operational capabilities, portfolios, operational improvements, increments, current operations, and individual programs or systems are addressed in safety assessments. It is essentially a look “across” the NAS at project-level, inter-architectural alignment, linkages, and interdependencies. • Temporal integration  ensures that the impacts of hazards and their associated mitigations across implementation timelines are understood and taken into consideration. It is a look at the impact of phased implementations of NAS initiatives. • System safety is a basic requirement of the total system. The results of the system safety effort depend on the PO’s clear communication of objectives/requirements in the SOW. • System safety requirements are basic tools for systemically developing design specifications. • System safety must be planned as an integrated and comprehensive safety engineering effort that is sequential and continual. o The system developer’s System Safety Program Plan (SSPP) must align with the PO’s PSP. 9_SRMGSA_202003  Originally published March 2020  Uncontrolled copy when downloaded  50 9.3  FAA / System Developer Interface 