Statement_of_Work_19Sep14_rev4.pdf

STATEMENT OF WORK (SOW)

FOR

AC/MC-130J RADIO FREQUENCY COUNTERMEASURES

(RFCM)

ENGINEERING, PRODUCTION, and SUSTAINMENT

19 September 2014

RELEASED BY:

AFLCMC/WNY

235 Byron Street, Suite 19A Robins Air Force Base, Georgia 31098-1670

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense (DoD) and United States DoD Contractors only to protect technical, operational or information data, or information from automatic dissemination under the international exchange program or by other means; determination date: 12 July 2014. This protection covers publications required solely for official use or strictly for administrative or operational purposes. Refer other requests for this document to AFLCMC/WNY, Air Force Life Cycle Management Center, Robins Air Force Base, Georgia 31098.

Destruction Notice - Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

PR FD2060-14-30015 Rev 4

Table of Contents

1 AC/MC-130J RADIO FREQUENCY COUNTERMEASURES (RFCM) PROGRAM

1.1 SCOPE

1.2 CONTRACT OBJECTIVES

1.3 CONTRACT STRUCTURE

2 APPLICABLE DOCUMENTS

3 EMD

3.1 EMD, SYSTEM DESIGN

3.1.1 RFCM Prime Mission Equipment

3.1.1.1 RFCM External Controls and Sustaining Engineering Planning

3.1.1.2 RFCM Software Design

3.1.1.2.1 Software Functional Qualification Test (SFQT)

3.1.1.3 RFCM Aircraft Interface and Compatibility Design

3.1.1.3.1 Electrical

3.1.1.3.2 Environmental Control

3.1.1.3.3 Airworthiness Certification

3.1.2 System Engineering

3.1.2.1 Human Factors Engineering

3.1.2.2 Interface Control Working Group (ICWG)

3.1.2.3 Technical Performance Measures (TPMs)

3.1.2.4 System Engineering Management Plan (SEMP)

3.1.3 Manufacturing Readiness Assessment (MRA)

3.1.4 Technology Readiness Assessment (TRA)

3.1.5 Critical Technology Demonstration (CTD)

3.1.6 Program Protection Planning (PPP)

3.1.6.1 Inspection and Audit

3.1.6.2 Cybersecurity

3.1.6.3 Anti-Tamper (AT)

3.1.6.4 Security

3.1.6.5 Security Classification Data

3.1.6.5.1 Safeguarding Classified Material

3.1.7 Antenna Study

3.1.8 Data Rights

3.1.8.1 Unlimited Rights

3.1.8.2 Government Purpose Rights

3.1.8.3 Limited or Restricted Rights

3.1.9 Lead Free Control Plan

3.1.10 Corrosion Prevention and Control Plan (CPCP)

3.1.11 Configuration Management (CM)

3.1.11.1 Data Accession List (DAL)

3.1.12 Program Management (PM)

3.1.12.1 Contractor Integrated Performance Management

3.1.12.2 Integrated Baseline Reviews (IBRs)

3.1.12.3 Status Reports

3.1.12.4 Contract Funds Status Report (CFSR)

3.1.12.5 Integrated Master Schedule (IMS)

3.1.13 Risk Management

3.1.14 Subcontractor/Supplier Management

3.1.15 Data Management

3.1.15.1 Data Repository

3.1.15.2 Government Furnished Data

3.1.15.2.1 Government Furnished Documentation (GFD)

3.1.15.2.2 Government Furnished Software (GFS)

3.1.15.2.3 Special Mission Processor (SMP) Interface Station

3.1.15.3 Acquired or Furnished Data

3.1.15.3.1 Contractor Acquired Property

3.1.15.3.2 Government Furnished Property (GFP) and Services

3.1.15.3.3 Government Property (GP) and Loss of GP Definition

3.1.15.3.4 Reporting Loss of Government Property

3.1.15.3.5 GFE / GFP / Management/GFI

3.1.16 Supply Chain Risk Management (SCRM) and Counterfeit Prevention

3.1.17 Reliability, Maintainability, and Supportability (RM&S)

3.1.17.1 Reliability Engineering

3.1.17.2 Supportability

3.1.17.3 Support Equipment (SE)

3.1.17.3.1 Peculiar SE

3.1.17.3.2 Common SE

3.1.17.3.3 Maintenance Test and SE

3.1.17.3.4 Common Aircraft Portable Reprogramming Equipment (CAPRE)

3.1.17.4 Integrated Logistics Support

3.1.17.4.1 Integrated Logistics Support (ILS) Management

3.1.17.4.2 Provisioning

3.1.17.4.3 Initial Spares and Repair Parts

3.1.17.4.4 Parts Obsolescence and Parts Management

3.1.17.5 Technical Manuals and Time Compliance Technical Orders (TCTO)

3.1.17.6 Unique Identification (UID)

3.1.17.7 Packaging & Marking

3.1.17.8 Transportation and Transportability

3.1.18 Safety

3.1.18.1 Environmental, Safety, and Occupational Health (ESOH)

3.1.18.2 System Safety

3.1.18.2.1 System Safety Program Plan (SSPP)

3.1.18.2.2 Safety Assessment Report (SAR)

3.1.18.2.3 Critical Safety Items (CSI)

3.1.18.3 Hazardous Material Management

3.1.18.4 Safety Review Board (SRB)

3.1.19 Quality Assurance (QA)

3.1.20 Green Procurement Program (GPP)

3.1.21 Voluntary Protection Program (VPP)

3.2 EMD, I&T (OPTION 1)

3.2.1 RFCM Hardware

3.2.1.1 Environmental Testing

3.2.2 RFCM Software

3.2.2.1 Software Development Tools Delivery

3.2.3 AC/MC-130J Platform Integration, Assembly, Test and Checkout

3.2.3.1 Weight and Balance

