HQ0858-20-R-0003 Att J-01 TEAMS-Next Safety SOW 29 May 20.pdf

HQ0858-20-R-0003

Attachment J-01 (Safety) SOW

Approved for Public Release

20-MDA-10497 (29 May 20)

TEAMS-Next Statement of Work

Safety

29 May 2020

Revision History

Author Date MR Number P00000 Reason For Change(s) SOW Version

29 May 20 Baseline 0

1.0 Top Level Overview

1.1. Purpose

The Missile Defense Agency (MDA or Agency) requires Safety services providing high quality, professional services identified in this Statement of Work (SOW).

The requirements in this contract are for Agency-wide Safety services directed by the MDA

Quality, Safety & Mission Assurance (QS), supporting Senior Leadership, Execution, and

Functional Management organizations.

1.2. Organizational Description & General Requirements

The Missile Defense Agency (MDA) established the QS organization to perform a continuous assessment of the engineering, technology, processes, production, and programmatic practices used to develop and operate the Missile Defense System (MDS) such that high risk attributes can be identified and addressed to increase confidence in achieving mission success while ensuring personnel safety.

The QS Directorate plans, executes, analyzes and reports technical results for all MDA operations and MDS design, development, production, testing and operations. The QS Directorate functions as an independent, unfettered and unrestricted, non-advocate technical organization for MDA with a specific focus on mission success and personnel safety. It provides executive leadership and policy direction on all quality, safety and mission assurance (QSMA) matters throughout

MDA and ensures compliance with QSMA strategies, policies, agreements and standard practices to advance capabilities and ensure that effective and efficient functional management is in place to enhance the success of MDA.

As reflected in the figure below, this organization has two offices that align with MDS and programs operations to manage the overall execution of the QSMA Program across the agency, including the SOH Program for ground mishap prevention. In addition, there are QS Program

Functional Leads that manage the QSMA program within the Program Elements and serve as technical advisors to the QS Director and assigned Program Director/Program Manager (PD/PM) to help ensure mission success by providing oversight and insight to acquisition, development, fielding, integration and operations. The Functional Leads are responsible for coordinating the daily tasking of assigned functional personnel and provide the day-to-day, working level interface between MDA functions, Programs, and QS Directorate.

1.2.1. Non-Personal Services

The Government shall neither supervise Contractor employees nor control the method by which the Contractor performs the required work. It shall be the responsibility of the

Contractor to manage its employees and to guard against any actions that are of the nature of personal services, or give the perception of personal services. If the Contractor believes that any actions constitute, or are perceived to constitute personal services, it shall be the

Contractor’s responsibility to notify the PCO immediately

1.2.2. Business Relations

The Contractor shall successfully integrate and coordinate all activity needed to execute the requirement. The Contractor shall manage the timeliness, completeness, and quality of problem identification. The Contractor shall provide corrective action plans, proposal submittals, timely identification of issues, and effective management of subcontractors.

The Contractor shall seek to ensure customer satisfaction and professional and ethical behavior of all Contractor personnel

1.2.3. Contractor Flight and Ground Operations involving Air Force

The contractor shall comply with non-crewmember requirements set forth in DCMA

Instruction 8210.1C Change 1 dated April 5, 2017 (Air Force Instruction 10-220), “Contractor’s Flight and Ground Operations” as applicable.

1.3 Reference Documents

20-MDA-10497 (29 May 20)

MDA Director’s Safety Policy (MDA Memorandum 12)

MDA Program/Project Director’s Safety Policy

Accident and Mishap Safety Investigations and Reporting (MDA Instruction

6055.02-INS)

MDA Assurance Provisions (MAP, MDA-QS-001-MAP)

Work Time Restrictions for Safety and/or Mission Critical Personnel Supporting

Tests and Critical Operations (MDA Instruction 6055.04-INS)

MDA Instruction 6055.06-INS, Defense Explosives Safety Regulation 6055.09, DoD

4145.26M, and Service/installation specific explosives Safety requirements

Program Unique Safety Documentation Management Plans and Policies

Support development of Program POA&M for inclusion in the Agency-level IM

Strategic Plan

DoD 6055 Series Standards and Directives

OSHA 29 CFR 1960, Basic Program Elements for Federal Employees OSHA

MDA SOH Program Management Directive, MDA 6055.01, SOH Program Management

QS Mission Assurance Audit Program Standard Operating Procedure, QS-SOP-06

MIL-STD-882

BMDS System Safety Program Plan (QS-SOP-14)

Support under this requirement will be completed using the referenced documents listed in this section. While this section provides documents to be used completing this requirement, work is not limited to these documents. Other documents may be provided by the

Government, or required by the Government, for use in supporting this requirement throughout the life of the contract.

2.0 Non-Disclosure Agreements

The Contractor shall obtain from each employee under this contract, a written MDA NDA (Section

J Attachment 06) which shall provide that the employee shall not, during his/her employment by the

Contractor or thereafter, disclose to others or use for their benefit, privileged government information or proprietary data received in connection with the work under this contract. The

Contractor shall educate its employees regarding the philosophy of FAR Part 9.505-4 so that they will not use or disclose government information or proprietary data acquired in the performance of this contract.

The MDA NDA is required of all Contractor employees and Subcontractors supporting this effort;

