Attachment_0006-Test_Plan-20171207.PDF

Detailed Test Plan for the

Electro-Optic/Infrared/Laser Designator Payload for the RQ–7B version 2 Tactical Unmanned Aerial System

ATEC Project No.: H0174

YPG No.: 18–TP–0084–L5

Brianna Carlson

7 December 2017

Plan Produced By U.S. Army Yuma Proving Ground

Plan Produced For Product Manager Electro-Optical/Infrared

Approved for public release: distribution unlimited.

The use of a trade name or the name of the manufacturer or a contractor in this report does not constitute an official endorsement or approval of the use of such commercial hardware or software or of service.

The report may not be cited for purposes of advertisement.

i

APPROVAL

The following document was submitted and approved for distribution.

SUBMITTED BY: APPROVED BY:

BRIANNA CARLSON For ROSS GWYNN Test Officer, Chief, Sensor Test Branch Aviation Systems and Electronic Test Division

For ii

TABLE OF CONTENTS

SECTION 1. INTRODUCTION

1.1 SYSTEM DESCRIPTION

1.2 SUMMARY

1.3 UNIQUE DEMONSTRATION PERSONNEL REQUIREMENTS

SECTION 2. SUBSECTIONS

2.1 AIRWORTHINESS SPECIFICATIONS

2.2 SENSOR RESOLUTION

2.3 LASER DESIGNATOR

2.4 LASER RANGEFINDER

2.5 LASER TARGET MARKER

2.6 TARGET LOCATION ERROR

2.7 SYSTEM FUNCTIONALITY

SECTION 3. APPENDICES ..................................................................................................... A–1

A. DEMONSTRATION CRITERIA ................................................................................. A–1

B. DEMONSTRATION SCHEDULE ............................................................................... B–1

C. INFORMAL COORDINATION ................................................................................... C–1

D. CRITERIA FOR METEOROLOGICAL CONDITIONS ............................................. D–1

E. LASER EXCLUSION ZONES ..................................................................................... E–1

F. LEVER ARM DATA .................................................................................................... F–1

G. HEIM RECORDER FORMATS ................................................................................... G–1

H. EQUIPMENT RACK DRAWINGS ............................................................................. H–1

I. ESSENTIAL FUNCTION FAILURE FLOW CHART ................................................. I–1

J. INTEGRATION CHECKLIST ...................................................................................... J–1

K. PRE-DEMONSTRATION COORDINATION INFORMATION AND

DOCUMENTATION .................................................................................................... K–1

K1 Pre-Demonstration Checklist ................................................................................ K–1

K2 Pre-Demonstration Coordination Information ...................................................... K–2

K3 Extended Range Information Sheet ...................................................................... K–5

K4 Air Transportation Agreement .............................................................................. K–6

K5 Flight Authorization Form .................................................................................... K–7

K6 Required Documentation for Contractor-Owned PCs .......................................... K–8 iii

K7 Required Documentation for Army-Owned PCs ................................................ K–11

L. 6DVTS MESSAGE FORMATS ................................................................................... L–1

M. REFERENCE ............................................................................................................... M–1

N. ABBREVIATIONS ....................................................................................................... N–1

O. DISTRIBUTION LIST .................................................................................................. O–1

SECTION 1. INTRODUCTION

1.1 SYSTEM DESCRIPTION

This demonstration is being conducted as a portion of the vendor source selection for the Electro-Optic (EO)/Infrared (IR)/Laser Designator (LD) payload subsystem for the RQ–7Bv2 (Shadow) Tactical Unmanned Aerial System (TUAS). Multiple vendors will demonstrate their system capabilities and will be assessed by the Source Selection Evaluation Board (SSEB) in accordance with the solicitation provisions against the requirements of Sub factor 1.1 – Payload Performance. All vendor payload subsystems will be evaluated against the specifications described in the Performance Based Specification (PBS) for the Payload Subsystem for the RQ– 7Bv2 TUAS Version 1.0, authored by Program Executive Office (PEO) Intelligence, Electronic Warfare, and Sensors (IEW&S), Program Manager (PM) Terrestrial Sensors, and Product Manager (PdM) EO/IR (appendix [app] L, reference [ref] 1). Specific requirements to be assessed are shown in table 1.2–1.

During this demonstration, each payload will be mounted on a United States (U.S.) Army Cessna 208B Caravan fixed-wing aircraft for flight demonstration. The Caravan will act as a surrogate platform, also referred to as test aircraft, for the Shadow TUAS, shown in figure 1.1–1.

Figure 1.1–1. Yuma Test Center Cessna 208B Caravan Sensor Test Bed

The payloads will be mounted on an arm that protrudes from the side of the test aircraft via the rear door. The arm will have a standardized mount that will match the Shadow TUAS Interface Control Document to allow for installation without modification(s) between payloads.

1.2 SUMMARY

a. Demonstration Authority. Yuma Test Center (YTC) is working with PEO IEW&S, PM Terrestrial Sensors, and PdM EO/IR under U.S. Army Test and Evaluation Command (ATEC) project number (No.) 2018–DT–YPG–IEWSS–H0174.

b. Demonstration Objectives. The objectives are to demonstrate the capabilities of different payloads provided by various vendors, analyze the demonstration results, and provide data to the SSEB for assessment. Table 1.2–1 describes the individual objectives of each subsection of the demonstration.

Table 1.2–1. Shadow TUAS Payload Demonstration Objectives

Demonstration Subsection Objectives

2.1 Airworthiness

Specifications To verify the vendor payload meets all YPG AWR requirements for installation and flight on the test aircraft.

2.2 Sensor Resolution

a. To determine the resolution performance of each vendor’s EO sensor against EO FEBTs.

b. To verify EO optical sensor functionality.

c. To determine the resolution performance of each vendor’s IR sensor against IR FEBTs.