3.2.3.2 Electrical

3.2.3.3 Environmental Control

3.2.3.4 Avionics Integration, Test, and Checkout

3.2.3.5 Data Display and Controls

3.2.3.6 Airworthiness Certification

3.2.3.7 Electromagnetic Environmental Effects (E3) Program

3.2.3.8 AT Implementation

3.2.4 Integration and Test Reviews/Meetings/Working Groups

3.2.4.1 Integrated Test Team (ITT)

3.2.4.2 Technical Review Board (TRB)

3.2.4.3 TRR

3.2.4.4 OTRR

3.2.4.5 Training Equipment Working Group

3.2.5 Design Verification Test (DVT)

3.2.6 Other Aircraft Applicability

3.2.7 Test Requirements Documents (TRD)

3.2.8 Developmental Test (DT)

3.2.8.1 Test and Evaluation Support

3.2.8.2 Test Facilities

3.2.8.3 DT Modeling and Simulation (M&S)

3.2.8.4 DT/OT Test Instrumentation

3.2.8.5 Deficiency Reporting (DR)

3.2.9 Operational Test (OT)

3.2.9.1 PMAT

3.3 DATA RIGHTS

3.4 RFCM SYSTEM INTEGRATION LABORATORY (SIL)

4 PRODUCTION

4.1 LOW RATE INITIAL PRODUCTION (LRIP)

4.1.1 Site Training

4.2 FULL RATE PRODUCTION (FRP)

4.2.1 Manufacturing

4.2.1.1 Manufacturing Management

4.2.1.2 Manufacturing Readiness Assessments (MRAs)

4.2.1.3 Other Manufacturing

5 SUSTAINMENT

5.1 INTERIM CONTRACTOR SUPPORT (ICS)

5.2 DEPOT LEVEL ACTIVATION AND STAND-UP

5.2.1 Depot Maintenance Activation Planning (DMAP)

6 TECHNICAL DATA PACKAGE (TDP)

6.1 ENGINEERING DATA

6.1.1 Engineering Data Guidance Conference

6.1.2 In-Process Review (IPR)

6.1.3 Relationship of Contractor with Subcontractors/Vendors

6.1.4 Engineering Data Updates and Revisions

6.2 OTHER ENGINEERING DATA

7 APPENDICES

7.1 APPENDIX A: APPLICABLE DOCUMENTS

7.2 APPENDIX B: DATA ITEM DESCRIPTION (DID) LIST

7.3 APPENDIX C: ACRONYM LIST

List of Tables

Table 1 – Receive CTEs Table 2 – Transmit CTEs Table 3 – AFSOC Common SE List

1 AC/MC-130J Radio Frequency Countermeasures (RFCM) Program

1.1 Scope

The RFCM program will improve AC-130J and MC-130J aircraft system survivability and the capability to detect, identify, locate, deny, degrade, deceive, disrupt, and defeat threat systems in operational environments applicable to the AC/MC-130J missions. The contractor shall design, develop, integrate, test, manufacture, and sustain (through Interim Contractor Support [ICS]) an RFCM System (Group A and Group B) to satisfy the performance requirements defined in the “System Requirements Document (SRD) for AC/MC-130J RFCM” when installed on AC-130J and MC-130J aircraft. The RFCM statement of work (SOW) defines the efforts required to develop, test, produce, and sustain (through ICS) the RFCM system for United States Special Operations Command (USSOCOM).

1.2 Contract Objectives

The Government may award multiple contract(s) with multiple options to contractors that shall have the responsibility to manage, execute, and support the development, test, production, and sustainment of an RFCM system. The contracts and contract option types shall be aligned to meet the specific requirements of the contracts and options.

1.3 Contract Structure

The RFCM contract consists of Engineering and Manufacturing Development (EMD) followed sequentially by Production and Sustainment.

EMD: In EMD the contractor shall design and develop the RFCM system, complete full system integration, develop affordable and executable manufacturing processes, fabricate the system, and test and evaluate the system to include providing support during Government Developmental Test (DT) and Operational Test (OT). EMD is comprised of System Design (the basic contract) and Integration & Test (I&T) (Option 1). Production, including Low Rate Initial Production (LRIP) and Sustainment may be exercised prior to completion of EMD.

The requirements for EMD are delineated in paragraphs 3.1 (System Design) and 3.2 (I&T) of this Statement of Work. Paragraph 3.1 further delineates those requirements that must be complied with throughout the life of the Basic Contract and all Options.

System Design / Basic Contract: System Design is initiated with the award of the basic contract. The basic contract includes the system design with a Period of Performance (PoP) of 12 months and includes Critical Design Review (CDR). System Design shall include a Critical Technology Demonstration (CTD) in a requisite simulated threat environment. The Government may award up to two (2) contracts to initiate System Design.

Options

The contractor shall propose the following options to complete the RFCM program:

1. Option 1 (paragraph 3.2) shall be I&T and commences once a single contractor is downselected. I&T shall complete the remaining post-CDR activities and extend through completion of EMD.

2. Option 2 (paragraph 3.3) is an option for the Government to purchase no less than Government Purpose Rights (GPR) from the contractor for RFCM-related technical data that was developed exclusively at the contractor’s expense. This Option is only viable if the contractor has offered these rights for sale to the Government.

3. Option 3 (paragraph 3.4) shall consist of the design, development, assembly, and delivery of a System Integration Laboratory (SIL) to Robins Air Force Base (RAFB), GA.

Production: Initiated as Options at the discretion of the Government in conjunction with or upon completion of EMD. It includes options for Low Rate Initial Production (LRIP) and Full Rate Production (FRP):

1. Option 4 (paragraph 4.1) shall be LRIP.

2. Option 5 (paragraph 4.2) shall be FRP.

