C4I Applications Utilizing Embedded Simulation Infrastructure February 7,2003 Dr. Gene Layman John Daly Naval Research Laboratory 202 767-6873 202 767-6766 [e-mail] [e-mail]

1
C4I Applications Utilizing Embedded Simulation
InfrastructureFebruary 7,2003Dr. Gene
LaymanJohn DalyNaval Research Laboratory202
767-6873202 767-6766layman_at_nrl.navy.miljjdaly_at_n
inja.nrl.navy.mil
2
Adaptable C4I Operational Domains

• Complementary COPs
• Overlays (time projected activity)
• Inserted objects (CBR Clouds)
• Other views of battlespace
• EM space
• Acoustic space
• IW space
• Network space

C4I

• Information/processes beyond human cognition
• Geospacial information other than track data
• May be multidimensional (2-3D plus time)
• Displayed in COP as adjunct data/objects
  overlays
• Displayed in SIMCOP as alternate views in
• Time base
• Visualization (3-D etc.)
• Function (control/analysis/planning)

3
Tactical C4I Decision Support

• Tactical vice Deliberative Planning process
• Situational Assessment
• Simulation/C4I TDA used to evaluate Course of
  Action
• Requires Scenario Generation tools and capture of
  real world C4I picture/ integration into C4I COP
• Need to create electronic plans/scenarios for
  evaluation by simulation TDA and distribution to
  other users
• Timeliness of results critical to tactical
  relevance
• Simulation/C4I TDA used to produce C4I Adaptable
  Operational Domains of information for analysis
• Simulation/C4I TDA used to show effects of
  current operations and planning options

4
Embedded Simulation Infrastructure (ESI) Program
Objectives

• Create a Modeling Simulation Environment in the
  DII COE/NCES for development of simulation based
  Tactical Mission Applications.
• Link simulated data to DII COE Services
• Develop additional DII COE MS Services
• Aggregate services in HOST APPLICATIONS
• Distribute functionality between MS and C4I
  systems.
• Proof-of-concept C4I Mission Applications
• Weapons of Mass Destruction Analysis (WMDA)
• C4I Team Training System (SPAWAR)
• Create DII COE Modeling and Simulation Software
  Developers Kit (MS SDK)

5
GSSC-M WMDA Mission ApplicationSegment/COE
Architecture
WMDA Mission Application
COP
WMDA Segment
Mission Editor

• Common Services
• Unique Services

APIs
HPAC Server
Common Support Applications

Future Home For ESI SVCS?
MS
MS Excel
MS Word
JMV
Common Operational Environment

Infrastructure Services
OODBMS
TMS
UCP
HLA RTI

Kernel
Solaris OS
NT OS
- Primary COE Services used by WMDA
XXXX
6
Mission EditorRequirements

• Create Manage Scenarios
• US, Threat, Others
• Real, Slower Faster than real time operations
• Represents Physical Environments
• Sea, Undersea, Air, Land, Space, weather
• Uses Common Data, Standardized Models
• TMS data structures
• Standard messages
• Database information ( XML etc)
• Connects Synthetic Battle Forces to GCCS
  Applications
• DII COE Services
• Mission Applications

7
Scenario Generation
Waypoints
Direction Of movement.
Platform Position at Reference Time (11 08253Z
JAN 02)
Midpoints
8
Scenario Editing
9
COP CaptureMS Service
Purpose capture real world tracks and provide
them to an application for initialization time
projections.

• Select Tracks of Interest (Forces, Platforms,
  Track Types, etc).
• Select geographic location (lat/long and
  circumference area).
• Extract data from TMS.
• Set DTG.
• Provide to an Application as
• Simulated Tracks Objects (TMS-4 objects).
• Message Objects (OTH Gold, RPR, DIS).

10
WMDA Mission Application Generate and Display
the Resulting NBC Analysis
HPAC Server
Simulation COP
Dynamic Run
SIM-COP Display
SIM-COP Generator
(Track Objects)
Archive
Replay
Debrief Author
Archive/Replay
Create the Mission Run
Model Run the Plan Display the Results
11
NBC Common Operational Picture (COP)Global
Command and Control System (GCCS)
10 DEC 02 exercise at the Joint War Fighting
Center
12
C4I-MS Host Application.

• Standard ESI MS Application architecture.
• Provides C4I functions tailored for MS
  Application
• Situation Assessment - Visualization
• COA Analysis - Operation analysis
• Planning - Information Processing
• Readily hosts other relevant NBC simulations.
• Models Simulations can be developed by non-C4I
  experts.
• Composible, from
• C4I MS services
• To aggregate Host Application frameworks for use
  type
• Reuse of components from other Mission
  Applications.

13
C4I MS Host Application Definition
A C4I (e.g., GCCS, GCCS/M) application shell that

• Aggregates a set of COE and ESI MS services
  relevant to a particular C4I Mission. (e.g., WMD
  Defense)
• Hosts 1 or more simulations or processes that
  perform specific Mission analysis. (e.g., Down
  Wind Hazard Assessment, Urban Contamination
  Analysis, lethality etc.)
• Readily modifiable to host additional simulations
  of the same category. (e.g., NBC Sensor Fusion,
  Strike Planning)

14
MS Host Application Architecture For Embedded
Simulations.
Example COA Analysis or Planning Application
Simulation (Server)
Simulated Force Generation
SIM-COP
Initialization Client
Output Client
Reusable MS functions
Dynamic Run
Runtime Client
Archive/Replay/ Debrief
SIM links to C4I services data bases.
COE Applications Services
C4I Data Bases
15
WMD Defense Host Application Architecture

Sensor Planning/Fusion (e.g., JWARN)
Urban/Zone Contam. Anal. (e.g., CT Anal).
Down Wind Hazard Analysis ( HPAC)
Weapons Effects (e.g., MEA)
Embedded Simulations (Examples) Mission Segmen
ts Standard MS Services COE Data Bases

Zone Defense
NBC COP
COA Analysis
Planning
Clients
Clients
Clients
Clients

Mission Editor
Dynamic Run
Archive/Replay /Debrief
Data Base Access
SIM COP
Visualization
COA Analysis
Comms.
Applications Services

MS Services
COMMS
JMV
TMS
C4I Data Bases
16
The ESI Program Products

• An established Embedded Simulation Architecture
  used in C4I Application designs
• WMDA Mission Application
• C4I Team Training System
• GCCS/GCSS/I3 Embedded (operator level) Training
• Reconstruction Segment
• LATR/C4I
• MS DII COE SDK FY03
• Initial Host Application Functionality
• WMD
• Training

17
The ESI and XMSF

• New capability in C4I, harmonize now with
  emerging MS architectures
• XML already used for new MS specific data for
  ESI services
• Composible Architecture fits well with XMSF
  paradigm
• Requires well defined models and data
• Scales well from embedded to distributed between
  C4I and MS systems.

18
END