Attachment_1_-_PWS_-_UAS_ISR_--_22_Dec_17.docx

PERFORMANCE WORK STATEMENT (PWS)

FOR

UNITED STATES AIR FORCES CENTRAL COMMAND (USAFCENT)

UNMANNED AIRCRAFT SYSTEMS (UAS)

INTELLIGENCE, SURVEILLANCE, AND RECONNAISSANCE (ISR)

SERVICE

Solicitation Number: FA4890-17-R-0015-0004

Date: 22 December 2017

TABLE OF CONTENTS

SECTION A - DESCRIPTION OF SERVICES

1.0 SCOPE OF WORK

2.0 PROGRAM MANAGEMENT

3.0 UAS REQUIREMENTS

4.0 OPERATIONS AND MISSION SUPPORT

SECTION B – SERVICES SUMMARY

SECTION C – GENERAL INFORMATION

SECTION D – GOVERNMENT PROVIDED PROPERTY AND SERVICE

SECTION E – APPENDICES

ATTACHMENT 1 - COCO AIRCRAFT AIRWORTHINESS DATA PACKAGE (AADP)

SECTION A - DESCRIPTION OF SERVICES

1.0 SCOPE OF WORK.

1.1 Mission. United States Air Forces Central Command (USAFCENT) is the air component of United States Central Command (USCENTCOM), a regional unified command. USAFCENT is responsible for air operations (either unilaterally or in concert with coalition partners) and developing contingency plans in support of national objectives for USCENTCOM's 20-nation Area of Responsibility (AOR) in Southwest Asia.

1.2 Scope. The Department of the Air Force is acquiring Land-Based Unmanned Aircraft Systems (UAS) Intelligence, Surveillance, and Reconnaissance (ISR) Services to support force protection efforts at airfields located within the USAFCENT’s AOR. Current service locations are as follows:

1.2.1 Bagram Airfield, Afghanistan.

1.2.2 Kandahar Airfield, Afghanistan.

1.3 Objective. The objective of this Performance Work Statement (PWS) is to define the requirements for a Contractor-provided turn-key ISR service including, but not limited to labor, personnel and ISR hardware necessary to perform the ISR service mission while at land-based operational sites. The Contractor shall provide a non-developmental Contractor-Owned and Contractor-Operated (COCO) UAS ISR solution to perform operational, engineering, and sustainment efforts necessary to effectively execute pre-deployment, deployment operations, post-deployment, and engineering support activities. The COCO ISR solution is required to support ISR tasking occurring anytime (24-hours per day, seven (7) days per week). The ISR Air Vehicle (AV) system requirements, performance requirements, and operating sites are defined in Paragraph 3.0 – UAS Performance – of this PWS.

2.0 PROGRAM MANAGEMENT

2.1 Project Manager. 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 Project Manager or designated alternate shall be available to respond to Government inquiries within one (1) hour.

2.2 Program Management Plan. The Contractor shall develop, implement, and maintain a comprehensive management plan that addresses the Contractor’s management approach to ensuring personnel, resources, life cycle management, training, site management, employment in peace, time of war, evacuations, expeditionary site, and security throughout all locations of the contract. The plan shall also address the specific topics listed below. The Management Plan shall be provided not later than (NLT) 30-days after contract award and be updated annually in accordance with Appendix D - Deliverables.

2.2.1 Human Resources Plan. The Contractor shall provide overall management, supervision, personnel, and services necessary to execute requirements at the UAS ISR Sites, to include, but not limited to: hiring all personnel; determining how personnel will be qualified, certified, retained, and terminated; and following laws, directives, and regulations of the U.S. Government and Host Nation (HN). The Human Resources Plan shall include the Contractor’s staffing plan for each site.

2.2.2 Training Plan. The Contractor shall develop and maintain individual training records to document training requirements for UAS positions. The Contractor shall maintain each training record at the individual’s work location and make available to Government representatives upon request.

2.2.3 Site Management Plan. The Contractor shall provide effective site management services, leadership for contractor personnel, and be responsible for execution of all contracted UAS ISR site activities as defined in this PWS. The Contractor shall provide a primary and alternate point of contact (POC) for each site.

2.2.3.1 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.

