## 5.3.5 Trace the ASOR Results to the OHA 

Trace the ASOR results to each safety objective identified in the OHA. 

## 5.3.6 Share Safety Objectives and Coordinate Safety Requirements 

Coordinate the ASOR results such that: 

• The impact of the ASOR on the NAS and other operational assessments is identified and reported. 

• The impact of the ASOR on development and qualification of solution elements is identified and reported to the appropriate organizations. This impact includes criteria for quantifying safety objectives, identifying development assurance requirements, considering system architecture (including design features), and reducing the effects of generic design and implementation errors. Criteria for validating the effectiveness of procedural requirements must also be provided. 

## 5.4 Assemble the OSED, OHA, and ASOR as an OSA and Prepare it for Approval 

OSAs must be approved per the guidance in the SMS Manual. ( Note : The PO must submit OSAs that support NAS acquisitions to the ATO Chief Safety Engineer for approval. 11 ) The PO also must upload OSAs to SMTS per the instructions in the SMTS User Manual. 

## 5.5 Validate OSA Results 

Ensure the correctness and completeness of the safety objectives and requirements, including candidate safety requirements identified during the OHA. This ensures that requirements are necessary and sufficient for operational implementation. The validation may include analysis, simulation evaluations, concept testing, and operational trials. The validation includes a consistency check between the safety requirements and the OSED. 

