Section J - Attachment 1 - JMM BRU SOW.pdf

JOINT MINIATURE MUNITIONS BOMB RACK UNIT (JMM BRU)

STATEMENT OF WORK

Attachment 1 JMM BRU Statement of Work (SOW)

Solicitation No: FA8672-12-R-0168

TABLE OF CONTENTS

SECTION 1.0 PURPOSE

1.1 Introduction

1.2 Scope

1.3 Background

1.4 SOW Structure

1.5 Applicable Documents

1.5.1 Department of Defense Specifications

1.5.2 Department of Defense Standards, Handbooks and Instructions

1.5.3 Industry Standards

1.5.4 SOW Appendices

SECTION 2.0 TECHNOLOGY DEVELOPMENT (TD)

2.1 Technology Development

2.2 Integrated Baseline Review (IBR)

2.3 Program Management

2.3.1 Program Management

2.3.2 Integrated Master Plan (IMP)

2.3.3 Integrated Master Schedule (IMS)

2.3.4 Program Reviews

2.4 Contractor Integrated Performance Management

2.4.1 Contractor Integrated Management

2.4.2 Cost Reporting

2.4.3 Over Target Baseline (OTB), Over Target Schedule (OTS) and Restructure

2.4.4 Schedule Risk Assessment (SRA)

2.4.5 Contract Work Breakdown Structure (CWBS)

2.5 Technical Baseline and Data Management

2.5.1 Data Management

2.5.2 Integrated Digital Environment (IDE)

2.5.3 Technical Baseline Management

2.5.3.1 Engineering Change Proposal (ECP)

2.5.3.2 Request for Deviation “Variance” (RFD)

2.5.3.3 Notice of Revision (NOR)

2.6 Systems Engineering

2.6.1 Systems Engineering and Technical Management

2.6.2 Systems Engineering Management Plan (SEMP)

2.6.3 Requirements Management

2.6.4 Design

2.6.5 Manufacturing and Producibility

2.6.6 Sustainment

2.6.7 Technical Management and Control

2.6.7.1 Systems Engineering Technical Reviews (SETRs)

2.6.7.2 Technical Meetings

2.6.7.2.1 Systems Engineering and Integration Team (SEIT) Meetings

2.6.7.2.2 Technical Interchange Meetings (TIMs)

2.6.7.3 Technical Performance Measurements (TPMs)

2.6.7.4 Technology Readiness Assessment (TRAs)

2.6.7.5 Technology Maturation Plan (TMP)

2.6.8 Working Groups

2.6.9 Risk Management

2.6.10 Interface Management

2.6.11 Decision Analyses

2.6.12 Specialty Engineering Requirements

2.6.13 System Safety

2.6.13.1 System Safety Program

2.6.13.2 Critical Safety Items

2.6.13.3 System Safety Assessments

2.6.14 Human Systems Integration (HSI)

2.6.14.1 Human Factors Engineering Program

2.6.14.2 Human Factors Engineering Evaluation

2.6.15 Reliability

2.6.15.1 Reliability Program Plan (RPP)

2.6.15.1.1 Reliability Management Activities

2.6.15.1.2 Reliability Design Activities

2.6.15.1.3 Reliability Analysis Activities

2.6.15.1.4 Reliability Verification and Testing Activities

2.6.15.1.5 Reliability Growth Planning Model

2.6.15.1.6 Reliability Growth Tracking Model

2.6.15.1.7 Reliability Growth Projection Model

2.6.16 Mechanical and Structural Integrity

2.6.17 Corrosion Prevention and Control

2.6.18 Materials and Processes

2.6.18.1 Non-Destructive Testing and Inspection (NDT/I)

2.6.19 Modular Open Systems Architecture (MOSA)

2.6.20 Environmental, Safety and Occupational Health (ESOH)

2.6.20.1 Hazardous Material

2.6.21 Software Engineering

2.6.21.1 Software Development

2.6.21.2 Software Development Plan (SDP)

2.6.21.3 Software Metrics

2.6.21.4 Software Deliverables

2.6.21.5 Universal Armament Interface (UAI)

2.6.22 Modeling and Simulation (M&S)

2.6.23 JMM BRU Design Specifications

2.6.23.1 System Design Specification (SDS)

2.6.23.2 Environmental Design Criteria (EDC)

2.6.24 JMM BRU Test Assets and Test Support Equipment Design and Fabrication

2.6.24.1 Prototypes

2.6.24.2 JMM BRU Instrumented Measurement Vehicles (IMV)

2.6.24.3 JMM BRU Telemetry (JMM BRU TM)

2.6.24.4 JMM BRU Weapon System Simulators (WSS)

2.6.24.4.1 JMM BRU Racks and Containers

2.6.24.4.2 JMM BRU Simulators

2.6.24.4.3 JMM BRU Simulator Controller Laptop Computer

2.6.25 System Verification

2.6.25.1 Verification Activities

2.6.25.2 Verification Plan

2.6.25.3 Prototype Testing

2.6.25.3.1 Prototype Test Procedure(s)

2.6.25.3.2 Prototype Test Conduct

2.6.25.3.3 Prototype Test Report(s)

2.6.25.4 Design Qualification

2.6.25.4.1 Design Qualification Plan

2.6.25.4.2 Design Qualification Procedure(s)

2.6.25.4.3 Design Qualification Conduct

2.6.25.4.4 Design Qualification Report(s)

2.7 Associate Contractor Agreements (ACA)

2.8 Airworthiness

2.9 Logistics Management

2.9.1 Integrated Logistics Support (ILS)

2.9.2 Logistics Support Documentation

2.9.3 Common Aircraft Armament Test Set (CAATS)

2.9.4 Support Equipment

2.10 Manufacturing and Producibility

2.10.1 Manufacturing Management

2.10.2 Manufacturing Readiness Assessment (MRA)

2.10.3 Manufacturing Readiness Maturation

2.10.4 MRA Update for Milestone B (MS B)

2.10.5 Key Production Characteristics (KPCs)

2.10.6 Process Improvement

