Test & Training Enabling Architecture (TENA) Overview

Test & Training Enabling Architecture(TENA) OverviewKeith PochFoundation Initiative 2010 Cadre20 Aug 2002

Overview of theTest and Training Enabling ArchitecturenFI 2010 OverviewnTENA Architecture OverviewnMC-02 OverviewnMC-02 Range IntegrationnTENA Use Cases at other RangesnSummary

Foundation Initiative 2010Overall VisionnDesign and prototype a technological infrastructure to enableinteroperability and reuse within the range communitynnnRecognize that our solutions need to bemore than quality software,we need to:nnnnSeamless environments that integrate test ranges and facilities, trainingranges, laboratories, and modeling and simulation (M&S) assetsImprove the scope and scale of testing and training the increasinglycomplex systems and missions in a cost-effective mannerElegantly solve key usability issuesSatisfy the core operational andperformance requirementsWork with the range communityso the solutions are implementedLay the groundwork for fulllifecycle support forintegrated multi-range eventsSlide 3

Foundation Initiative 2010Mission SummaryProvide the Core Products necessary to:nnEnable Interoperability among Ranges,Facilities, and Simulations in a quick, costefficient mannerFoster Reuse for Range asset utilization andfor future developmentsSupportsSupports thethe WarfighterWarfighter (Joint(Joint VisionVision 2010/2020)2010/2020)ll EnablesEnables SBA,SBA, STEP,STEP, CEE,CEE, JSB,JSB, andand JDEPJDEPllFostersFosters TestTest andand TrainingTraining IntegrationIntegrationll InIn thethe longlong term:term: SAVESSAVES MONEY!MONEY!llLay the Foundation for Future Range InstrumentationSlide 4

Common Test & Training RangeArchitecture vesTestTestRangesRangesWSMREPGPMRFAFFTCMC AJFCOMDMSOJITCNAVAIRHPCMOJNICSTRICOMAF stAgenciesOPTEVFORAFOTECATECArmy DTCArmy OTCMCOTEASystems engineers & software developers in the DoD Range and Facilitycommunity (both T&E and Training)n13 three-day workshops held (usually every 6-9 months)nCTTRA XIII workshop was held Feb 27-Mar 1Slide 5

Architecture Management Team(TENA AMT)§ System Engineers & Technical Leads for the current majorstakeholders of TENA§§§§§§§§§§§AAC, Eglin AFB FLNUWC, Newport RINAWC-AD, Pax River MDWSMR, White Sands NMRTTC, Huntsville ALEPG, Fort Huachuca AZNAWC-WD, China Lake & Point Mugu CAVirtual Proving Ground (VPG)Common Training Instrumentation Architecture (CTIA)PMRF Synthetic RangeNational Unmanned Underwater Vehicle T&E Center (NUTEC)MeetingsMeetings everyevery4-64-6 weeksweeks§ Design Decisions / Trade-offs / Status§ TENA Use Cases / Prototype Test Strategies§ Technical Exchanges of Lessons Learned§ Issues & Concerns Identification, Investigation, & ResolutionSlide 6

Overview of theTest and Training Enabling ArchitecturenFI 2010 OverviewnTENA Architecture OverviewnMC-02 OverviewnMC-02 Range IntegrationnTENA Use Cases at other RangesnSummary

Foundation Initiative 2010Product SummaryExecution &Configuration ToolsLayer 5Instrumentation &Tactical InterfacesLayer 4Range & FacilityStandardsl SelectedT&E resourceinterfaces to TENAl Performance reports ofcommercially availablecommunication systemsl Procedures for executingsynthetic, multi-range testsLayer 3DoD StandardsLayer 2Networks & HardwareLayer 1Comply with the Joint Technical Architecture(JTA) & the High Level Architecture (HLA)Leverage Existing DoD Networks &Commercially Available HardwareSlide 8

TENA Technical DrivingRequirementsnInteroperability – the ability of independently developed anddeployed systems to seamlessly work together and exchangeinformation to solve a user’s problemnnInteroperability is requirednBetween range resourcesnAcross phases of the acquisition, test, and training processesnBetween range resources and C4ISR resourcesnBetween range resources and simulationsReuse – the ability to use a system or a software application orcomponent at sites or in test or training events other thanthose in which the software was originally designed tooperate.nReuse impliesnComponentization and modularitynStandard, documented interfacesnEncapsulation of legacy capabilitiesSlide 9

