test and training enabling architecture tena l.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Test and Training Enabling Architecture (TENA) PowerPoint Presentation
Download Presentation
Test and Training Enabling Architecture (TENA)

Loading in 2 Seconds...

play fullscreen
1 / 28

Test and Training Enabling Architecture (TENA) - PowerPoint PPT Presentation


  • 583 Views
  • Uploaded on

Test and Training Enabling Architecture (TENA). Gene Hudgins TENA Development Lead 4 March 2003. The Foundation for DoD Range Interoperability. Foundation Initiative 2010 Mission.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Test and Training Enabling Architecture (TENA)' - Samuel


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
test and training enabling architecture tena

Test and Training Enabling Architecture (TENA)

Gene Hudgins

TENA Development Lead

4 March 2003

TheFoundationfor DoD Range Interoperability

foundation initiative 2010 mission
Foundation Initiative 2010Mission
  • Enable Interoperability among Range systems, Facilities, Simulations, C4ISR systems in a quick, cost-efficient manner, and
  • Foster Reuse for Range asset utilization and for future developments.

Currently, range systems tend to be non-interoperable, “stove-pipe” systems.

The purpose of TENA is to provide the architecture and the software implementation necessary to:

  • Support the Warfighter (Joint Vision 2010/2020)
  • Enable Simulation-Based Acquisition
  • Foster Test and Training Integration
  • In the long term: SAVE MONEY!

Lay the Foundation for Future Test and Training Range Instrumentation

foundation initiative 2010 project objectives
Foundation Initiative 2010Project Objectives
  • Define a common Architecture for the test/training range community – called “TENA” (Test & Training Enabling Architecture)
    • Define a common Object Model to be used across the ranges
    • Define and build a common Software Middleware that will:
      • Use the object model
      • Enhance interoperability and reuse among the ranges
  • Common understanding of range processes – the Logical Range Concept of Operations
  • Define and prototype common Tools to configure and conduct multi-range, synthetic test events or training exercises
    • Create distributed, synthetic battlespaces with real weapon systems
    • Link multiple ranges together to form a larger, cohesive range
    • Enable testing, assessment, experimentation, and training of weapon system interoperability, C4ISR, and system-of-systems
overall development strategy
TENA was revised based on user feedback and lessons learned from working software prototypes

TENA will be revised in the future based on future prototypes

TENA is based on real-world tests at real ranges

Test & Training Enabling Architecture(TENA)

Prototypes

User Feedback

User Feedback

User Feedback

Prototypes

Prototypes

Prototypes

Prototypes

LessonsLearned

LessonsLearned

LessonsLearned

Prototypes

Overall Development Strategy
driving technical requirements
Interoperability

The characteristic of a suite of independently-developed components, applications, or systems that implies that they can work together, as part of some business process, to achieve the goals defined by a user or users.

Reusability

The characteristic of a given component, application, or system that implies that it can be used in arrangements, configurations, or in system-of-systems beyond those for which it was originally designed.

Composability

The ability to rapidly assemble, initialize, test, and execute a system from members of a pool of reusable, interoperable elements.

Composability can occur at any scale — reusable components can be combined to create an application, reusable applications can be combined to create a system, and reusable systems can be combined to create asystem-of-systems.

Driving Technical Requirements
achieving interoperability reuse and composability
Interoperability requires:

A common architecture

An ability to meaningfully communicate

A common language

A common communication mechanism

A physical connection between the two systems

A common context

A common understanding of the environment

A common understanding of time

A common technical process

Reuse and Composability require the above, plus

Well defined interfaces and functionalityfor the application to be reused

TENA

TENA Object Model (OM)

TENA Middleware

Network, shared memory

TENA Object Model(Environment)

TENA OM, TENA Middleware

TENA Technical Process

Reusable Tools,Repository

Achieving Interoperability, Reuse, and Composability
ways tena middleware can exchange data
Ways TENA Middleware CanExchange Data
  • TENA presents to the range user a unification of several powerful inter-application communication paradigms
    • Publish/Subscribe
      • Similar in effect to HLA, DIS, or other PDU-based communication systems
      • Each application publishes certain types of information (the publication state) which can be subscribed to by any other application
    • Remote Method Invocation
      • Similar to CORBA or Java RMI
      • Each object that is published may have methods that can be remotely invoked by other applications
    • Messages
      • Individual messages that can be sent from one application to one or more other applications
    • Data Streams
      • Native support for audio, video, and telemetry
