FTUAS_Draft_RFP_Package.pdf

Solicitation Number: W911QY-18-R-0048 Future Tactical Unmanned Aerial Systems (FTUAS)

THIS IS A DRAFT RFP FOR INDUSTRY REVIEW AND FEEDBACK.

(i) INTRODUCTION: This is a combined synopsis/solicitation for commercial items prepared in accordance with the format in FAR Subpart 12.6, as supplemented with additional information included in this notice. This announcement constitutes the only solicitation; proposals are being requested and a written solicitation will not be issued.

(ii) SOLICITATION TYPE: This combined synopsis/solicitation, W911QY-18-R-0048, is a Request for Proposals (RFP) issued by Natick Contracting Division (NCD) on behalf of the PEO-Aviation.

(iii) CURRENTNESS: The Solicitation and incorporated provisions and clauses are those in effect through Federal Acquisition Circular 2005-97 Effective 24 Jan 2018.

(iv) SET ASIDE: Market research has indicated there are not enough small businesses available to conduct a set-aside, therefore this requirement is Full and Open with no set-aside. The North American Industry Classification System (NAICS) code is 336411. The small business size standard for the NAICS Code is 1500.

(v) Contract Line Item Numbers (CLINs): This CLIN structure for the IDIQ Contract is listed below:

Ordering Period (2-years):

CLIN 0001 – Systems Purchase (Firm Fixed Price) CLIN 0002 – System Components (Firm Fixed Price) CLIN 0003 – Replacement and Spare Parts (Firm Fixed Price) CLIN 0004 – Field Service Representatives (FSR) Support (Cost Plus Fixed Fee) CLIN 0005 – Contractor Logistical Support (CLS) (Cost Plus Fixed Fee) CLIN 0006 – New Equipment Training (NET) (Cost Plus Fixed Fee) CLIN 0007 – Contract Data Requirement List (CDRL) CLIN 0008 – RESERVED (Travel, ODCs, CMR) CLIN 0009 – RESERVED (Travel, ODCs, CMR) CLIN 0010 – RESERVED (Travel, ODCs, CMR)

Systems, parts, components will be issued with the unit of “each” with quantities based on delivery requirements. The CLS and FSR Support, Travel, and ODC CLINs will be issued with the unit “Job” at a Quantity of 1. The CMR CLINs will be issued at the unit “each” and the quantity will vary based on the required deliveries.

(vi) DESCRIPTION OF REQUIREMENTS: See attached Performance Work Statement (PWS) and CDRLs.

(vii) DELIVERY: Delivery requirements and instructions will be determined at the Delivery Order level.

(viii) PROPOSAL INSTRUCTIONS: The provision of FAR clause 52.212-1, Instructions to Offerors -- Commercial, applies to this acquisition. The attached Instructions to Offerors is included in addendum to FAR clause 52.212-1.

(ix) EVALUATION OF PROPOSALS: The provision of FAR clause 52.212-2, Evaluation -- Commercial Items, will be utilized to determine award. Below is incorporated in addendum to FAR Clause 52.212-2:

Trade-Off procedures will be used. Three factors will be used to determine award. These factors are:

1) Technical,

2) Program Management, and

3) Price.

Technical and Program Management, when combined, are more important than Price. The technical and program management requirements will be evaluated IAW the Army Source Selection Supplement on a scale of Unacceptable, Marginal, Acceptable, Good, and Outstanding.

1) Technical requirements are listed in the attached PWS.

2) Program Management will have several subfactors. These are:

2.1) Design / System Technical Maturity 2.2) Facilities and Equipment / Manufacturing Readiness 2.3) Management Responsiveness / Program Management Approach 2.4) Inventory/Subcontractor Management Approach 2.5) Staffing/Personnel Management/Experience 2.6) Quality Control/Management 2.7) Configuration Management/Control Processes 2.8) Risk Management Mitigation

3) Price will be evaluated for Reasonableness. Cost factors for associated Cost CLINs will be evaluated for Reasonableness and Realism.

In addendum FAR 52.212-2, the Government will be hosting a No-Cost fly-off, where offerors who have been determined to be in the competitive range after review of paper proposals will have the opportunity to demonstrate their systems. This fly-off will be at cost of the offeror and will be no cost to the Government. Following the Fly-Off event, the final awardees will be determined based on the technical performance of the system.

(x) OFFEROR REPRESENTATIONS AND CERTIFICATION: The provision of FAR clause 52.212-3, Offeror Representations and Certifications -- Commercial Items applies to this solicitation.

(xi) Applicable Clauses Required: FAR clause 52.212-4, Contract Terms and Conditions -- Commercial Items, applies to this acquisition.

The following FAR and DFARS clauses apply to this acquisition and are incorporated by reference in addendum to FAR 52.212-4:

52.202-1 Definitions NOV 2013 52.203-3 Gratuities APR 1984 52.203-12 Limitations on Payments to Influence Certain Federal Transactions OCT 2010 52.209-7 Information Regarding Responsibility Matters JUL 2013 52.216-19 Order Limitations OCT 1995 52.216-22 Indefinite Quantity OCT 1995

52.216-27 Single or Multiple Awards OCT 1995 52.217-5 Evaluation of Options JUN 1990 52.217-9 Option to Extend the Term of the Contract MAR 2000 52.232-40 Providing Accelerated Payments to Small Business Subcontractors DEC 2013 252.203-7000 Requirements Relating to Compensation of Former DoD Officials SEP 2011 252.203-7005 Representation Relating to Compensation of Former DoD Officials NOV 2011 252.204-7011 Alternative Line Item Structure SEP 2011 252.204-7015 Notice of Authorized Disclosure of Information for Litigation Support MAY 2016 252.216-7006 Ordering MAY 2011 252.232-7010 Levies on Contract Payments DEC 2006 252.244-7000 Subcontracts for Commercial Items JUN 2013 252.203-7003 Agency Office of the Inspector General DEC 2012 252.204-7008 Compliance with Safeguarding Covered Defense Information Controls OCT 2016 252.204-7012 Safeguarding Covered Defense Information and Cyber Incident