Sustainment: Initiated as Options at the discretion of the Government in conjunction with or upon the completion of Production. The RFCM Sustainment includes options for ICS, organic Depot stand-up/activation and delivery of a non-restricted Technical Data Package (TDP), and shall consist of all activities required to develop the capability to sustain fielded and installed RFCM Systems. The contractor shall propose the following Sustainment Options to complete a RFCM proposal / program:

1. Option 6 (paragraph 5.1) shall consist of ICS for a period of two (2) years following the first deployed installation of an RFCM equipped MC-130J aircraft.

2. Option 7 (paragraph 5.2) shall include all activities required to stand-up and activate an organic Depot-level support capability.

3. Option 8 (paragraph 6) shall be the delivery of the TDP and other engineering data to include the information required to enable organic, Government support, sustainment, and production of the RFCM system.

2 Applicable Documents See Appendix A.

3 EMD

EMD contains requirements for System Design and the I&T (Option 1) option of the RFCM Program. The deliverables contained in the Basic portion of the contract may extend over the entire life of the contract.

3.1 EMD, System Design

The contractor shall consider all the requirements during System Design, but the deliverable items may only be relevant to the downselected vendor.

Within the time constraints of the Basic contractual coverage, the contractor shall initiate those post CDR activities necessary to maintain schedule to the start of DT as required in SOW paragraphs 3.2.1, 3.2.2, and 3.2.3. The contractor shall order sufficient quantities of long lead items to assure that the government’s Line Replaceable Unit(s) (LRU)/Shop Replaceable Unit(s) (SRU) requirements during Trial Kit Installations (TKI), Design Verification Test (DVT), DT/OT, and qualification testing can be satisfied. The contractor shall submit a list of long lead items to the PCO for approval during the Systems Requirement Review. The government shall have approval / disapproval authority over the contractor’s long lead item list prior to purchase.

The contractor shall present a draft DD Form 1494 at all major design reviews (e.g. PDR, CDR).

3.1.1 RFCM Prime Mission Equipment

The contractor shall provide an RFCM system that meets or exceeds the RFCM System Specification (SS) requirements and must be a Technology Readiness Level (TRL) of 7 or higher, as defined in the DoD Technology Readiness Assessment (TRA) Guidance paragraph 2.5, at Functional Configuration Audit/Physical Configuration Audit (FCA/PCA). The contractor shall integrate the RFCM system such that it meets the capability requirements of the contractor developed RFCM SS. The RFCM SS shall be the basis for subsequent generation and development of the RFCM System/Subsystem Specification (SSS). The RFCM SSS shall be derived from, and shall be consistent with, the RFCM SS and shall be established at System Requirements Review and continually revised throughout the program. [A001, DI-IPSC- 81431A, System/Subsystem Specification (SSS)]

The SRD Geolocation requirement, SRD_756, is not intended to introduce a Geolocation capability if it is not, at proposal submission, already part of the contractor's starting technology foundation, discussed in the following paragraph; however, if it is part of the starting technology foundation, the contractor shall not remove the capability from the design.

The contractor shall design, develop, integrate, functionally check/verify, qualify, test, and deliver a fully capable RFCM System (Group A and Group B), associated Computer Software Configuration Items (CSCIs), any required peculiar Support Equipment (SE) and training (aircrew and maintenance). The contractor shall deliver a minimum of four (4) RFCM Systems that shall be installed on one (1) AC-130J aircraft and three (3) MC-130J aircraft. RFCM System Group B shall be identical between aircraft. Group A shall have maximum commonality between the aircraft.

The contractor shall utilize a starting technology foundation of hardware, software, and firmware that includes Critical Technology Elements (CTEs) identified in Table 1 and Table 2, each taken from a system having associated Technology Readiness Level (TRL) of seven (7) or higher.

CTEs shall be demonstrated per the 2nd column of Table 1 and Table 2 as further described in paragraph 3.1.5.

The contractor shall design, analyze, develop, integrate, test, and manufacture a flight certified (MIL-HDBK-516B Expanded) RFCM System (Group A and Group B) that satisfies the SSS, when installed on an AC-130J and a MC-130J aircraft.

Table 1 – Receive CTEs Receive CTE Pre-CDR

Demonstration Receive Sensitivity Yes Receive Dynamic Range Yes Direction finding (DF) No Field of Regard (FoR) No Polarization No Digital Radio Frequency Memory (DRFM) Yes Signal Identification , including algorithms/data in software/firmware

Yes

Table 2 – Transmit CTEs Transmit CTE Pre-CDR

Demonstration Effective Isotropically Radiated Power (EIRP) Yes Field of Regard (FoR) No Polarization No Countermeasures Generation, including algorithms/data in software/firmware

Yes

3.1.1.1 RFCM External Controls and Sustaining Engineering Planning The contractor shall develop a stand-alone RFCM control and display capability to support laboratory, flight testing and initial operational capability. The contractor shall deliver two (2) stand-alone RFCM control and displays (not-installed on aircraft) for engineering lab purposes and for use if SMP is not available. [A035, DI-SESS-81876, Interface Control Document (ICD)]

The Contractor shall design the RFCM hardware and develop associated data item deliverables to position the Government to accomplish in-house or contracted engineering change and repair to RFCM system hardware, to the component level, where “contracted” refers to contracted procurement that is not restricted to the Original Equipment Manufacturer (OEM). Note: this requires an approach to support a future enabling of in-house capability at the minimum.

3.1.1.2 RFCM Software Design

The contractor shall provide to the Government a current copy of their Software Development Plan (SDP) in accordance with (IAW) the Software Engineering Institute (SEI) Capabilities Maturity Model Integrated (CMMI) Version 1.3 Level III process areas.

[A009, DI-IPSC-81427A, Software Development Plan (SDP)]

