Battle Lab Collaborative
Simulation Environment
(BLCSE) Transition to OneSAF
Bob Kleinhample
ARCIC, JAMSD
TICC Section Manager, SAIC
17 January, 2008
Agenda
Is The Battle Lab Collaborative Simulation Environment
What
(BLCSE)?
Why Adopt OneSAF
BLCSE Enterprise Change
Managing OneSAF Adoption
Technical Integration Events (TIEs)
Battle Lab Collaborative Simulation Environment (BLCSE) Transition to OneSAF
2
What is BLCSE?
Technical Management and Standards Technical Management
CCB BLCSE TCC TICCs & Standards
Event Life Cycle
CES MC2
Radios EADSIM Distributed
BEST WECM Simulation
Planning, Preparation, Execution, Post Event Analysis
ACRT OneSAF
CMS2
SSE FireSim Component
Study
TRAC Exp Reports
DCMP
Support Analysis
System Data
(ESS) Collection Study Component
and Analysis Plans
VOIP File & Application
Sharing Data
VTC Collaboration &
Access to Data
Component
Ft. Lee WSMR
Ft. Sill Ft. Bragg
Ft. Belvior Ft. Benning
Others Ft. Leavenworth
Ft. Monroe Ft. Leonard Wood Network
Ft. Bliss
Ft. Knox Ft. Gordon SMDC Ft. Huachuca Ft. Rucker Foundation
Security Agreements
Battle Lab Collaborative Simulation Environment (BLCSE) Transition to OneSAF
3
Why Adopt OneSAF
Dynamics of ARCIC Experimentation and Studies
– Short prep timelines - Rapid Entity Composability
- Government owned/open source
– Large Integrated Warfight – Scalability
Reduce Integration Risk - Homogeneity
Homogeneity
OTB OneSAF
Replace Core Entity Driver
Battle Lab Collaborative Simulation Environment (BLCSE) Transition to OneSAF
4
Managing OneSAF Adoption
Overcome Change
– Battle Lab Acceptance – Replacement of Models/Functions
– Configuration Management - Rigid to Flexible
Management Structure
– BLCSE Technical Configuration Controller (TCC)
– BLCSE Engineering Support Team (BEST)
– BLCSE Technical Integration Configuration Control Teams
(TICCs)
Battle Lab Collaborative Simulation Environment (BLCSE) Transition to OneSAF
5
BLCSE Technical Integration Events (TIEs)
Test Objectives and Schedule
– TIE-1 (Feb 07): Introduce HLA (OneSAF and Modeling Architecture for
Technology, Research, and Experimentation (MATREX) RTI) in the
BLCSE Federation.
– TIE-2 (May 07): Stress the Federation to 5K Medium Resolution (MR)
Entities.
– TIE-3 (Jul 07): Stress to 10K MR Entities and Test Cluster
Configurations.
– TIE-4 (Aug 07): Continue with TIE-3 Objectives
– TIE-5 (Oct 07): Stress to 25K Entities, add OneSAF based
Reconfigurable Simulators, add OneSAF v1.5, and test Ft. Bliss and
White Sands Missile Range (BLSMR) Terrain Database.
– TIE-6 (Feb 08): HLA OneSAF and OneSAF hosted ACRT interoperability
with DIS OTB based environment. Test OneSAF v 1.5.1 performance
and ability to meet Complex Web Defense objectives for Stryker unit in
Urban Operations.
Battle Lab Collaborative Simulation Environment (BLCSE) Transition to OneSAF
6
OneSAF Transition and TIE Objectives
Load. BLCSE routinely supports up to a Brigade
Entity
Combat Team with opposing forces ~ 40K MR entities.
– Immediate future: ~25K MR entities. Combined Arms Battalion (CAB) in
heavy contact and another CAB in medium contact.
– Can OneSAF achieve 25K MR entities and maintain a stable HLA
federation?
OneSAF Integration with Other Federates
– OneSAF Testbed Baseline (OTB), Fire Simulation (FireSim), Advanced
Tactical Combat Model (ATCOM), Extended Air Defense Simulation
(EADSIM), and Advanced Concepts Research Tool (ACRT).
– Test using nine technical integration threads.
OneSAF Integration over the Wide Area Network (WAN)
– High Level Architecture
– Geographically distributed network
Replace other OTB federation environment functions: e.g.
Effects Server, SA Sever, Dynamic Terrain Server.
Battle Lab Collaborative Simulation Environment (BLCSE) Transition to OneSAF
7
OneSAF Transition and TIE Objectives
Hardware and Software Configurations
– Gain data to support site infrastructure decisions
– Test performance on hardware platforms
– Test performance on CentOS
ARCIC will implement OneSAF on hundreds of hardware platforms. If
OneSAF is stable on CentOS then significant cost savings.
– Test OneSAF Cluster Configurations
– ID and Test OneSAF configuration settings
Battle Lab Collaborative Simulation Environment (BLCSE) Transition to OneSAF
8
Useful Results To Date
Operating System.
– OneSAF is stable on CentOS v.4.4
Cluster Configurations - ID factors that contribute towards optimal cluster
design.
– MCT uses most RAM
– SimCore Requires greatest processor capability
– Interop can run on common hardware platform
OneSAF Software Configuration (Standard Settings)
– Produce and refine configuration setting document. (OneSAF.properties (scenario
file path, terrain file path), MTU size, java version, interop.config.xml file (federate
name, DDM), .bashrc (path settings, alias), etc.)
– CentOS v4.4 and OneSAF v1.0.2 - Produced
– CentOS v5 and OneSAF v1.5.1 - Under Development.
OneSAF Own-ship model works well within the ACRT.
Produced OneSAF Installation and User Manual
Entity Load.
– 20,255 entities using OneSAF v1.0.2 Not stable for very long.
– Expect OneSAF v1.5.1 to resolve stability issues.
Battle Lab Collaborative Simulation Environment (BLCSE) Transition to OneSAF
9
FY08-09 OneSAF-Supported Efforts
4Q FY07 1Q FY08 2Q FY08 3Q FY08 4Q FY08 1Q FY09 2Q FY09
3CE OneSAF
2.0
Base JUL AUG SEP
1.5 OCT NOV DEC JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC JAN FEB MAR
2.1 2.5 3.0
1.0.1
1.5 1.5.1
1.0.2
OF
IE 5 6 7 8 9
A B C
Qtr IE
BLCSE TIE 3 4 5 6 7 9 10
8
FFID TLC Train-Up
ARCIC
FDT&E
ACDEP AAEF AAEF
D
CWD EWF E
OF08 EWF
Scenario HBCT Co
TRAC
FCS CAB FCS BCT
Behavior Entity Level CO Level
Phy Mdls Aviation Move/Shoot
FSE
BCT /LSI
PM FCS
SO-1 TFT
JEFX08 OF 08/UR Ph3/JEFX 08
Core Prg IV 1 IMT
ATEC SO-1 LUT
Summary
Assess OneSAF within intended environment
Incremental adoption approach to learn
employment
Replace OTB as Core Entity Driver
Inform the community
See Paper # 7477
Battle Lab Collaborative Simulation Environment (BLCSE) Transition to OneSAF
11
Backup
Battle Lab Collaborative Simulation Environment (BLCSE) Transition to OneSAF
12
TIE 5 Site Participation
Battle Lab Collaborative Simulation Environment (BLCSE) Transition to OneSAF
13