ATTACHMENT_07_MISTE_DO_SCETI_ACE_PERFORMANCE_SPEC_FINAL_REV.pdf

i Distribution C – Authorized to U.S. Government agencies and their contractors in support of this contracting effort. Other requests for this document shall be referred to PM ITTS, IMO.

SYSTEM PERFORMANCE SPECIFICATION

FOR

MODERNIZING INSTRUMENTATION SOLUTIONS FOR

TEST AND EVALUATION

(MISTE)

SYSTEM-OF-SYSTEMS CONTROLLED ENVIRONMENT TEST INFRASTRUCTURE

(SCETI

ATMOSPHERIC CONDITIONS ENHANCEMENT (ACE)

U.S. ARMY PROGRAM EXECUTIVE OFFICE

FOR

SIMULATION, TRAINING AND INSTRUMENTATION (PEO STRI)

12211 SCIENCE DRIVE

ORLANDO, FL 32826-3276

ii

Table of Contents

Para./Section Title Page

1. SCOPE

1.1 Identification

1.2 System Description

1.2.1 Atmospheric Effects Development Capabilities Description

1.2.2 AM Capabilities Description

1.3 Document Overview

2. APPLICABLE DOCUMENTS

2.1 Government Documents

2.1.1 Federal Regulations

2.1.2 Occupational Safety and Health Administration

2.1.3 Program Level Documents

2.2 Non-Government Documents

2.3 Order of Precedence

3. SYSTEM REQUIREMENTS

3.1 SCETI General Requirements

3.1.1 DVE Volume

3.1.1.1 Threshold DVE Volume Dimensions

3.1.1.2 Threshold DVE Volume Emulation Zones

3.1.1.3 Objective DVE Volume Emulation Zones

3.1.2 SCETI Operating Conditions

3.1.2.1 RTC Operating Location

3.1.2.2 RTC Operating Environment

3.2 Snow Development Capability Requirements

3.2.1 SDC Generation Amount

3.2.2 Threshold Snow Conditions Duration

3.2.3 Objective Snow Conditions Duration

3.2.4 SDC Capability

3.2.5 SDC Reconfiguration

3.2.6 EFC Occlusion by the SDC

3.3 Fog Development Capability Requirements

3.3.1 FDC Generation Volume

3.3.2 Threshold Fog Conditions Duration

3.3.3 Objective Fog Conditions Duration

3.3.4 FDC Capability

3.3.5 FDC Reconfiguration

iii

3.3.6 EFC Occlusion by the FDC

3.4 AM Capability Requirements

3.4.1 AM Reporting

3.4.2 Instrumentation Transportability

3.4.3 Instrumentation Stand-Alone Mode

3.4.4 Snow Condition Characteristics

3.4.5 Fog Condition Characteristics

3.5 Control Software Requirements

3.5.1 Cybersecurity

3.5.2 Subsystem Control

3.5.3 Health and Status Monitoring

3.6 Hardware Requirements

3.7 Logistics Requirements

3.7.1 Maintenance Downtime

3.7.2 Maintenance Concept

3.7.3 Transportability

3.7.4 System Assembly, Disassembly, and Storage

3.7.5 Permanent Infrastructure

3.7.6 Spares

3.8 Environmental, Safety, and Operational Health Requirements

3.9 Security and Privacy Requirements

3.10 Site Infrastructure

3.11 Design and Construction Constraints

3.12 Facilities and Infrastructure

4. VERIFICATION

4.1 Methods of Verification

4.2 Classes of Verifications

5. SCETI DEFINITIONS

5.1 DVE Condition Definition

5.2 DVE Volume Definition

6. ACRONYMS

FIGURES

Fig. No. Title Page Figure 1: SCETI Test Site Figure 2: RATH System View iv

TABLES

Table Title Page Table 1: Huntsville, Alabama Average Weather Conditions Table 2: Requirement/Verification Cross-Reference Matrix

PRF-PT-703

15 April 2019

Performance Specification For System-of-Systems Controlled Environment Test Infrastructure Atmospheric

Conditions Enhancement

1. SCOPE

This specification establishes the performance requirements for the design, development, implementation, integration, installation, demonstration, verification, and training of the Atmospheric Conditions Enhancement (ACE) for the System-of-Systems Controlled Environment Test Infrastructure (SCETI) at Redstone Test Center (RTC).

The acquisition agency for this effort is the Project Manager for Instrumentation, Targets, Threat Simulators and Special Forces Operations (SOF) Training Systems, Instrumentation Management Office (IMO). U.S. Army Test and Evaluation Command (ATEC) is the combat developer, and RTC is the system user of all capabilities delivered by SCETI ACE.

1.1 Identification

SCETI is a test asset for aircraft sensor assemblies to verify their functionality within Degraded Visual Environment (DVE) conditions. The primary capabilities of the base SCETI are listed below, and the ACE subsystems are described in section 1.2.

a. Emulated Flight Capability (EFC)

b. Atmospheric Effects Development Capabilities, including the Rain

Development Capability, Dust Development Capability, Snow Development Capability (SDC), and Fog Development Capability (FDC)

c. Atmospheric Measurement (AM) Capability

d. Test Control Center (TCC)

e. Landing Zone Staging and Obstacles

This specification defines the requirements to develop and deliver the ACE for SCETI, which includes the SCETI SDC, FDC, and enhancements to the AM capabilities in order to characterize snow and fog.

1.2 System Description

A full suite of the SCETI capabilities will be delivered to RTC. Figure 1.2-1 depicts a concept drawing for the full SCETI system.

1.2.1 Atmospheric Effects Development Capabilities Description The SCETI has a requirement to generate DVE conditions for testing the functionality of sensors in low-visibility flight conditions. The atmospheric effects development capabilities initially provide operationally relevant DVE rain and dust conditions within the DVE emulation volume to verify System Under Test (SUT) functionality. This effort is to enhance the atmospheric effects development capabilities with operationally relevant DVE snow and fog conditions. These capabilities are expected to be produced by themselves or combined with other environmental conditions (i.e., rain and fog concurrently, snow and fog concurrently).

The SCETI system at RTC will generate DVE snow and fog conditions at a Government instrumentation test facility on Test Area 6. The contractor is responsible for delivering the snow and fog generation systems, and defining to the Government the infrastructure connections necessary to generate these conditions.

Figure 1: SCETI Test Site

The contractor shall conduct a study to identify operationally relevant conditions of snow and fog for DVE sensor testing.

1.2.2 AM Capabilities Description

The AM capabilities consist of a suite of instrumentation support equipment to measure relevant characteristics of the atmosphere within the DVE emulation volume. These instruments are connected to the TCC to report real-time atmospheric conditions and changes in weather conditions. Data captured by the instrumentation is used by test operators to verify that conditions in the DVE volume are operationally relevant, and to characterize the performance of the SUT.

1.3 Document Overview

This specification describes essential SCETI ACE performance and functionality to support project initiation and contracting efforts. It will be augmented by a contractor-developed and complete system/subsystem specification as part of this acquisition.

2. APPLICABLE DOCUMENTS

The following documents of the exact issue listed form a part of this specification to the extent specified herein. This specification is designated as a first tier document. The documents referenced directly in this specification are designated as second tier documents, and are considered part of this specification to the extent specified herein.

Documents referenced in successive tiers are not part of this specification and are to be used for guidance only.

2.1 Government Documents

a. Military Standard 810G with Change Notice 1, Department of Defense Test Method Standard, Environmental Engineering Considerations and Laboratory Tests, 15 April 2014.

b. MIL-Handbook-310, Department of Defense Handbook, Global Climatic Data for Developing Military Products, 23 June 1997.

c. Test/Training Enabling Architecture (TENA) Architecture Reference Document 2016-11

2.1.1 Federal Regulations

2.1.2 Occupational Safety and Health Administration

2.1.3 Program Level Documents

SOW-2018-0008 Statement of Work for SCETI ACE

2.2 Non-Government Documents

Weather Taxonomy for Atmospheric Fog by AQRSC, LLC, 23 Aug 2017

2.3 Order of Precedence

In the event of a conflict between the text of this specification and the references cited herein, the text of this specification takes precedence. Nothing in this specification, however, supersedes applicable laws and regulations, unless a specific exemption has been obtained.

3. SYSTEM REQUIREMENTS

The following section defines the requirements that the SCETI ACE shall meet to be acceptable to the Government. The main elements of SCETI ACE are the SDC, the FDC, the AM capability enhancements, and associated control software to be installed within the existing TCC. Capabilities developed under SCETI ACE shall be delivered to RTC. All drawings and illustrations used in this document are notional and for illustration purposes only. The Government is not specifying any particular design, and the illustrations are used to improve communication of the functional requirements.

3.1 SCETI General Requirements

The following requirements apply to the SCETI system overall.

3.1.1 DVE Volume

SCETI shall provide a DVE volume in which all DVE conditions to which the SUT is subjected will be generated.

3.1.1.1 Threshold DVE Volume Dimensions

The threshold DVE volume shall be at least 100 feet wide, 200 feet long, and 80 feet high.

3.1.1.2 Threshold DVE Volume Emulation Zones

The DVE volume shall be able to be divided into up to four zones which can be controlled independently to generate different DVE conditions characteristics. Each zone shall have a minimum division of 25 feet long x 50 feet wide x 80 feet high, and up to the complete DVE volume. Zones shall not be physically portioned and do not have to be partitioned in equal volumes. Zones shall be able to be adjacent or not adjacent to one another.

3.1.1.3 Objective DVE Volume Emulation Zones

The DVE volume shall be able to be divided into up to eight zones which can be controlled independently to generate different DVE conditions characteristics. Each zone shall have a minimum dimension of 25 feet long x 50 feet wide x 80 feet high and up to the complete DVE volume. Zones shall not be physically portioned and do not have to be partitioned in equal volumes. Zones shall be able to be adjacent or not adjacent to one another.

3.1.2 SCETI Operating Conditions

3.1.2.1 RTC Operating Location

The SCETI system shall operate in an open field at Redstone Arsenal without pre-existing concrete foundations.

3.1.2.2 RTC Operating Environment

All systems shall be operable outdoors in temperature and weather conditions typical to Redstone Arsenal.

Historical weather data may be found through the National Oceanic and Atmospheric Administration’s National Climactic Data Center at, https://www.ncdc.noaa.gov/, or a similar reputable source of climate information.

Currently the Government does not have a Snow Taxonomy reference to serve as a guide to support the vendor’s technical approach development. For this reason the vendor will be required to conduct and independent validation of MIL-STD 810G and assess its applicability to the SCETI snow development sub-system. In addition, the Government is providing pertinent operational boundary conditions to assist industry in the development of their technical approach.

Snow Meteorological conditions in Huntsville Alabama. The SCETI instrumentation system will be delivered, integrated and fielded at test area 06 Redstone Arsenal. Table 1 below identifies the average weather conditions in Huntsville as reported by the National Climatic Data Center, NOAA’s 1981-2010 Climate normal:

High (°F) Low (°F) High °C High

°C Annual average Temperature (1) 73 51 23 11 Days Inches Centimeters Average Annual Snowfall (2) 2.3 2.4 6.1 Daily (%) Morning (%) Afternoon (%) Annual Average Humidity (3 & 4) 70 84 53 High Time Low Time Highest and Lowest Humidity (5) 84.1 6 am 53.3 3 pm Days Inches Millimeters Average Annual Precipitation (6) 117 54.3 1380 Sunny Partly Sunny Totals with Sun Days of Sunshine (7) 100 101 201

Table 1: Huntsville, Alabama Average Weather Conditions https://www.ncdc.noaa.gov/

Notes:

(1) The table gives the normals for maximum and minimum temperatures based on weather data collected from 1981 to 2010 by the US National Climatic Data Center.

(2) The table gives yearly averages for total snowfall. The numbers are for the total amount of snow and for how many days it snows at least 0.1 inches (0.25 centimeters)

(3) The average humidity year round is listed in the table. The table gives daily averages along with highest and lowest relative humidity levels. Relative humidity measures the actual amount of moisture in the air as a percentage of the maximum amount of moisture the air can hold. All the numbers here are averages for the years 1961 to 1990.

(4) In this table, the Daily number is the average of humidity readings taken every three hours throughout the day. Morning percentages are for 6 am and Afternoon measures are for 3 pm local standard time.

(5) Figures are averages over the year for maximum and minimum humidity levels in Huntsville Alabama. The hours when the highest and lowest humidity readings usually occur are given in local standard time.

(6) The table lists yearly averages for rainfall plus snowfall. This is the total for the amount of precipitation it usually receives in a year. This includes the days when precipitation amounts to 0.01 inches (0.25 millimeters) or more.

(7) Partly Sunny Days have cloud covering from 40% to 70% of the sky during the daytime.

Total Days with Sun is a sum of the Sunny plus Partly Sunny days. The rest of the days are mainly overcast, with at least 80% cloud cover. All the numbers are annual averages, made from years of weather watching.

Based on the weather climate conditions of Huntsville AL, the Government understands that snow generation can only occur via machine-made applications. In addition, generating representative snow conditions is challenging due to weather condition dependencies at the day and time when snowfall is generated; research indicates that machine-made snow is denser than natural snow. Therefore, the following parameters are provided as additional guide:

Blowing Snow: MIL-STD-810G provides operational extremes for blowing snow are given in terms of horizontal mass flux of snow particles; that is, the mass of snow moving horizontally across a unit area per unit time. There are no requirements for horizontal mass flux; suggest for industry to provide the technical performance attributes of the snow-making equipment selected for their technical approach.

Intensity or Visibility: There is not a requirement for intensity or visibility because snow will be used as a degraded visual environment to assess the sensor’s specialized technology performance. However, vendors are required to provide the projected snowfall generation with the equipment selected for their technical approach.

3.2 Snow Development Capability Requirements

SCETI shall generate machine-made, operationally relevant DVE snowfall conditions at the SCETI site at RTC with the following characteristics below. The generated snow shall be water based and not artificially/chemically created. However, the use of ice nucleating crystals in generating snow is acceptable. The SDC system shall be able to be operated manually in a standalone mode and computer software controlled.

Particle size distribution range: 47-130 micrometers

Snowfall rates:

Low rate is Less than 0.5 inches per hour Medium rate is 0.5 to 1.5 inches per hour High rate is Greater than 1.5 inches per hour

3.2.1 SDC Generation Amount

Operationally relevant DVE conditions generated by the SDC shall fill either the entire DVE volume or zone of the DVE volume being used, up to the full height of the volume.

Wind factors are unpredictable and shall not be considered.

3.2.2 Threshold Snow Conditions Duration

DVE conditions generated by the SDC shall last long enough to support test durations of at least 10 minutes.

3.2.3 Objective Snow Conditions Duration

DVE conditions generated by the SDC shall last long enough to support test durations of 15 minutes or longer.

3.2.4 SDC Capability

The SDC shall be ready for test within 15 minutes after each test completion. This time does not include the time required to reconfigure the SDC for different snow conditions.

The SDC shall support the capability for 4 test iterations per an 8-hour day.

3.2.5 SDC Reconfiguration

The SDC shall be adjustable and reconfigurable to support the range of snow parameters identified in Paragraph 3.2 that are automated to the maximum extent practical.

3.2.6 EFC Occlusion by the SDC

The SDC design shall not have any SDC equipment located within the DVE volume..

3.3 Fog Development Capability Requirements

SCETI shall generate operationally relevant DVE fog conditions at the SCETI site at RTC as described in the Weather Taxonomy for Atmospheric Fog that replicates closely the atmospheric parameters for radiation fog, ground fog and advection fog. The generated fog shall be water based and not artificially/chemically created.

3.3.1 FDC Generation Volume

Operationally relevant DVE conditions generated by the FDC shall fill either the entire DVE volume or zone of the DVE volume being used. Wind factors are unpredictable shall not be considered.

3.3.2 Threshold Fog Conditions Duration

DVE conditions generated by the FDC shall last long enough to support test durations of at least 10 minutes.

3.3.3 Objective Fog Conditions Duration

DVE conditions generated by the FDC shall last long enough to support test durations of 15 minutes or longer.

3.3.4 FDC Capability

The FDC shall be ready for test within 15 minutes after test completion. This time does not include the time required to reconfigure the FDC for different fog conditions. The FDC shall support the capability for 4 test iterations per an 8-hour day.

3.3.5 FDC Reconfiguration

The FDC shall be adjustable and reconfigurable to support the range of fog parameters identified in Paragraph 3.3 in ways that are automated to the maximum extent practical.

3.3.6 EFC Occlusion by the FDC

The FDC design shall not have any FDC equipment higher than 2ft above ground within the DVE volume.

3.4 AM Capability Requirements

SCETI shall use a suite of instrumentation to characterize the atmospheric conditions within the DVE volume during test events as conditions identified in the atmospheric conditions parameters study conducted by the contractor, and agreed to by the Government. Data collected by the atmospheric effects measurement capability will be used to verify that conditions generated were the conditions desired for SUT testing.

3.4.1 AM Reporting

SCETI AM capabilities shall be able to report measurements to the TCC for display and recording.

3.4.2 Instrumentation Transportability

AM instrumentation and equipment shall be transportable and able to support testing at outdoor locations away from the primary SCETI installation.

3.4.3 Instrumentation Stand-Alone Mode

Instrumentation shall have a stand-alone mode able to measure, display, and record atmospheric parameters without connecting to the TCC.

3.4.4 Snow Condition Characteristics

AM instrumentation shall measure relevant characteristics of DVE snow conditions reported in the atmospheric conditions parameters study.

3.4.5 Fog Condition Characteristics

AM instrumentation shall measure relevant characteristics of DVE fog conditions as identified in the atmospheric conditions parameters study.

3.5 Control Software Requirements

The SCETI ACE control software shall be developed as user interface plugins to the RTC Architecture for Test and Evaluation of Hostile Fire (RATH).

3.5.1 Cybersecurity

All software and software documentation delivered shall be in compliance with Risk Management Framework (RMF) standards and the Cybersecurity Plan to be developed by RTC per the Program Level Agreement.

3.5.2 Subsystem Control

The subsystem plugins developed for SCETI ACE subsystems shall support operation of subsystems to include activation and deactivation of all subsystems and automated reconfiguration of the SDC and FDC subsystems.

3.5.3 Health and Status Monitoring

The subsystems shall monitor the current status of all associated equipment and report to the operator any errors to include battery errors, missing connections, out of bound errors, or any other error which will prevent normal operation of the system.

3.6 Hardware Requirements

All SCETI ACE hardware shall meet RMF standards for cybersecurity and be in compliance with the RTC-developed Cybersecurity Plan.

3.7 Logistics Requirements

3.7.1 Maintenance Downtime

The SCETI ACE subsystems shall be designed such that annual maintenance activities do not exceed 0.3 man-years (Threshold) or 0.25 man-years (Objective).

3.7.2 Maintenance Concept

SCETI ACE shall be designed to accommodate a two-level maintenance concept consisting of test range organic support and Original Equipment Manufacturer support, with organic maintenance consisting of fault verification, isolation, and repair.

3.7.3 Transportability

The SCETI ACE capabilities shall be transportable to the extent feasible to support testing at other sites using commercial trailers. The teardown and packing of the SDC, FDC, and AM equipment shall be completed within 5 working days. The unpacking and setup of the SDC, FDC, and AM equipment shall be completed within 5 working days.

The contractor will provide special procedures for handling equipment, if required. The contractor will not be responsible for providing shipping containers, trailers and/or vehicles for the shipment of SCETI ACE components.

3.7.4 System Assembly, Disassembly, and Storage

To the maximum extent possible, all SCETI ACE components shall be designed for disassembly and storage when not in use for test events.

3.7.5 Permanent Infrastructure

SCETI ACE design shall indicate all permanent infrastructure required for the development and operation of SCETI ACE subsystems.

3.7.6 Spares

SCETI ACE shall be delivered with an initial provision of spares for frequently used equipment, important non-redundant systems, and systems or equipment with high expected failure rates.

3.8 Environmental, Safety, and Operational Health Requirements SCETI ACE shall comply with federal laws and regulations and commercial standards and practices related to the environment.

3.9 Security and Privacy Requirements

SCETI ACE shall comply with Army, ATEC, and RTC cybersecurity requirements for operation at both the Sensitive but Unclassified level, and alternatively operation at the Secret level, as configured by operators.

SCETI ACE development itself will not produce or involve classified data, but operations producing test data at classified levels up to Secret are expected after fielding. Any capability fielded to RTC shall be compliant with the RTC Cybersecurity Plan for SCETI.

3.10 Site Infrastructure

Power, data, and water will be provided to the SCETI ACE subsystems by Redstone Arsenal, which may be modifiable by the Government to meet requirements at the permanent SCETI site. SCETI ACE design documentation shall indicate power, data, and water connections required for all SCETI ACE subsystems in order to guide the Government in making the necessary facilities modifications and/or providing specialized connections.

3.11 Design and Construction Constraints

The RATH, shown in Figure 3.11-1, has a software architecture based on the TENA, plug-ins, real-time control, and rapid processing of test data. RATH code and documentation will be provided to the SCETI ACE contractor.

Figure 2: RATH System View

The SCETI control and monitoring functionality shall leverage the RATH to the maximum extent feasible, using the same or compatible software elements and development tools to provide an open, modular, flexible, and extensible architecture.

3.12 Facilities and Infrastructure

The Government will be responsible for all facilities work or permanent infrastructure work required for the installation and testing of the SDC and FDC systems at RTC.

4. VERIFICATION

4.1 Methods of Verification

The following methods will be utilized to accomplish the verification of requirements:

• Analysis – Use of established technical or mathematical models or simulations, algorithms, charts, graphs, circuit diagrams, or other scientific principles and procedures to provide evidence that stated requirements were met. May also include a combination of other methods below.

• Demonstration - Actual operation of an item to provide evidence that the required functions were accomplished under specific scenarios. The items may be instrumented and performance monitored.

• Examination - Generally nondestructive verification that typically includes the use of sight, hearing, smell, touch, and taste; simple physical manipulation; and mechanical and electrical gauging and measurement.

• Test – Applying scientific principles and procedures to determine the properties or functional capabilities of items.

• N/A – Not applicable, no verification necessary.

4.2 Classes of Verifications

The system will be subject to the verification classes listed below, as shown in the Requirement/Verification Cross-Reference Matrix, Table I.

• Contractor Test – Verification performed at a contractor’s location, prior to shipment to RTC.

• Subsystem Test – Verification performed on an element after shipment to RTC, but prior to integration with other SCETI elements.

• Site Acceptance Test (SAT) – Verification of SCETI as an integrated system performed at RTC.

• Functional Configuration Audit (FCA) – Verification of SCETI as an integrated system performed by auditing verification evidence after SAT is complete.

• Other – Verification not performed as part of above classes.

Table 2: Requirement/Verification Cross-Reference Matrix

Requirement/Verification Cross-Reference Matrix

VERIFICATION METHOD VERIFICATION CLASS

N/A - NOT APPLICABLE Con - Contractor Testing

AN - ANALYSIS Sub - Subsystem Testing

DEM – DEMONSTRATION SAT - Site Acceptance Test

EX - EXAMINATION FCA - Functional Configuration Audit

Test - TEST

SECTION 3 VERIFICATION METHOD VERIFICATION CLASS

REQUIREMENT An Dem Ex Test N/A Con Sub SAT FCA Other Verification Notes

3.1.1.1 x x

3.1.1.2 x x x x

3.1.1.3 x x x x

3.1.2.1 x

3.1.2.2 x x

3.2 x x

3.2.1 x x x x x

3.2.2 x x x x x

3.2.4 x x x x x

3.2.5 x x x

3.2.6 x x x x

3.3 x x x x

3.3.1 x x x x

3.3.2 x x x x

3.3.3 x x x x

3.3.4 x x x x x

3.3.5 x x x

3.3.6 x x x x

3.4 x

3.4.1 x x x

Requirement/Verification Cross-Reference Matrix

VERIFICATION METHOD VERIFICATION CLASS

N/A - NOT APPLICABLE Con - Contractor Testing

AN - ANALYSIS Sub - Subsystem Testing

DEM – DEMONSTRATION SAT - Site Acceptance Test

EX - EXAMINATION FCA - Functional Configuration Audit

Test - TEST

SECTION 3 VERIFICATION METHOD VERIFICATION CLASS

REQUIREMENT An Dem Ex Test N/A Con Sub SAT FCA Other Verification Notes

3.4.2 x x x x

3.4.3 x x

3.4.4 x x x x

3.4.5 x x x x

3.5 x x x x

3.5.1 x x Certified by RTC S6 l d

3.5.2 x x x x x

3.5.3 x x x x x

3.6 x x x RTC S6/YTC IA

3.7.1 x x Verify at CDR

3.7.2 x x Verify at CDR

3.7.3 x x Verify at CDR

3.7.4 x x x x Verify at CDR

3.7.5 x x Verify at CDR

3.7.6 x x Verify at Delivery

3.8 x x Verify at CDR

3.9 x x RTC S6/YTC IA

3.10 x x Verify at PDR

3.11 x x

5. SCETI DEFINITIONS

The following terms are used throughout this document and should be understood as defined in this section.

5.1 DVE Condition Definition

A DVE condition is the environment of interest for SCETI test operations, defined as atmospheric conditions which are sufficiently severe to impair the vision of a helicopter pilot.

5.2 DVE Volume Definition

The volume in which DVE conditions shall be generated by SCETI.

6. ACRONYMS

Acronyms Definition ACE Atmospheric Conditions Enhancement AM Atmospheric Measurement ATEC Army Test and Evaluation Command DVE Degraded Visual Environment EFC Emulated Flight Capability FCA Functional Configuration Audit FDC Fog Development Capability IMO Instrumentation Management Office RATH RTC Architecture for Test and Evaluation of Hostile

Fire RMF Risk Management Framework RTC Redstone Test Center SAT Site Acceptance Test SCETI System-of-Systems Controlled Environment Test

Infrastructure SDC Snow Development Capability SUT System-Under-Test TCC Test Control Center TENA Test/Training Enabling Architecture

1.3 Document Overview

6. ACRONYMS