TENM RFI Project Descriptions_RTC_WSTC_BLISS.pdf

Test Enterprise Network Modernization Program (TENM)

The Test Enterprise Network Modernization (TENM) compasses the ATEC requirements of the following three projects: Test Network Modernization, ATEC Fiber Modernization, and Future Wireless Network. TENM will provide ATEC the critical on-range test network bandwidth to move large volumes of test data for analysis and decision-making via fiber and wireless technologies. The on-range test network is the foundation necessary to meet the interconnectivity and interoperability demands of Multi-Domain Live, Virtual, and Constructive (LVC) distributed testing, and to move data to the cloud environment. Each program within TENM focuses on key requirements of the test network infrastructure modernization. TNM focuses on replacing inadequate and end-of-life (EOL) network hardware, addressing bandwidth limitations, redundancy, and network management. AFM’s objective is the replacement of existing and/or installation of new fiber optic test network infrastructure to meet current and future test data throughput requirements. FWN is the development of a wireless test network solution that complements the AFM project with increased performance/coverage, enhanced interoperability, and lower sustainment costs. The test network, composed of both wired and wireless infrastructure, is a critical component for the real-time processing and viewing of test data. Wireless capability provides test network connectivity when wired infrastructure is unavailable or unsuitable. This wireless test network augments the wired network, providing connectivity where no fiber exists and expanding network coverage across the ranges. FWN aims to provide wireless test network capabilities that offer reliable, high-capacity, and comprehensive coverage with throughput that allows streaming of large test data files for real-time viewing and processing to meet evolving test mission requirements. TENM will provide an innovative and efficient platform capable of supporting ATEC’s current and future mission-critical test network requirements.

TENM has identified shortfalls in the existing network infrastructure that are limiting its ability to meet current and/or future testing requirements. These include, but are not limited to:

• Condition of Fiber: Portions of the existing fiber-optic infrastructure is not in serviceable condition or are damaged.

• Lack of Fiber: Test areas/locations that are not serviced with fiber-optic infrastructure and/or areas where they don’t meet the minimum fiber strands per building.

• Fault Tolerance: No diverse fiber routes to maintain redundant network paths where needed. Redundancy eliminates single points of failure to maintain availability and provide uninterrupted data collection and transmission performance.

• Low Available Bandwidth: Current fiber infrastructure does not support required bandwidth of concurrent modern instrumentation.

• Maintenance and Testing: No modern equipment necessary to maintain, operate, and repair existing fiber infrastructure, or the ability to validate repairs to the level required for modern instrumentation.

• Accessibility: Inability for immediate access to be able to maintain/repair and support range fiber infrastructure.

• Fiber Documentation: No access to complete and accurate documentation of existing cable infrastructure, specifically, utility map inclusion of fiber-optic infrastructure.

• Wireless: Limited wireless infrastructure (both fixed and transportable) that does not allow ability to increase coverage area and or set up temporary networks with mobile assets.

• Expeditionary Network: Ability to configure and transport network capability to support operational testing at remote sites.

Test Network Modernization (TNM) Network Bandwidth Upgrade

The increase in test data requirements using high-definition video streaming, plus large data transport requirements for live and post mission data are driving the need for a high-capacity network. This high-capacity need is being addressed under an incremental modernization plan that replaces End of Life (EOL) equipment with equipment that has increased capabilities and allows for the bandwidth to be optimized for the Army Test and Evaluation Command (ATEC) Subordinate Organizations (ASOs). As the requirement for test data transport rates increases towards the 10 Gigabits per second (Gbps) network to the edge threshold, the network is at risk of failing to meet test requirements due to network traffic congestion, mission schedules, multiple and simultaneous projects, and mission delays in data distribution during pre-mission setup, live-mission, and post-mission. For example, the combination of optics and telemetry in close proximity for mission support when correlated to the physical network topology will push the edge bandwidth past the nominal 1Gbps network limit. The packetized data both in real-time and post-mission for optics and telemetry are increasing because of high-definition video requests and Telemetry-over-IP (TMoIP) requirements for future modernization plans at the ASOs. The ASOs currently support 1Gbps to the network edge utilizing different topologies, equipment, and infrastructures, as shown in Figure 1.

Figure 1. Current 10 Gbps Core to 1 Gbps to the Edge

The network bandwidth, systems of systems, and technologies under development for future Test and Evaluation (T&E) at ASOs will require much higher bandwidth. Streaming of live and post mission high-definition video over IP is already placing a heavy load on the networks. To support the increased network traffic generated by future projects, as well as high-definition video streaming over IP from mission support entities and unmanned vehicle testing, the network is being upgraded to support a minimum of 100 Gigabits per second at the network backbone and 10 Gigabits per second at the access layer (Figure 2). This incremental hardware upgrade is expected to be completed by FY2027.

Figure 2. 10 Gbps to the Edge with 100 Gbps Core

Army Test and Evaluation Command Fiber Modernization (AFM)

As military systems continue to evolve, T&E data complexity and volume is increasing, resulting in the need for improved data collection and transmission performance. Specifically, there is a need to modernize existing fiber optic infrastructure at ASOs to ensure that it is in proper condition to support bandwidth requirements of TNM equipment implemented on the test ranges. ATEC ASOs test networks require fiber optic infrastructure that supports the data transmission rate of 100 Gigabits per second (Gbps) at the core/distribution layer and 10 Gbps to the access layer. Without sufficient fiber optic infrastructure, the test network equipment is at risk of not supporting bandwidth requirements of the TNM program. TNM equipment, along with fiber infrastructure, supports ASO test networks and instrumentation to improve route diversity and increase bandwidth. Increased U.S. Army Futures Command (AFC) Cross Functional Team (CFT) test workload and modernized minor and major test instrumentation investments are driving the need for increased network throughput, real-time data transmission, and data download capability.

