Statement_of_Work.pdf

JTE FA8210-18-R-5000

Attachment 1 - SOW

18 Jan 2018

STATEMENT OF WORK

Joint Threat Emitter (JTE) Enhanced Delivery Initiative (JEDI)

Revision A

Prepared by:

AFLCMC/HBZCB

6057 Box Elder Lane, Bldg. 1285

HILL AIR FORCE BASE, UTAH 84056

18 Jan 2018

Revision Record Revision Date Description Pages

A 18 Jan. 2018 Initial SOW 60

18 Jan 2018

Table of Contents

1 PROGRAM BACKGROUND

2 SCOPE

3 APPLICABLE DOCUMENTS

4 REQUIREMENTS

Program Management

Program Manager (PM)

Monthly Status Report

Contract Funds Status Report (CFSR)

Integrated Management Plan (IMP)

Integrated Master Schedule (IMS)

Meetings, Reviews, and Conferences

Configuration Management Plan (CMP)

Configuration Audit Plan

Data Management

Technical Orders (TO)

Risk Management

Government Contract Management

Government Furnished Property (GFP)

Systems Engineering

Security

Diminishing Manufacturing Sources and Material Shortages (DMSMS) Monitoring:

End-Items

FC2U

MC2U, TEU, and WTEU

Systems Design

Foreign Military Sales (FMS)

Site Survey(s)

Qualification Testing

First Article Testing

End-Item Production Testing

Line Replaceable Unit (LRU) Testing

Computer Software Configuration Item Testing

Bench Level Integration Testing

Factory Acceptance Test (FAT)

Environmental Testing

Electromagnetic Interference/Electromagnetic Compatibility (EMI/EMC)

Vibration/Mobility Testing

Site Acceptance Testing (SAT)

Foreign Military Sales (FMS) Site Acceptance Testing (SAT)

Reliability

Software Development Station (SDS)

Retrofit Kits

Spares & Support Equipment

Spares Delivery

Support Equipment

Engineering Change Proposal (ECP)

Class I ECPs Approval Process

Class II ECPs Approval Process

Requests for Variance (RFV)

Specification Change Notices (SCN)

ECP Labor

Test Items Associated with ECPs

Contents of an ECP

Software Changes

Travel

Packaging, Handling, Shipping, and Transportation (PHS&T)

Documentation

Electrostatic Material Packaging

Hazardous Material

Export Licenses

Training

Course Materials Updates

Training Team

Training Facility and Additional Support

Initial User Training

Advanced User Training

5 SERVICES SUMMARY

6 CDRL LIST

List of Tables

Table 1. Applicable Documents Table 2. JTE Nominal Computer Software Configuration Item Structure Table 3: Potential SAT Locations

List of Acronyms and Symbols

AAA Anti-Aircraft Artillery

ACO Administrative Contracting Officer

AIS Automated Information System

ARO After Receipt of Order

ATO Authority to Operate

C2U Command and Control Unit

CCB Configuration Control Board

CDRL Contract Data Requirements List

CFR Code of Federal Regulations

CM Configuration Management

CMP Configuration Management Plan

CONUS Contiguous United States

CSCI Computer Software Configuration Item

DAL Data Accession Lists

EIA Electronic Industries Association

EMI Electromagnetic Interference

EW Electronic Warfare

ECP Engineering Change Proposal

FAT Factory Acceptance Test

FC2U Fixed Command and Control Unit

FCA Functional Configuration Audit

FFP Firm Fixed Price

FMS Foreign Military Sales

GFI Government Furnished Information

GQAR Government Quality Assurance Representative

HMMP Hazardous Material Management Plan

IADS Integrated Air Defense System

IUID Item Unique Identification Data

IMP Integrated Master Plan

JTE Joint Threat Emitter

JTE-FO Joint Threat Emitter Follow-on

KPP Key Performance Parameters

KSA Key System Attributes

LRU Line Replaceable Unit

MC2U Mobile Command and Control Unit

MRL Manufacturing Readiness Level

OCONUS Outside the Contiguous United States

OSHA Occupational Safety and Health Administration

PCA Physical Configuration Audit

PCO Procurement Contracting Officer

POP Period of Performance

PTD Provisioning Technical Documentation

QA Quality Assurance

RFV Requests for Variance

SAT Site Acceptance Test

SDD Signal Definition Document

SDFP Supplemental Data for Provisioning

SDS Software Development Station

SPS System Performance Specification

STIG Security Technical Implementation Guides

SVD Software Version Description

TDP Technical Data Package

TEU Threat Emitter Unit

TIM Technical Interchange Meeting

TO Technical Order

TRR Test Readiness Review

WTEU Wideband Threat Emitter Unit

1 PROGRAM BACKGROUND

The Joint Threat Emitter (JTE) program provides advanced Electronic Warfare (EW) threat simulators that provide replication of Surface–to-Air Missile (SAM) and Anti-Aircraft Artillery (AAA) threats for aircrew training. The JTE provides improved training capability and is intended to replace aging legacy EW training equipment, which have become obsolete and costly to maintain. The JTE consists of a Threat Emitter Unit (TEU), and a Command and Control Unit (C2U). Two variants of the TEU exist, namely the Standard TEU, sometimes referred to as a Kit 1, and the Wide Band TEU (WTEU). Two variants of the C2U exist, namely the Mobile C2U (MC2U), and the Fixed C2U (FC2U). Previous Air Force and Navy contracts have fielded nineteen TEUs, three MC2Us, ten FC2Us, and two WTEUs. The JTE provides an Integrated Air Defense System (IADS) either as a self-controlled network or integrated with other threat systems on the range. The JTE is reliable, mobile, affordable, re-programmable, modular, remotely operated, easily maintained, and operated with a minimum amount of manpower.

