TECHNICAL CHALLENGES in JMRM

1
TECHNICAL CHALLENGES in JMRM

• Donna S. Womble, Ph.D.
• JTLS Entity Level Server
• Rolands Associates, Corporation

2
WHAT is JMRM?

• JTLS Representation
• Covers theater area of operations
• Includes all relevant actors
• Requires time/distance coordination at theater
  level

• JCATS Representation
• multiple interest areas
• polygonal
• may be geographically separate

3
WHAT is the ELS?

• JTLS component program which disaggregates ARUs
  into the representative combat system entities
• Entities available over the entire game board, or
  filtered by Command Hierarchy
• Purpose of the ELS provide a consistent
  representation of individual combat systems

4
JMRM version 1.0

• Scheduled release in July 2007
• Principal Federates JTLS and JCATS
• Several successful JMRM Exercises
• (US JWFC) before introduction of ELS

5
JMRM ARCHITECTURE
JTLS CEP
SDR
SDC
ACRONYM KEY AARC After Action Review
Client CEP Combat Events Program COP Common
Operational Picture ELS Entity Level
Server EODA ELS Object Data Authority JEM
JTLS External Module (C4I Interface Client) JODA
JTLS Object Data Authority JHIP JTLS HLA
Interface Program JXSR JTLS XML Serial
Repository MDP Message Delivery Program OEC
Order Entry Client OMA Order Management
Authority PACER Federation Time-Keeper SDC
Scenario Data Client SDR Scenario Data
Repository SYNAPSE Synchronized Application
Preference Service WHIP Web-Hosted Interface
Program XMS XML Message Service
ELS
OEC
Listener Clients
JODA
AARC
EODA
JEM
C O P
PACER
JHIP
JTLS WEB Services JXSR XMS OMA SYNAPSE MDP Apache
Server
HLA RTI
JCATS Bridge
JCATS Simulation
JTLS WHIP workstations
JCATS Player Clients
6
ENTITY-LEVEL Data Feeds

• JMRM Federation Operates using the HLA Run-Time
  Infrastructure (RTI) for object distribution
• JTLS-only entities published on the EODA
• EODA is simply another JODA instance which
  serves
• the entity-level objects created by the ELS
• EODA Listener clients may be developed by any
  JTLS end-user wishing to receive entity-level
  objects

7
MORE on Data Feeds

• HLA data feed is required for time sensitivity
• Necessary for federated simulations like JMRM
• (e.g. JTLS ?? JCATS)
• Slow throughput for relatively large numbers of
  entities
• To improve efficiency, entities from ELS must be
  published together in a list associated with
  their owning unit or target
• EODA data feed suitable for listener clients
• No time coordination
• Fast throughput for very large numbers of
  entities
• Entities published as individual objects

8
ENTITY-LEVEL OBJECT STRUCTURES
EODA Objects
HLA-RTI
JTLS Aggregate Unit
Entities appear in Lists
Hierarchical Individual Entities
Command Object 1
Aggregate Unit
CS Entity 1 CS Entity 2 CS Entity 3 CS Entity
4 CS Entity 5 CS Entity 6 CS Entity 7 CS Entity
8 CS Entity 9 CS Entity 10
Command Object 3
Command Object 2
CS Entity 6
CS Entity 1
CS Entity 7
CS Entity 2
CS Entity 8
CS Entity 3
CS Entity 9
CS Entity 4
When UNIT ownership is passed from JTLS to JCATS,
then JCATS creates an individual entity for each
item in the list
CS Entity 10
CS Entity 5
9
Why Two Data Feeds?

• Optimize ELS Execution speed
• To comply with JMRM HLA Federation Requirements
• 3. To provide JTLS end-users with alternatives
  for obtaining Entity-Level objects from JTLS

10
JMRM Technical Challenges?

• 1. Scenario Data correlation between models
• JTLS and JCATS combat system descriptions
• 2. Creation of template layouts / formations
• required to run the ELS

11
Define a Combat System

• Standard Database (sdb32) contains
• 100 generic combat system types

• Number of combat system types for sdb32 is
  virtually unlimited

12
1. DATA Correlation

• Example from SDB32
• Consider a ground SEAL PLATOON Tactical Unit
  Prototype (TUP)
• Composed of 20 Entities
• HOW ARE they described by each model?

?
13

14
Question Data Correlation,How big is this job?
(Continuing with SDB32 scenario)

• JTLS
• 432 TUPS
• 940 HUPS
• 342 Target subtypes
• 100 Combat Systems
• TOTAL number of ELS entities 1.2 Million!
• (_at_ game time Zero)

• JCATS
• Virtually unlimited number of unique entity types
  in the scenario database

ANSWER Gigantic JMRM solution Unit Generation
Utility (UGU)
15
RESULT

• At PLATOON Level, 4 grows into 9 when you move
  from JTLS to JCATS
• Inflationary Data correlation !

16
JMRM Technical Challenges?

• 1. Scenario Data correlation between models
• JTLS and JCATS combat system descriptions
• 2. Creation of template layouts / formations
• required to run the ELS

17
2. Creating ELS Templates
(Template formation / spatial layout of
entities)

• ELS Requirement at least 1, up to 4 templates
  for every TUP (Agg Unit) and HUP (HRU)
• Up to 4 Postures Defend, Attack-Mounted,
  Attack-Dismounted, Move
• Single template may be used for multiple postures
• Automatic (run-time) Template Creation under
  development
• Default Ground formations Circle, Wedge, Vee,
  Mob
• Formation choice dependent upon units combat
  function and its current posture

18
More on Creating Templates

• New GUI tool will be released with v.3.2
• Release scheduled for November, 2006
• Standalone Java application to graphically create
  templates
• Java Template Builder (JTB)
• Automated template generation within the ELS is
  currently under development

19
Q How many templates?
(Example SDB32)

• 432 TUPs
• 940 HUPs
• Multiply by 4 postures
• 5488 (maximum)

• A Hand building unique templates for every Unit
  Prototype is extremely time consuming

20
Where do we go from here?

• ELS Current Development Status
• ELS Near-Term Goals
• ELS Long-Term Goals

21
ELS Current Status

• Implementation completed, testing underway for
• Ground Units
• HRUs
• Target Types (3 so far)
• SAM / AAA
• SSM
• Aircraft Shelters

22
ELS Near-term Goals

• Create Default templates based on unit function
  and current posture automatically
• Truck Convoys (50 complete to date)
• Rail and Barge convoys later
• Individual aircraft within aggregate Air Missions

23
ELS Long-term Goals

• Coordinated Damage (e.g. JCATS fires on a JTLS
  mech unit. When a UAV Sim designates a specific
  tank as target, then JTLS CEP ARU is minus one
  tank, ELS correctly represents the right tank).
• Real-time Template Adjustment based on underlying
  terrain (e.g. no river or other barrier crossing
  through a template formation)

24
Long-term Goals

• Non-movement Movement
• Stationary unit Port Facility, Depot, Airbase
• Simulate trucks being loaded
• Aircraft movement on airfields
• Et Cetera
• JSTARS !

25
Long-term Goals

• Creation and Delivery of a 3-D Graphical Display
  (EODA client)
• Currently testing ELS with a rudimentary 2-D
  visualization tool for debugging purposes
• Contingent upon funding, this tool may be
  released as a CAX tool

26
Questions
27
Donna S. Womble, Ph.D.Rolands Associates,
Corporation500 Sloat AvenueMonterey,
California1 831-373-20251 888-FOR-JTLSwww.ROL
ANDS.com