2.2.3.2 The Contractor shall provide a Site Lead for each location who will be responsible for support and management of the site. The Site Lead shall also liaise with the Contracting Officer’s Representative (COR)/Liaison Officer (LNO) for fulfillment of contractual requirements. The Site Lead shall provide supervision for all Contractor employees and shall be responsible for their safety and accountability.

2.2.3.3 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.

2.2.4 Management Information System (MIS). The Contractor shall develop, administer, maintain, utilize and provide Government access to a MIS. The MIS location and access instructions shall be delivered to the Government NLT 30 calendar days after contract award. All deliverables shall be posted to the MIS as specified in Appendix D.

2.3 Performance Direction. The Contractor shall perform in accordance with the PWS or Contracting Officer’s (CO) direction. The Contractor shall notify the CO if direction outside the scope of this PWS occurs and shall not perform that work until such time it is authorized by the CO.

2.4 Meetings. The Contractor shall attend and support meetings and conferences convened by the CO. The Government will reimburse the Contractor for any Government-directed travel to support conferences, meetings, and reviews. Travel will be reimbursed IAW Section I of the contract.

2.4.1 Contract Kickoff Meeting. The Contractor shall participate in a contract kickoff meeting with the requirement owner, Government Program Manager (PM), CO, COR, functional representatives, and others as required. The Government will coordinate and schedule the kick-off meeting. The meeting is projected to occur within 30 days of contract award.

2.4.2 Program Management Review (PMR). The Contractor shall participate in PMRs with the requirement owner, PM, CO, COR, functional representatives, and others as required. The Government will coordinate and schedule each PMR with the Contractor.

2.5 Problem Management. The Contractor shall identify, document, and notify the Government of actual or potential Contractor program management problems and deficiencies, and report unresolved problems to the CO and PM. The Contractor shall report site-specific problems affecting mission accomplishment or Contractor performance to the Government PM within 12 hours; resolve at local level whenever possible.

2.6 Customer Notification. The Contractor shall notify affected personnel when any activities impact facility, equipment, and/or utility operations. The Contractor shall provide the job order and work request status to customers as requested/required.

2.7 Requests. The Contractor shall routinely provide information and/or recommendations on support and related functions to various agencies or higher headquarters as requested by the CO or PM.

2.8 Quality Management System (QMS). The Contractor shall implement a comprehensive higher-level QMS compliant with the most current SAE AS9100 standards, Section B – Service Summary, and Appendix C – Quality Management System Requirements.

2.8.1 Metrics. The Contractor shall develop, maintain, and analyze achievable metrics for program requirements, and continually explore opportunities for process improvements. The Contractor shall provide the Government access to the metrics.

2.8.2 Corrective Actions. The Contractor shall perform corrective actions for all identified Contractor program management problems and deficiencies IAW time frames specified by CO.

2.8.3 Compliance Requirements. The Contractor shall comply with applicable U.S. and HN laws, business practices, and restrictions as they pertain to management and execution of this contract.

2.8.4 Deliverables. The Contractor shall submit all deliverables in accordance with Appendix D - Deliverables.

2.9 Financial Management.

2.9.1 Financial Management Report. The Contractor shall prepare and submit a monthly financial management report in Microsoft Excel that reflects current and all previous fiscal year (FY) contract cost data (Appendix D - Deliverables). The following shall be included as a minimum:

2.9.1.1 A listing of cumulative authorized funding by contract modification and Contract Line Item Number (CLIN) for each FY, a listing of cumulative billing by CLIN, and a listing of cumulative funding by FY and CLIN.

2.9.1.2 A breakout of Firm-Fixed Price (FFP) funding status by CLIN for each FY showing total funded amount, cumulative billed amount, current month billed amount, and funds remaining.

2.9.1.3 A breakout of cost reimbursable funding status for each FY showing total funded amount, current month billed amount, funds remaining, cumulative percentage spent, and cumulative percentage remaining.

2.9.1.4 A listing of all CR travel invoices by FY showing the travel dates, brief description of the travel, and actual total cost per event.

2.9.2 UAS ISR Service Reimbursement. The Contractor shall invoice monthly in accordance with their proposed, and Government accepted, Milestone Payment Plan.