however, there may be additional NDAs required (i.e., H-16, Planning, Programming, Budgeting and Execution (PPBE)) dependent upon the support required at any given time throughout period of performance of the contract. The Contractor shall certify completion of the MDA NDA requirement and others applicable NDAs for each employee via the Monthly Manpower Report

(Contract Data Requirements List (CDRL) A004).

3.0 Scope of Work

3.1 Contract Program Management and Safety Support Functions

The Contractor shall provide the following functions:

a) Manage and execute all activities under this contract, including those of subcontractors, suppliers, and any and all sub-tier vendors.

b) Conduct and integrate all aspects of the contract such as schedule, cost, risk and opportunity management.

c) Recruit and maintain qualified personnel to support the required workload.

d) Provide technical status to ensure successful reviews and execution of the program.

e) Provide the necessary administration required to support the contract and provide coordination for the development of presentations, the arrangement and coordination of reviews and meetings.

f) Identify, estimate and report to Government contacts expected increases to budget prior to cost being incurred

g) Develop alternative approaches to accomplishing increases in tasks without increases to budget

3.2 Support MDS-Level Safety Program.

The contractor shall provide technical and program management support for the QS directorate at the

“Core”/ MDS-level to execute tasks listed below. The listed tasks are those which are typical in support of the MDA Safety Office. Some of the tasks may be repeated often, and others may not be executed during this period of performance. [NOTE: Core or MDS-level refers to QS personnel who are not assigned to individual programs, but instead are concerned with the whole integrated system / interactions between Elements, vice Element-level support which is concerned with only one project or sub-system component. Support at the MDS-level also includes a focus on policy development and oversight.] The contractor will often be required to deliver verbal or written reports which are part of the task, and maintain historical files after task execution. The specific requirement will be determined prior to execution of the tasks described below.

3.2.1 Support Development, Implementation, and Execution of MDS safety policies, requirements, and programs at the MDS level.

a. MDA and Department of Defense (DoD) Safety Policy at the MDS Level. The contractor shall support the development and implementation of safety policy and program documentation compliant with applicable DoD and MDA safety standards as well as local, state, federal, and international laws. The contractor shall support the review of each safety policy and directive for applicability to MDS and support the implementation for required MDS programs. The documents to be implemented will be based on DoD Safety policies as well as MIL-STD-882, and will include the following:

1) MDA Director’s Safety Policy (MDA Memorandum 12).

2) BMDS System Safety Program Plan (QS-SOP-14).

20-MDA-10497 (29 May 20)

3) Accident Investigations and Reporting (MDA Instruction 6055.02-INS).

4) Work Time Restrictions for Safety and/or Mission Critical Personnel Supporting

Tests and Critical Operations (MDA Instruction 6055.04-INS).

5) MIL-STD-882, Department of Defense Standard Practice for System Safety.

6) MDA Assurance Provisions (MAP, MDA-QS-001-MAP-Rev C).

7) Safety, Quality and Mission Assurance Isolation Protection profile (MDA-QS-IPP-

001 V2.0)

b. Maintain Safety Records. The contractor shall archive MDS-level safety records in a safety records library (including the Change Tracking and Integration tool on the Safety Division

(QSS) portal (i.e., MDA internal website), or other tool as directed by the Government) in compliance with MDA Records Management Policy (MDA Directive 8180.01).

c. System Safety Requirements for the MDS. The contractor shall Support MDS-level System

Safety requirements processes to include:

1) Participating in safety requirements development process and assisting with incorporating defined requirements in the MDS System Specifications, element-level specifications, and information exchange requirements.

2) Providing suggested updates to the safety section of the MDA Assurance Provisions

(MAP, MDA-QS-001-MAP) to capture all new and updated Office of the Secretary of

Defense (OSD) and MDA safety requirements and policies, and to capture safety lessons learned.

3) Verifying all applicable MDS safety requirements are included in Program and

Project level specification documents for all Programs.

d. Safety Policy Compliance. The contractor shall assist the Safety Division with reviews of the documents identified below to verify compliance with MDS Safety Policies and requirements:

1) MDS System Specifications and interface control documentation.

2) Program-level safety documents.

3) OSD and MDA Safety Policies, including drafts, revisions, and updates. Verify new or updated requirements are flowed into Program and Project level safety documentation.

4) Program level safety policy documentation.

e. System Safety Approach. The contractor shall assist the Safety Division in the development and maintenance of Safety Program documentation including:

1) Annual update to the MDS System Safety Program Plan.

20-MDA-10497 (29 May 20)

2) Maintain MDS hazard tracking system data using the Change Tracking & Integration

Tool on the QSS portal.

3) QS Directorate’s Change Tracking and Integration site on the MDA Portal

Knowledge On-line (MKO).

One- time update to the QSMA Isolation Protection Profile (IPP). The IPP is an MDA

Technical Standard defining design and verification safety requirements for the physical and cryptographic isolation of Test, Training, and Exercise (TT&E) data on MDS computing and communication architectures. The IPP requires updating in response to multiple new technologies proposed for use on BMD Systems. The focus of this effort will be designing safety into computing and communication architectures so as to reduce the likelihood of human and software errors.

3.2.2 Support System Safety Risk Identification and Management Process at the MDS level

a. Evaluations of Safety documentation, system design, and baseline changes. The contractor shall perform initial detailed evaluations of safety documentation, system design, and baseline changes to determine the overall safety impact of those changes to the safety of the MDS, including assessing the likelihood and severity of hazards created and the overall system safety risk. Reviews will assess compliance with the requirements principally identified in the MAP

