Test Resource Management Center Joint Mission Environment Test Capability (JMETC) Overview and Usage of OneSAF in Joint Battlespace Dynamic Deconfliction (JBD2)

1
Test Resource Management CenterJoint Mission
Environment Test Capability (JMETC) Overview and
Usage of OneSAF in Joint Battlespace Dynamic
Deconfliction (JBD2)

• Mr. John Rutledge
• OneSAF Users Group
• 31Mar, 2009

2
The JMETC Mission

• JMETC provides the DoD TE Community the resident
  distributed test expertise and the persistent
  modern network infrastructure needed for the
  connection and use of distributed live, virtual,
  and constructive resources to augment the DTE
  and OTE of joint systems and systems-of-system.

3
JMETC Distributed Test Infrastructure Product
Lines

• Persistent connectivity
• Middleware
• Standard interface definitions and software
  algorithms
• Distributed test support tools
• Data management solutions
• Reuse repository

4
JMETC EnablesDistributed Testing
Joint Operational Scenarios
SystemsUnderTest
Range
EnvironmentGenerator
ThreatSystems
VirtualPrototype
IntegratedTestResources
TENA Standard Interface Definitions
TENA Standard Interface Definitions
TENA Standard Interface Definitions
TENA Standard Interface Definitions
TENA Standard Interface Definitions
TENA Standard Interface Definitions
TENA CommonMiddleware
TENA CommonMiddleware
TENA CommonMiddleware
TENA CommonMiddleware
JMETC VPN on SDREN
Reuse Repository
JMETC Infrastructure
Distributed Test Support Tools
Data Management Solutions
Customer Support
TENA Test and Training Enabling Architecture
5
JMETC1. Reduces
Technical Risk 2. Saves Time
3. Reduces Costs

• People Experienced and highly skilled expertise
  forward deployed for distributed test planning
  and operations
• Network Modern, tested, and reliable network
  capability already in place
• Practices Integration and interoperability of
  test resources is proven practice plus a
  quarterly Users Group to capture technical
  requirements
• Data Exchange Methodologies and solutions have
  already been tested, proven, and put in practice
• RD ST JMETC actively captures customer
  needs and requirements on a continuous basis and
  programs basic and applied research projects to
  improve distributed test capabilities for the
  Department
• Lessons Learned JMETC is the TE Communities
  enterprise-level focal point for collecting and
  maintaining lessons learned as well as
  implementing resource reuse for improving the
  DoDs distributed test capability
• Tools JMETC maintains a comprehensive suite of
  distributed test toolsin fact, the same tools
  used by the Joint Interoperability Test Command
  (JITC) for net-ready KPP interoperability
  certification

6
JMETC Leadership Governance
JMETC Chain of Command
Honorable John Young USD (ATL)
JMETC Governance

• Senior DoD Leaders
• Charter signed 26 Oct 07

Testing in a Joint Environment Roadmap Senior
Steering Group

• Service/Agency reps
• Regularly held meetings to discuss/review plans,
  common issues, needed studies, etc.

JMETC Advisory Group
Chip Ferguson JMETC Program Manager

• Technical representativesof customers and test
  resource owners
• Six meetings held to date
• 265 participants at last meeting

JMETC Users Group
George Rumford Senior Technical Advisor
7
Relationship within TRMCSynergy through Aligned
Investment
Quadrennial Defense Review Strategic Planning
Guidance
Service TE Needs and Solutions Process
Service TE/ST Working Groups
DoD Strategic Plan for TE Resources
Risk mitigation needs Technology shortfalls
Requirements
TRMC Joint Investment Programs
Capabilities
Risk mitigation solutions Advanced development
6.3
6.4
6.5
Service Improvement Modernization/ Programs
Acquisition Programs / Advanced Concept
Technology Demonstrations
TE Multi-Service / Agency Capabilities
DoD Corporate Distributed Test Capability
8
TRMC Investment Programs Overview

• Established in FY2002
• Develops technologies required to test future
  warfighting capabilities
• 6.3 RDTE funds
• 95M / year
• 7 current focus areas
• Directed Energy
• Hypersonics
• Netcentric Systems
• Unmanned Systems
• Multi-Spectral Sensors
• Non-intrusive Instruments
• Spectrum Efficiencies