2.9.3 Travel Reimbursement.

2.9.3.1 Travel costs shall be based on estimated costs per FAR 31.205-46, Travel Costs. All trips shall be IAW regulatory requirements. All travel shall occur on an “as needed” basis, and associated estimated costs shall be presented to the COR and PM with a travel request at least five (5) business days prior to date of departure (CONUS), or at least ten (10) days in advance of minimum timeline necessary to obtain applicable access documents and start personnel processing requirements (OCONUS). All travel requests shall be coordinated and pre-approved in writing by the Government PM or COR prior to any trips.

2.9.3.2 The Contractor shall be responsible for all travel arrangements including airline, hotel, and rental car reservations, in addition to foreign travel processing requirements. Contractor employees shall be able to provide receipts for or evidence supporting associated travel expenses for which the Contractor is seeking reimbursement by the Government.

2.9.3.3 The Contactor shall submit travel invoices within 30 calendar days of completion of travel event. The Contractor will be reimbursed for allowable costs.

2.9.3.4 All travel aside from Government-directed travel (e.g., contract management oversight, site staffing/reassignments, etc.) shall be fixed price.

2.10 Future Optional Requirements.

2.10.1 The Government anticipates a requirement to add a new site at Muwaffaq Salti Air Base, Jordan. The services will be the same as for the existing two sites.

2.10.2 The potential exists to close sites at current locations, move sites from one location to another, or add sites at up to two new locations (in addition to the site referenced in paragraph 2.10.1). If required, these options will be identified and negotiated separately.

2.10.3 The potential also exists to add new missions that may require additional Government- or contractor-provided payloads (see paras 3.3.3 and 3.3.4). If required, the addition of Contractor-provided payloads to support these missions will be requested and negotiated separately.

2.11 Technological Advances Report. The Contractor shall provide the Government an annual report of any technological advances available to enhance performance of the UAS, payloads, and associated mission equipment (Appendix D - Deliverables). The report shall include the benefits to the Government with the estimated total costs to provide the enhanced services for the remaining options on the contract.

3.0. Unmanned AIRCRAFT SYSTEM (UAS) PERFORMANCE.

3.1. Air Vehicle (AV) Requirements. The AV shall be capable of executing a preprogrammed flight plan and shall be capable of accurately adapting to dynamic, in-flight re-tasking. The AV with full fuel and payload shall be capable of takeoff, operation, and recovery while operating in austere and arduous environments. Table 1 below outlines the performance that the UAS 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 at Standard Day Conditions[footnoteRef:1] [1: Standard Day Conditions – Temperature: 52F (15C); Pressure: 29.92 in Hg]

Table 1 Air Vehicle Performance Specifications

Service Ceiling[footnoteRef:2] [2: Service-ceiling is the altitude at which the AV’s vertical rate of climb performance is equal to 100 feet/minute]

Minimum 15,000 Feet MSL[footnoteRef:3] [3: MSL – Mean Sea Level]

-4F to +122F

Inches/Hour

3.2 Airworthiness (AW). The AV shall be capable of meeting appropriate AW flight authorizations required of USAF AW Policy. Specific AW requirements, COCO AV documentation, and AV AW inspection information is provided in Para 4.1.2, and Attachment 1 of this PWS.

3.3 AV System Requirements and Capabilities. Table 1 above outlines the performance that the AV shall be capable of achieving. The AV with full fuel and payload shall be capable of full operation in the environmental conditions described.

3.3.1 External Lighting. The AV shall have 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.

3.3.2 Loss of Link (LOL). The AV shall possess autonomous 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. Options such as belly landing on land is acceptable to allow possible contingency recovery. The contingency maneuver shall be such that the AV does not cause increased risk to friendly forces or non-combatant personnel.

3.3.3 Electro-Optical (EO) and Infrared (IR) Payloads and Sensors. The AV shall be capable of being configured with both EO and IR payloads. Only one of these two optical payloads/sensors will be required to be installed at any given point in time. The capability shall exist to switch between the optical sensor and any other installed payload from the Ground Control Station (GCS) while the AV is in flight. A Medium Wave IR payload is the minimum requirement, but the AV shall also be capable of supporting optional Long Wave IR and Short Wave IR payloads if needed for future mission requirements. Only one type of IR payload would be required to be installed on an AV for a given flight.

