Draft_UAS_ISR_PWS.docx

DRAFT

PERFORMANCE WORK STATEMENT (PWS)

FOR THE

UNMANNED AIRCRAFT SYSTEMS

INTELLIGENCE, SURVEILLANCE, AND RECONNAISSANCE (UAS ISR)

SERVICES CONTRACT

10 NOVEMBER 2016

NOTE: ANY NAVY REFERENCES/PUBLICATIONS IDENTIFIED WITHIN THIS DOCUMENT WILL BE REALIGNED AT A LATER DATE TO MEET AIR FORCE EQUIVALENT/STANDARDS.

RECORD OF REVISIONS

UAS ISR Services

PWS - 1

As identified within this PWS - SECTIONS B – M to include CDRLs and Appendices are currently in development and will be provide once the Request for Proposal is released.

SECTION A

DESCRIPTION OF SERVICES

SCOPE OF WORK

Mission

The Land-Based Unmanned Aircraft Systems Intelligence, Surveillance, and Reconnaissance Services (UAS ISR) mission is to support force protection at airfields in Afghanistan by providing up to 600 hours of full motion video coverage per month using UAS vehicles equipped with electro-optic, infrared, and midwave infrared imagery systems.

Scope

This Performance Work Statement (PWS) details requirements for 24-hours per day, seven (7)-days per week (24/7) availability of Unmanned Aircraft System (UAS) Intelligence, Surveillance, and Reconnaissance (ISR) services. The contractor shall provide all required resources and personnel to perform all efforts necessary to execute pre-deployment, deployment, and post-deployment activities as defined herein. The contractor shall utilize a UAS that provides ISR capability to land-based sites as designated by the US Government. Unless otherwise stated, all requirements of this PWS are Firm Fixed Price.

SYSTEM REQUIREMENTS

Air Vehicle (AV)

The AV shall be capable of executing a preprogrammed flight plan.

AV External Lighting.

Night Vision Device (NVD) Compatible Anti-Collision Lighting: The AV shall have an Infrared (IR) anti-collision lighting subsystem (providing a night visibility range of 3+ statute miles) producing energy emitted in a 360 degree pattern around the AV +30 degrees (above) and -30 degrees (below) the horizontal plane of the AV. The IR-light intensity shall be at least of a Class B Night Vision Imaging System (NVIS) radiant intensity (NRIb) of 2.31 E-04 NRI. The Ground Control Station shall have the capability to turn the IR anti-collision light on or off.

Each AV shall be capable of accurately adapting to dynamic, in-flight re-tasking instructions.

The AV shall possess autonomous Loss of Link (LOL) behaviors to include loiter for a predetermined length of time in the event of sustained loss of control link. If the control link cannot be reacquired, the AV shall execute preprogrammed instructions resulting in a control-link recovery at a pre-determined end point. If control-link cannot be recovered, a mission termination maneuver shall be executed, such that the AV is destroyed without risk to friendly forces or non-combatant personnel.

The table below (Table 1) outlines the performance that the AV shall be capable of achieving to fulfill the required ISR services. The AV with full fuel and payload shall be capable of takeoff, operation, and recovery while operating in the environmental conditions described in Table 1.

Air Vehicle Performance Specifications

-20 to +140F 95% Relative Humidity

Inches/Hour

Surface Obstacles/Depressions Throughout, up to 1 Foot Depth/Height

Table 1 Air Vehicle Performance Specifications

The AV shall be configurable with Electro-Optical (EO) and Infrared (IR) payloads. The AV is not required to be simultaneously configurable with both payloads.

It is desired that the AV be simultaneously configurable with both Electro-Optical (EO) and Infrared (IR) payloads/sensors. Only one of these two optical payloads/sensors shall be required to be operating/active at any given point in time. The active payload/sensor shall be selectable from the GCS while the AV is in-flight, including the capability to switch between active payloads/sensors from among those with which the AV is configured.

The AV shall capable of accepting modular payloads. Modular payloads are defined as payloads that can be replaced or interchanged with the previously-installed EO or IR payload(s) within one to two hours (elapsed time). Modular payloads may be government provided.