Foundation Initiative 2010Project ObjectivesnDefine a common Architecture for the test/training rangecommunity – called “TENA” (Test & Training Enabling Architecture)nnDefine a common Object Model to be used across the rangesDefine and build a common Software Middleware that will:nnnnnCommon understanding of range processes– the Logical Range ConOpsnnComply with the architectureUse the object modelBuild on the HLAEnhance interoperability and reuse among the rangesProvides a common understanding to range users how logical ranges are created(from the integration of range resources), what their capabilities are, and how theyare utilized, operated, and controlledDefine and prototype common Tools to configure and conductmulti-range, synthetic test events or training exercisesnnnCreate distributed, synthetic battlespaces with real weapon systemsLink multiple ranges together to form a larger, cohesive rangeEnable testing, assessment, experimentation, and training of weaponsystem interoperability, C4ISR, and system-of-systemsSlide 10

TENA Architecture OverviewTENA ResourcesNon-TENA ResourcesDisplay ResourceApplicationApplicationTENATENAObject TENA atewayTENA lewareServicesTENA ngToolsToolsEventData eportingReportingToolsToolsSlide 11

IKE 2 Design ApproachnIKE 2 presents to the range user a unification of several powerfulinter-application communication paradigmsnPublish/SubscribennnRemote Method InvocationnnnIndividual messages that can be sent from one application to one or more otherapplicationsData StreamsnnSimilar to CORBA or Java RMIEach object that is published may have methods that can be remotely invokedby other applicationsMessagesnnSimilar in effect to HLA, DIS, and other PDU-based communication systemsEach application publishes certain types of information (the publication state)which can be subscribed to by any other applicationNative support for audio, video, and telemetryArchitecture must support system-wide quality of servicerequirements (e.g., latency, predictability, reliability)nnSoftware must support diverse and often dynamic operating conditionsLeverage existing standards and implementationsSlide 12

Logical RangeSimple ExampleTENA specifies an architecture for range resourcesparticipating in logical tion Mechanism (Network, Shared Memory, etc.)Slide 13

Logical RangeSimple ExamplenTENA specifies a peer-to-peer architecture for logical rangesnnnnApplications can be both clients and servers simultaneouslyIn 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 stateThe IKE 2 Middleware, the TENA objects, and the user’s applicationcode are compiled and linked togetherTENA Application AUserTestApplicationControlCodeStationTENA Application BUserRemoteApplicationViewerCodeProxyProxyTENA Application CUserRadarApplicationCodeServant ProxyServantServantServantProxy Proxy ProxyProxy Servant munication Mechanism (Network, Shared Memory, etc.)Slide 14

Gradual Deployment of pplicationTENATENA/ angeApplicationApplicationA ATENA/ nTENATENA/ ewTENATENAApplicationApplicationSlide 15

IKE 2 Platform/Language SupportnPlatforms SupportednnnnnnnnnWindows NT 4.0 with MSVC 6.0sp5Windows 2000 with MSVC 6.0sp5Linux Red Hat 7.1 with gcc 3.0.3Sun Solaris 8 (SunOS 5.8) with gcc 3.0.3Sun Solaris 8 with SunPro 5.3 compiler (aka Forte Update 2)SGI IRIX 6.5.12 with MIPSPro 7.3.1.2SGI IRIX 6.5.12 with gcc 3.0.3 on SGI hardwareVxWorks, compiler TBDLanguages SupportednnC JavaSlide 16

User SupportnTraining ClassesnnnIKE 2 Web Site http://support.fi2010.org/ nnnUsers register to download software and submit help desk requestsn Registration back-end currently handled manuallyUsers not permitted to distribute the software beyond their local networkIKE 2 Users Email ReflectornnnnTechnical Introduction CourseHands-On Training CourseShare experiences/problems/questions with user group and developersUsed to issue developer announcements concerning the IKE 2 softwareSend an email to majordomo@fi2010.org with body “subscribe ike2-users”Help DesknnInitial submission must be done through web page, then email can be usedPublic solutions will be used for searching common difficulties or problemsSlide 17