d. To verify IR optical sensor functionality.

2.3 Laser Designator

a. To verify the LD functionality.

b. To verify vendor payload supports PRF mode and is functional.

c. To determine LD range of each vendor payload.

2.4 Laser Rangefinder

a. To determine the LRF range error.

b. To determine the maximum effective LRF range.

c. To verify the LRF functionality.

2.5 Laser Target Marker To verify the functionality of the LTM.

2.6 Target Location Error To determine the two- and three-dimensional target location error.

2.7 System Functionality

a. To document vendor payload subsystem functionality requirements.

b. To document laser safety interlock functionality between vendor payload and test aircraft.

LEGEND:

AWR – Airworthiness Release EO – Electro-Optical FEBT – Field-Equivalent Bar Target IR – Infrared LD – Laser Designator

LRF – Laser Rangefinder LTM – Laser Target Marker PRF – Pulse Repetition Frequency TUAS – Tactical Unmanned Aerial System YPG – U.S. Army Yuma Proving Ground

c. Demonstration Concept. The capabilities of the various payload subsystems will be demonstrated. Prior to the flight demonstration, the payload will be measured to assess compliance with the general system specifications. The payload optical sensors will be assessed to demonstrate the range at which the EO and IR cameras can recognize a 3.5-meter (m) by 3.5-m target. The LD will be assessed to demonstrate the designation range, accuracy, stability, and functionality. The Laser Rangefinder (LRF) will be assessed to demonstrate the accuracy, functionality, and Target Location Error (TLE). The Laser Target Marker (LTM) will be assessed to demonstrate laser functionality. Concurrently with the component demonstration, general system functionality requirements will be verified.

Each vendor will have 3 days total for the demonstration. The first day will be for integration, set up, and checkout. The second day will be for flight demonstration to include two flights: one day and one night. Each flight will be limited to a maximum of 3 hours. Table 1.2–2 outlines the go/no-go criteria for meteorological (MET) conditions to ensure weather does not impact test results. The last day will be for de-integration and teardown. A standard work day is limited to 10 hours on site, with a minimum of 10 hours between test days.

PdM EO/IR determined the periods during both daytime and nighttime that would be most conducive for the test as detailed in appendix D. Table 1.2–2 outlines the go/no-go criteria for MET conditions to ensure weather does not impact test results. Due to the fact that the IR target boards available for test have a characteristic dimension of 2.03 m as opposed to the Shadow requirement for recognition of a 3.5-m by 3.5-m target, the threshold range at which IR resolution performance will be assessed will be 4 kilometers (km) versus the 7 km required in the Shadow PBS.

Table 1.2–2. Shadow Go/No-Go Criteria for Meteorological Conditions

Sensor

Target Test Period

(normalized to sunrise @

0600L)

Min. Target Recognition

Range (km)

Max.

Temp.

(°F)

Min.

Temp.

(°F)

Max.

Relative Humidity

Min.

Visibility

(km)

Max. Optical Atmospheric Turbulence

(Cn 2)

EO

(daytime)

0600–0900 13 92 32 96 24 2.5x10−13

IR

(nighttime)

0300–0600 4 92 32 96 10 2.5x10−13

LEGEND:

°F – degrees Fahrenheit % – percent Cn

2 – Scintillation EO – Electro-Optic km – kilometer L – local time Max. – Maximum Min. – Minimum Temp. – Temperature

Appendix K2 outlines and defines the requirements for non-YTC personnel including visit request processing (U.S. citizens and foreigners); directions to U.S. Army Yuma Proving Ground (YPG) and the Visitor Control Center; shipping instructions; classified material handling; internet access; and flight documentation. Failure to complete the required documents provided in appendices K3–K7 may result in delays and denial of access to certain sites, briefs, and/or activities.

1.3 UNIQUE DEMONSTRATION PERSONNEL REQUIREMENTS

Qualified personnel from each vendor will operate the sensor payload. Government personnel are not responsible for and will not operate the payload during this demonstration. It is solely the vendor’s responsibility to supply personnel qualified to operate the payload during the demonstration. Government personnel will be on site to provide integration checklists, Government Flight Representatives, and security, but are not responsible for integration beyond what is necessary for safe operation of the aircraft. The Government is not liable for any damages to the payload during the duration of this demonstration.

SECTION 2. SUBSECTIONS

2.1 AIRWORTHINESS SPECIFICATIONS

2.1.1 Objective

To verify the vendor payload meets all YPG Airworthiness Release (AWR) requirements for installation and flight on the test aircraft.

2.1.2 Criteria and Analysis

YTC personnel will analyze the vendor payload subsystem data gathered during this subsection of the demonstration as presented in table 2.1–1. Criteria for this subsection were derived by YPG or from the PBS for the Payload Subsystem for the RQ–7Bv2 TUAS Version 1.0.

Table 2.1–1. Airworthiness Specifications Criteria and Analysis App A, Item No. Criteria Analysis

The total weight of the payload shall be no greater than 50 lb. (R.B.197)

The total weight of the vender payload will be measured and included in the final report.

When in the installation and removal position (i.e., payload stowed), the payload diameter shall be no greater than 10.4 in.

(R.B.195)

The payload diameter will be measured and included in the final report.

The total height of the payload shall be no greater than 16.9 in. (R.B.196)

The total height of the payload will be measured and included in the final report.

The laser system must have been evaluated by PHC or equivalent DoD radiation safety office and received approval to operate on DoD installations. Documentation of safety evaluation and approval to operate must be provided to YTC prior to test.

The laser system’s approval from PHC or equivalent DoD radiation safety office will be verified and included in the final report.

The laser system must meet the laser ANSI Z136.1 Section 4, Control Measures.

The laser ANSI Z136.1 Section 4 Control Measures will be verified prior to the start of testing.

