MISTE_SCETI-ACE-Performance-Spec-PSN.PDF

PRF-PT-703

11 Oct 2018 ii

FOR OFFICIAL USE ONLY (FOUO)

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 Atmospheric Measurement 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.1 DVE Volume

3.1.1.1 Threshold DVE Volume Dimensions

3.1.1.2 Objective DVE Volume Dimensions

3.1.1.3 Threshold DVE Volume Emulation Zones

3.1.1.4 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 Reset

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 Reset

3.3.5 FDC Reconfiguration

3.3.6 EFC Occlusion By The FDC

iii

3.4 Atmospheric Measurement Capability Requirements

3.4.1 Atmospheric Measurement 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 Identification

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 (ESOH) requirements

3.9 Security and Privacy Requirements

3.10 System Quality Factors

3.10.1 Power Infrastructure

3.11 Interface identification and diagrams

3.12 Design and construction constraints

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

FIGURES

Fig. No. Title Page

Figure 1.2-1 SCETI Conceptual Drawing Figure 3.12-1 RATH System View iv

TABLES

Table Title Page

Table I. Requirement/Verification Cross-Reference Matrix

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 (PM ITTS), Instrumentation Management Office (IMO). Army Test and Evaluation Command (ATEC) is the combat developer, and Redstone Test Center (RTC) is the system user of all capabilities delivered by SCETI ACE.

1.1 Identification

The SCETI concept drawing is included in Figure 1.2-1. 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 (RDC), Dust Development Capability (DDC), 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 (LZ SO)

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.

The Government is coordinating site preparation to support SCETI.

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.

Test Network

A

B

C

C

D

E

F

Figure 1.2-1 SCETI Conceptual Drawing

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 3. 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.

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

1.2.2 Atmospheric Measurement 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 (MIL-STD) 810G with Change Notice 1, Department of Defense

Test Method Standard, Environmental Engineering Considerations and Laboratory Tests, 15 Apr 2014.

b. MIL-HDBK-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

None

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 DVE volume shall be at least 100 feet wide, 200 feet long, and 80 feet high.

3.1.1.2 Objective DVE Volume Dimensions

The DVE volume shall be up to 150 feet wide and at least 200 feet long and 80 feet high.

3.1.1.3 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.

3.1.1.4 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.

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 year round.

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

https://www.ncdc.noaa.gov/

3.2 Snow Development Capability Requirements

SCETI shall generate operationally relevant DVE snow conditions at the SCETI site at RTC that match conditions identified in the atmospheric conditions parameters study conducted by the Contractor and agreed to by the Government.

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.

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 Reset

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

3.2.5 SDC Reconfiguration

The SDC shall be adjustable and reconfigurable to support the range of snow parameters identified in the atmospheric conditions parameter study in ways that are automated to the maximum extent practical.

3.2.6 EFC Occlusion By the SDC

The SDC design shall not impede the motion of the EFC throughout the entirety of the DVE volume.

3.3 Fog Development Capability Requirements

SCETI shall generate operationally relevant DVE fog conditions at the SCETI site at RTC that match conditions identified in the atmospheric conditions parameters study conducted by the Contractor and agreed to by the Government.

3.3.1 FDC Generation Volume

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

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 Reset

The FDC shall reset and be ready for test within 15 minutes after test completion. This reset time does not include the time required to reconfigure the FDC for different fog conditions.

3.3.5 FDC Reconfiguration

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

3.3.6 EFC Occlusion By The FDC

The FDC design shall not impede the motion of the EFC throughout the entire DVE volume.

3.4 Atmospheric Measurement 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 Atmospheric Measurement Reporting

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

3.4.2 Instrumentation Transportability

Instrumentation 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

Instrumentation shall measure operationally relevant characteristics of DVE snow conditions reported in the atmospheric conditions parameters study.

3.4.5 Fog Condition Characteristics Identification

Atmospheric measurement capability design shall identify 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 program-level agreement (PLA).

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 (OEM) 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. The contractor will provide special procedures or handling equipment, if required.

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 (ESOH) 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 System Quality Factors

SCETI ACE shall be designed to utilize existing Government ground test equipment, Government test capabilities, Government support equipment, and Government and commercial-off-the-shelf (COTS) equipment to the extent practical.

3.10.1 Power Infrastructure

Power will be provided to the SCETI ACE subsystems by Redstone Arsenal through an interface which may be modifiable by the RTC personnel to meet requirements at the permanent SCETI site. SCETI ACE design documentation shall indicate power connections required for all SCETI ACE subsystems in order to guide Redstone Arsenal in providing specialized connections.

3.11 Interface identification and diagrams.

SCETI interfaces to external elements are summarized as follows:

• Global Positioning System (GPS) – Provides time information to calibrate SCETI time code generation. This is an interface typically used during test setup.

• RTC Base Infrastructure – Provides electrical power and water to SCETI, receives testing status and security information. This optional interface is used when SCETI is located at Redstone Arsenal. Interface control documentation for the Base Infrastructure will be provided by RTC.

• Operator, Analysts – Provide test controls and data inputs, receive test results.

3.12 Design and construction constraints

The RATH, shown in Figure 3.12-1, has a software architecture based on the Test and Training Enabling Architecture (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 3.12-1 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.

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 I. 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

3.1.1.3 x x x

3.1.1.4 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

Table I. 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 CDR

3.10.1 x x Verify at PDR

3.11 x x Verify at PDR

3.12 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.

1.3 Document Overview