Overview of theTest and Training Enabling ArchitecturenFI 2010 OverviewnTENA Architecture OverviewnMC-02 OverviewnMC-02 Range IntegrationnTENA Use Cases at other RangesnSummary

JFCOM Objectives for MC02“Build upon past efforts and advance theconcepts that will rapidly co-evolve enhancedjoint capabilities for conducting rapid, decisive,joint operations in a 2007 timeframe.”l“Emphasize the integration of innovations indoctrine, organization, training, material,leadership, personnel and facilities that enhancethe future joint force commander’s operationallevel command and control”lRef: Initial Planning Conference (16-19 jul 01) IPC msg 131514ZJUN01Slide 19

MC02 Scenario / 110-10844MAP DEPICTS SWUS ONLYOregonIdahoWyomingSW US INCLUDINGALL RANGES 4242#GREAT SALT LAKE#SALT LAKE CITY40#38UtahNevadaFort B ragg40Colorado38SAN FRANCISCO#Monterey#California36Nellis AFB#36Ridgecrest#Vandenberg AFBImaginary PeninsulaIncluding SupportBases with required detail(Exact shape not depicted)#3432Edwards AFB#Twentynine Pal ms Base#New Mexico34ArizonaPHO ENIX#Oceanside#SAN 18-116-114-112-110-108Slide 20

MC02 Ranges & SimsScenario MapD-DayD 7D 14CHINALAKENAWSNELLISIX AIR FORCERANGE risticsCharacteristics PhasingPhasing PreparationPreparation PredictabilityPredictability SynchronizationSynchronizationFT IRWINCSS-C-2EffectsII29PALMSMCA/GCCStrikesEnemy ForcesSlide 21

MC02 Experiment OrganizationSimulation Based Joint Experimentfollowed by:Service Experiments w/ mixed Live / SimlSomereplication of Joint (Sim-based) in Live / SimService ExperimentslEach Service defines Live / Sim mix for its ExperimentlRange Integration opportunity is in Serviceexperimentsl Yetneed to show value to Joint as well as ServiceSlide 22

MC02 Live Deep StrikeNellis AFB RangesTraining Areas212km/132miNellis AFBChina LakeNAWC53km/33mi136km/85miFort Irwin83km/52miSCLASlide 23

Overview of theTest and Training Enabling ArchitecturenFI 2010 OverviewnTENA Architecture OverviewnMC-02 OverviewnMC-02 Range IntegrationnTENA Use Cases at other RangesnSummary

JFCOM Objectives for“Range Integration”l “Demonstratepotential linkage of Western Ranges toshow feasibility for the purposes of joint training andexperimentation”l “Demonstrateintegration of live and simulated actionsin an environment that feeds situational awareness atthe operational level.”Ref: J7 White Paper of 9 Aug 01, “Range Integration in Support of MC02 ExerciseObjectives”Slide 25

Western Ranges Integration Team:Desired “Operational Capabilities”l Providefor interoperability of range Time SpacePosition Information datal Provideinformation to user sitesl Providedistributed fused view of the battlespace in aC4ISR formatl Providefor exercise controll C4ISR/instrumenteddata correlation testingl Providedata collection systemsl Providefor data analysisKey Product: the JFCOM-desired view of the“Common Relevant Operational Picture” (CROP)Slide 26

Overview Of Range IntegrationConnectivity For REPt. MuguSea RangeMicrowave/T-1SecureMicrowave (NRMS)ChinaLakeEC RangeSecure FiberChina LakeLand RangeSecure Leased T-1& Secure teriB a al- upc kupT1Ft. IrwinDRENDNellisRangeOne-way (Transmit Only) Fiber OpticEthernet Interface To Inject UnclassifiedData Into NetworkSlide 27

Overview of theTest and Training Enabling ArchitecturenFI 2010 OverviewnTENA Architecture OverviewnMC-02 OverviewnMC-02 Range IntegrationnTENA Use Cases at other RangesnSummary