ID07190065_REAP_PH2_PWS_06.10.2019_DRAFT.pdf

General Services Administration (GSA)

Greater Southwest Region

CONTRACT # ID07190065

REAP PHASE 2

for the

Air National Guard

Performance Work Statement (PWS)

6 June 2019

1. Background

The Rosetta Echo Advanced Payload (REAP™) System Phase 1 program leveraged the achievements of the Tactical Airborne Communications Pod (TACPOD) Beyond Line of Sight

Command and Control (BLOS C2) Employment Quick Reaction Capability (QRC) conducted by the U.S. Air Force Life Cycle Management Center (LCMC) at Hanscom, AFB.

The TACPOD system is a persistent communications repeater capability for MQ-9 Remotely

Piloted Aircraft (RPA) and was flown and tested on the China Lake Government test range to a

Technology Readiness Level (TRL) 8 in 2013. The Air National Guard accepted transfer of the

TACPOD system in the first quarter of 2017 and possession is maintained by the 163rd

Reconnaissance Wing at March ARB.

In 2018, the REAP™ Phase 1 effort configured the TACPOD to suit the Air National Guard’s mission using MANET radios, P-25 radio, KOR-24A STTs, ADS-B and other software updates.

The REAP™ Phase 2 Operational Assessment will evaluate the REAP™ system ability to provide the following Critical Capabilities as defined in the ANG Weapons System

Modernization Priorities 2018:

MINIMAL LATENCY TACTICAL DATA LINK – ANG MQ-9 aircraft require an onboard

Tactical Data Link (TDL) radio, with associated hardware and antennas, to employ across

Multiple Areas of Responsibility (AOR).”

COMMUNICATION SUITE WITH IMPROVED INTERFACE – The MQ-9 operates simultaneously across multiple domains and mission sets and requires a flexible, tactical voice system that interconnects all mission participants.”

MISSION-CRITICAL HIGH-BANDWIDTH DATA TOOLS AND APPLICATIONS – ANG

missions support both military and public safety support to augment airborne disaster relief/recovery communications.

2. Program Objectives/Description of Work

The objective of the Air National Guard (ANG) MQ-9 REAP™ Phase 2 Operational Utility

Evaluation (OUE) effort is to demonstrate integration of critical capabilities for airborne disaster relief and recovery using the MQ-9 aircraft and the AgilePod® 16, resulting in a fieldable

System.

This requires the contractor to provide program management, non-recurring engineering, integration, test and evaluation support to update the REAPTM System The contractor shall provide engineering support for an Operational Utility Evaluation (OUE) to be conducted by the

Air National Guard Air Force Reserve Command Test Center (AATC).

The contractor shall provide design tradeoffs, engineering, integration, test, certification and

TCTO development.

The contractor shall provide a solution suitable for use with MQ-9 Block 5 and Block 1

BADDC-equipped aircraft, Block 30 Ground Control Station (GCS), and 2400 series software.

The REAP™ Phase 2 solution will provide 4th Generation Long Term Evolution (4G LTE) and

3G cellular capability, upgradable to 5G, and accompanying high-bandwidth backhaul component to support mission-critical high-bandwidth data tools and applications being developed for military and public safety use. This capability will augment airborne disaster relief/recovery communications.

The REAP™ Phase 2 solution will be incorporated into AgilePod® 16.

The contractor shall provide engineering support for the Government Airworthiness process to execute the ground and flight testing. The contractor shall support Air Worthiness qualification of an additional AGILE POD Payload like EBAS as part of this effort.

The contractor shall provide technical support for the Operational Utility Evaluation (OUE).

The contractor shall provide engineering support for the Government Cybersecurity

Authorization process to achieve the goal of an updated Authorization To Operate (ATO) for the

REAP™ Phase 2 System

3. Scope

This document is the Government’s Statement of Work (SOW) to provide program management, non-recurring engineering, integration, test and evaluation support, materials, and travel for the

REAP™ Phase 2 Operational Utility Evaluation.

The REAP™ Phase 2 Operational Assessment will utilize Air National Guard MQ-9 Block 5

Barrett Asymmetric Digital Datalink Computer (BADDC)-equipped aircraft, Block 30 GCS, and

2408 software.

The contractor shall provide engineering support and travel for an Operational Utility Evaluation

(OUE) to be conducted by the Air National Guard Air Force Reserve Command Test Center

(AATC).

The term “contractor” refers to General Atomics Aeronautical Systems, Inc and “subcontractor” refers to Ultra Electronics Advanced Tactical Systems.

3.1. References

Technical and Contract references are on file with the Air National Guard ISR Requirements

Manager, NGB/A5RS for the Rosetta Echo Advanced Payloads (REAP™) Phase I Contract.

3.1. References

The documents listed in Attachment 6 make up a part of this SOW to the extent specifically imposed herein. Unless otherwise stated, the most current version of each document, as of the date of this SOW, shall be used. Any revisions to Contractor documents require Government concurrence prior to implementation under this contract. Second tier references called out by the

Government documents listed in Attachment 6, and any referenced documents not specially imposed by the SOW shall be used for guidance. Not all documents listed in Attachment 6 will be applicable to this TME effort

4. Technical Requirements / Task Descriptions

Services will be requested and controlled by means of specific objectives, deliverables, and constraints. Services to be performed will consist of the following:

4.1. Place(s) of Performance

Work shall be performed at the following locations:

Subcontractors Facility: Austin, TX- Perform the required modernization upgrades to the

REAP™ Pod system prior to ground and flight Testing.

Contractors Facility: San Diego, CA– Perform the required system integration upgrades to the

REAP™ system prior to ground and flight Testing.

Ground and flight testing will be conducted with support from the Air National Guard Air Force

Reserve Command Test Center (AATC) at March ARB for MQ-9 Block 5 and Block 1.

Operational Utility and Evaluation will be conducted with support from the Air National Guard