2 SCOPE

The scope of this contract includes but is not limited to production, testing, and delivery of JTE Follow-on (JTE-FO) baseline FC2U, MC2U, TEU, and WTEU end-items; original production (referred to as Legacy JTE) JTE FC2U, MC2U, TEU, and WTEU retrofit kits; Spares and Support Equipment procurement; Engineering Change Proposals (ECPs) including Software Changes, Training and Travel. End-items (for the purpose of this SOW) are defined as FC2U, MC2U, TEU, and WTEU. Additionally, the scope of this contract includes Foreign Military Sales (FMS) and US Government procurement and delivery. Retrofit kits shall ensure that the US Government can create and maintain a single system configuration across the entire US JTE fielded fleet. If First Article Testing is ordered, each end-item undergoing First Article Testing shall be validated by the Government to ensure compliance with system design and system performance requirements. The Government will provide a technical data package as Government Furnished Information (GFI) for use by the Contractor to produce the approved JTE-FO design and procure approved JTE-FO initial spares and retrofit kits. The Contractor shall demonstrate through performance testing that the production systems meet performance requirements. The Contractor shall ensure conformance to system performance requirements for all spares ordered under this contract. Item Unique Identification Data (IUID) shall be adhered to by the Contractor; items shall be marked in accordance with (IAW) IUID standards, and IUID marking information shall be entered into the Government IUID database (Wide Area Work Flow) and delivered in a marking report. (CDRL A043, A044)

3 APPLICABLE DOCUMENTS

Table 1. Applicable Documents

Document # Date Title of Document

1077-9430010 Rev C 8 April

Interface Design Description for the JTE Follow-on Production Program

1077-9170002 Rev D 30 Aug

JTE Follow-on Production USAF Command and Control Unit Subsystem Specification

1077-9170001 Rev E 14 Oct

JTE Follow-on Production USAF Threat Emitter Unit Subsystem Specification

1077-9170004 Rev D 30 Aug

JTE Follow-on Production Interface Requirements Specification

201028094 Rev H 12 July

System Performance Specification for JTE Follow-on Production

43D7-19-7-1, 43D7-19-7- 3, 43D7-19-7-4, 43D7-19-

7-6WC-1, 43D7-19-7-13,

43D7-19-7-23, 43D7-19- 8-1, 43D7-19-8-3, 43D7-

19-8-4, 43D7-19-8-6WC-

1, 43D7-19-8-13, 43D7- 19-8-23

Current Revision from

ETIMS

USAF Follow-on Production Technical Orders

DoD Manual 4140.01 9 Mar 2017 DoD Supply Chain Materiel Management Procedures

DoD Manual 5220.22-M

28 Feb

National Industrial Security Program Operating Manual

MIL-STD-461G 11 Dec

Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment

MIL-STD-810G(1) 15 Apr

Environmental Engineering Considerations and Laboratory Tests

MIL-STD-1472G 11 Jan

Human Engineering

MIL-STD-2073-1E(1) 7 Jan 11 Standard Practice for Military Packaging

MIL-STD-130N(1) 16 Nov

Identification Marking of U.S. Military Property

MIL-STD-1686C 25 Oct 95 Electrostatic Discharge Control Program for Protection of Electrical and Electronic Parts, Assemblies and Equipment (Excluding Electrically Initiated Explosive Devices)

MIL-STD-129R 18 Feb

Military Marking for Shipment and Storage

FED-STD-313E 01 Jul 2014 Material Safety Data, Transportation Data, and Disposal Data for Hazardous Materials Furnished to Government Activities

J-STD-001 Apr 2010 Requirements for Soldered Electrical and Electronic Assemblies

MIL-HDBK-310 23 Jun 97 Global Climatic Data for Developing Military Products

MIL-HDBK-454B 15 Apr

General Guidelines for Electronic Equipment

MIL-HDBK-781A 30 Jan

Reliability Test Methods, Plans, and Environments for Engineering Development, Qualification, and Production

MIL-HDBK-61A 07 Feb 01 Configuration Management Guidance

MIL-PRF-38535K 20 Dec

Integrated Circuits (Microcircuits) Manufacturing, General Specification

MIL-PRF-29612B 31 Mar

Training Data Products

MIL-PRF-49506 11 Nov

Logistics Management Information

AFI 61-201 9 Feb 2016 Management of Scientific and Technical Information (STINFO)

AFI 63-101/20-101 9 May

Integrated Life Cycle Management

AFI 23-101, AMC

Supplement

08 August 2013, 09 Dec 2013

Air Force Material Management

AFMCI 24-201 14 Jan

HQ AFMC Packaging and Materials Handling Policies and Procedures

AFMAN 24-204 13 Jul 2017 Preparing Hazardous Materials for Military Air Shipments

AFJMAN 23-215 21 Jan

Reporting of Supply Discrepancies

AFPAM 63-128 10 Jul 2014 Integrated Life Cycle Management

Technical Order (TO) 00-

35D-54

1 Sep 2015

USAF Deficiency Reporting, Investigation, and Resolution

Electronic Code of Federal Regulations (e-

CFR)

1 Oct 2017 Electronic Code of Federal Regulations (e-CFR)

TRA Deskbook July 2009 DOD Technical Readiness Assessment (TRA) Deskbook

DoDI 5200.39 28 may