The laser system must have Laser Fire Exclusion Zones per App E.

The laser system Laser Fire Exclusion Zones will be verified prior to test start.

The payload shall operate using no more than 300 W of the Shadow TUAS power specification.

The power requirement for each item within the payload will be verified prior to installation on the test aircraft.

The proposal must include all required documentation listed in section 2.1.3.c as required for AWR approval.

Provided documentation will be included in the AWR package and sent to AFTD for approval.

Table 2.1–1. General System Specifications Criteria and Analysis (Concluded)

LEGEND:

AFTD – Aviation Flight Test Directorate ANSI – American National Standards

Institute App – appendix AWR – Airworthiness Review DoD – Department of Defense

in. – inch lb – pound No. – number PHC – Public Health Center R.B. – Requirements Baseline TUAS – Tactical Unmanned Aerial System W – watts

2.1.3 Demonstration Procedures and Data Required

a. Instrumentation. Measuring devices and a scale will be used for this subsection of the demonstration.

b. Targets. No targets are required for this subsection of the demonstration.

c. Procedures. If the payload fails to meet any of the criteria listed in table 2.1–1, it will be documented in the report and reviewed for impact on flight safety on the test aircraft. If the payload fails to meet requirements for safety of flight or any of the requirements below for airworthiness, it will not be installed or flown for the demonstration. Once the vendor data package is reviewed and approved the payload can be flown on the test aircraft. Each vendor is required to submit the following documentation to be included as part of their AWR package:

(1) Structural analysis on all components that will be installed on the Cessna Caravan 208 test aircraft. The test aircraft has a 9g factor.

(2) Electrical load analysis.

(3) Break down of each item that will be installed and the amps or watts that it will draw.

(4) System wiring drawings.

(5) Integration drawings that include all components that will be installed.

(6) Manufacturer data sheets for all commercial-off-the-shelf (COTS) products.

The general system specifications procedures are as follows:

(1) Upon arrival at YPG, vendor/YTC personnel will use a scale to weigh the vendor payload.

(2) Vendor/YTC personnel will measure the payload diameter, and total height (per app A, table A–1, items 2–5).

(3) Vendor/YTC personnel will then install that vendor payload onto the Shadow Payload Mount.

(4) Steps (1) through (3) for AWR will be repeated for each vendor.

d. Data Required:

(1) Date and Time

(2) Vendor

(3) System name

(4) Subsystem weight (pounds [lb])

(5) Payload diameter (inches [in.])

(6) Total payload height (in.)

(7) Payload-unique settings

2.2 SENSOR RESOLUTION

2.2.1 Objectives

a. To determine the resolution performance of each vendor’s EO sensor against EO Field-Equivalent Bar Targets (FEBTs).

b. To verify EO optical sensor functionality.

c. To determine the resolution performance of each vendor’s IR sensor against IR FEBTs.

d. To verify IR optical sensor functionality.

2.2.2 Criteria and Analysis

YTC personnel will analyze the vendor payload data for the sensor resolution subsection of the demonstration as presented in table 2.2–1. All criteria for this subsection were derived from the PBS for the Payload Subsystem for the RQ–7Bv2 TUAS Version 1.0.

Table 2.2–1. Vendor Assessment Criteria and Analysis for Sensor Resolution

Item No. Criteria Analysis

The EO sensor recognition requirement is per the Johnson Criteria. The assumed operational altitude is 8,000 ft AGL. The EO sensor shall supply a video output of sufficient quality to recognize, with 70% probability of recognition, a 3.5-m by 3.5-m target at a slant range of not less than 13 km (T), 35 km (O) given an N50 of 3 cycles on target, relative humidity of 90%, visibility of 23 km, and a target contrast of 40%.

(R.B.135)

YTC personnel will document and include in the final report the vendor’s 70% probability of recognition range against a 3.5m by 3.5m target utilizing the EO sensor.

The IR sensor recognition requirement is per the Johnson Criteria. The assumed operational altitude is 6,000 ft AGL. The IR sensor shall supply a video output of sufficient quality to recognize, with 70% probability of recognition, a 3.5-m by 3.5-m target at a slant range of not less than 7 km (T), 35 km (O) given an N50 of 3 cycles on target, relative humidity of 90%, visibility of 23 km, and a target foreground-background temperature difference of 4 degrees C.

(R.B.141)

YTC personnel will document and include in the final report the vendor’s 70% probability of recognition range against a 3.5-m by 3.5-m target utilizing the IR sensor by assessing target recognition of a 2.03-m by 2.03-m target against which the threshold recognition range will be 4 km.

Table 2.2–1. Vendor Assessment Criteria and Analysis for Sensor Resolution (Concluded)

LEGEND:

% – percent AGL – Above Ground Level App – appendix EO – Electro-Optical ft – foot m – meter

O – Objective R.B. – Requirements Baseline T – Threshold YTC – Yuma Test Center

A minimum of four isolated observers will observe the sensor resolution video. All observers will be YTC personnel and will be briefed together on the proper scoring procedures.

The identity of the payload/vendor being assessed will be withheld from the observers. The same data set will be scored by all observers. A call is defined as the observers completely resolving the FEBT bars at least 50 percent (%) of the time. Each observer will have identical viewing stations and setup. Runs from all vendors will be combined and randomized prior to providing data to observers to remove biases. While viewing the recorded imagery, each observer will attempt to resolve all the bars on each target. If the imagery is sufficient to make these calls, the observer will record the call. If no determination can be made, the observer will record “No Call.” Observers will be given a proficiency test prior to scoring the video. The proficiency test will consist of a sample of videos that will be scored in succession while varying the order of viewing. Observers that have the lowest variance in results will be used to score the videos.

Resolution ranges will be obtained by differencing the aircraft position from the target position at the time of the observation call. Summary statistics will be compiled to determine any trends.