Air Force Reserve Command Test Center (AATC) at March ARB for MQ-9 Block 5 .

4.2. Technical Approach

The Contractor shall:

a) Be responsible for the system design, implementation, test and verification of the

REAP

TM

system

b) Demonstrate TRD compliance of the MQ-9 Block1/5 integrated REAP

TM

system solution

c) Provide required artifacts to support airworthiness (Modified Airworthiness Certification

Criteria (MACC))

d) Update MQ-9 Product documentation to the extent necessary to support the REAP

TM

System installation on two (2) MQ-9 Aircrafts – one (1) MQ-9 Block 1 and one (1) MQ-9

Block 5 (i.e. specifications (spec), spec tree, drawings, X-Rev , etc.)

e) Update logistics support, technical data, and other related to REAP

TM

capability integration to the extent necessary to support the REAP

TM

system installation on two (2)

MQ-9 Aircrafts – one (1) MQ-9 Block 1 and one (1) MQ-9 Block 5 (i.e. technical manual, training, support equipment, etc.)

f) Update MQ-9 Product production/modification documentation and procedures to the extent necessary to support the REAP

TM

system installation on two (2) MQ-9 Aircrafts – one (1)

MQ-9 Block 1 and one (1) MQ-9 Block 5 (i.e. Product Test Procedures (PTP), Authorized

Work Instructions (AWI), etc.)

g) Develop and deliver an updated contractor certified Flight Manual and Checklist

Supplement.

h) Develop certified Interactive Electronic Technical Manual (IETM) content which will include General System Information, Fault Isolation, Installation and Removal, Operational

Checks, Illustrated Parts Breakdown and Wiring Diagrams. All new Technical Data shall be developed in accordance with TO 00-5-3, AF Technical Manual Acquisition Procedures and TM-86-01, Technical Manual Contract Requirements (TMCR)

4.3. Technical Requirements

The Rosetta Echo Advanced Payloads (REAP™) system consists of 4 subsystems:

1. REAP pod with 4G cellular LTE mounted to an aircraft.

2. Ground Control Station (GCS) hardware and software components that allow the operator to control and status the airborne pod.

3. Launch and Recovery Element (LRE) hardware and software components that support the end user’s pre-flight configuration of the airborne pod and pre-flight testing of a subset of the airborne pod’s capabilities.

4. Ground-based mobile receiver station with LOS and optional SATCOM equipment that allows the operator to route cellular backhaul traffic to a telecommunications point of presence.

4.3.1 Analysis of REAP

TM

Pod

The design objective for REAP™ is integration into a single pod comprised of a wing mounted aerodynamic enclosure for MQ-9 Block 5 and Block 1 using the AGILEPOD

GFE for the POD enclosure.

MQ-9 integration shall provide a single pod attached to the MQ-9 airframe at wing station 7. The MQ-9 L1 and R7 wing stations provide the critical aircraft electrical interfaces required for these upgrades.

4.3.2 REAP™ POD Capabilities

The REAP™ Pod shall contain the capabilities below:

Host Computer (Data Processing Software)

Hardware Interfaces (1553 Bus, RS-422, RS-170, GPS, Ethernet, etc.)

Ethernet Connectivity between REAP™ components and data routing

Small Tactical Terminal (STT) for Link 16 and Military Voice/Data

ADS-B Mobile Ad-Hoc Network (MANET)

P25 Public Safety Organization voice communications

Four analog audio/PTT interfaces and VoIP bridging

4G LTE and 3G cellular data service

LOS cellular backhaul to telecommunications point of presence

Pod C2 Link

4.3.3 Link 16 Capability

The REAP™ system shall provide a Viasat/Harris Small Tactical Terminal (STT) KOR-24A

Link 16 radio, Radio Frequency (RF) transmission antennas and filtering, and host software system to transmit and receive Link16 messages. The platform position is extracted from MQ-9

Block 5 and Block 1 GPS system. The REAP™ Pod implements a non-C2 function for the MQ-

9 Block 5 and Block 1 to provide these key capabilities required by ANG:

REAP™ MQ-9 Block 5 and Block 1 transmits own ship J2.2 direct PPLI on the LOS

Link 16 network with decreased latency, increased track quality, and when GIG connectivity to the AOR is not available.

REAP™ MQ-9 Block 5 and Block 1 transmits J12.6 Target Sorting on the “Fighter to

Fighter’ NPG 19-20 with decreased latency, increased track quality, and when GIG connectivity to the AOR is not available.

Configuration of the MQ-9 Block 5 and Block 1 Link 16 operating parameters will be performed during pre-flight check-out at the Launch and Recovery Element (LRE). The REAP™

Maintenance Kit system provides a flight line laptop to connect to the local network access port on the REAP maintenance panel. The flight line laptop shall enable pre-flight configuration of the REAP™ Link 16 subsystem by providing the following functions:

Initialize the KOR-24A terminal to allow loading of Link 16 cryptographic key material, Assignment of Precise Participant Location Information including JTIDS Unit (JU) to the MQ-9 Block 5 and Block 1 platform, Push the Initialization DownLoad (IDL) to the KOR-24A terminal from a local file on the laptop.

The Government will provide the Contractor with an IDL for REAP, distribute OPTASKLINK information to network participants, distribute Link 16 key material to MQ-9 Block 5 and Block

1 facilities, provide spectrum authorization and input to the Link 16 deconfliction server, and other actions required by Government doctrine and directives for Link 16 operations.

4.3.4 ADS-B Capability

In order to satisfy the FAA mandated requirement, the REAP pod provides an Automatic

Dependent Surveillance – Broadcast (ADS-B) output. MQ-9s are expected to host an organic ADS-B capability in the future so a design tradeoff shall be conducted to determine if ADS-B is needed in the Phase II effort.

4.3.5 Persistent Systems Wave Relay MANET Capability