Key Performance Parameter (KPP) Requirements.

This section lists the Key Performance Parameters (KPPs) and Key System Attributes (KSAs) that will address several shortfalls identified above of the current fiber infrastructure, along with ensuring an enterprise approach by creating a basic minimum standard across all the ATEC ASOs. The KPPs listed in Table 1 address the shortfalls for AFM.

Table 1 – KPPs

NUMBER KPP Requirement

Threshold (T): All ASO projects that require the use of single mode fiber optic cables shall have the maximum acceptable attenuation calculated according to the equation in Table 2 using values for coefficients included in the baseline condition row using a wavelength of 1310 nanometer (nm).

Fiber-Optic Attenuation

T: All ASO projects that require the use of single mode fiber optic cables in Dense Wavelength Division Multiplexing (DWDM), or long-distance applications (>=40 kilometers (km)) shall have the maximum acceptable attenuation calculated according to the equation in Table 2 using values for coefficients included in the baseline condition row using a wavelength of 1550 nm.

T: All ASO projects that require the use of multimode fiber optic cables shall have the maximum acceptable attenuation calculated according to the equation in Table 2 using values for coefficients included in the baseline condition row using a wavelength of 850 nm.

Fiber-Optic Attenuation.

Optical Time Domain Reflectometer (OTDR) or a light source with a power meter will be used to test optical fiber attenuation. The metered testing should not exceed the threshold acceptable attenuation value as calculated using the equation for total acceptable attenuation for single and multi-mode fiber in the following table. This KPP ensures conformity with the values for the attenuation calculation for the American National Standards Institute/Telecommunications Industry Association/Electronic Industries Alliance (ANSI/TIA/EIA)-568 B Section B.3 (pg. 27-28 – Optical Fiber Cables).

Table 2 – Attenuation Equation Calculation

Equation Total Attenuation (TA) = n * C + c * J + L * a + M n=number C= C= J= L= a=attenuation M= of attenuation number attenuation total for optical system connectors for one of for one length cable margin optical splices splice (dB) of the (dB/km) (Typically, connector optical 3dB) (dB) cable (km)

LEGEND:

dB – decibel dB/km – decibels per kilometer nm – nanometers

Key System Attributes.

The KSAs listed in Table 3 address the shortfalls for AFM. Reference is made to the USAISEC Technical Criteria for the Installation of Information Infrastructure Architecture (I3A), February 2010 for fiber considerations in the design.

Table 3 – Key System Attributes

Number KSA Requirement 1 Fiber to Test Areas Threshold (T): All fiber runs to Test Areas shall be a minimum of 12 strand cable in accordance with I3A, section 3.15.4.2, unless specified otherwise in local ASOs policies and procedures in conjunction with their agencies.

2 Backbone Fiber T: All outside plant backbone fiber runs shall be a minimum of 24 strand single mode cable in accordance with I3A section, 3.15.4.2, unless specified otherwise in local ASOs policies and procedures in conjunction with their agencies.

3 Fiber Splices T: All outside plant backbone fiber runs shall be fusion spliced to manufactured pigtails in accordance with I3A, section 3.17.3.2.

4 Fiber Specification T: Installed fiber-optic cable shall conform to the specifications outlined in section 3.15 of the I3A.

5 Testing of Fiber T: All fiber runs shall be tested before and after installation using the OTDR method as defined in I3A, section 3.19.2.

6 Range Fiber Installation

T: Fiber installed outside the main cantonment area or designated as “range-controlled fiber” shall be installed in accordance with section

3.12 of the I3A.

8 Diversity T: Communication between Core and Distribution Nodes requires multiple fiber-optic lines to create redundant communication paths to provide fault tolerance and communication availability to support all current and future data bandwidth requirements, as defined in I3A section 3.15.4.5.

9 Dark Fiber T: All multi-destination cables shall be sized with minimum 50 percent spare, unused strands as defined in I3A, section 3.15.4.4.

11 Bandwidth T: All backbone fiber between network cores and distribution nodes shall support a minimum of 100Gb/s bandwidth.

12 Fiber Connector Quality

T: All new fiber-optic terminations shall use an ultra-physical contact spliced-on pigtail connector as defined in I3A, section 3.17.3.2, unless specified otherwise in local policies and procedures in conjunction with their agencies.

Design Constraints

T: All fiber-optic designs shall not include aerial implementations as the primary or preferred solution in accordance with I3A, section 3.6.4. In addition to the stated requirements above, any additional design guidance decisions shall be based on I3A, unless specified otherwise in local policies and procedures in conjunction with their agencies.

16 Operational Availability T: ASO fiber optic infrastructure operational availability, as a system, shall also be 95%.

Future Wireless Network (FWN)

The ASOs require wireless network capabilities for transporting test data in austere environments. These capabilities describe wireless network characteristics in the form of Point-to-Point, Point-to-Multi-Point (PTmP), and mobility scenarios of Line of Sight (LOS) and Non- Line of Sight (NLOS) activities that support T&E across ATEC SOs.

Test capabilities are divided into the following functional areas:

(1) Wireless network to enable instrumentation monitoring and control.

(2) Wireless data transport (i.e., health and test status, real time data collection).

(3) Wireless backhaul to support long-range and high-bandwidth connectivity for field communications.

(4) Wireless data collection from mobile platforms to include dismounted soldiers, vehicles, and Tier 1 Aviation (e.g., helicopters and Unmanned Aerial Vehicles).

(5) Portable wireless infrastructure to enable ad hoc connectivity at remote locations.