The Contractor shall design the RFCM software and develop associated data item deliverables to position the Government to accomplish in-house (i.e. organic) engineering changes to all RFCM CSCIs and Mission Data Files (MDF) IAW AFI 10-703, Electronic Warfare Integrated Reprogramming (EWIR). In addition, the contractor shall comply with the Mission Data Generator (MDG) Technical Exhibit 201326571 requirements.

The contractor shall design, develop, and test CSCIs for:

1. RFCM

2. MDG

3. Post Mission Analysis Tool (PMAT) (see paragraph 3.1.15.3.5)

4. SIL and SE

5. MDTS

For each CSCI, the Contractor shall develop and deliver requirement specifications, design documents, product specifications, interface specifications, programming manuals, user’s manuals, and software version description documents. [A031, DI-IPSC-81433A, Software Requirements Specification (SRS)] [A033, DI-IPSC-81435A, Software Design Description (SDD)] [A032, DI-IPSC-81434, Interface Requirement Specification (IRS)] [B007, DI-IPSC- 81441A, Software Product Specification (SPS)] [B008, DI-IPSC-81442A, Software Version Description (SVD)] [A034, DI-IPSC-81436A, Interface Design Description (IDD)] [B006, DI- IPSC-81447A, Computer Programming Manual (CPM)] [B018, DI-IPSC-81437, Database Design Description (DBDD)] [B023, DI-MISC-80343, Multiplex Interface Control Document] [B009, DI-IPSC-81443A, Software User’s Manual (SUM)]

The contractor shall identify and document as CSCIs all RFCM software and memory-based firmware used or developed within this contract. All firmware shall be documented as software.

[B028, DI-IPSC-81448B, Firmware Support Manual (FSM)]

The contractor shall identify any commercial tools, including software development tools, needed to sustain and test the Mission Data Test Station (MDTS). The MDTS shall be delivered and installed in Det 1 AFSOAWC’s RAFB facility no later than 90 days prior to OT. The contractor shall develop and submit an Acceptance Test Procedure (ATP) for the MDTS. The MDTS shall be tested and the results documented. Discrepancies shall be corrected and a complete re-test of applicable, related functions shall occur. [B012, DI-NDTI-80603A, Test Procedure] [B013, DI-NDTI-80809B, Test/Inspection Report]

The contractor shall design, develop, test and produce the MDTS to support the RFCM reprogramming functions in compliance with MDTS Technical Exhibit 201326572 requirements.

The contractor shall develop any models and simulations required to support design efforts, verification testing and DT/OT substantiation. The Government shall have unlimited rights in all technical data and computer software for all models and simulations and their derivations that are funded exclusively with Government funds. The Government shall have government purpose rights in all technical data and computer software for all models and simulations and their derivations that are funded with a mix of Government funds and contractor funds. All models and simulation shall be delivered with documentation and data rights. [B001, DI-MCCR- 80700/T, Computer Software Product End Items] [B022, DI-TMSS-80527C, Commercial Off- The-Shelf (COTS) Manuals and Associated Supplemental Data]

3.1.1.2.1 Software Functional Qualification Test (SFQT)

The contractor shall develop software plans, procedures and descriptions as necessary to perform software verification testing on the CSCIs to include Functional Testing, Regression Testing, Integration Testing, Performance Testing, and Acceptance Testing. The Contractor shall execute the Government approved plans and procedures and provide test reports.

The contractor shall notify the Government when they will perform a Software Verification Review (SVR) and provide the Test Descriptions and Acceptance Test Procedures. See paragraph 3.1.2 for general data requirement deliveries (Agenda, Minutes, Presentation) associated with meetings, reviews, and working groups. [B017, DI-IPSC-81438A, Software Test Plan] [B012, DI-NDTI-80603A, Test Procedure] [B010, DI-IPSC-81439A, Software Test Description] [B011, DI-IPSC-81440A, Software Test Report]

3.1.1.3 RFCM Aircraft Interface and Compatibility Design

The Contractor’s RFCM System, as designed, shall interface with AC/MC-130J RF receivers and RF transmitters in the RFCM frequency range, including the MC-130J Common Terrain Following/Terrain Avoidance (MCTF), and Programmable Interference Blanker Unit (PIBU), as appropriate, to provide mutual look-through and/or blanking for all aircraft systems. This allows for direct connection between the RFCM and other receivers and transmitters for blanking, and/or allows for use of the PIBU. The Contractor shall integrate with the PIBU as needed to meet SOW and RFCM SSS requirements and shall document the interface requirements in a Technical Report-Study/Services report. [B019, DI-MISC-80508B/T, Technical Report- Study/Services]

The contractor shall design the RFCM System to ensure that there is minimal Electromagnetic Interference (EMI)/Electromagnetic Compatibility (EMC) interferences between RFCM and onboard systems and between RFCM and offboard systems that would degrade mission effectiveness.

The Contractor’s RFCM System, as designed, shall interface directly with the AN/ALE-47 Countermeasures Dispenser System to initiate dispensing.

3.1.1.3.1 Electrical

The contractor shall design all electrical subsystem changes required to satisfy the RFCM requirements IAW MIL-E-7016F. The contractor shall analyze and document any impacts to the AC-130J and MC-130J aircraft electrical load. [A020, DI-MISC-80508B/T, Technical Report- Study/Services]

3.1.1.3.2 Environmental Control

The contractor shall analyze and document the impacts to the aircraft Environmental Control Systems (ECS) created by the installation of the RFCM in the AC-130J and MC-130J aircraft. .

[A020, DI-MISC-80508B/T, Technical Report-Study/Services]

3.1.1.3.3 Airworthiness Certification

The contractor shall develop, implement, and deliver an airworthiness certification program plan for the RFCM program. The program plan shall comply with USAF policy on airworthiness certification as defined in MIL-HDBK-516B Expanded. The contractor shall use AFI 62-601 AFMC Supplement 1, MIL-HDBK-516B Expanded, and Airworthiness Bulletins (AWBs)