Reporting

OCT 2016

252.205-7000 Provision of Information to Cooperative Agreement Holders DEC 1991 252.211-7003 Item Unique Identification and Valuation MAR 2016 252.211-7006 Passive Radio Frequency Identification MAR 2018 252.211-7008 Use of Government-Assigned Serial Numbers SEP 2010 252.215-7008 Only One Offer OCT 2013 252.215-7010 Requirements for Certified Cost or Pricing Data and Data Other Than

Certified Cost or Pricing Data--Basic

JAN 2018

252.223-7008 Prohibition of Hexavalent Chromium JUN 2013 252.225-7009 Restriction on Acquisition of Certain Articles Containing Specialty

Metals

OCT 2014

252.225-7010 Commercial Derivative Military Article—Specialty Metals Compliance Certificate

JUL 2009

252.225-7012 Preference for Certain Domestic Commodities DEC 2017 252.226-7001 Utilization of Indian Organizations, Indian-Owned Economic

Enterprises, and Native Hawaiian Small Business Concerns

SEP 2004

252.227-7037 Validation of Restrictive Markings on Technical Data SEP 2016 252.232-7003 Electronic Submission of Payment Requests and Receiving Reports JUN 2012 252.232-7006 Wide Area WorkFlow Payment Instructions MAY 2013 252.232-7011 Payments in Support of Emergencies and Contingency Operations MAY 2013 252.239-7017 Notice of Supply Chain Risk NOV 2013 252.239-7018 Supply Chain Risk OCT 2015 252.243-7002 Requests for Equitable Adjustment DEC 2012 252.246-7003 Notification of Potential Safety Issues JUN 2013 252.246-7008 Sources of Electronic Parts DEC 2017

The following are added by full text in addendum to FAR 52.212-4:

52.252-1 Clauses Incorporated by Reference (Feb 1998)

This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at this/these address(es):

Federal Acquisition Regulation (FAR): http://farsite.hill.af.mil/vmfara.htm Defense Federal Acquisition Regulation Supplement (DFARS): http://farsite.hill.af.mil/vmdfara.htm Army Federal Acquisition Regulation Supplement (AFARS): http://farsite.hill.af.mil/vmafara.htm

(xii) Applicable Clauses Required to Implement Statues or Executive Orders: The clause 52.212-5, Contract Terms and Conditions Required To Implement Statutes Or Executive Orders -- Commercial Items, applies to this acquisition.

(xiii) Additional Clauses: No further clauses.

(xiv) Defense Priorities and Allocations System (DPAS): None Applicable.

(xv) SUBMISSION: Proposals shall be submitted electronically to Mr. Jeremy Deorsey at Natick Contracting Division (NCD) via email: jeremy.a.deorsey.civ@mail.mil. All proposals shall be submitted by 1700 (5:00PM) Eastern Time on [INSERT DATE].

**Proposals will only be accepted electronically via the email address provided above**

(xvi) QUESTIONS: Questions regarding this solicitation can be directed to the Contract Specialist (KS) Jeremy Deorsey at the above listed email address. Questions must be submitted only through email and no questions will be addressed through phone calls. All technical questions must be submitted no later than 1700 (5:00PM) EST [INSERT DATE].

Contracting Office Address:

Army Contracting Center – Aberdeen Proving Ground, ATTN: CCRD-NA-SY, Natick Contracting Division Building 1, General Greene Ave, Natick, MA 01760-5011

Point of Contact(s): Jeremy Deorsey; jeremy.a.deorsey.civ@mail.mil; (508) 233-6192 http://farsite.hill.af.mil/vmfara.htm http://farsite.hill.af.mil/vmdfara.htm http://farsite.hill.af.mil/vmafara.htm mailto:jeremy.a.deorsey.civ@mail.mil mailto:jeremy.a.deorsey.civ@mail.mil

ADDENDUM TO FAR 52.212-1 – INSTRUCTION TO OFFERORS

In response to this RFP, sufficient documentation is required to substantiate vendor claims of system maturity, capability, performance, safety, reliability, and cybersecurity. Information submitted in response to this RFP shall be sufficient to substantiate the entire system is TRL 8 or greater. Substantiation in the form of detailed system and subsystem technical descriptions, vehicle and sensor performance, software and network security, initial and continued airworthiness based on analytical and test data are required to be provided in a technical report format within a single Microsoft Word document. The document must be formatted with 12-point Arial font, sentence case, 1-inch borders, and provide a summary of all subject areas numbered as they are listed below (including all items addressed in the PWS, as referenced in Section 1.33, Assertion and Evidence), method of validation (i.e.

analysis, ground test, flight test, operational usage, vulnerability scans, etc.), sample analytical and test results, and references to all supporting data.

Supporting ground and flight test reports shall contain scope and method of test along with clearly defined system configurations. Supporting data shall be accompanied by technical drawing packages, diagrams, and photos as applicable to support a full technical review by a panel of government representatives. Qualification standards applied for the entire platform and individual components shall be included in the documentation. An assessment of ability to achieve airworthiness and cybersecurity qualification at a system and subsystem level shall be provided.

