Joint Simulation System JSIMS and The High Level Architecture Runtime Infrastructure Ms' Laura D' Kn

1
Joint Simulation System (JSIMS) andThe High
Level Architecture Runtime Infrastructure Ms.
Laura D. Knight, SESJSIMS Alliance Executive
26 Mar 2001
2
Briefing Outline

• Background
• Architecture Integration Approach
• HLA and JSIMS
• Summary

3
JSIMS Program Management
JSIMS PM Mr. James M. Skurka, SES (USA)
JSIMS Requirements Control Board Chair MG
Scott Wallace (USA)USJFCOM JWFC
Executive Agents (EA)
Alliance Executive Office (AEO) Laura Knight,
SES (USN)
Development Agents (DA)
USN DA Maritime CDR Jeff McCampbell (USN)
USA DA WARSIM/WIM COL Randy Ball (USA)
USAF DA NASM Col Phil Faye (USAF)
USMC DA COL Joe Buranosky (USMC)
NSA DA JSIGSIM Mr. John Riordon
DIA DA DOMINO Mr. Peter Starr
NRO DA NATSIM LtCol John Tillie (USAF)
DMSO DA RTI COL Forrest Crain (USA)
Joint DA Joint Models CDR Jim Booth (USN)
4
JSIMS Program Management
JSIMS PM Mr. James M. Skurka, SES (USA)
Executive Agents (EA)
JSIMS Reqts Control Board
Alliance Executive Office (AEO)
Development Agents (DA)
USA DA WARSIM/ WIM
USN DA Maritime
USAF DA NASM
DMSO DARTI
USMC DA
Joint DA Joint Models
NSA DA JSIGSIM
DIA DA DOMINO
NRO DA NATSIM
5
JSIMS Development Partners
JSIMS Maritime --San Diego, CA Maritime Domain
Joint SIGINT Simulation (J-SIGSIM) -- Ft Meade,
MD Signal Intelligence, BTG
National Simulation (NATSIM) -- Chantilly,
VA National Intelligence Systems Veridian/MRJ
National Air and Space Model (NASM) -- Hanscom
AFB, MA Air and Space Domain, Raytheon
DIA Object Oriented Model for Intelligence
Operations (DOMINO) -- Bolling AFB, Wash.,
DC National Intel Process Modeling, Veridian/MRJ
ESC
NSA
NRO
DIA
DMSO
SPAWAR
High Level Architecture (HLA) --
Alexandria, VA Architecture, SAIC
JIOC
MARCORSYSCOM
Joint
STRICOM
NASM Joint Operations ISR Simulation (JOISIM)
-- San Antonio, TX Airborne Sensors, JIOC/CACI
USMC DA -- Orlando, FL USMC Requirements VISICOM
Warfighters Simulation (WARSIM) -- Orlando, FL
Land Domain, Lockheed-Martin WARSIM
Intelligence Module (WIM) -- Orlando, FL Tactical
Intelligence, Veridian/MRJ
JSIMS Joint DA -- Orlando, FL Joint Domain, TRW
6
Program Integrated Master Schedule

2003
2004
2007
2000
2001
2002
2005
2006
Major Milestones (FY)
1
2
3
G
B
Federate Integration
Key Joint/User OT Event
Federation Integration
1
2
3
4
5
Systems Test
(Feb 02)
(Mar 02)
Block 1 (Version Release 1.0)
User Events
- Functional Assessments
(Oct 01)
- System Functional Assessment
- Post VRM System Validation Events
(1 Apr - 15 Nov 02)
OTE Events
- Operational Test Event Observation
- DT/OT
Validation Event Training Audience (Nov 02)
IOC Event (USJFCOM Exercise)
(15 Nov 02 - 8 Mar 03)
- JTASC Exercise Prep w/JSIMS
Unified Endeavor Exercise
- Multi-Service OTE (MOTE)
(8 - 17 Mar 03)
IOC Decision
Block 2 (Version Release 2.0)
Block 3 (Version Release 3, tbd)
(Mar 03 - 05)
Version Release 3.0
(Sep 04 - 06)
Version Release 4.0
7
JSIMS Blocks
FY01
FY02
FY03
FY04
FY05
FY06
FY07
FY08
V1.0
V3.0
V5.0
V2.0
V4.0
Mar 02
Dec FY04
BLOCK 1 (Version 1.0)
"IOC"
Sep 01
Sep 03
Sep 05
BLOCK 2 (Version 2.0)
"Service/Agency Legacy
System Replacement"
Basis for 20-year LCC
P3I
Mar 03
Mar 05
BLOCK 3 (Version 3.0 ?)
"Theater Operations
Enhancements"
Combined
Combined
Combined
B 1 Review,
B 2 MS C,
B 1 MS C,
B 2 MS B
B 3 Review
B 2 Review,
Aug 01
Feb 05
B 3 MS B
Aug 03
B 3 MS A
Jun 02
BLOCK IV and beyond
to be determined
Development
Operations and Support
Block 2 is basis for 20-year
life cycle costs
8
Briefing Outline