(as tailored) and other applicable DoD standards for system and software safety (e.g. MIL-STD-

882, AMCOM Policy 385-17), and local, state, federal, and international laws; and other requirements imposed by test ranges and Services. These evaluations include the following:

1) Review Program-level system safety assessment reports for completeness, technical accuracy and assessment of safety risk to the overall MDS (i.e. unintended or unsafe interactions among elements/programs). The systems under consideration include:

interceptors; targets; sensors; mobile launchers (land and sea-based); weaponized lasers;

and command, control, battle management and communications systems.

2) Review MDS software safety requirements, analyses, and test results.

3) Review verification evidence and provide assessment of whether safety specifications, hazard mitigations, and requirements are met.

4) Review Baseline Change Requests (BCR) presented to the MDS Integration

Synchronization Group (ISG), Systems Engineering Integration Council (SEIC), MDS

Requirements Working Group (MRWG), Interface Control Working Group (ICWG) or other MDA Boards.

a) The contractor shall track their findings and observations regarding BCRs using the QS Change Tracking and Integration Portal at MKO.

b) The contractor shall assist the government in preparing a QSMA slide (chart) in accordance with the ISG template for each BCR reviewed in order to support and provide additional information for the baseline change.

20-MDA-10497 (29 May 20)

5) Assess recent Government/Industry Data Exchange Program (GIDEP) reports for risk impacts to the MDS.

b. Program Reviews and Meetings. The contractor shall support program reviews and/or meetings addressing development, operations and testing of the MDS. Tasks associated with this activity include:

1) Attending and supporting system-level design reviews and assessing changes throughout the life-cycle of the Programs/Project.

2) Attending and supporting design and test reviews, execution meetings such as IPT meetings, working groups, change and failure review boards, and technical interchange meetings (TIM) to identify and characterize risks at the integrated MDS level.

3) Attending and supporting milestone reviews including Preliminary Design Reviews

(PDR), Critical Design Reviews (CDR), Ship Readiness Reviews (SRR), Test Readiness

Reviews (TRR), Mission Readiness Reviews (MRR), and Flight Readiness Reviews

(FRR).

4) Assisting in the tracking and closure of safety-related action items assigned during program reviews/meetings.

c. Safety Audit Support. The contractor shall support Safety Audits and report deficiencies identified in the audits related to implementation of, and compliance with, MDA safety policies and requirements at the following locations:

1) Government, Prime Contractor, and Sub-contractor facilities.

2) Operational fielding or deployed sites.

3) Test Ranges.

The contractor shall perform safety audit follow-ups, track findings, and verify closure within the guidelines identified in the Mission Assurance Audit Program Standard Operating

Procedure, QS-SOP-06.

d. Safety Assessments and Analysis. The contractor shall participate in the development and review of safety risk assessments and other safety analysis and assist in obtaining approval from the appropriate authority in accordance with (IAW) the MAP. Tasks associated with this activity include:

1) Developing professional quality MDS Safety Assessment Reports (SAR) (DI-SAFT-

80102B) addressing risks at the integrated MDS Level, and summarizing results of the

System Hazard Analysis (SHA) and Operation and Support Hazard Analysis (O&SHA).

Preparing System Safety Risk Assessments (SSRA) Reports, risk acceptance memos and associated briefings for Baseline Change Requests and MDS-level tests.

2) Developing MDS-level SSRAs and associated risk acceptance packages per MAP section 3.14 in response to planned test activities, identified hazards, and capability deliveries.

20-MDA-10497 (29 May 20)

3) Reviewing Program-level SSRAs, acceptance memos, and associated briefings to verify accuracy and to identify deficiencies or safety impacts outside of the Program.

4) Preparing and documenting a MDS-level Preliminary Hazard Analysis (PHA).

5) Performing a MDS-level SHA annually IAW MIL-STD-882E Task 205 per DI-

SAFT-80101B.

6) Performing a MDS-level O&SHA annually IAW MIL-STD-882E Task 206.

7) Evaluating technical change proposals or presentations to agency-level change control boards. This task may include entering comments in the Change Tracking and

Integration (CT&I) database or the Task Management Tool database. It may also include preparing a single “QSMA slide” summarizing findings.

8) Supporting development of a Plan of Action and Milestones (POA&M) for inclusion in the Agency level Insensitive Munitions (IM) Strategic Plan which is required every other year. The next IM Strategic Plan is due in February 2022.

9) Staffing and obtaining concurrence on safety analyses, reports, and plans.

10) Attending and participating in the DoD Insensitive Munitions IPT.

11) Coordinating MDA IM working groups, and preparing meeting invitations and minutes.

12) Supporting Joint Services Insensitive Munitions Technical Panel and Joint

Insensitive Munitions Technical Panel Munitions Advanced Technology Group meetings.

13) Reviewing and providing recommendations on program Insensitive Munitions

Documentation.

e. System Safety Working Groups. The contractor shall support and attend System Safety

Working Groups (SSWGs). Support tasks for SSWGs include activities such as:

1) Arranging facilities and logistics for MDS SSWGs, including securing audio/visual

(A/V) capabilities and communications means.

2) Recording minutes and action items from the MDS SSWGs, and publishing IAW the

MDS SSWG charter.

3) Developing briefings for assigned MDS SSWG topics.

4) Tracking action items generated by the MDS SSWG and reporting closure status