AWB-002, AWB-003A, AWB-004A, AWB-005, AWB-006, AWB-007, AWB-008, AWB-009,

AWB-013A, and AWB-015A as guides. [A036, DI-MGMT-80004A, Management Plan] The contractor shall document and provide an Airworthiness Specification (Modification Airworthiness Certification Criteria (MACC)). The contractor shall identify and provide rationale for all criteria identified in the Airworthiness Specification as being non-applicable.

The contractor shall tailor, if needed, the Method of Compliance to provide an accurate verification/compliance description of their approach. [B025, DI-SESS-81766, Airworthiness Specification]

The contractor shall provide an Airworthiness certification Criteria Report addressing their airworthiness compliance results and all substantiating compliance artifacts required for Military Flight Release for the AC-130J and MC-130J installations of RFCM. [B024, DI-SESS-81768, Airworthiness Certification Criteria Report]

The contractor shall include substantiating compliance artifacts’ development and delivery in the program Integrated Master Schedule (IMS).

3.1.2 System Engineering

The contractor shall conduct the technical and management tasks of directing and controlling an integrated engineering effort for the RFCM Program. The contractor, with mutual Government agreement, shall specify the number of technical meetings/reviews required. All meetings/reviews shall be held at Robins Air Force Base (RAFB). Using MIL-STD-1521B as a guide, the contractor shall plan, conduct, and support all program technical reviews including Certification Working Group (CertWG), Threat Working Groups (TWGs), Technical Interchange Meetings (TIMs), Human Factors Working Groups (HFWGs), Program Management Reviews (PMRs), System Requirements Review, Software Requirements Review, Software Specification Review (SSR), System and Software Preliminary Design Reviews (PDRs), System and Software CDRs, System Security Working Groups (SSWGs), FCA/PCA, In-Process Reviews (IPRs), Integrated Test Team (ITT), Technical Review Board (TRB), Safety Review Board (SRB), Guidance Conference, Test Readiness Review (TRR), Flight Readiness Review (FRR), Operational Test Readiness Reviews (OTRR), etc. The contractor shall establish entrance and exit criteria for Government approval for each review. The entrance and exit criteria shall be provided to the Government prior to the review.

The contractor shall provide agendas, minutes and presentation material to include, but not limited to, audits, technical interchange meetings, program management reviews, and technical working groups. As requested by the Government, the Contractor shall produce the Agenda, Minutes, and Presentation Material for the specified review meeting or working group. These data items are delineated once for the convenience of the Government, but are applicable to each and every gathering specified in the basic contract and all executed options. [A005, DI-ADMN-

81249A, Conference Agenda] [A006, DI-ADMN-81250A, Conference Minutes] [A007, DI- ADMN-81373, Presentation Material]

3.1.2.1 Human Factors Engineering

The contractor shall conduct HFWG meetings and evaluations to investigate integration issues.

The contractor shall address all human factors requirements with respect to the RFCM design for operations and maintenance IAW MIL-STD-1472G as a guide. The contractor shall report all areas of non-compliance with MIL-STD-1472G to the Government. The contractor shall conduct work load analysis to demonstrate the crew station man-machine interface(s) and shall present the findings at HFWG meetings.

The contractor shall employ Human Factors Engineering and Human Systems Integration best practices as an integral part of systems engineering to optimize system performance and reduce technical and performance risk

3.1.2.2 Interface Control Working Group (ICWG)

The contractor shall conduct an ICWG to discuss and refine system and subsystem on-board and off-board interface requirements supporting RFCM integration.

3.1.2.3 Technical Performance Measures (TPMs)

The Contractor shall maintain and track TPMs in accordance with the RFCM System Engineering Management Plan (SEMP). The TPMs shall be briefed at both the PDR and CDR within System Design. See paragraph 3.1.2 for general data requirement deliveries (Agenda, Minutes, Presentation) associated with meetings, reviews, and working groups.

In the CDR presentation material, the Contractor shall identify specific material that has a relationship to RFP FA8540-14-R-30015, Section M-901 Final Downselect, RFCM I&T Engineering Subfactor criteria IAW paragraph 3.1.2.

3.1.2.4 System Engineering Management Plan (SEMP)

The contractor shall develop a 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. [A004, DI-SESS-81785, Systems Engineering Management Plan (SEMP)]

3.1.3 Manufacturing Readiness Assessment (MRA)

The contractor shall conduct an MRA 90 days after CDR. The contractor shall use results of the MRAs to develop and execute planning to resolve all identified industrial resources shortfalls including trained and certified touch-labor employees. Risks and mitigation actions shall be addressed within applicable manufacturing planning documents and the contractor’s Risk Management Plan (RMP). [A019, DI-MGMT-81808, Contractor’s Risk Management Plan]

3.1.4 Technology Readiness Assessment (TRA)

The contractor shall develop and conduct a TRA of the RFCM System components. Preliminary results of the TRA shall be presented at PDR, an updated version presented at CDR and a final document report provided at the Manufacturing Readiness Assessment (MRA)., The contractor shall provide a maturation plan that shows a roadmap for the RFCM System to reach TRL 7 or higher by Milestone C. The contractor shall support integration of its TRA results into the Government’s TRA process to support the Government’s Milestone C process. [A020, DI- MISC-80508B, Technical Report - Study/Services]

3.1.5 Critical Technology Demonstration (CTD)

The contractor shall participate in a demonstration in a designated Government facility (e.g.

laboratory) to permit early assessment of technology maturity and functional capabilities in support of technical reviews. The CTD shall be conducted IAW the RFCM CTD Plan. The demonstration shall be conducted prior to RFCM CDR. The demonstration shall be planned and conducted by the Government in a Government designated facility. (For planning purposes, consider Wright-Patterson AFB as the demo site.)

