The SRVT must contain the following information: 

• Hazard identification: This identifies each safety hazard. 

• Causes or contributing factors, combinations of which lead to the identified safety hazard: This describes the origin of each hazard. 

• Safety risk evaluation: This shows the results of the safety risk evaluation and indicates the initial and predicted residual risk (i.e., the risk that is present before and after the safety requirements are implemented). 

• Safety requirements: This shows the safety requirements that form the basis for the reduction in risk between the initial and residual state of the system and may refer to another document that describes the controls in more detail. 

• Traceability data: This shows traceability between controls / safety requirements, design requirements, and Verification and Validation (V&V) activities and includes: 

o Requirement identification: This points to the clauses in the design documentation that define requirements relating to a given risk control measure. 

o Test identification: This points to clauses in test procedures or other V&V documents that confirm the controls were implemented as agreed. 

• Method of safety requirement verification: This describes the method used to verify safety requirements. 

• Status information: This tracks the progress in completing SRM activities or highlighting incomplete activities and the plans for completing them. 

## 5.9 Monitoring Plan 

All safety requirements must be verified and validated while the system is being developed prior to system implementation. In a typical acquisition program, the PO must accomplish this by applying development assurance methods, conducting design audits, developmental and operational tests and evaluations, and/or performance checks. 

However, this V&V of safety requirements does not eliminate the need for monitoring the safety performance of the fielded system. The PO must establish safety performance targets for all hazards that were identified in the PHA and develop an operational monitoring plan to track these performance targets. The duration of the monitoring activities will depend on the complexity of the system being deployed, the sites at which the system will be deployed, and the nature of the established performance targets. The risk acceptor or his or her designee must conduct the monitoring. 

The PO must also recognize that: 

• The SSAR may identify workarounds to safety requirements that were not implemented prior to initial deployment despite the ISD authority granting approval to deploy. 

• Additional safety requirements may be developed post-IOC as a result of an Operational Suitability Demonstration, IOA, or PIR. 

If either of these conditions apply, then the PO may need to develop additional or modified post-deployment monitoring plans as part of the SRM effort. 