3.3.4 Modular Payloads. The AV shall provide on-board power generation and be simultaneously configurable with both an optical sensor (EO or IR) and a Tactical Compact Communications Relay (TCCR) brand name or equivalent modular payload. The TCCR (brand name or equivalent) shall have a minimum Ground-Relay-Ground range of 100 nautical miles and support encrypted and non-encrypted “bent-pipe” voice and data transmission. The AV shall be capable of accepting other modular payloads, some of which may be Government-provided. Each modular payload shall be simultaneously configurable with the EO or IR optical payloads (i.e., minimum requirement is to have the capacity to support an optical sensor (either EO or IR) and one additional modular payload at the same time). Each payload module shall include provisions for power, volume and subsystems needed for its operation which exceed what is available from the aircraft’s baseline capacity. The following modular payloads are examples of payloads that may be requested in the future: synthetic aperture radar (SAR), electronic warfare (EW), light detection and ranging (LIDAR), and signals intelligence (SIGINT). The modular payloads must be capable of being interchanged within two hours (elapsed time). Estimates of payload module impact on vehicle performance and operating limitations shall be included for each module configuration.

3.3.5 Non-Detectable. At steady-state cruise power setting, the AV shall provide sensor data IAW paragraph 3.8.1.1, at an altitude of 3000 feet above the ground and slant angle of 45 degrees.

3.3.5.1 Acoustic Non-Detectability. At the stated flight conditions the AV shall remain acoustically non-detectable per MIL-STD-1474E, Level 1, Requirement 2 conditions (quiet rural area with the closest heavily used highway and community noises at least 2.5 miles away).

3.3.5.2 Visual Non-Detectability. The AV shall incorporate a low-visibility, counter-shaded paint scheme consisting of FED-STD-595C FS 36320 (or similar) matte gray upper surfaces and FED-STD-595C FS 36375 (or similar) matte gray lower surfaces. Markings shall be painted in the respective contrasting gray as depicted in MIL-STD-2161C(AS).

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

3.3.7 Fuel Additives. All additives shall be assessed as potential hazardous material(s) to determine the risk to the AV, personnel and the environment during stowage, handling, operations, and disposal. If additives are found to be hazardous, they must be handled IAW FED-STD-313D, Material Safety Data, Transportation Data, and Disposal Data for Hazardous Materials Furnished to Government Activities.

3.3.7.1 Lubricant Engine Additives. Engine lubricants are allowed and must be provided by the Contractor.

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

3.3.7.2.1 All additives and their related systems must be capable of being approved via the AW Military Flight Release (MFR) process (see paragraph 4.1.2.3).

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

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

3.5 ISR Services. The Contractor shall provide sufficient resources to conduct ISR services for up to 600 sensor hours per month at each location.

3.6 Ground Control Station (GCS) Requirements. The contractor shall be prepared to control the AV and receive video inside a Combat Operations Center (COC)/Tactical Operations Center (TOC).

3.6.1 Simultaneous Control. 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.

3.6.2 Full Motion Video Feeds. The Contractor shall have the ability to provide full motion video feeds directly to a Contractor-provided display in the GCS.

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

3.6.4 Video and Metadata. 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 3.10). The Contractor shall also provide imagery with all metadata removed that can be releasable to HN (when applicable).

3.6.5 Power. The Contractor shall operate on electrical power provided by their own diesel-generator(s). The Government will provide the diesel fuel for the generators. Use of Government-provided electrical power if already existing at the site is acceptable but is not guaranteed to be available.

3.6.6 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’s operating manual/Standard Operating Procedures (SOP)).

3.6.7 Operator Capabilities. 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 UAS’s airspeed, altitude, and heading by their specific actions.

3.7 Communication, Navigation and Identification Systems (CNI)

3.7.1 Communications (Datalinks Operation). Use of Bandwidth Efficient Common Data Link (BE-CDL) radios, when available, is desired. Otherwise, the contractor shall use either L-3 Communications’ Bandit or Vortex brand name or equivalent radios for 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) and provide hemispherical, 360 degrees of coverage, to maintain direct unobstructed LOS communications.