The REAP system will participate in the MANET through the Persistent Systems Wave Relay

MPU-5 radio system in the 2200-2500 MHz S-Band. The MPU-5 provides a high bandwidth secure network for voice, video, and data for interoperability with US Army and Special

Operation Forces. The REAP will extend the range and performance of MANET networks while performing the ISR mission.

The REAP system shall:

Extend the range of the MANET network by providing an airborne MANET relay, Automatically distribute the MQ-9 Block 5 and Block 1 Full Motion Video (FMV) on the MANET, Automatically distribute the MQ-9 Block 5 and Block 1 aircraft position in Cursor-

On-Target (COT) on the MANET, Output the MQ-9 Block 5 and Block 1 Cursor-On-Target (COT) Sensor Point of

Interest (SPI) on the MANET when enabled through the Ku Backhaul.

4.3.6 Public Safety Organization P25 Voice Bridge

The REAP™ system provides a voice communications repeater capability using a P25 radio.

The REAP shall bridge P25 voice communications to the military voice and MANET voice channel.

4.3.7 Military VULOS Voice Bridge

The REAP™ system shall provide a voice communications bridge capability using the STT

KOR-24A second channel for VULOS AM voice and, when not configured for Link 16 operations, the STT KOR-24A first channel for VULOS FM voice. The REAP™ pod will bridge military voice communications to the Public Safety Organization P25 and MANET voice channels. The STT KOR-24A second channel UHF antenna and band-pass filter will be optimized for the 225-400 MHz military air-to-ground communications band. The STT

KOR-24A first channel VHF antenna and band-pass filter will be optimized for the 137-174

MHz military air-to-ground communications band.

4.3.8 4G LTE and 3G Communications Relay

The REAP™ system shall provide 4th Generation Long Term Evolution (4G LTE) and accompanying high-bandwidth backhaul component to support mission-critical high-bandwidth data tools and applications being developed for military and public safety use.

This capability will augment disaster relief/recovery communications in areas where cellular service is no longer operational or where the service never existed. 4G LTE will provide high bandwidth data communication capability to military operators, National Guard, and civilian First Responders. This airborne capability can also operate as an ad-hoc private LTE network for government agencies when needed.

The REAP system shall incorporate a voice-centric 2G or 3G cellular radio, which can be integrated with 4G LTE cellular equipment, that enables REAP™ to also carry 911 emergency calls from the general public to Public Safety Answering Points (PSAPs) during emergencies. The cellular equipment shall be 5G-ready so that a future software upgrade can be purchased to serve next generation cellular devices.

The high bandwidth backhaul component for relaying traffic from the 4G LTE/3G radios to the ground will be provided by LOS link. The LOS link radio, amplifiers and antenna will be integrated into the POD. The LOS ground receiver station will provide a mobile, high bandwidth cellular datalink link to the aircraft within a 100 km radius RPA operational area.

This base configuration assumes that the ground station is located near the point of presence.

An optional configuration allows connection to a point of presence over a SATCOM link.

4.3.9 Pod C2 Link

The MQ-9 Block 5 and Block 1 BLOS / BADDC link provides an Ethernet connection between the REAP™ pod at the wing station and network switch allowing communications back to the command center. The connection will be used to control selected REAP™ capabilities. The

Contractor shall implement the following REAP critical mission capabilities over the Ethernet link:

Enable/Disable the transmit of the J12.6 message on Link 16 NPG 19-20, Enable/Disable the output of the COT SPI message on the MANET, Set the waveform, modulation and frequency of the STT KOR-24A’s first and second

VULOS channels, Set the Fighter-to-Fighter channel for the Link 16 network, Select frequency preset of the Public Safety Organization P25 voice radio, Set the frequency and frequency bandwidth of the MPU-5 MANET radio over the

Ethernet interface, Send a ‘chronometer time’ message to the KOR-24A terminal based on GPS time or GPS time with offset, Send a Link 16 Net-Entry message to the KOR-24A terminal, Control the cellular transceiver and associated LOS subsystem backhaul functionality, as applicable.

4.3.10 REAP™ Maintenance Kit

Contractor shall provide a Maintenance Kit to facilitate the REAP™ MQ-9 Block 5 and Block 1 ground and flight tests, and pre-flight ops-checks. The Maintenance Kit will include computers, networking equipment, military voice and data radio, Public Safety Organization P25 radio, ADS-B receiver, Persistent Systems Wave Relay MANET radio, ATAK tablet, RF antennas, cellular user equipment with SIM cards, LOS ground station, power supplies, headsets, and interconnect cabling in transit cases.

4.4 REAP

Performance

4.4.1 The REAP

SYSTEM shall be controllable by the aircrew and provide all capabilities listed in Section 4.3 of this PWS.

4.4.2 The REAP

system shall provide health and status indications to the aircrew.

4.4.3 The REAP

system capability shall be integrated onto one (1) MQ-9 Block 1

(UHK97000-10/- 12) aircraft, which may be equipped with the following additional components:

ER Mod Kit (UHK16256-1 or UHK16456-1)

ER AWI Mod Kits (UHK16249-1 or UHK16449-1)

BLOS Station 7 (UHK16121-1)

BADDC (UHK16176-1)

GPS Splitter (UHK16072-1)

VORTEX (UHK16072-1)

AH (UHK16099-1)

Hi-Jack (UHK16094-1)

Lynx SAR 20A (SCD01226-4)

Weaponization Kit (UHK16003-1 or UHK16203-1)

Hellfire Weapon Installation Kit (UHK16015-1 or UHK16036-1 or UIHK16136-1)

GBU-12 Weapon Installation Kit (UHK16037-1 or UHK16137-1)

GBUGBU-49 Weapon Installation Kit (UHK16038-1 or UHK16138-1)

GBU-38 Weapon Installation Kit (UHK16039-1 or UHK16139-1)

4.4.4 The REAP™ system capability shall be integrated onto one (1) MQ-9 Block 5