Once the data have been reviewed and quality assurance checks completed, run-by-run data will be compiled. The run-by-run data will contain all relevant information such as the event time, range-to-target, field-of-view (FOV), sensor selected, observer, and MET conditions.

2.2.3 Demonstration Procedures and Data Required

a. Instrumentation. Data collection during resolution trials will be performed with the use of on-board aircraft instrumentation including: data recorders to collect payload sensor video, selected metadata parameters, Embedded GPS/Inertial Measurement Unit (IMU) (EGI) for vendor payload utilization (YPG will utilize the 6-Dimensional Vehicle Tracking System [6DVTS], for more information contact the Contracting Officer), and a Differential Global Positioning System (DGPS) unit to collect aircraft Time-Space-Position Information (TSPI).

Appendix L shows the 6DVTS message formats. Data recorders will also overlay a timestamp provided by the DGPS onto the vendor’s video for time correlation. The planned data recorder from YPG for the test aircraft is the HEIM recorder. Appendix G shows the video formats that the recorder can support. Range instrumentation will include a MET system for atmospheric documentation; Mission Control for data recording and real-time screening; instrumentation cameras for documenting and recording target conditions; and a range time system for data correlation.

b. Targets. FEBTs will be used to collect resolution data on the EO and IR cameras. A set of FEBTs will be used for IR and EO trials to represent recognition of a 3.5-m by 3.5-m target with appropriate cycle requirements for 70% probability of recognition Johnson Criteria (N70). The cycle requirements for N70 will be calculated given that the default cycles on a target for N50 recognition is three cycles. Each set will contain a vertical bar target and a horizontal bar target. The IR target will maintain a temperature delta of 4.0 degrees Celsius between the heated bars and the background. An example of IR targets is shown in figure 2.1–1 (targets pictured may not be the actual targets used during this subsection). The targets used for EO trials will be painted to provide a 40-percent visual contrast between the bars and the background. An example of the EO targets is shown in figure 2.2–2 (targets pictured may not be the actual targets used during this subsection).

Figure 2.2–1. Example Infrared FEBT

Figure 2.2–2. Example Electro-Optical FEBT

c. Procedures. For each applicable flight, the sensor polarity will be set to the operator-selected optimum polarity for IR trials and the operator-selected best color setting for EO flights.

A dry-run for sensor calibration/optimization will be conducted prior to each set of collection runs (i.e., one dry-run for EO resolution and one dry-run for IR resolution) within a given flight.

Sensor settings will not be adjusted in between runs once data collection has begun. If the test aircraft has to land in the middle of a test, dry runs for optimization will be allowed prior to resuming the test. A run-in method will be used to collect the data for this subsection and the FOV will remain constant for each run-in. Figure 2.2–3 shows the flight profile used for the sensor resolution trials. Trials will be conducted along this flight path but the start and end point locations will vary in range based on the requirements in the demonstration matrix.

Figure 2.2–3. Sensor Resolution Example Flight Profile

The sensor resolution demonstration matrix is shown in table 2.2–2. Each vendor will complete resolution trials utilizing the narrowest FOV. Post-event, observers will assess each trial. A trial will consist of performing target resolution attempts inbound to the bar target.

Trials will be conducted on inbound and outbound runs for efficiency; however, the outbound runs will be shown to the observers in reverse to ensure consistency with runs. Exactly eight data points will be collected for each sensor in each direction, in accordance with table 2.2–2.

Table 2.2–2. Sensor Resolution Demonstration Matrix Demonstration

Point Sensor Day/ Night FOV Filter/Polarity

Altitude (ft AGL)

Data Points

RES–1 EO Day NFOV color 8,000 16

RES–2 IR Night NFOV optimum polaritya

6,000 16

NOTE: Horizontal and vertical bars will be resolved on each trial.

a The operator will select either white hot or black hot for the system’s optimal polarity and it will remain that polarity for the duration of IR resolution testing.

LEGEND:

AGL – Above Ground Level EO – Electro-Optical FOV – Field-of-View ft – foot

NFOV – Narrow Field-of-View RES – Resolution

(1) Each trial will begin with the aircraft at the specified start point and fly to the specified end point. Trials will be completed flying towards and away from the target. The sensor operator will change the FOV for the next run-in when directed by Mission Control.

(2) Operator will locate the target and maintain it in the center of the sensor’s FOV.

(3) Aircraft will begin to fly toward the target while the operator attempts to resolve the target’s bar pattern (break-out the bars). Operator will set the default image processor and filter per table 2.2–2. The operator will use a set of dry runs to optimize the image for the targets. Dry runs will not be analyzed as part of testing.

(4) As the operator/observer views the real-time video, they will make a distinct call of “mark vertical” and another call of “mark horizontal” when the vertical and horizontal bar patterns are resolved, respectively. The video will also be recorded for post-demonstration data scoring.

(5) Steps (1) through (4) will be repeated until the data points required in the demonstration matrix (table 2.2–2) have been completed.

(6) Steps (1) through (5) will be repeated for each vendor.

During demonstration trials, one operator/observer will be making “calls” real time.

These “calls” will only be used to verify ranges and to ensure that all data points needed for post-demonstration scoring are collected. The real-time “calls” will not be grouped with the post-demonstration scoring.

If an essential function failure occurs during testing, the system will be rebooted. If another essential failure occurs, the test aircraft will land and be examined. At this time the vendor will have the option to install a backup payload. Once the test aircraft re-launches to resume test, if an essential function failure occurs, the system will be rebooted. If a second essential function failure occurs on the second flight attempt, testing will end for that vendor and system. The flow chart for decision making regarding essential function failures can be found in appendix I.

d. Data Required. The following data will be recorded:

(1) YPG flight No.

(2) Date and time of flight

(3) Event No.