• Established in FY1991
• Develops or improves test capabilities that have
  multi-Service utility
• 6.4 RDTE funds
• 140M / year
• 52 current projects
• 27 projects developing core Joint capabilities
• 2 projects improving interoperability test cap.
• 9 projects improving threat representations used
  in testing
• 16 projects addressing near-term OT shortfalls

• Established in FY2007
• Provides corporate infrastructure for distributed
  Joint testing
• 6.5 RDTE funds
• 10M / year
• 33 current sites
• Expanding to 42 sites
• Maintains
• Network connections
• Security agreements
• Integration software
• Interface definitions
• Distributed test tools
• Reuse repository

TE/ST
CTEIP
JMETC
9
Current JMETC Connectivity

• Dedicated, trusted VPN on SDREN (part of the GIG)
• Encrypted for Secret System High
• DISA-registered IP address space
• Active monitoring of network performance
• Capable of supporting multiple simultaneous test
  events

Ft Lewis EPG
Aberdeen ACCN
Pax River (2) ACETEF, E2C
Dahlgren (2)CEDL, IWSL
JMETC SYSCON
Boeing-St. LouisCIDS
Lorton HPCMO
JFCOM JSIC
Nellis CAOC-N
Dam Neck CDSA
China Lake (2) AV-8B, F/A-18
Kirtland AFBSDOCC
Redstone (3) DTCC, GMAN, SED
Edwards Ridley
Pt Mugu (2) ITEC, AEA
Charleston (2) IPC, MEF-MEU
Camp Pendleton MCTSSA
WSMR IRCC
Pt Loma ICSTD
Army Air Force Navy Marines Joint Industry
33Sites
Ft Huachuca JITC
Ft Hood (2) CTSF, TTEC
Eglin (3) AOC, DTF, GWEF, Hurlburt 505CCW
10
Planned JMETC Connectivity
Ft Lewis EPG
Hanscom CEIF
Aberdeen ACCN
Pax River (2) ACETEF, E2C
Dahlgren (3)CEDL, IWSL, C2 Lorton HPCMO
JMETC SYSCON
Boeing-St. LouisCIDS
JFCOM JSIC
Nellis CAOC-N
Dam Neck CDSA
Wallops NAVSEA
China Lake (2) AV-8B, F/A-18
Kirtland AFBSDOCC
Tinker AFBAWACS
Edwards Ridley
Pt Mugu (2) ITEC, AEA
Charleston (2) IPC, MEF-MEU
Camp Pendleton MCTSSA
Redstone (3)DTCC, GMAN, SED
WSMR IRCC
Greenville Rivet Joint
Pt Loma (2)ICSTD, RLBTS
Army Air Force Navy Marines Joint Industry
40 Sites
Ft HuachucaJITC
Eglin (4) AOC, DTF, GWEF,
KHILS Hurlburt 505CCW
Ft Hood (2) CTSF, TTEC
MelbourneJSTARS
11
Network AggregationBridging Networks
JTEN
SIPRNet
NAVY DEP
AF ICE
ATIN
JMETC VPN
12
Joint Mission Environment TestCapability
(JMETC)FY08 Accomplishments
13
FY09 JMETC Major Test Support Schedule
Discussions for possible future teaming Gerald
R. Ford Class (CVN-21) Joint Strike
Fighter (JSF) Multi-mission Maritime Aircraft
(MMA) Net-Enabled Command Capability
(NECC) Future Combat System (FCS) Broad
Area Maritime Surveillance (BAMS)
14
JMETC Typical Support
Customer JPO
Infrastructure Support
Requirements
JMETC
JMETC Operations Planning Support
Technical Support
JMETC Event Support Team
Planning
Tools
Middleware
Network
JMETC Tool Suite InterTEC
TENA SDA
JMETC
15
JBD2 OneSAF Briefing Outline

• JBD2 Event Summary
• JBD2 JME Physical Design Overview
• JBD2 OneSAF Usage
• OneSAF Configuration
• JMETC TENA-MATREX Gateway
• JBD2 Observations

16
JBD2 OneSAF Briefing Outline

