DRAFT_BAT_Statement_of_Work dated_21_Jan_16 _Rev_5.pdf

DRAFT BAT Statement of Work (SOW), 01/21/16, Rev 5

DRAFT Bomber Armament Tester (BAT)

Statement of Work (SOW)

01/21/16, Rev 5

Prepared by

AFLCMC/WNA

AUTOMATIC TEST SYSTEMS DIVISION

460 RICHARD RAY BLVD STE 200

ROBINS AFB GA 31098

DISTRIBUTION STATEMENT A. Approved for public release: Distribution is unlimited. (78 ABW/PA Certificate Number 15-04268).

Table of Contents

1.0 SCOPE

1.1 PROGRAM SYNOPSIS

1.2 OVERVIEW OF BAT PROGRAM

1.2.1 Increment 1 (B-2A)

1.2.2 Increment 2 (B-1B)

1.2.3 Increment 3 (B-52H)

1.2.4 Government Data Rights

2.0 APPLICABLE DOCUMENTS

3.0 GENERAL REQUIREMENTS

3.1 PROGRAM CONFERENCES

3.1.1 Post-Award Conference (PAC)

3.1.2 Engineering Data Guidance Conference

3.1.3 Technical Order (T.O.) Guidance Conference

3.1.4 Provisioning Guidance Conference

3.2 GENERAL TECHNICAL REQUIREMENTS

3.2.1 General Design Requirements

3.2.2 Technical Approach

3.2.3 TPS General Design Requirements

3.2.4 BAT System Software Requirements

3.2.4.1 Software Requirements Specification (SRS)

3.2.4.2 Software Product Specification (SPS)

3.2.4.3 Software Version Description (SVD)

3.2.4.4 Computer Software Product – Software Delivery

3.2.4.5 Automated Computer Program Identification Number System (ACPINS) Data and Control Record

3.3 NUCLEAR CERTIFICATION

3.3.1 Nuclear Certification Impact Statement (NCIS)

3.3.2 Certification Requirements Plan (CRP)

3.3.3 Nuclear Safety Analysis Report (NSAR)

3.4 RELIABILITY

3.5 PROGRAM PROTECTION

3.5.1 Program Protection Implementation Plan (PPIP)

3.5.2 Inspection and Audit

3.5.3 Cybersecurity

3.5.3.1 Cybersecurity Controls

3.5.3.2 System Security Plan (SSP)

3.5.3.3 Cybersecurity Risk Management

3.5.3.4 System Level Plan of Action and Milestones (POA&M)

3.5.3.5 Cyber-Secure Development Environment

3.5.4 Anti-Tamper

3.5.5 Counterfeit Prevention Plan (CPP)

3.6 SAFETY

3.6.1 Hazard Analysis and Risk Mitigation

3.6.2 Environmental, Safety, and Occupational Health (ESOH)

3.7 TECHNICAL REVIEWS

3.8 PROGRAM MANAGEMENT ACTIVITIES

3.8.1 Program Manager (PM)

3.8.2 Earned Value Management (EVM)

3.8.2.1 Integrated Program Management Reporting

3.8.2.2 Integrated Master Schedule (IMS)

3.8.3 Program Reviews and Conferences

3.8.3.1 Support of Reviews and Meetings

3.8.3.2 Meetings (Conferences)

3.8.3.3 Technical Interchange Meetings (TIM)

3.9 LOGISTICS

3.9.1 Test Assets and Government-Furnished Equipment (GFE)

3.9.2 Technical Orders (T.O.s)

3.9.2.1 Development

3.9.2.1.1 Technical Order Library

3.9.2.2 Validation/Certification

3.9.2.3 Verification

3.9.3 Engineering Data

3.9.3.1 In-Process Review (IPR) of the TDP

3.9.3.2 Relationship of Contractor with Subcontractors/Vendors

3.9.3.3 Engineering Data Updates and Revisions

3.9.3.4 Data Accession List (DAL)

3.9.4 Familiarization

3.9.5 Provisioning

3.9.5.1 Request for Nomenclature (RFN)

3.9.6 Configuration Management (CM) and Control

3.9.6.1 Configuration Requirements

3.9.6.2 Configuration Items (CIs)

3.9.6.3 Engineering Change Proposal (ECP) / Notice of Revision (NOR) / Contract

Change Proposals (CCP)

3.9.6.4 Authorization

3.9.6.5 Signature Authorization

3.9.6.6 Engineering Change Proposal Costs

3.9.6.7 Request for Variance (RFV)

3.9.6.8 Item Unique Identification (IUID)

3.9.6.8.1 Marking

3.9.6.8.2 IUID Marking Plan

3.9.6.8.3 IUID Marking Activity and Verification Report

3.9.7 Diminishing Manufacturing Sources and Material Shortages (DMSMS)

3.9.8 Parts Control and Standardization Program

3.10 SECURITY

3.10.1 Security Information

3.10.2 Contractor Facilities

3.10.3 Communications Security (COMSEC)

4.0 INCREMENT 1 (B-2A)

4.1 EMD

4.1.1 BAT System Requirements Review (SRR)

4.1.2 BAT System Functional Review (SFR)

4.1.3 BAT Preliminary Design Review (PDR)

4.1.4 BAT System CDR

4.1.5 BAT System Verification Review (SVR)

4.1.5.1 Develop/Build Production Representative (Core Tester) Articles

4.1.5.1.1 BAT Calibration and Measurement Requirements Summary (CMRS)

4.1.5.2 Testing of the BAT Core Tester

4.1.5.2.1 Environmental Testing

4.1.5.2.2 Reliability Testing

4.1.5.2.3 Cybersecurity Testing

4.1.5.2.4 BAT Core Tester for Red Team Analysis

4.1.5.3 Develop/Build Production Representative Article TPSs

4.1.5.3.1 UUT Test Requirements Documents (TRDs)

4.1.5.4 Environmental Testing for UUT TPS Hardware