IAW the program MDS SSWG charter.

5) Attending Program SSWGs as the QS representative. Prepare and present briefings on

MDS-level topics that affect the Programs. Provide summary details of meeting topics and potential safety impacts.

20-MDA-10497 (29 May 20)

6) Arranging facilities and logistics for MDA Insensitive Munitions Working Groups.

f. Electronic Hazard Tracking System. The contractor shall maintain data and assist with populating and updating records in a web-based electronic hazard tracking system to document the identification, mitigation, verification, and assessment of residual safety risks.

g. End of Week Report. The contractor shall provide an end-of-week (EOW) report for each person supporting tasks under this SOW to document significant issues and milestones in support of this Performance Objective. Reporting shall follow the requirements for reporting and formatting found in the QS EOW Report Development Guideline.

h. The contractor shall provide work instructions (CDRL A007) for each position. These work instructions shall document the work processes for the individual position. These processes must be updated as necessary IAW CDRL.

3.2.3 Support Safe Conduct of MDS-Level System Demonstration Activities, Including Flight and

Ground Tests

a. Test Planning Support and Verification/Validation. The contractor shall provide test planning support and verification/validation for the following tasks. The tasks and subtasks include the following:

1) Evaluating mission specific safety risks, particularly for interaction of the test event with other systems within the MDS.

2) Assessing test architecture for safety concerns at the MDS-level.

a) Test article(s) include required safety features incorporated.

b) Interaction with other systems within the MDS.

c) Isolation of test assets from operational assets to include isolation of test data passing over Tactical Data Link (TDL) and other communication systems.

3) Reviewing test plans and procedures for safety concerns.

4) Supporting development of IM and Final Hazard Classification (FHC) detailed test plans.

a) Plans incorporate TB 700-2 and MIL-STD-2105/STANAG requirements.

b) Test article fidelity is sufficient to meet test plan requirements.

b. Test Documentation. The contractor shall review and provide initial safety assessments of specific test documentation to include the following tasks:

1) Reviewing and assessing BMDS Discrepancy Reports (BDR) for potential safety risks and mitigation, considering safety impacts to the integrated MDS, and to individual

MDA Programs.

20-MDA-10497 (29 May 20)

2) Reviewing the interface documents and providing an assessment of whether test assets are adequately isolated from operational assets.

3) Reviewing waivers and deviations to safety policies.

4) Reviewing Ground Test execution plans and analysis plans.

c. Integration and Test. The contractor shall provide on-site support for Integration and Test to include the following tasks:

1) Participating in pre-test reviews, such as, Test Planning Reviews (TPRs), TRRs, MRRs, FRRs, and pre-mission daily status briefings.

a) Support development of briefing materials.

b) Track safety-related action items to closure.

2) Witnessing countdown tests.

a) Verify compliance with countdown documentation and procedures.

b) Document and report any safety variations and/or anomalies.

3) Participating in Failure Reviews and Mishap Investigations (Support to mishap investigations will be limited to no more than 2 weeks unless extended at the direction of the Government).

a) Support development of briefing materials.

b) Participate as the QS representative for safety.

c) Track safety-related action items to closure.

3.2.4 Support Safe Interoperability of MDS Elements when Communicating Over MDS and

Non-MDS Communication Systems.

a. Network Vulnerability Assessment. The contractor shall assess networks (MDS and Non-

MDS) used to support communications between MDS elements to identify vulnerably which might allow Test, Training, and Exercise (TT&E) data to leak to safety critical environments having live ordnance.

b. Develop Safe Isolation. The contractor shall in conjunction with MDS program offices, external agencies, and military services develop network architectures, operational concepts, and procedures to ensure the safe isolation of TT&E data from safety critical environments.

3.2.2

c. Records. The contractor shall document findings and recommendations per paragraph 3.2.2.

3.3 Support Program/Project Safety Programs.

Task Details. The contractor shall provide technical and program management support for the QS directorate at the Program/Project level to execute the tasks listed below. The listed tasks are those

20-MDA-10497 (29 May 20) which are typical in support of the MDA Safety Office. Some of the tasks may be repeated often, and others may not be executed during this period of performance. The contractor shall deliver verbal or written reports which are part of the task and maintain historical files after task execution. The specific requirement will be determined prior to execution of the tasks described below.

3.3.1 Support Development, Implementation and execution of safety policies, requirements, and programs at the Program/Project level Task details are as follows:

a. MDA and DoD Safety Policy at the Program/Project Level. The contractor shall support the development and implementation of safety policy and program documentation including safety program, policy, requirements, analyses, reports, and plans to meet applicable DoD, service and installation specific, MDA safety and core standards and local, state, federal, and international laws. The documents to be implemented will be based on DoD Safety policies as well as MIL-STD-882, and may include the following:

1) MDA Director’s Safety Policy (MDA Memorandum 12).

2) Program/Project Executive/Director’s Safety Policy.

3) Accident and Mishap Safety Investigations and Reporting (MDA Instruction 6055.02-

INS).

4) MDA Assurance Provisions (MAP, MDA-QS-001-MAP).

5) Requirements for Hazardous and Safety-Critical Procedures (MDA Instruction

6055.03-INS)

6) Work Time Restrictions for Safety and/or Mission Critical Personnel Supporting

Tests and Critical Operations (MDA Instruction 6055.04-INS).