• JBD2 Event Summary
• JBD2 JME Physical Design Overview
• JBD2 OneSAF Usage
• OneSAF Configuration
• JMETC TENA-MATREX Gateway
• JBD2 Observations

17
JBD2 JTEM 08 Test Event Background and Rationale

• Future Combat Systems (FCS)
• Oct 2002 FCS Test (IST/CTO) recognized that FCS
  presents new testing challenges that require new
  test capabilities
• Systems of Systems on a grand scale
• Move, shoot , communicate simultaneously
• Seamless integration with Joint elements for
  Network-centric operations
• 2003 and 2006 TEMP codified the need for
  investments to provide needed test capability
• Instrumentation
• Modeling and Simulation
• Networking
• Multiple investments initiated to provide needed
  stimulation, data collection and analysis
  requirements
• Many of these investments are maturing and need
  to be tested

• DoD Joint Test Capability Roadmap
• Mar 2003 DoD recognized that its ability to
  implement seamless Joint operations is
  insufficient
• 2004 DoD Strategic Planning Guidance demanded
  creation of Joint environment testing capability
• 2005 OSD Initiated Joint Test and Evaluation
  Methodology (JTEM) project and Joint Mission
  Environment Test Capability (JMETC) development
  effort
• JTEM focuses on the methods and processes
  associated with testing in a Joint environment
• JMETC focuses on the infrastructure needed to
  facilitate the JTEM methods and processes
• JTEM and JMETC have created test methods and
  infrastructure that need to be tested

2008 Event Objective Assess suitability of JTEM
CTM for testing FCS test technologies using JMETC
infrastructure in a relevant Operational context
18
JBD2 JTEM 08 Test Event Goals

• JTEM
• Assess effectiveness and suitability of JTEM
  Capability Test Methodology (CTM) processes
• JMETC
• Characterize the network infrastructure and
  mature the baseline capability to support SoS
  level testing across the Services
• FCS
• Establish a rigorous test context to examine FCS
  test technology requirements needed for testing
  in a Joint environment in support of FCS
  Milestone C test activities
• Application of JTEM methods and processes Use of
  JMETC infrastructure
• Perform test capability assessment within JBD2
  context
• Establish and Utilize FCS CTO Test Technology
  investments to baseline this context
• Common Control Nodes (CCN)
• Test Center Assets
• Test Tools and Instrumentation
• Risk reduction for critical FCS test technology
  areas
• Critical network test technologies
• Distributed Test Infrastructure Technologies
• V V A of the LVC-DE

Support of Joint Initiatives While Meeting FCS
Test Technology Objectives
19
Current Airspace Control Geometries
LARGE VOLUMES ARE CLEARED FOR SURFACE TO SURFACE
ATTACK MISSIONS
MAXIMUM ALTITUDE OF AIRCRAFT
MISSILE FLIGHT PATH
ZALT
GT
TARGET
TARGET AREA HAZARD
LAUNCHER
PLATOON AREA HAZARD
20
Workaround to Reduce Volume of Airspace Control
Geometries
21
Advanced Concept for Airspace Control Geometries
MAXIMUM ALTITUDE OF AIRCRAFT
VOLUME OF AIRSPACE THAT CAN BE CLEARED WITH THE
MISSILE FLIGHT PATH
MISSILE FLIGHT PATH
ZALT
GT
TARGET
TARGET AREA HAZARD
LAUNCHER
PLATOON AREA HAZARD
22
Joint Battlespace Dynamic Deconfliction Relevant
Operational Context (OV-1)
JLENS
AWACS
JSTARS
UH-60
AH-64
Blue Force Mission Objective
JAOC
PATRIOT
UAV
JLENS
ASOC
0
IBCS
NLOS-LS
NLOS-C
0
DCGS-A
Joint Fires / Joint CAS
USMC
Air Maneuver/Operations
Air and Missile Defense
23
JBD2 JTEM 08 Test Event Infrastructure Build Up

• Conduct distributed test using FCS Common Control
  Nodes (CCN), Army Test Centers, and appropriate
  Joint assets in a JBD2 context
• Follow JTEM CTM Processes end-to-end
• Flow down requirements from Mission Effectiveness
  to define traceability for collectable data
  elements