4.1.5.5 Reliability Testing For B-2A UUT TPSs

4.1.5.6 Test Readiness Review (TRR)

4.1.5.6.1 TPS Fault Detection/Fault Isolation (FD/FI)

4.1.5.7 Integrated TPS Configuration Item (CI) Developmental Testing & Evaluation

(DT&E)

4.1.5.7.1 TPS FIAT

4.1.5.8 Integrated System DT&E

4.1.6 Operational Test Readiness Review (OTRR)

4.1.7 Operational Test and Evaluation (OT&E)

4.1.8 PCA

4.1.9 BAT Core Tester Test Requirements Documents

4.1.10 Production Readiness Review (PRR)

4.2 PRODUCTION

4.2.1 BAT Core Tester Production for B-2A

4.2.2 BAT Core Tester Production Acceptance Procedures and Reports

4.2.3 B-2A TPS Production

4.2.4 Warranty

5.0 INCREMENT 2 (B-1B)

5.1 EMD

5.1.1 PDR

5.1.2 CDR

5.1.3 SVR

5.1.3.1 Develop / Build Production Representative Article UUT TPSs

5.1.3.1.2 UUT Test Requirements Documents (TRDs)

5.1.3.2 Environmental Testing For UUT TPS Hardware

5.1.3.3 Reliability Testing For B-1B UUT TPSs

5.1.3.4 Cybersecurity Testing For B-1B TPSs

5.1.3.5 Test Readiness Review (TRR)

5.1.3.6 TPS Fault Detection/Fault Isolation (FD/FI)

5.1.3.7 Integrated TPS Configuration Item (CI) and Integrated System Developmental

Testing & Evaluation (DT&E)

5.1.3.7.1 TPS FIAT/Integrated System DT&E

5.1.4 Operational Test Readiness Review (OTRR)

5.1.4.1 Operational Test and Evaluation (OT&E) Support

5.1.5 Production Readiness Review (PRR)

5.2 PRODUCTION

5.2.1 BAT Core Tester Production for B-1B

5.2.2 BAT Core Tester Production Acceptance Procedures and Reports

5.2.3 B-1B TPS Production

5.2.4 Warranty

6.0 INCREMENT 3 (B-52H)

6.1 EMD

6.1.1 PDR

6.1.2 CDR

6.1.3 SVR

6.1.3.1 Develop/Build Production Representative Article UUT TPSs

6.1.3.1.2 UUT Test Requirements Documents (TRDs)

6.1.3.2 Environmental Testing For UUT TPS Hardware

6.1.3.3 Reliability Testing For B-52H UUT TPSs

6.1.3.4 Cybersecurity Testing For B-52H TPSs

6.1.3.5 Test Readiness Review (TRR)

6.1.3.6 TPS Fault Detection/Fault Isolation (FD/FI)

6.1.3.7 Integrated TPS Configuration Item (CI) and Integrated System Developmental

Testing & Evaluation (DT&E)

6.1.3.7.1 TPS FIAT/Integrated System DT&E

6.1.4 Operational Test Readiness Review (OTRR)

6.1.4.1 Operational Test and Evaluation (OT&E) Support

6.1.5 Production Readiness Review (PRR)

6.2 PRODUCTION

6.2.1 BAT Core Tester Production for B-52H

6.2.2 BAT Core Tester Production Acceptance Procedures and Reports

6.2.3 B-52H TPS Production

6.2.4 Warranty

7.0 ICS MANAGEMENT

7.1 INTERIM CONTRACTOR SUPPORT (ICS)

8.0 OVER AND ABOVE

8.1 OVER AND ABOVE (O&A)

APPENDIX A: UUT LISTS

Table A-1: B-2A Armament System Units Under Tests Table A-2: B-1B Armament System Units Under Tests Table A-3: B-52H Armament System Units Under Tests

APPENDIX B: APPLICABLE DOCUMENTS

B.1 GOVERNMENT DOCUMENTS

B.1.1 Specifications, standards, and handbooks B.1.1.1 Military Standards B.1.1.2 Military Handbooks B.1.2 Other Government documents, drawings, and publications

B.2 OTHER DOCUMENTS

APPENDIX C: CDRL CROSS REFERENCE

APPENDIX D: USER LOCATIONS

1.0 SCOPE

1.1 Program Synopsis

This Statement of Work (SOW) defines the tasks and deliverables for the procurement and sustainment of the BAT and associated UUT TPSs, as described by the BAT System Performance Specification and all program required data as documented and defined in support of this acquisition.

The purpose of the Bomber Armament Tester (BAT) program is to design, develop, integrate, test, manufacture, and sustain a common tester for armament systems on the B-2A, B-1B, and B- 52H platforms, capable of testing on-aircraft Stores Management Systems, and capable of testing Line Replaceable Units (LRUs) both on-and off-aircraft. The BAT core tester shall be common to all three platforms, while Test Program Sets (TPSs) shall be platform-specific. A list of the applicable aircraft-specific tests is provided in Section 3.4 (and sub-paragraphs) of the BAT System Performance Specification. A list of the applicable B-2A, B-1B, and B-52H Units Under Test (UUTs) is provided in Appendix A: UUT Lists.

The “BAT system” is hereby defined as: consisting of the core tester and supporting UUT TPSs required to support respective B-2A, B-1B, or B-52H weapon systems. The “Core Tester” includes hardware, operating system software, firmware, test executive software, power-on confidence test TPS, user-selectable self-test TPS, and a calibration TPS. A UUT TPS includes all cables, Interface Test Adapters (ITA), software, and technical documentation needed to test a

UUT.

1.2 Overview of BAT Program

The BAT Program follows an incremental approach. Each increment includes Engineering and Manufacturing Development (EMD), followed by Production and Interim Contract Support (ICS). Three increments are planned; with Increment 1 for B-2A, Increment 2 for B-1B, and Increment 3 for B-52H.