(6) Wireless scalability to provide extended and reliable coverage.

(7) Automated reporting tool to support wireless management of the network.

(8) Situational awareness for wireless devices.

(9) Propagation and planning tools to provide quick and accurate prediction of network performance.

The test network, composed of both wired and wireless infrastructure, is a critical component for the real-time processing and viewing of test data. Wireless capability provides test network connectivity when wired infrastructure is unavailable or unsuitable. This wireless test network augments the wired network, providing connectivity where no fiber exists and expanding network coverage across the range. As military systems evolve, T&E data complexity and transport requirements also increase which drive the need for increased performance in FWN. FWN aims to provide wireless test network capabilities that offer reliable and comprehensive coverage with throughput that allows streaming of large test data files for real-time viewing and processing. In maintaining a forward perspective, FWN will provide a wireless test network capability that is high capacity to meet evolving test mission requirements.

The desired approach will maximize the use of wireless capabilities (both fixed and transportable) across the respective test centers to allow flexibility in configuring the desired network that still meets the requirements.

The below use cases/locations are a subset of the overall networking requirements for each ASO.

Additional use cases/locations may be included in any future RFI release based on the responses received to these initial RFIs.

Redstone Test Center (RTC)

Use Case #1: Network Connection at Tethered Hover Pad.

RTC Aviation Flight Test Directorate (AFTD) has the requirement to perform tethered hover testing on U.S. Army aircraft. Fulfillment of this requirement necessitates collecting, in real time, weather data for decision making purposes and telemetry data for safety of flight.

Before a tethered hover event, flight test engineers must monitor weather data for several days to identify trends in wind speed and direction, particularly as to when wind speed will be below the no-go limit of 5 knots. On the day of the event, flight test engineers must be cognizant of the wind speed and direction in order to make the decision on whether to proceed with the test. The current method of collecting weather data over several days is to use the Redstone Test Center’s weather group, who collects data over the entire Arsenal and not specifically at the tether pad. On the day of the test, an AFTD weather van is located at the pad and weather data is called back via radio to the Flight Test Control Center (FTCC), where flight test engineers are prepared to monitor telemetry data. A network capability would allow an AFTD weather van to be located at the tether pad for several days prior to and the day of the test, providing more accurate trend data and allowing real time display of weather data in the FTCC.

Because of the location of the tether pad in relation to AFTD’s telemetry antenna sites, it can often be difficult to maintain good telemetry reception during tethered hover operations. A network-connected telemetry van located at the tether pad would provide a clear line of sight to the test aircraft, improving telemetry reception and eliminating telemetry data dropouts that reduce response time in determining if the aircraft is operating safely.

The Tethered Pad is a concrete circle with no power and no fiber cable. The Tethered Pad has line of sight to Weeden Mountain as shown in figure 1. The distance between the Tethered Pad and Weeden Mountain is 2.4 miles. Solutions should consider alternate ways to power network equipment at the Tethered Pad. Weeden Mountain has a shelter with shore power and backup generator. Weeden Mountain currently has network via existing point-to-point wireless connection. Weeden will be covered in a different use case. Bandwidth requirement for the Tethered Pad is between 500Mb/s and 1Gb/s. Latency requirement is <100ms.

Figure 1.

Use Case 2: Network Connection on Weeden Mountain.

RTC operates building 4193 on top of Weeden Mountain. This building has a shelter with shore power and a backup generator. Currently all networking to Building 4193 is provided by a 300Mb/s point-to-point link. Building is currently used to house LMR Radios and RTC’s Spectrum monitoring system. Weeden Mountain has advantageous geography and location for a future point-to-point wireless hub as well as potential for other test event uses.

AFTD has the requirement to track the position of, in real time, U.S. Army aircraft under test, and to control aircraft systems under test. Tracking data is used for situational awareness, and for pointing vectors for telemetry antennas and sensors under test. A

Bldg. 4193

Weeden Mountain

Bldg. 3689

Madkin Mountain

Redstone Army Airfield

Bldg. 4880

Tethered Pad network connection to the FTCC would allow a two-way, direct connection to the aircraft over a 900 MHz RF modem located on Weeden Mountain. Aircraft position could be input into AFTD’s telemetry antennas and plotted on situational awareness maps.

Instructions from the FTCC could be sent back to the aircraft to control systems under test. In addition, the AFTD Tethered Hover Pad has line-of-sight to the existing tower at Weeden Mountain which could be used to solve lack of networking at that pad.

Due to the possibilities of multiple high bandwidth point-to-point wireless connections, telemetry antennas, situational awareness cameras, spectrum monitoring system, and other uses, Weeden Mountain would be best served by installing new fiber optic cabling to Building 4193. Lack of any fiber has caused this location to be minimally used. There is an existing utility pole line (Figure 2) from B4193 to the base of the mountain that could be used for aerial cable installation up the mountain. The distance from 4193 to ground level is ~3500 feet. The terrain is extremely rocky and uneven. Once to ground level, an additional 10,000 feet of fiber would be ran into the NEC’s concrete duct bank system and pulled to their network hut. If fiber were to be installed, RTC could connect 4193 to its backbone at 40Gb/s speeds providing ample bandwidth for all RTC future needs.

Figure 2.

Bldg.

Ground Level

Use Case 3: Test Area 1 (TA1) Mobile Wireless.