The Contractor shall provide support to the Government for development of the detailed demonstration procedures and conducting the laboratory demonstration.

For each CTE in Table 1 and Table 2 (paragraph 3.1.1) identified as being required to be demonstrated in laboratory testing, the Contractor shall deliver hardware/software/firmware in support of Government CTE evaluation. The Contractor is permitted to make any configuration changes needed to the Contractor CTEs to achieve compatibility of technologies to be demonstrated. CTEs delivered/brought to the demonstration can be included or hosted within other hardware not defined by the Contractor as part of the CTE.

3.1.6 Program Protection Planning (PPP)

The contractor shall develop and implement a PPP, for the RFCM system, as required by Air Force Pamphlet (AFPAM) 63-113, PPP for Lifecycle Management; DoD Instruction 5200.39 change 1, Critical Program Information (CPI) Protection Within the Department of Defense;

DoD Instruction 5200.44, Protection of Mission Critical Functions to Achieve Trusted Systems and Networks (TSN) and the Program Protection Plan. [A015, DI-MGMT-80004A, Management Plan]

The contractor shall support the Government in the development and maintenance of a PPP to include System Functional Decomposition, Criticality Analysis, CPI/CC identification, and countermeasure development. This support shall include identification of Program Protection points of contact, identification of Program Protection schedule events, identification of additional CPI not previously identified by the Government, identification of measures being taken to protect CPI and identification of unique Program Protection costs.

3.1.6.1 Inspection and Audit

The contractor shall support Government-led reviews and assessments of Information Assurance (IA) and Program Protection areas of concern in all contractor and subcontractor facilities as needed to ensure compliance with published requirements and protection measures.

3.1.6.2 Cybersecurity

The contractor shall implement an Information Assurance (Cybersecurity) program and provide technical support to assist the Government in complying with the instructions and guidance in the Chairman of the Joint Chiefs of Staff Instruction (CJCSI) 6510.01F, Information Assurance (IA) and Support to Computer Network Defense (CND); Department of Defense Instruction (DoDI) 8500.01, Cybersecurity; DODI 8510.01, Risk Management Framework for DoD Information Technology, Air Force Life Cycle Management Center (AFLCMC) Standard Process Platform Information Technology (PIT) Certification and Accreditation (C&A); Air Force Instruction (AFI) 33-210, Air Force Certification and Accreditation Program (AFCAP);

and AFI 33-210, AF Guidance Memorandum 2 (AFGM2), AF Guidance Memorandum to AFI 33-210, Committee on National Security Systems (CNSS) Instruction 1253,Security Categorization and Control Selection for National Security Systems, and the applicable security and privacy controls in the National Institute of Standards and Technology (NIST) Special Publication 800-53 Revision 4, Security and Privacy Controls for Federal Information Systems and Organizations to complete Cybersecurity C&A.

Prior to each System Requirements Review (SRR), PDR and CDR, the contractor shall conduct SSWG meetings. The SSWGs establish security controls for RFCM, baseline the security requirements and identify the supporting artifacts IAW NIST SP 800-53R4, and other DoD, USAF, and AFLCMC guidance to assess program risk in support of the C&A. See paragraph

3.1.2 for general data requirement deliveries (Agenda, Minutes, Presentation) associated with meetings, reviews, and working groups. [A012, DI-MGMT-80368A/T, Status Report]

The contractor shall prepare and deliver a preliminary and final Cybersecurity Assurance Assessment Report of the RFCM based on the SSWG finalized security controls and requirements. [A013, DI-MGMT-81845, IA Design Review Information Package (DRIP)] [A014, DI-MGMT-81844, IA Test Plan]

3.1.6.3 Anti-Tamper (AT)

The contractor shall develop and deliver an Anti-Tamper Protection Plan for Critical Program Information and Technologies. The contractor shall follow the following process in preparing the plan.

1. The contractor shall identify CPI/CC in accordance with the DoD 6-step CPI/CC process provided as Government Furnished Information (GFI), and submit a list of recommended CPI/CC with rationale and an Anti-Tamper strategy/plan for review at the SRR for Government approval.

2. The Government will provide a final CPI/CC list to the contractor as GFI. The contractor shall develop and implement an Anti-Tamper Plan in accordance with DoDI 5200.39 using the DOD Anti-Tamper Template, provided as GFI. The contractor will submit an initial Anti-Tamper Plan 30 days prior to RFCM hardware PDR for Government approval.

3. If implemented, the contractor shall update the Anti-Tamper Plan (Final Anti-Tamper Plan), to include a Verification and Validation (V&V) Plan, 30 days prior to RFCM hardware CDR for Government approval.

[A020, DI-MISC-80508B/T, Technical Report-Study/Services]

3.1.6.4 Security

The contractor shall establish and maintain a security program to satisfy the requirements of the Government provided Contract Security Classification Specification, DD Form 254 and IAW DoDI 5000.02 Interim, Operation of the Defense Acquisition System, Enclosure 3, paragraph 13, Program Protection and AFP 63-113, Program Protection Planning for Life Cycle Management, Chapter 3, Program Protection Requirements.

The contractor shall comply with the provisions of the National Industrial Security Program Operating Manual (DoD 5220.22-M Change 1). National Agency Checks (NACs) up to level(s) specified by DD Form 254 shall be conducted for all personnel having access to classified hardware or data IAW DoD 5200.2–R. The contractor shall be responsible for obtaining employee security clearances to the access level required for proper accomplishment of contract requirements. The Contractor’s inability to obtain proper employee security clearances shall not constitute an excusable delay in contract performance.

The contractor shall obtain and/or maintain clearance of their facility by Defense Security Services (DSS) to receive and generate classified information and hardware through the level(s) specified by DD Form 254. The contractor shall have or obtain a DoD Activity Address Code (DoDAAC) capable of receiving classified hardware and data.

3.1.6.5 Security Classification Data