• Establish a rigorous test context to examine FCS
  test technology requirements needed for testing
  in a Joint Mission Environment in support of
  FCS Milestone C test activities
• Leverage existing / emerging test technologies to
  provide required capabilities
• AF ICE IF 07 Baseline
• JMETC Infrastructure
• CTEIP Products (InterTEC)
• FCS Test Technologies investments
• ATEC Instrumentation investments
• Army Cross Command Collaborative Environment
  (3CE) products, infrastructure and processes
• Others as defined by requirements process
• Focus on FCS Milestone C test requirements
• End-to-end network capabilities
• Joint test environment context
• Verification and validation of all test
  technologies

Leave-Behind Joint Infrastructure and Systems
Engineering Processes and Products
24
JBD2 OneSAF Briefing Outline

• JBD2 Event Summary
• JBD2 JME Physical Design Overview
• JBD2 OneSAF Usage
• OneSAF Configuration
• JMETC TENA-MATREX Gateway
• JBD2 Observations

25
JBD2 JME Physical Design Overarching Design
Constructs

• Requirement is for a composable, scalable Free
  Play environment
• Support for varying degrees of deconfliction
• Support for current force, integrated force, and
  future force activities
• Support for JBD2 relevant Mission Threads
• Support for live, virtual, and/or constructive
  operational capabilities and test resources for
  different test runs
• Desire is to be able to measure improvements
  future force JBD2 brings beyond current force
  implementation
• Current Force JBD2 Operational Test
• Future Force JBD2 Developmental Test

26
JBD2 JME Physical Design JTEM 08 Test Event OV-1
SIMAF
SIMAF
AFRL
Reaper
AWACS
SIMAF ACETEF
C2TF
Networked Munitions
Net Enabled Weapon
SPAWAR-C
JFMCC
SIMAF C2TF WSMR ACCN
ACCN ACETEF WCCN
JAOC
JTAC
CL I UAS
ASOC
Enemy Armor
GCIC
ACCN
C2TF
OTC
Paladin
BCT
CCA
GMAN
Blue Force Mission Objective
GMAN
ACCN
ARS BN
USMC RGT
Enemy Vehicles
NLOS-LS
SPAWAR-C
OTC
DTCC
JAGS
Joint Fires / Joint CAS
1CAB BN
WCCN
Air Maneuver/Operations
Counter IED
Combat Identification
OTC
SPAWAR-C GMAN
USMCRecon
Battlespace Deconfliction C2
USMC HIMARS
OTC
27
JBD2 JME Physical Design Tactical Roles

• ACCN, Aberdeen
• ARS BN FSE
• 1 PLT ARS Leader
• 2 PLT ARS Leader
• JTAC for 1 PLT ARS
• UAS for 1 PLT ARS
• Threat Vehicles

• ACETEF, Pax River
• F-18 (2)
• Threat Vehicles

• SIMAF, WP AFB
• AWACS
• JTAC for 2 PLT ARS
• F-16 (2)
• MQ-9 Reaper UAS

• GCIC, Langley AFB
• JAOC

• WCCN, White Sands
• 1CAB FSE
• 1 PLT 1CAB Leader
• 2 PLT 1CAB Leader
• Threat Vehicles
• IRCC
• JTAC for 1 PLT 1CAB

• JSIC, Suffolk
• JTF Command

• NECS, SPAWAR - C
• JFMCC Command

• GMAN, Redstone Arsenal
• 5 BCT FSE
• USMC Forward Observer
• Threat Vehicles

• USMC, SPAWAR - C
• USMC RGT FSCC
• USMC Recon JTAC

Site Key
Army Air Force Navy Marines Joint

• OTC/TTEC, Ft Hood
• 5 BCT Knights (3)
• Fires BN FSE
• NLOS-LS Section
• Paladin Battery
• USMC HIMARS

• 46TS, Eglin AFB
• ASOC
• JTAC for 2 PLT 1CAB
• SDB II Weapon
• GWEF, Eglin AFB - SWARM Weaponized UAS

28
JBD2 JME Physical Design Systems View 1 (SV-1)

• JBD2 Test Sites Utilize
• JMETC Provided Network Infrastructure
• LVC Operational Capability Layer
• LVC Test Resource Layer
• FCS Funded Terrain Databases
• AETF LDIF
• SO-1 Lessons Learned and SW fixes

