A07-RFP_W911QY_17R0017_Attachment_J_-_FoSUAS_Products_II_SOW.pdf

ATTACHMENT J – FoSUAS Products II Statement of Work SOW

Family of Small Unmanned Aircraft Systems (FoSUAS)

UNMANNED AIRCRAFT SYSTEMS

(UAS)

Systems and Parts Acquisition

Indefinite Delivery Indefinite Quantity (IDIQ)

Statement of Work (SOW)

19 January 2017

Prepared By:

Unmanned Aircraft Systems (UAS) Project Office

SFAE-AV-UAS-TU

Table of Contents

1.0 SCOPE

1.1 Background and Project Description

2.0 APPLICABLE DOCUMENTS

3.0 REQUIREMENTS

3.1 General Requirements

3.2 Program Management

3.2.1 Management Structure

3.2.2 Meetings, Reviews and Reports

3.2.3 Cost, Performance and Progress Reporting

3.2.4 Security Requirements

3.2.5 Risk Management

3.2.6 Contracting Officer’s Representative

3.2.7 System Safety

3.2.7.1 System Safety Program Plan

3.2.7.2 Mishaps and Accidents

3.2.7.3 Environmental Safety and Occupational Health

3.2.7.4 Hazardous Materials Management Program (HMMP)

3.2.7.5 Warranty

3.3 Systems and Parts

3.3.1 Upgrades and Modifications

3.3.2 Parts Obsolescence

3.3.3 Quality Program

3.3.3.1 Quality Control Program

3.3.3.2 Factory Acceptance Test (FAT)

3.3.4 Product Verification Testing (PVT)

3.3.4.1 PVT, Procedures and Reports

3.3.4.2 Failure Analysis and Corrective Action Report (FACAR)

3.3.5 Failure Modes, Effects, and Criticality Analysis (FMECA)

3.3.6 Failure Reporting and Corrective Action System (FRACAS)

3.3.7 Item Unique Identification (IUID)/Radio Frequency Identification (RFID) ... 21

3.3.8 Flight Operations

3.3.9 Packaging, Shipping

3.3.10 Software Products

3.4 Systems Engineering

3.4.1 Configuration Management (CM)

3.4.2 Configuration Management Plan (CMP)

3.4.3 Configuration Change Control

3.4.4 Engineering Change Proposal

3.4.5 Request for Variance

3.4.6 Configuration Auditing and Verification

3.4.7 Physical Software Control

3.4.8 Technical Data Package

3.4.8.1 Repair Procedures

3.4.8.2 Data Accession List

3.4.9 Technical and Engineering Support Data

3.4.9.1 Interface Control Documents

3.4.9.2 Spectrum Support

3.4.9.3 Technical Manual/Complete Training Package

3.4.9.4 Training Products

3.4.9.5 Airworthiness Data Support

3.4.9.6 Aeronautical Design Standards Verification and Analysis

3.5 Information Assurance (IA)

3.5.1 Counterfeit Risk Management

4.0 GENERAL INFORMATION

4.1 Travel

4.2 Release of Data and Information

4.3 Invoicing

4.4 Payments

5.0 DATA REQUIREMENT AND DATA RIGHTS

5.1 Non-Disclosure Agreement and Transfer of Information

5.2 Units of Measure

5.3 Data Discrepancy Notification and Correction

1.0 SCOPE

This Statement of Work (SOW) describes the full spectrum of Small Unmanned Aircraft System (SUAS) and Parts required to support the Tactical UAS (TUAS) Product Office (PdO) in the Continental United States (CONUS) and Outside Continental United States (OCONUS), as well as its domestic and foreign customers. The contract will consist of the following independent domains:

• Systems – Long Range Reconnaissance and Surveillance (LRRS) and Medium Range Mobile

(MRM) UAS

• Future Flight Control Systems (FCS) and Radios

• Ground Control Systems (TOGA)

• Other Major Components (Line Replaceable Units (LRU’s) and components such as Flight Surfaces, Fuselages, Batteries and Payloads not included in other domains)

• RQ-11B and RQ-20A spare and repair parts