(UHK97000-15/20)

aircraft, which may be equipped with the following additional components:

ER Mod Kit (UHK16256-1 or UHK16456-1)

ER AWI Mod Kits (UHK16249-1 or UHK16449-1)

BLOS AE (UHK16535-1)

BADDC (UHK16505-1)

Vortex (UHK16172-1)

AH (UHK16340-1)

Link 16 (UHK16603-1)

4.4.5 The REAP™ system capability shall be integrated onto one (1) Ground Control Station

GCS Block 15 in Linux configuration, which may be equipped with the following additional components:

BADDC Mod Kit (UPB95611-1)

4.4.6 The REAP™ system capability shall be integrated onto one (1) Ground Control Station

GCS Block 30 in Linux configuration, which may be equipped with the following additional components:

BADDC Mod Kit (UPB95611-1)

4.4.7 All MQ-9 Block 1 and Block 5 payloads shall remain on aircraft. Modifications to existing payloads and configurations on MQ-9 Block 1 and Block 5 shall be identified and agreed upon as part of technical design review process.

4.4.8 The REAP™ system Modification Kits shall utilize common part numbers for MQ-9

Block 1/5 and GCS Block 15/30 to the maximum extent possible.

4.3.14 The Contractor shall ensure the changes to the MQ‑9 weapon system and its associated subsystems meet their functional, performance, interface, and usability, suitability, and interoperability requirements

4.4 Technology Maturation Effort

4.4.1 Hardware Development

4.4.1.1 The Contractor shall develop the hardware required to integrate the REAP

TM

SYSTEM

with the aircraft and GCS including but not limited to: electrical cables and brackets, utilizing hardware full development cycle process.

4.4.1.2 All Aircraft/GCS Hardware and Modification Kits drawings shall be Production Ready

Release.

4.4.1.3 The contractor shall produce two (2) prototype Aircraft Retrofit Kits for test - one (1)

MQ-9 Block 1 and one (1) MQ-9 Block 5. The aircraft retrofit kits shall contain hardware and documentation necessary to support MQ-9 Block 1/5 REAP

TM

SYSTEM installation on MQ-9 Block 1/5 aircraft in configuration described in paragraph 4.4.3 and 4.4.4 correspondingly.

4.4.1.4 The contractor shall produce two (2) prototype GCS Retrofit Kits for tests - one (1) Block

15 Linux and one (1) Block 30 Linux.

4.5 Software Development

4.5.1 Software Management and Planning

The Contractor shall comply with their standard internal processes ASI-16692, except as modified by this SOW. The Contractor shall ensure the changes to the MQ-9 weapon system and its associated subsystems meet their functional, performance, interface, and usability, suitability, and interoperability requirements. The Contractor shall develop, verify, and deliver an initial engineering build of the software modules associated with the improved capability integration. The Contractor shall update the SDP as appropriate for the TME contract, if changes are required for implementation/development of the TME. DI-IPSC-81427B, A070 Software

Development Plan

4.5.2 Software Documents

The Contractor shall create/update, coordinate with Government and deliver the baseline aircraft

Software Version Matrix (SVM) and Computer Software Component (CSC) Lineage document updated by incorporating the changes required to support this SOW. The Contractor shall create, update and maintain the following software documentation to reflect the software changes authorized under this contract: Software Requirements Specification (SRSs), Human Machine

Interface (HMI) Design Documents, Software Design Description (SDD), and draft SVM. DI-

IPSC-81433A/T, A013, Software Requirements Specification; DI-MISC-80508B/T, A027, GCS

Human Machine Interface (HMI) Description; DI-IPSC-81442A/T, A052, Software Version

Description/Software Version Matrix; DI-IPSC-81435A/T, A073, Software Design Description;

DI-IPSC-81438A/T, A017, Software Test Plan; DI-IPSC-81439A/T, Software Test Description;

DI-IPSC-81440A/T, A018, Software Test Report

4.5.3 Interfaces

The Contractor shall comply with providing documentation of existing interfaces and design, to include Human Machine Interfaces integrated into the existing MQ-9 Block 1 and Block 5 technical baseline.

4.6 Systems Engineering

The Contractor shall comply with their standard internal processes defined in the Systems

Engineering Management Plan (SEMP), ASI-09425D, except as modified by this SOW. Update the SEMP as applicable to reflect the systems engineering process and provide via the DAL.

The Contractor shall:

Be responsible for the REAP

TM

capability integration requirements definition for the MQ-9 system baseline.

Create any new specs and or Delta specifications documenting the capability.

Shall meet the requirements as defined this PWS, as well as, show verification and traceability to all PWS requirements.

Provide traceability from the REAP

TM

capability defined in the PWS to the delta system/subsystem specifications to the verification artifacts and identify deficiencies

Technical Reviews

The Contractor shall plan and conduct the following technical reviews during the MQ-9 Block

1/5 REAP

TM

system integration TME in the order presented. Note: A System Verification

Matrix shall be provided to establish requirements traceability and verification as part of the Test and Qualification review.

Combined System Requirements Review (SRR) and Preliminary Design Review (PDR)

Critical Design Review (CDR)

Test Readiness TIM

System Verification Matrix (SVM)

The meeting dates and agenda will be mutually agreed to by the Government and Contractor.

The Contractor shall provide all meeting related materials to include the agenda, meeting minutes and action item summaries via the Data Accession List.

4.6.1 Airworthiness Approach

The Contractor shall submit to the Government the System Interface Control Document drawing, Electrical Loads Analysis, RF Profile Analysis, and Aero and Mechanical Analysis documents for updates made to the REAP™ configuration.

The Contractor shall perform analysis of weight and balance, stability and control, electromagnetic interference/compatibility (EMI/EMC), ground vibration test (GVT), Structural

Model Interaction (SMI), and flutter data. The Contractor shall perform GA-ASI AFA airworthiness analysis so as to support the U.S. Government requirements for USAF Military