• Common Systems
• DCARS (RICS) 2
• Test Talk
• SIMDIS
• IVT
• VOIP
• TENA Gateways

• EPG, Ft Lewis
• RPWS
• DCARS
• DAUVS
• STARSHIP

EPG, Ft Lewis
ACCN, APG

• ACCN, APG
• AFATDS
• RPWS (2)
• vJTAC
• MDV
• OneSAF
• CL 1 UAS Sim

• SIMAF, WP AFB
• EAAGLES
• Kaleidoscope
• vJTAC
• TENA Video Client
• ASTi

• WARCAP, Pentagon
• TAIS
• ASTi

WARCAP, Pentagon
SIMAF, WP AFB

• WDTC, DPG
• 4DWX
• (Safari to DTCC)

• ACETEF, Pax River
• JIMM
• NGTS
• ASTi

ACETEF, Pax River
WDTC, DPG

• JSIC, Suffolk
• GCCS-J (CTP)
• ASTi
• JNTC, Suffolk
• - JDAS / DCARS Server

JSIC, Suffolk JNTC, Suffolk

• GMAN, RSA
• AFATDS
• GCCS-A
• TAIS
• RPWS
• DAUVS
• ASTi
• MDV
• JEMS
• TSIU
• TENA Video Client
• OneSAF
• DTCC, RSA
• TAIS
• ASTi
• OneSAF
• TENA Exe Mgr
• 4DWX

• GCIC, Langley AFB
• GCCS-J
• TBMCS
• ASTi

System Key Live Virtual Constructive Test
Resources
GCIC, Langley AFB
GMAN, RSA DTCC, RSA

• WCCN, WSMR
• AFATDS
• RPWS (2)
• ASTi
• OneSAF
• IRCC, WSMR
• vJTAC
• ASTi
• ILH

WCCN, WSMR IRCC, WSMR

• NECS, SPAWAR - C
• GCCS-M
• TBMCS
• CEC RTTS
• ASTi
• USMC, SPAWAR - C
• GCCS-J
• TBMCS
• AFATDS
• ASTi

NECS, SPAWAR - C USMC, SPAWAR - C
OTC/TTEC, Ft Hood
46TS, Eglin AFB GWEF, Eglin AFB
Site Key

• 46TS, Eglin AFB
• TBMCS
• TACP-CASS
• vJTAC
• JRE-LINK 16/11
• ASTi
• DREAMS
• GWEF, Eglin AFB - SWARM
• ASTi

• OTC-TTEC, Ft Hood
• - ExCIS
• MDV
• RPWS
• OneSAF
• OT-TES
• - Live Vehicles

Army Air Force Navy Marines Joint
29
JBD2 JME Physical Design Site Connectivity
Pax River
Aggregation Router
SYSCON Pax River
RTTC (DTCC, GMAN) Redstone
E1
AF-ICE Key
SDREN Key
JTEN Key
E3
E3
E2
E3
JSIC JFCOM
E3
E3
ACCN Aberdeen
E3
AFCA, Scott AFB Network Monitoringof AF-ICE
Enclave
E1
GWEF Eglin AFB
E3
E3
WARCAP Pentagon
EPG Ft. Lewis
Test Bay 8 JFCOM
E2
E2
Hub
46TS C2TF Eglin AFB
E2
SIMAF, WP AFB
E3
E3
TTEC Ft Hood
E2
E3
GCIC, Langley AFB
E3
IRCC WSMR
Bldgs. 3147 and 3440 Charleston SSC
ACETEF Pax River
E1 TacLane with JTEN Key E2 TacLane with
AF-ICE Key E3 TacLane with SDREN Key
30
JBD2 JME Physical Design Data Management
Architecture (1 of 2)
31
JBD2 JME Physical Design Data Management
Architecture (2 of 2)
32
JBD2 OneSAF Briefing Outline

• JBD2 Event Summary
• JBD2 JME Physical Design Overview
• JBD2 OneSAF Usage
• OneSAF Configuration
• JMETC TENA-MATREX Gateway
• JBD2 Observations

33
JBD2 OneSAF UsageOneSAF Configuration