2.10.7 Producibility

2.11 Quality Management

2.11.1 Quality Management System (QMS)

2.11.2 Quality Assurance Plan

2.11.3 Government Industry Data Exchange Program (GIDEP)

2.12 Supply Chain Management (SCM)

2.12.1 SCM Plan

2.12.2 Supply Chain Risk Management

2.12.2.1 Criticality Analysis

2.12.2.2 Risk Mitigation

2.12.3 Obsolescence and Diminishing Manufacturing Sources and Material Shortages (DMSMS) Management

2.13 Test Equipment

2.13.1 Portable Test Equipment

2.14 Information Assurance (IA)

2.14.1 Information Assurance Plan and IA Support

2.14.2 IA Support of Commercial Off the Shelf (COTS) Software

2.14.3 IA Technical Considerations

2.14.4 Mission Assurance Category (MAC) II Classification IA Controls

2.14.5 Protection of DoD Information

2.14.6 Protection of Non-DoD Information Systems

2.14.7 Foreign National Access

2.15 Program Protection Plan (PPP)

2.15.1 Anti-Tamper (AT)

2.16 Item Unique Identification

SECTION 3.0 ENGINEERING AND MANUFACTURING DEVELOPMENT (EMD) JMM BRU

DEVELOPMENT

3.1 EMD JMM BRU Development

3.2 Integrated Baseline Review (IBR)

3.3 Program Management

3.3.1 Program Management

3.3.2 Integrated Master Plan (IMP)

3.3.3 Integrated Master Schedule (IMS)

3.3.4 Program Reviews

3.4 Contractor Integrated Performance Management

3.4.1 Contractor Integrated Management

3.4.2 Cost Reporting

3.4.3 Over Target Baseline (OTB), Over Target Schedule (OTS) and Restructure

3.4.4 Schedule Risk Assessment (SRA)

3.4.5 Contract Work Breakdown Structure (CWBS)

3.5 Technical Baseline and Data Management

3.5.1 Data Management

3.5.2 Integrated Digital Environment (IDE)

3.5.3 Technical Baseline Management

3.5.3.1 Engineering Change Proposal (ECP)

3.5.3.2 Request for Deviation “Variance” (RFD)

3.5.3.3 Notice of Revision (NOR)

3.5.3.4 Configuration Status Accounting (CSA)

3.6 Systems Engineering

3.6.1 Systems Engineering and Technical Management

3.6.2 Systems Engineering Management Plan (SEMP)

3.6.3 Requirements Management

3.6.4 Design

3.6.5 Manufacturing and Producibility

3.6.6 Sustainment

3.6.7 Technical Management and Control

3.6.7.1 Systems Engineering Technical Reviews (SETRs)

3.6.7.2 Technical Meetings

3.6.7.2.1 Systems Engineering and Integration Team (SEIT) Meetings

3.6.7.2.2 Technical Interchange Meetings (TIMs)

3.6.7.3 Technical Performance Measurements (TPMs)

3.6.7.4 Technology Readiness Assessment (TRAs)

3.6.7.5 Technology Maturation Plan Updates for Milestone C (MS C)

3.6.8 Working Groups

3.6.9 Risk Management

3.6.10 Interface Management

3.6.11 Decision Analyses

3.6.12 Specialty Engineering Requirements

3.6.13 System Safety

3.6.13.1 System Safety Program

3.6.13.2 Critical Safety Items

3.6.13.3 System Safety Assessments

3.6.14 Human Systems Integration (HSI)

3.6.14.1 Human Factors Engineering Program

3.6.14.2 Human Factors Engineering Evaluation

3.6.15 Reliability

3.6.15.1 Reliability Program Plan (RPP)

3.6.15.1.1 Reliability Management Activities

3.6.15.1.2 Reliability Design Activities

3.6.15.1.3 Reliability Analysis Activities

3.6.15.1.4 Reliability Verification and Testing Activities

3.6.15.1.5 Reliability Growth Planning Model

3.6.15.1.6 Reliability Growth Tracking Model

3.6.15.1.7 Reliability Growth Projection Model

3.6.16 Mechanical and Structural Integrity

3.6.17 Corrosion Prevention and Control

3.6.18 Materials and Processes

3.6.18.1 Nondestructive Testing and Inspection (NDT/I)

3.6.19 Modular Open Systems Architecture (MOSA)

3.6.20 Environmental, Safety and Occupational Health (ESOH)

3.6.20.1 Hazardous Material

3.6.21 Software Engineering

3.6.21.1 Software Development

3.6.21.2 Software Development Plan (SDP)

3.6.21.3 Software Metrics

3.6.21.4 Software Deliverables

3.6.21.5 Universal Armament Interface (UAI)

3.6.22 Modeling and Simulation (M&S)

3.6.23 JMM BRU Design Specifications

3.6.23.1 System Design Specification (SDS)

3.6.23.2 Environmental Design Criteria (EDC)

3.6.24 JMM BRU Test Assets and Test Support Equipment Design and Fabrication

3.6.24.1 JMM BRU Instrumented Measurement Vehicles (IMV)

3.6.24.2 JMM BRU Telemetry (JMM BRU TM)

3.6.24.3 JMM BRU Weapon System Simulators (WSS)

3.6.24.4 Tactical JMM BRU Fabrication

3.6.25 System Verification

3.6.25.1 Verification Activities

3.6.25.2 Verification Plan

3.6.25.3 JMM BRU Acceptance

3.6.25.3.1 Acceptance Plan

3.6.25.3.2 Acceptance Test Procedure (ATP)

3.6.25.3.3 JMM BRU IMV Performance Test Procedure(s)

3.6.25.3.4 JMM BRU TM Performance Test Procedure(s)

3.6.25.3.5 Tactical JMM BRU Performance Test Procedure(s)

3.6.25.3.6 Performance Test Conduct

3.6.25.3.7 Performance Test Reporting

3.6.25.4 Design Qualification

3.6.25.4.1 Design Qualification Plan

3.6.25.4.2 Design Qualification Procedure(s)

