1 / 13

Battle Lab Collaborative Simulation Environment (BLCSE) Transition to OneSAF Bob Kleinhample

Battle Lab Collaborative Simulation Environment (BLCSE) Transition to OneSAF Bob Kleinhample ARCIC, JAMSD TICC Section Manager, SAIC 17 January, 2008. Agenda. What Is The Battle Lab Collaborative Simulation Environment (BLCSE)? Why Adopt OneSAF BLCSE Enterprise Change

greenec
Download Presentation

Battle Lab Collaborative Simulation Environment (BLCSE) Transition to OneSAF Bob Kleinhample

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

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

  3. What is BLCSE?

  4. 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

  5. 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)

  6. 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.

  7. OneSAF Transition and TIE Objectives • Entity Load. BLCSE routinely supports up to a Brigade 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.

  8. 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

  9. 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.

  10. FY08-09 OneSAF-Supported Efforts 4Q FY07 1Q FY08 2Q FY08 3Q FY08 4Q FY08 1Q FY09 2Q FY09 JUL AUG SEP OCT NOV DEC JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC JAN FEB MAR 2.0 Base OF 1.5 OneSAF 3.0 2.5 2.1 1.0.1 1.5.1 1.5 1.0.2 IE Qtr IE 5 7 6 9 8 3CE A B C 6 5 4 7 3 10 9 BLCSE TIE FFID 8 TLC Train-Up ARCIC FDT&E ACDEP CWD OF08 AAEF D AAEF E EWF EWF Scenario Behavior Phy Mdls HBCT Co FCS CAB FCS BCT TRAC Entity Level Aviation CO Level Move/Shoot FSE SO-1 JEFX08 Core Prg PM FCS BCT /LSI TFT OF 08/UR Ph3/JEFX 08 IV 1 IMT ATEC SO-1 LUT

  11. Summary Assess OneSAF within intended environment Incremental adoption approach to learn employment Replace OTB as Core Entity Driver Inform the community See Paper # 7477

  12. Backup

  13. TIE 5 Site Participation

More Related