networked telemetry vision and challenges– networked telemetry is a potential game changer in the...

Networked Telemetry

Vision and Challenges

Paul Waters412 TENG Tech Director

[email protected]/17/2019 1

2019 Test Instrumentation Workshop

DISTRIBUTION STATEMENT A. Approved for public release; Distribution is unlimited 412TW-PA-19262

mailto:[email protected]

Overview• Objective

– Discuss where the 412 TW is going with respect to enhancing our real-time monitoring and analysis based around networking advances in instrumentation, telemetry, and ground infrastructure

• Audience participation is encouraged– NOTE: Including a user’s perspective on iNET implementation that

IS different than iNET program vision

• Outline– Drivers– Envisioned End-State– Challenges Remaining

• BLUF– Networked telemetry is a potential game changer in the real-time

analysis area– BUT there is a lot of work remaining to make it operational

5/17/2019 2DISTRIBUTION STATEMENT A. Approved for public release; Distribution is unlimited 412TW-PA-19262

DRIVERS


Driving Forces• Customer Requirements

– The customer base is changing and the requirements from the customer are changing

• Technology Changes– Key technologies are emerging that will have significant impact

on the systems we test and how we test them

• Industrial Base– T&E Infrastructure is largely Commercial Off the Shelf

technologies that are integrated to create T&E capabilities

• Obsolescence– T&E systems are getting old and in many cases unsustainable


Driving Forces - Customers• Systems Under Test

– No longer “just” testing aircraft or weapons• Flight Sciences is still critical, but a reduced volume of testing• Testing flying software

– Types of systems is more widely varying• Autonomy, Hypersonics, C4ISR, Sensors, New and Legacy Platforms

– Highly sophisticated and integrated systems• Requiring a more realistic environment• More difficult to replicate test conditions exactly

• Reasons for Real-Time support are changing– Less Flight Sciences (Safety of Flight)– More Mission Systems (Test Quality/Efficiency) testing

• Increased need for mission control• Customer Requirements

– More data required for T&E• Aircraft are generating TBs of data per flight

– Decision makers wanting test data to support decisions• Faster turn of decision quality information


Driving Forces - Technology• Technology Changes

– Networking– Data Analytics– Miniaturization– Spectrum limitations

• Industrial Base– Heavily reliant on commercial technologies and

standards• Challenges and opportunities to leverage new industries

• Obsolescence– Much of our Range and Instrumentation systems are

obsolete and nearing unsustainability• Driving a timeline that is not in sync with programmatics


ENVISIONED END STATE


Envisioned End State

5/17/2019 8

Select Capabilities from the “Buffet” to make a Mission “Meal”

• Meet unique Requirements

• Integrate LVC

Configurable

• Quick change configurations

• Maintain reqdcontrols

Agile • Near real-time analyses

• Connected to Team

Fast

• Low O&S costs

• High Reliability

Effective

”Any Data, Any Time, Any Where”


CAFE Specifics• Configurable

– Reconfigure Range & Airborne Instrumentation to meet unique requirements

• Fixed core augmented by mobile/variable extensions• Modular architecture that enables adding and subtracting

modules based on mission requirements– Integrate Facilities, Ranges, Labs, SILs

• Provide required test environment• Enable collaboration with system under test experts

• Agile– Change configurations without years in advance planning

• IA approvals; Security controls; • Pre-approved airspace & landspace

– Maintain Range control (safety, test environment, soft and hard mission termination)


CAFE Specifics• Fast

– Transform data into information in real and near real-time• Higher quality real-time data (no dropouts), faster offload of data

to data centers• Integrating previous data, simulations and real-time to support

evaluations• Able to mine the data for help resolving system anomalies

• Effective (Cost and Mission)– Cost effective to operate and sustain

• Need to be able optimize staffing• Equipment needs to be open architecture and integrated through

RCC standards• Ranges not required to maintain depot level repair capabilities

– Reliability – Test systems can not be “system under test”• Systems work consistently, can be repaired quickly• Test systems performance proven and documented


How to Reach Envisioned End State• Key Enabler (Packetized Data & Network TM)

