dependencies, and holistic performance of the NAS to be allocated among integral groups of dependent NAS systems. EA views, more so than roadmaps, help control the impacts of change among NAS systems. 

The PO is responsible for monitoring safety requirements of acquisition programs to ensure the requirements are met through design audits, developmental and operational tests and evaluations, and performance checks (most notably before the Initial Operating Capability and the Post-Implementation Review). The PO must also identify programmatic risks (e.g., cost or schedule) that could affect safety. 

Many functions performed by successful acquisition POs are beyond the scope of the SMS and the SRMGSA. However, some of these functions are relevant to fulfilling the SRM requirements as they relate to acquiring new solutions. Among them are planning and resource management, which includes ensuring that SRM considerations are part of the decision-making process. The PO must ensure that SRM policy and guidelines are followed. 

## PO Roles and Responsibilities 7 

When forming a Program Safety Team (PST), the PO should choose people who are able to: 

• Communicate with program stakeholders, 

Understand program objectives, 

• Understand program plans and acquisition strategy, 

Develop strategy and action plans for the safety compliance of the program, 

• Define safety input into program plans and supplier agreements, 

Perform safety analyses, 

• Track and analyze safety compliance for the program, 

Implement mitigation steps as required, and 

• Report program safety activity and monitoring results. 

The PO must ensure that all members of the PST receive SMS training and understand the SRM process. 

For SRM efforts conducted as part of the AMS process, the PO should hold a meeting with the ANG Enterprise Safety Team (EST) 8  to review any relevant enterprise safety assessments and HEAT reports and to assist with SRM compliance. The PO must include the PST SRM efforts in 

