ESTHER G2 HLA Synthetic Environment Framework for Command Post Exercise

1
ESTHER G2HLA Synthetic Environment Framework for
Command Post Exercise

• DSA/SPOTI/ST/DSIO/SFEA

Lionel Khimeche lionel.khimeche_at_dga.defense.gouv.f
r
2
AgendaESTHER overviewESTHER vision for C4I-MS
interoperability ESTHER Technical
CapabilitiesESTHER Operational
CapabilitiesExperimentation with the SIRFuture
workConclusion
3
ESTHER overview
4
The SIR within the C4I chain
SICAT
XL
5
SIR Education Training

• Newly Fielded at Company and Regimental levels
• Until 2008, first degree in the Digitised
  Battlefield
• SIR Education in Army Schools and Regiments
• Students to be convinced to change paper map for
  computer
• Courses need to be interactive and demanding
• The SIR trainee is to be stimulated with a
  realistic simulated environment
• SIR - MS interoperability is to be addressed

6
ESTHER Mission
Build a framework providing common services to
C4I and Simulations for training education
purposes
ESTHER
Preparation Supervision
Animation Analysis
HLA
Network
Mail
Debriefing
Libraries
Reference Database
Technical Supervision
Operational Supervision
COMMUNICATION SERVICES
QoS
Frame Relay
VoIP
HLA
HLA
SICAT
LIVE
VIRTUAL
CONSTRUCTIVE
C4I
7
ESTHER Master Planning
2003
2002
2004
2001
2005
Mono-site
G1V1 Development Studies
Franco-German Exercise
Exp
Mono-site
G1V2 Development
Upgrade from RESIDENT JANUS HLA E-FOM WAN study
SIR msg automatic generation
Exp
Fr-Ge
ACE SimCom Terrain
Multi-sites
G2 Developpement
Exp
Training
RALGate GESI HLA
8
ESTHER vision for C4I-MS interoperability
9
ESTHER Vision for Interoperability
Address the Interoperability problematic in 2
stages
ESTHER
C4I
SIR
MS
JANUS

• Instantiation for SIR and JANUS through ESTHER

10
ESTHER Vision for Interoperability

• Convergence between ESTHER and TRM

ESTHER Model
C4I-MS Interoperability TRM
11
ESTHER Vision for Interoperability

• ESTHER approach particularities
• ESTHER seeks immediate interoperability between
  operational/legacy systems SIR, JANUS, GESI,...
• when TRM seeks mid or long term MS - C4ISR
  integration and alignment through Component
  Interoperability
• Leading to two characteristics
• Interface oriented, with a mix between message
  and HLA approaches
• Through a third block (ESTHER itself) providing
• Services to both worlds
• Integration capability for systems meeting
  Interface Requirements
• ESTHER FOM and SICAT message format
• Independence from evolutions from/to both sides

12
ESTHER Vision for Interoperability

• ESTHER Middleware layer between C4I and
  Simulation

SIR Network
ESTHER Services and Protocols
Simulation Network
13
ESTHER Technical Capabilities Data
DistributionC4I Simulation GatewayCommand
AgentMultisites communicationsGESI integration
14
Data Distribution Capability (1/2)

• In the area of Static interoperability, ESTHER
  aims at
• Defining exercise data
• Providing the various systems with their data
• Minimising manual input and Ensuring consistency
• Type of data handled
• ORBAT, Communication, weather, networks data,
• Distribution to Workstations via xml files
• ESTHER for exercise management
• SIR for ORBAT initialisation
• Simulation for synthetic environment
  initialisation
• Extension within ESTHER G2
• Integration of GESI

15
Data Distribution Capability (2/2)
16
C4I Simulation Gateway Capability (1/2)

• In the area of Dynamic Interoperability, aims at
  
• Stimulating the SIR at Coy and Battalion levels
• By extracting relevant data from simulation data
  flow
