Preparing, Performing, and Documenting a Safety Analysis  Section 5  7 5  5.4_SMSM_201904  Originally published April 2019  Uncontrolled copy when downloaded • The current hardware or software system or existing procedures/operations and the corresponding (operational) system states. • A brief background on what triggered the need for a NAS change or the evaluation of an existing safety issue. If there is an associated SRM document, compliance issue, or Top 5 issue that necessitated this NAS change, briefly summarize it here and include the associated reference or documentation as attachments. 1. Concurrence. This signature is used to represent a technical review of the safety analysis and to confirm that the rationale used throughout is consistent with the overall risk assessment. The concurrence signature comes from an SRM expert who is well versed in the SMS Manual and familiar with the terminology and processes therein. Refer to  Section 6.5. 2. Approval. Include an approval signature from an official representing the organization responsible for implementing the NAS change (and from the ATO Chief Safety Engineer, if required). An approver provides a technical and administrative quality control review of the safety analysis, its findings, and the identified results. Refer to Section 6.6. 3. Risk Acceptance.   Include a risk acceptance signature from an appropriate official representing the organization that will be using the safety-assessed NAS equipment, policy, or procedure. This signature indicates acknowledgment of the identified safety risk(s) and denotes its acceptance into the NAS upon implementation of the NAS change. Refer to Section 6.4. If no hazards are identified, do not include the above tables. Instead, provide a brief rationale  for a safety finding without hazards.  Listed below are the signatures required on the SRM document signature page. For each  signatory, include the printed name, signature (handwritten or electronic), organization, and  date. Signatures should be obtained, and must be listed, in the following order: concurrence  (where appropriate), approver, risk acceptor, and ATO Chief Safety Engineer (when necessary). The safety requirements signatures from the responsible organization(s) and associated POC(s)  are contained within the Executive Summary. Provide a detailed description of the hardware/software system, operation, or procedure that  constitutes the NAS change or the environment in which the existing safety issue has  manifested. Refer to Section 3.3 for information on Phase 1 of the DIAAT process, “Describe  System.” Include the following information when applicable:  5.4.4.3 Current System  5.4.4.2 SRM Document Signatures  Safety Performance Target  Associated  Hazard ID  Safety Requirement  Associated  Hazard ID(s)  Organization  Responsible  POC  Signature  Table 5.5: Monitoring Plan Summary  Table 5.4: Safety Requirements 