1.2.1 Increment 1 (B-2A)

Increment 1 shall include an initial EMD acquisition effort for requirements analysis, design, development, integration, and test of production representative articles of the BAT Core Tester (common to all platforms), B-2A TPSs, the SUU-67 Pylon Wing Disconnects TPS for B-52H, and the Multi-Purpose Rotary Launcher (MPRL) TPS for B-1B. EMD is followed by production of BAT testers and TPSs to support the B-2A mission, and ICS to provide sustainment. The initial Required Assets Available (RAA) quantity of production deliverables for B-2A Increment 1 shall be fielded not later than 25 September, 2020.

1.2.2 Increment 2 (B-1B)

Increment 2 EMD covers TPS design, development, integration, and test for the remaining B-1B TPSs, beyond the MPRL TPS described in Paragraph 1.2.1. Increment 2 EMD is followed by production of BAT testers and TPSs to support the B-1B mission, and ICS to provide sustainment. All production deliverables for B-1B Increment 2 shall be fielded not later than 25 September 2022.

1.2.3 Increment 3 (B-52H)

Increment 3 covers TPS design, development, integration, and test for the remaining B-52H TPSs, beyond the SUU-67 Pylon Wing Disconnects TPS described in Pparagraph 1.2.1.

Increment 3 EMD is followed by production of BAT testers and TPSs to support the B-52H mission, and ICS to provide sustainment. All production deliverables for B-52H Increment 3 shall be fielded not later than 25 September 2025.

1.2.4 Government Data Rights

All hardware, software, firmware, software development environments, and technical data items delivered under this contract shall be delivered with Government Purpose Rights, at a minimum, so that the BAT System can be maintained, sustained, modified, re-used, or re-procured by 3rd parties of the Governments’ choosing after this contract is concluded. This includes the rights to use, modify, reproduce, release, perform, display, or disclose technical data within the Government without restriction and to release or disclose technical data outside the Government and authorize persons to whom release or disclosure has been made to use, modify, reproduce, release, perform, display, or disclose that data for United States Government purposes.

All software executables and source code developed by the contractor for the BAT System shall be property of the Government for unlimited use. This includes BAT Core Tester software, TPS, and qualification software. BAT Core Tester software is defined as the operating system software, firmware, power-on confidence test software, self-test software, calibration software (if calibration required), test executive software, system recovery and/or security software required to meet cybersecurity requirements. The deliverables shall be addressed by Contract Data Requirements Lists (CDRL).

Freeware shall not be used in the design, development, or production of the BAT System, and shall not be incorporated into any of the software deliverables of the BAT System. Freeware is defined as free software which is copyrighted by its developer, who retains the rights to control its distribution, modify it and sell it in the future.

For any and all commercial software used on the BAT System that requires a license, the license “key” shall not be hardware based (i.e. USB-based dongle key). The ability to utilize any and all commercial software shall not require any additional hardware to verify possession of appropriate and corresponding license(s), nor require any recurring license fees for continued use of and reinstallation of the existing software configuration. All licenses shall be “royalty-free,” worldwide, irrevocable and non-exclusive.

2.0 APPLICABLE DOCUMENTS

See Appendix B.

3.0 GENERAL REQUIREMENTS

3.1 Program Conferences

3.1.1 Post-Award Conference (PAC)

The Contractor shall attend a PAC that shall be conducted no later than 45 days after contract award. The conference shall be held at Robins AFB, GA or at the Contractor’s facility, at the discretion of the Government Contracting Officer. The Government Contracting Officer will conduct this meeting to review in detail all terms and conditions of the contract with the Contractor’s program team. Any technical issues that may need to be discussed can be highlighted at this event; however, such issues shall be expressly discussed in the Guidance Conferences governing Engineering and Technical Data, Technical Orders, and Provisioning, as defined further within this SOW.

(A001, DI-ADMN-81249A, Conference Agenda) (A002, DI-ADMN-81250A, Conference Minutes)

3.1.2 Engineering Data Guidance Conference

The Contractor shall support and co-chair a Guidance Conference with AFLCMC/LZPEM, the Engineering Data Management Office, for engineering data no later than 45 days after contract award to be held at Robins AFB, GA. The Conference shall be convened on a date agreed upon by the Government and the Contractor. The Contractor shall prepare an agenda and record the minutes of the Guidance Conference. The Contractor shall address, discuss, and provide status on the following:

a) Understanding of all CDRL requirements, applicable Data Item Descriptions (DIDs), specifications and standards.

b) Technical Data Package (TDP) review requirements and schedules.

c) TDP delivery requirements and schedules.

d) The Contractor's drafting practices, procedures, and TDP drawing formats.

e) The Contractor's quality assurance procedures relating to TDP documents, including quality control of subcontractor and vendor data.

f) The role of subcontractors and vendors who may deliver TDP documents under this contract.

g) The Contractor's configuration management system, including methods for releasing documents, approving documents, and incorporating changes into documents.

h) Digital TDP deliverables.

3.1.3 Technical Order (T.O.) Guidance Conference

In accordance with TM-86-01N requirements, the Contractor shall co-chair a T.O. Guidance Conference that shall be conducted no later than 45 days after contract award. The conference shall be held at Robins AFB, GA. The conference shall be convened on a date agreed upon by the Government and the Contractor. The Contractor shall prepare an agenda and record the minutes of the Guidance Conference.

3.1.4 Provisioning Guidance Conference

The Contractor shall participate in a Provisioning Guidance Conference, initiated by the Government, which shall be conducted no later than 45 days of contract award.

3.2 General Technical Requirements

3.2.1 General Design Requirements

The BAT System shall meet the requirements of the BAT System Performance Specification, the System/Subsystem Specification developed by the Contractor and approved by the Government, the UUT Test Requirements Analysis Report, and this SOW.