3.7.2 Communications (Spectrum). Specific bands and/or frequencies required will be part of the pre-deployment work-ups. 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.

3.7.3 Communications (Encryption). The Contractor shall utilize FIPS-197, Advanced Encryption Standard (AES) compliant 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.

3.7.4 Communications (Remote Video Terminals (RVT)). The AV shall provide EO/IR video, with Key Length Variable (KLV) metadata, to an RVT up to 5 NM from the AV. The Contractor shall provide a communications architecture that allows for the Rover (IV+) Series, VideoScout or OSRVT system to be selected for a particular mission from the flying schedule.

3.7.5 Navigation (Global Positioning System (GPS)). The Contractor shall only use DoD approved keyed Precise-Positioning System (PPS) GPS. The UAS shall utilize approved PPS-GPS (SAASM or M-Code) for all phases of flight to include launch and recovery. The Contractor shall utilize DS101 port(s) to receive the appropriate 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.

3.7.6 Identification (Transponder/Identification). The AV shall use an Air Traffic Control Radar Beacon System, Identification Friend or Foe, Mark XII/Mark XIIA, Systems (AIMS) certified Mode 3/C transponder with “IDENT” capability, controllable from the GCS, in accordance with AIMS 03-1000B and shall otherwise comply with all applicable airspace policies and regulations in which it is expected to be flown. This can include but is not limited to expected future policy requirements such as ADS-B or Mode S. The UAS shall have an AIMS platform certification in accordance with AIMS 03-1000B.

3.8 Full Motion Video (FMV) & Still Imagery. The Contractor shall be capable of injecting UAS sensor data into host unit’s Processing, Exploitation, Dissemination (PED) system(s). The system shall be able to autonomously maintain uninterrupted tracking of a stationary or moving object, while in visual contact.

3.8.1 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.

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

3.8.1.2 EO/IR Usage. The Contractor shall provide EO and IR video output hours as tasked in the ATO.

3.8.2 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. 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 UAS at an altitude of 3000 feet Above Ground Level (AGL) at a 45 degree slant range and viewed via a VideoScout MC2 PED. The Contractor shall provide IR still images in NITF 2.1 format, captured from the FMV stream. The Contractor-provided system shall be capable of producing an MWIR output meeting or exceeding the NIIRS rating of 7.2, when taken from the UAS at an altitude of 3000 feet AGL at a 45 degree slant range and viewed via a VideoScout MC2 PED. SSCAM IP (August 2009) and NVTherm IP (August 2009) shall be used to verify the capability of the EO and IR sensor systems, respectively.

3.9 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.”

3.10 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:

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

b. FMV must use the MPEG-2 transport stream.

c. FMV must use the User Diagram Protocol.

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

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

3.11 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 3000 feet AGL at a 45 degree slant range, within 60 seconds.

3.12 Data Dissemination & Storage Requirements. The still photography, video and metadata recorded from each mission shall be stored by the Contractor for one (1) 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 (Appendix D – Deliverables). 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’s 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 will 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).

4.0 OPERATIONS AND MISSION SUPPORT

4.1 Pre-Deployment Requirements

4.1.1 Complete AW Inspection. Following contract award and before AV deployment, the Contractor shall participate in an AW Inspection at the Contractor site. Inspection dates and location will be coordinated following contract award. The goal of this inspection is to issue a USAF MFR for the COCO AV.

4.1.2 Airworthiness Requirements

4.1.2.1 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 MFR for a Group 3 UAS.

4.1.2.2 The flight operations required by this contract have been determined to be Public Aircraft Operations (PAO) and shall be conducted under the USAF Technical Airworthiness Authority (TAA). The aircraft ground and flight operations shall be conducted using FAA approved data, if available, or OEM equivalents, to include specifications, drawings, procedures, manuals, and limitations. Operations requiring deviation from the FAA (or OEM equivalent) approved technical data, procedures, and limitations shall be specifically approved by the USAF Technical Airworthiness Authority. During the period of the contract, the USAF TAA or the Delegated Technical Authority (DTA) reserves the right to inspect the aircraft and operation records to verify compliance.