3.6.25.4.3 Design Qualification Conduct

3.6.25.4.4 Design Qualification Report(s)

3.7 Associate Contractor Agreements (ACA)

3.8 Airworthiness and Aircraft Integration Testing Support

3.9 Wind Tunnel Support

3.10 Training

3.11 Logistics Management

3.11.1 Integrated Logistics Support (ILS)

3.11.2 Logistics Support Documentation

3.11.3 Common Aircraft Armament Test Set (CAATS)

3.11.4 Support Equipment

3.11.5 Logistic Evaluation

3.12 Manufacturing and Producibility

3.12.1 Manufacturing Management

3.12.2 Manufacturing Readiness Assessment (MRA)

3.12.3 Manufacturing Readiness Maturation

3.12.4 MRA Update for Milestone C (MS C)

3.12.5 Key Production Characteristics (KPCs)

3.12.6 Process Improvement

3.12.7 Producibility

3.13 Quality Management

3.13.1 Quality Management System (QMS)

3.13.2 Quality Assurance Plan

3.13.3 Government Industry Data Exchange Program (GIDEP)

3.14 Supply Chain Management (SCM)

3.15 Test Equipment

3.15.1 Portable Test Equipment

3.15.2 Factory Test Set

3.16 Information Assurance (IA)

3.16.1 Information Assurance Plan and IA Support

3.16.2 IA Support of Commercial Off the Shelf (COTS) Software

3.16.3 IA Technical Considerations

3.16.4 Mission Assurance Category (MAC) II Classification IA Controls

3.16.5 Protection of DoD Information

3.16.6 Protection of Non-DoD Information Systems

3.16.7 Foreign National Access

3.17 Program Protection Plan (PPP)

3.17.1 Anti-Tamper (AT)

3.18 Item Unique Identification

SECTION 4.0 ENGINEERING AND MANUFACTURING DEVELOPMENT (EMD) JMM BRU F-35

FLIGHT TEST

4.1 EMD JMM BRU F-35 Flight Test

4.2 Integrated Baseline Review (IBR)

4.3 Program Management

4.3.1 Program Management

4.3.2 Integrated Master Plan (IMP)

4.3.3 Integrated Master Schedule (IMS)

4.3.4 Program Reviews

4.4 Contractor Integrated Performance Management

4.4.1 Contractor Integrated Management

4.4.2 Cost Reporting

4.4.3 Over Target Baseline (OTB), Over Target Schedule (OTS) and Restructure

4.4.4 Schedule Risk Assessment (SRA)

4.4.5 Contract Work Breakdown Structure (CWBS)

4.5 Technical Baseline and Data Management

4.5.1 Data Management

4.5.2 Integrated Digital Environment (IDE)

4.5.3 Technical Baseline Management

4.5.3.1 Engineering Change Proposal (ECP)

4.5.3.2 Request for Deviation “Variance” (RFD)

4.5.3.3 Notice of Revision (NOR)

4.5.3.4 Configuration Status Accounting (CSA)

4.6 Systems Engineering

4.6.1 Systems Engineering and Technical Management

4.6.2 Systems Engineering Management Plan (SEMP)

4.6.3 Requirements Management

4.6.4 Design

4.6.5 Manufacturing and Producibility

4.6.6 Sustainment

4.6.7 Technical Management and Control

4.6.7.1 Systems Engineering Technical Reviews (SETRs)

4.6.7.2 Technical Meetings

4.6.7.2.1 Systems Engineering and Integration Team (SEIT) Meetings

4.6.7.2.2 Technical Interchange Meetings (TIMs)

4.6.7.3 Technical Performance Measurements (TPMs)

4.6.8 Working Groups

4.6.9 Risk Management

4.6.10 Interface Management

4.6.11 Decision Analyses

4.6.12 Specialty Engineering Requirements

4.6.13 System Safety

4.6.13.1 System Safety Program

4.6.13.2 Critical Safety Items

4.6.13.3 System Safety Assessments

4.6.14 Human Systems Integration (HSI)

4.6.15 Reliability

4.6.15.1 Reliability Program Plan (RPP)

4.6.15.1.1 Reliability Management Activities

4.6.15.1.2 Reliability Analysis Activities

4.6.15.1.3 Reliability Verification and Testing Activities

4.6.15.1.4 Reliability Growth Planning Model

4.6.15.1.5 Reliability Growth Tracking Model

4.6.15.1.6 Reliability Growth Projection Model

4.6.16 Mechanical and Structural Integrity

4.6.17 Corrosion Prevention and Control

4.6.18 Materials and Processes

4.6.19 Environmental Safety and Occupational Health (ESOH)

4.6.19.1 Hazardous Material

4.6.20 Software Engineering

4.6.20.1 Software Development

4.6.20.2 Software Development Plan (SDP)

4.6.20.3 Software Metrics

4.6.20.4 Software Deliverables

4.6.20.5 Universal Armament Interface (UAI)

4.6.21 Modeling and Simulation (M&S)

4.6.22 JMM BRU Design Specifications

4.6.22.1 System Design Specification (SDS)

4.6.22.2 Environmental Design Criteria (EDC)

4.6.23 JMM BRU Test Assets and Test Support Equipment

4.6.23.1 JMM BRU Instrumented Measurement Vehicles (IMV)

4.6.23.2 JMM BRU Telemetry (JMM BRU TM)

4.6.23.3 JMM BRU Weapon System Simulators (WSS)

4.6.23.4 Tactical JMM BRU

4.6.24 System Verification

4.6.24.1 Verification Activities

4.6.24.2 Verification Plan

4.6.24.3 JMM BRU Acceptance

4.6.24.3.1 Acceptance Plan

4.6.24.3.2 Acceptance Test Procedure (ATP)

4.6.24.3.3 JMM BRU IMV Performance Test Procedure(s)

4.6.24.3.4 JMM BRU TM Performance Test Procedure(s)

4.6.24.3.5 Tactical JMM BRU Performance Test Procedure(s)

4.6.24.3.6 Performance Test Conduct