– Collect data as a information packet– Move data as a packet– Process data as a packet– Display data as a packet

• Similar in concept to implementation of smartphones

• Handle data as data– Video, Audio, Data are all processed as packets

• Minimize proliferation of specific hardware system• Label data at source

– Metadata for processing and analytics– Security labels for Multi-level security– Timing labels for time alignment of data sources


Ground Station

Control Room

Range Ground Network

Serial Streaming Telemetry (PCM)

TEST ARTICLE NETWORKED INSTRUMENTATION- Replacing Obsolete CAIS Instrumentation Architecture with

Network Architecture- Utilizing 10 GigE Backbone and 1 GigE Legs to increase

capacity and reduce wiring

Network Telemetry on VLAN

Range Ground Network

Network TM Upgrades

TELEMETRY- Upgraded (412 TW) / Upgrading

(SW Ranges) to L/S/C Band capable ground antennas

- Upgrading Aircraft and Ground radios to support all of the ARTM waveforms (PCM, SOQPSK, CPM)

- Added/(ing) hooks to support future bi-directional command and control of airborne instrumentation system

RANGE GROUND NETWORKS- Migrating from ATM based network to IP

based range network- Replacing long-haul microwaves with fiber- Connecting to DREN for distributed test

operations at Eglin, WSMR, and others- Migrating voice, video and data to

packetized data

MISSION CONTROL ROOMS- Upgrading the MCR architecture to

a modular design that enables future flexibility by adding/swapping modules

- Minimizes specialized hardware dependencies

- Supports distributed operations from ground up

- Integrates simulations and stimulation into the MCR

Leveraging iNET, I&M and SRFDISTRIBUTION STATEMENT A.

Approved for public release; Distribution is unlimited 412TW-PA-19262

Mapping Capability to End-StateConfigurable Agile Fast Effective

Inve

stm

ent P

roje

ct

Capability Delivered

Rec

onfig

urab

le R

ange

Rec

onfig

urab

le

inst

rum

enta

tion

Inco

rpor

ate

LVC

Link

to S

yste

m u

nder

Tes

t Ex

perts

Cha

nge

Con

figur

atio

ns

Ran

ge C

ontro

l

Nea

r Rea

l tim

e da

ta

corre

ctio

n

Nea

r Rea

l tim

e In

tegr

atio

n of

prev

ious

dat

a

Link

real

-tim

e si

mul

atio

ns

Nea

r Rea

l tim

e D

ata

Arch

ive

Min

ing

Opt

imiz

e st

aff r

equi

rem

ents

Ope

n ar

chite

ctur

e an

d st

anda

rds

base

d

Plan

for D

epot

leve

l m

aint

enan

ce a

nd s

uppo

rt

Rel

iabi

lity

–sy

stem

wor

ks

cons

iste

ntly

Prov

en a

nd d

ocum

ente

d pe

rform

ance

NTI

P

Robust TM Network

Des

ign

Cha

ract

eris

tics

for a

ll Pr

ojec

ts

X X

Instr0 Config Load Change X X X X

Change TM Frequenciies X X X

TM Backfill X

User Req. Data Download X X

MM

CR

U

Modular Control Rooms X X X X X

Mutli-ship Support X

Integrated Post Test Data X X

Integrated Simulations X X

CAN

IS

& AA

IS Networked Instro for Aircraft X X

Networked Telemetry X X X X


Network TM End-State• Safety of Test / Safety of Flight

– Data will continue to be transmitted using Serial Streaming TM (SST) - legacy

• ~ 25 percent of spectrum requirements• Mission Systems and Test Efficiency Data

– Core displays will also be sent SST– Backup displays will not be transmitted until

needed • Data on demand

• Dropouts in Data– Will be automatically transmitted to allow for

more rigorous analyses5/17/2019 14DISTRIBUTION STATEMENT A. Approved for public release;

Distribution is unlimited 412TW-PA-19262

Network TM Capability Plan• Challenge

– 70+ aircraft that need to be upgraded– New customers and Weapons systems are difficult to

migrate (size, management)

• Phased Capability Deployment– Utilizing NTIP

to build on iNETdevelopments

5/17/2019 15

