| Date post: | 14-Jan-2016 |
| Category: |
Documents |
| Upload: | elwin-eaton |
| View: | 221 times |
| Download: | 4 times |
Gene HudginsTENA Development Lead
4 March 2003
Test and Training Enabling Test and Training Enabling Architecture (TENA)Architecture (TENA)
TheThe FoundationFoundation for DoD Range Interoperabilityfor DoD Range Interoperability
Slide 2
Foundation Initiative 2010Foundation Initiative 2010MissionMission
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:
Lay the Foundation for Future Test and Training Range Instrumentation
Support the Warfighter (Joint Vision 2010/2020) Enable Simulation-Based Acquisition Foster Test and Training Integration In the long term: SAVE MONEY!
Support the Warfighter (Joint Vision 2010/2020) Enable Simulation-Based Acquisition Foster Test and Training Integration In the long term: SAVE MONEY!
Slide 3
Foundation Initiative 2010Foundation Initiative 2010Project ObjectivesProject 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
Slide 4
Overall Development StrategyOverall 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
User Feedback
LessonsLearned
User Feedback
LessonsLearned
User Feedback
LessonsLearned
PrototypesPrototypesPrototypesPrototypes
PrototypesPrototypesPrototypesPrototypes
PrototypesPrototypes
PrototypesPrototypes
Test & Training Enabling
Architecture(TENA)
Slide 5
Driving Technical RequirementsDriving Technical Requirements
1. 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.
2. 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.
3. 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.
Slide 6
Achieving Interoperability, Achieving Interoperability, Reuse, and ComposabilityReuse, 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 OM, TENA Middleware
TENA
TENA Object Model (OM)
TENA Middleware
Network, shared memory
TENA Object Model(Environment)
TENA Technical Process
Reusable Tools,Repository
Slide 7
TENA Architecture OverviewTENA Architecture Overview
Non-TENA Applications
RangeResource
Application
RangeResource
Application
Management andMonitoring Apps
Management andMonitoring Apps
Analysis andReview Apps
Analysis andReview Apps
Non-TENA Communications
TENATENATENA
TENARepository
Range ResourceApplication
Range ResourceApplication
DataCollectors
DataCollectors
HWILHWIL
RangeResource
Application
RangeResource
Application
TENA Middleware
Repository Utilities
Repository Utilities
TENAObject
TENAObjectTENA
Object
Logical Range Planning Utilities
Logical Range Planning Utilities
Object Model Utilities
Object Model Utilities
LogicalRangeData
Archive
TENA Utilities
TENA Common Infrastructure
TENA Applications
Non-TENA System
Non-TENA System
I S R F o r c e M i x S t u d y
S h a d i n g i s : P h a s e
6 .26 .05 .44 .84 .23 .63 .02 .41 .81 .20 .60 .0
TENA Tools
GatewayGateway
Slide 8
Ways TENA Middleware CanWays TENA Middleware CanExchange DataExchange 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
Slide 9
Stateful Distributed ObjectsStateful 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
Slide 10
TestControl Station
Simulation
Logical RangeLogical RangeSimple ExampleSimple Example
TENA specifies an architecture for range resources participating in logical ranges
Communication Mechanism (Network, Shared Memory, etc.)
Radar
Slide 11
Logical RangeLogical RangeSimple ExampleSimple 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
TestControl Station
Communication Mechanism (Network, Shared Memory, etc.)
RadarSimulation
TENA Middleware
TENA Application C
UserApplication
Code
Servant Proxy
Proxy ProxyServant
TENA Middleware
TENA Application B
UserApplication
Code
Proxy Proxy
Proxy Proxy Proxy
TENA Middleware
TENA Application A
UserApplication
Code
Servant
ServantServant
Slide 12
Clients and Proxies,Clients and Proxies,Servers and ServantsServers and Servants
Remote Method Invocation
Proxy Object on ClientProxy for Object 27
Remote Interface
Publication State Interface
Publication State Cache
Local Methods Interface
Servant Object on Server
Object 27
Remote Interface
Publication State
Local Methods Interface
Client Process Server Process
TENA Middleware TENA Middleware
Network
UserApplication
RemoteInterface
Implementation
Local MethodsImplementation
Local MethodsImplementation
UserApplication
Slide 13
Clients and Proxies,Clients and Proxies,Servers and ServantsServers and Servants
Publication State Dissemination and Access
Proxy Object on ClientProxy for Object 27
Remote Interface
Publication State Interface
Publication State Cache
Local Methods Interface
Servant Object on Server
Object 27
Remote Interface
Publication State
Local Methods Interface
Client Process Server Process
TENA Middleware TENA Middleware
Network
UserApplication
RemoteInterface
Implementation
Local MethodsImplementation
Local MethodsImplementation
UserApplication
“Set” Methods
Slide 14
Clients and Proxies,Clients and Proxies,Servers and ServantsServers and Servants
Local Methods used on both Client and Server
Proxy Object on ClientProxy for Object 27
Remote Interface
Publication State Interface
Publication State Cache
Local Methods Interface
Servant Object on Server
Object 27
Remote Interface
Publication State
Local Methods Interface
Client Process Server Process
TENA Middleware TENA Middleware
Network
UserApplication
RemoteInterface
Implementation
Local MethodsImplementation
Local MethodsImplementation
UserApplication
Slide 15
TENA MiddlewareTENA MiddlewarePlatform / Language SupportPlatform / 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
Slide 16
TENA Compliancy LevelsTENA Compliancy Levels
Uses the TENA Middleware
Defined as TENA Objects
TENA Level 1
Uses the TENA Middleware
Defined as TENA Objects
Standard use and definition of Time
Only uses the TENA Middleware
Data Archiving Uses RCC Objects (whenever possible)
Standard Control
TENA Level 3
Uses the TENA Middleware
Defined as TENA Objects
Standard use and definition of Time
Only uses the TENA Middleware
TENA Level 2
Slide 17
Other sites
New TENA Application
Existing Range
Application
Existing Range
Application
Existing Range
Application
Existing Range
Application
Existing Range
Application
Existing Range
Application
NowRange Protocols
TENA-Range
Gateway
Event-ually
Existing Range
Application
Re-architected TENA-compliant
Application
Re-architected TENA-compliant
Application
Re-architected TENA-compliant
Application
New TENA Application
New TENA Application
New TENA Application
Range ProtocolsOther sites
TENA-Range
Gateway
New TENA Application
Existing Range
Application
Existing Range
Application
Existing Range
Application
Existing Range
Application
Re-architected TENA-compliant
Application
New TENA Application
Re-architected TENA-compliant
Application
A Few Years Range Protocols
Other sitesTENA-Range
Gateway
Gradual Deployment of TENAGradual Deployment of TENA
Slide 18
Range Integration in Millennium Range Integration in Millennium Challenge 2002 (MC02)Challenge 2002 (MC02)
Joint Training, Analysis, and
Simulation Center
Global Command &
Control System
IntegratingSoftware
TENA Gateway
Joint Joint NetworkNetwork
Command, Control, Communications, Computers, Intelligence Feed
Blue Forces
Opposing Forces
• Aircraft & air targets• Ships• Ground forces
• Ships• Ground forces• Aircraft
Electronic Combat Range/China Lake
Nellis AFB
National Training Center/Ft. Irwin
Land Range/China Lake
Sea Range/Point Mugu
TENA Gateway
TENA Gateway
TENA Gateway
TENA Gateway
TENA Gateway
US Marines/So. CaliforniaLogistics Airfield
Model & SimulationFeed
Slide 19
Gulf Range VAST/IMPASSGulf Range VAST/IMPASS
Acoustic ProcessingGPSCommunication Link
Shipboard ProcessingMap RenderingVirtual Target
Repeater
Shot 1
Shot 2
FFE 3,4,5
Slide 20
VAST/IMPASSVAST/IMPASSNetwork ConnectivityNetwork Connectivity
EGLINAFB
400 Miles
200 Miles
Eglin Central Eglin Central Control FacilityControl Facility
CSSCSS Panama City, FLPanama City, FL
CDSACDSADam Neck, VADam Neck, VA
Eglin Range Site A-15Eglin Range Site A-15
TENA on NIPRNET
TENA on MicrowaveTENA on Fiber
Slide 21
JCIDEX03 – a JNTC EventJCIDEX03 – a JNTC EventGeography, Facilities, and NetworkGeography, Facilities, and Network
Eglin AFB3039N 8632W
De SotoMOA
South Ext.
SouthCorridor
19
0 m
ile
s
150 miles11 Mar 03
RGS
RGSRGS
NetworkBackbone
Ground Basing / OpsFixed-Wing Ops
Ft RuckerVirtual/Constructive Simulation
New Orleans
Shelby
Fixed-WingBasing / Ops
GulfportCRTC
Slide 22
JCIDEX 03 / TENA ActivityJCIDEX 03 / TENA Activity767
ARDS GPS Pods
JTIDS
Terminal
ARDS
GND STN
767
JTIDS TENA IF
Gateway
ARDS
TENA IF
JECG Display
-Rangeview –
( Analysis
(AMO, TSPI, JTIDS,
Instrumentation)
Casualty Assessment Workstation
(A/G, G/G, A/A geo-pairing)
Router
Router
SA/AAR Display
JECG Display
Rangeview
JECG Display
Camp Shelby MS
Ft. Rucker (opt)
Gulfport
CRTC
Live Infrastructure
Gulfport/Shelby/Camden MOA
Router
TENA Display
Rangeview
Eglin AFB
CRTC
TACTS
GND STN
TACTS
TENA IF
Gateway
SA/AAR Display
- PCDS -
(TSPI)
Router
JCIET
ADNET
TACTS Pods
SA/AAR Display
- PCDS -
SA/AAR Display
CRTC LAN
Slide 23
JNTC Horizontal Thrust Event – Jan 04JNTC Horizontal Thrust Event – Jan 04Range Integration & Instrumentation SolutionRange Integration & Instrumentation Solution
DIS DIS
DIS TENA
TENA
29 PalmsWRC Event Network
IGRS TENAProxy
PCDSDisplayTENA
Twentynine Palms
ARDSARDS TENA Gateway
TENA
TENA
Nellis
TENA JTASC WRC Event Network
TENA/HLAGateway(GOTH)
PCDSDisplayTENA
TENAHLA
JTASC
TENA Server
TENA
ExistingAir
WarriorT-1
TENA
Nellis WRC Event Network
PCDSDisplay(CAOC)
Air Warrior TENA Gateway
RangeviewDisplay(CAOC)
RangeviewDisplay
(GW Control)TENA TENA
RangeviewDisplay
TENA
RangeviewDisplay
TENA
NTC-ISTENA Gateway
PCDSDisplayNTC DBST Hub
ITM
NTC-IS (CIS)
AW CSS
RangeviewDisplay
VBrick
VBrickNTSCVideo
VBrick
IGRS
MetricsCapture
ARDSGroundStation
NTC WRC Event Network
NTC Ft. Irwin
ARDSGroundStations
T-1 from Tierfort Mtn. to 930 thru 988
TENA
File/ChatServer
WRCHorizontal
Event DISADATMSNetwork
UnclassifiedTENA
Gateway& Server
NTSCVideo
NTSCVideo
Slide 24
Architecture Management Architecture Management Team (TENA AMT)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
Meetings every 4-8 weeks
Raytheon, Boeing,
SAIC, APL, MIT LL,
JITC, DMSO, NRL, &
ATC also attend &
participate
Slide 25
Key Elements of TENA Key Elements of TENA RevisitedRevisited
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
Slide 26
Key Elements of TENA Key Elements of TENA Revisited (cont.)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
Slide 27
Summary of What We HaveSummary of What We Have
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
An Architecture for Ranges, Facilities, and Simulations to Interoperate, to be Reused, to be Composed into greater capabilities
An Architecture for Ranges, Facilities, and Simulations to Interoperate, to be Reused, to be Composed into greater capabilities
Slide 28
Important Contact InformationImportant 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:[email protected]
Questions, comments, feedback about the TENA architecture or the TENA Middleware:
TENA user community:[email protected]
TENA Object Model technical team:[email protected]