4.6.24.3.7 Performance Test Reporting

4.6.24.4 Design Qualification

4.6.24.4.1 Design Qualification Plan

4.6.24.4.2 Design Qualification Procedure(s)

4.6.24.4.3 Design Qualification Conduct

4.6.24.4.4 Design Qualification Report(s)

4.7 Associate Contractor Agreements (ACA)

4.8 Airworthiness and Aircraft Integration Testing Support

4.9 Logistics Management

4.9.1 Integrated Logistics Support (ILS)

4.9.2 Logistics Support Documentation

4.10 Test Equipment

4.10.1 Portable Test Equipment

4.10.2 Factory Test Set

4.11 Program Protection Plan (PPP)

SECTION 5.0 PRODUCTION LOTS 1 AND 2

5.1 Production Lots 1 and 2

5.2 Integrated Baseline Review (IBR)

5.3 Program Management

5.3.1 Program Management

5.3.2 Integrated Master Plan (IMP)

5.3.3 Integrated Master Schedule (IMS)

5.3.4 Program Reviews

5.4 Contractor Integrated Performance Management

5.4.1 Contractor Integrated Management

5.4.2 Cost Reporting

5.4.3 Over Target Baseline (OTB), Over Target Schedule (OTS) and Restructure

5.4.4 Contract Work Breakdown Structure (CWBS)

5.5 Technical Baseline and Data Management

5.5.1 Data Management

5.5.2 Integrated Digital Environment (IDE)

5.5.3 Technical Baseline Management

5.5.3.1 Engineering Change Proposal (ECP)

5.5.3.2 Request for Deviation “Variance” (RFD)

5.5.3.3 Notice of Revision (NOR)

5.5.3.4 Configuration Status Accounting (CSA)

5.6 Systems Engineering

5.6.1 Systems Engineering and Technical Management

5.6.2 Systems Engineering Management Plan (SEMP)

5.6.3 Requirements Management

5.6.4 Design

5.6.5 Technical Management and Control

5.6.5.1 Systems Engineering Technical Reviews (SETRs)

5.6.5.2 Technical Meetings

5.6.5.2.1 Systems Engineering and Integration Team (SEIT) Meetings

5.6.5.2.2 Technical Interchange Meetings (TIMs)

5.6.5.3 Technical Performance Measurements (TPMs)

5.6.6 Working Groups

5.6.7 Risk Management

5.6.8 Interface Management

5.6.9 Decision Analyses

5.6.10 Specialty Engineering Requirements

5.6.11 System Safety

5.6.11.1 System Safety Program

5.6.11.2 Critical Safety Items

5.6.11.3 System Safety Assessments

5.6.12 Human Systems Integration (HSI)

5.6.13 Reliability

5.6.13.1 Reliability Program Plan (RPP)

5.6.13.1.1 Reliability Management Activities

5.6.13.1.2 Reliability Analysis Activities

5.6.13.1.3 Reliability Verification and Testing Activities

5.6.13.1.4 Reliability Growth Planning Model

5.6.13.1.5 Reliability Growth Tracking Model

5.6.13.1.6 Reliability Growth Projection Model

5.6.14 Corrosion Prevention and Control

5.6.15 Materials and Processes

5.6.15.1 Nondestructive Testing and Inspection (NDT/I)

5.6.16 Environmental Safety and Occupational Health (ESOH)

5.6.16.1 Hazardous Material

5.6.17 Software Engineering

5.6.17.1 Software Development

5.6.17.2 Software Development Plan (SDP)

5.6.17.3 Software Metrics

5.6.17.4 Software Deliverables

5.6.17.5 Universal Armament Interface (UAI)

5.6.18 Modeling and Simulation (M&S)

5.6.19 JMM BRU Design Specification

5.6.19.1 System Design Specification (SDS)

5.6.19.2 Environmental Design Criteria (EDC)

5.6.20 System Verification

5.6.20.1 JMM BRU Acceptance

5.6.20.1.1 Acceptance Plan

5.6.20.1.2 Acceptance Test Procedure (ATP)

5.6.20.1.3 Acceptance Test Conduct

5.6.20.1.4 Acceptance Test Report(s)

5.7 Associate Contractor Agreements (ACA)

5.8 Logistics Management

5.8.1 Integrated Logistics Support (ILS)

5.8.2 Logistics Support Documentation

5.9 Manufacturing Management

5.9.1 Manufacturing Readiness Assessment (MRA)

5.9.2 Key Production Characteristics (KPCs)

5.9.3 Process Improvement

5.9.4 Producibility

5.10 Quality Management

5.10.1 Quality Management System (QMS)

5.10.2 Quality Assurance Plan

5.10.3 Government Industry Data Exchange Program (GIDEP)

5.11 Supply Chain Management (SCM)

5.12 Test Equipment

5.12.1 Factory Test Set

5.13 Information Assurance (IA)

5.13.1 Information Assurance Plan and IA Support

5.13.2 IA Support of Commercial Off the Shelf (COTS) Software

5.13.3 IA Technical Considerations

5.13.4 Mission Assurance Category (MAC) II Classification IA Controls

5.13.5 Protection of DoD Information

5.13.6 Protection of Non-DoD Information Systems

5.13.7 Foreign National Access

5.14 Program Protection Plan (PPP)

5.14.1 Anti-Tamper (AT)

5.15 Item Unique Identification

5.16 Production Engineering Support

5.17 Technical Data Package (TDP)

5.18 First Article Acceptance Test (FAAT)

5.18.1 First Article Acceptance Test (FAAT) Procedure(s)

5.18.2 First Article Acceptance Testing

5.18.3 First Article Acceptance Test (FAAT) Report

5.19 Lot Acceptance Test (LAT)

5.19.1 Lot Acceptance Test (LAT) Procedure(s)

5.19.2 Lot Acceptance Testing

5.19.3 Lot Acceptance Test (LAT) Report

SECTION 6.0 ACRONYMS

SECTION 1.0 PURPOSE

1.1 Introduction