Data already captured in systems operators manuals, maintenance manuals, or technical manuals shall be referenced by page number and the reference document provided. Documentation subject areas that are not applicable will be listed as such and an explanation provided. The following list presents the MINIMUM required documentation subject areas, while EXAMPLE data which may accompany each subject area (and shall be addressed in most cases) is provided as a reference.

1.1 Aircraft description

Aircraft model and version, list configurations and differences between aircraft models, include operational implications between aircraft versions.

1.2 System description

Description of the vehicle, launch, and recovery systems. Vehicle description includes a depiction of major subsystems (propulsion, fuel, payload, vehicle control, navigation, etc.) relative to the vehicle. Description of vehicle subsystems shall be sufficiently detailed to provide an understanding of its functions, interfaces to other subsystems, normal and emergency/backup modes, dependency on intra and extra-vehicular information (data links, operator commands, etc.). Description includes processing modules, their interfaces, software architecture, and software qualification standards used (see Software subject area). Include design drawings of the system showing dimensions, weights, material, hardware assembly, and installation. Include description and dimensions for the launch and recovery area, including the approach (air and ground) pathway clearances needed.

1.3 Airframe and system structures

Load criteria and structural analysis (static and fatigue), limit and ultimate loads, material types and properties, margins of safety, structural reports of test results, finite element analysis results, detailed structural analysis and substantiation of crashworthiness.

1.4 Airframe dynamic analysis

Vibration and modal analysis description and test results. Substantiation of separation between natural and driving frequencies (resonance avoidance).

1.5 Electrical systems

Electrical interface wiring diagrams (interface control document) in block and/or schematic format, power requirements (AC and DC), noise floor, Electromagnetic Interference (EMI)/Electromagnetic Compatibility

(EMC)/Electromagnetic Vulnerability (EMV) results, MIL-STD-461/462 or ADS-37A PRF results, MIL-

STD-704 requirements, electrical loads analysis report (power distribution, circuit breaker protection, wire-sizing), power source (buss and/or circuit breakers), excess power available regarding total electrical load.

Ground power analysis, engine starting, and battery cold soak limits. Address the Hazards of

Electromagnetic Radiation to Ordnance, Hazards of Electromagnetic Radiation to Personnel, and Hazards of

Electromagnetic Radiation to Fuel for equipment that emits Radio Frequencies (RF). Installation of electronic systems which are flight critical shall be subject to High Intensity Radiated Field testing (HIRF) and documentation provided.

1.6 Alternator/Generator

Type (brushless, brushed, etc.), manufacturer, make, model, and power rating.

1.7 Propulsion

Manufacturer, model, variant (if applicable), power/torque rating and associated curves referenced to revolutions per minute (RPMs) and altitude, specific fuel consumption (SFC) at rated max power and cruise/loiter. Define any special fuel requirements. Also include descriptions of the following systems (to include but not be limited to): engine management/control system (type/detailed description of operation), ignition system, fuel management and delivery system, all system monitors and sensors (i.e. cylinder head temperature sensors, coolant temperature sensors, mass airflow sensors, manifold absolute pressure sensors, throttle position sensors, exhaust gas temperature sensors, oxygen/lambda sensors, etc.). Additionally, all engine warning systems shall be described along with associated actions based on alerts. Mean time between failure (MTBF) and mean time between overhaul (MTBO) shall be given as well as any FAR Part 33 test reports/results.

1.8 Fuel systems

Fuel type, fuel specifications, fuel system type (gravity feed, pressure feed), fuel measuring/indicating system, fuel tank containment approach under crash conditions, fuel/oil ratio, max/min quantity. Describe the fueling procedures, identify any special equipment needed, and provide the timing to refuel the aircraft from a zero state.

1.9 Propeller

Type, manufacturer, make, model, configuration, performance.

1.10 Hydraulic systems

Type, components, description, failure modes.

1.11 Autopilot/flight controls

Components, modeling data/analysis/validation, and failure modes analysis. Detailed description of all flight modes and gain sets. Discuss unusual/un-commanded attitude/altitude detection and response, and stall/spin detection, avoidance, and response. Lost link description/performance. Flight Termination System description. Lost Global Positioning System (GPS) description/ performance. Other emergency modes description/performance. Testing and validation methods. Discuss level of automation (i.e. pilot/operator input vs. autopilot automated responses) and ability to modulate flight profile in order to remain within the safe operating envelope as a function of current conditions. If the pilot commands maneuvers outside the safe operating envelope, will the autopilot modify flight control inputs, or will the autopilot allow operation beyond limitations? If the autopilot does intervene to prevent exceedances beyond the safe operating envelope, discuss in detail the sequence of inputs, processing, commanded outputs, control deflections, and feedback.

1.12 Aerodynamic characteristics/Handling Qualities

Discuss how the stability and control characteristics were initially measured/defined and what method was used to validate/verify. Discuss specific tests and test conditions, modeling, and analysis.

1.13 Flight Envelope

Provide and discuss how the flight envelope was defined and what method was used to validate/verify.

Discuss specific tests and test conditions.

1.14 Performance

Vehicle performance model and validation method. Climb/descent/cruise flight performance data/charts.

1.15 Navigation systems

Type, manufacturer, make, model, description, functional block diagram, system components layout and analysis, performance summary, accuracy and modes of operation, component reliability and failure modes.

1.16 Avionics/Communications

Avionics functional block diagram, components layout and analysis, system performance summary/description. Communications and Command Control (C2) system description (air to air, air to ground, etc.), cooperative avionics or tracking equipment description (Identification Friend or Foe, Traffic

Collision Avoidance System, Automatic Dependent Surveillance – Broadcast , etc.), and encryption capability.

1.17 Software

Air vehicle, ground station, data links, and others as applicable – Testing, qualification (i.e. DO-178 and version), certification, substantiation, and configuration management. List all commercial off the shelf

