## 3.3.2.2 Required Depth and Breadth of the Analysis 

The required depth and breadth of the safety analysis and the amount of collaboration across organizations can vary based the following factors: 

• The complexity of the NAS change. The complexity and nature (i.e., operational or system acquisition) of the NAS change will dictate the type, depth, and number of analyses required. 

• The breadth of the NAS change. The scope of an SRM activity will require additional details when the NAS change affects more than one organization or Line of Business (LOB). 

In general, safety analyses for more complex and far-reaching NAS changes will require a greater scope and more detail. When evaluating a NAS change, consider any potential effect on organizations outside the Air Traffic Organization (ATO) (e.g., the Office of Aviation Safety and the Office of Airports). 

## 3.3.2.3 Involving Other FAA LOBs 

When an ATO safety analysis impacts Federal Aviation Administration (FAA) LOBs and/or organizations outside the ATO, the provisions and guidance in the current version of FAA Order 8040.4, Safety Risk Management Policy , apply. Refer to Section 3.4.5 for information on coordinating and addressing existing  safety issues. Refer to Section 6.4.1 and Section 6.4.2 for discussion on cross-LOB risk acceptance. 

## 3.3.2.4 Setting the Scope of the Analysis 

Guidelines to help determine the scope of the SRM effort include: 

• Having a sufficient understanding of system boundaries, including interfaces with peer systems, larger systems of which the system is a component, and users and maintainers; 

• Determining the system elements that interact or sub-system components that may be affected; and 

• Limiting the system to those elements that affect or interact with each other to accomplish the mission or function. 

When setting the scope of a safety analysis: 

• Define the relationships/interactions of the NAS change. 

• Identify temporal aspects of these relationships/interactions. 

• Collect safety documentation that has assessed the building blocks of the NAS change. 

• Set the scope wide enough to determine the aggregated risk and assess any gaps. 

