Battle Lab Collaborative Simulation Environment BLCSE Transition to

Battle Lab Collaborative Simulation Environment (BLCSE) Transition to One. SAF Bob Kleinhample ARCIC, JAMSD TICC Section Manager, SAIC 17 January, 2008 1

Agenda q What Is The Battle Lab Collaborative Simulation Environment (BLCSE)? q Why Adopt One. SAF q BLCSE Enterprise Change q Managing One. SAF Adoption q Technical Integration Events (TIEs) Battle Lab Collaborative Simulation Environment (BLCSE) Transition to One. SAF 2

What is BLCSE? Battle Lab Collaborative Simulation Environment (BLCSE) Transition to One. SAF 3

Why Adopt One. SAF q Dynamics of ARCIC Experimentation and Studies – Short prep timelines - Rapid Entity Composability - Government owned/open source – Large Integrated Warfight – Scalability q Reduce Integration Risk - Homogeneity OTB One. SAF Replace Core Entity Driver Battle Lab Collaborative Simulation Environment (BLCSE) Transition to One. SAF 4

Managing One. SAF Adoption q Overcome Change – Battle Lab Acceptance – Replacement of Models/Functions – Configuration Management - Rigid to Flexible q 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 One. SAF 5

BLCSE Technical Integration Events (TIEs) q Test Objectives and Schedule – TIE-1 (Feb 07): Introduce HLA (One. SAF and Modeling Architecture for – – – Technology, Research, and Experimentation (MATREX) RTI) in the BLCSE Federation. TIE-2 (May 07): Stress the Federation to 5 K Medium Resolution (MR) Entities. TIE-3 (Jul 07): Stress to 10 K MR Entities and Test Cluster Configurations. TIE-4 (Aug 07): Continue with TIE-3 Objectives TIE-5 (Oct 07): Stress to 25 K Entities, add One. SAF based Reconfigurable Simulators, add One. SAF v 1. 5, and test Ft. Bliss and White Sands Missile Range (BLSMR) Terrain Database. TIE-6 (Feb 08): HLA One. SAF and One. SAF hosted ACRT interoperability with DIS OTB based environment. Test One. SAF 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 One. SAF 6

One. SAF Transition and TIE Objectives q Entity Load. BLCSE routinely supports up to a Brigade Combat Team with opposing forces ~ 40 K MR entities. – Immediate future: ~25 K MR entities. Combined Arms Battalion (CAB) in heavy contact and another CAB in medium contact. – Can One. SAF achieve 25 K MR entities and maintain a stable HLA federation? q One. SAF Integration with Other Federates – One. SAF Testbed Baseline (OTB), Fire Simulation (Fire. Sim), Advanced Tactical Combat Model (ATCOM), Extended Air Defense Simulation (EADSIM), and Advanced Concepts Research Tool (ACRT). – Test using nine technical integration threads. q One. SAF Integration over the Wide Area Network (WAN) – High Level Architecture – Geographically distributed network q Replace other OTB federation environment functions: e. g. Effects Server, SA Sever, Dynamic Terrain Server. Battle Lab Collaborative Simulation Environment (BLCSE) Transition to One. SAF 7

One. SAF Transition and TIE Objectives q Hardware and Software Configurations – Gain data to support site infrastructure decisions – Test performance on hardware platforms – Test performance on Cent. OS § ARCIC will implement One. SAF on hundreds of hardware platforms. If One. SAF is stable on Cent. OS then significant cost savings. – Test One. SAF Cluster Configurations – ID and Test One. SAF configuration settings Battle Lab Collaborative Simulation Environment (BLCSE) Transition to One. SAF 8

Useful Results To Date q Operating System. – One. SAF is stable on Cent. OS v. 4. 4 q Cluster Configurations - ID factors that contribute towards optimal cluster design. – MCT uses most RAM – Sim. Core Requires greatest processor capability – Interop can run on common hardware platform q One. SAF Software Configuration (Standard Settings) – Produce and refine configuration setting document. (One. SAF. properties (scenario file path, terrain file path), MTU size, java version, interop. config. xml file (federate name, DDM), . bashrc (path settings, alias), etc. ) – Cent. OS v 4. 4 and One. SAF v 1. 0. 2 - Produced – Cent. OS v 5 and One. SAF v 1. 5. 1 - Under Development. q q q One. SAF Own-ship model works well within the ACRT. Produced One. SAF Installation and User Manual Entity Load. – 20, 255 entities using One. SAF v 1. 0. 2 Not stable for very long. – Expect One. SAF v 1. 5. 1 to resolve stability issues. Battle Lab Collaborative Simulation Environment (BLCSE) Transition to One. SAF 9

FY 08 -09 One. SAF-Supported Efforts 3 CE One. SAF 4 Q FY 07 Base JUL AUG 1. 5 SEP 1. 0. 1 1. 0. 2 2 Q FY 08 2. 0 JAN OCT NOV DEC 1. 5 FEB 3 Q FY 08 MAR APR MAY JUN JUL 1 Q FY 09 2 Q FY 09 AUG SEP OCT NOV DEC JAN FEB MAR 3. 0 2. 5 2. 1 1. 5. 1 4 Q FY 08 OF IE 5 7 6 8 9 A Qtr IE BLCSE TIE 3 ARCIC FFID 6 5 4 TLC 7 B 9 8 C 10 Train-Up FDT&E ACDEP Scenario Behavior Phy Mdls PM FCS BCT /LSI TRAC 1 Q FY 08 AAEF D HBCT Co Entity Level Aviation CWD EWF FCS CAB AAEF E OF 08 EWF FCS BCT CO Level Move/Shoot FSE SO-1 JEFX 08 Core Prg ATEC TFT OF 08/UR Ph 3/JEFX 08 IV 1 IMT SO-1 LUT 10

Summary Assess One. SAF 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 One. SAF 11

Backup Battle Lab Collaborative Simulation Environment (BLCSE) Transition to One. SAF 12

TIE 5 Site Participation Battle Lab Collaborative Simulation Environment (BLCSE) Transition to One. SAF 13