(COTS) software that is part of the flight critical and flight essential control chain (i.e. any system software that can affect control of aircraft). Describe the COTS software manufacturer’s safety practice, change and implementation process. Describe how the COTS software is distributed to the fleet. List and describe non-

COTS software (software developed by the vehicle manufacturer independently) that is part of the flight critical and flight essential control chain. Describe non-COTS software development process. Describe non-

COTS software safety practices (development, Validation & Verification, testing, etc.). Describe how non-

COTS software revisions are distributed to the fleet.

1.18 Weight and balance

Longitudinal and lateral calculations with equipment locations (station and butt line). Empty weight, max gross weight, payload weight, fuel weight, center of gravity ranges/envelope and method of validation.

1.19 Ground station

Hardware, software, payloads interface, human machine interface, power requirements, launch and recovery systems. Provide documentation on controller operation and video features. Personnel manning procedures, checklists, and duty descriptions.

1.20 Ground support equipment

Generators, batteries, structures, system deployment mechanisms.

1.21 Configuration Management

Processes, procedures, and description of current and expected configurations. All foreign components utilized in the proposed system are to be identified along with the associated manufacturer.

1.22 Instrumentation

Flight test, telemetry, or other required instrumentation.

1.23 Environmental conditions

Limitations, restrictions and test results – altitude, temperature, winds, turbulence, lightning, visible moisture/humidity, vibration, crash shock, and explosive atmosphere, MIL-STD-810G results.

1.24 System safety

System safety assessment report in accordance with (IAW) MIL-STD 882E, dated 11 May 2012. Accident and incident rates per current flight hours. Describe the primary phases of flights where majority of accidents occur (takeoff, landing, enroute maneuver, etc.). List accidents (both number and percentage of total) that were material failures, human error, or external contributors (i.e. bird strike). Provide the most current total of fleet/systems hours of the current configuration. Also include the type of available aircraft lighting and/or other safety features.

1.25 Cybersecurity

System’s ability to support or provide secure configuration including Access Control, Auditing, Identification & Authentication, Least Functionality, Encryption, System and Data Integrity, Patch

Management, and Network Security/Monitoring. Include vulnerability scans using industry-standard tools such as Tenable Nessus.

1.26 Mission payloads

Electro-optical/infrared sensor, airborne communications relay, data links, capabilities (including latencies, line of sight range), imagery description and associated embedded (or other) data, testing, external stores.

Note any usage of standards, such as from the Motion Imagery Standards Board (MISB), National Imagery

Transmission Format (NITF), etc. Laser illuminator/pointing specifications and safety information. Include laser illuminator useful range, Above Ground Level (AGL), and estimated spot size under described conditions of visibility. Provide aircraft/sensor information on >X ft. AGL (day) and >X ft. (night); standoff ranges; Field of Views (FOVs); zoom capabilities; Probability of Recognition (PR) for Electro-Optic and

Infrared; Modes of Operations; color; etc. In addition, provide an estimated Target Location Error (TLE) in the form of a Circular Error (CE) = X meters and Linear Error (LE) = X meters based on a minimum of an 8 digit grid location from an operationally effective altitude and standoff range of X km from the imaged target. If other payloads have been integrated and are available, include a description. “X” to be defined by the vendor.

1.27 Mission

Provide endurance (time to target, time on station, time to base) data based on the number of aircraft required to sustain operations for 96-hours at an Operational Tempo (OPTEMPO) of 24-hours a day and fuel needs.

Provide endurance mission profile:

X (e.g. 50) km range from launch and recovery site to loiter point. State maximum operating range.

Standard day conditions and no winds

Altitude of the launch and recovery site of 0 ft. Mean Sea Level (MSL)

Climb and descend on route

Cruise airspeed and altitude (e.g. 70 Kias at 11,000 ft. MSL)

Dash airspeed

Loiter time and operational altitude

State altitude inaudible from the ground (@ 65dB and 35 dB)

X-minute fuel reserve. (e.g. 30 minutes)

1.28 Servicing and maintenance

Procedures and intervals.

1.29 Radio frequency authorization

To support operations on a government range and frequency assignment, provide the following information for all system transmitters: equipment nomenclature, frequency range, emission designator, maximum power, and airborne vs. ground based.

1.30 Sustainment

To support a 96-hour OPTEMPO at a 24 hour per day without resupply, provide list of equipment/supplies needed to include transport and operations. (E.g. air vehicles, ground control stations, ground data terminals, spare parts, tools, support equipment, petroleum, oil, and lubricant capable of maximizing air vehicle spares that provide redundancy to the ground force commander)

1.31 Vendor Assessment of Technology Readiness Level (TRL) and Manufacturing Readiness Level (MRL)

To support MRL assessment, vendors shall complete the MRL Vendor Questionnaire Excel document and submit with the substantiation package.

1.32 Vendor Assessment of capability to achieve airworthiness qualification.

1.33 Assertion and Evidence of ability to achieve requirements as outlined in the PWS.

Additionally, all vendors shall provide the following documentation to support operations on a government range:

(1) internally approved Flight Operations Procedures (FOPs) and Ground Operations Procedures (GOPs), (2) radio frequency authorization details (IAW RFI paragraph 4.28), and (3) an Environmental Impact Statement (EIS) or equivalent details to support assessment (requirements to dig at launch/recovery location, HAZMAT considerations, etc.).

Attachment 001

Performance Work Statement

For Group 2/3 Unmanned Aircraft Systems

And

Contractor Logistics Support