This Statement of Work (SOW) identifies the minimum tasks to be executed by the Joint Miniature Munitions Bomb Rack Unit (JMM BRU) Contractor to complete the Technology Development (TD), Engineering and Manufacturing Development (EMD) and to fabricate and deliver Production Lot 1 and 2 units for the JMM BRU Program.

1.2 Scope

The Contractor shall furnish documentation, services, hardware, software, material, facilities, and equipment required to develop, qualify, build and maintain JMM BRU prototypes, JMM BRU Instrumented Measurement Vehicle (IMV), JMM BRU Telemetry (TM), and Tactical JMM BRU for the TD, EMD and to fabricate, test and deliver Production Lot 1 and 2 units. The Contractor shall support integration of the JMM BRU with the Small Diameter Bomb Increment II (SDB II) and the F-35B and F-35C aircraft.

1.3 Background

The JMM BRU Program is an evolutionary acquisition of the miniature munitions carriage to meet the Department of Navy (DoN) integration requirements in support of the SDB II, F-35B and F-35C weapon systems. The JMM BRU requirements are defined in the JMM BRU System Performance Specification (SPS), 20107143. The JMM BRU (BRU-61A/A) will be designed to satisfy the F-35B and F-35C aircraft, carriage and weapon system integration requirement for the DoN.

1.4 SOW Structure

The tasks and activities in this SOW shall be executed by the Contractor and are provided in six sections.

Section 1.0 is purpose. Section 2.0 provides requirements that are specific to the TD of this contract.

Section 3.0 provides requirements that are specific to the EMD JMM BRU Development option of this contract. Section 4.0 provides requirements that are specific to the EMD JMM BRU F-35 Flight Test option of this contract. Section 5.0 provides requirements that are specific to the Production Lot 1 and 2 option of this contract. Section 6.0 is acronyms.

1.5 Applicable Documents

The documents listed below are applicable to this SOW to the extent specified herein. Unless otherwise stated, the Offeror shall utilize the version of each document listed below.

1.5.1 Department of Defense Specifications

UAI-PSICD R03 Feb 2010 Universal Armament Interface (UAI) Platform / Store Interface Control Document

20118100 JMM BRU Performance Environments Criteria (PEC) 20107143 JMM BRU System Performance Specification (SPS)

1.5.2 Department of Defense Standards, Handbooks and Instructions

Assistant Secretary of Defense DTM 08-027 Ch 2 Sep 2011

Security of Unclassified DoD Information on Non-DoD Information Systems

Aeronautical Systems Center MDG Oct 2010

Manufacturing Development Guide (MDG)

DD Form 1949-3 Aug 1992 Logistics Support Analysis Record (LSAR) Data Requirements DFARS 252.234-7001 Notice of Earned Value Management System DFARS 252.234-7002 Earned Value Management System DFARS 252.239-7000 Protection Against Compromising Emanations DoD Manual 4245.7-M Sep 1985

Transition from Development to Production

DoD Manual 8570.01-M Ch2 Feb 2010

Information Assurance Workforce Improvement Program (Change 1 incorporated May 2008, Change 2 incorporated February 2010)

DoD Directive 5230.09 Aug 2008

Clearance of DoD Information for Public Release

DoDI 3020.46 Oct 2008 The Militarily Critical Technologies List (MCTL) DoDI 5000.02 Dec 2008 Operation of the Defense Acquisition System DoDI 5200.39 Ch1 Dec

Critical Program Information (CPI) Protection Within the DoD

DoDI 8500.2 Feb 2003 Information Assurance (IA) Implementation DoDI 8520.02 May 2004 Public Key Infrastructure (PKI) and Public Key (PK) Enabling DoD CPC Planning Guidebook Sep 2007

DoD Corrosion Prevention and Control Planning Guidebook Spiral No. 3

DoD MRL Deskbook V2.01 Jul 2011

Manufacturing Readiness Level (MRL) Deskbook

DoD TRA Guidance Dated April 2011

DoD Technology Readiness Assessment (TRA) Guidance

DoN DIACAP Handbook, Version 1.0 July 2008

DoD Information Assurance Certification and Accreditation Process (DIACAP) Handbook

Joint Strike Fighter Jan

Joint Service Store Certification Guide Phase II

MIL-HDBK-189C Jun 2011 Reliability Growth Management MIL-HDBK-516B Ch1 Feb

Airworthiness Certification Criteria

MIL-HDBK-838 Dec 1997 Lubrication of Military Equipment MIL-HDBK-896 Aug 2008 Manufacturing and Quality Program MIL-HDBK-1763 Jun 1998 Aircraft Stores Compatibility: Systems Engineering Data

Requirements and Test Procedures MIL-HDBK-2164A Jun

Environmental Stress Screening Process for Electronic Equipment

MIL-HDBK-6870A Aug

Inspection Program Requirements Nondestructive for Aircraft and Missile Materials and Parts

MIL-STD-129P Ch4 Sep

Military Marking for Shipment and Storage

MIL-STD-130N Dec 2007 Identification Marking of U.S. Military Property

MIL-STD-882D Feb 2000 Standard Practice for System Safety MIL-STD-1760E Oct 2007 Interface Standard Aircraft/Store Electrical Interconnection System MIL-STD-2073-1E Ch1 Jan 2011

Standard Practice for Military Packaging

MIL-STD-3001 May 2001 Preparation of Digital Technical Information for Multi-Output Presentation of Technical Manuals

MIL-STD-8591 Dec 2005 Design Criteria Standard. Airborne Stores, Suspension equipment and Aircraft-Store Interface (Carriage Phase)

MIL-STD-46855A May

Human Engineering Requirements for Military Systems, Equipment, and Facilities

NAVAIRINST 4200.25D

Jun 2002

Management of Critical Application Items Including Critical Safety Items

NAVAIRINST 4355.19D

Apr 2009

Systems Engineering Technical Review Process

NAVAIRINST 13034.1D

Mar 2010

Flight Clearance Policy for Air Vehicles and Aircraft Systems

NAVSEAINST 8020.6E