Critical Program Information (CPI) Protection with the Department of Defense

AFPAM 63-113 17 Oct

Program Protection Planning for Life Cycle Management

AFI 16-601 18 Feb

Implementation of, and Compliance with, International Arms Control and Nonproliferation Agreements

DSCA 5105.38-M 3 Oct 2003 Security Assistance Management Manual

AFMAN 16-101 15 Feb

International Affairs and Security Assistance Management

DoDI 8510.01 12 Mar

Risk Management Framework for DoD Information Technology

AFPD 17-1 12 Apr

Information Dominance Governance and Management

AFI 33-580 24 Dec

Spectrum Management

AFI 91-204 19 Jan

Safety Investigations and Reports

AFI 63-101 9 May

Integrated Life Cycle Management

AFI 48-109 1 Aug 2014 Electromagnetic Field Radiation (EMFR) Occupational and Environmental Health Program

Other publications

Source/Document Number

Date Document Title

SAE-AS8090 17 Sep 97 Equipment, Towed Aerospace Ground, Mobility

JTE SDD version 10 10 Oct 10 JTE Threats (U) for Follow-on Production, (Secret N/F)

VMEbus Specification Manual

Oct 1985

VMEbus Specification Manual Rev C.1

Range Threat Systems -

SCG

27 Oct

Electronic Warfare Threat Emitter Security

Classification Guide

JTE SPO 18 May

Joint Threat Emitter Capability Production Document

IEEE SA - C62.41.1991 25 Feb 95 IEEE Recommended Practice for Surge Voltages in Low-Voltage AC Power Circuits

Note: Copies of listed federal and military standards, specifications and handbooks are available for download from the following websites:

o DoD Issuance Website, http://www.dtic.mil/whs/directives/ o ASSIST database, https://assist.daps.dla.mil/quicksearch/ o IEEE, http://www.IEEE.org o SAE specifications, http://www.sae.org/

4 REQUIREMENTS

PROGRAM MANAGEMENT

Program Manager (PM) The Contractor shall identify and maintain a PM who shall be the single point of contact for all matters under this contract. This program manager shall ensure all systems engineering and obsolescence monitoring and identification are completed. The Contractor shall also ensure that all program management personnel assigned to the program shall be available, as required, to meet all SOW requirements. The Contractor shall flow down all applicable requirements of this SOW and contract to all subcontractor, suppliers and vendors. The Contractor also shall submit a small business subcontracting plan. (CDRL A011)

The Contractor shall report ALL Contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the JTE via a secure data collection site. The Contractor is required to completely fill in all required data fields at http://www.ecmra.mil.

Reporting inputs will be for the labor executed during the Period of Performance (POP) for each Government Fiscal Year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year. Contractors may direct questions to the CMRA help desk.

Monthly Status Report The Contractor shall develop a monthly metrics report consisting of general program status, the http://www.dtic.mil/whs/directives/ https://assist.daps.dla.mil/quicksearch/ http://www.ieee.org/ http://www.sae.org/ http://www.ecmra.mil/ current status of each end-item in production, all retrofit kits, all spares, and ordered support equipment, and status updates for all ongoing ECPs. (CDRL A009)

ECP tracking within the monthly report shall include:

1) Unique tracking number for each ECP

2) Brief description of ECP

3) Whether the ECP is Class I or II

4) Status of the cost shall be reported

5) Current status of ECP progress

6) Any required Government actions shall be detailed

7) The actual schedule shall be tracked against the estimated schedule

Contract Funds Status Report (CFSR) The Contractor shall provide on a monthly basis a current accounting of all funds included on cost reimbursable CLINs in the CFSR. (CDRL A010)

Integrated Management Plan (IMP) The Contractor shall implement and maintain an IMP for this program. The IMP is an event driven plan that defines a program’s major tasks and activities and lays out the necessary conditions to complete them. This plan shall include the manufacturing/production approach, methodologies, tools, and procedures to be used during the hardware production, testing, and system integration of all end-items. This IMP must also include major tasks and activities necessary for procurement and delivery of retrofit kits, support equipment, and spares orders.

The IMP shall be a single plan for the entire effort, including associate and/or major subcontractor activities. Each section/subsection of the IMP shall contain events, Significant Accomplishments, accomplishment criteria, and selected narratives. (CDRL A004)

• Event: An IMP event is a key contractual or programmatic event defined by the Government or the offeror, which defines progress at a specific point in time. The offeror shall include definitions of each event at the beginning of the IMP. IMP events shall be properly sequenced and may include demonstration milestones, technical or program reviews and audits, and other key decision points. For each IMP event, there shall be one or more entry or exit Significant Accomplishments.

• Significant Accomplishment: Significant Accomplishments are interim or final critical efforts that must be completed prior to entering or exiting an event. Significant Accomplishments are organized by the PWS element/product. Entry accomplishments reflect what must be complete to initiate an event. Exit accomplishments reflect what must be done in order for the event to be successfully closed and that the program is ready for the next event. For each Significant Accomplishment, there shall be one or more accomplishment criteria. The Government is seeking Significant Accomplishments that provide sufficient insight to the process for achieving SOW requirements. The accomplishments shall be sequenced in a manner that ensures a logical path is maintained throughout the effort and tracks against key events.

• Accomplishment Criteria: Measurable and useful indicators demonstrating that the required level of maturity/progress in an associated Significant Accomplishment has been achieved.