• Background
• Architecture Integration Approach
• HLA and JSIMS
• Summary

9
Components of JSIMS

• Common Libraries
• Common Component SimulationEngine
• Common Algorithm Support Serv.
• Synthetic Natural Environment
• Security Common Services
• Runtime Infrastructure
• Support Federates
• C4I Adapters
• Federation Control Manager
• Technical Control
• Common Component Workstation
• Applications
• Civil Environment DatabaseGeneration Tool
• Synthetic Natural EnvironmentDatabase Generation
• Workstation Server
• Workstation Tools
• Security Out Guard

• Domain Federates
• JSIMS Maritime Domain
• Joint Simulation
• National Air and Space Model (NASM)
• Joint Information Operations Center Operation,
  Intelligence, Surveillance, and Reconnaissance
  (JOISIM)
• Civil Environment Battlespace
• Warfighters Simulation (WARSIM)
• Warfighters Simulation IntelligenceModule (WIM)
• Joint Signals Intelligence Simulation (JSIGSIM)
• National Simulation (NATSIM)
• DIA Object Oriented Model of Intelligence
  Operations (DOMINO)

10
Architecture of JSIMS
J-SIGSIM
DOMINO NATSIM WIM
Model
Model
SNE
JCL
Sim Engine
RTI
RTI
Upper Enclave
High Level Architecture Connections
RTI
Scenario Generation Exercise Control Unit
Control Evaluation and Reporting
Workstation Federate
Workstation Server
Tool
Client Infrastructure
Server Infrastructure
Client Infrastructure
Client/Server Connections
CE DOMINO Joint JOISIM JSIMS-M NASM WIM
WARSIM
RTI
Lower Enclave
High Level Architecture Connections
RTI
Scenario Generation Exercise Control Unit
Control Evaluation and Reporting
Workstation Federate
Workstation Server
Tool
Client Infrastructure
Server Infrastructure
Client Infrastructure
Client/Server Connections
11
Basic Integration and Test Premise

• First we make simple federates
• Then we make small federations
• size is a function of both the number of
  federates and the amount of functionality (size
  of FOM)
• Then we combine small federations to make bigger
  and bigger federations
• As we integrate it we test it.
• We bring the user in early by helping to conduct
  our tests
• Once it is all integrated we test it end-to-end
• Once we test it end-to-end we let the user test
  it end-to-end
• Applications are overlaid on this process

12
Basic Premise
13
Briefing Outline

• Background
• Architecture Integration Approach
• HLA and JSIMS
• Summary

14
HLA and JSIMS

• Targeting HLA Spec 1.3
• Extensive use of DMSO RTI 1.3 NG
• Using GOTS COTS to support development,
  integration and test
• Also using GOTS COTS as part of fielded system

15
JSIMS and the 1516

• Currently using 1.3, since summer of 2000
• A fundamental change to the 1516 can only be
  entertained at a Version Release Milestone
  boundary
• Conditions for transition
• DoD acceptance of 1516
• Rich community of support for 1516 (schools,
  text, people)
• Not interested in plowing new ground
• commercially or government developed RTIs
  available
• schools to hire from with 1516 experience
• Could be significant security driven challenges
  with a transition

16
JSIMS HLA RTI Support

• At a minimum we need support for 1.3 until all
  the conditions for a 1516 standard are met
• earliest development transition is Version
  Release Milestone 3.0
• VR 3.0 development- starts March 2003
• VR 3.0 is March 2005
• VR 2.0 still needs support through March 2006

17
Definition of JSIMS HLA RTI Support

• Ability to respond to software changes to support
  JSIMS
• do not believe software is fully matured
• do not believe RTI has been exposed to a demand
  similar to what is expected in JSIMS
• JSIMS specific tuning
• Full participation in JSIMS integration, test,
  user events, service/joint uses throughout
  program lifetime
• Continued participation as a JSIMS Development
  Agent and ability to support program demands
• Uninterrupted support of this quality requires a
  permanent institutional home for the HLA, at
  least for those customers that are already
  invested in RTI NG

18
Briefing Outline

• Background
• Architecture Integration Approach
• HLA and JSIMS
• Summary

19
Summary

• Bottom Line
• JSIMS need continuing support for RTI 1.3 NG
  through March 2006
• This support will require a long-term
  institutional home for the HLA in general, and
  specifically for RTI 1.3 NG