The AV shall be simultaneously configurable with both an optical payload/sensor (either EO or IR) and an additional Tactical Compact Communications Relay (TCCR) modular payload. The TCCR shall have a minimum Ground-Relay-Ground range of 100 nautical miles and support encrypted and non-encrypted “bent-pipe” voice and data transmission.

At steady-state cruise power setting, the AV shall provide sensor data IAW paragraph 2.6.2.4, at an altitude of 3,000 feet above the ground and slant angle of 45 degrees. At the stated flight conditions the AV shall remain acoustically non-detectable per MIL-STD-1474D, Level 1, Requirement 2 conditions (quiet rural area with the closest heavily used highway and community noises at least 2.5 miles away).

The UAS shall possess an autonomous recovery wave-off feature, with operator-override capability. When threshold conditions required for successful recovery cannot be achieved, the UAS autonomously commands the AV to wave-off (abort its recovery).

Fuel Additives:

Lubricant Engine Additives: Engine lubricants are allowed and must be provided by the contractor.

Non-Lubricant Additives: Additives other than engine-lubricants must be provided by the contractor and shall meet the following criteria:

All additives and their related systems must be capable of being approved via the NAVAIR Flight Clearance process (processes (see paragraph 4.1.1.1).

All additives shall be assessed as potential hazardous material(s) to determine the risk to the UAS, ship and ship systems, personnel and the environment during stowage, handling, operations, and disposal.

The UAS shall possess adequate airworthiness to ensure integrity and control of the air vehicle during launch and recovery phases, to confine the air vehicle flight path to within suitable operational areas and to reliably terminate the air vehicle within a suitable crash zone. For rotary wing aircraft, the air vehicle shall be free from ground resonance and have sufficient dynamic system and airframe integrity to preclude catastrophic failure during ground operations. Evidence that the UAS meets the aforementioned airworthiness criteria shall be documented as part of the Category 3 Interim Flight Clearance (IFC) data cited in paragraph 4.8.

System Footprint/Mobility and Transportation Requirements

System Footprint. The terrain and tactical situation will dictate the specific site selection and available geographic footprint, as generally defined within Table 1.

Mobility and Transportation Requirements

Land-based launch and recovery equipment shall be capable of employment by contractor personnel in less than 30 minutes.

All UAS and supporting equipment shall be air transportable by C-130 and CH-53 (internally or externally loaded, for the H-53) aircraft. Multiple loads are acceptable. The contractor shall be responsible for any required shipping containers.

Each UAS shall be capable of being set-up and operational within 12 hours of arrival at a forward operating location.

Additionally, a functioning UAS in forward operating locations shall be able to be disassembled and stowed for transportation in less than 12 hours of tasking.

MTMCTEA4 Pamphlet 70-1 Transportability for Better Deployability is provided for guidance.

MIL-STD-209K, Interface Standard for Lifting and Tie down Provisions is provided for guidance.

Hub or Hub and Spoke Operations

A hub and spoke operational model has the hub as the center of operations and the spoke as the downrange extension which allows the system to continue to operate at a distance from the central hub. The HUB is defined as a location wherein the contractor shall be responsible for all activities necessary for UAS operations, including but not limited to: Administration, Mission Planning, AV Launch and Recovery, AV Command & Control (C2), Networked Data Dissemination, and Maintenance and Logistics Support. The SPOKE has the identical C2 capabilities of the hub but lacks the capabilities of AV Launch and Recovery, and Maintenance and Logistics Support. The spoke will participate in the administration and mission planning processes, but will not have the same stand-alone capabilities as the hub.

ISR-Services operations shall be primarily of a "Hub" nature, where the AV is launched, operated/controlled and recovered from a single GCS or hub. The contractor shall provide the capability to employ ISR-services using a hub and spoke configuration, and coordinate the requirement with the Contracting Officer’s Representative (COR) and the Liaison Officer (LNO).

The contractor shall provide sufficient resources to conduct ISR services in the hub and spoke model at the following levels of Sensor Data Hours per month:

Ground Control Station (GCS) Requirements. The GCS shall be installed within proximity to the Combat Operations Center (COC)/Tactical Operations Center (TOC). Short length cable runs to areas such as the COC/TOC should be expected.

The contractor shall provide the ability to maintain simultaneous positive control of the air vehicle and the payload.

The contractor shall have the capability of directing in-flight re-tasking and controlling payload sensors.

The contractor shall have the ability to provide full motion video feeds directly to a contractor-provided display in the Combat Operations Center (COC) / Tactical Operations Center (TOC) within a half mile of the contractor’s launch and recovery site.

The contractor shall have the ability to operate with its antenna/antennae located up to 500 feet away from the GCS.

The GCS shall provide the capability to display and output video imagery, and metadata into a classified network (low-to-high) via the government provided Cross Domain Solution (CDS) (See paragraph 2.6.5). The contractor shall also provide imagery with all meta-data removed that can be releasable to Afghanistan.

The contractor shall operate on electrical power provided by their own diesel-generator(s). The Government will provide the diesel fuel for the generators.

As applicable, the contractor shall use a GCS at each spoke. The spoke-based GCS shall provide Level 4 interoperability per STANAG 4586 and shall have human-interface characteristics identical to that of the hub-based GCS.

Positive Control: The UAS shall provide for a qualified operator to be in control of the UAV, at any time that intent-for-flight exists (intent-for-flight shall be as defined in the respective UAS’ operating manual / Standard Operating Procedures (SOP)).

The operator shall be capable of expeditiously responding to system malfunctions, emergencies and Air Traffic Control (ATC) direction.

A UAS with an autopilot or programmable mode capability can be considered under control with such mode engaged provided the responsible and qualified operator maintains continuous situational awareness, and can alter the UAV’s airspeed, altitude and heading by their specific actions.

Communication, Navigation, and Identification Systems (CNI)

Communications (Datalinks Operation)

The contractor shall utilize either L-3 Communications’ Bandit or Vortex radios for video downlink.

The contractor provided Datalinks shall be capable of operating at a minimum range of 50 Nautical Miles (NM) with unobstructed Line of Sight (LOS).

The contractor provided Datalink shall provide hemispherical, 360 degrees of coverage, to maintain direct unobstructed LOS communications.

Communications (Spectrum): Specific bands and/or frequencies required will be defined within the TO or as part of the pre-deployment work-ups (reference 3.1.1.7).

The contractor shall provide a field configurable Command and Control (C2) communications architecture that allows, at a minimum, L, S, and C Band configuration.

The contractor shall provide a field configurable sensors payload communications architecture that allows, at a minimum, L and S Band configuration if the sensors require a separate datalink.

Communications (Encryption)

The contractor shall utilize FIPS-197 compliant Advanced Encryption Standard (AES) encryption on all data communication links; Electronic Code Book (ECB) mode shall not be used.

The system shall be able to enable/disable AV datalink encryption from the GCS, while the AV is airborne.

Communications (Remote Video Terminals (RVT))

The AV shall provide EO/IR video, with Key Length Variable (KLV) metadata, to an RVT at a minimum range of 5 NM from the AV.

The contractor shall provide a communications architecture that allows for the Rover (IV+) Series, VideoScout or OSRVT system.

Navigation (Global Positioning System (GPS))

The contractor shall only use Selective Availability Anti-Spoofing Module (SAASM)-compliant Precise-Positioning System (PPS) GPS.

The contractor shall utilize DS101 port(s) to receive SAASM encryption keys.

The contractor shall incorporate a method for the user interface to manually select C/A mode (L1) on the receiver.

The contractor shall utilize a GPS receiver that will automatically select C/A mode (L1) on the receiver when the GPS cryptographic keys are not loaded or are expired.

Identification (Transponder/Identification). The AV shall have a Mode 3/C transponder with “IDENT” capability, controllable from the GCS.

Data Products

Full Motion Video (FMV) & Still Imagery

The contractor shall be capable of injecting UAS sensor data into host unit’s PED system(s).

The system shall be able to autonomously maintain uninterrupted tracking of a stationary or moving object, while in visual contact.

Full Motion Video Output & Quality

The contractor shall provide an output of Motion Imagery Standards Profile (MISP) MPEG-4, Part 10, or H.264 format FMV, through an MPEG 2 transport stream.

If standard definition motion imagery is used then it shall be Motion Imagery System Matrix (MISM) Level 3 compliant to MISP recommended practice 9720d.

If high definition motion imagery is used then it shall be MISM Level 9 compliant to MISP recommended practice 9720b.

EO/IR Video Output Quality: During daytime and nighttime operations, the Contractor-provided system shall be able to not only identify a man, but also to identify what that individual is carrying; specifically the difference between a shovel and an AK-47 rifle, when exploiting UAS video as defined in RFP Section L.

The sensor data hours required under Section B of this PWS are estimated to be distributed between EO and IR as follows but may vary:

Still Imagery Output & Quality

The contractor shall provide EO still images in National Imagery Transmission Format (NITF) 2.1 format, captured from the FMV stream (CDRL A0XX). The contractor-provided system shall be capable of producing EO output meeting or exceeding the National Image Interoperability Rating Scales (NIIRS) rating of 8.4, when taken from the UAV at an altitude of 3000 ft Above Ground Level (AGL) at a 45 degree slant range and viewed via a VideoScout MC2 Processing, Exploitation, Dissemination (PED) (CDRL A0XX).

The contractor shall provide IR still images in NITF 2.1 format, captured from the FMV stream (CDRL A0XX). The contractor-provided system shall be capable of producing IR output meeting or exceeding the NIIRS rating of 7.2, when taken from the UAV at an altitude of 3,000 ft AGL at a 45 degree slant range and viewed via a VideoScout MC2 PED (CDRL A0XX).

Metadata

The contractor shall provide metadata in compliance with MISP Minimum Metadata Set Standard 0902, with all digital FMV.

The contractor shall provide metadata in compliance with MISP Standard 102 “Security Metadata Universal and Local Sets for Digital Motion Imagery.”

The contractor shall provide any metadata not covered in MISP 902 or 102 via MISP Standard 0601 “UAS Datalink Local Metadata Set.”

Cross Domain Solution (CDS) Interface

The contractor shall provide for a single Cat 6a cable with a male RJ45 connector to serve as the connecting element from the GCS to the Government provided CDS.

The contractor shall provide a data flow from the GCS to the government provided CDS that adheres to the following:

FMV must be in the form of MPEG-4, Part 10, or H.264 compliant FMV.

FMV must be use the MPEG-2 transport stream.

FMV must use the User Diagram Protocol.

All metadata must follow the KLV standard and be delivered as KLV over Internet Protocol (IP).

The GCS must have the ability to configure the port on which the FMV and metadata traverses.

Sensor Point of Interest (SPOI). The contractor shall provide SPOI spatial location accuracy for a stationary object of 20 meters Circular Error (CE), at accuracy of 90%, and from an altitude of 3,000 ft AGL at a 45 degree slant range, within 60 seconds.

Data Dissemination & Storage Requirements

The video and metadata recorded from each mission shall be stored by the Contractor for one week.

As directed, the video/metadata shall be capable of being fed directly to the Government-provided CDS via direct-data-transmission in real-time. Video/metadata shall also be consolidated on Digital Video Disks (DVD), or suitable storage device (external hard drive) and provided weekly to the LNO.

All data, video, and information collected shall be considered the property of the Government.

After the video/metadata is turned over to the Government, via DVD, Hard Disk Drive (HDD), and/or via direct-data-transmission, the contractor shall destroy/delete the data on the contractor system upon direction from the Government. The data destruction/deletion should occur on a periodic basis; however, at the end of the deployment the government shall confirm that all data has been deleted/destroyed from the contractor’s systems.

The contractor shall have no rights to use the video imagery, metadata, or specifics of the operation (expressed or implied).

Recommended Best Practices

MIL-STD-1472F; Human Engineering, Design Criteria for Military Systems, Equipment, and Facilities, is provided for guidance and as recommended best practice.

MIL-STD-810G; DOD Test Method Standard for Environmental Engineering Considerations and Laboratory Tests, is provided for guidance and as recommended best practice.

CONTRACTOR PROVIDED SERVICES

PRE-DEPLOYMENT REQUIREMENTS

System Certification: Prior to deployment, the contractor shall support the following essential certifications/qualifications necessary to operate the system. Specific requirements will be determined based upon the individual contractor’s technical solution, but will likely include data, hardware, and personnel. These certifications/qualifications shall include (but not necessarily be limited to) the following:

The contractor shall submit System Description Documents (SDD) containing engineering data necessary to support a Category 3 Interim Flight Clearance IAW NAVAIRINST 13034.1D (CDRL A0XX), See section 4.8 of this PWS.

As an element of the SDD, the Contractor shall submit a System Safety Plan and Hazard Analysis IAW NAVAIRINST 5000.21B, Naval SYSCOM Risk Management Policy, and NAVAIRSYSCOM Letter 5100/Ser AIR-4.0/026 of 14FEB2011, Incorporation of Revised Cost Threshold for Catastrophic Severity into System Safety Risk Assessments (see Appendix X).

The contractor shall provide Electromagnetic Environmental Effects (E3) and ElectroMagnetic Interference (EMI) data to demonstrate their design practices pertinent to MIL-STD-464A requirements (CDRL A0XX) as follows:

Intra-system ElectroMagnetic Compatibility (EMC) shall be maintained between AV, GCS, and CNI and between the individual subsystems and equipment of each.

The AV shall be compatible with its external Radio-Frequency (RF) ElectroMagnetic Environment (EME).

CNI equipment shall be compatible with its external RF EME or internal EME, as applicable.

The GCS shall be compatible with the internal EME.

The UAS shall not present an electromagnetic radiation hazard to personnel, ordnance, or fuel.

The UAS shall not present an electrostatic discharge hazard to personnel, ordnance, fuel, electronics or the proper operation of radio receivers.

The contractor shall provide Material Safety Data Sheets and identification IAW FED-STD-313D (CDRL A0XX).

Personnel Considerations

In accordance with Contract Clause 252.225-7040 “Contractor Personnel Authorized to Accompany U.S. Armed Forces Deployed Outside The United States” 252.225-7040(e)(vii), prior to deployment contractor personnel designated to deploy shall attend a one-week military-run training center such as the National Deployment Center (Camp Atterbury IN), CRC (Ft. Benning GA), or the Deployment Processing Center (DPC) (Camp Pendleton CA). A web-based source is NOT approved by the Contracting Officer.

ISOPREP: All personnel traveling OCONUS are required to complete a DD Form 1833, Isolated Personnel Report (ISOPREP). This applies to all military, civilian, and contractor personnel supporting forces in CENTCOM AOR. Forces under the Operational Control of USASOC or USSOCOM are exempt from this requirement and will follow USSOCOM guidance to meet the pre-deployment requirement. ISOPREPs may be submitted either on-line via the Pre-OCONUS travel File (PRO-File) system or via paper form. The PRO-File system is available at the following site: < http://www.jrtc-polk.army.mil/Transition_team/Files_&_Images/files/ISOPREP.pdf >. The ISOPREP form is available at the following site: < http://www.dtic.mil/whs/directives/infomgt/forms/eforms/dd1833t.pdf >

The UAS shall conform to DoD security guidance regarding Information Assurance (IA), including all appropriate controls as defined by the Mission Assurance Category, and Data Classification of the system in accordance with DoD Directive 8500.1, DoD INST 8500.2, DoDI 8510.01, and CJCSI 6510.01.

The UAS shall protect Critical Program Information (CPI) from reverse engineering exploitation and incorporate Anti-Tamper features as required by DoDD 5200.39, DoDI 5000.2, and DoD Interim Defense Acquisition Guidebook. Protection measures implemented must ensure that reverse engineering, replication, modification by an unauthorized nation or organization would require a capability comparable to a US National Laboratory with significant time and funding. The protection capabilities must prevent unauthorized access to critical software functionality regardless of the system configuration. Source readable software is not to be in deployed systems.

The UAS shall adhere to the encryption requirements as defined in the “Encryption of Sensitive Unclassified Data at Rest on Mobile Computing Devices and Removable Storage Media” Memo issued by the DoD CIO on July 03, 2007 (CDRL A0XX).

The contractor shall provide data, engineering, test articles, equipment, and test support for Authority to Operate (ATO).

The UAS shall comply with OPNAV Instruction 2400.20F, Electromagnetic Environmental Effects (E3) and Spectrum Supportability Policy and Procedures. The contractor shall provide the Application for Equipment Frequency Allocation spectrum analysis and allocation IAW DD1494.

System Description Documents (SDD): The contractor shall provide detailed and comprehensive system description documentation data-package including both physical and communications/data-aspects of the system. The contractor shall provide a detailed SDD including data necessary to support the Category 3 Interim Flight Clearance (IFC) as well as to validate the ability of their systems to comply with the integration and interface requirements listed within this PWS (CDRL A0XX).

Description of Physical System & Interfaces: This documentation shall completely describe the contractor’s technical solution. Data shall be sufficient to ensure that the UAS shall interface effectively with all government provided systems. This shall include all mechanical, electrical, environmental and other interfaces.

Description of Electronic-Data System & Interfaces: This documentation shall completely describe the contractor’s technical solution to ensuring that data flows from the contractor's GCS to the program-provided CDS. The documentation shall include a detailed description of all physical connections/interface(s) and any data flow(s) to include data format descriptions and port/protocol information for all data elements. The contractor shall also provide a sample data message of their metadata as part of the SDD.

Payload Interface & Flexibility: The contractor shall provide a detailed payload Interface Control Document (ICD) describing the payload interface with the AV and UAS, including the following minimum data (CDRL A0XX).

Maximum payload weight.

Maximum payload volume.

Electrical power available to payload.

Definition of the electronic data/control interfaces/connectors between payload and AV.

Maximum volume and shape-of-space available for payload.

Any other significant parameters that may affect the integration of new/alternative payloads into the AV.

Standard Operating Procedures.

The contractor shall develop with the Contracting Officers Representative (COR) and LNO a site specific Standard Operating Procedures (SOP) prior to activation of the site. The SOP will serve as a living document outlining daily operations procedures, flight planning resources, frequency coordination and deconfliction procedures, personnel, responsibilities, contact information and other vital information to assist mission accomplishment at the specific operating location.

The Standard Operating Procedures shall include a Communication Security (COMSEC) Memorandum of Understanding (MOU) with all sites for which operational support is provided. All MOUs shall be drafted by the contractor and the appropriate personnel at each site, normally the site’s Electronic Key Management System (EKMS) Manager.

The contractor shall order Net-40 Advanced Encryption Standard (AES) Bandit Keys (Test and Operational) from the National Security Agency (NSA). The contractor shall order Selective Availability Anti-Spoofing Module (SAASM) Keys (Test and Operational) from Strategic Command (STRATCOM). The contractor shall store all AES Bandit and SAASM Keys in a Government Services Administration (GSA) approved storage container. The contractor shall comply with NSA/CSS Policy Manual No. 3-16 minimum standards, procedures, specifications, and guidance for safeguarding and controlling COMSEC materials, including all Keying Materia (KEYMAN), Keys and Government Furnished Equipment (GFE) requirements.

The contractor shall perform site surveys at ordered deployment locations to implement integration/installation.

The contractor shall coordinate equipment needs, proposed locations, and shipping protocols to support the deployment and operations.

The contractor shall communicate any deficiencies noted to the designated COR and LNO.

The contractor shall have all Contractor Furnished Equipment (CFE) inventoried and accounted for.

The contractor operators will develop and maintain qualification and proficiency levels IAW the site specific SOP.

The contractor shall be responsible for system set-up and checkout at the operational site prior to commencing the deployment phase.

Pre-Deployment shall be complete upon completion of the first familiarization mission in the Area of Responsibility (AOR) and acceptance of the final checkout by the LNO.

Contractor’s SOP shall address the applicable elements of OPNAVINST 3710.7U, Chapter 14, that apply to daily flight operations.

Training Requirements. Individual TOs may identify training requirements that ranges from individual familiarization training to unit level field training exercises.

Deployment

The contractor shall meet or exceed a Mission Reliability Rate (MRR) of 95% as defined in the RFP Section H.

The contractor shall be capable of providing UAS/ISR services 24 hours a day, 7 days per week. Operations shall be conducted IAW contractor’s SOP.

The contractor shall be able to execute the routine daily flight operations schedule with 8 hours of advance notification.

The contractor shall respond to a launch request for a non-scheduled mission within 30 minutes, weather conditions permitting, when the site is operational and in an active standby status5.

Mission Duration

Mission Definition – Threshold & Definition

The contractor shall support mission requirements of up to 10 continuous on-station sensor data hours per mission of ISR services in daylight and/or darkness. A typical 12 hour mission includes up to 1 hour of flight time to station, 10 continuous hours of on-station sensor data, and up to 1 hour of flight time back to the recovery site. This may vary depending on the target location and operational needs. The LNO or Mission Commander will determine the point when sensor data is required. The average duty day includes the mission, refueling, LRE set-up and take-down, and pre-/post-flight maintenance. The daily flight schedule will be coordinated with the LNO.

It is desired that the contractor be capable of supporting mission requirements of up to 18 continuous on-station sensor data hours per mission of ISR services in daylight and/or darkness.

Surge Capabilities: The contractor shall be able to respond to urgent requests for surge services. Surge services may require operations beyond the typical mission and continue for several consecutive days. Surge services shall also include the capability to fly two (2) AVs simultaneously. Following surge flight operations the contractor shall be provided a corresponding recovery period by the LNO upon consultation with the site representative which will be reasonable to ensure deferred maintenance actions are completed to include all maintenance and log book documentation and status reporting, personnel rest, and overall safety of operations.

The contractor shall provide all environmental systems required to operate the GCS.

The contractor shall provide fuel to support the AV. Supply chain considerations necessitate the storage of a 60-day supply of fuel. Anything greater than a 60-day supply will be coordinated with the COR and the LNO.

POST-DEPLOYMENT REQUIREMENTS

Upon completion of the ISR task order, including any extensions or follow-on orders, the contractor shall disassemble and prepare for shipment all Contractor-Owned and Contractor-Operated (COCO) systems, equipment and spares and return all Government Furnished Equipment (GFE) to the Government to include Common Access Cards for accountability.

Upon completion of ISR performance, any contractor-owned data-storage media shall be turned-over to the Government for deletion/destruction of all data.

The Government will transport the contractor's equipment to a secure transshipment point within Theater. Thereafter, shipping of the contractor's equipment back to the contractor's point-of-origin will be at the contractor’s expense.

STAFFING REQUIREMENTS

The contractor shall staff each operational deployment with a team sufficient to provide the UAS/ISR Services. The contractor shall utilize professional and technically qualified personnel to perform the tasks outlined herein.

The contractor shall provide a CONUS-based Project Manager as the single point of contact with the authority to act on behalf of the contractor on all matters as they relate to this contract including all administrative matters.

The contractor shall provide a Site Lead who will be responsible for support and management of this contract. The Site Lead shall also liaise with the COR/ LNO for fulfillment of contractual requirements. The site lead shall provide supervision for all employees and will be responsible for the safety and accountability of all contractor employees.

The contractor shall provide system familiarization training to Government host unit in the areas of safety, emergency procedures, flight planning and airspace de-confliction and data dissemination.

REPORTING REQUIREMENTS

The contractor shall prepare and submit, to the designated COR/ LNO, the following reports:

A consolidated Daily Report shall be submitted IAW (CDRL A0XX). This report shall include the following elements:

Service Hour Summary / System Status Report

Brief description of all incidents and mishaps

Personnel Report

Tracking of all equipment and parts shipments to and from theater

Employee Training: Training OIs shall be submitted to the CO for acceptance IAW CDRL A0XX.

The contractor shall provide a root-cause failure analysis of any system mishap or operational incident. The compliance-time for the final Root Cause Analysis (RCA) of the mishap/incident shall be within 120-days of the incident. In the event of any formal US government investigation(s) (e.g. JAGMAN, NAVSAFECEN, etc.), the contractor shall support the effort as required (CDRL A0XX).

The contractor shall brief the Government via VTC/teleconference once per week with a focus on parts required for all down aircraft or equipment and the usage and status of mission critical spare parts, including tracking of all equipment and parts shipments to and from theater. VTC/teleconference may also encompass discussion of technical issues affecting UAS operations.

The contractor shall report all COMSEC incidents in accordance with the National Security Telecommunications and Information Systems Security Instruction (NSTISSI) Number 4003, Annex B. The contractor shall utilize a secure means such as Secure Voice over Internet Protocol (SVoIP) to report COMSEC incidents.

TRANSPORTATION

The contractor will transport CFE from contractor’s facility to a Point of Embarkation within the Theater (expected to be Kandahar, Afghanistan or Bagram Air Base, Afghanistan). The contractor shall make in-theater parts and sparing provisions to sustain normal operations in light of possible government transportation delays of up to 45 days. At the end of the deployment the contractor shall transport CFE to the contractor’s facility.

The contractor shall be responsible for arranging transportation of contractor personnel to a point of embarkation within Theater (expected to be Kandahar, Afghanistan or Bagram Air Base, Afghanistan). The contractor shall be responsible for arranging transportation of contractor personnel from the point of debarkation within Theater to home station.

The contractor is responsible for replacement of personnel forward and coordination of such transport to and from.

The contractor shall be responsible for all on-site storage management and tracking of spare parts.

The contractor shall ship ISR systems and equipment in accordance with MIL-STD-2073-1D, MIL-STD-129P, and PAM 70-1.

The contractor shall be responsible for shipment of parts and spares to the Theater. The contractor will coordinate with the Government for transfer from the Theater location to the deployed site.

Contractor or equipment relocation shall not be permitted without prior Government authorization by the COR.

Security

The security clearance level will be in accordance with the DD Form 254 Contract Security Classification Specification.

The contractor shall safeguard classified information and classified materials, obtain and verify personnel security clearances, verify security clearances and indoctrination of visitors, control access to restricted areas, and protect Government property, automated/non-automated management systems and data.

The contractor’s management system shall prevent the unauthorized disclosure of classified and sensitive unclassified information.

The Government shall be immediately notified if any security incident or indication of a potential unauthorized disclosure or compromise of classified or sensitive information occurs.

Category 3 Interim Flight Clearance. The contractor shall provide all information and support necessary to obtain Category 3 IFC approval.

Training Requirements. Individual TOs may identify training requirements that range from individual familiarization training to unit-level field training exercises.

GOVERNMENT PROVIDED SUPPORT

The Government will provide a military liaison to assist the contractor to facilitate air space integration, mission coordination and deconfliction.

Upon completion of the contractor services, the Government will provide return transport for Contractor furnished equipment from deployed location to the nearest overseas logistics center. The Contractor will be responsible for shipping from there to the contractor’s facility.

The Government will provide all known applicable instructions, regulations, and excerpts as guidance.

The Government will assist the contractor with acquiring personnel passes, identification cards, and vehicle permits required in the performance of this contract in accordance with the contractor provided Personnel Rotation Schedule.

The Government will provide contractor personnel with deployment in-processing briefings to ensure understanding and integration into the operational environment.

The Government may provide transportation within the operating area to assist in the initial setup and relocation of the operational deployments as required. The Government will provide for transportation coordination within Theater.

The Government will establish a Quality Assurance Surveillance Program; it is not a substitute for quality control by the Contractor.

The Government will supply COMSEC Electronic Key device and COMSEC security and management as necessary, to include facilitating key requests from issuing agencies.

The government may provide UAS Payloads to include (Communication Relay, and/or Signals Intelligence).

The Government will supply KEYMAT for SAASM GPS as necessary.

The Government will provide the Cross Domain Solution hardware.

The Government will provide tactical and aeronautical maps/charts and DTED data as required /available prior to deployment.

The Government may provide technical support on any issues affecting UAS operations.

UAS ISR Services

PWS - 18