Mar 2008

DoN Weapon System Explosives Safety Review Board

NSTISSP -11 July 2003 National Security Telecommunications and Information Systems Security Policy Number 11

SECNAVINST 5230.15

Apr 2009

Information Management/Information Technology Policy for Fielding of Commercial Off the Shelf Software

SO300-BT-PRO-010 Sep

GIDEP Operations Manual

1.5.3 Industry Standards

ANSI/EIA-748B Earned Value Management Systems ANSI/GEIA-STD-0009 Reliability Program Standard for Systems Design, Development, and

Manufacturing AS9100-C Quality Management Systems for Aviation, Space and Defense

Organizations

IEEE/EIA STD 12207.1-

1997 Apr 1998

Standard for Information Technology-Software Life Cycle Processes- Life Cycle Data

GEIA-STD-0007 V1.0 Aug

Logistics Product Data

National Aerospace Standard 410 (NAS 410) Rev 3 Mar 2008

Certification and Qualification of Nondestructive Test Personnel

National Aerospace Standard (NAS 411) Jan

Hazardous Materials Management Program

National Defense Industrial Association System

Engineering for System Assurance

Assurance Committee V1 National Institute of Standards and Technology Dec 2002

Federal Information Processing Standards Publication (FIPS 140-2)

– Security Requirements for Cryptographic Modules

National Institute of Standards and Technology Interagency Report 7622 Jun 2010

Piloting Supply Chain Risk Management for Federal Information Systems

1.5.4 SOW Appendices

Appendix 01 JMM BRU Project Plan Appendix 02 Cost and Software Data Reporting (CSDR) Plan Appendix 03 SEP Appendix 04 JMMUWG Charter Appendix 05 Tailored MIL-T-7743 Requirements for JMM BRU Design

Qualification Plan Appendix 06 DFDDP Requirements Document Appendix 07 TMCR 11-004 Appendix 08 BRU-61A/A, SDB II & F-35B/C Aircraft Integration Planning

Information Appendix 09 SPVP Outline - CDRL A027, B027, and C027 Appendix 10 PIT Risk Approval (PRA) tool Excel Spreadsheet/Workbook

Template - CDRL A032 and B032

SECTION 2.0 TECHNOLOGY DEVELOPMENT (TD)

2.1 Technology Development

The Contractor shall conduct TD to initiate JMM BRU design activities, mature JMM BRU technologies, initiate production process development to determine the appropriate set of technologies to be integrated into a full system, and conduct prototyping in a relevant environment.

2.2 Integrated Baseline Review (IBR)

The Contractor shall review the performance measurement baseline plan with the Government within three months of contract award and when warranted following major changes to the baseline. The Government will verify during the initial and follow-on IBRs that the Contractor has established and maintains a reliable performance measurement baseline. Entry and exit criteria for IBRs are defined in the Systems Engineering Plan (SEP). The IBR shall be conducted in accordance with Systems Engineering Technical Reviews (SETR) paragraph 2.6.7.1.

2.3 Program Management

2.3.1 Program Management

The Contractor shall provide program management that is responsible for all aspects of this contract.

This Contractor shall provide a direct point of contact for program concerns and shall control all cost, schedule, performance, earned value, planning, and incorporation of all design modifications. The Contractor shall provide the necessary engineering services, project management functions, financial control, planning and control functions required to fulfill deliveries in accordance with Section F of the contract.

2.3.2 Integrated Master Plan (IMP)

The Contractor shall manage the execution of the JMM BRU program using the IMP and the associated JMM BRU Integrated Master Schedule (IMS) as day-to-day execution tools and periodically assess progress in meeting program requirements. The Contractor shall maintain the IMP and shall update the IMP when deemed necessary to reflect changes to the JMM BRU program, subject to approval by the Government JMM BRU Program Office (AAC/EBM Eglin AFB, FL). The Contractor shall report on program progress in accordance with the IMP at each program management review, technical reviews, and at any other times at the Government's request. The Contractor shall use only one IMP for the entire JMM BRU program (TD, EMD JMM BRU Development, EMD JMM BRU F-35 Flight Test, and Production Lots 1 and 2) and the Contractor shall include all subcontractor activities in the IMP. The JMM BRU Contractor shall flow this requirement down to all subsystem suppliers. (CDRL A006, Data Accession List)

2.3.3 Integrated Master Schedule (IMS)

The Contractor shall maintain and revise the JMM BRU IMS to reflect the JMM BRU IMP. The Contractor shall use the Government JMM BRU Project Plan (Appendix 01) as the basis for developing the Contractor’s IMP and IMS. The Contractor shall use the JMM BRU IMS as a day-to-day execution tool and periodically assess progress in meeting program requirements. The Contractor shall maintain and update the JMM BRU IMS to reflect approved changes to the JMM BRU IMP, or changes in the Contractor's detailed execution activities or schedule. The JMM BRU IMS shall include the activities of the JMM BRU Contractor and their major subcontractors. All Contractor schedule information delivered to the Government or presented at program reviews shall originate from the JMM BRU IMS. The Contractor shall perform appropriate analysis of the JMM BRU IMS tasks and report to the Government potential or existing problem areas and recommended corrective actions to reduce or eliminate schedule impacts.

(CDRL A001, Integrated Master Schedule)

2.3.4 Program Reviews

The Contractor shall conduct quarterly Program Management Review (PMR) meetings at mutually agreed upon dates at the Contractor facility. During these reviews, the Contractor shall present integrated cost, schedule, and technical performance status.

PMRs shall include cost information in discussions of schedule status, technical performance, and risk using earned value as an integrating tool. The following shall be addressed: cost and schedule trends;

significant cost; schedule or technical variances; projected impacts; quantified risk assessments and corrective action plans.

The Contractor shall prepare and deliver the PMR agenda five working days prior to the PMR. The Contractor shall document the attendees, a synopsis of the PMR, significant PMR action items, issues discussed during the PMR, and presentation material presented at the PMR by the Contractor and Government in the PMR minutes within five working days after conducting the PMR. (CDRL A006, Data Accession List)