Robust Bi-Directional NetworkConfiguration of Network Components

DISTRIBUTION STATEMENT A. Approved for public release;


Timelines for Capability

• IOC – operational capability for single aircraft• FOC – operational capability for Edwards Fleet

5/17/2019 16

FY18 FY19 FY20 FY21 FY22 FY23 FY24 FY25 FY26 FY27TMnS SUT HW/SW components

Robust Bi-Directional NetworkIn-Flight Configuration ChangesRT TM BackfillUser Requested Data DownloadNetwork-based Distributed Testing

NTIPiNET

SRFSRF FOC

CANIS AAISCANISMMCRU MMCRU

Network TM IOC

Network TM FOC

SRF

iNET, SRF, CANIS

Configuration of Network Components

iNET, SRF, CANIS, NTIP

NTIP

NTIP

NTIP, MMCRU

MMCRU

CHALLENGES


Challenge Overview• Programmatics

– iNET Incompletion– Complexity– Test Asset Availability

• Technical– Technical Complexity– Technology Availability

• Sustainment– Workforce– Funding

• Partnerships5/17/2019 18DISTRIBUTION STATEMENT A. Approved for public release;


Programmatic Challenges• iNET Incompletion

– iNET is not delivering an operational capability• Proof of Concepts have demonstrated potential capabilities, BUT

work remains• Validating the Robustness and Reliability of the Network

– Operating across multiple ranges– Maneuvering test article– Operator capability to maintain C-Band tracking lock

• No software toolset to configure instrumentation and network components

• Actions – Collaborate with Navy on Western Range

implementation• Conducting Prof/Test flights to validate network

performance• Updating tracking tools to help with maintaining lock

– Work with Navy and TRMC to add configuration toolset to existing System Manager

• Backup – Develop a external configuration toolset5/17/2019 19DISTRIBUTION STATEMENT A. Approved for public release;


NTIP PM ViewPhased Approach

• Phase 1: 2-Way Telemetry Point-to-Point Link– Scenarios based development– Operational Proof-of-Concept for deployment

• Phase 2: Core Capabilities Build– Define and prioritize core mission capabilities – Develop HW gap analysis for core capabilities– Develop CONOPS for mission support around capabilities– Develop SW gap analysis for capabilities

• Phase 3: Post Production Sustain and Develop– S/W Sustain

• Bug fixes / New Capabilities• Contract Management

– H/W Sustain / Development• New Equip. and Capabilities • RCC Standards / Certification Testing

20

Some of This

A Little of That

None at All

CTEIP Produced:


Programmatic Challenges• Complexity

– Relying on capabilities being successfully integrated from 5 different programs and 3 different funding sources

– 4 separate PMs required to deliver Network TM capabilities as well as other related capabilities

– Coordinating with Eglin to have common solutions• Different missions are driving different requirements

• Actions– Closely coordinating all related developments through a

Network Telemetry Data Integration working group• Meets bi-weekly to discuss plans, status, and issues• Resolves programmatic and technical issues

– Meeting regularly and coordinating jointly on all requirements documents


Programmatic Challenges• Test Asset Availability

– Requires integrating with every test program at Edwards to gain access to aircraft to upgrade the instrumentation systems

– Programs are also upgrading their test assets• Actions

– Coordinating with the Programs to encourage them to follow a similar design architecture

• Offering funding as needed to encourage architecture compliance


Technical Challenges• Technical Complexity

1. Systems are not all network enabled• Classic “orange wire” sensors are not replaceable• Weapons may not upgrade in the foreseeable future

2. Timing and quality of service are paramount• Current Requirements are for 500ms latency maximum and 1ms

difference in timing between systems3. Current Encryption device does not pass network

packets• Also don’t support automated tracking based on QOS

4. Security/Cybersecurity is more difficult• No longer have uni-directional data

5. Standards will have to evolve• iNET standards were developed over last decade and do not

incorporate emerging technologies• Chap 10/11 standards are not optimized for network

access/queries


Technical Challenges• Technical Complexity Actions

1. Utilizing other technologies (e.g., ethernet to serial) to control devices that are not currently network enabled and converting the data to network packets in acquisition units