TA1 (Figure 3) is used for testing multiple missile systems and their sensors. TA1 is ~3.6 miles long and up to .75 miles wide. The main road, Centerline Road, runs from the block house (Bldg. 7820) to the other end of the range. Along the side of centerline there is fiber optic cable that runs the length of the road. Approximately every 600 meters there is a “vault” and a “test pad” where some of the fiber is broken out to be used at that test pad. During testing there are several high-speed cameras used at different locations depending on the item that is being tested. The locations of these cameras are not always near a test pad and there are two main “dead spots” where cameras need to be used and there is no network connectivity available. In addition, there is no power available in these dead spots as well. The use case for TA1 would be mobile “kits” (Quantity of 10) that would include their own power source and a wireless point-to-point connection to some central point. Building 6770 sits on top of Hatton Mountain and has line of site to all of TA1. 6770 also has shore power and existing network infrastructure. Building 7820 also has line of sight to all of TA1 and has a short tower that could be used. All range fiber terminates in 7820. Bandwidth requirements for these cameras would be between 500Mb/s and 1Gb/s with <20ms of latency.

Figure 3.

FUTURE VERTICAL LIFT (FVL) ECOSYSTEM USE CASES

Future Vertical Lift Ecosystem Background.

The FVL ecosystem is comprised of three major Army modernization programs, Future Long Range Assault Aircraft (FLRAA), Future Tactical Unmanned Aircraft System (FTUAS), and Launch Effects (LE). This FVL ecosystem re-shapes the battlefield, providing cutting edge capabilities to the Warfighter, enabling critically needed tactic advancement in today’s ever evolving threat environment. The FVL ecosystem programs are slated to execute within unprecedented fielding timelines. These unprecedented fielding timelines, coupled with complex MDO test scenarios, require ATEC and the subordinate organizations to fundamentally re-architecture our foundational networks to provide efficient data pipelines for test execution.

Bldg. 7820 TA1

Dodd Road

Bldg. 6770

Use Case 1: Open Air Flight Test.

In order to expand the flight envelope of the FLRAA and its suite of systems, open air flight test must be performed in both DT and OT scenarios. Due to the extended operational range of these FVL assets, testing will be conducted with operational flight distances greater than ever before tested in ATEC. To effectively capture and evaluate performance in these flight conditions, an extensive network extension with network backhaul provisions must be created. This network will not only be critical to transport at these extended ranges but must also be thick enough to handle the large amounts of data produced by these assets. These network interfaces must also be enabled to translate about subordinate organizations, stakeholders, and OEM partners in order to provide data access that is critical for the expedited fielding timelines.

Concept of Operations:

a. Overview

1) The FVL ecosystem will be equipped with endurance ranges unlike ATEC has ever seen before. In order to effectively test these systems in operationally realistic scenarios, long haul networks with expeditionary nodes should be considered.

b. Functions Performed:

1) Expand the flight envelope of the FLRAA, FARA aircraft.

2) Evaluate interoperability and communication links between the FVL ecosystem in open air environment.

3) Integrate DT/OT/AEC/OEM partners for streamlined data products and test execution. The ultimate goal is to combine DT/OT and minimize redundant test efforts to expedite fielding.

4) Data collection and analysis tools to support post run system performance assessment.

c. Conditions:

1) Open air flight

d. Performance Parameters:

1) All network parameters have not been fully materialized due to lack of specifications from FVL ecosystem; however, initial descriptions indicate that the FVL ecosystem (when considering the LE variants) could have an operational profile upwards of 8,000KM.

e. Rationale:

1) The purpose of this scenario is to evaluate the FVL ecosystem in an open-air flight test environment.

f. Example Use Case Details:

1) Two FLRAA a/c in formation evaluating intercommunication throughout flight while expanding the flight envelope of the aircraft.

2) FLRAA aircraft equipped with LE platforms and evaluating the A/C performance and handling with payload and launch of payload.

3) 2 FTUAS operating in the local area with 2 LE equipped FLRAA A/C.

Intercommunication between assets will be evaluated while expanding the flight envelope.

g. Data Products:

1) Aircraft bus data (ground truth of aircraft status and location to include time synced aircraft configuration parsed into man-readable files).

2) Through-sight video with embedded metadata to include weapons camera for engagement analysis.

3) Parsed communication data (internal (Digital Intercommunication System (DICS)) and external (e.g., voice radio, tactical data links, command, and control situation awareness messages)).

4) Time coded over-the-shoulder video of multifunction display screens and pilot interactions with controls.

5) Parsed automated aircraft health (maintenance) messages.

6) Parsed logged state-of-system changes (e.g., detection, detection to tracking, tracking to launch, etc.).

7) Through-sight video with embedded metadata to include weapons camera for engagement analysis.

8) Parsed time synced logs of threat system configuration.

9) Ground truth location.

h. Limitations Of Current Test Approach:

1) Bandwidth (Currently limited to 20MB on a/c 40 MB on the ground)

2) Current antennas require line-of-sight (LOS). Long haul capability is a must.

3) Range: currently capable of 100-150miles. Expeditionary extension of the current TM network

4) Pipes for transport of data to the cloud at post test. Current 1Gb pipe, not capable of transporting large data size 10G near-mid-term requirement - 40G long term requirement with AI requiring larger amounts of data sets to inform and train off the data. Bandwidth will likely be a critical breaking point for in the future. AI has a need for speed, both for from a processing perspective and feeding the data model.

5) Edge processing capability to parse the data into manageable sized to push through the pipes (bell forecast 2-3TB files off aircraft)

6) OEM network must be provided.

7) Bi-directional TM extension.

8) Latency for the long-haul networks? What do we need? Where are we currently?

i. Needed Products:

1) 40G network bandwidth

2) Edge processing onboard instrumentation

3) External network connectivity for stakeholders

4) Last mile expeditionary connectivity

5) Expeditionary infrastructure will not be comprised on one single solution, it will be a compilation of complimentary solutions that enable the overall transport.

Use Case 2: Multi-Domain Operations Live, Virtual, Constructive Deep Air Assault.