4.1.2.3 Airworthiness Assessment. The Contractor shall support the USAF airworthiness assessment process for Public Aircraft Operations (PAO). For aircraft development and/or modification activities not approved by the FAA, the Contractor shall support the USAF airworthiness process IAW AFI 62-601, USAF Airworthiness. The USAF will use a non-design based AW assessment as stated in AFI 62-601, paragraph 1.7.2 as the basis for a MFR.

4.1.2.3.1 The Contractor shall submit a COCO Aircraft Airworthiness Data Package required to obtain Military Flight Release IAW AWB-1012, USAF Airworthiness (AW) Requirements for Contractor-owner and Contractor Operated (COCO) Aircraft, Attachment 4 (included as Attachment 1 to this PWS) (Appendix D - Deliverables).

4.1.2.3.2 The Contractor shall submit answers to the questions found in SUAS MFR – Attachment 1 (included as Attachment 2 to this PWS) (Appendix D - Deliverables).

4.1.2.3.3 The Contractor shall submit answers to the questions found in Range Commanders Council Document 323-99, Range Safety Criteria for Unmanned Air Vehicles, Rationale and Methodology Supplement, Appendix B (included as Attachment 3 to this PWS) (Appendix D - Deliverables).

4.1.2.4 The Contractor shall develop and document a formal risk assessment IAW MIL-STD-882E (Appendix D - Deliverable).

4.1.2.5 Aircraft Modification. The Contractor shall operate and maintain their aircraft, which have standard certificates of airworthiness, using approved FAA data and procedures if available, or OEM equivalent. Should modifications be necessary to aircraft not conforming to an approved type design, the contractor shall use the USAF airworthiness process and obtain approval from the USAF’s Technical Airworthiness Authority. All aircraft modifications shall be completed at the contractor’s expense.

4.1.2.6 Airworthiness Flight Authorization. The Contractor shall assess the airworthiness of the modified aircraft system and provide a documented recommendation that the aircraft system be authorized for flight operations. The Contractor shall obtain the appropriate TAA/DTA issued Airworthiness Flight Authorization prior to conducting any COCO flight operations. For PAO this is a Military Flight Release (MFR).

4.1.2.7 Maintenance. The Contractor shall maintain the aircraft IAW applicable FAA regulations and standards if available, or OEM equivalent. The Contractor shall use the Approved, or Accepted FAA maintenance plan, if available, or maintenance procedures provided by the OEM, as applicable. The Contractor shall adhere to, and comply with, all applicable FAA and OEM airworthiness directives and service bulletins.

4.1.2.8 Operations. For PAO, the contractor shall have a documented Standards and Evaluations (STAN EVAL) program to monitor both pilots and sensor operators. The contractor shall have documented processes to include, but not limited to, train aircrew and document risk analysis, standardized crew communications, crew resource management, and deficiency reporting. The contractor shall maintain an initial and recurring training and evaluation documentation folder for each crew member.

4.1.2.9 Quality Assurance. The Contractor and subcontractors shall maintain a commercial aviation quality program for the modification, maintenance, and operation of commercial aircraft under FAA regulation, and maintenance of electronic systems.

4.1.2.10 Regulatory Oversight. The Contractor shall support site visits by the contracting organization, COCOM, COCOM supporting unit or end user. For PAO, the Contractor shall supply the CO a copy of Contractor flight procedures and documents for review including but not limited to Flight Operation Plans (FOPs), Ground Operation Procedures (GOPs), Standard Operating Procedures (SOPs), Operational Risk Management (ORM) sheet, Master Minimum Equipment List (MMEL) and crew qualification documents as appropriate. The Contractor will immediately notify the CO in the event of any mishap or reportable incident involving the COCO aircraft.

4.1.3 The Contractor shall submit a System Safety Plan and Hazard Analysis IAW AFPAM 90-803, Risk Management (RM) Guidelines and Tools, and AFI 91-204 Safety Investigations and Reports (Appendix D - Deliverables).

4.1.4 The Contractor shall provide Electromagnetic Environmental Effects (E3) and ElectroMagnetic Interference (EMI) data to demonstrate their design practices pertinent to MIL-STD-464C requirements as follows (Appendix D - Deliverables):

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

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

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