Integrated Master Schedule (IMS) The Contractor shall implement and maintain an IMS for this program. The Critical Path and Secondary Critical Path shall be delivered as separate and individual views with each submission. A baseline IMS shall be developed at the start of the program. An IMS shall be developed and maintained throughout the program, using the original baseline schedule as an unchanging reference. The IMS shall be provided in Microsoft Project format. (CDRL A005)

Meetings, Reviews, and Conferences

4.1.6.1 Program Management Review (PMR) support

The Contractor shall participate in and support all reviews, audits, and meetings as requested by the Government. PMRs shall be conducted quarterly and as requested by the Government, at a mutually agreeable location or via teleconferences. The total number of PMRs per year will not exceed five. (CDRLs A001, A002, A003)

4.1.6.2 Conference Room

The Contractor shall provide a conference room suitable for meetings of Government representatives, plus Contractor personnel, in support of scheduled meetings at the Contractor’s facility.

4.1.6.3 Meeting Agendas and Presentation Material

The Contractor shall publish an agenda and presentation material for all meetings and conferences. The Contractor shall request from the Government any items or issues to be discussed or presented at the meetings, and shall include such items in the agenda and presentation material. Agendas and presentation material shall be submitted not less than ten business days prior to any meeting. (CDRLs A001, A002)

4.1.6.4 Meeting Minutes

The Contractor shall provide a written record of the discussions, decisions and action items identified at each meeting. (CDRL A003)

4.1.6.5 Post-Award Conference (PAC)

The Government will convene a PAC with the Contractor at a location that is mutually agreeable to both parties within 90 calendar days after contract award. The Government will coordinate the actual date, time, and location of the conference with the Contractor.

4.1.6.6 Contractor Facility Access

The Contractor shall arrange for full access to applicable Contractor facilities and offices by Government representatives conducting any business, making observations, or performing inspections required by public law or by this contract.

4.1.6.7 Functional Configuration Audit (FCA) and Physical Configuration Audit (PCA) The Contractor shall host an FCA and PCA for each end-item undergoing First Article Testing, if ordered, using multiple formal meetings as required. The Contractor shall host an FCA and PCA for each approved ECP using multiple formal meetings as required. The FCA shall verify that the system and components meets all System Performance Specifications (SPS), Systems Specifications, and applicable subsystem specifications (FC2U, MC2U, TEU, WTEU, and Retrofit kits). The PCA shall ensure that all parts match their drawings. For each PCA event, drawings to be reviewed shall be available to the Government not less than ten business days prior to the scheduled event. For each FCA and PCA, separate reports shall be submitted not later than 15 business days after completion of the individual event. The final FCA and PCA shall include an overall report that references and summarizes all previous FCA and PCA reports. The final FCA must be completed not later than 15 calendar days prior to system acceptance. The final PCA must be completed not later than 15 calendar days before Contractor Factory Acceptance Testing (FAT). The Contractor shall generate and submit a Specification Change Notice (SCN) for any system design and requirement change recommendations, including all internal and/or external interfaces, and system and/or subsystem specifications for Government approval. Written Government approval is required before any configuration changes are implemented into the JTE system design. (CDRLs A015 through A022, A024, A025)

The Government reserves the right to conduct Configuration Management (CM) audits, assessments, verifications, and reviews of the Contractor’s data and processes for generation, verification, and control of this data on an as-needed basis. The Contractor shall support all such audits, assessments, verifications, and reviews to confirm data, records, and process integrity and consistency to assure that the baselines are accurately documented.

4.1.6.8 Design Reviews

At a minimum the Contractor shall hold a Manufacturing Readiness Review (MRR) that shall be considered a formal design review, for the first end-item of each type (independent of first article testing) ordered prior to proceeding into production. When mutually agreed upon between the Government and the Contractor, the MRR for multiple end-item types can be combined. The

Contractor shall hold formal design reviews for all proposed design changes that arise as part of an ECP. Additional design reviews can be added as agreed upon by both the Contractor and the Government. (CDRLs A001, A002, A003, A014 through A035)

Design reviews shall include, but are not limited to:

1) Calculations

2) Any necessary design studies or analyses, including the design analysis as required in this document

3) Drawings, including equipment layout drawings (packaging), design processes, components, assemblies, work instructions, and component calibration/setup

4) Electrical and mechanical design

5) Environmental control

6) Thermodynamic design

7) Software design/implementation (including third party software)

8) Training material updates

9) Lists of materials, parts, and processes

10) Human engineering elements

11) Corrosion control

12) Maintainability

13) Production capability and manufacturing

14) Quality considerations

15) Risks and Risk Management

16) All information regarding any mockups/assemblies (i.e. software development stations, etc.)

Configuration Management Plan (CMP) The Contractor shall maintain a robust CMP for software, technical data, drawings, and all data deliverables. The Contractor’s hardware and software documentation shall be compliant with ANSI/EIA-649 or with the guidelines in the MIL-HDBK-61A Configuration Management Guidance (07 Feb 01). The Contractor shall establish a CM program including Configuration Identification, Change Control, Configuration Control Board (CCB) activities, Configuration Baseline Management, Configuration Status Accounting and Reporting, Configuration Verification and Audit, and Release/Database Management for hardware, software, and associated documentation. All Contractor CCB activities including but not limited to non-conformances, testing, PCAs, software changes, etc. shall include Government Program Office representation unless delegated to a DCMA representative.

The Contractor shall deliver a CMP that details the processes that will be followed to ensure a complete, and accurate Technical Data Package (TDP) is maintained. This CMP shall encompass all general aspects on: Configuration Identification, Configuration Control, Configuration Status Accounting, Configuration Verification and Auditing. The CMP shall summarize the CM organization and process used by the Contractor, and how this process will be used on this contract. The CMP must show how the ECP process ties into the Contractor’s configuration management processes.