July 2018

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense (DoD) and U.S. DoD contractors only; Administrative or Operational Use, 28/10/2016. Other requests for this document shall be referred to the Program Executive Office Aviation, Unmanned Aircraft Systems Project Management Office, ATTN: SFAE-AV-UAS-TUAS, Redstone Arsenal, AL 35898-5000.

Table of Contents

1.0 Scope

1.1 Purpose

2.0 Applicable Documents

3.0 Requirements

3.1 Program Management

3.1.1 Integrated Master Schedule

3.1.2 Performance and Cost Reporting

3.1.3 Post Award Kickoff Meeting

3.1.4 Program Management Reviews

3.1.5 Integrated Product Teams

3.2 Production

3.2.1 Quality Program

3.2.2 Inspection and Acceptance

3.2.3 Flight Testing

3.2.4 Serialization and Lot Control

3.2.5 Item Unique Identification Markings

3.2.6 Equipment Logbooks

3.2.7 Packaging and Marking

3.2.8 Shipping

3.3 Configuration Management

3.3.1 As-Built Configuration List

3.3.2 Data Accession List

3.4 Safety Requirements

3.4.1 System Airworthiness

3.4.2 Software Airworthiness

3.4.3 Mishap Investigation Support

3.5 Contractor Logistics Support

3.5.1 System Flight Hours

3.5.2 System Availability

3.5.3 Supply Chain Management

3.5.3.1 Supply Support

3.5.3.2 Unit Prescribed Load List (PLL)

3.5.3.3 Inventory Control Point (ICP)

3.5.3.4 Inventory and Shelf Life Management

3.5.3.5 Contractor Inventory Management System

3.5.3.6 Spare Parts Usage Report

3.5.3.7 Obsolescence Management

3.5.3.8 Notification of Critical Shortages

3.5.3.9 Packaging, Handling, Storage, and Transportation

3.5.3.10 Shipment of Spare Parts

3.5.3.11 Shipment of Hazardous Materials

3.5.4 Maintenance Concept

3.5.4.1 Sustainment (Depot) Maintenance

3.5.4.2 Special Tools, Ground Support Equipment, and Calibrated Items

3.5.5 Field Service Representatives

3.5.5.1 System Daily Status Report

3.5.5.2 Logbooks and TAMMS-A

3.5.5.3 Weight and Balance Forms/Records

3.5.6 Technical Manuals

3.5.6.1 Technical Manual Printing

3.5.7 New Equipment Training

3.5.7.1 Training Support Package (TSP)

3.5.7.2 NET Completion Report

4.0 Information Assurance

5.0 Hazardous Material Management

6.0 Security

6.1 Anti-Terrorism (AT) Level I Training

6.2 Access and General Protection/Security Policy and Procedures

6.3 Contractors Requiring Common Access Card (CAC)

6.4 iWATCH Training

7.0 List of Abbreviations and Acronyms

1.0 Scope

This Performance Work Statement (PWS) defines the requirements for a Firm Fixed Price contract to procure two (2) Non Developmental Item (NDI) Group 2/3 Unmanned Aircraft Systems (UAS) and associated Contractor Logistics Support (CLS) covering training, maintenance, sustainment, and operational support of these systems at two Army units. CLS activities are limited to operations inside the Continental United States (CONUS) for a minimum period of six (6) months with additional options to increase the total term to two (2) years if required.

1.1 Purpose

The purpose of this PWS is to describe the efforts necessary to conduct a demonstration with NDI Group 2/3 UAS. Project Manager Unmanned Aircraft Systems and Product Manager Tactical Unmanned Aircraft System (PdM TUAS) will procure up to six NDI Group 2/3 UAS as part of demonstrations within United States Army Forces Command Brigade Combat Teams in support of the Future Vertical Lift Cross Functional Team. This effort is being conducted to address gaps identified in the Operational Needs Statements from 82nd Airborne Division and inform future requirements in support of the Future UAS Initial Capabilities Document.

System(s) will be required for a period not to exceed two years.

2.0 Applicable Documents

All applicable documents are listed in the contract Document Summary List (DSL) by number, title, and date (Attachment 002). The document versions specified in the DSL take precedence over the generic references (without revision letters) cited in this PWS.

3.0 Requirements

The contractor shall be responsible for the production and delivery of two (2) fully operational NDI Group 2/3 UAS In Accordance With (IAW) Paragraph 3.2 Production of this PWS. The contractor shall be responsible for training Soldiers to operate and maintain the system, operational readiness, parts supply, maintenance and shipping support. The contractor shall furnish all labor and be fully responsible for obtaining all materials and technical expertise required, including any support from sub-contractors necessary to execute the requirements in this PWS.

3.1 Program Management

The contractor shall perform and manage all technical and functional disciplines to ensure the cost, schedule and performance requirements of this PWS.

3.1.1 Integrated Master Schedule

The contractor shall prepare an Integrated Program Management Report, Format 6, Integrated Master Schedule (IMS) IAW DI-MGMT-81861 (CDRL A001). The IMS shall be delivered to the Government in Microsoft Project.

3.1.2 Performance and Cost Reporting

The contractor shall prepare a Performance and Cost Report IAW DI-FNCL-80912 (CDRL A002).

3.1.3 Post Award Kickoff Meeting

The Contractor shall host a kickoff meeting at their primary location for executing the effort.

The contractor shall provide a detailed execution plan for their method to complete the scope in this PWS. The Contractor shall have at a minimum the Program Manager, Integrated Product Team (IPT) Leads, and any direct management associated with the execution of the scope of the PWS. The Contractor shall provide the charts in advance of the meeting IAW DI-MGMT-81605 and deliver IAW CDRL A003. The Contractor shall take detailed meeting minutes from the kickoff meeting IAW DI-ADMN-81250B and deliver IAW CDRL A004.