The Contractor shall develop a System Engineering Management Plan (SEMP) that contains the Contractor's approach to implementing this SOW’s provisions. The SEMP is the top-level technical document governing the implementation of basic system engineering activities.

Directives in this plan relate to the engineering management of all program activity.

(B002, DI-SESS-81785, System Engineering Management Plan (SEMP))

3.2.2 Technical Approach

The Modular Open System Architecture approach described in the BAT System Performance Specification shall be utilized.

3.2.3 TPS General Design Requirements

Each TPS shall be independent and completely documented for stand-alone operation. The Contractor may recommend for a TPS to cover more than one UUT, subject to approval by the Government.

ITAs shall be designed to be "passive" to the maximum extent practicable, in accordance with the BAT System Performance Specification. Government approval is required for the development of electronically active ITAs. Any active ITA candidates shall be identified by the Contractor for approval no later than Preliminary Design Review (PDR), and Government approval shall be established prior to Critical Design Review (CDR).

To ensure standardization of all TPSs that will be executed on the BAT, the contractor shall develop and utilize a TPS Style Guide for TPS Development. The TPS Style Guide shall be delivered under this contract and shall not be proprietary.

(B00K, DI-IPSC-81633/T, Software Programmer’s Manual (Test Program Set Style Guide and

Application Program Interface))

3.2.4 BAT System Software Requirements

The BAT System software components include operating system software, firmware, power-on confidence test software, self-test software, calibration software, test executive software, and TPS software. The operating system software includes any system recovery and/or security software required to meet cybersecurity requirements. TPS software, delivered separately, is not part of the BAT Core Tester configuration but is run on the BAT by field users to test UUTs.

The Contractor shall utilize their overall Systems Engineering process to design, develop, and test the BAT System software. All BAT System software, including each UUT TPS software package, shall be managed as separate Computer Software Configuration Items (CSCIs). Each CSCI and related documentation shall be identified with a Computer Program Identification Number (CPIN) that is distinct and separate from any other BAT software component.

Firmware is considered software and shall be treated accordingly. The Contractor shall document via a Firmware Support Manual, any and all firmware that is used as a part of BAT.

This applies to read only memories (ROMs), Programmable ROMs (PROMs), Erasable PROMs (EPROMs), and any other firmware devices (i.e. Electrically-Erasable Programmable Read-Only Memories (EEPROMs), Field-Programmable Gate Arrays (FPGAs), etc.). The Contractor shall provide software and firmware source code on all Contractor-developed and subcontractor-developed software and firmware for the BAT System.

(B00H, DI-IPSC-81448B, Firmware Support Manual)

3.2.4.1 Software Requirements Specification (SRS)

The Contractor shall develop and deliver a SRS for each component (CSCI) of the BAT System software.

(B00G, DI-IPSC-81433A, Software Requirements Specification (SRS))

3.2.4.2 Software Product Specification (SPS)

The Contractor shall provide a SPS for each component (CSCI) of the BAT System software. In addition to the requirements detailed in DI-IPSC-81441A, the Contractor shall provide and demonstrate the steps necessary to rebuild the software for operational use in a BAT system that has no software installed.

(B00E, DI-IPSC-81441A, Software Product Specification)

3.2.4.3 Software Version Description (SVD)

The Contractor shall deliver SVD documentation for each component (CSCI) of the BAT System software. The SVD shall include complete installation and checklists for all software used in, on, or in support of the BAT System or UUT TPSs. The Contractor shall ensure that all software installed is identified and the installation instructions and procedures are documented fully and completely. The SVD shall also include the Software Installation Procedures, Drive Imaging Procedures and the Drive Imaging Restoration Procedures.

(B00F, DI-IPSC-81442A, Software Version Description)

3.2.4.4 Computer Software Product – Software Delivery

The Contractor shall develop and deliver CD-ROM media containing software executable files and source code files for all BAT tester software and UUT TPS software in accordance with the listed CDRL. Data rights shall be in accordance with Paragraph 1.2.4.

(B00J, DI-IPSC-81488, Computer Software Product)

3.2.4.5 Automated Computer Program Identification Number System (ACPINS) Data and Control Record The Contractor shall submit a request for CPIN assignment for each BAT software CSCI and each TPS CSCI, and any other software configuration entity to be delivered to the Government to support the BAT testing of the UUTs in Appendix A. CPIN assignment requests shall be accomplished by direct on-line data entry into ACPINS. The CPIN media label information shall match the information in ACPINS. Access to ACPINS is detailed in Technical Order 00-5- 16, Software Managers and Users’ Manual for the USAF Automated Computer Program Identification Number System (ACPINS).

(C004, DI-MISC-81454C, Automated Computer Program Identification Number Data and Control Record)

3.3 Nuclear Certification

Nuclear certification for the BAT Core Tester and applicable TPSs shall be in accordance with AFI 63-125, Nuclear Certification Program.

3.3.1 Nuclear Certification Impact Statement (NCIS)

The Contractor shall develop and deliver a detailed Nuclear Certification Impact Statement (NCIS), in accordance with DI-NUOR-81888A. The Detailed NCIS shall be delivered 45 days prior to CDR for nuclear certified TPSs and BAT Core. The core tester hardware design should be stabilized to prevent resubmittal of the NCIS due to significant architectural or component changes. Updates to the detailed NCIS shall be developed and delivered as required and requested by the Government in order to develop a Basic Certification Requirements Plan (CRP).

After CDR when the Government-approved design baseline has been established, an NCIS shall also be generated for all Class I, Class II and deviation proposals to the approved baseline unless waived by the Government.

(B012, DI-NUOR-81888A, Nuclear Certification Impact Statement (NCIS))

3.3.2 Certification Requirements Plan (CRP)

An initial Certified Requirements Plan will be provided by the Air Force Nuclear Weapons Center (AFNWC). The Contractor shall develop and deliver a detailed CRP, in accordance with

DI-NUOR-81409A.