Traditional open-air DT/OT will be insufficient for capturing and evaluating the FVL ecosystem’s ability to operate within the MDO mission space. A combination of LVC and live assets must be considered. For the purposes of this scenario, we will consider a formation flight of 4 FLRAA, equipped with LE, conducting an Air assault mission, cross flock with indirect fires. Supported by unmanned and manned assets. (AF or UAS counterpart) with ground forces interacting in the mission space.

Figure 4. Multi-Domain Operations Battlefield Scenario

Figure 5. Simulated Assets Connectivity

Figure 6. Concept of Operations for Simulated Assets

1) The FVL ecosystem will be equipped with endurance ranges unlike ATEC has ever seen before. In order to effectively test these systems in operationally realistic scenarios with the full gamut of ecosystem assets, LVC must be considered.

2) Stimulate pilot response through threat injection on the A/C displays.

3) Pilot responds to the threat by directing LE launch/ground force to eliminate the target.

4) Observe the TTP response for the threat injection.

b. Functions Performed:

1) Expand the flight envelope of the FLRAA aircraft and intercommunication with operationally realistic battlefield scenario.

2) Evaluate interoperability and communication links between the FVL ecosystem suite through LVC.

3) Integrate DT/OT/AEC/OEM partners for streamlined data products and test execution. Ultimate goal to combine DT/OT and minimize redundant test efforts to expedite fielding.

4) Data collection and analysis tools to support post run system performance assessment.

c. Conditions:

1) Open air flight test coupled with LVC assets.

d. Performance Parameters:

1) All network parameters have not be fully materialized due to lack of specifications from FVL ecosystem; however, initial descriptions indicate that the FVL ecosystem (when considering the LE variants) could have an operational profile upwards of 8,000KM.

e. Rationale:

1) The purpose of this scenario is to evaluate the FVL ecosystem in an open-air flight test environment.

f. Example Use Case Details:

1) Two live FLRAA a/c equipped with LE payloads.

2) Two LVC FLRAA a/c equipped with LE payloads.

3) Two live legacy a/c equipped with LE payloads.

4) Two LVC legacy a/c equipped with LE payloads.

5) Live and LVC FTUAS.

6) Interactive ground force support (see other UCs).

7) Interoperability with other US force support.

g. Data Products

1) Aircraft bus data (ground truth of aircraft status and location to include time synced aircraft configuration parsed into man-readable files).

2) Through-sight video with embedded metadata to include weapons camera for engagement analysis.

3) Parsed communication data (internal (Digital Intercommunication System

(DICS)) and external (e.g., voice radio, tactical data links, command, and control situation awareness messages)).

4) Time coded over-the-shoulder video of multifunction display screens and pilot interactions with controls.

5) Parsed automated aircraft health (maintenance) messages. For threat systems the four data categories are the following:

6) Parsed logged state-of-system changes (e.g., detection, detection to tracking, tracking to launch, etc.).

7) Through-sight video with embedded metadata to include weapons camera for engagement analysis.

8) Parsed time synced logs of threat system configuration.

9) Ground truth location.

h. Limitations Of Current Test Approach:

1) Bandwidth

2) Network Backbone to enable cross org connections.

3) Integration software to enable cross org nodes (this ties the LVC components together).

4) AFSim connection.

5) Lack of Expeditionary connections.

6) Multiple Classification levels for network.

7) Cybersecurity.

8) Bidirectional link.

9) Recorders that filter down to the parameter level and TM (COP manipulated by the user per test scenario).

i. Needed Measurement Products:

1) 40G network bandwidth.

2) Edge processing onboard instrumentation.

3) External network connectivity for stakeholders.

4) Last mile expeditionary connectivity.

5) Expeditionary infrastructure will not be comprised on one single solution, it will be a compilation of complimentary solutions that enable the overall transport.

Use Case 3: Uncrewed Aircraft Systems (UAS) Swarm.

UAS Swarms will be a critical part of the modern battlefield to overload and overtake the enemy. Current networks do not have the bandwidth to support the DT/OT space for evaluation of the swarm technology.

1) For this scenario we will consider a UAS swarm of 200 being launched from a base of operations and conducting reconnaissance about an area. The effectiveness of their intercommunications, ability to recon an air, and engage on a threat will be evaluated.

b. Functions Performed:

1) UAS swarm intercommunication with operationally realistic battlefield scenario.

2) Evaluate interoperability and communication links between the FVL ecosystem suite and UAS.

3) Integrate DT/OT/AEC/OEM partners for streamlined data products and test execution. Ultimate goal to combine DT/OT and minimize redundant test efforts to expedite fielding.

4) Data collection and analysis tools to support post run system performance assessment.

c. Conditions:

1) Open air flight test.

d. Performance Parameters:

1) All network parameters have not be fully materialized due to lack of specifications from FVL ecosystem.

e. Rationale:

1) The purpose of this scenario is to evaluate a UAS swarm in an open-air flight test environment.

f. Example Use Case Details:

1) UAS swarm of up to 200 assets

2) RF network mesh to support the swarm and transmit TSPI back to operating base.

g. Data Products:

1) Aircraft bus data (ground truth of aircraft status and location to include time synced aircraft configuration parsed into man-readable files).

2) Through-sight video with embedded metadata to include weapons camera for engagement analysis.

3) Parsed communication data (internal (Digital Intercommunication System (DICS)) and external (e.g., voice radio, tactical data links, command, and control situation awareness messages)).

4) Time coded over-the-shoulder video of multifunction display screens and pilot interactions with controls.

5) Parsed automated aircraft health (maintenance) messages. For threat systems the four data categories are the following:

6) Parsed logged state-of-system changes (e.g., detection, detection to tracking, tracking to launch, etc.).

7) Through-sight video with embedded metadata to include weapons camera for engagement analysis.

8) Parsed time synced logs of threat system configuration.

9) Ground truth location.

h. Limitations Of Current Test Approach:

1) Bandwidth.

2) Real time RF network mesh to support a large swarm and get the TSPI back home. Addressing the internet of things problem. Reg hurdles to overcome.

3) Compilation of this could create a spectrum problem. Need to explore UWB solution for this scenario?

4) We have to utilize spectrum efficient technologies to support these scenarios.

5) Cybersecurity.

i. Needed Measurement Products:

1) 40G network bandwidth.

2) Edge processing onboard instrumentation.

3) External network connectivity for stakeholders.

4) Last mile expeditionary connectivity.

5) RF Mesh network.

Use Case 4: Assured Position Navigation and Timing (APNT).

Due to the sensitive nature and operational complexity of providing an operational relevant APNT environment, testing must be conducted in a controlled anechoic chamber (provides radio frequency [RF] isolation) with appropriate simulated live-sky translation and threat injection. A realistic and immersive synthetic Global Navigation Satellite System (GNSS) distributed test environment is an essential test technology for determining the impact of GPS/GNSS degradation and denial on APNT Multi-Domain Operations (MDO). Real-world GNSS constellations consist of many individual satellites in orbit. Each satellite transmits a RF signal towards the Earth. A typical GNSS receiver has one antenna which collects all GNSS signals available and combines it into a single RF signal which is used to derive a position solution. Many GNSS receivers can be tricked into tracking an artificial signal thus modifying the derived position solution. To combat this currently exploited vulnerability, engineers designed a GNSS antenna called a controlled reception pattern antenna (CRPA). A CRPA antenna design uses combined RF output from multiple single antennas arranged in a phased array to determine which direction the RF signal is being transmitted from. Therefore, to test CRPA’s, a GNSS simulation needs to have the capability to emulate an RF signal transmitted from each GNSS satellite transmitted from realistic directions (usually above the test item) inside the E3 anechoic chamber. This capability will also include testing of GNSS systems installed on tactical FVL platforms (and sub-components) to test anti-jam antenna (CRPA) technology, as well as encrypted GNSS signals such as P(Y) code and Military-code (M-code) signals. All APNT sensors (GNSS, INS, etc.) on the aircraft will need to be stimulated with this distributed test capability so that the test item thinks it is flying a mission in a multi-domain environment. This solution will provide critical test data used to determine if currently deployed aircraft systems detect a jamming event, how long it takes to recognize this jamming event, did the aircraft systems respond to the jamming event correctly, etc. Furthermore, this solution will generate data on potential ripple effects during a GPS jamming event on the larger battle space through MDO testing.

Concept of Operations:

1) The rotary-wing platform is de-fueled and placed inside the anechoic chamber.

2) Auxiliary power is provided to the aircraft.

3) Instrumentation is installed to monitor relevant aircraft systems and components.

4) Connection to the JMN node for distributed testing is provided through the aircraft data buss.

5) The E3 anechoic facility will develop a flight profile for the GNSS and INS simulator.

6) Test environment equipment will be configured for the appropriate E3 tests performed (electromagnetic vulnerability - EMV, GPS Denial, other RF signals/threats, RF Cyber).

7) Place aircraft in virtual flight.

b. Functions Performed

1) Verify CRPA on the aircraft is operational and tracking the simulated GNSS/GPS signals. This will include P(Y) code and Military-code (M-code) signals.

2) Perform EMV, GPS Denial, other RF signals/threats, RF Cyber as applicable.

3) Monitor the ripple effects of potential aircraft vulnerabilities on other theater

MDO through the JMN connection.

c. Conditions

1) Aircraft in simulated flight with stimulation from GNSS/GPS and INS simulator.

2) GPS Denial, other RF signals/threats, and RF Cyber all must be validated.

3) Aircraft in MDO environment through the JMN connection.

d. Performance Parameters

1) Maintain GNSS/GPS lock in all threat environments.

2) Maintain aircraft functionality in EMV, GPS Denial, other RF signals/threats, RF

Cyber environments.

e. Rationale

1) The purpose of the EMV, GPS Denial, other RF signals/threats, RF Cyber environments tests are to verify aircraft systems performance in potential hostile RF environments from validated threats.

2) Furthermore, effects on other systems in the other operational domains will be assessed through the JMN connection.

f. Example Use Case Details

1) Verify aircraft ability to navigate in GPS denied environments from external threat jammer/spoofing equipment.

2) Verify aircraft ability to navigate in the presence of an RF Cyber-attack.

3) Verify aircraft ability to navigate in the presence of other enemy RF threats.

4) Monitor critical test data used to determine if currently deployed aircraft systems detect a jamming event, how long it takes to recognize this jamming event, did the aircraft systems respond to the jamming event correctly, etc.

5) Generate data on potential ripple effects during a GPS jamming event on the larger battle space through MDO testing.

g. Limitations Of Current Test Approach

1) The Military Systems Electromagnetic Tests Support (MSETS) Facility anechoic chamber is still yet to be constructed but expected in the next couple years.

2) The GNSS/GPS Simulator will need to be purchased and installed in MSETS and must have limit the CRPA perceived AoA error from the simulator. This may be particularly challenging for extended test runs where simulating the movement of the GNSS satellites across the sky and making sure the AoA is correct for the duration.

h. Needed Measurement Products

1) Measurement of profile simulated in each spectrum with enough fidelity to verify profile.

2) SUT data collection.

3) Other ground truth data measurement.

4) Post run performance assessment tools.