3.1.4 Program Management Reviews

The Contractor shall conduct quarterly Program Management Reviews (PMR) with the Government. The PMR location shall be at the Contractor’s facility at a date agreed to by the Government. The PMR shall cover program status, financials, issues/risks and additional topics requested by the Government. The Contractor shall provide the charts in advance of the meeting IAW DI-MGMT-81605 and deliver IAW CDRL A003. The Contractor shall take detailed meeting minutes from the kickoff meeting IAW DI-ADMN-81250B and deliver IAW CDRL A004.

3.1.5 Integrated Product Teams

The contractor shall utilize a Government/Contractor IPT structure to manage this effort. The IPTs shall include government and contractor participation with a designated IPT lead from each organization. The contractor shall establish an IPT to encompass program management, production/engineering, and logistics support functions. Additional IPTs may be stood up if deemed necessary and agreed upon by the Government. The IPT shall resolve issues/conflicts, and as such, the IPT shall develop objective means to measure program success and shall identify risk areas and develop solutions to mitigate these risks. The IPT(s) shall meet on a weekly basis, until the Government and contractor agree to reduce this to a bi-weekly requirement as the program progresses. Under no circumstance shall the IPT authorize work that impacts the existing specified cost of the contract. Only the Contracting Officer will authorize changes to the contract. Any IPT recommendation, requiring PWS modification shall be forwarded to the Contracting Officer with a justification and request to modify the contract, including projected cost and schedule impact.

3.2 Production

The contractor shall deliver two (2) complete and fully operational NDI Group 2/3 UAS to the Government No Later Than (NLT) 12 months after contract award. The NDI Group 2/3 UAS shall include all air vehicles, ground control stations, ground data terminals, ground support equipment, special tools and initial spares needed to immediately support fielding and New Equipment Training (NET).

3.2.1 Quality Program

The contractor shall implement and maintain an effective Quality Control Program IAW ANSI/ISO/ASQ 9001:2015 or equivalent systems as agreed between the contractor and the Government to ensure system performance complies with this PWS. The contractor shall develop and implement procedures to identify and prevent defective components. The contractor shall prepare and deliver a Quality Program Plan IAW DI-QCIC-81722 (CDRL A005).

3.2.2 Inspection and Acceptance

Inspection and Acceptance shall be performed IAW the contractor’s approved in-plant Inspection Procedures and Factory Acceptance Test Procedures. The contractor shall prepare and deliver an Acceptance Test Plan IAW DI-QCIC-80553A (CDRL A006) and conduct acceptance testing of the following components including but not limited to: Complete Systems, Air Vehicles, Payloads, Ground Control Stations, Ground Data Terminal and Launch/Recovery items (if required), as directed by the Government. The contractor shall prepare and submit a copy of their Final Acceptance Test Procedures IAW DI-SESS-81704 (CDRL A007). The contractor shall prepare and deliver acceptance test results of these items IAW DI-NDTI-80809B (CDRL A008). Final inspection and acceptance testing shall be performed by the contractor at the contractor-provided test facility and verified/observed by representatives from the Defense Contract Management Agency (DCMA) and/or PdM TUAS. Federal Acquisition Regulation (FAR) clause 52.246-2, “Inspection of Supplies—Fixed Price,” and ANSI/ASQC Z1.4-2003, Sampling Procedures and Tables for Inspection by Attributes, which are in effect the date of award for all delivery actions shall apply.

3.2.3 Flight Testing

The contractor shall perform acceptance test flights for any of the system(s) and/or end items delivered to the government. The contractor shall notify the Government at least 10 days prior to the acceptance flights for the opportunity to participate.

3.2.4 Serialization and Lot Control

The contractor shall maintain a system for serialization and lot control which shall provide traceability to the end item part number and serial number, as applicable, for all configurations produced under this contract. The purpose of the serialization and lot traceability is to assist in location and containment of items should any quality or design issue arise.

3.2.5 Item Unique Identification Markings

All end items, components, sub-components, assemblies, sub-assemblies and parts meeting Item Unique Identification (IUID) requirements (see Defense Federal Acquisition Regulation Supplement (DFARS) 252.211-7003 and DFARS 252.211-7007) shall be marked by the contractor with IUID-compliant 2D Data Matrix symbols IAW the latest version of MIL-STD- 130 Identification Marking of U.S. Military Property. The contractor shall place permanent IUID marks upon material delivered and address mark durability issues during the testing process prior to material delivery. The contractor shall agree with the Government upon a

Contract Line Item Number and Sub-Line Item Number or exhibit and attachment to the contract that contains all end items, components, sub-components, assemblies, sub-assemblies and parts meeting IUID requirements (see DFARS 252.211-7003 and DFARS 252.211-7007). The contractor shall utilize the Wide Area Workflow as the preferred process to register all material being delivered. The use of virtual IUID is not authorized. The contractor shall ensure that the DoD IUID Registry shall be updated whenever IUID assets are upgraded, destroyed or permanently withdrawn from service. Assets lost or destroyed due to accidents shall be inventoried and their status shall be updated in the IUID Registry.

3.2.6 Equipment Logbooks

The contractor shall provide system component logbooks and documentation using Department of the Army Pamphlet (DA PAM) 738-751 Functional Users Manual For The Army Maintenance Management System - Aviation (TAMMS-A) as a guide. The contractor shall maintain records of all maintenance actions performed on any end item component of the NDI Group 2/3 UAS during acceptance testing IAW DA PAM 738-751 TAMMS-A. Completed functional logbooks will be approved by DCMA or PdM TUAS prior to system acceptance.

3.2.7 Packaging and Marking