stateful distributed objects
Stateful Distributed Objects
  • An SDO is a combination of two powerful concepts:
    • a distributed object paradigm (like the one used in CORBA)
    • a distributed publish and subscribe paradigm.
  • Benefits of this combination:
    • A conventional distributed object-oriented system offers no direct support to the user for disseminating data from a single source to multiple destinations.
    • A conventional publish-subscribe system does not provide the abstraction of objects with a set of methods in their interface.
    • Interface to SDOs is a lot simpler and more usable than the combination of interfaces to their underlying technologies.
  • ANY APPLICATION can act as a server of some SDO objects and a client of other objects AT THE SAME TIME
    • TENA is a PEER-TO-PEER Architecture
logical range simple example
Logical RangeSimple Example

TENA specifies an architecture for range resources participating in logical ranges

Radar

TestControl Station

Simulation

Communication Mechanism (Network, Shared Memory, etc.)

logical range simple example11

TENA Application A

TENA Application C

UserApplicationCode

UserApplicationCode

Proxy

Servant

Servant

Servant

Proxy

Servant

Servant

Proxy

TENA Middleware

TENA Middleware

TENA Application B

UserApplicationCode

Proxy

Proxy

Proxy

Proxy

Proxy

TENA Middleware

Logical RangeSimple Example
  • TENA specifies a peer-to-peer architecture for logical ranges
    • Applications can be both clients and servers simultaneously
    • In their role as servers, applications serve TENA objects called “servants”
    • In their role as clients, applications obtain “proxies,” representing other applications’ servants. Only servers can write to their servant objects’ publication state
  • The TENA Middleware, the TENA objects, and the user’s application code are compiled and linked together

Radar

TestControl Station

Simulation

Communication Mechanism (Network, Shared Memory, etc.)

clients and proxies servers and servants
Clients and Proxies,Servers and Servants
  • Remote Method Invocation

Client Process

Server Process

Proxy Object on Client

Servant Object on Server

Proxy for Object 27

UserApplication

Object 27

UserApplication

Remote Interface

Publication State Interface

Remote Interface

RemoteInterfaceImplementation

Publication State Cache

Local Methods Interface

Publication State

Local Methods Interface

Local MethodsImplementation

Local MethodsImplementation

TENA Middleware

TENA Middleware

Network

clients and proxies servers and servants13

“Set” Methods

Clients and Proxies,Servers and Servants
  • Publication State Dissemination and Access

Client Process

Server Process

Proxy Object on Client

Servant Object on Server

Proxy for Object 27

UserApplication

Object 27

UserApplication

Remote Interface

Publication State Interface

Remote Interface

RemoteInterfaceImplementation

Publication State Cache

Local Methods Interface

Publication State

Local Methods Interface

Local MethodsImplementation

Local MethodsImplementation

TENA Middleware

TENA Middleware

Network

clients and proxies servers and servants14
Clients and Proxies,Servers and Servants
  • Local Methods used on both Client and Server

Client Process

Server Process

Proxy Object on Client

Servant Object on Server

Proxy for Object 27

UserApplication

Object 27

UserApplication

Remote Interface

Publication State Interface

Remote Interface

RemoteInterfaceImplementation

Publication State Cache

Local Methods Interface

Publication State

Local Methods Interface

Local MethodsImplementation

Local MethodsImplementation

TENA Middleware

TENA Middleware

Network

tena middleware platform language support
TENA MiddlewarePlatform / Language Support
  • Release 4.0 Platform Support
    • Windows 2000 sp4 with MSVC++ 7.0
    • Windows XP sp1 with MSVC++ 7.0
    • Linux Red Hat 8.0 (2.4.18 kernel) with gcc 3.2
    • Linux Red Hat 9.0 (2.4.20 kernel) with gcc 3.2.2
    • Sun Solaris 8 (SPARC) with gcc 3.2.3
  • Release 4.0 Language Support
    • C++ support provided with current release
    • OCX (COM) wrapper developed by one of the TENA Users (RTTC)
    • Java wrapper methodology provided by one of the TENA Users (Eglin)
  • Soon
    • Support for Windows MSVC++ 7.1 on XP and 2000
    • Support for SGI with both gcc and MIPSPro compilers
    • Support for VxWorks
tena compliancy levels

TENA Level 3

  • Data Archiving
  • Uses RCC Objects (whenever possible)
  • Standard Control

TENA Level 2

  • Standard use and definition of Time
  • Only uses the TENA Middleware
  • Standard use and definition of Time
  • Only uses the TENA Middleware

TENA Level 1

  • Uses the TENA Middleware
  • Defined as TENA Objects
  • Uses the TENA Middleware
  • Defined as TENA Objects
  • Uses the TENA Middleware
  • Defined as TENA Objects