In addition to PMRs, the Contractor shall conduct weekly teleconferences with the Government team.

During these teleconferences, the Contractor shall present integrated cost using Contractor Earned Value Management Systems (EVMS), IMS, and technical performance status.

2.4 Contractor Integrated Performance Management

2.4.1 Contractor Integrated Management

In accordance with DFARS 252.234-7001 and 252.234-7002, the Contractor shall establish, maintain, and implement an integrated management system compliant with the Industry Guidelines for EVMS ANSI/EIA-748B. The Contractor shall ensure that application of their integrated management system provides for early indications of contract cost and schedule performance. The Contractor shall ensure the earned value assessments correlate with progress meeting all the aspects of the JMM BRU program and technical achievement.

2.4.2 Cost Reporting

The Contractor shall provide a Contract Performance Report (CPR), Contract Funds Status Report (CFSR), and Cost Data Summary Report (CDSR). The Contractor shall flow down the requirements of these reports to their subcontractors and suppliers as appropriate. (CDRL A002, Contract Performance Report), (CDRL A003, Contract Funds Status Report), (CDRL A004, Cost Data Summary Report)

2.4.3 Over Target Baseline (OTB), Over Target Schedule (OTS) and Restructure

In the event the Contractor concludes that the program baseline no longer represents a realistic plan in terms of budget or schedule execution, the Contractor may request an OTB, OTS, and Restructuring action. The Contractor shall include in the OTB, OTS, and Restructure request, detailed implementation procedures as well as an implementation timeframe. The Contractor shall not implement the OTB, OTS, and Restructuring prior to receiving written approval from the JMM BRU Procuring Contracting Officer.

2.4.4 Schedule Risk Assessment (SRA)

The Contractor shall conduct a quarterly SRA with Government participation in conjunction with the quarterly PMR. The SRA is to provide program management with an understanding of the potential schedule impacts associated with existing or emerging program risks. These analyses will compute the probability of completing key milestones, events, tasks, and activities by specific dates. The Contractor shall report optimistic, pessimistic, and most likely remaining durations and rationale for the values in accordance with the IMS for each task or activity on any of the following paths: critical path to program completion and the critical path to the next Major Milestone. For tasks or activities not identified as being on any of the critical paths, Global Weighting Values and rationale shall be provided by the Contractor.

Global Weighting Values will be used to establish minimum and maximum remaining duration estimates.

In addition, technical team members will be asked to provide pessimistic, most likely and optimistic durations for any moderate to high risk activities identified in the Program Risk Database (generally identified through a risk cube) that are associated with IMS tasking. (CDRL A001, Integrated Master Schedule), (CDRL A006, Data Accession List)

2.4.5 Contract Work Breakdown Structure (CWBS)

The Contractor shall develop, maintain, and deliver the CWBS and CWBS dictionary using the Work Breakdown Structure (WBS) contained in the attached Cost and Software Data Reporting (CSDR) plan (Appendix 02). (CDRL A005, CWBS and CWBS dictionary)

2.5 Technical Baseline and Data Management

2.5.1 Data Management

The Contractor shall establish, implement, and maintain data management activities that facilitate planning, acquiring, accessing, protecting, and the use of technical data. The Contractor shall ensure data products are produced with the appropriate document representation and data file identification, version control, and clear and unambiguous relationships to the product configuration with which they are associated, and to changes that delineate each configuration of the product. The Contractor shall develop and maintain a Data Accession List (DAL). The DAL shall identify all Contractor-generated data such as data used in the development, testing, and management of the program. The Contractor shall include all specifications, drawings, reports, analyses, white papers, computer software testing plans, and reports generated or utilized as part of the JMM BRU contract on the DAL. The Contractor shall document the data management processes in the Systems Engineering Management Plan (SEMP).

(CDRL A006, Data Accession List), (CDRL A010, Systems Engineering Management Plan (SEMP))

2.5.2 Integrated Digital Environment (IDE)

The Contractor shall establish and maintain an unclassified IDE that provides the Government on-line access to programmatic and technical data developed or utilized as part of the JMM BRU program. The Contractor shall ensure the IDE implements the capability for program management and technical activities to digitally create, store, access, manipulate, share, and exchange programmatic and technical data. The Contractor shall notify the Government via electronic means when any data is added to the IDE. All Contract Data Requirements List (CDRL) items shall be delivered to the Government via the IDE.

All formal correspondence deemed appropriate for delivery via electronic facsimile, the United States (US) mail, or other couriers shall also be scanned and posted to the IDE after signatures are applied.

2.5.3 Technical Baseline Management

The Contractor shall define the configuration management (CM) processes in the SEMP, and shall implement and maintain the CM processes to control the configuration of technical baseline data and product configurations. The Contractor shall ensure the CM processes provide access to technical product data for authorized program participants. The Contractor shall ensure the CM processes identify document, and control the functional and physical characteristics of the system design; track any changes; provide an audit trail of program design decisions and design modifications. The Contractor shall maintain consistency of the system's attributes with its requirements and the evolving technical baseline over the life of the contract. The Contractor shall ensure their CM processes maintain compatibility with the government CM process. The Government shall have visibility into the configuration activities of all suppliers. (CDRL A010, Systems Engineering Management Plan (SEMP))

The Contractor shall establish a Configuration Status Accounting (CSA) process. The Contractor shall ensure the CSA process includes a contractor accounting system that includes:

• A record of approved configuration documentation and identification numbers

• The status of proposed Engineering Change Proposals (ECPs), change documents and deviations to the configuration

• The implementation status of approved changes (Class I or Class II)

The configuration of all hardware (units) and software of the configuration item in the operational inventory

2.5.3.1 Engineering Change Proposal (ECP)

The Contractor shall submit ECPs for changes to configuration items that impact Government controlled configuration documentation and Contractor managed baseline documentation. Unsolicited Class I ECPs are discouraged; however, at the discretion of the JMM BRU Procuring Contracting Officer, a Contractor-generated Draft Class 1 ECP may be submitted. All proposed changes shall require Government review and concurrence in classification. (CDRL A007, Engineering Change Proposal)