The contractor shall identify changes, if necessary, to the RFCM Security Classification Guide (SCG). The contractor shall prepare the information IAW AFI 31-401, Information Security Program Management. [A020, DI-MISC-80508B, Technical Report - Study/Services]

3.1.6.5.1 Safeguarding Classified Material

The contractor shall ensure all technical documents developed under this effort are properly marked with Distribution Statements IAW the applicable Defense Department (DD) Form 1423 and AFI 61-204 and conform to the RFCM SCG and DD Form 254.

3.1.7 Antenna Study

The contractor shall conduct a study on each aircraft (AC-130J, MC-130J) to determine the most effective antenna types and mounting positions. The contractor shall consider typical aircraft flight attitudes and minimize impact to aircraft structure, interference with other aircraft systems while maximizing system effectiveness. This analysis shall, at a minimum, include an investigation of wider field of view antennas, selectable steerable antenna angles, and multiple antennas.

[A020, DI-MISC-80508B/T, Technical Report-Study/Services]

3.1.8 Data Rights

The RFCM system (Group A and Group B) is a non-commercial defensive system based on critical technology technical data with military application. DFARS 252.227-7013 and DFARS 252.227-7014 apply.

In the event it is necessary for the Contractor to purchase licenses to third party software using contract funds in order to fulfill its obligations under the contract, the Contractor shall deliver those licenses to the Government. The Government's rights in such software will be determined by the provisions of those license agreements. If any licenses include a transfer clause for unused license term, then the Contractor shall transfer the remaining license period to the Government.

The Contractor shall not mark briefings, reports, drawings, technical data, non-commercial computer software and non-commercial computer software documentation, or other types of data, to include contract deliverables, with trade secret markings, proprietary markings, or any other markings that would violate DFARS 252.227-7013(f), DFARS 252.227-7014(f), or DFARS 227.7103-9. Deliveries of data, documentation, computer software and computer software documentation with restrictive markings prohibited by this SOW will be rejected on delivery, and the delivery will be counted as not occurring.

3.1.8.1 Unlimited Rights

The Government shall have unlimited non-exclusive rights in all RFCM SOW CDRLs, hardware, technical data, computer software, and computer software documentation developed under this contract exclusively with Government funds. The Government shall have unlimited non-exclusive rights in, and the contractor shall deliver all RFCM SOW CDRLs, hardware, technical data, computer software, and computer software documentation developed under any previous Government contract exclusively with Government funds which are necessary to fulfill the requirements of this contract.

3.1.8.2 Government Purpose Rights

The Government shall have Government Purpose Rights in all RFCM SOW CDRLs, hardware, technical data, computer software, and computer software documentation developed under this contract with mixed funding. The Government shall have Government Purpose Rights in, and the contractor shall deliver all RFCM SOW CDRLs, hardware, technical data, computer software, and computer software documentation developed under any previous Government contract with mixed funding which is necessary to fulfill the requirements of this contract.

3.1.8.3 Limited or Restricted Rights

The Government shall have Limited Rights or Restricted Rights in, and the contractor shall deliver all RFCM SOW CDRLs, hardware, technical data, computer software, or computer software documentation previously developed exclusively at private expense.

3.1.9 Lead Free Control Plan

The contractor shall develop a Lead-Free Control Plan and implement a lead-free program for all RFCM Group A, Group B, and SE that eliminates Tin Whiskers and other deficiencies created by the use of lead-free solder and components. The contractor shall utilize the soldering and re-tinning processes identified in paragraph 6.2.3 and associated Table 1 of “Warner Robins Air Logistics Center (WR-ALC) Lead-Free Control Plan”, GEIA-STD-0005-2-A Rev A, “Standard for Mitigating the Effects of Tin Whiskers in Aerospace and High Performance Electronic Systems” and GEIA-STD-0005-1-A,“Performance Standard for Aerospace and High Performance Electronic Systems Containing Lead-Free Solder.” [A022, DI-MGMT- 81772, Lead Free Control Plan]

3.1.10 Corrosion Prevention and Control Plan (CPCP)

The contractor shall develop and maintain engineering and technical data for corrosion-related materials and processes for the RFCM within the contractor’s CPCP and aircraft technical orders. [A018, DI-MFFP-81403, Corrosion Prevention and Control Plan]

3.1.11 Configuration Management (CM)

The contractor shall develop and maintain a Configuration Management Plan (CMP) to control all aspects of the CM process using MIL-HDBK-61A. Contractor shall use ANSI/EIA-649 as a guide. The CMP shall include an event based criteria for assumption of control of the CM process following acceptance by the Government of documents, designs or requirements. The CMP shall include responsibilities for configuration identification, change control, data management, deviations/waivers, audit plan, audits, status accounting, interface management and subcontractor management.

The contractor shall establish a process to assure that configuration control is maintained on the system, and in functional, allocated and product baseline configuration identification documentation. The contractor shall provide agendas, briefing documentation and minutes to include, but not limited to, audits, technical interchange meetings and program management reviews. The contractor shall provide Configuration Status accounting information. See paragraph 3.1.2 for general data requirement deliveries (Agenda, Minutes, Presentation) associated with meetings, reviews, and working groups.

The contractor shall designate a CM representative to serve as a primary point of contact to the Government for all CM matters and be responsible for any subcontractor CM efforts. The contractor shall notify the Government of any changes which affect the contractor’s established CM process. [A030, DI-CMAN-80858B, Configuration Management Plan] [A011, DI-CMAN- 81253A, Configuration Status Accounting Information] [A010, DI-CMAN-80640C, Request for Deviation]

The contractor shall identify system hardware and software recommendations for designation as CIs and CSCIs and provide recommendations to the Government for review and concurrence.