(B011, DI-NUOR-81409A, Certification Requirements Plan (CRP))

3.3.3 Nuclear Safety Analysis Report (NSAR)

The Contractor shall develop and deliver an NSAR for review and approval by the Government.

The NSAR shall document how the BAT System meets the nuclear safety design certification requirements for test equipment mandated in AFI 91-107, Design, Evaluation, Troubleshooting, and Maintenance Criteria for Nuclear Weapon Systems, AFMAN 91-118, Safety Design and Evaluation Criteria for Nuclear Weapon Systems, and AFMAN 91-119, Safety Design and Evaluation Criteria for Nuclear Weapon Systems Software.

(B010, DI-NUOR-81405B/T, Nuclear Safety Analysis Report)

3.4 Reliability

The Contractor shall develop a reliability strategy and program plan which describes and discusses how the Contractor satisfies the reliability requirements of the BAT System Performance Specification and SOW; specifically how the Contractor will achieve the 1500 hour Mean Time Between Failure (MTBF) requirement prior to Test Readiness Review (TRR). The reliability program shall be an integral part of the systems engineering process and shall address:

a) Defining the reliability strategy and program, system-wide design decisions affecting reliability, reliability growth planning and tracking with growth curves, Built-In-Test (BIT) verification, and compliance with MIL-HDBK-189C.

b) Failure Modes Effects and Criticality Analysis (FMECA) .

c) Failure Reporting and Corrective Action System (FRACAS).

d) Reliability verification to meet the MTBF schedule requirement prior to TRR.

e) Design verification testing of safety critical failure modes.

f) Utilizing reliability prediction and modeling during planning, design and development to assess the design and identify risk.

(B009, DI-SESS-81613A, Reliability and Maintainability Program Plan) (B008, DI-SESS-81497A, Reliability and Maintainability Predictions Report)

(B00P, DI-TMSS-81586A, Reliability Test Report)

3.5 Program Protection

Program protection for the BAT System is required by Air Force Pamphlet 63-113, Program Protection Planning for Lifecycle Management; DoD Instruction 5200.39, Change 1, Critical Program Information (CPI) Protection Within the Department of Defense; and DoD Instruction 5200.44, Protection of Mission Critical Functions to Achieve Trusted Systems and Networks.

3.5.1 Program Protection Implementation Plan (PPIP)

After contract award, the Contractor shall be provided a Government-developed Program Protection Plan (PPP) in draft version. Contained therein shall be all known and defined CPI elements of the program. As the Contractor develops the BAT System design, identification of additional CPI not previously identified shall be added to the PPP by the Contractor. The Contractor shall develop a Program Protection Implementation Plan (PPIP) which shall outline and define the Contractor’s implementation of the Government-developed PPP. The PPIP shall provide identification of Program Protection points of contact, identification of Program Protection schedule events, identification of measures being taken to protect CPI and identification of unique Program Protection costs.

Within the PPIP, the Contractor shall also address the following software assurance measures:

a) How software shall be designed and tested to assure protection of critical functionality.

b) How software architectures, environments, designs, and code shall be evaluated with respect to CVE (Common Vulnerabilities and Exposures), CAPEC (Common Attack Pattern Enumeration and Classification), and CWE (Common Weakness Enumeration).

c) How Commercial Off-the-Shelf (COTS) software and software of unknown pedigree (i.e., software from sources buried in the supply chain) shall be protected and tested/vetted.

d) How the critical functions shall be protected in the operational system.

The Contractor shall support the Government in the development of the Anti-Tamper (AT) Annex of the PPP. The Contractor shall develop an AT Annex to the PPIP, following the PPP Anti-Tamper Plan Annex Template.

(B001, DI-ADMN-81306, Program Protection Implementation Plan (PPIP))

3.5.2 Inspection and Audit

The Contractor shall support Government-led reviews and assessments of Cybersecurity and Program Protection areas of concern in all Contractor and subcontractor facilities as needed to ensure compliance with published requirements and protection measures. The Contractor shall report to the Government Program Manager and Government Contracting Officer all incidents of computer malware or viruses IAW T.O. 33-1-38.

3.5.3 Cybersecurity

The Contractor shall implement cybersecurity for the BAT System in accordance with DoDI

8500.01 and DoDI 8510.01. Within DoDI 8510.01, Cybersecurity is defined as the “Prevention of damage to, protection of, and restoration of computers, electronic communications systems, electronic communications services, wire communication, and electronic communication, including information contained therein, to ensure its availability, integrity, authentication, confidentiality, and nonrepudiation.”

The Contractor shall identify, manage, and verify adherence to cybersecurity requirements in the same manner as all other system requirements. The Contractor shall identify the requirements that are security critical, and identify and establish corresponding process controls for these requirements. The Contractor shall ensure and document bi-directional traceability between security controls and requirements.

All BAT System software, TPSs, and firmware created, delivered, and installed shall utilize non-repudiation techniques to guarantee the integrity and origin of the system software, TPSs and firmware throughout the entire system software, TPSs and firmware lifecycle.

The Contractor shall prepare a system level architecture report describing the Platform Information Tecthnology (PIT) boundary, interconnections and data transfers in accordance with the Architecture Analysis Report Template.

(B016, DI-MISC-80508B/T, Technical Report Study/Services (Architecture Analysis Report))

3.5.3.1 Cybersecurity Controls

The Contractor shall identify and implement the applicable cybersecurity controls from Committee on National Security Systems Instruction (CNSSI) No. 1253 for the BAT System.

The implemented controls shall be documented and submitted in a technical report due as a draft at the System Requirements Review (SRR), with an updated version due at the PDR, and final version due at the CDR, with updates to the final as required.

(B014, DI-MISC-80508B/T, Technical Report Study/Services (Cybersecurity Controls Report))

3.5.3.2 System Security Plan (SSP)

The Contractor shall develop, deliver and update a SSP for review by the Government in accordance with the DD1423 CDRL item.