Flight Release. DI-MGMT-81501A, A029, Weight and Balance Report For Aircraft

The Contractor shall perform a system-level test as specified in the latest revision of ASI-03063

“Payload EMI/EMC Source/Victim Ground Test Plan for MQ-1 and MQ-9” to provide reasonable assurance that there are no EMI or EMC issues related to the changes to the System.

The Contractor shall provide support for a Military Flight Release for test flights, including but not limited to:

Load-out Clearance Drawing

Weight & Balance

Flutter Analysis

Loads & Stress analysis

Preliminary Performance analysis

Stability & Control analysis

Autopilot evaluation

Power Budget table

Source Victim test report

System-level requirements

Loading & Delivery procedures

System Safety Risk Assessment(s)

4.6.2 Technical Integration/Information Exchange Meetings

The Contractor shall support regular Technical Integration Meetings (TIMs)/Information exchanges with the Government and associate Contractors throughout the contract period to address programmatic and technical issues of specific interest. Such meetings may be conducted remotely via a teleconference and will be held regularly based on complexity of the program and as agreed to by the Contractor and government.

4.6.3 Coordination with Cockpit Working Group and Cockpit Evaluation Team

The Contractor shall coordinate with the Cockpit Working Group (CWG) to receive input and consensus for HMI modifications related to the capabilities of this TME. Coordination cycle shall be per the MQ-9 Reaper Program Charter for CWG (dated June 15). At a minimum, the

Contractor shall coordinate and receive input on HMI design prior to PDR; and again CDR using simulations, prototypes or mock-ups to illustrate the HMI design. Additional coordination meeting through TR TIM shall be on an as required basis.

The Contractor shall coordinate with the Cockpit Evaluation Team (CET) to receive input and consensus for HMI modifications related to the capabilities of this TME. The CET shall be used as the source of representative operators for human factors engineering-related evaluations and testing. Prior to integrated test, the Contractor shall coordinate with, provide input to, and solicit feedback from the CET regarding the TME. Inputs describing the capability development using simulation, mockups, surrogate and prototype systems as the Contractor determines applicable

The Contractor shall document the findings and recommendations of the CWG/CET interactions to be available through the DAL commencing with the PDR. The Contractor shall work with the

Government to evaluate test operator feedback and document specific recommendations for future improvement. Improvements will be incorporated into future contract actions and/or software releases.

4.6.4 Technical Baseline Management

The Contractor shall perform system engineering in accordance with the MQ-9 SEMP (ASI-

09425); software engineering in accordance with the MQ-9 Software Development Plan (ASI-

16692); and safety engineering in accordance the MQ-9 System Safety Program Plan (ASI-

09435). The TME shall prepare the required technical baseline documentation needed to document the changes to the Technical Baseline for the implementation of the MQ-9 Block 1/5

REAP

system capability up to and including this TME.

4.6.5 Delta Specification

The Contractor shall document impacts to the current MQ-9 specifications based on the MQ-9

Block 1/5 REAP

TM

system TME as defined by the MQ-9 Block 1/5 REAP

TM

System PWS in a

Delta Specification document.

Updates to the Weapons System (level A), Segment (level B+) and Subsystem (level B-) content shall be formally approved by the USAF. The Delta Specifications shall include updates required to the MQ-9 Unmanned Aerial System Weapon System Specification Tree, ASI-09880

(latest), based on the changes to the baseline MQ-9 specification as a result of the MQ-9 Block

1/5 REAP

TM

Ssystem integration TME; Updates may include references to existing documentation developed for other customers that contains specific design detail being incorporated. DI-IPSC-81431A/T, A011, System/Subsystem Specification; DI-IPSC-81433A/T, A013, Software Requirements Specification; DI-MISC-80508B/T, A034, MQ-9 Spec Tree

4.6.6 New Specifications

The Contractor shall develop and deliver new specifications (if any) as required to document the capabilities of the MQ-9 Block 1/5 REAP

TM

system as integration on the MQ-9. DI-IPSC-

81431A/T, A011, System/Subsystem Specification; DI-IPSC-81433A/T, A013, Software

Requirements Specification

4.6.7 Integrated Requirements Management

The Contractor shall update and maintain the current MQ-9 technical baseline (specifications, ICDs, and design descriptions) for MQ-9 Block 5 Unmanned Aircraft System (UAS) to reflect the system requirements, both directed and derived, of the capabilities defined in the MQ-9

Block 1/5 REAP

TM

system integration PWS. The Contractor shall update and maintain the

Requirements Management database content that is updated for the MQ-9 Block 1/5 REAP system integration TME requirements.

4.6.8 Interface Control Documents

The Contractor shall develop and deliver draft updates to the MQ-9 UAS Interface Control

Documents (ICD) as required, based on the updates associated with this MQ-9 Block 1/5

REAP

TM

system integration TME and associated changes to the MQ-9 product baseline. The

Contractor shall develop and deliver any new ICDs required to document interfaces introduced by the MQ-9 Block 1/5 REAP

TM

system integration TME. If ICDs were developed for another customer, they may be used to document the interfaces if no changes are required. DI-SESS-

81248B, A060, Interface Control Document (ICD)

4.6.9 System/Subsystem Design Description

The Contractor shall develop and deliver draft updates to the MQ-9 Unmanned Aircraft System

Weapon System System/Subsystem Design Description (SSDD) document (ASI-14650) based on the MQ-9 Block 1/5 REAP

TM

systemTME design. DI-IPSC-81432A/T, A012, System/Subsystem Design Description

4.6.10 CONOPS/CONEMPS and Use Cases

The Contractor shall support the updates to CONOPS/CONEMPS for the MQ-9 Block 1/5

REAP

TM

system TME capability. The Contractor shall develop Use Cases detailing the employment of the MQ-9 Block 1/5 REAP