(4) Event time

(5) Vendor

(6) System name

(7) Mission type

(8) Sensor configuration (software [S/W], hardware [H/W] loads)

(9) Sensor operator and aircrew identification

(10) Sensor select

(11) FOV select

(12) Tracker mode and polarity select

(13) Target location with sufficient precision to evaluate TLE to a precision of 1 m (i.e., 10-digit MGRS or Latitude/Longitude in DEG:MIN:SEC to at least 2 decimal places)

(14) Reported DGPS coordinates

(15) True aircraft Height Above Target (HAT)

(16) True aircraft XYZ coordinates

(17) Aircraft heading

(18) Reported horizontal and vertical resolution times

(19) Observer and TO comments/remarks

(20) Payload-unique settings

(21) Lever arm offsets (shown in app F)

(22) MET conditions:

(a) Wind speed

(b) Wind direction

(c) Air and ground temperature

(d) Absolute humidity

(e) Atmospheric transmittance

1. 8–12 microns ()

2. 3–5

3. 400–700 nanometers (nm)

4. 650–900 nm

(f) Scintillation

(g) Solar illumination

(h) Lunar illumination

(i) Pressure

(j) Turbulence

2.3 LASER DESIGNATOR

2.3.1 Objectives

a. To verify the LD functionality.

b. To verify vendor payload supports Pulse Repetition Frequency (PRF) mode and is functional.

c. To determine LD range and accuracy of each vendor payload.

2.3.2 Criteria and Analysis

YTC personnel will analyze the vendor payload data for the LD subsection of the demonstration as presented in table 2.3–1. All criteria for this subsection were derived from the PBS for the Payload Subsystem for the RQ–7Bv2 TUAS Version 1.0.

Table 2.3–1. Laser Designator Criteria and Analysis

Item No. Criteria Analysis

The LD shall support PRF mode. (R.B.174) YTC personnel will document and include in the final report if the LD supports PRF mode.

The LD beam divergence, boresight error, and stabilization shall be such that not less than 90% of the designator beam energy falls on a 3.5-m by 3.5-m target not less than 90% of the time when the designator is fired from a range of 7 km (T), 10 km (O).

(R.B.166)

YTC personnel will document and include in the final report if the laser designator is able to designate the target at 7 km (T), 8.5 km, 10 km, 11.5 km, and 13 km with 90% of the designator beam energy on a 3.5-m by 3.5 target.

LEGEND:

App – appendix % – percent FOV – field-of-view km – kilometer

O – Objective PRF – Pulse Repetition Frequency R.B. – Requirements Baseline

Prior to demonstrating the vendor LD on the test aircraft, all laser system safety interlocks will be demonstrated and verified to make sure the system is safe for use by the YTC Aviation Safety Officer.

LD accuracy data will be grouped to assess designation performance as a function of sensor FOV and sensor selected (EO/IR).

The laser spot position of every laser pulse on the vertical target board will be processed through YPG’s Video-Based Laser Scoring System (VBLSS). The data will be processed to obtain the laser spot size, X, Y coordinates of the laser spot centroid relative to the aim point

(center of the target) as a function of time. Products of data analysis will be a verification of the criteria in table 2.3–1.

2.3.3 Demonstration Procedures and Data Required

The instrumentation, targets, and demonstration procedures planned for these trials are as follows:

a. Instrumentation. Data collection during laser designation trials will be performed with the use of on-board aircraft instrumentation including data recorders to collect sensor video, selected metadata parameters, and a DGPS unit to collect aircraft TSPI. Range instrumentation will include a MET system for atmospheric documentation; Mission Control for data recording and real-time screening; instrumentation cameras for documenting and recording target conditions; a range time system for data correlation; the VBLSS to record and score the laser spot on target; and a laser test set to verify PRF codes.

The VBLSS will be used to determine the laser hit point and spot size of each laser pulse during a particular designation trial, and these data will be used to verify the criteria in table 2.3–1. A standard frame-rate video camera equipped with a silicon vidicon lens and a near IR camera will be used to visualize and record the laser spot. Prior to the start of a laser mission, the camera-target setup will be calibrated.

b. Targets. During LD trials, the mobile VBLSS target will be utilized. The mobile VBLSS target is mounted on an M988 tank chassis and the outside dimensions of the target are 7 m by 7 m. The target utilizes a heated 2.3-m by 2.3-m center tracking target to provide a high-contrast aiming target for the IR sensor. The target is painted to a 40% contrast between the center tracking target and the background for EO tracking. The large target size provides a larger background-to-target ratio, which offers more optimum tracking conditions. A photograph of the mobile VBLSS target board is provided in figure 2.3–1.

Figure 2.3–1. Mobile VBLSS Target

c. Procedures. Prior to record trials, a dry run will be conducted to ensure all procedures are followed, as required, and that laser energy is being recorded by the VBLSS. The dry run will also be used to verify the system can use PRF codes. A random PRF code will be selected, the operator will set the laser for the PRF, and the laser scoring system will verify the same PRF code is transmitted on the target.

The test aircraft will fly various arcs at 8,000 feet (ft) Above Ground Level (AGL) and 6,000 ft AGL for EO and IR trials, respectively. The operator will switch the active camera (EO or IR) to the narrowest FOV, acquire the target (track), center the reticule (crosshairs) on the center of the target, lase the target for 30 seconds at the direction of the YTC TO, and safe the laser during a single event. If a tracker break lock occurs during designation, the trial will be aborted and reinitiated. The operator will break lock and reacquire the target after each designation. The LD accuracy demonstration matrix is shown in table 2.3–2. The purpose of the LD range and accuracy demonstration is to verify LD functionality, range, and accuracy in the narrowest FOV.

Table 2.3–2. LD Accuracy Demonstration Matrix Demonstration

Point Day/Night Slant Range

