BLCSE Use of OneSAF - OneSAF Public Site

OneSAF Technical Exchange MeetingBLCSE Use of OneSAFLarry RiegerARCIC BLCSE TCCApproved for public ReleaseDistribution unlimited

JAMSD Mission• Serves as the TRADOC lead and cross domaincoordinator for Models and Simulations (M&S).• Provides staff management of M&S support to conceptdevelopment and learning, requirements determination,and capabilities integration.• Coordinates, and directs the use and development of theTRADOC-wide distributed M&S asset, Battle LabCollaborative Simulation Environment (BLCSE)Battle Lab Collaborative Simulation Environment (BLCSE)TRADOC simulation environment for ExperimentationOneSAF is THE primary maneuver entity driver in BLCSE8/27/2012 3L. Rieger 757.7501 6298

BLCSE Events using V5.x• BLCSE has been using OneSAF since OF 08 (2008) V2.1• JFEWE (Joint Forced Entry Warfighter Experiment) V5.0+- First OneSAF use that was really reliable• CAMWAS (Combined Arms Maneuver Wide Area Security)using V5.0+ (+V5.1 memory fixes)- Memory patch fixed last stability issues.- No cluster failures during event (foibles-yes)• GAMOA (Gain and Maintain Operational Access) V5.1.1.5- Performed very well, until day 8.- HLA Interop failed – due to network bandwidth(Network, not OneSAF issue – but OneSAF crashed)• BLCSE has re-baselined at V5.1.1.6 for FY12 work8/27/2012 5 L. Rieger 757.7501 6298

BLCSE CHP• 2011 Purchase of standard Hardware “Cluster” for BLCSE• Cluster is 20 Platforms, 10 “heavy” and 10 “light” all dual NIC• Heavy platform is dual-socket quad cores, total 7 CPU cores– One is Cluster Controller (“BattleMaster”) platform– One is SORD/SCAMT box– One is Interop box– 7 are SimCore boxes• Light platform is single socket quad core – used as MCT• All are Xeon E5620 at 2.4 GHz with GForce GTC570 GPU- using 1 Terabyte SATA III removable hard drives• BLCSE rule is 150 entities per CPU core, or 1200/Simcore;- which works out to 8400 per cluster (typically load less)• In benchmark tests, Simcore load fail point was 3600/Simcore- using V5.1.B (PM Baseline V5.1.1 equivalent)8/27/2012 6 L. Rieger 757.7501 6298

BLCSE OneSAF Toolkit• Primary Simulation: OneSAF Includes OneSAF-based ACRT (Virtual Simulation){Advanced Concepts Research Tool} Includes OneSAF-based DES (Adjudication tool){Damage Effects Server} Includes OneSAF-based BONST (Node Manager){BLCSE OneSAF Node Status Tool} Includes OneSAF-based ASGTK (Scenario Tool){Automated Scenario Generation ToolKit}– ForceBuilder in development (used in GAMOA)– ForceBuilder will replace ASGTK in BLCSE8/27/2012 7 L. Rieger 757.7501 6298

OneSAF DES Issues• Composition Issues – DES has to have an entity compositionwith all munitions types• Backstop Issues – Need to have a default “backstop” data forPk calculations• Enumeration Issues – DES is not providing feedback whenenumeration doesn’t match – We need to fix this• Huh?? Issues – How does a 9mm shoot down F-22s?The DES produces some anomalies based on data/backstop.The bottom line is good data is required for effective DES8/27/2012 8 L. Rieger 757.7501 6298

BLCSE OneSAF NodeStatus Tool (BONST)Similar to the SCAMT tool from OneSAF.The BONST communicates to the OneSAF machinesvia the JMX management protocol. This allows theBONST to perform remote method queries to retrievedata from any OneSAF workstation with JMX enabled,which it is enabled by default. That includes OneSAFmachines that are running in standalone, beforeinitialization, and even SCAMT nodes.Primary use is Federation Operations Controller toolto see what is stress level, and functions,in the various OneSAF Clusters8/27/2012 9 L. Rieger 757.7501 6298

BLCSE Big Issues• AMSAA Data Load – still too hard, too clumsy- Looking ahead to V6 and new tools• Need too many pucksters – better aggregate commandforce behaviors- Company level behaviors that are more intuitive and lessoperator demanding – Bn. level puckster• Ability to support CAMEX faster than real time excursions(burst of 3-4 hours non-HITL at 4x in brigade+ events)- Looking at both OneSAF and ULE• Dynamic Terrain Server – Added with V6 migration– Will be part of BLCSE baseline from FY13 event• BLCSE, and Army, is being driven to cloud computing underArmy CIO initiatives. This will impact OneSAF platform8/27/2012 10 L. Rieger 757.7501 6298

Army Requirements Integration CenterQUESTIONS?Larry RiegerBLCSE Technical Configuration Controller757.501.6298Lawrence.a.rieger.civ@mail.mil8/27/201211