TENA Compliancy Levels
gradual deployment of tena

TENA-Range

Gateway

TENA-Range

Gateway

TENA-Range

Gateway

Re-architected TENA-compliant Application

New TENA Application

Existing Range Application

Existing Range Application

Other sites

A Few Years

Range Protocols

Existing Range Application

Existing Range Application

Re-architected TENA-compliant Application

New TENA Application

Re-architected TENA-compliant Application

Re-architected TENA-compliant Application

New TENA Application

Existing Range Application

Other sites

Event-ually

Range Protocols

New TENA Application

Re-architected TENA-compliant Application

New TENA Application

Gradual Deployment of TENA

New TENA Application

Existing Range Application

Existing Range Application

Existing Range Application

Other sites

Now

Range Protocols

Existing Range Application

Existing Range Application

Existing Range Application

range integration in millennium challenge 2002 mc02

TENA Gateway

Nellis AFB

Blue Forces

Joint Training,

Analysis, and

Simulation Center

TENA Gateway

Land Range/China Lake

TENA Gateway

Joint

Network

National Training

Center/Ft. Irwin

Integrating

Software

  • Ships
  • Ground forces
  • Aircraft

TENA Gateway

Opposing Forces

Global

Command &

Control System

Electronic Combat

Range/China Lake

Model & Simulation

Feed

TENA Gateway

Sea Range/Point Mugu

Command, Control, Communications, Computers, Intelligence Feed

TENA Gateway

  • Aircraft & air targets
  • Ships
  • Ground forces

US Marines/So. California

Logistics Airfield

Range Integration in Millennium Challenge 2002 (MC02)
gulf range vast impass
Gulf Range VAST/IMPASS

Shipboard Processing

Map Rendering

Virtual Target

Repeater

FFE

3,4,5

Shot

1

Acoustic Processing

GPS

Communication Link

Shot

2

vast impass network connectivity

EGLIN

AFB

200 Miles

400 Miles

VAST/IMPASSNetwork Connectivity

TENA on NIPRNET

CDSA

Dam Neck, VA

Eglin Central Control Facility

TENA on Fiber

TENA on Microwave

Eglin Range Site A-15

CSS

Panama City, FL

jcidex03 a jntc event geography facilities and network

Network

Backbone

JCIDEX03 – a JNTC EventGeography, Facilities, and Network

Ft Rucker

Virtual/Constructive

Simulation

Ground Basing / Ops

Fixed-Wing Ops

Shelby

De Soto

MOA

RGS

RGS

South Ext.

Eglin AFB

3039N 8632W

RGS

South

Corridor

Gulfport

CRTC

190 miles

New Orleans

Fixed-Wing

Basing / Ops

11 Mar 03

150 miles

jcidex 03 tena activity

767

767

SA/AAR Display

SA/AAR Display

TENA Display

Rangeview

JECG Display

JECG Display