The primary configuration baseline for this contract is the Government provided TDP, however, multiple baselines may diverge from this baseline with customer specific purchase orders and associated ECPs. The Contractor shall provide a CMP that outlines the management of multiple configurations of the JTE system.

In the case of multiple configuration baselines, a separate count shall be created for the release of the design CDRLs and TDP for each configuration baseline being maintained.

The CMP shall include a detailed process for upgrading drawings and documents of multiple configuration baselines while maintaining the integrity of each baseline. (CDRL A007)

4.1.7.1 Quality Assurance (QA) Program

The CMP shall also include a QA plan that outlines the Contractor QA program.

The Contractor shall maintain a QA program that integrates QA requirements into the manufacturing, and testing of hardware and software. The Contractor’s QA program shall establish the necessary QA processes, controls, and approval authority to ensure that product quality, reliability, safety, and other element attributes are not compromised. The QA program shall be compliant with the requirements of ISO-9001 IAW the SPS. Unless otherwise specified in the contract, the Contractor is responsible for ensuring all inspection requirements are met and ensuring standards for quality deliverables are set. The Government reserves the right to perform any inspection, or verify any test and inspection record it deems necessary to ensure the requirements of the SOW and the SPS are met. Except as otherwise specified in the contract, the Contractor may use their own or any other suitable facilities approved by the Government to perform the inspection set forth in the SOW where such inspections are deemed necessary to assure supplies conform to prescribed requirements.

Previous acceptance or approval of material by the procuring activity shall in no case be construed as a guarantee of the acceptance of the finished product. The Government reserves the right to inspect any part, assembly, or testing event, using a Program Office Representative, or other Government representatives. The Contractor shall support all inspections required by the Government. (CDRL A007)

Configuration Audit Plan The Contractor shall deliver a configuration audit plan containing the provisions for performing an FCA and PCA as part of First Article Testing on each end-item type, for each delivery, standard and accelerated, and retrofit kit ordered. (CDRL A019)

Data Management The Contractor shall implement a data management program with controls to address quality of data preparation, compliance with CDRL specifications, timely submittal, maintenance, and tracking of all data deliverables, data products, and related correspondence. The Contractor shall, as part of their data management program, ensure proper handling of the GFI TDP IAW the distribution statements and other markings. All CDRL items shall be packaged separately and delivered as data items. All deliverables shall be delivered in English and in the format and media established by the individual CDRLs. If a CDRL does not specify a length of time for review, the Government will have 45 calendar days. If the Government requires more than 45 calendar days the Contractor will be notified in writing. Acceptance of a deliverable will follow the instructions identified in block 7 of the CDRL. In the event of rejection of any deliverable, the Contractor will be notified in writing by the Contracting Officer of the specific reasons why the deliverable was rejected. The Contractor shall have ten business days to correct the deliverable and resubmit to the Government for re-inspection. If the Contractor requires longer than ten business days, the Contractor shall provide a written notification of the delay within five business days and provide justification for the delay. The Contractor shall be responsible for redelivery of CDRLs affected by ECP changes approved by the Government IAW CDRL delivery timeline requirements if not otherwise specified in the ECP.

4.1.9.1 Government Data Rights

The Government requires the ability to fully sustain the JTE program as well as support future procurement requirements competitively. The Government is providing a Government owned TDP as GFI under this contract and retains all rights to the TDP as well as all changes to this data under the contract. Therefore any ECP changes affecting the Government owned TDP shall be delivered to the Government with Unlimited Rights as the action(s) will be fully funded by the Government. Any non-commercial technical data developed by the Contractor or a subcontractor that exceeds the scope of the TDP shall be delivered with a minimum of Government Purpose Rights (GPR), when mixed funding from the Government and Contractor were utilized. Non-commercial technical data includes, but is not limited to: computer software, systems, processes, and technical data. Computer software is defined as source code, source code listings, object code listings, design details, algorithms, processes, flow charts, formulas and related material that will enable the software to be reproduced, recreated or recompiled. The Contractor is required to include flow down provisions in all subcontracts requiring delivery of a minimum of GPR in all technical data and software delivered to the Government under this contract. Any assertions of data rights other than Unlimited Rights to any of the aforementioned data must be in writing prior to basic contract award and agreed upon by the Government. Also, changes to data rights assertions due to ECPs must be made in writing as part of the ECP proposal and award and agreed upon by the Government.

4.1.9.2 Commercial Item Technical Data License Rights

The Government shall receive, at a minimum, license rights IAW DFARS 252.227-7015 for all Contractor identified commercial item technical data, as proposed in the Contractor’s technical solution, under this contract.

4.1.9.3 Standard Commercial Software License Rights

The Government shall receive, at a minimum, standard commercial license rights in all commercial computer software, as identified and proposed in the Contractor’s technical solution, associated with this contract as outlined in DFARS 227.7202. The Contractor shall deliver a list of commercial software licenses and keys for each computer within an end-item, retrofit kit, Software Development Station (SDS), spares, and support equipment ordered. (CDRL A050)

4.1.9.4 Distribution of Technical Documents

The distribution of technical documentation shall be no less than Distribution Statement D unless otherwise stated in a CDRL or in the provided GFI IAW AFI 61-201. Distribution D denotes authorized distribution to the Department of Defense (DoD) and DoD Contractors only (AFI 61- 201 Management of Scientific and Technical Information (STINFO) 29 Jan 2016). If any deliverable is other than Distribution D, the Contractor must identify and obtain approval from the Government prior to submission. Technical documentation shall also include appropriate export control and destruction notices.