5) Fiber backbone for distributed connectivity (both classified and unclassified).

White Sands Test Center (WSTC)

Use Case #1: Wireless Test Network (WTN) infrastructure.

Operational Requirement:

WSTC Wireless Test Network (WTN) infrastructure (aka WTN towers) needs to provide Test Support Network (TSN) access to instrumentation capabilities/assets within the range.

The WTN towers supported WSTC instrumentation commodities such as Telemetry, Optics, and Communications groups. In addition, these towers were heavily utilized during the Network Integration Evaluation (NIE) events to support wireless instrumentation and data collection for ground vehicles and the ATEC Wireless

Integrated Network (AWIN) infrastructure. The AWIN infrastructure was used to distribute data collection between ATEC and (Brigade Modernization Combat) BMC.

Current Network Infrastructure:

Existing network and power infrastructure are present at the tower locations. WTN radio towers are part of the TSN infrastructure.

Current WTN towers integrated Fortress ES2440 radios into the Test support Network (TSN). This effort was finalized in 2012. This is no longer used due to low bandwidth capacity and end of life security support which impacts the TSN authority to Operate

(ATO).

WTN Location Requirements:

Data Requirements:

• Provide 99.99% coverage.

• Minimal loss roaming/Fast hand-off.

• Fully integrated into the test support network (TSN).

• 300Mbps – 500Mbps Upload speeds for real-time data.

• 600Mbps to 1Gbps speed for dump data (raw data transport).

• Latency Requirements for KTM – 50ms - 150ms.

Operational/Safety Requirements:

• Cybersecurity.

Future Plans:

• WTN towers are planned to support MDO events across the range with network access at remote locations.

• WTN towers expect to support upcoming programs with mobility scenarios.

• WTN towers will support higher bandwidth assets such as the Optics.

capability Advanced Range. Tracking and Imaging System (ARTIS). Optics ARTIS per single system: 300-400Mbps.

• WTN towers expect to support the Passive/Active Tracking Radar (Dome) effort.

• WTN towers expect to support Eight KTMs converted to Fixed Domes - Optics KTM One unit: 105 – 210Mbps @ 1080p.

• WTN towers can support various programs and instrumentation enclaves as soon as tower network access becomes operational.

• Autonomous Optical Tracker – 4kp – 4 units per cell.

• Edge processing programs.

Use Case #2: Off-range to Range Control.

Alamo Peak – Telemetry Station Critical Path

Operational Requirement:

WSTC Telemetry J67 and J167 antennas require to continuously provide telemetry (TM) data into the Test Support Network (TSN) to support mission evaluation events.

There is network infrastructure and power at this location.

The location for the telemetry equipment is Alamo Peak, an off-range location, Bureau of Land Management (BLM), situated south of Cloudcroft, NM. This location is owned by Lincoln Parks and Recreation, therefore WSTC is not allowed to trench fiber. The Alamo Peak Aeronautical Telemetry (ATM) is used to continuously remote and manage two TM stations, J67 and J167.

Currently, network access is based on wireless Point to Point (PtP) Cambium radios that link into a TSN node at Building 335. B335 is a critical location that utilizes remote command and control to all fixed ATM locations, Alamo Peak, Salinas Peak, and Dry Site. It is critical, that B335 maintains direct connectivity to Alamo Peak.

In addition, at maximum mission support operations, TM aggregates up to three ATM mobile trackers to Alamo Peak (two ATM fixed trackers), and then transports all data to B335.

Data Requirements:

• Provide 99.99% coverage.

• Fully integrated into the test support network (TSN).

• 80Mbps per station (Six downlink channels at 20M each x 2 ATM’s) - 240Mbps per stream.

• Aggregated data Alamo Pk to B335 from 5 ATMs [J67, J167, 3 mobiles] (max): 400-600Mbps.

• GPS – 8Mbps.

• Latency Requirements for ATM ACU – 50ms - 150ms.

• Cybersecurity.

• Surveillance Cameras - 5 cameras – 40 Mbps.

• RF/IP – TBD - Dependent on future spectrum selloff. This will increase network data needs considerably.

• RTSP Cameras: Current discussion about Blue Eye support for video safety/awareness on Range.

• Passive/Active Tracking Radar (Dome) – 7 CSAS nodes across Range (max): 1.680Gbps.

o 12 downlinks (20Mbps per channel): One node - 240Mbps.

o 12 downlinks (20Mbps per channel) x 7 systems = 1.680Gbps aggregate.

o CSAS effort will have fixed stations across WSTC Range.

o Still under discussion what nodes will not have Fiber presence.

Use Case #3: “BLANK” Off-range Last Mile High-Capacity throughput.

LC94 / Lee’s Ranch / McGregor Base Camp / WSTC cantonment – Communications data links

(a) Launch Complex 94 (LC94) / Lee’s Ranch

(b) McGregor Base Camp

(c) WSTC Cantonment area & Impact

Operational Requirements:

WSTC Communications group needs provide wireless TSN network access extension to off-range remote test locations such as a) Launch complex 94 (LC-94), this is 22.5 miles away from WSTC contentment area wireless network link. b) McGregor Base Camp, 22.4 miles away from WSTC contentment area. c) WSTC Contentment & impact zone.

Instrumentation assets are required to transport both real-time data and post-mission data collection to Range Control B335.

The setting for these communication network extension links is located at off-range locations such as a) LC94 and b) McGregor Base Camp and c) within WSTC contentment area. Both off-range locations are utilized to support TSN access to mission events that require test data collection.

These remote locations support different mission activity events composed of numerous test instrumentation assets as a campus network model. Instrumentation assets are Optics, radar, telemetry, GPS, and remote communications.

Existing power infrastructure is present at this location.