Rangeview

  • JECG Display
  • Rangeview –
  • ( Analysis
  • (AMO, TSPI, JTIDS,
  • Instrumentation)

SA/AAR Display

- PCDS -

SA/AAR Display

- PCDS -

(TSPI)

JCIDEX 03 / TENA Activity

Live Infrastructure

Gulfport/Shelby/Camden MOA

Router

ARDS GPS Pods

JCIET

ADNET

Camp Shelby MS

TACTS Pods

JTIDS

Terminal

CRTC

TACTS

GND STN

ARDS

GND STN

Ft. Rucker (opt)

CRTC LAN

Router

ARDS

TENA IF

TACTS

TENA IF

Gateway

JTIDS TENA IF

Gateway

Router

Gulfport

CRTC

Eglin AFB

Router

Casualty Assessment Workstation

(A/G, G/G, A/A geo-pairing)

slide23

Metrics

Capture

VBrick

VBrick

ARDS

Ground

NTC WRC Event Network

Station

NTC Ft. Irwin

Air

Warrior

T-1

Rangeview

Rangeview

PCDS

Display

Display

Display

(GW Control)

(CAOC)

(CAOC)

Nellis WRC Event Network

Air Warrior TENA Gateway

IGRS

NTSC

Video

VBrick

ARDS

Ground

Stations

JNTC Horizontal Thrust Event – Jan 04Range Integration & Instrumentation Solution

DIS

DIS

DIS

TENA

ITM

Rangeview

PCDS

Display

Display

NTC DBST Hub

NTC-IS (CIS)

TENA

TENA

NTC-IS

File/Chat

NTSC

Server

Video

TENA Gateway

NTSC

Video

TENA

Rangeview

Display

AW CSS

T-1 from Tierfort Mtn. to 930 thru 988

PCDS

TENA

Display

HLA

WRC

TENA

TENA/HLA

Horizontal

Gateway

Existing

Event DISA

(GOTH)

TENA

DATMS

TENA Server

Network

TENA

JTASC WRC Event Network

JTASC

TENA

TENA

TENA

Nellis

TENA

Rangeview

PCDS

Unclassified

Display

Display

TENA

TENA

Gateway

& Server

IGRS TENA

Proxy

TENA

TENA

29 Palms

ARDS TENA Gateway

WRC Event Network

ARDS

Twentynine Palms

architecture management team tena amt
Architecture Management Team (TENA AMT)
  • System Engineers & Technical Leads for the current major stakeholders of TENA
    • AAC, Eglin AFB FL
    • NUWC, Newport RI
    • RTTC, Huntsville AL
    • PMRF Synthetic Range
    • EPG, Fort Huachuca AZ
    • WSMR, White Sands NM
    • NAWC-AD, Pax River MD
    • Virtual Proving Ground (VPG)
    • Joint National Training Center (JNTC)
    • NAWC-WD, China Lake & Point Mugu CA
    • Common Training Instrumentation Architecture (CTIA)
    • National Unmanned Underwater Vehicle T&E Center (NUTEC)
  • Design Decisions / Trade-offs / Status
  • TENA Use Cases / Prototype Test Strategies
  • Technical Exchanges of Lessons Learned
  • Issues & Concerns Identification, Investigation, & Resolution

Meetings every 4-8 weeks

Raytheon, Boeing, SAIC, APL,MIT LL, JITC, DMSO, NRL, & ATC also attend & participate

key elements of tena revisited
Key Elements of TENA Revisited
  • TENA lowers the cost to integrate systems together
    • Some systems made TENA-compliant <$20K for MC-02
  • TENA decreases the time to integrate systems together
    • Auto-code generator generated 50K+ SLOC in a few hours from a 4 pg interface definition document
    • Legacy display system made TENA-compliant in 4.5 days for MC-02
    • Hydrophone instrumentation system made TENA-complaint in 2 days
    • HLA-compliant display system gateway made TENA-complaint in 1 day
  • TENA lowers the cost to reuse systems in future events
    • Examples include VAST/IMPASS reusing pre-existing TENA capability
    • Will be better realized in future JNTC events
  • TENA improves flexibility of integrating systems together
    • Range applications can be optimally configured for the particular test event
key elements of tena revisited cont
Key Elements of TENA Revisited (cont.)
  • TENA improves reliability of integrating systems together
    • Auto-code generator ensures that every system has same baseline of source code
    • Standard, validated algorithms (such as coordinate translations or unit conversions) can be embedded in TENA rather than burden software applications of managing and performing translations
    • TENA Middleware performs data marshalling/demarshalling rather than burden software applications
  • TENA eases Deployment at the DoD Ranges
    • TENA can be deployed gradually (system by system) rather than requiring all systems be redesigned
    • Providing on-site training at a number of ranges
  • TENA has a process to follow for sustainment/improvement
    • Leveraged CTTRA workshops and the Architecture Management Team (AMT)
    • Established on-line User Help Desk system to capture feedback from TENA users
    • Pursuing RCC standards, and investigating OMG standards
    • Working with T&E CTTRAP to determine TENA policy among Services
summary of what we have
Summary of What We Have

An Architecture for Ranges, Facilities, and Simulations to Interoperate, to be Reused, to be Composed into greater capabilities

  • Working Implementations of the Architecture
    • TENA Middleware currently works on Windows, Linux, and Sun
  • A Process to Develop and Expand the Architecture
    • CTTRA Workshops, AMT Meetings, and RCC Coordination
  • A Technical Strategy to Deploy the Architecture
    • Gateways provide interim solutions as TENA interfaces
  • A Definition of Compliancy
    • Levels of compliancy to enhance communication among systems engineers and investment decision makers
important contact information
Important Contact Information
  • FI Program Web site, links to Middleware, help desk:http://www.fi2010.org
  • Get the TENA 2002 Document:http://www.fi2010.org/documents/tena2002.pdf
  • FI 2010 Program Topics:fipmo@jcs.mil
  • Questions, comments, feedback about the TENA architecture or the TENA Middleware:TENA-feedback@fi2010.org
  • TENA user community:TENA-users@fi2010.org
  • TENA Object Model technical team:TENA-om-team@fi2010.org