Technical Orders (TO) The Government shall have Unlimited Rights in all TO change pages and manuals modified or delivered under this contract. The Contractor shall develop, prepare and deliver TO change pages in MIL-STD-38784A, MIL-STD-38807C, and MIL-PRF-5096G format resulting from ECPs.

The Contractor shall ensure the data supports the USAF two level JTE maintenance concept (operation level and depot level) and ensure the TOs are fully sustainable with the configuration of the JTE system/equipment’s hardware, software, firmware and operational mission requirements. The Contractor shall deliver their QA validated TO change pages no later than 20 business days prior to the completion of any approved ECP. TO change page procedures must account for and document the support equipment required, provide any commercial technical manuals referenced if different from existing manuals, and include necessary usable on code identification. (CDRLs A041, A042)

4.1.10.1 Provisioning Technical Documentation (PTD)

The Contractor shall submit PTD in LSA036 format compatible with the AFMC Automated Provisioning System (D220) as required by MIL-PREF-49506. PTD shall be required as part of any ECP intended to alter the hardware baseline. The schedule for submitting the PTD shall be IAW the authorizing ECP Provisioning Performance Schedule (PPS) (AFMC Form 718).

(CDRLs A036, A037, A039)

4.1.10.2 Supplemental Data for Provisioning (SDFP)

Schedule and requirements for submitting the SDFP shall be IAW the authorizing ECP Provisioning Performance Schedule. (CDRL A039)

Risk Management The Contractor shall establish, execute, and sustain a Risk Management Plan. The Risk Management Plan shall, at a minimum (CDRL A006):

1) Identify, analyze, mitigate, and track schedule and performance risks, integrating quantitative risk assessments

2) Identify, analyze, manage, and track risks that could impact the outcome of test events

3) Use risk assessments as part of entry and exit criteria for all design reviews

4) Identify effect to Key Performance Parameters (KPP), Key System Attributes (KSA), Mean Time Between Failure, and Mean Time to Repair, as outlined in the SPS, and show mitigation for each risk

5) Review current risks as part of each formal PMR

6) Review current and new risks as part of any ECP

Government Contract Management Responsibility for Government contracting activities rests solely with the Procurement Contracting Officer (PCO). No conversation, recommendations, or direction, whether given directly by, or implied by Government personnel, that will affect the scope, schedule, or price of the program covered by this SOW shall be acted upon by the Contractor unless specifically approved by the PCO in writing.

The Contractor shall deliver a safety plan that outlines compliance with all safety provisions, e.g., technical specifications, technical publications, and Federal Contractor Occupational Safety and Health Standards (Title 29 CFR Part 1910). If there is no applicable Occupational Safety and Health Administration (OSHA) standard, use other applicable nationally recognized sources of safety, health, and fire prevention standards. (See appendix A for information on safety)

(CDRL A013)

Government Furnished Property (GFP) The only anticipated GFP on this contract is technical data, SDS, and training material. However, if the Contractor requires additional GFP, and the need is validated by the Government, the following is applicable.

The GFP, as defined in this SOW, includes Government Furnished Equipment (GFE) and GFI.

Any GFP provided to the Contractor shall be inventoried and maintained. Contractor GFP requests shall include all information required to complete form AFMC IMT 8 .Contractor GFP requests will be rejected if they are incomplete, or the GFP is not available. Formal GFP requests shall be written and submitted to the Contracting Officer not later than 90 days prior to need date(s). Location of GFP access, vendor facility or operating location, shall be submitted as part of the GFP access request to the PCO. If the Contractor requires access to operational units a visit request shall be coordinated through the Program Office and Joint Personnel Adjudication System (JPAS). All required visit request information shall be provided by the PM, or their designee, to the Contractor.

In the event of an accident involving GFP, the Contractor shall immediately report, to the PCO and Government PM, all available facts relating to each instance of injury to personnel or damage to GFP. If a major mishap, as defined in AFI 91-204, involving GFP occurs, the Contractor shall immediately secure the accident scene and the damaged item until released by the accident investigation authority. If the Government elects to conduct an investigation of the accident, the Contractor shall cooperate fully and assist Government personnel until the investigation is completed at no additional cost to the Government. The Contractor shall include a clause in each of its subcontracts requiring subcontractor cooperation and assistance in accident reporting and investigation. The Contractor is responsible for all costs associated with shipping GFP. The Contractor is responsible to make all arrangements for the shipment of GFP. The Contractor is responsible for any/all damages as a result of loading, shipment, unloading, and use of GFP. At the completion of all contract activities and prior to final contract closeout or invoicing, the Contractor shall return all GFP to the SPO, operating location of origin, or as directed in writing by the PCO. The Contractor shall maintain a property accounting system and shall submit inventory audits as part of the monthly report. (CDRLs A009, A012)

Systems Engineering

4.1.14.1 General Engineering Methodology

The Contractor shall implement robust Systems Engineering processes to fabricate, integrate, test, evaluate, document, deliver, and support the FC2U, MC2U, TEU, WTEU, and other components as described in this SOW. Technical management shall include but is not limited to decomposition of requirements, engineering trade studies and implementation of the System Engineering processes. Expected and measured system performance compared to the KPPs and KSAs in the SPS shall be briefed at all PMRs.

4.1.14.2 System Specifications