(km) LD Target Maneuver Sensor

Focal Length

Data Points

LD–1 Day 7.0 Stationary EO Optimal 10

LD–2 Night 7.0 Stationary IR Optimal 10

LD–3 Day 8.5 Stationary EO Optimal 10

LD–4 Night 8.5 Stationary IR Optimal 10

LD–5 Day 10.0 Stationary EO Optimal 10

LD–6 Night 10.0 Stationary IR Optimal 10

LD–7 Day 11.5 Stationary EO Optimal 10

LD–8 Night 11.5 Stationary IR Optimal 10

LD–9 Day 13.0 Stationary EO Optimal 10

LD–10 Night 13.0 Stationary IR Optimal 10 NOTE: If system does not meet the criteria for this subtest at a demonstration point, the subsequent demonstration points will not be completed.

LEGEND:

EO – Electro-Optical FOV – Field-of-View

LD – Laser Designation

The specific procedures for LD accuracy events are as follows:

(1) Perform all normal sensor preflight checks in accordance with (IAW) the aircraft manual.

(2) Transition the aircraft to the demonstration area.

(3) Set up for aircraft maneuver as required by the demonstration matrix (table 2.3–2).

(4) Acquire the target board and center the reticule (crosshairs).

(5) Verify target crew is ready for data collection.

(6) Begin countdown to engagement.

(7) Designate target for 30 seconds.

(8) Document if 90% of the laser beam falls within a 3.5-m by 3.5-m target.

(9) Break lock on target and reacquire on target for another 30 second designation.

(10) Repeat steps (8) through (9) until aircraft reaches the end of the flight profile.

(11) Repeat (3) through (10) as required by demonstration matrix (table 2.3–2).

(12) Steps (3) through (11) will be repeated for each vendor.

vendor will have the option to install a backup payload. Once the test aircraft re-launches to resume test, if an essential function failure occurs, the system will be rebooted. If a second essential function failure occurs on the second flight attempt, testing will end for that vendor and

Figure 2.3–2 shows the flight profiles for the slant ranges at 7.0, 8.5, 10.0, 11.5 and

13.0 km. Flight profiles will be in an arc to keep the distance from the target consistent throughout the lasing event.

Figure 2.3–2. Example Laser Designator Accuracy Flight Profiles

d. Data Required. Refer to section 2.2.3d for data requirements.

2.4 LASER RANGEFINDER

2.4.1 Objectives

a. To determine the LRF range error.

b. To determine the maximum effective LRF range.

c. To verify the LRF functionality.

2.4.2 Criteria and Analysis

YTC personnel will analyze the vendor payload data for the LRF subsection of the demonstration as presented in table 2.4–1. All criteria for this subsection were derived from the PBS for the Payload Subsystem for the RQ–7Bv2 TUAS Version 1.0.

Table 2.4–1. LRF Range Error Criteria and Analysis

Item No. Criteria Analysis

The LRF shall have a maximum effective range of not less than 7 km (T), 10 km (O).

(R.B.158)

YTC personnel will document and include in the final report the LRF’s maximum effective range.

The magnitude of the LRF range error shall not be greater than 5 m to a 90% confidence. (R.B.160)

YTC personnel will document and include in the final report the LRF’s range error to a 90% confidence.

LEGEND:

App – appendix km – kilometer LRF – Laser Rangefinder

O – Objective R.B. – Requirements Baseline

LRF performance will be determined by the range error and maximum effective range.

a. Range Error. Range error will be calculated by differencing the reported sensor-to-target slant range and the true slant range. The true slant range will be determined by the instrumented DGPS on the aircraft and geodetic survey of the target. Moment arm corrections will be accounted for between the DGPS receiver and the payload.

b. Maximum Effective Range. The maximum effective range will be calculated by conducting LRF events at increasing ranges until the LRF range error is exceeded. The effective range is defined as the range at which the range error still meets the specification requirement (less than 5 m of range error).

Once the data have been reviewed and quality assured, run-by-run data will be compiled.

The run-by-run data will contain all relevant information such as the event time, range-to-target, FOV, target location, and sensor selected.

2.4.3 Demonstration Procedures and Data Required

a. Instrumentation. Data collection during LRF trials will be performed with the use of on-board aircraft instrumentation including data recorders to collect sensor video, selected metadata parameters, and a DGPS unit to collect aircraft TSPI. Range instrumentation will include a MET system for atmospheric documentation; Mission Control for data recording and real-time screening; instrumentation cameras for documenting and recording target conditions; a range time system for data correlation; and the VBLSS to record and score the laser spot on target.

b. Target. Refer to section 2.3.3b for targets.

c. Procedures. The test aircraft will fly various arcs at 8,000 feet (ft) Above Ground Level (AGL) and 6,000 ft AGL for EO and IR trials, respectively. LRF events will be conducted using a manual “ranging” trigger at various ranges including 7.0, 8.5, 10.0, 11.5, and 13.0 km.

Figure 2.4–1 shows the various flight profiles.

Figure 2.4–1. Example Flight Profiles

LRF testing will be conducted concurrently with the LD subtest events. The LRF performance demonstration matrix is shown in table 2.4–2.

Table 2.4–2. LRF Performance Demonstration Matrix Demonstration

Point Sensor Day/ Night

Slant Range

(km) Target

Focal Length

(mm) Data Points

LRF–1

EO or

IR

Day/ Night

7.0

Static Optimal

LRF–2 8.5 6

LRF–3 10.0 6

LRF–4 11.5 6

LRF–5 13.0 6

NOTE: Slant range will be increased until LRF range error requirement is not met.

LEGEND:

EO – Electro Optical mm – millimeter

Procedures for collecting the LRF performance are as follows:

(1) A calibration maneuver will be performed at the vendor’s request prior to beginning LRF testing. A dry run will be performed to ensure that laser energy is being recorded by the VBLSS. Payload-unique settings will be recorded.

(2) Perform all normal sensor preflight checks IAW the aircraft manual.

(3) Transition the aircraft to the demonstration area.

(4) Acquire the target board and center the reticule (crosshairs).

(5) Verify target crew is ready for data collection.

(6) Begin countdown to engagement.

(7) Range target for 3 seconds.

(8) Data collector will document the start time.

(9) Data collector will document the end time.

(10) Break lock on target and reacquire on target for another 3-second event.

(11) Repeat steps (9) through (11) until the aircraft reaches the end of the flight profile

(12) Repeat steps (1) through (5) as required by the demonstration matrix.

vendor will have the option to install a backup payload. Once the test aircraft re-launches to resume test, if an essential function failure occurs, the system will be rebooted. If a second essential function failure occurs on the second flight attempt, testing will end for that vendor and

d. Data Required. Refer to section 2.2.3d for data requirements.

2.5 LASER TARGET MARKER

2.5.1 Objective

To verify the functionality of the LTM.

2.5.2 Criteria and Analysis

YTC personnel will analyze the vendor data for the LTM subsection of the demonstration as presented in table 2.5–1. Criterion for this subsection was derived from the PBS for the Payload Subsystem for the RQ–7Bv2 TUAS Version 1.0.

Table 2.5–1. Laser Target Marker Criterion and Analysis

Item No. Criterion Analysis

The LTM shall have a wavelength of 850 nm ± 50 nm. (R.B.151)

The vendor payload’s LTM wavelength will be documented and included in the final report.

LEGEND:

App – appendix nm – nanometer

All functionality requirements of vendor LTM on the TUAS will be demonstrated and verified to make sure the system is safe for use.

2.5.3 Demonstration Procedures and Data Required

a. Instrumentation. For this subsection, either night vision goggles (NVGs) or a video camera with appropriate filter (850 nm) will be used to enable viewing the laser energy from the LTM. All LTM testing will be completed during nighttime.

b. Targets. See Section 2.3.3b for targets.

c. Procedures. LTM functionality will be determined by illuminating the target and verifying the laser is visible from the ground using NVGs, or a camera with an appropriate filter.

All LTM testing will be completed during nighttime. LTM testing will be conducted on the return flight for efficiency.

d. Data Required. No additional data required for this subsection of the demonstration.

2.6 TARGET LOCATION ERROR

2.6.1 Objective

To determine the two- and three-dimensional TLE).

2.6.2 Criteria and Analysis

YTC personnel will analyze the vendor data for the TLE subsection of the demonstration as presented in table 2.6–1. All criteria for this subsection were derived from the PBS for the Payload Subsystem for the RQ–7Bv2 TUAS Version 1.0.

Table 2.6–1. TLE Criteria and Analysis

Item No. Criteria Analysis

The payload shall be capable of calculating 3-dimensional geographic coordinates of target objects along the sensor LOS.

(R.B.182)

The capability of calculating 3-dimensional geographic coordinates of target objects along the sensor LOS will be documented and the target location errors will be included in the final report.

TLE shall be not greater than 30 m circular (2-dimensional) to a 90% confidence (T), 15 m circular and linear (3-dimensional) to a 90% confidence (O) from an operationally-effective altitude (8,000 ft AGL-day; 6,000 ft AGL-night) and slant range of 7 km.

(R.B.183)

The 2-dimensional and 3-dimensional TLE will be calculated to a 90% confidence and will be documented and included in the final report

LEGEND:

% – percent AGL – Above Ground Level App – appendix ft – foot

LOS – Line of Sight

O – Objective R.B. – Requirements Baseline

TLE – Target Location Error

Horizontal TLE (HTLE) is defined as the two-dimensional distance and absolute TLE (ATLE) is the three-dimensional distance, in meters, between the reported coordinates and the true target location. The TLEs will be reported as a mean value and the TLE Circular Error 90% (CE90). TLE CE90 is the radius of a circle, centered about the true target position, which encompasses 90% of the data. When measuring ATLE, the vertical distance which encompasses 90% of the data points is referred to as Linear Error 90% (LE90).

2.2.3 Demonstration Procedures and Data Required

a. Instrumentation. See Section 2.3.3a for instrumentation.

b. Targets. See Section 2.3.3b for targets.

c. Procedures. Data for this subsection will be collected concurrently with LRF subsection events.

d. Data Required. No additional data required for this subsection.

2.7 SYSTEM FUNCTIONALITY

2.7.1 Objectives

a. To document vendor payload subsystem functionality requirements.

b. To document laser safety interlock functionality between vendor payload and test aircraft.

2.7.2 Criteria and Analysis

YTC personnel will analyze the vendor payload data for the system functionality subsection of the demonstration as presented in table 2.7–1. All criteria for this subsection were derived from the PBS for the Payload Subsystem for the RQ–7Bv2 TUAS Version 1.0.

Table 2.7–1. System Functionality Criteria and Analysis

Item No. Criteria Analysis

The payload shall transition to the Operate State when 28 VDC power is applied and the payload is commanded on (R.B.06).

YTC personnel will document and include in the final report if the vendor payload transitioned to the Operate State when 28 VDC power was applied and the payload was commanded on.

The vendor supplied interface hardware and software shall enable full command and control of the payload to complete the test objectives in sections 2.2 through 2.6 of this test plan.

YTC personnel will document and include in the final report if the vendor supplied interface hardware and software enabled full command and control of the payload to complete the test objectives in sections 2.2 through 2.6 of this test plan.

The vendor payload shall output digital Full Motion Video for recording and post-flight analysis.

YTC personnel will document and include in the final report if the vendor payload output digital Full Motion Video for recording and post-flight analysis.