The contractor shall furnish all containers, packaging material, and mark items for shipping. The contactor shall use best commercial practices for packaging to assure safe delivery of equipment to its final destination.

3.2.8 Shipping

The contractor shall coordinate and cover all first destination shipping costs, this includes the delivery of material purchased from the manufacturing source to the point of Government acceptance. Shipment of the complete system(s) from point of Government acceptance to the Army customer will be the responsibility of the government.

3.3 Configuration Management

3.3.1 As-Built Configuration List

The contractor shall deliver an As Built Configuration List IAW DI-CMAN-81516 (CDRL A009) for each of the systems individual end items, down to the Line Replaceable Unit (LRU) level.

3.3.2 Data Accession List

The contractor shall provide a Data Accession List (DAL) IAW DI-MGMT-81453B (CDRL A010) of all documentation developed as part of this PWS. The contractor shall ensure documents on the DAL are available upon request.

3.4 Safety Requirements

3.4.1 System Airworthiness

The governing Army Regulation (AR) for Airworthiness of Army Systems is AR 70-62 Airworthiness of Aircraft Systems. The Aviation and Missile Research, Development and Engineering Center Aviation Engineering Directorate (AED) is the delegated authority for the execution of all Army airworthiness qualification and continued airworthiness. The U.S. Army AED utilizes multiple documents to substantiate Levels of Airworthiness, which determined by specific site of Operation and weight of the aircraft. The contractor shall obtain Level III Airworthiness, at a minimum, for the flight demo/user evaluation. The contractor shall ensure the following information is made available to the U.S. Army AED for UAS Airworthiness Qualification to obtain an Air Worthiness Release:

• Safety Assessment Report – If existing

• Functional Hazard Analysis (FHA) and Fault Tree Analysis (FTA) of the system – If existing

• System Level Failure Modes Effects and Criticality Analysis (FMECA) – If existing

• Operator's manuals

• Operator's and Crewmembers Checklist

• Emergency procedures

• Power Budget Analysis and Report

• Weight and balance Documentation

• Configuration Documentation

• Electromagnetic Interference / Electromagnetic Compatibility Check plans and reports –

If existing

• Environmental test plans and reports – If existing

• Structures Design Criteria Report – If existing

• Static Strength Reports – If existing

• Stress, Loads, and Fatigue Analyses - The fatigue analysis report should include the following: (1) identification and description of each component analyzed, the corresponding working S-N curve, analyses substantiating endurance limit and fatigue life, and all supporting test data; and (2) a summary of all endurance limits and fatigue lives. – If existing

• Finite Element Models – If existing

• Finite Element Analyses – If existing

• Fracture Analysis Report – If existing

• Damage limits and Repair Analyses/Reports – If existing

• Material Allowables Reports – If existing

• List of components that are single points of failure in the system that would lead to loss of flight of the Air Vehicles or loss of the ability to land the Air Vehicle – If existing

The contractor shall participate in a post award Technical Interchange Meeting (TIM) at the contractor’s facility and a complete production configuration system must be available on site at the time of the TIM for viewing by AED. The complete production UAS would include but is not limited to the Air Vehicle, Control Station, and Ground support equipment. The purpose of the TIM is to discuss with the systems developer and or vendor airworthiness aspects and concerns and to address questions the system proponent may have of AED.

As additional information regarding the system becomes available, the contractor shall ensure the documentation regarding the effects to any of the relevant safety documentation (FHA, FTA, FMECA), updates to the Operator's Manuals, Checklists, emergency procedures, and training plan, test plans and reports of the modified equipment against the baseline, as well as updated configuration documentation, shall be made available to the U.S. Army AED.

3.4.2 Software Airworthiness

The vendor shall provide the following artifacts:

• System Safety Program Plan (which includes Software System Safety Program Plan)

• Identification of Safety/Flight Critical Requirements (System, Hardware, and Software)

• Bi-directional Trace of Safety Requirements to Hazard Analysis

• Verification artifacts for Safety/Flight Critical Requirements

• Software Unit & Integration Test Results for Safety/Flight Critical Requirements

• Details of Loss-link and Flight Termination planning, functionality and verification

• Details of Emergency Return Home planning, functionality, and verification

• Details of Warning, Caution and advisory display, procedures, functionality, operator intended response, and verification.

• Airspace management planning and display coordination

• Details of any non-eye safe laser or weapons control planning, functionality, and verification (if applicable)

• Identification of Residual Risk

To help assess the vendor software craftsmanship/quality and software safety/airworthiness the vendor shall share the following where they exists:

• Software Version Description

• Software Development Plan

• Software Config Data Management Plan

• Problem/Bug Tracking and reporting

• Software static analysis against coding standards, and Software coverage analysis.

3.4.3 Mishap Investigation Support

In the event of a mishap or accident, the contractor shall provide technical assistance to Army mishap investigators, to include downloading/analysis of flight record data, inspections of mishap sites and wreckage, examination/operational check of hardware at the mishap site and determination of root cause down to LRU level.

The Contractor shall make the appropriate changes to system Technical Manuals (TM) if required based on the determination and corrective actions identified during the mishap investigation.

For all Class A through D mishaps the Contractor shall provide the following reports to the Government:

• Accident/Incident Report IAW DI-SAFT-81563 (CDRL A011)

• Estimated Cost Of Damage Report IAW DI-MISC-80508B (CDRL A012). The report shall include: Aircraft Serial Number, Aircraft Part Number, % Damaged, and Estimated Price, and timeline for repair.

3.5 Contractor Logistics Support

The purpose of this section is to describe the contractor’s logistics support efforts and products required during the contract period of performance.

3.5.1 System Flight Hours