4.1.4.4 The GCS shall be compatible with the external and internal EME.

4.1.4.5 The UAS shall not present an electromagnetic radiation hazard to personnel, ordnance, fuel, electronics, or the proper operation of radio receivers in accordance with MIL-STD-464C, Section 5.9, Electro-Magnetic Radiation Hazards.

4.1.4.6 The UAS shall not present an electrostatic discharge hazard to personnel, ordnance, fuel, electronics or the proper operation of radio receivers in accordance with MIL-STD-464C, Section 5.8, Electrostatic Charge Control.

4.1.4.7 The UAS shall not impact area radio receivers in accordance with MIL-STD-461G, RE102 for all UAS subsystems.

4.1.5 Safety Data Sheets. The Contractor shall provide Safety Data Sheets and identification IAW FED-STD-313E, Material Safety Data, Transportation Data, and Disposal Data for Hazardous Materials Furnished to Government Activities, 30-days before arrival of hazardous materials to a DoD installation (Appendix D - Deliverables).

4.1.6 UAS Cybersecurity. The UAS shall conform to DoD security guidance regarding cybersecurity, including all appropriate controls as defined by the Mission Assurance Category, and Data Classification of the system in accordance with DoDI 8582.01, Security of Unclassified DoD Information on Non-DoD Information Systems, and DFARS 252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting.

4.1.6.1 AV Critical Program Information (CPI). The UAS shall protect CPI from reverse engineering exploitation and incorporate Anti-Tamper features as required by DoDI 5200.39, Critical Program Information (CPI) Identification and Protection Within Research, Development, Test, and Evaluation (RDT&E) DoDI 5000.02, Operation of the Defense Acquisition System, and Defense Acquisition Guide. 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 shall not be in deployed systems.

4.1.6.2 The UAS shall adhere to the data at rest encryption requirements as defined in AFMAN 17-1301, Computer Security (COMPUSEC).

4.1.6.3 The UAS shall comply with AFI 17-221, Spectrum Interference Resolution Program. The Contractor shall provide the Application for Equipment Frequency Allocation spectrum analysis and allocation IAW DD1494 (Appendix D - Deliverables).

4.1.7 Standard Operating Procedures (SOP). The Contractor shall develop with the COR and LNO a site specific SOP prior to activation of the site (Appendix D - Deliverables). The SOP will serve as a living document outlining daily operations procedures, flight planning resources, frequency coordination and de-confliction procedures, personnel, responsibilities, contact information and other vital information to assist mission accomplishment at the specific operating location.

4.1.7.1 The SOP 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 submitted to the CO for review prior to forwarding to the appropriate personnel at each site, normally the site’s Electronic Key Management System (EKMS) Manager. The MOUs shall, at a minimum, contain the following sections: Purpose, Background, Scope, Responsibilities (both Contractor and Government), POCs, Modification and Termination procedures, Other, Effective Date and Signature Blocks for the appropriate Contractor and unit Commander (or designee) to sign.

4.1.7.2 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 Material (KEYMAT), Keys and Government Furnished Equipment (GFE) requirements.

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

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

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

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

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

4.1.7.8 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.

4.1.7.9 Contractor’s SOP shall address the applicable elements of AFI 11-502, Vol 3, General Flight Rules that apply to daily flight operations.

4.2 Deployment Requirements

4.2.1 Task Force UAS ISR Schedule. The Contractor shall provide EO and IR ISR Services as tasked in the Task Force UAS ISR schedule.

4.2.2 Mission Reliability Rate (MRR). The Contractor shall meet or exceed a MRR of 95% as defined in Appendix E.

4.2.3 Availability. The Contractor shall be capable of providing UAS/ISR services 24-hours a day, seven (7) days per week. Operations shall be conducted IAW Contractor’s SOP.

4.2.4 Advance Notice. During routine operations, the flight schedule is published with a three-day utilization projection; the schedule may be refined until day of execution. The Contractor shall be able to execute the routine daily flight operations schedule with eight hours’ advance notification (i.e., revision shall provide eight hours’ notice).