The payload shall support a hardware interlock function that would prevent Class 2 lasers and above from accidental firing.

(R.B.214)

The vendor payload’s ability to support a hardware interlock function that prevents Class 2 lasers and above from accidental firing will be documented and included in the final report.

Operator support equipment for payload shall adhere to the equipment rack specifications, per app H.

YTC personnel will document and include in the final report if the vendor payload support equipment adhered to the equipment rack specifications.

LEGEND:

App – appendix

VDC – Volts Direct Current

2.7.3 Demonstration Procedures and Data Required

a. Instrumentation. No instrumentation is required for this subsection.

b. Targets. No targets are required for this subsection.

c. Procedures. No specific procedures will be conducted for this subsection. If an essential function failure occurs during testing, the system will be rebooted. If another essential failure occurs, the test aircraft will land and be examined. At this time, the vendor will have the option to install a backup payload. Once the test aircraft re-launches to resume test, if an essential function failure occurs, the system will be rebooted. If a second essential function failure occurs on the second flight attempt, testing will end for that vendor and system. The flow chart for decision making regarding essential function failures can be found in appendix I.

System functionality requirements will be verified concurrently with all other subsections.

d. Data Required. No additional data required for this subsection.

APPENDIX A. SHADOW TUAS PAYLOAD DEMONSTRATION CRITERIA

A–1

SECTION 3. APPENDICES

A. DEMONSTRATION CRITERIA

Table A–1 shows the criteria for the Shadow TUAS payload demonstration.

Table A–1. Shadow TUAS Payload Demonstration Criteria Item No. Demonstration Criteria Subsection

1 The total weight of the payload shall be no greater than 50 lb. (R.B.197) 2.1

When in the installation and removal position (i.e., payload stowed), the payload diameter shall be no greater than 10.4 in. (R.B.195)

2.1

3 The total height of the payload shall be no greater than 16.9 in. (R.B.196) 2.1

The laser system must have been evaluated by PHC or equivalent DoD radiation safety office and received approval to operate on DoD installations.

Documentation of safety evaluation and approval to operate must be provided to YTC prior to test.

2.1

The laser system must meet the laser ANSI Z136.1 Section 4, Control Measures.

2.1

6 The laser system must have Laser Fire Exclusion Zones per App E. 2.1

The payload shall operate using no more than 300 W of the Shadow TUAS power specification.

2.1

The proposal must include all required documentation listed in section 2.1.3.c as required for AWR approval.

2.1

The EO sensor recognition requirement is per the Johnson Criteria. The assumed operational altitude is 8,000 ft AGL. The EO sensor shall supply a video output of sufficient quality to recognize, with 70% probability of recognition, a 3.5-m by 3.5-m target at a slant range of not less than 13 km (T), 35 km (O) given an N50 of 3 cycles on target, relative humidity of 90%, visibility of 23 km, and a target contrast of 40%. (R.B.135)

2.2

The IR sensor recognition requirement is per the Johnson Criteria. The assumed operational altitude is 6,000 ft AGL. The IR sensor shall supply a video output of sufficient quality to recognize, with 70% probability of recognition, a 3.5-m by 3.5-m target at a slant range of not less than 7 km (T), 35 km (O) given an N50 of 3 cycles on target, relative humidity of 90%, visibility of 23 km, and a target foreground-background temperature difference of 4 degrees C. (R.B.141)

2.2

11 The LD shall support PRF mode. (R.B.174) 2.3

The LD beam divergence, boresight error, and stabilization shall be such that not less than 90% of the designator beam energy falls on a 3.5-m by 3.5-m target not less than 90% of the time when the designator is fired from a range of 7 km (T), 10 km (O). (R.B.166)

2.3

The LRF shall have a maximum effective range of not less than 7 km (T), 10 km (O). (R.B.158)

2.4

The magnitude of the LRF range error shall not be greater than 5 m to a 90% confidence. (R.B.160)

2.4

15 The LTM shall have a wavelength of 850 nm ± 50 nm. (R.B.151) 2.5

The payload shall be capable of calculating 3-dimensional geographic coordinates of target objects along the sensor LOS. (R.B.182)

2.6

APPENDIX A. SHADOW TUAS PAYLOAD DEMONSTRATION CRITERIA

A–2

Table A–1. Shadow TUAS Payload Demonstration Criteria (Concluded) Item No. Demonstration Criteria Subsection

TLE shall be not greater than 30 m circular (2-dimensional) to a 90% confidence (T), 15 m circular and linear (3-dimensional) to a 90% confidence

(O) from an operationally-effective altitude (8,000 ft AGL-day; 6,000 ft AGL-night) and slant range of 7 km. (R.B.183)

2.6

The payload shall transition to the Operate State when 28 VDC power is applied and the payload is commanded on (R.B.06).

2.7

The vendor supplied interface hardware and software shall enable full command and control of the payload to complete the test objectives in sections

2.2 through 2.6 of this test plan.

2.7

The vendor payload shall output digital Full Motion Video for recording and post-flight analysis.

2.7

The payload shall support a hardware interlock function that would prevent Class 2 lasers and above from accidental firing. (R.B.214)

2.7

Operator support equipment for payload shall adhere to the equipment rack specifications, per app H.

2.7

NOTE: All criteria for this demonstration were derived by YPG or from the Performance Based Specification for the Payload Subsystem for the RQ–7Bv2 TUAS Version 1.0.

LEGEND:

% – percent ± – plus or minus AGL – Above Ground Level ANSI – American National Standards Institute App – appendix AWR – Airworthiness Release DoD – Department of Defense EO – Electro-Optical ft – foot

in. – inch IR – Infrared km – kilometer lb – pound

LOS – Line of Sight m – meter nm – nautical mile No. – number O – Objective PHC – Public Health Center PRF – Pulse Repetition Frequency R.B.