The contractor shall develop a CLS support strategy to cover the training, operation, maintenance, sparing, and shipping for all supported systems based on 300 flight hours per system for a period of 6 months.

3.5.2 System Availability

Fielded systems shall maintain an operational availability rate of 85%. Operational availability is defined as "uptime" divided by "total time".

3.5.3 Supply Chain Management

The contractor shall serve as the Supply Chain Manager and provide supply chain modeling, acquisition, storage, inventory control, transportation/shipping and maintain supply points for all NDI Group 2/3 UAS spares, consumables and repair parts. The contractor shall contract with sub-tier suppliers, as required, for the repair, remanufacture, and scheduled servicing of system parts.

3.5.3.1 Supply Support

The contractor shall provide and manage a sufficient inventory of repair, replacement, and replenishment parts so that required maintenance and supply requisitions are filled to achieve/maintain the defined flight hours and availability rate in Paragraphs 3.5.1 and 3.5.2 of this PWS.

3.5.3.2 Unit Prescribed Load List (PLL)

The contractor shall provide with each system delivered to the government those repair parts (e.g. LRUs, Shop Stock, Bench Stock (consumables)) required at the unit level to support routine operation and maintenance of the system (comparable to a PLL as stated in AR 710-2, Supply Policy Below The National Level). Bench Stock is defined as Consumable Class 2, 3 (packaged), 4, and 9 supplies used by maintenance personnel. Bench stocks are authorized for support level maintenance activities, including aviation unit maintenance activities. Shop Stock is defined as repair parts and consumable supplies stocked within a support level maintenance activity for internal use during accomplishment of maintenance requests. The contractor shall maintain the contents and stockage levels of the system PLL spares package in order to meet the flight hour requirement and availability rate defined in Paragraph 3.5.1 and 3.5.2 of this PWS.

3.5.3.3 Inventory Control Point (ICP)

The contractor shall serve as the supply ICP. The contractor shall provide storage, inventory control, and serve as the supply point for all spares/repair parts using the contractor’s internal supply database management tool. The contractor shall maintain inventory accountability of all spares procured under this effort to include failed spares and/or repaired and receipted back into inventory.

In support of mission operations, the contractor shall serve as the hub for parts and equipment replacement and for receipt, storage, and shipment of parts throughout the period of performance of this PWS. The contractor shall receive and fill parts requisitions from fielded Army units. The contractor shall coordinate with units, through Field Service Representatives (FSR), to ensure unserviceable components and LRUs are recovered and transported back to the contractor ICP or depot for repair and subsequent return to inventory. The contractor shall utilize a direct exchange supply support process to aid in the recovery of durable and repairable items. The contractor shall ensure the requisitions submitted by the units are filled IAW the priority codes address on the requisition form.

3.5.3.4 Inventory and Shelf Life Management

The contractor shall manage and rotate stock with in the ICP to maintain and maximize shelf life and items within their expiration dates. Stock of unique spare parts, repair parts, and consumables shall be maintained and cycled IAW shelf life requirements and demands.

3.5.3.5 Contractor Inventory Management System

The contractor shall maintain an up-to-date supply tracking system for all items procured and processed through the ICP. The tracking system shall be able to track parts on hand and parts on order. For parts on hand, the tracking system shall denote serviceability and track items in or requiring depot maintenance action. For items in depot maintenance, the tracking system shall track shipping and due-in dates for sub-vendor items and projected maintenance completion dates for all other items. For parts on order, the tracking system shall track order dates, shipping dates, and due-in dates. The contractor shall provide the Government with read access to the internal supply management system.

3.5.3.6 Spare Parts Usage Report

The contractor shall prepare a Spare Parts Usage Reports IAW DI-ILSS-80483 (CDRL A013).

3.5.3.7 Obsolescence Management

The contractor is responsible for parts obsolescence, tracking and resolution for the term of this contract. As such, the contractor shall: (1) identify alternate sources, replacement parts, or optional part numbers for parts and materials that become obsolete; (2) requisition qualified alternate parts prior to exhausting the obsolete parts inventory; (3) revise applicable technical manuals to incorporate the new part information.

3.5.3.8 Notification of Critical Shortages

The contractor shall notify the Government through the IPT process and IAW DI-MISC-80508B (CDRL A014) of any sparing or material shortage/deficiency that impacts fleet operation and/or readiness for more than 30 days. The report shall indicate the material shortage condition and provide the anticipated hardware get well date(s).

3.5.3.9 Packaging, Handling, Storage, and Transportation

The contractor shall utilize best commercial practices in preservation and packaging to provide protection of the NDI Group 2/3 UAS components and supplies of all classes during handling, storage, and shipment/transport.

3.5.3.10 Shipment of Spare Parts

The contractor shall be responsible for the shipment of all spares and repair parts requisitioned from the field by units to support and sustain the fight hour requirement in Paragraph 3.5.1. This includes the retrograde of durable/repair items from the field to the contractors ICP or depot.

3.5.3.11 Shipment of Hazardous Materials

Based on DoD and Department of Transportation hazard classification, mode of transportation, and destination all hazardous materials associated with the NDI Group 2/3 UAS the contractor shall prepare shipment of hazardous material IAW the requirements of the United Nations Transport of Dangerous Goods Regulations, Code of Federal Regulations (CFR) Title 29, CFR Title 49, and Federal Motor Carrier Safety Regulations. Equipment shall be marked by the contractor to convey hazards and lifting limitations using CFR Title 49 and MIL-STD-1472 as a guide.

3.5.4 Maintenance Concept

System maintenance shall align with the Army’s two categories of “Field” and “Sustainment”.

Field maintenance shall consist of unit level, on-system maintenance and those repairs which returns end items and/or LRUs back to the operator or user.