Any configuration changes after CDR, but before FCA/PCA, must be approved by the government prior to implementation. Any change prior to FCA/PCA shall be considered developmental and not subject to the formal Government Engineering Change Proposal (ECP)/ Specification Change Notices (SCNs)/Notice of Revision (NOR) process. The contractor shall prepare ECPs, SCNs, and NORs when directed by the Government. Any change after FCA/PCA which affects the form, fit, function, or interface, shall be prepared as an ECP. The contractor shall submit Class I ECPs to the Government for review and approval; Class II ECPs shall be submitted to the Government for review. Upon [E007, DI-CMAN-80639C, Engineering Change Proposal] [E008, DI-CMAN-80643C, Specification Change Notice (SCN)] [E018, DI-CMAN- 80642C, Notice of Revision (NOR)]

The contractor shall prepare and submit SCNs for Government approval concurrent with the preparation of an ECP for each specification to be revised upon ECP approval. The contractor shall mark prime contractor technical data with the appropriate distribution statements IAW marking criteria established in applicable Contract Data Requirements List (CDRL) exhibit general instructions and shall direct subcontractors to follow the same requirements.

Approved/accepted ECPs shall be incorporated into the production baseline definition.

An FCA will be conducted to verify the functional and allocated baselines of capabilities of the RFCM system. An Initial PCA and Final PCA will be conducted to verify the RFCM configuration. A joint FCA and PCA plan shall be developed utilizing MIL-HDBK-61A, Section 8 as a guide. Defense Contract Management Agency (DCMA) will be utilized as needed to support configuration audits. Prior to each delivery, an audit/inspection will be conducted to verify the configuration of each configuration item against the production configuration and applicable documentation. Deliveries prior to completion of OT will be delivered via a conditional DD Form 250. The Government will conduct periodic Operational Safety, Suitability and Effectiveness (OSS&E) audits of fielded aircraft to ensure configuration integrity of the aircraft and commodity documentation, compliance with the operational support requirements and completeness and adequacy of OSS&E baseline documentation (to include certifications) and requirements. See paragraph 3.1.2 for general data requirement deliveries (Agenda, Minutes, Presentation) associated with meetings, reviews, and working groups. [E009, DI-SESS-81646, Configuration Audit Plan]

3.1.11.1 Data Accession List (DAL)

The contractor shall maintain a current listing of all non-CDRL data generated in performance of the contract in a DAL electronic information system accessible by the Government. All documentation and any data generated in performance of this program shall be listed on the DAL. Any item listed on the DAL shall be provided to the Government upon Government request. Internally generated data shall be initially marked with the contract number, without requiring a separate marking effort after data is requested by the Government. DAL data shall include all drawings, records, software, and data (that was not delivered under a CDRL) whether or not developed under a Government contract required for repair, modification, or contracted procurement of the RFCM Group A or Group B without being restricted to the OEM. The Contractor shall levy on subcontractors and sub-vendors the same requirements for the DAL as are levied on them by this contract. This requirement shall apply at all tiers of subcontractor/vendor levels associated with the program. The Contractor shall identify to the Government any DAL limitations due to restricted or limited data rights associated with subcontractor/vendor subsystem/component design. [A021, DI-MGMT-81453A, Data Accession List]

3.1.12 Program Management (PM)

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

The contractor shall support the Government acquisition reviews, milestones, and associated documentation required by DoDI 5000.02 Interim. This support is exclusive of other tasks covered elsewhere in this SOW.

The contractor shall participate in a Post Award Conference, within thirty (30) days of contract award.

The requirements for contractor travel are as follows:

1. The contractor shall travel as required in support of this contract. Travel will only be reimbursed for travel to and from Government test events and meetings.

2. In the case of contractor travel involving 4 or more persons, the contractor shall provide the following information to the Procurement Contracting Officer (PCO) at least five (5) business days prior to planned travel: names of travelers, travel dates, purpose for travel, duration of the trip, cost estimate, and an itinerary.

3. The Joint Federal Travel Regulation (JFTR) shall be used as a guide for determining acceptable costs.

4. No First Class or Business Class travel is authorized at Government expense.

5. Travel reimbursement shall be IAW the General Services Administration (GSA)

Continental United States per diem travel rate schedule.

6. The contractor shall report all incurred travel cost data in trip reports.

3.1.12.1 Contractor Integrated Performance Management

The contractor shall establish, maintain, and use in the performance of this contract, an integrated performance management system. Central to this integrated system shall be a validated Earned Value Management System (EVMS) in accordance with Defense Federal Acquisition Regulation Supplement (DFARS) 252.234-7001, DFARS 252.234-7002, and the EVMS guidelines contained in ANSI/EIA-748. To establish the integrated performance management system, the EVMS shall be linked to and supported by the contractor’s management processes and systems to include the integrated master schedule, contract work breakdown structure, change management, material management, procurement, cost estimating, and accounting. The correlation and integration of these systems and processes shall provide for early indication of cost and schedule problems, and their relation to technical achievement [A008, DI-MGMT-81861, Integrated Program Management Report (IPMR)]

3.1.12.2 Integrated Baseline Reviews (IBRs).

The contractor shall engage jointly with the Government’s program manager in Integrated Baseline Reviews (IBRs) to evaluate the risks inherent in the contract’s planned performance measurement baseline. Initially, this shall occur as soon as feasible, but within 60 days of the exercise of Option 1, I&T, and subsequently following all major changes to the baseline. Each IBR should verify that the contractor is using a reliable performance measurement baseline, which includes the entire contract scope of work, is consistent with contract schedule requirements, and has adequate resources assigned. Each IBR should also record any indications that effective Earned Value Management (EVM) is not being used. IBRs should also be conducted on subcontracts that meet or exceed the EVM application threshold. The prime contractor shall lead the subcontractor IBRs, with active participation by the Government. (See

DFARS 252.234-7002)

3.1.12.3 Status Reports

The contractor shall generate and submit a monthly…