Atch_II_MEUAS_IV_CDP_18Jul19.pdf

H9240819R0001 Attachment III 18Jul19

Mid-Endurance Unmanned Aircraft System (MEUAS) IV

Capabilities Demonstration Plan

BACKGROUND

1.1 The primary purpose of the Mid-Endurance Unmanned Aircraft Systems (MEUAS) IV capabilities demonstration is to ensure offerors proposed system capabilities shall meet designated requirements identified below in the demonstration flight profiles. Data collected during the demonstrations will result in an acceptable or unacceptable evaluation of the proposed UAS. The demonstrations will be conducted within U.S. Army White Sands Missile Range (WSMR) approximately 80 miles south of Albuquerque, New Mexico. For offeror familiarization the WSMR Range Customer Handbook is provided at the following (https://www.wsmr.army.mil/pdf/RCH2012FinalOPSECApproved26September2012.pdf). Please disregard any requests for information discussed in the handbook. Additional range access information and detailed demonstration schedule and plan will be provided to the offeror with the invitation to the demonstration.

1.2 Offerors shall arrive at the demonstration site with their system, equipment, and personnel prepared to complete their system capabilities demonstration at the scheduled date and time in the invitation.

1.3 The following WSMR data call attachments shall be submitted with the Offeror’s proposal (Volume 1) consisting of the:

• WSMR UAV Data Request Letter (DRL)

• WSMR Spectrum Essential Information Request

• WSMR Range Frequency Assignment (RFA) Essential Information

• DD Form 1494

The offeror shall have all fields completed in attachments X03X-X05X that are associated with the Offeror’s proposed system. The offeror shall have all necessary form fields found within the provided DD Form 1494 referencing the offeror and information of all transmitters, receivers, and antennas associated with the Offeror’s proposed system. If the Offeror has already attained a DD1494 or J/F-12 Associated with their proposed system these may be included with the proposal submission. This data call will help expedite the system safety review and range frequency deconfliction.

All offerors are advised to contact WSMR as soon as an invitation by the government has been received to coordinate system safety review and de-conflict UAS operating frequencies. Any frequency issues could take multiple months to resolve. The WSMR MEUAS IV Range POC will be Mr. Alfredo Corral. Mr. Corral can be contacted at alfredo.i.corral.civ@mail.mil.

1.4 Failure to appear at the scheduled time may result in in the offeror’s demonstration evaluated as “Unacceptable.” Excusable delays shall be pre-coordinated with the Contracting Officer and may be defined as where the failure arises from causes beyond the control and without the fault or negligence of the offeror such as (1) acts of God or of the public enemy, (2) acts of the Government in either its sovereign or contractual capacity, (3) fires, (4) floods, (5) epidemics, (6) quarantine restrictions, (7) strikes, (8) freight embargoes, and (9) unusually severe weather. A back-up day shall be scheduled in the event of an excusable delay. All excusable delays will be approved by the Contracting Officer.

2.0 DEMONSTRATION CONCEPT

The system capabilities demonstrations will consist of a welcome briefing, range and safety briefing, UAS overview presentation, USG demonstration briefing, question and answer pertaining to execution of event, system setup and check-outs, mission planning period, and demonstration flights with predefined technical flight profiles.

3.0 DEMONSTRATION SCHEDULE OF EVENTS

Day 1 Day 3 Main Gate & Visitors Badging Demo Site Morning Brief Welcome Range and Safety Briefing Range/Safety/USG Briefing Pre-flight Briefing System Set-up/Check-Out Flight Demonstration UAS Overview Presentation Post Flight Debrief

Day 2 Day 4 Demo Site Morning Brief Weather Day or Range and Safety Briefing Further flights as needed & Pre-flight Briefing Offeror pack up Flight Demonstration Post Flight Debrief Day 5 (Backup Day) Further flights as needed & Offeror pack up

Table 1. Schedule of Events

4.0 DESCRIPTION OF DEMONSTRATION EVENTS

4.1 Welcome. To be conducted by the Government team. Welcome includes an introduction, overview of facilities, discussion of the sequence of events, general expectations, and rules of engagement for participants.

4.2 Range and Safety Briefing. To be conducted by the Government and range personnel team.

Briefings will cover range information, range regulations and procedures, and range safety followed by an open question and answer period.

4.3 4.3 USG Demonstration Briefing. Purpose is to inform industry on how the demonstration shall be executed. Briefing shall include detailed instructions on each phase of the demonstration.

4.4 System Set-up/Check-out. Time allocated for offeror to set up and check out its equipment and conduct any necessary checkout flights to prepare for the flight demonstrations.

4.5 UAS Overview Presentation. Presentation shall be conducted by the offeror. Presentation shall cover the following:

4.5.1 UAS capabilities

4.5.2 UAS subsystems (air vehicle, payloads, and ground control system)

4.5.3 System employment concept

4.5.4 Field maintenance approach

4.5.5 Support equipment requirements

4.5.6 System documentation (field manuals/instructions/user checklists)

4.6 Mission Planning

4.6.1 The offeror shall execute the mission planning described in special instruction as stated in paragraph 6. All demonstration activities are expected to be accomplished in the time allotted to the offeror.

4.6.2 The Government shall provide the offeror with demonstration flight route coordinates and range boundaries in Military Grid Reference System (MGRS) and latitude/longitude (DD.MM.SS.S, DD.MM.MMM, or DD.DDDDD) formats.

4.6.3 The offeror shall specify the Loss of Link (LOL) procedures inherent in the system and shall demonstrate the LOL procedures during the flight demonstration activity. The system shall possess an autonomous recovery feature to ensure the Air Vehicle (AV) predictably executes LOL recovery route to include orbit delay for a predetermined length of time in the event of a primary data link loss. If the data link cannot be reacquired, the AV shall execute the preprogrammed instructions resulting in a recovery at the pre-programmed end point.

4.7 Flight Demonstrations

4.7.1 Demonstration Guidelines. The offeror shall execute the flight profiles described in paragraph 4.7.4. All demonstration activities are expected to be accomplished in the time allotted. A backup day is scheduled in case of inclement weather or other unforeseen event(s) beyond the control of the offeror to complete their system demonstration flights.

4.7.2 Safety. Safety shall be evaluated throughout the demonstrations. This includes safety hazards in the operation and maintenance of the system as well as assembly/disassembly, hazardous materials safety, and laser safety, if required.

4.7.3 Flight Demonstration: The offeror shall be evaluated on the tasks listed in Table 1. Tasks that shall require specific guidance are addressed in paragraph 5.0.

Demonstrate/Verify PWS Ref. Demonstrate/Verify

PWS

Ref.

Personnel Proficiency 3.1.6 Night Time FMV 3.4.2 Inflight Ground Control Station (GCS) Hand-off 3.2.2 Remote Video Terminal 3.4.4

Dynamic Mission Re-tasking 3.2.3 Processing, Exploitation, and Dissemination (PED) Distribution 3.4.5

Loss of Link Programming 3.2.4 Video Clip Export 3.4.6 Execute Loss of Link Procedure 3.2.4 Video Metadata 3.4.7 Runway Independence 3.3.1 Video/Data recording and storage 3.4.9

Endurance 3.3.3 Command and Control (C2)/Datalink Encryption 3.5.1

Transit Speed 3.3.4 C2/Datalink Range 3.5.2 Operational Ceiling 3.3.6 Open Payload Architecture 3.6.1 Acoustic Signature 3.3.9 Payload Weight >5 lbs. 3.6.4 Visual Signature 3.3.10 Payload Power 3.6.5 Anti-Collision Lighting 3.3.11 Payload Data Rate 3.6.6 Transponder 3.3.14 Personnel 3.8.1 Day Time Full Motion Video (FMV) 3.4.1

Table 2. Table of Demonstrations

4.7.4 Specific Instructions

4.7.4.1 The following instructions are provided to ensure that the offeror has specific equipment / components that shall be required to complete the evaluation. The offeror must conduct demonstrations with configuration stated in MEUAS IV proposal submitted to the government.

4.7.4.2 Evaluation of PWS 3.2.4: The offeror shall demonstrate its mission planning capabilities and loss of link (LOL) programming while preparing the flight demonstration scenarios. The offeror shall demonstrate the procedures and features used to plan the flight parameters for the demonstrations. The offeror shall also demonstrate its ability to input required mission planning parameters (i.e., launch point, waypoints, orbit points, recovery points, airspeed and flight altitudes) and the ability to change the map coordinate format of the waypoints. The offeror shall demonstrate the ability to mission plan for the demonstration flights and store the mission plans on the GCS until execution.

4.7.4.3 Evaluation of PWS 3.2.4: The offeror shall specify the LOL procedures inherent in the system and shall demonstrate the LOL procedures during the flight demonstration activity. The system shall possess an autonomous recovery feature to ensure the Air Vehicle (AV) predictably executes LOL recovery route to include orbit delay for a predetermined length of time in the event of a primary data link loss. If the data link cannot be reacquired, the AV shall execute the preprogrammed instructions resulting in a recovery at the pre-programmed end point.

4.7.4.4 Evaluation of PWS 3.3.3: Endurance shall be demonstrated in a partial flight and the capability of the aircraft shall be extrapolated based on the fuel consumed on the partial flight.

The aircraft shall be weighed dry, and then “full fuel” with baseline configuration plus 5lbs secondary mass (provided by vendor). To ensure the excessive fuel consumption on climb out does not overly penalize the final value, the climb out shall be less than 10% of the total flight time. The aircraft shall be weighed before and after the flight to measure fuel burned. A simple extrapolation would be unacceptably skewed by the heavy weight of the aircraft. Therefore, the fuel burned shall then be used with the Breguet equation to solve for estimated maximum endurance with 30 minute reserve.

𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸 = 𝐶𝐶 × ln�

𝑊𝑊𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇

𝑊𝑊𝐿𝐿𝑇𝑇𝐿𝐿𝐿𝐿𝐿𝐿𝐿𝐿𝐿𝐿

(Breguet Equation)

C shall be a constant and shall be calculated from the partial flight.

For example:

If the aircraft takes off at 400 lbs. and lands 2 hours later at 350 lbs., but with 50 lbs. of fuel still in the tank.

𝐶𝐶 =

𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸

ln �

𝑊𝑊𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇

𝑊𝑊𝐿𝐿𝑇𝑇𝐿𝐿𝐿𝐿𝐿𝐿𝐿𝐿𝐿𝐿

2 ℎ𝐸𝐸𝑟𝑟.

ln �400 𝑙𝑙𝑙𝑙𝑟𝑟.

300 𝑙𝑙𝑙𝑙𝑟𝑟.�

= 15

If you were to use up those remaining 50 lbs., then it would land at 300 lbs. So you calculate:

𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸 = 𝐶𝐶 �ln�

𝑊𝑊𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇

𝑊𝑊𝐿𝐿𝑇𝑇𝐿𝐿𝐿𝐿𝐿𝐿𝐿𝐿𝐿𝐿

�� = 15 �ln �

400 𝑙𝑙𝑙𝑙𝑟𝑟.

300 𝑙𝑙𝑙𝑙𝑟𝑟.

�� = 4.3 ℎ𝐸𝐸𝑟𝑟.

Therefore the capability would be 3.8 hours max with 30 minutes of reserve.

4.7.4.5 Evaluation of PWS 3.3.9: Acoustic signatures shall be measured and collected in a static demonstration as well as during flight. If allowed by the range, one of the acoustic collection flight profiles shall be flown between 200 ft. – 500 ft. above the microphone array. The aircraft must be operating at a flight condition (airspeed, engine power, etc.) that is consistent with an ISR loiter condition

The following describes how the government shall collect flight acoustic data.

1. Measured time history data from fly over event shall be Fast Fourier Transformed (FFT) into 1/3rd Octave data

2. The spectra from (1) shall be adjusted using the 1/R2 Law until the levels are commensurate with the Threshold curve in Figure 1.

3. The spectra shall then be adjusted for atmospheric absorption based on a pre-determined relative humidity, temperature, and pressure using the standard ANSI S1.26-1995, “Method for Calculation of the Absorption of Sound by the Atmosphere’’ (ANSI Standards, New York, NY)

4. A final comparison with the Threshold curve in 3.3.9 (Found in Figure 2) and final determination in distance R shall be made. This final slant range, R, shall be determined and this shall be the slant range used for demonstration of paragraph 3.4.1 and 3.4.2 of the PWS.

5. Steps 2 thru 4 shall be repeated and shall target Objective curve in paragraph 3.3.9 of the PWS (Found in Figure 2) and produce a slant range for an extremely quiet background ambient noise environment.

The offeror shall provide a stand, method of securing, and lifting their aircraft in a static position at least five feet off the ground and does not obstruct any noise sources (e.g., the propulsion system), with the aircraft propulsion system operating consistent with an ISR loiter condition.

Acoustic data shall be collected at the four cardinal positions.

Figure 1: Acoustic array for 200ft - 500ft flight profile.

Figure 2: Target Sound Pressure Level spectra to meet acoustic requirements.

4.7.4.6 Evaluation of PWS 3.4.1 and PWS 3.4.2: The FMV quality of the system shall be measured in both a quantitative and qualitative manner. Only the quantitative measurement shall be graded. The capability shall be demonstrated in both daylight (EO) and a night capable (IR) configuration. The performance shall be demonstrated at two different standoff distances of threshold and objective determined in the acoustic measurements. Those distances are as follows:

• Informational Only: The distance where the UAS is acoustically undetectable in an extremely quiet background at target (worst case quiet desert nighttime)

• Graded: The distance where the UAS is acoustically undetectable in an moderately quiet background at target (quiet suburban nighttime)

At each distance, the UAS shall observe a target set provided by the government which includes standard “3 Bar” charts as well as other objects to include small arms, tools, mannequins and vehicles. The measurement of video quality shall be GRD (Ground Resolution Distance). This shall be measured by observing the 3bar chart. The resolution achieved is the smallest set that both vertical and horizontal bars can be separated (each of the 3 lines can be discriminated).

4.7.4.7 Evaluation of PWS 3.4.5: The system shall be expected to output the FMV via a line level feed (either High Definition (HD) video via High-Definition Multimedia Interface (HDMI) or High Definition - Serial Digital Interface (HD-SDI), or Standard Definition (SD) video via National Television System Committee (NTSC) standard. This feed shall be plugged into a government provided video monitor, and the monitor’s ability to decode/display the PED video output shall be observed through the flight. The system shall also be expected to output Key- Length-Value (KLV) metadata via an RS-232 serial feed. This data feed shall be plugged into a government provided laptop, and software tools shall be used to decode and display the KLV metadata. The display of this software tool shall be observed through the flight.

4.7.4.8 Evaluation of PWS 3.6.1: The system must have the ability to provide a simple bridged Ethernet datalink for payloads via a ground demonstration in the following manner. The offeror shall provide an Ethernet cable that plugs into the aircraft, and provides a standard RJ45 connector. A similar cable, with a standard RJ45 connector, shall be provided by the offeror for the ground station. The offeror shall also provide two appropriate pools of Internet Protocol (IP) addresses (one for the aircraft, one for the ground station). Two government provided laptops shall then be configured to those addresses; one shall then be plugged into the aircraft, the other shall be plugged into the ground station. Several Internet Control Message Protocol (ICMP) ping packets shall be sent from the “aircraft” laptop to the “ground station” laptop’s IP address, and results shall be observed.

4.8 Demonstration Objective: The objectives of the demonstration is to assess all items listed in Table 1. The demonstration is intended to allow the offeror to operate their system and perform specific tasks specified in the PWS that can be verified / and or evaluated through a live demonstration. Specific instructions pertaining to detailed schedule of events shall be provided to invitees upon invitation to the demonstration.

4.9 Demonstration Staff: The government demonstration staff shall consist of but are not limited to data collectors, observers, evaluators, and range personnel. The government staff shall be on site to monitor all offeror activities performed, including but not limited to, in the GCS, on the ground, in the hangar, and all platform demonstration and flights. The government staff shall operate all government demonstration instrumentation and requires the offeror to closely coordinate with the government staff so that the demonstration can stay on schedule.

5.0 Demonstration Conclusion

5.1 The offeror shall pack up and remove all its offeror owned demonstration material by end of day following their final flight.