200 likes | 706 Views
Using One Semi-Automated Forces (OneSAF) as a Tool to Support Analysis. Andrew Barnett 31 March 2009 US Army Materiel Systems Analysis Activity Aberdeen Proving Ground, Maryland 21005-5071. Approved for public release; distribution is unlimited. Agenda. How. When. What. OneSAF?.
E N D
Using One Semi-Automated Forces (OneSAF) as a Tool to Support Analysis Andrew Barnett 31 March 2009 US Army Materiel Systems Analysis Activity Aberdeen Proving Ground, Maryland 21005-5071 Approved for public release; distribution is unlimited.
Agenda How When What OneSAF? AMSAA … has been actively engaged with program support, testing, co-development activities and use of OneSAF. • AMSAA’s Role within the Army Analytical Community • Problem Statement • Key Simulation Capabilities • Operational Effectiveness Efforts • Simulation Preparation • Path Ahead
AMSAA’s Role (within Analytical Community) CAA (Warfighting in a Joint/Combined Context) Theater TRAC (Tactical Operations - Organization Design & Force Effectiveness thru Corps) Force Level Small Units AMSAA Data/ Meth. AMSAA (Logistics Systems & Network Performance Analysis) AMSAA (Materiel Sys. Performance Analysis) System & Technology RDECs/Labs (Sub-System/Component Performance & Technology Capabilities) Sub-Systems, Engr & Technology AMSAA – Army Materiel Systems Analysis Activity CAA – Center for Army Analysis TRAC – TRADOC Analysis Center RDECs – Research, Development and Engineering Centers AMSAA, TRAC & CAA Collaborate to Provide Army an Effective, Responsive, In-House Analysis Capability for Army Decision Makers
Problem Statement OneSAF …. release version 1.0 capabilities that support conducting an operational effectiveness analysis (OE) weren’t mature enough hence the OneSAF PrePlanned Product Improvement (P3I) requirements efforts have helped to ensure that these capabilities mature. Improving OneSAF Capabilities to support Analysis FY07 P3I Requirements FY08 P3I Requirements • Data Collection and Analysis • Repeatability and Replicability • Tools / processes to quickly generate classified scenarios • Causality Tools (Cause/affect tracking) • Data Collection and Analysis • Loading AMSAA weapons system performance data • Physical model enhancements OneSAF v3.0 OneSAF v2.0 FY09 P3I Requirements • Loading AMSAA weapons system performance data • Data collection and Analysis OneSAF v4.0
Key Simulation Capabilities(Supporting Analysis) • Data Collection and Analysis • Replicability & Repeatability • Behavior & Combat Physical Models • Scenario Composition Scenario Composition Weapon System Performance Data Other Data (i.e. behavior data) Entity Compositions
Operational Effectiveness Efforts Shakeout Study OneSAF v1.5 Purpose: • RDA domain’s transition to OneSAF, conduct AMSAA shakeout of OneSAF to assess it’s use as an analysis tool. • Determine best current operations Courses of Action (COAs) Description: Investigate various COAs based on current operations. AMSAA configured OneSAF baseline release version 1.5 for various COAs. • Summary: • Effort completed June 08 • Minimum number of OneSAF issues uncovered • OneSAF exhibited capability for use as an analysis tool Survivability Study OneSAF v2.1 Purpose: Assess the potential benefits and burdens for technologies that will provide increased crew protection against the specific threats. Description: Study investigated performance of various survivability countermeasures against various insurgent threats. Effort involved numerous organizations who conducted system level analysis, operational effectiveness (OE) analysis, tech performance analysis, engineering integration analysis, and cost analysis. • Summary: • OneSAF OE Effort completed Aug 08 • All involved organizations convened with analytical findings to determine the best available countermeasure technologies.
Simulation Preparation Define the problem at hand Create scenarios that best represent real-world situations Utilize the best available weapon system performance data (APEDS) Verify code is working as designed/required for study Execute all scenarios as defined in the run matrix Post process and analyze the output data
Define Problem • Purpose: Assess the potential benefits and burdens for technologies that will provide increased crew protection against various threats. • Customer: The Warfighter • Scope: System Engineering Study addressing: • Baseline crew protection • Assessment of survivability technology readiness • Technology performance analysis • Operational effectiveness analysis at system and force levels • Engineering integration analysis • Other factors including cost, potential for collateral damage, etc.
Create Scenario (1 of 2) OneSAF Terrain Engagement Area (EA) Satellite Imagery UNCLASSIFIED UNCLASSIFIED
Create Scenario (2 of 2) Plain View Display Ultra High Resolution Building Notional Scenario Status Window Mission Editor
Load Classified Data OneSAF has a requirement to provide the capability to use APEDS classified data. The unclassified data sets currently provided by OneSAF mimics the APEDS SFF. • APEDS data is consumed by OneSAF in its native format (colon delimited), no translation is required. • OneSAF v3.0 will be Standard File Format (SFF) 4.0 compliant.
Modify Code • Updated OneSAF v2.1 with all convoy study enhancements • Populated OneSAF with new entity compositions • Fixed known bugs • Enhanced fidelity of specific models • Verify model implementations after enhancements Sample model enhancement… • Previous Algorithm • Delivery Accuracy: Exact hit location on vehicle not known. (Hit or Miss) • Impacted Sector: Countermeasure (CM) sector is based solely on the centerline from the target to shooter. • Updated Algorithm • Delivery Accuracy: Actual hit location on vehicle determined. • Impacted Sector: CM sector is determined directly from munition hit location. Previous Algorithm Updated Algorithm Hit sector varies based on impact location Shooter to target centerline Multiple shots always hit same sector
Official Runs Notional Data • OneSAF has a Batch Mode Capability • No man-in-the-loop is required, scenarios are set up to run without intervention • Study required 50 replications for stability • Run Matrix: 12 sets of runs • multiple vehicles • multiple countermeasures + base case • Run Time for scenario • 5 minutes real time • 8-9 minutes computing time
Conduct Analysis • OneSAF data collection can be customized to meet the needs for a specific study, any variable that resides in the code has the potential to be collected • Adv Sim Team has developed tools to automatically consume and post process the raw output data Notional Data Sector Analysis UNCLASSIFIED UNCLASSIFIED % Total Hits per Sector
Path Ahead • Transitioning to OneSAF v3.0 for additional capabilities • DataDocs • APEDS SFF v4.0 Compliant • ARES • Continue to support PM in development of analytical tools (data loading/data collection) • Several Operational Effectiveness efforts to be conducted in the future using OneSAF as primary analysis tool