(B013, DI-MISC-80508B/T, Technical Report Study/Services (System Security Plan))

3.5.3.3 Cybersecurity Risk Management

The Contractor shall ensure that cybersecurity risks are identified and managed as a performance risk, as well as part of the overall program risk management process (consisting of cost/schedule/ performance risks). The status of cybersecurity risk management activities for the BAT program shall be reported each month in the Integrated Program Management Report (IPMR - reference Paragraph 3.8.2.1). The Contractor shall ensure that the cybersecurity risk management activity reexamines threats, exposure, and vulnerabilities, and assesses changes to all system architecture and design changes. The Contractor shall, as appropriate, recommend changes to cybersecurity controls for the system as part of all System Engineering Technical Reviews.

The Contractor shall integrate Testing and Evaluation (T&E) of cybersecurity requirements into the overall T&E process, to include component-level testing performed by suppliers. Testing shall be integrated throughout the development and test of the BAT System. The Contractor shall support the Government in obtaining the necessary Interim Authorizations to Test (IATTs) and Authority To Operate (ATOs) for all T&E.

The Contractor shall include cybersecurity risk management framework activities and events on the Integrated Master Schedule.

The Contractor shall ensure that familiarization materials, technical manuals, and other technical data developed for the program address any cybersecurity controls (e.g., administrative, procedural, inherited) or requirements that affect system operation, maintenance, repair, or other support activities.

The Contractor shall conduct analysis for any COTS and/or non-developmental items to ensure that they are appropriately configured, software/hardware/firmware is controlled, and any unique risks they pose are mitigated.

3.5.3.4 System Level Plan of Action and Milestones (POA&M)

The Contractor shall develop and maintain a milestone-based management plan to address all non-compliant cybersecurity requirements and vulnerabilities identified during the security control assessment.

(B017, DI-MISC-80508B/T, Technical Report-Study/Services (POA&M))

3.5.3.5 Cyber-Secure Development Environment

The Contractor shall maintain a cyber-secure development environment that reduces and manages risk by implementing, at minimum, the following select controls from CNSSI 1253 as defined in NIST SP 800-53r4: SA-10, SA-15, and AT-2.

3.5.4 Anti-Tamper

The Contractor shall develop and implement Anti-Tamper (AT) hardware and software protection measures to protect (by deterring, preventing, detecting, and/or reacting to anti-tamper attacks) the Government-approved Critical Technology (CT) subset of CPI per the AT Guidelines Version 2.1, 25 July 2014.

The Contractor shall integrate AT activities into the overall systems engineering process across the program's lifecycle, to include science and technology efforts, research, design, development, implementation, testing, operations, maintenance, upgrade, and disposal of the system. The Contractor shall include AT within the systems security planning, systems engineering, requirements, design, test and maintenance CDRL items.

The Contractor shall provide a mapping of each CPI/CT to the Contractor Work Breakdown Structure (CWBS). The Contractor shall conduct a risk assessment and establish a probability of occurrence and impact (i.e. severity of consequence) for each CPI/CT. The Contractor shall identify and document (in the AT Annex to the Program Protection Plan) the AT risk level (by completing the exposure and criticality analysis) and corresponding AT technique for each CT.

The Contractor shall employ AT techniques commensurate with the AT level. The Contractor shall employ an integrated multi-layer AT approach (i.e. apply at the chip, board, and system levels).

The AT approach shall combine various techniques (e.g. deter, prevent, detect, react) to defeat sequential attacks. The approach shall take into consideration the impacts of CT during functional decomposition to minimize those portions of the system that require AT protection, as well as considering the impacts of AT on functionality and maintenance.

The Contractor shall, for incremental development, ensure that upgrades to hardware or software include AT techniques equivalent to the protected measures originally employed.

The Contractor shall implement AT measures that prevent unauthorized access to critical software functionality regardless of the system mode (i.e. at rest, in transit, in use).

The Contractor shall ensure that the AT techniques, singly or in aggregate, prior to a tamper event, do not degrade system or mission performance.

The Contractor shall include incremental testing of AT technology within the overall system integration, test & evaluation planning. The Contractor shall provide the Government’s AT Verification and Validation Team the support necessary for them to evaluate the AT design and ensure that AT is installed and performs as expected. The team will be verifying and validating the system against the system and lower level (i.e., sub-system, configuration item) requirements as well as derived AT requirements.

The Contractor shall support the Government in the development of the AT Annex of the PPP.

The Contractor shall develop an AT Annex to the PPIP, following the PPP AT Annex Template.

3.5.5 Counterfeit Prevention Plan (CPP)