Using the Government SPS, system specifications, subsystem specifications, and other Government provided technical data or interface documents as the basis, the Contractor shall ensure that all requirements have been met. Updates to system or subsystem specifications shall be part of a Government approved ECP. Specification Change Notices shall be required for any requested specification changes. (CDRLs A016, A020, A021)

4.1.14.3 Hardware Architecture

Hardware architecture shall be updated only as part of an approved ECP. (CDRLs A017, A018, A020)

4.1.14.4 Engineering Reviews

The Contractor shall host, at their facility or another Government approved location, Technical Interchange Meetings (TIMs), Integrated Test Team meetings, Test Readiness Reviews (TRRs), and Program Management Reviews (PMRs). All associated deliverables that are part of the TIMs, TRRs, and PMRs shall be delivered IAW the contract CDRLs.

Each formal review shall utilize agendas, presentation material, and minutes, which shall be delivered to the Government. The duration and schedule for each of these reviews must be coordinated with the Government to assure that Government participation is possible. The Government reserves the right to postpone any review that it deems the Contractor is not prepared for. (CDRLs A001, A002, A003)

4.1.14.5 Non-Conforming Material

The Contractor shall control all material that has been determined to be non-conformant to engineering design documents in any way. A Material Review Board, with mandatory Government program office participation, shall be convened to disposition non-conforming materials. All minor non-conformances that result in a “use-as-is” disposition shall be reviewed with the local Government QA Representative (GQAR) or DCMA quality inspector for concurrence with the disposition. All materials that are “reworked” shall be presented to the GQAR as part of the re-inspection process for concurrence. All materials that are “returned to vendor” shall not require concurrence of the Government. All major non-conformances that are not “return to vendor” for the disposition shall be presented to the Government Program Office for review and approval. A summary of all non-conformances, including part number, revision and location in process where the non-conformance was identified, and the disposition shall be documented and released as part of the monthly status report. (CDRL A009)

4.1.14.6 Request for Variance

Any major material discrepancies found that are proposed for use or any product that does not fully meet the standards of the SPS, shall be submitted on a Request for Variance (DD Form 1694) for approval by the Government. (CDRL A022)

4.1.14.7 Specialty Engineering

The Contractor shall establish and maintain a Hazardous Material Management Plan (HMMP) and deliver a HMMP report. The Contractor’s HMMP shall include Radiation Hazard Control Procedures IAW AFI 48-109. The Contractor shall follow all system security engineering and cybersecurity requirements in the SPS and other program documents such as the Program Protection Plan (PPP), the DD Form 254, the JTE Authority to Operate (ATO) package, and the Security Classification Guide (SCG). (CDRL A008)

Security

4.1.15.1 Classified Information

The Contractor shall protect all classified information provided or generated on this contract, per DoD 5220.22-M (National Industrial Security Program Operating Manual). This shall include, but is not limited to: Facility Clearance, Personnel Security Clearance, Storage, Training, Marking, Safeguarding, and Reproduction.

4.1.15.2 Clearance

This contract will require access to classified information at the SECRET level. Work requiring a SECRET clearance shall require a DD Form 254 on file. The Contractor is not authorized to view the classified document(s) without a SECRET security clearance. All classified documents and information systems shall be protected IAW the National Security Act of 1947 and the Electronic Warfare Threat Emitter Security Classification Guide.

4.1.15.3 Confidentiality

The Contractor shall abide by all Government rules, procedures and standard of conduct. The Contractors requiring access to Government Automated Information Systems (AIS) shall have background investigations and security awareness training completed after contract award but prior to AIS access. The Contractor/contract personnel shall not release or remove system documentation, data, or reports generated by or through use of Government systems. All requests for requests for information shall be forwarded to the JTE JEDI program PCO.

Diminishing Manufacturing Sources and Material Shortages (DMSMS) Monitoring:

The Contractor shall monitor for parts obsolescence utilizing predictive tool(s), the GIDEP database, and other like industry databases. The Contractor shall notify the Government within five working days of discovery. The Contractor shall avoid counterfeit replacement parts and materials. Following initial notification the Contractor shall deliver information concerning the impact to procurement or production, and potential options for alternate parts, sources of supply, or design changes within ten working days of Government notification. Formal changes to the design will be approved as part of an ECP IAW SOW paragraph 4.8. (CDRLs A020, A049)

END-ITEMS

Each end-item shall be built IAW the GFI TDP. Updates to replace obsolete parts shall be through an ECP. Form, Fit, Function, and Interface (F3I) ECPs and all end-item production qualification testing shall be included in the scope of end-item production. First Article Testing shall not be included as part of the end-item price, but shall be priced into the First Article CLINs. See paragraph 4.4 Qualification Testing for more details. The end-item TDP shall be updated as part of any ECP with all affected drawings issued as a revision to the existing

Government Drawing(s) and delivered to the Government with a completed Engineering Change Order (AF3925) for each drawing, identifying all changes. (CDRLs A017, A018, A020)

Prior to proceeding into formal production of systems the Contractor shall ensure they can meet a minimum Manufacturing Readiness Level (MRL) of 7 before any required First Article Testing. Through First Article Testing and other available supporting documentation the Contractor shall provide justification that their production capability then meets a minimum MRL 9 as part of MRR as outlined IAW SOW paragraph 4.1.6.8. All MRLs are defined within the Manufacturing Readiness Level Deskbook Version 2.2.1 and described within the MRL_Users_Guide_V12.5.16.xls (attached in Section J of the Model Contract).