7) Explosives Safety Plan (Defense Explosives Safety Regulation (DESR) 6055.09, DoD 4145.26M, and Service/installation specific explosives safety requirements).

8) Program Unique Safety Documentation Management Plans and Policies.

9) Support development of Program POA&M for inclusion in the Agency-level IM

Strategic Plan.

b. Safety Records. The contractor shall maintain Safety Records. The contractor shall archive all Program and Project safety records in a safety records library incompliance with program/project level guidance and IAW MDA Record Management Policy (MDA Directive

8180.01).

c. Program and Project System Safety Requirements. The contractor shall support development of Program and Project System Safety requirements, to include:

20-MDA-10497 (29 May 20)

1) Confirm all Government defined safety requirements are included in the Program and

Project System Specifications, Statements of Work, and Contracts.

2) Provide recommended updates to the MDA Assurance Provisions (MAP, MDA-QS-

001-MAP) to capture all new and updated OSD and MDA safety requirements and policies, and to capture safety lessons learned.

3) Verify appropriate Range Safety requirements are included in Program and Project safety requirements for all ranges identified for each Program in the MDA Integrated

Master Test Plan and recommend tailoring approaches as required.

d. Safety Policy Implementation. The contractor shall assist the Program Safety Office with the development and implementation of safety policies within the Programs/Projects and performing reviews and recommending updates and modifications of the following documents addressing safety requirements and policies:

1) Documentation for other MDA contracts, such as Contract Data Requirements Lists

(CDRLs), Statement of Work (SOW), and award fee or Contractor Performance

Appraisal Report (CPAR) plans/factors associated with safety requirements.

2) Program Capabilities Document.

3) Interface Control Documents (ICD). ICDs exist between the MDS and programs and between programs.

4) Program/Project System Specifications.

5) OSD and MDA Safety policies, including drafts, revisions, and updates. Review policies and flow new and updated safety requirements into Program and Project level safety documentation.

e. Documentation. The contractor shall assist the Program Safety Offices in the development of safety documentation for testing and/or fielding of a system. Documentation may include:

1) Safety Releases (training warfighters) in accordance with applicable Service requirements.

2) Air Transport Waiver Documentation for Hazardous Materials in accordance with Air

Force Materiel Command guidelines.

3) Hazard Classification Documentation in accordance with Technical Bulletin (TB)

700-2.

4) Department of Transportation documentation in accordance with 49 Code of Federal

Regulation (CFR).

20-MDA-10497 (29 May 20)

5) Safety statements for Materiel Release in accordance with Army Regulation (AR)

700-142 or applicable Service requirements.

6) Support fielding activities for Foreign Military Sales.

f. System Safety Approach. The contractor shall assist the Program Safety Offices in the development and maintenance of:

1) An MDA Program Office System Safety Management Plan in accordance with MIL-

STD-882 and the MDA Assurance Provisions.

2) The development of the safety section of the Programmatic Environmental Safety

Occupational Health Evaluation (PESHE).

g. End of Week Report. Each individual performing tasks under this SOW shall provide an

EOW report to document significant issues/milestones in support of this requirement. Reporting shall follow the requirements for reporting and formatting found in the QS EOW Report

Development Guideline.

h. The contractor shall provide work instructions (CDRL-A007) for each position. These work instructions shall document the work processes for the individual position. These processes must be updated as necessary IAW CDRL.

3.3.2 Support System Safety Risk Identification and Management Process at the Program/Project level

a. Evaluation of Safety System Design and Baseline Changes. The contractor shall evaluate the safety of system design and baseline changes, at the program level, to determine the impact of those changes to the safety of the system, including assessing the likelihood and severity of hazards created and the impact to overall system safety risk. Reviews will assess compliance with the requirements principally identified in the MDA Assurance Provisions (as tailored) and other applicable DoD standards for system and software safety (e.g. MIL-STD-882, AMCOM

Policy 385-17, NAVSEAINST 8020.6E), and local, state, federal and international laws; and other requirements imposed by test ranges and Services. These evaluations include the following:

1) Review program system and sub-system safety analysis reports for completeness, technical accuracy and assessment of system safety risk. The systems under consideration may include: interceptors, targets, sensors, mobile launchers (land and sea-based), weaponized lasers, command, control and battle management, and fire control systems and battery support centers.

2) Review program system and sub-system Hazard Tracking Logs to verify that all credible safety hazards are accurately documented and risks identified.

3) Assist in developing and reviewing program Safety Assessment Reports.

4) Review program and MDS software safety requirements and analyses.

a) Participate in iterative (e.g. Agile) software development activities to ensure that critical software safety requirements are included in development.

5) Participate in development of verification activities and review verification evidence for safety specifications and requirements. Monitor software verification testing.

a) Verify safety critical software and hardware items have been tested per

Program requirements.

b) Document and report any safety variations/anomalies.

6) Review and assess safety impact of implementing Engineering Change Proposals

(ECPs), waivers, and deviations.

7) Review Operating and support hazard analysis.

8) Review Health Hazard Assessment.

9) Review Software System Safety Technical Review Panel (SSSTRP), Fuse and

Initiation System Technical Review Panel (FISTRP), Ignition System Safety Review

Board (ISSRB), and Weapon Systems Explosives Safety Review Board (WSESRB)

Technical Data Packages.

10) Review of other documents generated by the Program/Project office and the prime contractor relating to safety.