In accordance with DoD Instruction 5200.44, the Contractor shall establish policies and procedures to avoid, detect, mitigate and disposition counterfeit electronic parts to prevent such parts from entering the USAF/DoD supply chain. These policies and procedures shall be documented in a CPP for submission and approval in accordance with Data Item Description (DID) DI-MISC-81832 and accomplished for all specified contract items. DI-MISC-81832 is applicable to Parts, Material and Processes Selection associated with delivery of systems and assemblies to the USAF and DoD. The requirements established by DI-MISC-81832 also apply to electronics components procured in sustainment of such systems and assemblies. The requirements of the recently-adopted DoD SAE AS5553, Aerospace Standard, Fraudulent/Counterfeit Electronics Parts; Avoidance, Detection, Mitigation, and Disposition shall also apply. The Contractor shall require their vendors, suppliers and subcontractors to participate in the counterfeit prevention and supply chain risk mitigation activities. The Contractor shall buy parts directly from original equipment manufacturers (OEMs), original component manufacturers (OCMs), and authorized distributors, and provide rationale for any exceptions. The Contractor shall conduct supply chain risk assessments of all vendors/sources-of-supply to determine the potential for obtaining counterfeit parts from these sources. The Contractor shall place supply chain risk analyses conducted to inform their own technical decisions, along with a vendor source list, on the Data Accession List (DAL). The Contractor shall establish testing and verification requirements for items not received from an OEM, OCM, or authorized distributor, based on the items’ identified risk for counterfeit potential. Submittal of Certificates of Conformance to the Government indicating that the parts are not counterfeit shall be acceptable for verification of testing. The Contractor shall notify the Government no later than 10 days of determining that any end item, component, part, or material contained in supplies purchased for the program contains counterfeit electronic parts or suspect counterfeit electronic parts. Within the same period, the Contractor shall ensure that all suspected or confirmed counterfeit items are entered into the Government-Industry Data Exchange Program (GIDEP) system, which will serve as the DoD central reporting repository. The Contractor shall ensure that no information that would identify the intended end use of the system is communicated to suppliers or made public with respect to any anti-tamper, security, and cybersecurity-related parts and products obtained for this project. The Contractor shall establish and implement a Supply Chain Risk Management process, and integrate it into their configuration management and overall risk management processes to ensure that the delivered system, maintenance equipment, and supplies (e.g., spares and repair parts) do not incorporate counterfeit parts, malicious code, or any other elements that would allow adversaries to gain unauthorized access to data, alter data, interrupt communications, or otherwise disrupt operations. The Contractor shall report to the Government any case where configuration control of systems, assemblies, subassemblies and parts, and mechanisms in their own supply chain is not sufficient to allow traceability of parts to an OEM, OCM, or authorized distributor. In these cases, the Contractor shall either find alternative sources or use expanded acceptance testing processes and methods.

(B00X, DI-MISC-81832, Counterfeit Prevention Plan) (B00Y, DI-QCIC-80125B, Government Industry Data Exchange Program (GIDEP)

Alert/Safe-Alert Report) (B00Z, DI-QCIC-80126B, Government Industry Data Exchange Program (GIDEP)

Alert/Safe-Alert Response)

3.6 Safety

The Contractor shall implement a System Safety Program Plan and shall comply with standard practices for conducting system safety established in MIL-STD-882E.

(B00T, DI-SAFT-81626, System Safety Program Plan)

3.6.1 Hazard Analysis and Risk Mitigation

The Contractor shall perform all analyses necessary to identify hazardous conditions and develop strategies for eliminating or mitigating the associated risks in accordance with MIL-STD-882E.

These shall be documented in a System Safety Hazard Analysis Report and a Safety Assessment Report.

(B00R, DI-SAFT-80101C, System Safety Hazard Analysis Report) (B00S, DI-SAFT-80102C, Safety Assessment Report)

3.6.2 Environmental, Safety, and Occupational Health (ESOH)

The Contractor shall comply with all applicable ESOH laws and regulations. The Contractor shall identify ESOH hazards, evaluate the potential ESOH risks, and propose hazard controls and solutions to mitigate or eliminate risks. When a hazard cannot be eliminated, the associated risk shall be reduced to the lowest acceptable level per MIL-STD-882E. The Contractor shall implement a hazard tracking system based on MIL-STD-882E. The Contractor shall provide ESOH assessments and data requirements (such as system-related data and characterizations needed to support Hazardous Materials (HAZMAT), usage authorizations / waivers if needed, and data to support National Environmental Policy Act compliance) in a Hazardous Materials

Management Program (HMMP) Plan. The HMMP Plan shall be reviewed during scheduled integrated design and in-process reviews.

(B00Q, DI-MGMT-81398C, Hazardous Materials Management Program (HMMP) Plan)

3.7 Technical Reviews

The Contractor shall conduct technical reviews (list shown below) during EMD to determine and ensure that the BAT System design has demonstrated sufficient maturity to proceed further into development, and to ensure the adequacy of ongoing activities relative to System Engineering, Program Protection, Program Management, Nuclear Certification, System Safety, Logistics, Test, and Configuration Management. System design maturity shall be evaluated for all production representative article BAT Core Testers and all production representative article TPSs. The System Requirements Review (SRR) shall be held at Robins AFB, GA and all other reviews shall be held at the Contractor’s facility. Technical reviews required include:

a) System Requirements Review (SRR): System-level review

b) System Functional Review (SFR): System-level review

c) Preliminary Design Review (PDR): Separate reviews for BAT Core Tester and TPSs

d) Critical Design Review (CDR): Separate reviews for BAT Core Tester and TPSs

e) Test Readiness Review (TRR): System-level review

f) Functional Configuration Audit/System Verification Review (FCA/SVR): Separate FCA reviews for TPSs and system-level review for SVR

g) Production Readiness Review (PRR): System-level review

h) Physical Configuration Audit (PCA): Separate reviews for BAT Core Tester and TPS

System-level reviews address the BAT Core Tester and all TPSs. Each successive technical review shall be approved by Government Contracting Officer correspondence prior to the Contractor presenting any subsequent technical review. The Government determines successful completion of each successive technical review based on the following: successful completion of the technical review briefing, resolution of all associated critical action items documented during the review, and formal correspondence of completion from the Government Contracting Officer.

Critical action items are defined as any deficiency in the content that is not administrative or clerical in nature. The Contractor shall strive to conduct all system-level reviews as a single event. If necessary, and with Government approval, or upon Government request, system-level reviews may be broken down into discrete events occurring at separately scheduled times. In the instance where multiple reviews are required for a system-level review, that particular system-level review shall not be considered complete until all discrete reviews are completed. Each of the technical reviews is discussed in detail in the sub-paragraphs of Section 4.1 (Increment 1 EMD), Section 5.1 (Increment 2 EMD), and Section 6.1 (Increment 3 EMD).

3.8 Program Management Activities

The Contractor shall accomplish all PM tasks necessary to execute this effort successfully. The Contractor shall provide accurate and real-time program status updates to the Government. The Contractor shall designate a program manager and technical director responsible for managing all Contractor and s-ubcontractor efforts on the BAT Program. The Contractor shall ensure all efforts on this contract are managed as one (1) integrated systems engineering effort.