• Miscellaneous (such as Travel, Contract Delivery Requirements List (CDRLS), Other Direct Costs (ODC)

1.1 Background and Project Description

On 14 June 2013, the President signed an Executive Memorandum on expanding United States (US) leadership in wireless innovation and Congressional direction to expedite availability of CONUS spectrum, specifically the 1755-1780 megahertz (MHz) band, to support commercial broadband operations. This significantly affects US Department of Defense (DoD) SUAS operations. This creates an obsolescence issue for the TUAS PdO for the past-procured 1,017 LRRS and the 2,870 MRM Unmanned Aircraft (UA). The TUAS PdO is required to upgrade the UAs from the current occupied frequency range of 1755-1780 MHz for continued operations in 1780-1850 MHz along with sharing in the 2025-2110 MHz frequency range. In addition, as part of the frequency relocation effort the Government will procure 4,932 H-GCSs.

On 23 November 2013, the Army approved the Rucksack Portable Unmanned Aircraft Systems (RPUAS) Increment II CPD for a SUAS FoS. The Army approved the CPD based on dividing the requirements into Blocks. Block I requirements are for 1,402 LRRS UA and 2,485 MRM UA. The program will fulfill the Block I requirements with past-procured assets (RQ-11B and RQ-20A UAs) and additional assets pending available funding. There is a need to procure the remaining LRRS quantity of 385 UAs pending available funding.

The TUAS PdO located at Redstone Arsenal, Alabama, manages the Rucksack Portable Unmanned Aircraft System (RPUAS) Family of Systems (FoS) and has a need to:

(1) Implement the strategy of the RPUAS FoS Capability Production Document (CPD) for LRRS and MRM systems.

(2) Procure the required number of spares and repair parts necessary to support the Army inventory of RQ-11B (Raven) and RQ-20A (Puma) systems, based on historical repair data.

(3) Procure SUAS systems and parts that meet a defined set of salient characteristicsleast equal to the currently fielded systems.

(4) Transition SUAS to the reallocated 1625-2110 MHz frequency spectrum.

(5) Procure Handheld-Ground Control Stations (H-GCS), also referred to as Tactical Open Government-owned Architecture (TOGA) controllers.

2.0 APPLICABLE DOCUMENTS

Applicable documents are cited in the Document Summary List (DSL) by number, title, date, and as otherwise specified in this contract.

3.0 REQUIREMENTS

3.1 General Requirements

The contractor shall perform all tasks specified under this contract, within the applicable domains as identified in Section 3.3, over the five-year ordering period of the contract. The contractor shall provide all labor and materials in the performance of this SOW. The contractor shall supply SUAS, parts and components In Accordance With (IAW) schedules outlined in subsequent Delivery Orders.

The contractor, as an independent contractor and not as an agent of the Government, shall provide the necessary resources to accomplish tasks of the type set forth below.

3.2 Program Management

The contractor shall execute the requirements of this SOW by direction and with coordination of the Procuring Contracting Officer (PCO). The contractor shall perform all the program management functions that are necessary to support the Delivery Orders awarded under this contract.

The contractor’s program management requirements are allocated to the Delivery Order in which it is participating. The TUAS PdO will indicate the specific Contract Data Requirement Lists (CDRLs) that contractors shall provide for the Indefinite Delivery Indefinite Quantity (IDIQ) contract Delivery Orders.

The contractor shall deliver all CDRLs IAW the relevant Data Item Description (DiD) and DD Form 1423 as applicable by Delivery Orders. CDRL deliveries shall be made electronically to the TUAS Data Management system as specified in the CDRL. The contractor’s data manager(s) will require an External Certificate Authority (ECA) card to enable access to the TUAS Data Management system. Contractor’s accounts shall be requested via the TopVue site (https://topvue.peoavn.army.mil/Topvue-UAS).

3.2.1 Management Structure

As applicable by Delivery Order:

The contractor shall have a dedicated management team with defined roles and responsibilities.

The team shall participate in Government led Integrated Product Team (IPT) meetings to enable direct insight to the contractor’s activities at the working level.

3.2.2 Meetings, Reviews and Reports

Start of Work Meeting: The Kick-Off meeting shall be coordinated with the Contracting Officer’s Representative (COR) to determine a mutually agreed upon date that shall occur within ten (10) days after contract award. The contractor shall send out an agenda via an email notice.

The contractor shall submit summary/minutes of the start of work meeting to the Government IAW DI-ADMN-81505. Agenda shall include entrance and exit criteria for the meeting as directed by the Government.

Technical reviews consistent with the scope of the effort will be required specific to the effort.

The contractor shall coordinate with the COR to determine a mutually agreed upon date for each technical review. The contractor shall develop and present material IAW the agenda and entrance/exit criteria appropriate to the review and agreed upon by the COR. Presentation material shall be prepared and delivered to the Government IAW DI-ADMN-81373.

Technical Reports: The contractor shall prepare Technical Reports IAW DI-MISC-80508.

3.2.3 Cost, Performance and Progress Reporting

The contractor shall prepare Status Reports IAW DI-MGMT-80368 covering the status on price and schedule performance, tradeoffs and risk reduction activities. Additionally the report shall include the contractor’s performance in meeting/exceeding small business goals outlined in the Request for Proposal (RFP) and subsequent contract.

3.2.4 Security Requirements

The contractor shall comply with the requirements of the DoD Contract Security Classification Specification (DD Form 254) and shall utilize the Security Classification Guide (SCG) Family of Small Unmanned Aircraft Systems SCG for classification guidance. The contractor shall maintain facility clearance at the SECRET level for performance of duties under this contract.

The contractor shall provide adequate storage at their facility for classified material up to and including SECRET. Significant upgrades and materiel procurement related to facility clearance shall be assessed and agreed upon jointly by the contractor and the Government. The contractor shall maintain sufficient number of employees with a Personnel Security Clearance at the SECRET level to perform classified tasks during the performance of this contract.

The performance of this contract shall require access, generation, receipt, storage, and processing of Communication Security (COMSEC), Controlled Cryptographic Items (CCI) information, tactical ground control and airborne encryption equipment, and Secure Telephone Equipment necessary for secure communications. Access to COMSEC information and equipment requires a final United States (U.S.) Government security clearance at the appropriate level. Classified COMSEC material is not releasable to contractor employees who have not received a final U.S.

security clearance at the appropriate security level. COMSEC access shall be in accordance with National Industrial Security Program Operating Manual (NISPOM) (DOD 5220.22-M) and Policy for Safeguarding and Controlling Communications Security (COMSEC) Material (AR 380-40). When access is required at Government facilities, contractor personnel shall adhere to COMSEC rules and regulations as mandated by Command policy and procedures. National Security Agency (NSA) Central Security Service (CSS), NSA/CSS Policy Manual No. 3-16 “Control of Communications Security (COMSEC) Material” applies to this contract.

Contractor will require access to threat related data in the performance of this contract, to include the System Threat Assessment Report (STAR), which will require access to Non-Sensitive Compartmented Information (non-SCI).

Contractors requiring access to the Secure Internet Protocol Routing Network (SIPRNET), must receive a North Atlantic Treaty Organization (NATO) briefing, due to NATO information residing on the SIPRNET. NATO access requires a final U.S. Government clearance at the appropriate level and a NATO access briefing. The Facility Security Officer (FSO) is responsible for providing the NATO briefing. Contractors must comply with the following guidance for access to NATO material: DoD 5220.22-M, NISPOM, Chapter 10, Section 7, Memorandum, Secretary of Defense, OSD, Apr 5, 2007, Subject: U.S. Implementation Instruction for Protection NATO Classified Information, and AMC Regulation 380-12, U.S. Army Material Command

Control of NATO Material, 19 Nov 05. The prime contractor must receive approval from the GCA to impose NATO requirements or grant NATO access to a subcontractor.

The contractor shall require access to For Official Use Only (FOUO) information. FOUO information shall not be disclosed by contractor without approval of UAS Project Office.

Contractor is authorized access and e-mail account to SECRET Internet Protocol Router Network (SIPRNET) at Government facilities only. Contractor employees requiring access to the SIPRNET must complete the SIPRNET Access Request Form and obtain government supervisor approval. The contractor shall not access, download or further disseminate any special access data (Intelligence, NATO, COMSEC, etc.) outside the execution of the defined contract requirements and without the guidance and written permission of the Contracting Officer.

Contractor access to SIPRNET is restricted to sites directly related to meeting the requirements of this contract as validated by the Contracting Officer Representative (COR) and/or the Scope of Work. The contractor shall not access INTELLINK-S, while on the SIPRNET without formal access authorization of the COR and AMCOM G-2 (Intelligence and Security).

In accordance with AR 381-12, Threat Awareness and Reporting Program (TARP) 1 June 2016, contractor employees shall report threat-related incidents, behavioral indicators, and other matters of Counter Intelligence (CI) interest specified in AR 381-12, Chapter 3, to the Facility Security Officer (FSO), the nearest military CI office, the Federal Bureau of Investigation, or the Defense Security Service. Contractor employees working as an integral part of an Army organization shall complete annual Threat Awareness training in conjunction with Army personnel. Contractor FSOs shall ensure that all applicable AR 381-12 requirements are implemented for personnel who work at contractor facilities.

The performance of this contract shall require access, receipt, generation, and storage of classified information and equipment that has no-foreign stipulations at the SECRET level at contractor facilities in support of the work effort. Classified information is, and remains for the duration of the classification, the property of the U.S. Government, regardless of proprietary claims. Contractor is authorized to process classified information via accredited computer system in accordance with DOD 5220.22-M, NISPOM, Chapter 8. The contractor shall utilize the current Marking Classified National Security Information guide to ensure classified information generated is properly marked. At Government facilities, contractor shall follow AR 25-2 for guidance on classified computer processing. Contractor must provide adequate storage at their facility for classified material up to and including SECRET. All classified material must be accounted for on a DA Form 3964 or contract equivalent form throughout each phase of the contract.

In order to accomplish the technical tasks required under this SOW, the contractor shall maintain a valid U.S. COMSEC account throughout the period of performance of this contract. The contractor shall have access to COMSEC and Controlled Cryptographic Items (CCI) information and tactical ground control and airborne encryption equipment and Secure Telephone Equipment necessary for secure communications. Access to COMSEC information and equipment shall require a final U.S. Government security clearance at the appropriate level. National Security Agency (NSA) Central Security

Service (CSS), NSA/CSS Policy Manual No. 3-16 “Control of Communications Security (COMSEC) Material” shall apply to this contract. All COMSEC/CCI equipment shall be controlled and chain of custody maintained through a Standard Form (SF) 153. The contractor shall be responsible for the protection of COMSEC equipment from the time of receipt of the equipment until transferred via the completion of an SF-153, inventory, confirmation of end item (COMSEC) and serial numbers on the SF-153 with signatures.

Per AR 380-27, Paragraph 2-6, Control of Compromising Emanations (available at https://armypubs.army.mil/) A TEMPEST Countermeasures Review (TCR) will be conducted by an Army Certified TEMPEST Technical Authority (CTTA). TCR will be requested by the GCA via secure e-mail address (usarmy.meade.902-mi-grp.list.310th-tempest@mail.smil.mil) upon award of the contract. The TCR will be conducted at the contractor’s facility where classified information or material is to be received, generated or stored electronically. Results of the TCR will be provided to the contractor who will ensure that all applicable AR 380-27 requirements are implemented. If the Facility Security Officer (FSO) has a Common Access Card (CAC) AR 380-27 is available at https://armypubs.army.mil/. If the FSO does not have a CAC, contact the UAS Project Security Staff for a copy of AR 380-27 at usarmy.redstone.peo-avn.list.avn-uas-security@mail.mil for a copy of AR 380-27.

There is no required OPSEC deliverable associated with this contract. However, the contractor will need to adhere to all OPSEC requirements outlined in the Program Executive Office, Aviation ( PEO AVN) Policy Memorandum 15-13, Operational Security (OPSEC) Plan dated May 2015, National Security Decision Directive (NSDD) No. 298, "National Operations Security Program", dated January 22, 1988, Department of Defense Directive 5205.02E, "DoD Operations Security (OPSEC) Program", dated 20 June 2012, Department of Defense Manual 5205.02-M, “DoD Operations Security (OPSEC) Program Manual, dated 3 November 2008 and Army Regulation 530-1, "Operations Security", dated 26 September 2014. Government Contracting Activity approval is required prior to imposing OPSEC requirements on a subcontractor. PEO AVN Policy Memorandum 15-13, OPSEC Plan, will be provided under separate cover to the FSO.

Contractor shall be authorized to use the Defense Courier Service for keyed COMSEC.

Contractor Courier account shall be established and maintained in accordance with Defense Courier Operation (DOD 5200.33).

All submittals for request for public release of information, articles, videos, etc., shall be submitted to the Program Executive Office (PEO) Aviation, (SFAE-AV), Strategic Communications Specialist, 5667 Wood Road, Redstone Arsenal, AL 35898-5020. No request shall be sent or handed directly to UAS PO personnel. The submissions shall include a letter of transmittal certifying review by the FSO that the material has been reviewed and it contains no classified information. The letter of transmittal shall include the contract number. A minimum of 15 working days is required to process and review the request. Information or material shall not be released until approval is granted.

Contractor shall submit Visit Request via Defense Manpower Data Center - Joint

Personnel Adjudication System (JPAS). All Visit Request shall include the Technical POC and Technical POC telephone number. Visit Request shall not exceed a one year period or beyond the end of the contract if less than one year. The UAS JPAS SMO is W0H9AA4RB.

Contractor employees shall abide by Government Regulations (ARs 380-5, 380-10, 380-40, 381- 12, 25-2, 25-55, 190-13, 530-1) and Standard Operating Procedures when working or visiting Government facilities and installations.

Contractor personnel requiring access to Army Computer Networks shall annually complete the DOD Information Assurance (IA) Awareness Training, and annually sign an Acceptable Use Policy (AUP). The Certificate and AUP shall be provided to the designated personnel at Government facilities.

Foreign subcontractors are restricted from access to protected subsystems or functional military exercises.

Contractor personnel shall not be authorized to take pictures with any form of camera inside Government facilities or on military installations without prior coordination and approval of the Public Affairs office.

Contractor personnel shall utilize contractor company e-mail for transmitting official U.S.

Government business. Official U.S. Government business shall not be transmitted via personal, private, and commercial e-mail accounts, i.e., YAHOO, HOTMAIL, GMAIL, JUNO, AOL, etc.

U.S. Army UAS information shall NOT be processed or stored on contractor employees’ personal computer or any other personally owned electronic devices.

The UAS PO holds final determination on the approval for CACs. Consideration for a CAC will be addressed on a case-by-case basis. CACs will be considered for contractor employees that are deploying, that work full time on a military installation, and for contractor employees that require frequent access to multiple DOD installations in support of this contract. Justification, to include list of multiple DOD facilities, must be included with each request for a CAC. Contractor employees issued a CAC shall maintain possession of their CAC at all times. The CAC shall not be used in temporary badge exchanges. Contractor employees issued a CAC shall not share their CAC PIN with anyone. CAC shall not be left unattended in computer. CACs are the property of the U.S. Government and shall be given to the Contractor FSO upon termination of employment with the company, expiration of the CAC, replacement of a CAC, or upon contract completion.

The FSO shall return the CAC to the UAS PO Government Contracting Officer Representative (COR) or the UAS PO Security Manager. The loss of a CAC shall be reported, on the first business day following the discovery of the lost CAC, to your chain of command, FSO, UAS PO COR, UAS PO Security Office (256-313-5330/256-876-7102), and to the issuing agency. Visit the Realtime Automated Personnel Identification System (RAPIDS) site at:

https://www.dmdc.osd.mil/rsl/appj/site for local sites.

Unauthorized possession of a CAC can be prosecuted criminally under section 701, Chapter 33, Title 18, U.S. Code Part I. FAR 52.204-9 - Personal Identity Verification of Contractor Personnel (January 2011) applies to this contract. Photocopying of U.S. Government Identification (CAC) is a violation of Title 18, U.S. Code Part I, Chapter 33, Section 701 and punishable by both fine and imprisonment. Although the asking for military/government identification is totally permissible by commercial establishments, there is a prohibition on duplication of government identification. A state driver license or other form of photo identification should be provided to be photocopied if an establishment insists on a photocopy of the traveler’s identification. Please ensure all employees are aware of this law.

AT Level I Awareness Training. This standard language is for contractor employees with an area of performance within an Army controlled installation, facility or area. All contractor employees, to include subcontractor employees, requiring access to Army installations, facilities and controlled access areas shall complete AT Level I awareness training within 30 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. The contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee, to the COR or to the contracting officer, if a COR is not assigned, within 60 calendar days after completion of training by all employees and subcontractor personnel. AT level I awareness training is available at the following website:

http://jko.jten.mil.

Access and general protection/security policy and procedures. This standard language is for contractor employees with an area of performance within Army controlled installation, facility, or area. Contractor and all associated sub‐contractors employees shall provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office.

Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204‐9, Personal Identity Verification of Contractor Personnel) as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

For contractors requiring Common Access Card (CAC). Before CAC issuance, the contractor employee requires, at a minimum, a favorably adjudicated National Agency Check with Inquiries (NACI) or an equivalent or higher investigation in accordance with Army Directive 2014‐05.

The contractor employee will be issued a CAC only if duties involve one of the following: (1) Both physical access to a DoD facility and access, via logon, to DoD networks on‐site or remotely; (2) Remote access, via logon, to a DoD network using DoD‐approved remote access procedures; or (3) Physical access to multiple DoD facilities or multiple non‐DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more.

At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled NACI at the Office of Personnel Management.

For contractors that do not require CAC, but require access to a DoD facility or installation.

Contractor and all associated sub‐contractors employees shall comply with adjudication standards and procedures using the National Crime Information Center Interstate Identification Index (NCIC‐III) and Terrorist Screening Database (TSDB) (Army Directive 2014‐05/AR 190‐ 13), applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative), or, at OCONUS locations, in accordance with status of forces agreements and other theater regulations.

For contracts that require OPSEC Training. Per AR 530‐1 Operations Security, the contractor employees must complete Level I OPSEC Awareness training. New employees must be trained within 30 calendar days of their reporting for duty and annually thereafter.

For IA/Information Technology (IT) training. All contractor employees and associated sub‐ contractor employees must complete the DoD IA awareness training before issuance of network access and annually thereafter.

For IA/IT certification. Per DoD 8140.01, DoD 8570.01‐M, DFARS 252.239.7001 and AR 25‐2, the contractor employees supporting IA/IT functions shall be appropriately certified upon contract award. All contractor employees working IA/IT functions must comply with the baseline certification as stipulated in above references upon contract award.

Army Training Certification Tracking System (ATCTS) registration for contractor employees who require access to government information systems. All contractor employees with access to a government info system must be registered in the ATCTS (Army Training Certification Tracking System) at commencement of services, and must successfully complete the DOD Information Assurance Awareness prior to access to the IS and then annually.

For contracts that require handling or access to classified information. Contractor shall comply with FAR 52.204‐2, Security Requirements. This clause involves access to information classified “Confidential,” “Secret,” or “Top Secret” and requires contractors to comply with— (1) The Security Agreement (DD Form 441), including the National Industrial Security Program Operating Manual (DoD 5220.22‐M); (2) any revisions to DOD 5220.22‐M, notice of which has been furnished to the contractor.

Threat Awareness Reporting Program. For all contractors with security clearances. Per AR 381‐ 12 Threat Awareness and Reporting Program (TARP), contractor employees must receive annual TARP training by a CI agent or other trainer as specified in 2‐4b.

3.2.5 Risk Management

The contractor shall establish, implement, and maintain a proactive, on-going Risk Management Process that identifies, assesses, mitigates, and appropriately reports technical, cost, and schedule risk on this contract. The contractor shall use program reviews, reports, and IPT meetings to track risks and mitigation progress across each Delivery Order.

3.2.6 Contracting Officer’s Representative

The COR is an individual designated IAW DFARS 201.602-2 and is authorized in writing by the PCO to perform specific technical functions. The contractor will receive a copy of the COR appointment letter after Delivery Order award that will specify the extent of the COR’s authority to act on behalf of the PCO. The COR is not authorized to make any commitments or changes that will affect price, quantity, delivery or any other term or condition of a Delivery Order. Only the Contracting Officer has this authority.

3.2.7 System Safety

The contractor shall conduct system safety activities IAW AR 385-10 and MIL-STD-882. The contractor shall support and participate in semi-annual System Safety Working Groups (SSWGs) as required by the Program Manager (PM) UAS to assess on-going program flight and field operations regarding safety issues to include the review of operational instruction manuals, maintenance, and training procedures and documents, as well as conduct a system safety risk assessment to support material release requirements. The contractor shall identify hazards, assess hazard risk, identify the hazard risk mitigation measures, eliminate hazards through design selection, incorporate safety devices / features, provide warning devices, and appropriately develop / update procedures and training.

The contractor shall update the System Safety Hazard Analysis Report (SSHAR) IAW DI- SAFT-80101. The contractor shall reduce the identified risk to acceptable levels per the PMO UAS System Safety Management Plan (SSMP) and provide verification of mishap risk reduction. The hazard analyses shall include software hazard analysis that addresses both the software requirements and design for a system / subsystem and the software test plans and procedures. The contractor shall participate fully in an IPT format with the Government to review and assess on-going program flight and field operations regarding safety issues to include reviews of operations, maintenance, and training procedures / documents. The contractor shall:

(a) Ensure compliance with Government Flight Representative (GFR) requirements IAW AR 95- 20.

(b) Coordinate and administer Accident / Mishap investigations, subject to Government mishap investigation boards for operational systems.

(c) Serve as primary interface with Occupational Safety and Health Manager.

3.2.7.1 System Safety Program Plan

The contractor shall update and implement a System Safety Program Plan (SSPP) IAW DI- SAFT-81626. The SSPP shall demonstrate compliance with, and traceability to, the PM UAS System Safety Management Plan (SSMP). As an appendix to the SSPP, the contractor shall develop and provide a Software System Safety Program Plan (SwSSPP) that addresses integration of software safety within system safety and the software development process. The Software System Safety Program Plan (SwSSPP) shall comply with AMCOM Regulation 385- 17, MIL-STD-882, and specify Level of Rigor (LOR) to be performed in accordance with "Software System Safety, Implementation Process and Tasks Supporting MIL-STD-882 With Joint Software System Safety Engineering Handbook References Developed by the JS-SSA Sub- Working Group in Support of the Joint Services Weapon Safety Review (JSWSR) Boards”, April 1, 2016. The contractor shall identify, track, and manage all safety critical software. The SwSSPP shall address all software used in the system, to include Non-Developmental Item (NDI), Commercial Off The Shelf (COTS), and reuse software. The SwSSPP identifies safety-critical software functions, software contributions to system level hazards, safety-critical software requirements necessary to mitigate hazards, and the safety verification process for software, to include regression testing for modified software. Software Hazard Risk Indexes (SHRI) will be identified for all hazards affecting safety-critical and safety-related functions. The contractor shall perform Software Hazard Analyses and document the analyses in an appendix to the Safety Assessment Report (SAR). The Software Hazard Analysis process includes verification that the actual design supports elimination or reduction of the hazards. The contractor shall prepare a SAR IAW DI-SAFT-80102 that includes Hazard Tracking System Logs and a Subsystem Hazard Analysis (SSHA) as attachments.

3.2.7.2 Mishaps and Accidents

For any mishap, the contractor shall prepare and deliver an Accident/Incident Report IAW DI- SAFT-81563. The contractor shall comply with AR 385-10 – The Army Safety

Program and DA PAM 385-40 – Army Accident Investigations and Reporting for mishap and accident investigation reporting. Contractors operating Government Owned Contractor Operated (GOCO) aircraft will report all incidents and accidents meeting the reporting criteria of AR 385- 10 and DA PAM 385-40 to the appropriate PM UAS System Safety Engineer.

3.2.7.3 Environmental Safety and Occupational Health

The contractor shall prepare a Health Hazard Assessment Report (HHAR) IAW DI-SAFT- 80106.

3.2.7.4 Hazardous Materials Management Program (HMMP)

All contractor and subcontractor activities shall be in compliance with applicable Federal, state, and local environmental laws and regulations. The contractor shall ensure that design, maintenance, operation, manufacturing, programmatic decisions and trade-off studies strive to eliminate or reduce hazardous materials and waste. The contractor shall implement a Hazardous Material Management Program (HMMP) IAW National Aerospace Standard (NAS) 411. The contractor shall prepare a HMMP Plan IAW DI-MGMT-81398. The contractor shall not use any Class I Ozone Depleting Chemical/Ozone Depleting Substance (ODC/ODS) (identified at http://www.epa.gov/ozone/ods.html) or any ODC/ODS solvents (identified at http://www.epa.gov/ozone/snap/lists/index.html) in the manufacture or support of items required by this SOW unless a waiver is obtained from the Army Acquisition Executive. Any ODC/ODS refrigerant alternatives used must appear in the EPA’s Significant New Alternatives Policy (SNAP) list (identified at http://www.epa.gov/ozone/snap/lists/index.html) and have received a toxicity clearance from the U.S. Army Public Health Command (USAPHC). The Contractor shall prepare annual HMMP Reports IAW DI-MISC-81397. The HMMP Reports shall provide the following information: (1) any of the following materials that are contained within a user end item: EPA 17 List materials (identified at http://www.epa.gov/opptintr/3350/33finb1.htm), beryllium, coatings (identified by MIL SPEC), functional fluids (e.g., coolant, hydraulic fluid, petroleum products), energetics/solid rocket motor components (including Explosives Class Number), advanced composite materials (e.g., fabricated from silica, graphite, carbon, boron, fiberglass), batteries, Class I/Class II ODS/ODC materials, and asbestos; (2) a general description (to include a graphic or drawing) of where these materials are located within the end item; (3) required maintenance/repair/support materials to include: EPA 17 List materials, sealants, adhesives, coatings (identified by MIL SPEC), and Class I/Class II ODS/ODC materials; and (4) any EPCRA 302/313 materials (identified at http://www.epa.gov/emergencies/docs/chem/title3_Oct_2006.pdf) utilized in the manufacturing process. The Contractor shall provide immediate notification of any proposed hazardous material mitigation/elimination efforts that may adversely impact schedules, cost and/or performance.

3.2.7.5 Warranty

Warranty provisions as described in this section shall apply to the Basic IDIQ and all Delivery Orders.

The contractor shall warrant all items as proposed under their commercial warranty terms.

Additionally, the awardee shall warrant all items for a duration of up to eighteen (18) months from the date of acceptance, this period will include contractors commercial warranty period. If material has a shelf life the contractor shall provide warranty expiration dates based on shelf life.

The warranty shall include replacement of defective components and/or systems and replacement of defective spare parts to include shipping costs associated with the replacement of defective components and/or systems, including spares. Any replacement of components or parts shall be accomplished with minimum interruption of system operation. Contractors are responsible for round trip shipping, packaging and handling costs of all items repaired or replaced under warranty.

3.3 Systems and Parts

The contractor shall provide UAS systems, parts and components under one or more of the domains listed below. The payloads and other major component categories represent logical groupings of parts within a system to allow for competition on key technologies within this contract. Current RQ-11B and RQ-20A components shall be provided IAW SOW. The contractor shall provide the following systems and other parts and components as listed in schedule B and Parts list/Price Workbook:

• Systems - LRRS and MRM systems

- LRRS Unmanned Aircraft

- MRM Unmanned Aircraft

• Future FCS

• Ground Control Systems (TOGA)

• Other Major Components - Major LRUs not included in other domains

- Batteries

- Flight Surfaces

- Fuselages

- Payloads o Current RQ-11B and RQ-20A payloads

- Alternate MRM and LRRS payloads

- Current and alternate payload repair parts

• RQ-11B and RQ-20A spare and repair parts to include legacy Radios and Ground Control Systems

When required by Delivery Order, the contractor shall provide the capability to supply any item within their applicable domain(s) using the products’ technical specifications, data and production drawings provided as Government Furnished Information (GFI) as applicable.

3.3.1 Upgrades and Modifications

Upgrades and modifications to products previously purchased and approved through prior PVT shall require an Engineering Change Proposal (ECP) be provided to the Government by the contractor. The contractor shall deliver ECPs and Modification Work Orders (MWOs) IAW the ECP process outlined in section 3.4.4 of this SOW. The contractor shall perform all necessary work to complete the ECP and submit the ECP to the Government Configuration Control Board (CCB) for approval. The Government will determine what level of testing is required prior to approving the new version of the product. For planning purposes, anticipated ECPs may include, but not be limited to the following:

• Interoperability with fielded GCS/Government-owned controllers

• One System Remote Video Terminal (OSRVT) interoperability

• Radios and avionics kits to support operational frequency changes

• ECP Spiral upgrades in support of radios and avionics kits to support operational frequency changes.

• Obsolescence issues.

3.3.2 Parts Obsolescence

The contractor shall assume full responsibility for Parts Obsolescence issues, resolutions, and implementation for the term of the contract. Through the ordering period of the contract, the contractor shall receive Government approval via the ECP process to:

(1) identify alternate sources, replacement parts, or optional part numbers for parts and materials that become obsolete or damaged and need repair, and

(2) revise applicable engineering drawings, schematics, and specifications to incorporate the new information.

The parts obsolescence program and procedures shall be made available for review by Government Obsolescence Working Group.

3.3.3 Quality Program

3.3.3.1 Quality Control Program

As applicable by Delivery Order:

The contractor shall implement and maintain an effective Quality Control Program to ensure performance complies with this SOW. The contractor shall develop and implement procedures to identify and prevent defective parts. The contractor shall prepare and deliver a Quality Program Plan (QPP) IAW DI-QCIC-81722. When required by delivery order the Quality Control Program and Quality Program plan shall be IAW ANSI/ISO/ASQ 9001:2008, or Government approved equivalent. Product Verification Test (PVT) and Factory Acceptance Test (FAT) will be utilized to evaluate product conformance to the contract specification.

3.3.3.2 Factory Acceptance Test (FAT)

The contractor shall prepare a Factory Acceptance Test (FAT) Plan and Procedures for all equipment that is procured or goes through final assembly at the contractor’s facility prior to being delivered to the Government. The contractor shall prepare and deliver a FAT IAW DI- QCIC-80553 and conduct acceptance testing of the following components including but not limited to: Complete Systems, Air Vehicles, EO/IR Payloads, GCS/RVT, avionics, radios and battery chargers, as directed by the Government. The contractor shall prepare FAT Procedures IAW DI-SESS-81704. The contractor shall prepare and deliver acceptance test results IAW DI- NDTI-80809. Final inspection and acceptance testing shall be performed by the contractor at a contractor-provided test facility and verified/observed by DCMA and/or TUAS PdO personnel.

Under certain circumstances, final inspection and testing will be conducted by TUAS PdO personnel at the destination; however, this will be specified within an individual Delivery Order when required. Federal Acquisition Regulation (FAR) clause 52.246-2, “Inspection of Supplies—Fixed Price,” and ANSI/ASQC Z1.4-1993, Sampling Plan and Tables for Inspection by Attributes, which are in effect the date of award for all Delivery Order actions shall apply.

3.3.4 Product Verification Testing (PVT)

Supply Contract Line Item Numbers (CLINs) are for products that have been previously approved or purchased under prior or current PM UAS contracts. These products will not require additional PVT. Alternate Product CLINS are for those items that have not been previously approved or purchased under prior or current PM UAS contracts and will require testing and approval in order to be classified as a Supply CLIN and be eligible for purchase.

The Government will utilize contractor testing where possible to reduce costs. To support this approach, the contractor shall provide as requested: past test plans, past test reports, and planned contractor test plans. The plan shall include systems or material that must pass PVT before delivery of LRRS and MRM systems, and be prepared and delivered IAW DI-QCIC-80553. The contractor is responsible for ensuring that supplies are manufactured, produced, and subjected to all tests required by applicable material specifications/drawings specified in the purchase description of the IDIQ contract and subsequent Delivery Orders. The contractor shall produce systems and parts that will be tested to verify performance and to ensure the effectiveness of the manufacturing process, equipment and procedures.

The details of specific PVT will be outlined in applicable Delivery Orders. For planning purposes, PVT shall include, but not be limited to, part or all of: flight safety; personnel safety;

mechanical/dimensional conformance; environmental IAW MIL-STD-810 (e.g.: Salt Fog, Shock, Vibration, Moisture and Humidity, Sand and Dust, Fungal, Rapid Decompression);

spectrum analysis; Electromagnetic Testing (MIL-STD-461 and MIL-STD-464); Hazards of Electromagnetic Radiation to Ordinance (HERO), Hazards of Electromagnetic Radiation to Fuel

(HERF), Hazards of Electromagnetic Radiation to Personnel (HERP); endurance, range, navigation modes and lost link behaviors, sensor fidelity and tracking, and IOP compliance.

3.3.4.1 PVT, Procedures and Reports

The PVT shall be conducted at Government approved facilities. The contractor shall coordinate with the Government to provide all necessary equipment and manpower necessary to facilitate the conduct of testing. For specific tests within the PVT for which the contractor wishes to execute, the contractor shall prepare and deliver detailed test plans and procedures IAW DI- SESS-81704 to demonstrate performance requirements. The contractor shall prepare and submit Test/Inspection Reports IAW DI-NDTI-80809.

3.3.4.2 Failure Analysis and Corrective Action Report (FACAR)

The contractor shall notify the Government within 48 hours of each failure that occurs during FAT and shall prepare and deliver a FACAR IAW DI-SESS-81315. The FACAR shall include a summary of the analysis, identify the root cause(s), describe the corrective action(s) taken to prevent recurrence, identify if any delivered products or spares are affected, specify if Training Packages or Technical Manuals require update, provide notification for potential delivery schedule impact, and define cut-in points for related design and/or process improvements. The FACAR shall not be considered closed until the Government has approved the FACAR.

3.3.5 Failure Modes, Effects, and Criticality Analysis (FMECA)

The contractor shall maintain an FMECA Database IAW best commercial practices, representing the components to be delivered. The contractor shall update the FMECA to reflect the effects and criticality of hardware and software failures, safety hazards, the impact of engineering design changes, results of corrective actions, and approved design changes. The contractor shall make the FMECA available to the Government engineering IPT. The contractor shall prepare and submit FMECA Reports IAW DI-SESS-81495.

3.3.6 Failure Reporting and Corrective Action System (FRACAS)

The contractor shall implement a closed-loop FRACAS to ensure all failures are analyzed and corrective actions are developed and implemented. All failures experienced during contractor or Government testing shall be classified and tracked as part of the FRACAS. The contractor shall prepare and deliver a Failure Summary and Analysis Report IAW DI-SESS-80255. The contractor shall coordinate with the Government to ensure that each Government-generated Incident Report is traceable to a FRACAS Report. The contractor shall establish a Failure Review Board, with Government participation, for review, disposition and closure of SUAS failures. Failures shall not be closed without Government approval.

3.3.7 Item Unique Identification (IUID)/Radio Frequency Identification (RFID)

Applicable items delivered as part of this contract shall be marked IAW MIL-STD-130 according to the criteria in DFARS clause 252.211-7003, 252.711-7006. The PCO may designate additional items that shall be included for IUID/RFID marking. The Baseline Description document delivered as part of this effort shall include identification of items designated for IUID/RFID marking. All items designated for IUID/RFID marking including embedded items shall be reported IAW DI-MGMT-81804 upon completion of contract delivery.

3.3.8 Flight Operations

The contractor shall support production flights and acceptance test flights for the LRRS andMRM SUAS. The contractor shall coordinate procedures and scheduling of air space and frequencies with appropriate Government and local area personnel to ensure flight procedures comply with local and area requirements and appropriate flight regulations.

3.3.9 Packaging, Shipping

The contractor shall package and ship all equipment, systems and materials IAW standard commercial practices and standards, or as specifically defined in individual Delivery Orders.

3.3.10 Software Products

A fully pre-paid, non-revocable license shall be provided for all commercial software. The contractor shall prepare/revise and deliver the following software product deliverables based on individual Delivery Order requirements IAW:

Computer Software Products DI-IPSC-81488

Software Test Plan DI-IPSC-81438

Software Test Report DI-IPSC-81440

Software Test Description DI-IPSC-81439

Software Version Description DI-IPSC-81442

Software Requirements Specification DI-IPSC-81433

Software Design Description DI-IPSC-81435

Software Product Specification DI-IPSC-81441

Software User Manual DI-IPSC-81443

Software Transition Plan DI-IPSC-81429

Software Development Plan DI-IPSC-81427

System/Software Integration Laboratory (SIL) DI-SESS-81770

Development & Management Plan

Software Resources Data Reporting DI-MGMT-81739

- Initial Developer Report and Data

Software Resources Data Reporting DI-MGMT-81740

- Final Developer Report and Data Dictionary

3.4 Systems Engineering

3.4.1 Configuration Management (CM)

As applicable by Delivery Order:

The contractor shall serve as the configuration management activity for applicable Delivery Orders and shall be responsible for all functions related to the configuration management of engineering documentation to include change management of the functional, allocated, and product configuration baselines for all systems, subsystems, assemblies, components and parts delivered under awarded Delivery Orders. The contractor shall define and control all interface requirements and ensure compatibility and interoperability for hardware and software components. The contractor shall designate a single Configuration Manager (CM) to manage the Delivery Order configuration.

The contractor shall establish, update and deliver Baseline Description Documents IAW DI- SESS-81121 for the delivered products as required per Delivery Order. The Baseline Description

Document shall be updated as changes and spiral developments are incorporated into the system configuration.

3.4.2 Configuration Management Plan (CMP)

The contractor shall develop and implement a Configuration Management and Data Management (CM/DM) program to include configuration management planning, configuration identification, configuration control, and configuration verification and auditing. The contractor shall use MIL- HDBK-61, SAE EIA-649 and SAE EIA-649-1 as a guide in developing the CM/DM program and plan. The contractor shall prepare and deliver a program unique CMP IAW DI-SESS-80858.

The CMP shall document the contractor’s configuration and data management organization,…