a) LC-94 has power infrastructure. No TSN fiber.

Lee’s Ranch Does not have power infrastructure.

b) McGregor Base Camp has power infrastructure. No TSN fiber.

Setup locations does not have power infrastructure.

C) All setup sites except for Phil and School does not have power infrastructure.

All setup sites do not have TSN fiber.

• Provide 99.99% coverage.

• Fully integrated into the test support network (TSN).

• Optics KTM: 70 – 105Mbps @ 720p.

• Optics KTM runs low network bandwidth (1Gbps with current Cisco 3750).

• Aggregated up-range KTM:

• Aggregated KTM at link Baby Elephant Mtn – McGregor BC:

• TM: Aggregated to B335 from 5 ATMs (max): 400-600Mbps.

• GPS – 10Mbps.

• Surveillance Cameras: @ 15Mbps single video.

• Optics KTM: 110 – 205Mbps @ 1080p (units limited to 10Gbps with Cisco 3900).

• Cybersecurity.

• Optics KTM: 4kp.

• ARTIS: KTM’s will be replaced by ARTIS optical systems.

• ARTIS Fly-Out systems:

o Real-time streaming – 122Mbps.

o Post mission quick look – 120Mbps.

o Post mission upload uncompressed – 26927Mbps.

o File size (uncompressed) – 1010GB.

o Post mission upload compresses (10:1) 2693Mbps o File size (compressed) – 101GB.

• 4 x ARTIS Fly-Out.

• ARTIS Close-in Instrument system:

o Real-time streaming – 82Mbps.

o Post mission quick look – 80 Mbps.

o Post mission upload uncompressed – 22077Mbps.

o File size (uncompressed) – 828GB.

o Post mission upload compresses (10:1) 2208Mbps o File size (compressed) – 83GB.

• 6 x ARTIS Close-in Instrument system will be utilized.

• Eight KTMs converted to Fixed Domes utilizing the fiber.

Use Case #4: HELSTF remote sites coverage.

HELSTF – Directed Energy / Electronic Warfare Ground testing.

WSTC needs to provide TSN network access to remote test locations at HELSTF. This includes upcoming mission event: FY25 “Blank 2.”

Description:

HELSTF Campus is used to test DE systems at various sites due to distance/power/mobility requirements for the system under test.

Current Network Infrastructure:

The network and power infrastructure varies by location, as stated above in the chart throughout HELSTF campus.

• Provide 99.99% network coverage.

• Fully integrated into the test support network (TSN).

• Optics KTM: 70 – 105Mbps @ 720p limited by 1Gbps to the edge network bandwidth (Cisco 3750).

• 4x KTM – 280Mbps – 420Mbps @720p.

• *Optics KTM runs low network bandwidth (1Gbps with current Cisco 3750 until new Cisco 3900 is received).

• Communications van: VoIP + Quintron + video cameras – 64Mbps – 80Mbps.

• MT van: Quintron – 2 - 4Mbps.

• GPS Marshall – 8Mbps.

• RADA radar – 50Mbps – 80Mbps.

• Radar (FPS-16) - 40Mbps – 80Mbps.

• Latency Requirements for KTM real time – 50ms – 100ms.

• Other instrumentation data.

• Provide test personnel with communications LMR-Situational Awareness (Non-TSN).

• Surveillance Cameras: @ 15Mbps single video x6 cameras – 90Mbps.

• ARTIS: KTM’s will be replaced by ARTIS optical systems.

• ARTIS Close-in Instrument system:

o Real-time streaming – 82Mbps.

o Post mission quick look – 80 Mbps.

o Post mission upload uncompressed – 22077Mbps.

o File size (uncompressed) – 828GB.

o Post mission upload compresses (10:1) 2208Mbps.

o File size (compressed) – 83GB.

• 2 x ARTIS Close-in Instrument system will be utilized.

• Free Space Optics – TBD data rates.

• Autonomous Optical Tracker – 4kp – 4 units per cell.

Use Case #5: Salinas Peak Redundancy

Salinas Peak - Integrated Directed Energy Architecture (IDEA) and Telemetry

Tracker J10

WSTC needs to provide TSN network access redundancy to Salinas Peak.

Salinas Peak is a critical site for WSTC operations and communications. Salinas Peak houses a fixed Telemetry tracker J10, a communication building in charge of distributing network access, a meteorology tower, Land Mobile Remote (LMR) main tower, and a Directed Energy asset. Salinas Peak is considered a major distribution site with a fiber bandwidth capacity of 10Gbps. Salinas Peak fiber connects directly to Rob site, a core site on the WSTC backbone (100Gbps). Salinas Peak is heavily used for numerous mission events; however, it keeps losing network connectivity due to bad weather and power loss at Rob site. The importance of this site requires network access redundancy to avoid network failures during a mission.

Existing power infrastructure is present at this location.

• Provide 99.99% wireless coverage.

• Fully integrated into the test support network (TSN).

• TM tracker – 80Mbps per station (Six downlink channels at 20M each x 2 ATM’s) - 240Mbps per stream.

• TM tracker remote C2: 10-20Mbps.

• Optics KTM: 70 – 105Mbps @ 720p.

• Optics KTM runs low network bandwidth (1Gbps with current Cisco 3750).

• Directed Energy asset C2: 200 – 300Mbps.

• GPS – 8Mbps.

• Latency Requirements for TM – 50ms - 150ms.

• Latency Requirements for DE asset – 50ms - 100ms.

• LMR tower: RF.

• Verizon tower: RF.

• Surveillance Cameras: @ 15Mbps single video x6 cameras – 90Mbps.

• ARTIS.

• RF/IP – TBD - Dependent on future spectrum selloff.