b. Program Reviews. The contractor shall support program reviews addressing development, operations and testing. Tasks associated with this activity include:

1) Attend and support design reviews and assess safety of proposed changes throughout the life-cycle of the Programs and Projects.

2) Attend and support design and test reviews, and execution meetings such as IPT meetings, working groups, change and failure review boards, peer reviews, Interface

Control Document (ICD) Working Groups, and technical interchange meetings (TIM) to identify and characterize risks.

3) Attend and support program milestone reviews including, but not limited to, System

Requirements Review (SRR), Preliminary Design Review (PDR), Critical Design

Review (CDR), Incremental Engineering Technical Review (IETR), Test requirements review (TRR), Pre Ship Readiness Review (PSRR), Test Readiness Review (TRR), Mission Readiness Review (MRR) and Flight Readiness Review (FRR).

20-MDA-10497 (29 May 20)

a. Assist in the development of briefings for these reviews when requested by the Program Office.

b. Review prime contractor draft safety presentations for these reviews.

4) Assist in the closure of safety-related action items assigned.

c. Safety Audit Support. The contractor shall support safety audits to confirm implementation of, and compliance with, MDA safety policies and requirements. This could include reviewing safety documentation for the audit, and developing safety checklists necessary for the audit based on the documentation review. Participate as safety representatives in QS Government led audits at the following locations, to include:

1) Government, Prime Contractor and Sub-contractor facilities.

2) Operational fielding or deployed sites.

3) Test Ranges.

The contractor shall perform safety audit follow-ups, track findings and verify closure within the guidelines identified in the MDA/QS Mission Assurance Audit Program Standard Operating

Procedure, QS-SOP-06.

d. System Safety Risk Assessments. The contractor shall participate in the development and review of system safety risk assessments and assist in obtaining approval from the appropriate authority IAW the MDA Assurance Provisions, SSSTRP, WSESRB, ISSRB, and the applicable

Service Risk Acceptance Authority. Tasks associated with this activity include:

1) Support the development of system safety risk assessments.

2) Prepare System Safety Risk Assessment Reports, risk acceptance memos and associated briefings IAW MDA Risk Acceptance Policy and/or designated User

Representative.

3) Perform aircraft safety review and analysis to ensure aircraft compliance with Federal

Aviation Administration type acceptance processes. The contractor shall provide technical management support regarding the developer prime contractor’s aircraft safety effort to produce aircraft airworthiness certificates.

4) Support development of ISSRB, SSSTRP and WSESRB Technical Data Packages.

5) Support development of Technical Data Packages for the applicable Service Risk

Acceptance Authority. Support development of Technical Data Packages for FMS cases.

e. System Safety Working Groups (SSWGs). The contractor shall support and attend SSWGs.

Support tasks for SSWGs include activities such as:

1) Arranging facilities and logistics for SSWGs, including audiovisual capabilities and communications.

2) Recording minutes and action items from the SSWGs, and publishing per the program

SSWG charter.

3) Developing briefing materials for assigned SSWG topics.

4) Tracking actions generated by the SSWG to verify closure IAW the program SSWG charter.

f. Hazard Tracking System (HTS). The contractor shall as assist with populating and updating the records system to document the identification, assessment mitigation, and verification of residual safety risks. The HTS currently consists of approximately 3,000 records which will be provided.

MDA data generated/exchanged using the web-based Hazard Tracking System (HTS) shall be delivered to the Government upon request of the contracting officer, but no later than the last date of the period of performance for this contract. The data shall be delivered on CD or DVD.

These CDs or DVDs are to be delivered to the Government with unlimited data rights IAW

DFARS 252.227-7013 and 252.227-7014. All copyrights for any updated and newly developed technical data and models are/will be assigned to the Government IAW DFARS 252.227- 7020.

g. Fielding and Operational Activities. The contractor shall provide support to fielding and operational activities including FMS cases. Tasks associated with this activity include:

1) Evaluate and comment on procedures and work orders throughout the program lifecycle (MIL-STD 882, MAP, MDA Instruction 6055.03 and tailored Range Safety requirements).

2) Witness hazardous operations and pathfinder activities to verify compliance with policies and procedures, and report safety anomalies and issues.

3) Verify operational configuration to published test or operational policies and procedures, and report variances that impact safety.

4) Verify execution of approved hazard mitigations identified in hazard logs, Safety

Assessment Reports and other program and contractor safety documentation including move safe plans.

5) Perform site surveys for deployment and/or testing, such as explosives siting per

DESR 6055.09, applicable Service specific explosives safety standards, and DoD

4145.26M (DoD Contractor’s Safety Manual for Ammunition and Explosives), pre-operational ordnance surveys, and Radio Frequency (RF) surveys (DoD 6055.11

Protecting Personnel from Electromagnetic Fields).

6) Verify requirements of NAVSEA OP-4 (Ammunition and Explosives Safety Afloat) or NAVSEA OP-5 (Ammunition and Explosives Safety Ashore) are used for guidance, applicable to Navy programs and operations conducted at Navy installations.

3.3.3 Support Safe Conduct of System Demonstration Activities, Including Flight and Ground

Tests at the Program/Project level.

a. Test Planning Support. The contractor shall provide test planning support and verification/validation for the following tasks. The tasks and subtasks include the following:

1) Evaluate mission specific safety risks:

a) Electromagnetic radiation hazard zones for personnel, ordnance, fuels, and equipment.