3.8.1 Program Manager (PM)

The Contractor shall identify to the Government and maintain a single point of contact (Program Manager) for all matters under this contract. The Contractor shall also ensure that all program management personnel assigned to the program shall be available, as required, to meet program objectives.

3.8.2 Earned Value Management (EVM)

The Contractor shall utilize its existing internal performance management system to plan, schedule, budget, monitor, manage, and report cost, schedule, and technical status applicable to the contract. The Contractor's system shall be validated in accordance with DFARS 252.234- 7002, the Industry Guidelines delineated in the ANSI/EIA-748, Earned Value Management System (EVMS), and the general provisions of the contract, and this SOW.

The Contractor shall perform a two-phased Integrated Baseline Review (IBR):

a) A preliminary review of the IMS and Contractor preparedness, to be completed no later than 5 months after the contract award. The Government and Contractor shall incrementally and collaboratively review IBR artifacts to include, but not be limited to, validating the translation of SOW to Control Account work scope definition; analyzing the IMS, Schedule Health Assessments and Schedule Risk Assessment; mapping of high and moderate risks to affected Control Accounts; etc.

b) The full IBR event will be completed no later than 6 months after contract award. The Contractor shall also include the Government as a participant in the prime contractor-led major subcontractor IBR(s). IBR minutes shall be captured in the Integrated Program Management Report (IPMR).

3.8.2.1 Integrated Program Management Reporting

The Contractor shall report EVM data in the IPMR. The Contractor shall provide a reconciliation of reporting elements in the Contract Funds Status Report (CFSR) with the IPMR, and include as an addendum to the CFSR. Monthly billing vouchers will be available upon customer request. The Contractor shall format the deliverable data for electronic data interchange in accordance with the ANSI X12 Standard or XML equivalent. Subcontracts exceeding $20M in then-year dollars shall apply the requirements of DFARS 252.234-7002. For contracts valued at $50 million or more, the subcontractor must have an EVMS that has been validated in accordance with DFARS 252.234-7002. For contracts valued at or greater than $20 million but less than $50 million, DFARS 252.234-7002 applies. For contracts greater than $20 million but less than $50 million, the Contractor is required to have EVMS that complies with ANSI/EIA-748; however, the Government will not formally validate/accept the Contractor's management system (no formal review). EVMS flow down to contracts of less than $20M in then-year dollars or Firm-Fixed-Price contracts that exceed 12 months duration is a risk-based decision and shall be mutually agreed upon between the Contractor and the Government.

The Contractor shall track program progress and document in the Integrated Program Management Report, the status of all portions of the contract to include all events such as reviews, audits, tests, identification, and delivery of the contract line items. The Contractor shall document any activity and/or deliverable which will not be achieved as scheduled, citing the cause, contributing factors, impacts, and resolutions to get back on schedule.

(A005, DI-MGMT-81861, Integrated Program Management Report (IPMR)) (A004, DI-MGMT-81468, Contract Fund Status Report (CFSR))

3.8.2.2 Integrated Master Schedule (IMS)

Included with the IPMR, the Contractor shall implement and maintain an IMS for this program.

A baseline IMS shall be developed at the start of the program. A current IMS shall be developed and maintained throughout the program, using the original baseline schedule as an unchanging reference. The IMS shall be provided in both Microsoft Project format and PDF as part of the IPMR CDRL deliverable.

The IMS shall include the activities of the Contractor and major suppliers and shall be linked to the CWBS per MIL-STD-881C.

Prior to finalizing the initial IMS at the SRR, the Contractor shall perform a Schedule Risk Assessment (SRA) and adjust the IMS as necessary per the results of the SRA.

3.8.3 Program Reviews and Conferences

3.8.3.1 Support of Reviews and Meetings

The Contractor shall conduct all reviews, audits, and meetings as requested by the Government Contracting Officer. The Contractor shall conduct quarterly Program Management Reviews (PMR). The PMRs can be conducted concurrently with other reviews. In the event PMRs are not concurrent with other reviews, they shall be conducted at Robins AFB.

3.8.3.2 Meetings (Conferences)

The Contractor shall document all work performed, track the program’s progress, and complete all work related to this effort. Any non-critical administrative and technical issues that arise shall primarily be resolved through phone, e-mail, and/or teleconference, while more critical issues shall be addressed through formal reviews, meetings, and audits, as described within this SOW.

The Contractor shall publish an agenda for all meetings and conferences specified in this SOW.

The Contractor shall request from the Government any items or issues to be discussed or presented at the meetings, and shall include such items in the agenda. Conference agendas shall be submitted prior to any specified meetings or conferences to the Government and shall include all materials to be presented. The Contractor shall provide a written record of the discussions, decisions, and action items identified at each meeting.

3.8.3.3 Technical Interchange Meetings (TIM)

The Contractor or the Government may request that a TIM be held to resolve any program concerns that may arise during the performance of this contract. These meetings may be by Telecom, VTC, or in-person working sessions whose results and actions shall be documented in TIM minutes. The Contractor shall prepare the minutes, but the party who called the meeting shall prepare the agenda.

3.9 Logistics

3.9.1 Test Assets and Government-Furnished Equipment (GFE)

The Government will provide GFE as available from Appendix A: UUT Lists.

If the Contractor requires any listed GFE outside the times defined, the Contractor shall make the request to the Government’s Contracting Office for any GFE asset(s) no later than sixty (60) days prior to the need date. If the GFE is not available when requested, the Government will provide access to the GFE at the earliest opportunity.

The Contractor shall notify the Government Contracting Officer in the event a GFE asset fails during the period of performance. The Government will take appropriate action to replace the failed asset.

3.9.2 Technical Orders (T.O.s)

3.9.2.1 Development

Technical manuals shall be developed IAW TM-86-01N, Air ForceTechnical Manual Requirements (TMCR).