The Contractor shall provide all the equipment, manpower, facilities and other necessary resources to produce, test, maintain and deliver end-items as orders are awarded. The Contractor is not responsible for Site Acceptance Test (SAT) facilities and aircraft. The Contractor shall complete all required periodic maintenance as defined in 43D7-19-7-6WC-1 and 43D7-19-8- 6WC-1. See the pricing workbook for the end-item part number list. Multiple quantities of the same end-item, regardless of end user, in an order count towards the discount table (bundle buy).

Quantity buys shall be applied at the CLIN level, not the sub-CLIN level. The Government requires a maximum of 24 end-items to be delivered IAW the contract delivery schedule, unless a higher maximum quantity is mutually agreed upon during contract performance. The Contractor shall be able to produce 24 JTE end-items within the standard and accelerated delivery schedules outlined below in paragraphs 4.2.1 and 4.2.2. The Government will not order more than 24 total end-items in a 12 month period unless mutually agreed upon.

FC2U

The Contractor shall produce and deliver all FC2Us ordered within 12 months (accelerated) or 18 months (standard) After Receipt of Order (ARO).

MC2U, TEU, and WTEU The Contractor shall produce and deliver all MC2Us, TEUs, and WTEUs ordered within 18 months (accelerated) or 24 months (standard) ARO.

Systems Design JTE FC2Us, MC2Us, TEUs, WTEUs, retrofit kits, and spares produced or procured under this contract shall be compatible with currently fielded end-items as stated in the SPS. The Government will provide, as GFI, JTE pre-mission files that shall be loaded into each end-item.

Any changes to these pre-mission files shall only be accomplished as part of an approved ECP.

Additionally, all assets produced or procured under this contract shall conform to the configuration baseline of the JTE-FO. End-item design changes due to obsolescence, or other issues shall be submitted to the Government as an ECP IAW paragraph 4.8. (CDRLs A020, A021, A022)

4.2.3.1 Design for Non-available Items

The Contractor shall identify obsolete parts discovered during the performance of this contract.

If obsolete parts are discovered, the Contractor shall provide notification and submit an ECP to replace the part(s). If unavailable parts are discovered, the Contractor shall, as part of an ECP, propose replacement parts that meet all data rights requirements IAW paragraph 4.1.9.1 and meets at a minimum Technology Readiness Level 6. (CDRLs A020, A049)

4.2.3.2 Hardware Design

The Contractor shall adhere to the Government approved configuration baseline for hardware provided in the GFI technical data. Any changes required or recommended to the hardware design shall be delivered as part of an ECP per paragraph 4.8. The Government will approve or deny hardware configuration changes IAW the ECP process in paragraph 4.8. (CDRL A020)

4.2.3.3 Software Modification

If necessary during the course of production or procurement, any software changes that the Contractor feels need to be addressed shall be proposed to the Government as an ECP. If the Government deems the proposed changes necessary the ECP process shall be followed as defined in paragraph 4.8 authorizing the Contractor to make the changes.

Any software modifications made as part of this contract shall meet all requirements of the SPS, and shall undergo Computer Software Configuration Item (CSCI) testing IAW paragraph 4.4.4.

The software changes shall be made to the software, provided by the Government, as part of an approved ECP. Once all software changes are completed, the software source code and executables shall be provided to the Government for incorporation into the Government software configuration management systems. The Contractor’s software CM shall be, at a minimum, equivalent to the Software Engineering Institute (SEI) Capability Maturity Model Integration (CMMI) Level Three Core Process Areas and Development processes. (CDRLs A015, A016, A020, A026 through A031)

The Contractor shall ensure that all units (end-items and computers) delivered under this contract are up to date with all patches and Security Technical Implementation Guides (STIGs) available at the time of delivery. The Contractor shall provide recommended changes to the Risk Management Framework (RMF) package to facilitate a new ATO when proposed software changes affect the cybersecurity posture of the JTE. The Contractor shall work in conjunction with the Government Program Office to conduct necessary vulnerability remediation including, but not limited to all current updates, patches, security advisories and STIG compliance scans. The Contractor shall provide remediation for the operating system and additional software/firmware including, but not limited to, the BIOS, Acrobat Reader, Java, MS Office and any other third party software deemed necessary as part of CSCI testing. The Contractor shall address any STIG CAT I and ACAS Critical and High findings as part of the software change effort. All applicable Software Licenses and Keys shall be provided.

For all commercial software used in design, or updated during production or procurement by the Contractor or third party vendors, the Contractor shall deliver electronic copies of all firmware, technical data, drivers, and all special installation procedures. A separate Software License Requirements List (SLRL) shall be provided for all end-items delivered. The SLRL shall include commercial software keys to verify authenticity of all commercial products installed on the systems delivered. (CDRL A050)

Design changes to end-item software due to obsolescence, issues concerning proprietary rights, or other issues shall be addressed in the proposed ECP. (CDRL A020)

Two top-level CSCIs shall be used; one for installation on the TEU and WTEU and one for installation on the MC2U and FC2U. These shall be delivered with Install Shield-type programs to facilitate the installation. The organization of the various CSCIs is shown in Table 2. The most current CSCIs and executables will be provided to the Contractor as GFI at the start of the POP and at any time during the contract when the Government fields an update to one or both of the CSCIs.

Table 2. JTE Nominal Computer Software Configuration Item Structure

TEU Control Computer C2U

MSC Computer MSAT Computer

SCCMainWin

SCCMainRtx

Configure CEESIM

Fault_Control

Fault_Editor

Cal_Editor

Calibration_Control

Cal_Purge_Utility

UView

TEU Config Editor

TEU Version Tool

Radar…