2. Performing detailed timing analyses and conducting lab testing to document time performance

3. Working with to develop a network encryption device to reduce ground infrastructure requirements

• Unfunded request to AF and to DoD 4. Cybersecurity/Security is being worked as part of the

implementation design• Requiring more complex packages and more packages as we navigate the

data flow from the aircraft to the classified control rooms and back • Increasing the costs

5. Standards updates will be required• Working to implement the existing standards and identify gaps and/or

inconsistencies • RCC TG will be instrumental in updating the standards for iNET and Chap

10 after the fixes are identified


Technical Challenges• Technology Availability

1. Lacking multiple vendors for critical components• TM Radios

2. iNET Radios are not production ready• Radios are still undergoing beta testing• Funding for radios is available now, radios are not

3. Vendors have adopted proprietary networking standards• Most of the key vendors are producing network enabled

components 4. Discovering key component gaps

• Requirement for network encryption device• Enhanced TM antenna tracking for C-Band

5. iNET software is not mature• Link Manager is ~90% complete• System Manager is ~50% complete• Configuration tools for network components does not exist


Technical Challenges• Technology Availability Actions

1. Key network radio currently has only a single vendor, but the S&T program is funding a second vendor to produce the iNET radio

2. Testing is being conducted to validate the fixes required based on initial testing.

• Expected completion in Q4 of FY19.• Unknown production availability

3. Most airborne component are now being produced with Ethernet ports and can be controlled with the vendors tools

• Upgrading to TMnS and MDL (iNET developed standards) should only be a firmware upgrade to the hardware

• Hardware will need to be validated prior to use in a instrumentation system design

4. Capability Gaps are not unexpected• I&M programs in place to implement networked TM

– Behind “schedule” and over budget, but not stopping missions• Investments in labs will enable us to resolve and validate solutions

5. Software will be delivered with full rights and documentation• I&M program in place to mature the software

– Insufficient resources to address the MDL configuration tool– Will work with TRMC to address


Sustainment Challenges• Challenges

– Workforce• Requiring new skillsets and certifications for the workforce in the

Range and in Instrumentation– Increase training costs to bring people up to speed– May also require enhancing the software tools to increase the usability

• Will require a new workforce to maintain and enhance the software tools

– Difficult workforce for the government to keep together

– Funding• Difficult to predict sustainment costs due to the lack of maturity of

the systems• Software for the system will be required to be sustained (Link

Manager, System Manager, TM Front End, etc)– Most of these are new sustainment efforts– Coordination among the Ranges has not been accomplished to allow for

collaboration on the sustainment


Sustainment Challenges• Sustainment Actions

– Workforce• In-house training is being developed in conjunction

with the system development to operate and sustain the new systems

• Revising hiring plans to increase the network and software expertise requirements

• Identified a need to develop a integrated training and retention policy that sustains the right expertise

– Funding• POMing for new positions for sustainment positions

and dollars• Coordinating at working level on strategies to share

the sustainment efforts5/17/2019 28DISTRIBUTION STATEMENT A. Approved for public release;


Partnerships• Challenges

– Packetized data and Network Telemetry visions are requiring detailed collaboration

• Forcing a re-evaluation of processes, philosophies, etc in light of a changing mission set

• Requires engagement and a development of partnering beyond what has been done in the past

– Multiple levels required (leadership, management, working level)– Integration of systems and software require documentation of

interfaces and adherence to standards• Standards also need to evolve

– Cybersecurity risks are increased with networked telemetry• Need to engage early with cybersecurity teams to ensure that capabilities

that are delivered are sufficiently secure• Actions

– Collaboration and coordination are happening at multiple levels• Need to define final decision authorities

– Documentation and standards are being developed and coordinated• Multiple standards and standards take years to update

– Cybersecurity leadership is engaged• Collaboration and mission focus need to be maintained


Conclusions• Networked Telemetry, Packetized Data, etc

are coming– The capabilities delivered are essential for the

agility required in the future– They are late to need

• The successful implementation requires unprecedented collaboration across systems, organizations and missions


networked telemetry vision and challenges– networked telemetry is a potential game changer in the...

Documents