Professional Documents
Culture Documents
FTUAS Draft RFP Package
FTUAS Draft RFP Package
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.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.9 Propeller
Type, manufacturer, make, model, configuration, performance.
1.14 Performance
Vehicle performance model and validation method. Climb/descent/cruise flight performance data/charts.
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
nonCOTS 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
nonCOTS software safety practices (development, Validation & Verification, testing, etc.). Describe how
nonCOTS software revisions are distributed to the fleet.
1.22 Instrumentation
Flight test, telemetry, or other required instrumentation.
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.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.
Table of Contents
1.0 Scope ..........................................................................................................................................1
1.1 Purpose ..................................................................................................................................1
2.0 Applicable Documents ...............................................................................................................1
3.0 Requirements .............................................................................................................................1
3.1 Program Management.............................................................................................................1
3.1.1 Integrated Master Schedule .............................................................................................1
3.1.2 Performance and Cost Reporting .....................................................................................2
3.1.3 Post Award Kickoff Meeting ...........................................................................................2
3.1.4 Program Management Reviews .......................................................................................2
3.1.5 Integrated Product Teams ................................................................................................2
3.2 Production...............................................................................................................................2
3.2.1 Quality Program...............................................................................................................3
3.2.2 Inspection and Acceptance ..............................................................................................3
3.2.3 Flight Testing ...................................................................................................................3
3.2.4 Serialization and Lot Control...........................................................................................3
3.2.5 Item Unique Identification Markings ..............................................................................3
3.2.6 Equipment Logbooks .......................................................................................................4
3.2.7 Packaging and Marking ...................................................................................................4
3.2.8 Shipping ...........................................................................................................................4
3.3 Configuration Management ....................................................................................................4
3.3.1 As-Built Configuration List .............................................................................................4
3.3.2 Data Accession List .........................................................................................................4
3.4 Safety Requirements ...............................................................................................................4
3.4.1 System Airworthiness .......................................................................................................4
3.4.2 Software Airworthiness ....................................................................................................6
3.4.3 Mishap Investigation Support ..........................................................................................6
3.5 Contractor Logistics Support ..................................................................................................7
3.5.1 System Flight Hours ........................................................................................................7
3.5.2 System Availability .........................................................................................................7
3.5.3 Supply Chain Management..............................................................................................7
3.5.3.1 Supply Support ..........................................................................................................7
3.5.3.2 Unit Prescribed Load List (PLL) ..............................................................................7
3.5.3.3 Inventory Control Point (ICP)...................................................................................8
3.5.3.4 Inventory and Shelf Life Management .....................................................................8
3.5.3.5 Contractor Inventory Management System ..............................................................8
3.5.3.6 Spare Parts Usage Report ..........................................................................................8
3.5.3.7 Obsolescence Management .......................................................................................8
3.5.3.8 Notification of Critical Shortages .............................................................................9
3.5.3.9 Packaging, Handling, Storage, and Transportation...................................................9
3.5.3.10 Shipment of Spare Parts ..........................................................................................9
3.5.3.11 Shipment of Hazardous Materials ...........................................................................9
3.5.4 Maintenance Concept ......................................................................................................9
3.5.4.1 Sustainment (Depot) Maintenance ............................................................................9
3.5.4.2 Special Tools, Ground Support Equipment, and Calibrated Items ...........................9
3.5.5 Field Service Representatives ........................................................................................10
3.5.5.1 System Daily Status Report ....................................................................................10
3.5.5.2 Logbooks and TAMMS-A ......................................................................................11
3.5.5.3 Weight and Balance Forms/Records .......................................................................11
3.5.6 Technical Manuals .........................................................................................................11
3.5.6.1 Technical Manual Printing ......................................................................................11
3.5.7 New Equipment Training ..............................................................................................11
3.5.7.1 Training Support Package (TSP) ............................................................................12
3.5.7.2 NET Completion Report .........................................................................................12
4.0 Information Assurance .............................................................................................................12
5.0 Hazardous Material Management ............................................................................................13
6.0 Security ....................................................................................................................................13
6.1 Anti-Terrorism (AT) Level I Training..................................................................................13
6.2 Access and General Protection/Security Policy and Procedures .........................................13
6.3 Contractors Requiring Common Access Card (CAC) ..........................................................14
6.4 iWATCH Training ................................................................................................................14
7.0 List of Abbreviations and Acronyms ........................................................................................14
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-
STD130 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:
• 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: