Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 21

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,
MILSTD-704 requirements, electrical loads analysis report (power distribution, circuit breaker protection,
wiresizing), 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
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.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.).
Performance Work Statement
For
Group 2/3 Unmanned Aircraft Systems
And
Contractor Logistics Support

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:

• 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. Sustainment maintenance shall
consist of off-system (depot) repairs that returns equipment or LRUs back to the supply system.
3.5.4.1 Sustainment (Depot) Maintenance
The contractor shall furnish all labor and supplies, materials, equipment, spares and repair parts
required to perform Sustainment maintenance (i.e. inspection, disassembly, repair, overhauls,
reassembly, and acceptance testing) on the system reparable items. The contractor shall ensure
post repair that all hardware is in a repaired and/or reconditioned state and is serviceable and
issuable without limitation or restriction. The contractor shall be accountable for each item and
piece of hardware from induction to completion. The contractor shall be responsible for
contracting to sub-tier vendors and suppliers for repair/replacement and scheduled servicing.
3.5.4.2 Special Tools, Ground Support Equipment, and Calibrated Items
The contractor shall furnish all labor, hand, and special tools required to perform Field and
Sustainment maintenance (i.e. inspection, disassembly, repair, overhauls, reassembly, and
acceptance testing) on the system reparable items. The contractor shall ensure that all required
Special Tools, Ground Support Equipment, and Calibrated Items are in serviceable and issuable
condition without limitation or restriction. The contractor shall induct and calibrate those NDI
Group 2/3 UAS specific items IAW current version of TB 43-180 Calibration and Repair
Requirements for the Maintenance of Army Materiel. The contractor shall be accountable for
inducted items through completion of repair or calibration. The contractor shall be responsible
for contracting to sub-tier vendors and suppliers for repair, replacement and scheduled servicing
/calibration as required.
3.5.5 Field Service Representatives
The contractor shall provide fully trained FSRs to support and maintain the flight hour and
system availability requirements described in Paragraphs 3.5.1 and 3.5.2 of the PWS. The FSRs
shall be fully trained on the delivered NDI Group 2/3/ UAS system configuration and be capable
of providing Field-level mechanical, technical, weight and balance, documentation support,
troubleshooting, identification, diagnosing, repairs, and conduct limited Sustainment-level
maintenance IAW AR 95-23, TC 3-04.61 and associated system specific TMs. FSRs shall be
accountable for supply/support functions at the Unit’s location. The FSR shall be the interface
between the Unit and contractor’s ICP and/or depot facility ensuring that parts flow to the Unit
and that retrograde flows back to the appropriate contractor depot repair location. The FSRs
shall utilize the contractor’s internal supply management database for all NDI Group 2/3 UAS
component and logistics transactions. The FSR shall serve as the point of contact for field
failures and recipient of replacement parts and requisitions submitted by the supported Unit.
FSRs shall be required to work in field conditions comparable to those of the supported Army
Units during NET, Unit training, field exercises and rotations to Army Combat Training Centers.
The Government will provide FSRs access to government facilities and operational areas needed
to perform assigned duties. The Government will provide FSRs with an on-site office space,
furniture, and required storage to support supply processes. The contractor shall be responsible
for providing cellular phones, computers, and internet access in support of FSR operations. The
Contractor shall also provide vehicles to perform assigned FSR duties.
3.5.5.1 System Daily Status Report
The contractor shall maintain and provide a Government-approved contractor format Daily
Status Reports (DSR) IAW DI-MISC-80508B (CDRL A0015) reflecting the summary of daily
flight and maintenance information for NDI Group 2/3 systems and equipment that are delivered
(i.e. DD 250) to the Government.
Reports shall be submitted daily to address readiness, maintenance, and supply status of each
component item of the NDI Group 2/3 UAS.
Data from each flight shall include: date; aircraft serial number; flight hours scheduled; flight
hours flown; operational sorties scheduled; operational sorties flown; reasons for mission aborts;
operational hours lost with reasons; and comments. Maintenance data shall include all parts,
including LRUs and components, replacement. The DSR shall include the status of critical
system LRUs/components which could affect overall system availability.
Every daily report shall include: aircraft status, and amount of time in hours in each status, of
Fully Mission Capable (FMC), Partially Mission Capable (PMC), Not Mission Capable (NMC)
of each sub-system Unmanned Aircraft (UA), Ground Control Station (GCS), Ground Data
Terminal (GDT) and shall address the PMC and NMC conditions as supply or Maintenance. If a
supply discrepancy, ensure the part(s) required are listed to return to FMC with shipping dates.
Once the shipping information on a requisition is determined (i.e., Transportation Control
Number (TCN)), it shall be included. If a maintenance discrepancy is identified, the Estimated
Completion Date (ECD) shall be provided. If delays are experienced for returning a sub-system
to FMC, a short explanation shall be provided in the report.
3.5.5.2 Logbooks and TAMMS-A
The contractor shall maintain equipment logbooks in the Unmanned Aircraft Systems – Initiative
or Aircraft Notebook automated systems IAW DA PAM 738-751.
3.5.5.3 Weight and Balance Forms/Records
The contractor shall perform Weight and balance as required IAW the Automated Weight and
Balance System and TM 55-1500-342-23, Joint Service Technical Manual Organizational,
Intermediate And Depot Maintenance Aircraft Weight And Balance.
3.5.6 Technical Manuals
The contractor shall provide all system TMs and Associated Supplemental Data IAW DI-
TMSS80527C (CDRL A0016).
3.5.6.1 Technical Manual Printing
Contractor shall provide printed copies of system TMs to support each NET event. Printed
quantities shall include: five (5) Operator Manuals; five (5) Preventive Maintenance Daily
Manuals; twenty-five (25) Check Lists; and four (4) Maintenance Manuals.
3.5.7 New Equipment Training
The contractor shall conduct NET to Army operator and maintenance personnel at a CONUS
Government location. The contractor shall provide a team of trained and qualified instructors,
IAW AR 95-1, AR 95-20 and Government Flight Representative approved procedures, to
conduct on-site training and support the initial transfer of knowledge from the contractor to the
Soldier. The contractor shall support up to four (4) NET events IAW the Government provided
HQDA fielding schedule. NETs will occur sequentially and class size shall not exceed 27
students. The contractor shall provide the training support equipment at each training site to include
but not limited to: colored printing capability, sufficient supplies and student guides per the TSP for
up to 27 Soldiers per class, computer(s) and projector(s) to support two simultaneous class rooms
(operator and maintainer) for each NET class. The contractor shall be available to conduct training
during days, nights, weekends, and Federal Holidays as needed to meet the Unit’s training and
operational schedules.
3.5.7.1 Training Support Package (TSP)
The contractor shall develop and provide a system TSP complete with Program of Instruction,
Lesson Plans, Instructor Guides, Student Handouts, test and answer sheets, to include
audio/visual aids to support NET.
3.5.7.2 NET Completion Report
The contractor shall provide a training completion memorandum at the conclusion of each NET
event. The NET Memo of Record shall serve as formal documentation of the completion and
acceptance of contractor training services. This memo shall be delivered to the Government
NLT 14 days after NET completion, IAW DI-MISC-80508 (CDRL A017). This memo shall
include the following items;

• Number of Soldiers trained by MOS


• Number of Soldiers qualified by MOS
• Number of flights conducted
• Number of hours flown
• Number of simulator hours performed (if applicable)
• List of instructors by position that conducted the NET
4.0 Information Assurance
The contractor shall support the preparation of the Risk Management Framework (RMF)
accreditation package and participate in the RMF accreditation event performed by a
Government approved Security Control Assessment (or equivalent) team. For this event, all
system hardware and software components will be required to be present and in an operationally
representative state. In preparation for the event, the contractor shall provide the following
documentation IAW DI-MISC-80508 (CDRL A017) to the Government NLT 45 days before the
event:
• Hardware/Software/Firmware List
• Network Diagram
• Data Flow Diagram
• Ports, Protocols and Services List
• User Access Control Description
• Configuration Management Plan
• Defense in Depth Security Description (to include detailed information pertaining to the
applicable security configurations such as Solidcore configuration, local/network
firewall(s) configuration, antivirus software configurations, auditing policies, password
requirements/change policies, access rules, physical protection, etc.)
• A Common Control Identifiers spreadsheet (Rapid Acquisition Controls template to be
provided), completed to the best of the contractors ability.
The contractor shall also provide results of an internal (self-assessment of the applicable system
hardware and software components) vulnerability scan. The contractor shall use the most current
Nessus plugins, SCC tool and applicable SCAP benchmarks (found here
https://iase.disa.mil/stigs/scap/Pages/index.aspx) and submit the raw scan data to the
Government IAW DI-MISC-80508 (CDRL A####).
5.0 Hazardous Material Management
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 411. The
contractor shall prepare a HMMP IAW DI-MISC-81398 (CDRL A018). The contractor shall
request Government approval to use any of the 17 target chemicals/substances identified in the
Environmental Protection Agency 33/50 Program (available at
https://archive.epa.gov/oppt/3350/web/html/). The contractor shall not use any Class I Ozone
Depleting Chemical/Ozone Depleting Substance (ODC/ODS) (available at
https://www.epa.gov/ozone-layer-protection/ozone-depleting-substances) in the manufacture or
support of items required by this PWS unless a waiver is obtained from the Government. The
Contractor shall provide, electronically and through the IPT process, immediate notification of
any proposed hazardous material mitigation/elimination efforts that may adversely impact
schedules and/or cost, or performance. The contractor shall prepare an HMMP Report IAW
DIMISC-81397C (CDRL A019) to report perchlorates, Class II ODC/ODS materials (available
at https://www.epa.gov/ozone-layer-protection/ozone-depleting-substances) and/or any
substances listed in Emergency Planning and Community Right-to-Know Act (EPCRA) Section
313 "toxic chemicals" and EPCRA Section 302, "extremely hazardous substances" (available at
https://www.epa.gov/epcra/consolidated-list-lists-under-epcracerclacaa-ss112r-march-
2015version). The HMMP Report shall also identify via technical drawing/publication the
specific location of each hazardous material contained in the final end item(s). Any hazardous
materials used in the manufacturing process shall be identified as such in the HMMP Report.
6.0 Security
6.1 Anti-Terrorism (AT) Level I Training
All contractor employees, to include subcontractor employees, requiring access Army
installations, facilities and controlled access areas shall complete AT Level I awareness training
within 60 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
Contracting Officer Representative (COR) or to the contracting officer, if a COR is not assigned,
within 30 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.
6.2 Access and General Protection/Security Policy and Procedures
Contractor employees 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,
Head Quarters Department of the Army, and/or local policy. In addition to the changes
otherwise authorized by the changes clause of this contract, should the Force Protection
Condition at any individual facility or installation change, the Government may require changes
in contractor security matters or processes.
6.3 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 IAW
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
DoDapproved 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 Federal Bureau of Investigation fingerprint check and a
successfully scheduled NACI at the Office of Personnel Management.
6.4 iWATCH Training
The contractor and all associated sub‐contractors shall brief all employees on the local iWATCH
program (training standards provided by the requiring activity ATO). This local developed
training will be used to inform employees of the types of behavior to watch for and instruct
employees to report suspicious activity to the COR. This training shall be completed within 60
calendar days of contract award and within 30 calendar days of new employees commencing
performance with the results reported to the COR NLT 90 calendar days after contract award.

7.0 List of Abbreviations and Acronyms


AED Aviation Engineering Directorate
AR Army Regulation
AT Anti-Terrorism
CAC Common Access Card
CDRL Contract Data Requirements List
CFR Code of Federal Regulations
CLS Contractor Logistics Support

You might also like