TM

system TME capabilities defined in the PWS. The results of the analysis to be included with the agenda and minutes of the cockpit working group.

4.6.11 Test Observations and Issues/Deficiencies Reports

The Contractor shall use their internal process to investigate and adjudicate identified Test

Observation Issues (TOIs) deficiencies from testing in support of the Government led Deficiency

Reports (DR) management process.

4.6.12 Reliability and Maintainability

The Contractor shall conduct reliability and maintainability predictions for the MQ-9 Block 1/5

REAP

TM

system integration TME in accordance with the MQ 9 RAM Program Plan (ASI-03951) and reliability allocations in accordance with the MQ-9 RDD Reliability Allocation Report (ASI-

10831). The Contractor shall develop and deliver the results in an MQ-9 Block 1/5 REAP system integration R&M predictions and allocations report. DI-SESS-81968; A007, Requirements Allocation Sheets

4.6.13 Safety Engineering

The Contractor shall conduct the safety engineering program for the MQ-9 Block 1/5 REAP system integration TME in accordance with the System Safety Program Plan (ASI-09435). If updates are required as a result of the changes associated with the MQ-9 Block 1/5 REAP system integration TME, the Contractor shall update the MQ 9 System Safety Program Plan as required using MIL-STD-882E as guidance.

4.6.14 System Safety Hazard Analysis (SSHA)

The Contractor shall identify hazard effects that result from functional failures of the Block 5 and Block 1 aircraft and Block 30 GCS and perform analysis on UAS that can cause potential severe hazards unique to the these platforms. The Contractor shall ensure that all hazards identified by this analysis are reflected in the IETM procedures, Notes, Cautions, and Warnings.

The Contractor shall prepare and deliver a System Safety Hazard Analysis (SSHA) Reports for the Block 5 aircraft, Block 1 aircraft, and Block 30 GCS.

The SSHA reports shall also contain the following analyses specific to the capability deltas being implemented under this contract:

Functional Hazard Assessment (FHA)

Preliminary Hazard List (PHL)

Safety Critical Function List (SCFL)

Common Cause Analysis (CCA)

Fault Tree Analysis (FTA)

Failure Modes Effects and Criticality Analysis (FMECA)

Safety Critical Function Thread Analysis (SCFTA)

DI-SAFT-80101C, A054 System Safety Hazard Analysis; DI-SESS-81495A, A023 Failure Modes

Effects Criticality Report

4.7 Airworthiness

The Contractor shall provide subject matter support for Government airworthiness efforts required by the Government for the developmental testing efforts. The support shall include developing a Modification Airworthiness Certification Criteria (MACC) document, conducting compliance verification activities and providing airworthiness data.

4.7.1 Certification Basis

To facilitate Government certification for this modification, the Contractor shall use MIL-

HDBK-516C to develop a MACC Certification Basis document. The MACC Certification Basis will include criteria applicability, standards and methods of compliance tailored as appropriate for modification attributes. The Contractor shall deliver to the USG the initial MACC updates to the MACC Certification Basis ahead of each major technical review, as necessary. The initial delivery is the DT MACC compliance report. The Contractor shall update the DT MACC

Compliance Report with DT results to develop and publish a final MACC Compliance Report.

The Contractor shall develop and deliver agreed upon artifacts that suitably substantiate compliance with applicable airworthiness criteria in the MACC Certification Basis. Any documentation used to substantiate the airworthiness of the design or declares airworthiness from the corporate perspective shall be prepared for USG review in advance of developmental tests or evaluations (DT&E). DI-SESS-81768, A067, MACC Compliance Report

4.7.2 Declaration of Configuration

The Contractor shall create/update, coordinate with USG and deliver the baseline aircraft

Declaration of Configuration (DoC) document to incorporate the changes required to support this

SOW; ASI-03560 and ASI-03786. DI-MISC-80711A/T, A038, Declaration of Configuration

4.7.3 Airworthiness Risk Assessments

The Contractor shall identify and document any new and affected hazards due to these modifications per MIL-STD-882E. If the determination is made that the contract modifications is reportable to the USAF Technical Airworthiness Authority (TAA) (e.g. as documented in the

Airworthiness Determination Form (ADF)), then the contract shall support USAF Airworthiness

Board meetings as required. In the event that the USAF TAA determines there are non-compliances against the approved certification criteria pertaining to the system integration effort, the Contractor shall support the associated System Safety Risk Assessment (SSRA)/RA 1210

Issue 3 process to enable the USG to mitigate the risks associated with non-compliant criteria.

DI-SAFT-80102C/T, A055 Safety Assessment Report

4.7.4 Post Compliance Report Delivery Support.

The Contractor will provide email and telephone support after delivering the DT MACC

Compliance Report to provide clarification and additional information necessary to obtain the

DT Military Flight Release (MFR). If the determination is made that the contract modification is reportable to the USAF Technical Airworthiness Authority (TAA) (e.g. as documented in the

Airworthiness Determination Form (ADF)), then the Contractor shall support USAF

Airworthiness Board meetings as required.

4.7.5 Engineering Tasks and Studies

The Contractor shall undertake engineering tasks and studies at the written direction of the contracting officer. The PCO will communicate the scope of the effort via a written task description. Examples of tasks that could be directed under this section include engineering analyses, requirements development, hardware/software prototyping and qualification, demonstrations, and tests. The Contractor shall submit a technical report for each directed engineering task. DI-MISC-80508B/T, A030 Engineering Task Report; DI-MISC-80508B/T, A031 Trade Study Report

The Contractor shall provide a summary of the results of each tasking and study in a technical report. The Contractor shall provide additional documentation as described in each task description.

4.7.6 Development Testing

The Contractor shall support the government-led TME test program for verification of the capability specifications conducted in accordance with government-approved objectives and processes. This process includes Test Kick-off, Test Plan generation, Test Plan Working Group

(TPWG) meetings, Technical Review Board (TRB)/Safety Review Board (SRB) meetings, Test

Readiness Review (TRR), SIL/HILL, and Ground and Flight Test, and generation of Flight Test

Cards, Test Observations and Issues (TOIs), quick look reports, and test reports. The Contractor shall coordinate the scheduling of test events and resources with the Government Flight Test

Engineer (FTE). The Government program office will be responsible for ensuring test resources are made available in accordance with development and test schedules and will provide coordination and interface with other Government certification and support groups. Flight testing shall be conducted in accordance with a Government approved test plan. DI-NDTI-80566A/T, A048, Test Plan, DI-NDTI-80809B, A049 Test/Inspection Report

4.7.7 Test Information Sheet

The Contractor shall prepare and submit a Test Information Sheet (TIS) to convey recommendations for test activities, across SIL/HILL, Ground and Flight, and to provide artifacts to support requirements verification, with updates at PDR and CDR. The TIS shall include requirements traceability, test methodology and success criteria. DI-QCIC-81536A/T,A050, Test

Information Sheet(TIS)

4.7.8 Test Facilities

The Contractor shall update hardware and software in the System Integration Laboratory (SIL), Hardware in the Loop Laboratory (HILL), and other facilities (test benches, tools, etc.) as necessary to support the MQ-9 Block 1/5 REAPTM SYSTEM integration TME development and test efforts. The Contractor shall update all simulations/test equipment necessary to achieve adequate test fidelity in the SIL/HILL, and other facilities to support development and test. Prior to upgrading test facilities, the Contractor shall notify the Government of all changes or updates to Contractor facilities, Government facilities, and support tools (e.g. models and simulations) associated with this effort.

4.7.9 T-2 Modification

The Contractor shall build and delivery of T-2 modification kits as necessary for the aircraft, the

GCS and the GSE to support MQ-9 Block 1/5 REAP system integration TME testing at the

SIL/HILL, and Gray Butte Flight Test Facility. The Contractor shall install and conduct functional and fit checks on the T-2 Modification kits, and update production and retrofit drawing packages, as required. The Contractor shall prepare and submit T-2 information to support government to generate the modification packages. DI-MISC-81562/T, A040 T2

Modification Package

4.7.10 System Integration and Test

Contractor shall perform integration and factory test of the REAP™ equipment at their facility with support from subcontractors.

4.7.11 Platform Integration and Test

Contractor and subcontractors shall perform MQ-9 Block 5 platform integration, ground, and flight test of the REAP™ equipment, estimated as a four week effort, at MARCH ARB, California. Flight testing shall be conducted in accordance with a Government approved test plan (DI-NDTI-80566A/T, A001) Contractor shall perform MQ-9 Block 5 platform integration, ground, and flight test of the REAP™ equipment for six weeks, to be followed by another 6 weeks for the MQ-9 Block 1.

4.7.12 REAPTM SYSTEM Operational Utility Evaluation

Contractor shall support Operational Utility Evaluation effort for the MQ-9 Block 5. OUE will not be required for MQ-9 Block 1.

4.7.13 Spectrum Certification

The contract shall provide any and all such information as may be required to complete the certification process and obtain National Telecommunications and Information Administration

(NTIA) and Military Communications-Electronics Board (MCEB) approval of all spectral dependent equipment developed or integrated into MQ-9 system under this contract.

DI-EMCS-81827, A053 Spectrum Certification Spectral Data

4.8 Security Management & Program Protection

In order to reduce program vulnerabilities and to protect controlled unclassified information technologies from inadvertent disclosure, the Contractor shall implement the operations security

(OPSEC) countermeasures described in the MQ-1/MQ-9 Program Protection Plan, Annex E. The

Contractor shall mark and protect documents produced in the course of executing this contract in accordance with the MQ-1/MQ-9 Program Security Classification and Declassification Guide.

4.9 The Contractor shall utilize DoD 5200.39 and program office provided evaluation criteria to conduct a Critical Program Information (CPI) evaluation and Criticality Analysis. The

Government will provide MQ-9 protection plan annex B as GFI within 30 days of contract award.

4.9.1 Per 5200.39, the Contractor shall update the Program Protection Implementation Plan

(PPIP) documenting the company's protection plan for system CPI, both legacy CPI still resident in the MQ-9 software as well as any new CPI identified in the TME. This plan should use the countermeasures outlined in the MQ-9 Program Protection Plan (PPP), Annex C as a guide for the completion of the PPIP. The update to the PPIP will remain unclassified.

4.9.2 The Contractor shall implement the operations security (OPSEC) countermeasures described in Annex E of the MQ-1/MQ-9 PPP.

4.9.3 The Contractor shall provide an Anti-Tamper Plan recommendation based upon the CPI evaluation results. If necessary, the Contractor shall provide Anti-Tamper Plan(s) and corresponding verification test support sufficient to receive final approval from

SAF/AQL.

4.9.4 The Contractor shall mark and protect documents produced in the course of executing this contract in accordance with the MQ-1/MQ-9 Security Classification Guide, the Big

Safari Security Classification Guide, DoD 5200.39 and adhere to DFARS Clause

252.204-7012, safeguarding of Unclassified Controlled Technical Information, and protection FOUO/Proprietary Information.

4.10 Cybersecurity

4.10.1 The Contractor shall identify the delta system impacts to the baseline (Block 1 ER, Block

5, Block 5 ER, Block 15/25 and 30 GCS; Block 5 MQ-9, Portable Ground Terminal) using NIST 800-53 and AFLCMC/EZAS overlay controls.

4.10.2 The Contractor shall implement the applicable security controls and apply the appropriate guidelines outlined in the Defense Information Systems Agency (DISA) Security

Technical Implementation Guides (STIGs) and DODI 8500.01.

4.10.3 The Contractor shall provide Risk Management Framework (RMF) documentation to support the Assessment and Authorization under the DODI 8510.01 RMF.