To facilitate Government determination of ECP classification, the Contractor shall submit a Preliminary Engineering Change Proposal (PECP) for all Contractor proposed changes. In order to expedite the change approval process, the Government shall have five working days from receipt of the PECP to notify the Contractor of the change classification decision. Proposed changes classified by the Government as Class II may be pursued by the Contractor upon receipt of the Government classification decision.

Proposed changes classified by the Government as Class I must be submitted via an ECP to the affected baseline and, if approved by the Government, incorporated into the contract prior to implementation.

Notwithstanding any other clause of the contract, no change to the specifications proposed by the Contractor in order to permit achievement of the contractual requirements shall entitle the Contractor to any increase in the unit prices, or to any extensions in the delivery schedule, neither shall disapproval by the Government of a proposed change entitle the Contractor to relief from meeting any contractual requirement.

For each Class I ECP, the Contractor shall assume that adequate ground and flight tests will need to be completed to verify system-level SPS compliance. Further, the Contractor shall be responsible for updating and distributing all system documentation as required to all users, to include technical manuals.

The required number and design of verification tests shall be commensurate with the potential impact of the proposed change on the weapon functional baseline and be subject to Government determination as part of the Government assessing the Class I ECP. The Contractor shall ensure changes are proposed in time to allow for review, approval, determination of testing, and conduct of testing prior to implementing the change.

2.5.3.2 Request for Deviation “Variance” (RFD)

The Contractor shall prepare RFDs. The Contractor shall classify each RFD as Minor, Major, or Critical corresponding to the classification characteristics specified below. The Contractor shall ensure that all units impacted by an RFD are identified by serial number, lot number, or similar identifier that allows identification of affected units.

• Critical – Category assigned if the variance consists of a departure involving safety or when the configuration documentation defining the requirements for the item classifies defects in requirements and the variance consists of a departure from a requirement classified as critical

• Major – Category assigned if the variance consists of a departure involving:

o Performance o Interchangeability, reliability, survivability, maintainability or durability of the item o Effective use or operation o Weight and size o Appearance o The configuration documentation defining the requirements for the item classifies defects in requirements and the variance consists of a departure from a requirement classified as major

• Minor – Category assigned if the variance consists of a departure which does not involve any of the factors listed as critical or major

(CDRL A008, Request for Deviation)

2.5.3.3 Notice of Revision (NOR)

The Contractor shall generate and submit NORs concurrently with Class I ECPs submitted to the Government for approval. The NOR shall include a From and To condition for all proposed document changes. (CDRL A009, Notice of Revision)

2.6 Systems Engineering

2.6.1 Systems Engineering and Technical Management

The Contractor shall design and develop the JMM BRU to meet the criteria in the JMM BRU SPS utilizing a systems engineering approach and process to balance system performance, ownership cost, schedule, and risk. The Contractor shall perform technical planning activities and establish systems engineering processes that are systematically applied, concurrent with the design activities, and traceable to the CWBS, IMP, and IMS. The Contractor’s technical planning shall include requirements, design, manufacturing, sustainment, verification, project planning, technical management and control, risk management, configuration management, and decision analysis.

2.6.2 Systems Engineering Management Plan (SEMP)

The Contractor shall implement the Systems Engineering activities necessary to design, develop, verify, produce, and sustain the JMM BRU system to meet the requirements of this contract. The Contractor shall document the systems engineering activities in a SEMP which is aligned with and supports the Government SEP provided as (Appendix 03) to this SOW. The Contractor’s SEMP is the Contractor’s overarching plan that outlines the Contractor’s approach for planning, controlling, and conducting a fully integrated engineering effort. The Contractor shall include the systems engineering activities in the IMP and IMS.

The Contractor’s SEMP shall include at a minimum, the following key elements:

• Requirements Analysis

• Functional Analysis

• Synthesis and Design

• System Analysis and Trade Studies

• Verification Approaches

• Requirements Management

• Requirements Traceability

• Technical Baseline Management

• Interface Management

• Data Management

• Risk Management

• Technical Performance Measurements (TPMs)

The Contractor’s SEMP shall include at a minimum, the following appendices:

• Software Development Plan

• Corrosion Prevention And Control Plan

• Reliability Program Plan

• Producibility Plan

• Anti-Tamper (AT) Plan

• Information Assurance (IA) Plan

• Modular Open Systems Architecture (MOSA) Plan

• Human Systems Integration (HSI) Plan

• Environment Safety Occupational Health (ESOH) Plan

• Hazardous Materials Management Program (HMMP) Plan

• Obsolescence and Diminishing Manufacturing Sources and Material Shortages (DMSMS)

Management Plan

• Modeling and Simulation (M&S) Plan

• Technology Maturation Plan

• Quality Assurance Plan

• Supply Chain Management Plan

The Contractor’s SEMP shall document the activities that the Contractor will utilize to ensure that performance, safety, reliability, software development, service life, human factors, ESOH, testability, logistics, and producibility are continuously addressed throughout the JMM BRU program and contract.

The Contractor shall include the systems engineering activities in the IMP and IMS. (CDRL A010, Systems Engineering Management Plan (SEMP))

2.6.3 Requirements Management

The Contractor shall establish, document, update, and maintain an electronic requirements management system to provide traceability between the Government's system performance requirements and verification requirements and the Contractor's allocated system, subsystem, and component performance and verification requirements. The Contractor shall identify traceability between requirements documents and other related technical planning documents including the System Performance Verification Plan (SPVP). The Contractor shall utilize Telelogic’s Dynamic Object Oriented Requirements System (DOORS). The Contractor shall review and brief the requirements traceability at all SETRs. The Contractor shall provide the Government with full access, through the Government’s existing internet browser capabilities, to read, analyze, and discuss the requirements held in the Contractor’s electronic requirements traceability and management system. The Contractor’s requirements traceability and management system shall provide requirement and requirement verification traceability and management t