4.2.5 Adhoc Taskings. The Contractor shall respond to a launch request for a non-scheduled (advance notification of eight hours not provided) mission within 30 minutes, weather conditions permitting, when the site is operational and in an active standby status[footnoteRef:7]. [7: Active Standby Status means the Contractor is on duty and the GCS is operational and manned.]

4.2.6 Mission Duration

4.2.6.1 Mission Definition – Threshold & Definition

4.2.6.1.1 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. Two missions may be scheduled simultaneously from the same base of operations. 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 shall be coordinated with the LNO.

4.2.6.2 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. 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.

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

4.2.8 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 shall be coordinated with the COR and the LNO.

4.2.9 Mission Reporting Requirements. The Contractor shall prepare and submit the following reports.

4.2.9.1 A Daily Report, including the following elements (Appendix D - Deliverables):

4.2.9.1.1 Service Hour Summary / System Status Report – Includes daily hours utilization and MRR situation report

4.2.9.1.2 Personnel Status Report

4.2.9.1.3 Tracking of all equipment and parts shipments to and from theater

4.2.9.2 A consolidated Monthly Report that consists of a shipping report, service hour summary, end of month MRR report, and an incident report (Appendix D – Deliverables).

4.2.9.3 Employee Training. Training OIs shall be submitted to the CO for acceptance (Appendix D - Deliverables).

4.2.9.4 AV Mishap Report. The Contractor shall provide an initial mishap report that provides the following information within 24 hours of the incident: Date, Time, Location, Weather, AV type, Other Pertinent Configuration Notes, Brief Summary of Mishap and Initial Root Cause Assessment. 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), the Contractor shall support the effort as required (Appendix D - Deliverables).

4.2.9.5 Report COMSEC incidents IAW 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.

4.3 Post-Deployment Requirements

4.3.1 Upon completion of the ISR performance, including any extensions or Option Period awards, the Contractor shall disassemble and prepare for shipment all COCO systems, equipment and spares and return all Government Furnished Equipment (GFE) to the Government to include Common Access Cards for accountability.

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

4.3.3 The contractor shall fully cooperate with the follow-on contractor and the Government at the end of the contract Period of Performance to coordinate and de-conflict actions to ensure minimal disruption of services at performance changeover.

SECTION B - SERVICE SUMMARY (SS)

1.0. SS NARRATIVE.

This SS implements AFI 63-138, performance-based service contracts, and identifies critical success factors for the successful performance of requirements. The SS is listed in Table 1.0 and identifies:

1.1. Purpose. The SS lists performance objectives for the required service that the Government shall surveil. The absence of any contract requirement from the SS shall not detract from its enforceability nor limit the rights or remedies of the Government under any other provision of the contract including the clauses entitled “Inspection of Services” and “Default.”

1.2. Components. The SS states the performance objective (required service), and threshold (performance standard, accept/reject point (if applicable) in either qualitative or quantitative fashion) for each critical success factor.

1.3. Quality Assurance Surveillance Plan (QASP). The SS shall be used as the baseline to develop a Government QASP. The QASP shall identify the audit methods/procedures the Government shall use to evaluate the Contractor's performance.

1.4. Right to Surveil. The Government reserves the right to surveil all services and requirements called for in this PWS to determine whether the performance objectives and performance standards were met.

Table 1. Performance Requirements Summary Matrix

PERFORMANCE OBJECTIVE

(PWS Reference)

Program Management:

Provide and maintain comprehensive, pro-active, integrated program management that focuses on meeting or exceeding customer requirements and ensures compliance to all mandatory, statutory, and regulatory requirements.

PWS Sect. A, Para 2.0

Meet or exceed customer requirements; manage program by identifying interrelated processes, perform management reviews, and take action as a result of those reviews, and create organizational value by fostering a mutual beneficial relationship with the government.

No major nonconformance is allowed. If a major nonconformance is discovered this SS item will be considered non-compliant.

Quality Management System (QMS):

Implement, maintain, and comply with a comprehensive QMS

PWS Sect. A, Para 2.8 and Appendix C

IAW ANSI/ISO/ASQ Most Current Version of 9001 QMS requirements and PWS

No major nonconformance is allowed. If a Major nonconformance is discovered the QMS will be considered non-compliant.

PWS Sect. A., Para 4.2.2

Meet or exceed a MRR…