• Archiving message exchanges for analysis
• Type of data handled
• French Army message format SICAT V1.2
• SITREP, Intelligence, Logistic messages
• Reports (up) and Reference (down) messages
• Distribution to SIR via SMTP
• Extension within ESTHER G2
• Improvement of GUI to facilitate message
  generation process
• Addition of Leclerc Tank messages Location and
  Logistic

17
C4I Simulation Gateway Capability (1/2)
SICAT/SMTP

• Messages Handled
• SITREP/PTSITU
• SITEFF SYNSAN
• Intell Report
• InfoSITREF Own ENI
• Obstacle Report Modif
• Alarm
• Text
• PosAuto/XL
• LogAuto/XL
• PosManu/XL

SIR
ESTHER
JANUS
RTI 1.3 NG V6
18
Command Agent Capability (1/3)

• In the area of Dynamic interoperability, ECA aims
  at
• Minimising resources for exercise control
• By giving orders from C4I system to simulation
• To control Coy level neighbour force units (up to
  20 platforms each)
• Orders used
• Operation Order to extract Co-ordination Lines
• Order of movement Via an enriched Syntax Text
  Message
• Location and Logistic Request for automatic
  response
• ECA content
• Up to 10 Command Agents designed within ESTHER
  Exercise
• Order of Movement according to various formation
  geometries
• Computation via a dedicated ESTHER WorkStation

19
Command Agent Capability (2/3)

• ECA Generation process

20
Command Agent Capability (2/3)

• ECA imposed evolution of ESTHER FOM
• Creation of interactions to convey

1- The OpO the ECA Text Messages
2- The JANUS Movement Order
21
ESTHER Multisites Communications (1/3)

• Requirements
• Multisites Federation 2 to 5 sites
• Exercise with 2 000 Entities
• Distribution of Static (initialisation) and
  Dynamic (HLA ) Data
• ESTHER works on Reliable Mode
• A dedicated structure is needed to minimise
  Bandwidth
• One Reliable Distributor per LAN
• Initialisation Data Distribution on each LAN
• One local Fedex per LAN Multisite Flow sent
  only once
• Provided in ESTHER via ESTHER Gate

22
ESTHER Multisites Communications (2/3)

• ESTHER Gate

• Static data Flow

• Dynamic data Flow

23
ESTHER Multisites Communications (3/3)

• Technical trials proved the efficiency of ESTHER
  Gate
• Measurements on two sites and 6 federates

With ESTHER Gate 47 Kbit/s (50)
Without ESTHER Gate 131 Kbit/s (150)

• Flow is related to sites number no more to
  number of connected federates

24
GESI Integration in ESTHER (1/3)

• GESI (CAE GmbH)
• Client-Server Platform-Level Warfighting
  Simulation
• Designed to operate in standalone mode
• Integration into ESTHER
• Proof of ESTHER Capability in the Area of
  Interoperability
• Demonstrate Applicability of ESTHER Interface
  Requirements
• Static interoperability
• Dynamic interoperability
• Demonstrate Building and Execution of an
  Heterogeneous Federation JANUS, GESI SIR
  under ESTHER Supervision

25
GESI Integration in ESTHER (2/3)

• ESTHER Initialisation xml files fit most of needs
• However some static interoperability issues
  remained
• Order of battle Scenario
• Date/Time
• Management of opposite sides
• Location Data Export and Import - Co-ordinate
  system
• Solutions implemented to ensure data consistency
  between federates
• Use of common standards (co-ordinates)
• Limitations of range (ORBAT, Scenario, Date)
• Rules of exercise (Sides)

26
GESI Integration in ESTHER (2/3)

• GESI HLA adapter designed to fulfil ESTHER IR
• RTI, E-FOM, GRIM
• However dynamic interoperability issues remained
  
• Models coverage (different in JANUS and GESI)
• Entities definition (different in JANUS and GESI)
• Life form (different levels of aggregation)
• Minefield objects (different levels of
  aggregation)
• Time Management
• Solutions to ensure coherent federation execution
  
• ESTHER FOM amendments eg. AggregateMines for
  GESI