b) Launch and intercept debris exclusion zones.

c) Launch commit criteria.

d) Potentially hazardous interactions between test components or between test components and other MDS systems not participating in the test.

e) Work time restrictions (MDA Instruction 6055.04).

f) Determine if there are connections that would allow test data on to the real world operational (RWO) tactical system. If such connections are necessary for the test, assess proposed mitigations to determine the risk to RWO.

2) Assess test architecture for safety concerns.

a) Test article(s) include required safety features incorporated.

b) Potentially hazardous interactions between test components or between test components and other MDS systems not participating in the test.

3) Review test plans and procedures for safety concerns (MDA 6055.03-INS).

4) Support development of Insensitive Munitions (IM) and Final Hazard Classification

(FHC) detailed test plans.

a) Plans incorporate TB 700-2 and MIL-STD-2105/STANAG requirements.

b) Verify test article fidelity meets test plan requirements.

20-MDA-10497 (29 May 20)

5) Evaluate residual safety risk assessments for individual program level tests. Prepare appropriate level assessment documentation, as required by the evaluation.

b. Range and Test Safety Working Groups. The contractor shall support Range and Test

Safety Working Groups.

1) Participate in program safety working groups.

2) Record and publish meeting minutes and notes.

3) Record and track action items to closure.

c. Test Documentation. The contractor shall review specific test documentation to include the following tasks:

1) Review ground safety data packages to verify inclusion of safety risk and mitigation identification.

2) Review and assess BMDS Discrepancy Reports (BDRs) for potential safety risks and mitigation. Consider safety impact to sibling programs.

3) Review Range Safety Data Packages (RSDPs) to verify compliance to Range and

Program Safety requirements.

d. Integration and Test Support. The contractor shall provide on-site support for Integration and Test to include the following tasks:

1) Observe and witness assembly process to verify safety features are installed per procedure.

2) Participate in pre-test safety reviews and working groups such as TRRs, and FRRs.

a) Support development of briefing materials.

b) Track safety-related action items to closure.

3) Participate in Failure Reviews and/or Safety Investigations

a) Support development of briefing materials.

b) Track safety-related action items to closure.

4) Witness countdown tests.

a) Verify test conductors comply with countdown documentation/procedures.

5) Monitor software verification testing.

a) Verify safety critical software items have been tested per Program requirement.

6) Witness and verify test asset configuration.

a) Verify test assets are built to procedures and have incorporated required safety features.

e. Test Related Tasks. The contractor shall support the development, review and approval process for test-related tasks to include the following:

1) Range Safety waiver and/or deviation packages (verify safety-related requirements are incorporated).

2) Safety releases (coordinate with the Service to develop specific warfighter tasks for tests).

3) Range safety approvals.

4) Test specific Safety risks.

5) Orbital debris and collision avoidance (COLA).

6) Notice to Airmen/Notice to Mariners (NOTAM/NOTMAR) documentation development and dissemination.

7) Range safety surveillance plans.

8) Collection and analysis of data characterizing toxic components of Ground Based

Interceptor (GBI) launch plume during Ground Based Mid-course Defense Program

(GM) launches.

a) Set up test equipment for monitoring toxic data.

b) Document and report data with comparisons to previous toxic data.

c) Maintain calibration/certification of toxic monitoring equipment.

20-MDA-10497 (29 May 20)

f. Laser Safety Tasks in support of Directed Energy Programs and other program activities involving lasers. The contractor shall perform laser safety tasks typical of a Laser

Safety Officer as described in ANSI Z136.1 in support of directed energy and high energy laser

(HEL) programs to include the following:

1) Advise Government safety personnel in matters of Directed Energy Weapon

(DEW)/High Energy Laser (HEL)/general laser safety and policy.

2) Develop plans and procedures to implement laser safety programs in compliance with all applicable safety requirements, laws, policies, and regulations for all MDS laser systems.

3) Produce laser safety evaluation reports in accordance with ANSI Z136.1 including:

a) Laser Optical Hazard Reports for specific mission scenarios (targets and trajectories) for all categories of lasers.

1. Direct Ocular Hazard Analysis Reports and Memos.

2. Reflective Ocular Hazard Analysis Report and Memos.

3. Test Hazard Analysis (THA) Reports.

b) Determine Optical Density (OD) requirements of laser eyewear for participating and observing personnel including aided and non-aided viewing.

c) Prepare Laser Eye Protection (LEP) Recommendations, Reports and Memos.

d) Perform measurements and analyses to certify test ranges for all MDS laser testing.

1. Establish safe areas and Keep Out Zones

2. Prepare mission specific laser and optical evaluation analysis, reports and memos. This is documented through the Laser Safety Assessment.

3. Prepare a Laser Hazards Evaluation Report.

e) Produce Laser Incident Reports to aid hazard evaluations and support incident investigations for on range and off range environments, during testing or system integration for Category I-III LASERs and High Energy Lasers (HEL).

1. Recommend requirements for safe operations of laser systems at locations including ranges, industrial facilities and remote locations. This requires preparation of Laser Technical Papers.

20-MDA-10497 (29 May 20)

2. Conduct laser safety meetings to educate, and generate understanding with ranges, MDS laser system designers, manufacturers, operators, and maintainers to validate compliance with laser safety requirements and guidelines.

3. Observe, document, and make recommendations to validate compliance of programs, contractors, ranges and facilities with various laser safety programs and requirements which includes the Laser Safety