4.10.4 The Contractor shall perform a Design Code Software Assurance Evaluation (DCSAE) utilizing a government approved source code analysis tool on the final software release of the code comprised in the MQ-9 REAPTM SYSTEM Integration Effort. The deficiencies, defects, and anomalies that are identified from the DCSAE tool shall be analyzed to determine technical details and validity of the findings. The contractor shall provide a report of their findings with recommended corrective actions. The report should contain a listing of all findings identified by the DCSAE tool and analysis on the findings. The contractor shall provide an unedited copy of the raw output from the

DCSAE tool in the native file format. Raw data generated by the DCSAE tool shall be treated as Unclassified/FOUO. The technical analysis shall be treated as classified and classified SECRET when submitting the DCSAE Report. DI-MISC-80508B/T, A033, Design Code Software Assurance Evaluation

4.10.5 The contractor shall utilize the DCSAE tool throughout the software development process and resolve new Critical/High findings identified by the DCSAE tool. Any new

Critical or High findings that cannot be resolved within the scope of this software release must be coordinated with the government prior to final software release for risk acceptance.

4.11 Information Assurance Approach

Contractor shall update the Information Assurance documentation provided as part of REAPTM

SYSTEM integration.

Relating to the aircraft, contractor will perform the following activities:

The contractor shall identify the delta system impacts to the baseline (MQ-9 Block 5 and

Block 1) NIST 800-53 and AFLCMC/EZAS overlay controls.

The contractor shall identify the delta system impacts to the baseline (Block 15 and 30

GCS; Block 5 and Block 1 MQ-9) NIST 800-53 and AFLCMC/EZAS overlay controls.

The contractor shall implement the applicable security controls and apply the appropriate guidelines outlined in the DISA Development Security Technical Implementation Guide

(STIG).

The contractor shall provide Risk Management Framework (RMF) documentation to support the Assessment and Authorization under the DODI 8510.01 RMF.

4.12 Configuration Management

The Contractor shall conduct configuration management (CM) in accordance with the current approved GA-ASI Configuration Management Plan, ASI-00015 using MIL-STD 61A as a guide.

Major contract changes, engineering changes and deviations/waivers shall require Government approval. The Contractor shall maintain the existing CM program and shall flow down the same

CM requirement to their subcontractors.

4.12.1 Configuration Changes and Variance

The Contractor shall not manufacture items for acceptance by the Government that incorporate a known departure from the approved specifications unless a Request for Variance (RFV) has been submitted and approved in accordance with the requirements of this SOW. The RFV request shall be processed and submitted in accordance with Configuration Management Plan. DI-SESS-80640D, A057,Request for

Variance

4.12.2 Engineering Change Proposal and Contract Change Proposals

The Contractor is required to submit an Engineering Change Proposal (ECP) or Contract Change

Proposal (CCP) for Government approval prior to implementing any changes to the technical or contractual requirements. An ECP or CCP shall include the documentation by which the change is described and recommended. The ECP shall also include a complete analysis of the technical, interface, cost, schedule and logistic impacts of the proposed change. All ECPs and CCPs shall be prepared in accordance with this SOW and Configuration Management Plan. DI-SESS-80639D/T, A056, Engineering

Change Proposal (ECP); DI-ADMN-81401B/T, A004 Contract Change Proposals (CCP)

4.12.3 Configuration Status Accounting

The Contractor’s CM system shall capture complete product configuration status, configuration documentation and baselines necessary to establish or reconstruct all as-designed, as-planned, as-built configurations of production systems. The Contractor shall also ensure that all approved changes to the

“as delivered” configuration are documented in the status accounting record for each asset delivered.

4.12.4 Data Management

The Contractor shall develop and submit all data in accordance with contract requirements and shall maintain revision/version control over delivered data. The Contractor shall maintain the data at their facility and at an on-line data library with controlled access for all data formally submitted under this contract. The Government shall have access to the data during the

Contractor’s normal.

4.13 Product Support Management

The Contractor shall designate a single POC who is responsible for managing and directing the

Integrated Logistics Support (ILS) tasks with respect to this effort. The responsibilities for the product support manager shall include providing program status, a program schedule(s), conducting supportability analysis, and providing support to required Contractor and

Government meetings.

4.13.1 Integrated Logistics Support Management Team

The Contractor shall support an Integrated Logistics Support Management Team (ILSMT) on a quarterly basis for the duration of this effort. The ILSMT shall identify, review, approve, and integrate the 12 IPS elements for the specific modifications and capabilities being implemented in accordance with this SOW. The Contractor shall reference AFI 63-101/63-131/20-101 and

AFPAM 63-128 as guides

4.14 Supply Support

4.14.1 Development Spares

The Contractor shall recommend and procure sufficient development spares to support operational assessment/test, and training for this SOW. The Contractor shall consider spares already procured or in inventory in determining the total requirement and procurement recommendation. The Contractor shall explain all assumptions, methods, or models used to formulate the spares proposal. DI-PSSS-80134B/T, A069, Proposed Spare Parts List

4.14.2 Product Support Analysis

The Contractor shall conduct and perform product support analysis (PSA) tasks for the capabilities/modifications applicable to this SOW: Using MIL-HDBK-502A as a guide, the

Contractor shall conduct and perform necessary PSA to include Reliability-Centered

Maintenance Analysis (RCMA) and Level of Repair Analysis (LORA) to determine, define, identify, document, and submit logistics support elements and data requirements. All PSA efforts, Logistics and Logistics Product Data (LPD), and guidance under the PSA will be supported and reviewed by a Government/Contractor ILSMT approach with the Government

ILSMT chair or Product Support Manager (PSM) having the required final decision authority.

PSA efforts may be tailored with recorded agreement of the ILSMT and approval of the

Government ILSMT chair or the PSM. LMI inputs and output deliverables and reports shall be based on the…