• Specific rules of federation eg. Mine
  detonation by Mine owners
• Main Problem remaining Entities definition
• To be solved by operational SME in both
  simulations

27
ESTHER Operational Capabilities
28
ESTHER Operational Capabilities

• Derived from the Technical Capabilities
• Main capability
• Training with the SIR
• This is what ESTHER was designed for (see
  Experimentations)
• but also (realised during Experimentation)
• Education to the SIR
• Doctrinal Studies on C4I impact
• Test Experimentation for C4I Interoperability
• Obtained via the combination ESTHER technical
  capabilities
• eg. ESTHER HLA Replay Message Generation
• or ESTHER Command Agent Message Generation
• With a good compromise of realism, resources
  needs and costs

29
Experimentations with the SIRFrench Infantry
School Janus Center French Armoured School Janus
Center
30
Infantry School Exercise
DISTAFF
ECA Neighbours
II
HICON
TRAINEES
LOCON
SIMULATION
1
2
3
7
8
4
5
6
?
Battle Group
Neigbours
OPFOR
31
Infantry School Exercise

• Where Infantery School Janus Center
• When From 16th to 20 th February 04
• Level Experimentation at Coy level (4 captains)
• Trainees Unit Commander from 2 REI
• Main Focus
• Using SIR messages
• Building recognised picture on the SIR
• Results
• High level of satisfaction from 2 REI
• SIR Stimulation from High and Low echelons
• Next SIR/ESTHER exercise for 2 REI planned in
  4th quarter

32
Armoured School Exercise
DISTAFF
X
HICON
ECA Neighbours
Voisins
TRAINEES
ANI/Joueurs
SIMULATION
1
2
3
12
13
14
4
5
6
7
8
9
10
11
15
16
17
BattleGroup
Neigbours
OPFOR/Civilian
33
Armoured School Exercise

• Where Armoured School Janus Center
• When From 8th to 12 th March 04
• Level Experimentation at Battalion level
• Trainees Battalion Commanders from Tactical
  Center
• Main Focus
• Using XL messages - Building recognised picture
• Using ESTHER Command Agent
• Results
• High level of satisfaction from Janus Center
• ECA effectiveness to save resources (Janus
  Operator for Neighbours)
• XL message to prepare SIR - SIT interconnection
• SIR/ESTHER exercise for 6/12 Regiment planned in
  3th quarter

34
ConclusionESTHER SummaryFuture Work
35
ESTHER Summary

• ESTHER is the result of a pragmatic approach
• Separate from the Armament Program approach
• Executed within a Short loop - Incremental
  development process
• In close relationships with Army End users,
  Experts, Staff
• Incorporating Lessons Learnt from Experimentation
  in actual conditions
• Despite the RT character
• Deployment for regular use in Infantry and
  Armoured JANUS Centres
• Evolutions and News applications identified for
  next future
• Impact on Fielding Process of Operational Systems
  SIR, SIT, ...
• One of the most significant efforts in training
  and education at battalion level with current C4I
  systems

36
Future Work CALIPSO

• Subject
• Address the issues of Alignment of C4I and
  Simulation Systems in the Area of Training and
  Decision Making
• Target
• Provide Guidance needed by French Army for
  definition of C4I and Simulation Operational
  Systems of the next decade
• Expected Results
• Identification of C4I/Sim Interchange
  Requirements
• Assessment of C4I/Sim Convergence Alternatives
• Definition of C4I/Sim Common Reference Model for
  interoperability
• Definition of C4I/Sim Common Architecture
• Co-operation
• Consistency with NATO Work (MSG-027)

37
Thank You !
38
Architecture ACE
SIR Reg
SMTP flow HLA flow
OpO
TOP Server
Situation (HLA)
Gateway
Com Model
SIR Coy
DEM XL
POS/LOG XL
Mail
SICAT msg ACE Order
CR ACE
ACE Order (HLA)
Historic OpO
PBE /ACE
PBE/GUI
Gateway
Path (HLA)
Situation (HLA)
Situation (HLA)
JANUS