Audit & Report as well as the Evaluations of DVD Contractor Actions.

4. Assess and technically monitor contract efforts to maintain and upgrade various facilities used to support DVD, e.g., Edwards Air Force

Base, CA; Dryden Test Facility, CA; White Sands Missile Range

(WSMR), NM; Vandenberg Air Force Base (VAFB), CA; and Pacific

Missile Test Range, HI.

5. Prepare Food and Drug Administration laser product exemption letters as required for MDA tests and products.

3.4 Provide Support for Developing, Implementing and Executing an Effective MDA Safety and

Occupational Health (SOH) Program

The contractor shall provide technical and program management support for the QS directorate to execute the tasks listed below for each objective. The contractor will often be required to deliver verbal or written reports which are part of this task and maintain historical files after task execution. The specific requirement for reporting will be determined prior to execution of the tasks.

3.4.1 Support Development, Implementation and execution of safety and occupational health

(SOH) policies and procedures for programs across the Agency.

The contactor shall provide support for developing, implementing and executing effective MDA safety and occupational health (SOH) programs to include support for agency policies and procedures; and provide support for developing, implementing and executing an effective SOH program at the Program and Project level. The listed tasks are those which are typical in support of the MDA Safety Office.

Some of the tasks may be repeated often, and others may not be executed during this period of performance.

a. Implement MDA and DoD SOH Policy. The contractor shall support the development and implementation of SOH policy and program documentation for safety program, policy, requirements, analyses, reports, and plans to meet applicable DoD and MDA safety standards and local, state, federal, and international laws. The documents to be implemented include the following:

1) OSD Safety Policies.

2) MDA Director’s Safety Policy (MDA Memorandum 12).

3) DoD 6055 Series Standards and Directives.

20-MDA-10497 (29 May 20)

4) OSHA 29 CFR 1960, Basic Program Elements for Federal Employees OSHA.

5) MDA SOH Program Management Directive, MDA 6055.01, SOH Program

Management.

6) Accident Investigations and Reporting (MDA Instruction 6055.02-INS).

7) Work Time Restrictions for Safety and/or Mission Critical Personnel

Supporting Tests and Critical Operations (MDA Instruction 6055.04-INS).

8) MDA Assurance Provisions (MAP, MDA-QS-001-MAP, Rev. C).

9) Program Unique Safety Documentation Management Plans/Policies.

b. SOH Record. The contractor shall maintain SOH Records. The contractor shall archive all

Program and Project safety records, to include the following:

1) Comply with MDA Records Management Policy (MDA Directive 8180.01).

2) Comply with OSHA 29 CFR 1904, Recordkeeping.

3) Maintain Accident and Hazards Database.

c. Safety Audit Support. The contractor shall support Safety Audits to verify implementation of, and compliance with, MDA safety policies at the following locations, to include:

1) Prime contractor and sub-contractor facilities and operations.

2) Operational fielding or deployed areas.

3) Test ranges.

The contractor shall perform safety audit follow-ups, track findings and verify closure within the guidelines identified in the QS Mission Assurance Audit Program Standard Operating

Procedure, QS-SOP-06. The contractor shall provide written report of SOH findings and assist in developing the final audit report.

d. SOH Inspections. The contractor shall conduct SOH Inspections of MDA owned or leased facilities to verify compliance with federal regulatory agency directives and provide written reports. Directives include the following:

1) OSHA; 29 CFR 1910, General Industry, 29 CFR 1926, Construction, and 29 CFR

1904, Recordkeeping.

2) National Fire Codes (NFPA).

3) American National Standards Institute (ANSI).

4) Environmental Protection Agency (EPA).

5) OSHA 29 CFR 1915, Occupational Safety and Health Standards for Shipyard

Employment.

20-MDA-10497 (29 May 20)

6) OSHA 29 CFR 1917, Marine Terminals.

7) Service and MDA core standards.

e. Consolidated Missile Activities. The contractor shall provide support to the assembly, storage, transportation and testing of consolidated missile activities. Tasks associated with this activity include:

1) Supporting quarterly safety stand down days, which includes participating in discussions and presenting briefings when required.

2) Supporting consolidated missile safety council meetings and training. Prepare agenda and minutes.

3) Coordinating ordnance moves with Airport Authority and developing associated documentation.

f. Hazard Identification, Abatement, and Analysis. The contractor shall support hazard identification and reporting initiatives, hazard abatement, and hazard analysis.

g. Support Mishap Investigations. The contractor shall support accident investigation, reporting and trend analysis where incidents involve MDA federal civilian employees, military personnel assigned to MDA, MDA contractors, or incidents involving MDA owned or leased facilities and or MDA operations (MDA 6055.02-INS). The contractor will maintain liaison with local workers compensation program administrators. The contractor will provide written reports IAW

DODI 6055.07. (Support to mishap investigations will be limited to no more than 2 weeks without a contract modification to account for the extended timeframe of the activity).

h. Safety and Occupational Health Training. The contractor shall assist the Government Safety

Office to develop and conduct SOH training to include:

1) OSHA General Industry Standards.

2) New hire Safety Orientation.

3) Collateral Duty Safety Representative (CDSR).

4) Supervisor’s Safety Training.

i. Construction Safety. The contractor shall at the direction of the government provide technical support to the monitoring of construction sites, attend and participate in pre-construction and final acceptance conferences, and building modification and change reviews.