• Three distributed sites running OneSAF Version
  1.5.1 were used in support of the JBD2 Event
• Sites included
• White Sands Missile Range (WSMR), NM
• Aberdeen Common Control Node (ACCN), Aberdeen, MD
• Redstone Technical Test Center (RTTC), Redstone
  Arsenal, AL
• Each site was running a standalone Federation on
  the local LAN
• Forces used to provide scenario context for the
  event as well as provide hostile entities for the
  event.
• Entity information was published using the HLA
  Adapter and MATREX FOM
• Entity information distributed on the JMETC VPN
  via Test and Training Enabling Architecture
  (TENA) via the JMETC TENA-MATREX Gateway

34
JBD2 OneSAF UsageJMETC TENA-MATREX Gateway

• GatewayBuilder (GWB) was used to generate a
  Gateway that mapped MATREX HLA platform and
  engagement information into Standard TENA
  Platform and Engagement Object Models (OMs).
• GatewayBuilder is a flexible, extensible,
  graphically driven tool that automatically
  generates gateways to bridge simulation and live
  protocols
• GatewayBuilder streamlines integration process
  and reduces time and effort of creating gateways
• GatewayBuilder supports mappings between TENA,
  DIS, HLA, and other message-based protocols
• The TENA Standard Platform OM was extended to
  pass OneSAF specific entity information.

35
JBD2 OneSAF Briefing Outline

• JBD2 Event Summary
• JBD2 JME Physical Design Overview
• JBD2 OneSAF Usage
• OneSAF Configuration
• JMETC TENA-MATREX Gateway
• JBD2 Observations

36
JBD2 Observations

• Three separate federations running multiple
  instances of OneSAF were used to provide the
  scenario context for the JBD2.
• OneSAF was used to provide hostile targets to be
  engaged during the exercise
• Using the JMETC TENA-MATREX Gateway allowed
  OneSAF entities and engagements to be integrated
  into the rest of the JBD2 Live, Virtual,
  Constructive environment.

37
Forward Thinking - Native TENA support for OneSAF

• Ultimate goal would be to have native support for
  TENA in OneSAF
• Possible Course of Action (COA)
• TENA/JMETC development team(s) work in
  conjunction with the OneSAF team to develop a
  native TENA plugin similar to the OneSAF HLA
  Adapter
• TENA/JMETC developers could build the core plugin
  while working with the OneSAF development team to
  insure a tight interface to the core OneSAF
  product
• Benefits to the Customer
• Ease of application development
• Higher performance (no gateway required)
• Additional middleware options
• Easy access to range instrumentation

38
JMETC Initiatives

• Streamlining the Network Accreditation process
• DoD Information Assurance Certification and
  Accreditation Process (DIACAP) Implementation
  Tiger Team
• Cross-Domain Solutions
• Unified Cross Domain Management Office (UCDMO)
• Information Operations Range (IO Range)
• Joint Improvised Explosive Device Defeat
  Organization (JIEDDO)
• West Coast Aggregation Router
• Mobile Node Capability (Transportable Node)

39
Summary

• JMETC supports the full spectrum of Joint
  testing, supporting many customers in many
  different Joint mission threads
• JMETC is being built based on customer
  requirements
• JMETC event support can be tailored to customer
  needs
• JMETC is partnering with Service activities and
  leveraging existing capabilities
• JMETC is coordinating with JFCOM to bridge test
  and training capabilities
• JMETC Users Group provides an open forum to
  present emerging requirements as well as new
  technologies capabilities
• Next JMETC Users Group 24-26 March, San Destin, FL

40
JMETC Program Points of Contact

• JMETC Program Manager Chip Ferguson
• chip.ferguson_at_osd.mil
• 703-604-0350 x138
• JMETC Principal Deputy PM Bruce Bailey
• bruce.bailey_at_osd.mil
• 703-604-0350 x144
• JMETC Senior Technical Advisor George Rumford
• george.rumford_at_osd.mil
• 703-601-5233
• JMETC Lead Systems Engineer Ryan Norman
• ryan.norman_at_osd.mil
• 703-604-0350 x146
• JMETC Operations, Planning Support Marty
  Arnwine
• martemas.arnwine_at_osd.mil
• 703-604-0350 x141