ONE SEMI-AUTOMATED FORCES

1. DoD Modeling & Simulation ConferenceOne Semi-Automated Forces(OneSAF)Doug ParsonsUS Army, PEO STRI7 May 2007

2. ONE SEMI-AUTOMATED FORCES • A composable, next generation CGF • Represent a full range of operations, systems, and control processes (TTP) • Entity up to brigade level • Variable level of fidelity • Supports multiple Army M&S domain (ACR, RDA, TEMO) applications. Software only Automated Composable Extensible Interoperable Platform Independent Field to: RDECs / Battle Labs National Guard Armories Reserve Training Centers All Active Duty Brigades and Battalions Capable of replacing legacy entity-based simulations: BBS, OTB/ModSAF, CCTT/AVCATT SAF, Janus, JCATS MOUT

3. Army’s Mission for OneSAFAddress Three critical needs OneSAF MCT BBS OTB/ModSAF CCTT SAF AVCATT SAF Janus JCATS MOUT Reduce duplication of investments by eliminating the Army’s need for multiple simulations DIS and HLA ‘out of the box’ - Federation Development Tool; SOM-FOM mapping Reuse and Common Components - C4I adaptor, Environmental Runtime Component - Military Scenario Development Environment, AAR Common SAF - USMC Combined Arms Staff Trainer - Common Gunnery Architecture - Common Driver Trainer - JLCCTC ERF and MRF Foster interoperability and reuse Meet M&S requirements of the future force Army Transformation - Brigade Combat Teams Future Combat Systems Contemporary Operating Environment - Urban environment, terrorist activities

4. Fidelity Entity Count The OneSAF Community – Army Modeling and Simulation Domains • OneSAF Fulfilling Domain Needs • RDA and ACR • - Repeatable scenarios • Flexible architecture, extensibility • Ability to readily accept classified weapon system performance data. • TEMO • COE behaviors and organizations • Automated; low overhead driver • High fidelity Urban Operations • Connectivity to C4I devices • Streamlined scenario generation • Composable entities, units, behaviors • Ability to use 3rd party components • Advanced Concepts and Requirements • (Doctrine, Analysis & Concepts Forces) • Analysis of Alternatives - O&O development • Doctrine development - Army Transformation • Mobilization analysis/planning • Research, Development & Acquisition • (Equipping the Force) • System Analysis/Design - Life Cycle Cost • Component Analysis/Design - Logistics Analysis • Performance Factors - Reliability Analysis • Training, Exercises & Military Operations • (Preparing the Warfighter) • - Collective training - Staff training • Individual training - Crew training • Embedded training - Distributed training • Mission rehearsal

5. Low Medium High Multiple Levels of Fidelity • Most entities come in low, medium, and high resource utilization. • Interactions between entities of different levels of fidelity are tested. • Allows users to “dial up” the level of fidelity where it is needed. • Users build / customize compositions based on the desired resolution and available computer resources.

6. OCONUS 11 Sites OneSAF Initial Army Fielding Battlelabs School houses Training centers Academies Simulation centers Research centers ACR - 16 Sites RDA - 40 Sites TEMO - 44 Sites

7. Cooperative Development of OneSAF Baseline with AlliesCode developed by foreign partners will be rolled into the U.S. baseline.- United KingdomForeign Military SalesAssociated with the purchase of hardware, software, training, technical expertise, etc.Current and Pending FMS Cases- Australia- Canada- Czech Republic- Denmark- Slovakia- South Korea OneSAF Community – Multi Service, DoD Industry, and International Leveraging the Talents and Resources Across the M&S Community • Engaging with Users and External Developers • Distributed with source code • Web-based collaboration • - Commercial best practices • User Conferences • User and Developer training Early Joint & Multi-Service Engagements USMC CACCTUS Training System USAF SIMAF (EAAGLES), AFAMS, JFCOM

8. DoD Modeling & Simulation ConferenceOneSAF System Capabilities7 May 2007

9. OneSAF DesignSupporting a Full Range of Operations Composable Units, Entities, and Behaviors with Multiple Levels of Resolution Humanitarian Assistance Resupply, Repair, Towing, Medical Treatment, Casualty move / evacuation Load/Unload Personnel / Supplies / Equipment Non-Governmental & Private Volunteer Organizations Field Mission Delegate Branch General / Medical / Relief Work Support Branch Construction Element Private Security Team Complete Simulation Solution Full range of BFA systems and operations Semi- or Fully-Automated behaviors Multi-resolution, validated models Multi-resolution terrain (Weather/NBC) Ultra High Resolution Buildings Two-way connectivity to C4I devices Ultra-High Resolution Buildings Advanced features - closet, elevator shaft, hallway, stair, etc. Apertures - breach hole, door, etc. Enhanced attribution - lighting characterization, interior wall/floor construction Enhanced route planning within buildings - routes through apertures, line of sight through apertures Bullets passing through walls Urban Operations Clear a Building Assault a Building Urban Sniper Execute Urban Ambush Air Conduct Raid Conduct Ambush

10. OneSAF Modeling the Contemporary Operating Environment • Improvised Explosive Devices • Mouse Hole Creation • Dynamic Side Changes • Reduced Profile Shooting • Detect Vehicle Borne IED • Indirect Fire Weapons used as Direct fire weapons • Urban Operations Medevac • Sniper Tactics • Penetration of Building Walls • Conduct Raid • Controlled Mines • Ambush • “Technicals” • Shielding Tactics • Expedient Field Fortification • Decoys • Rocket & Mortar Attack Multiple sides (25) Changeable/Asymmetric relationships • Friendly • Hostile • Suspect • Neutral Some crowd modeling

11. OneSAF Objective System Synthetic Natural Environment Enhanced Terrain Representation • Multi-resolution terrain databases; High resolution (1:50k), Very-high resolution (1:12.5k) • Varying levels of building fidelity; Medium, high, and ultra high • DI reasoning and movement planning in an urban environment • Ray-trace LOS through terrain, features, and UHRB apertures • Standardization of OTF specification and API • Multi-resolution NBC/Smoke/Obscurants • Support for subterranean structures • Tunnels, sewers, basements, etc. • Building damage and rubble of buildings Ultra-High Resolution Buildings Advanced features - balcony, closet, elevator shaft, hallway, fire escape, ramp, stair, etc. Apertures - breach hole, door, skylight, trapdoor, etc. Enhanced attribution - lighting characterization, interior wall/floor construction Enhanced route planningwithin buildings - routes through apertures, line of sight through apertures Bullets passing through walls

12. OneSAF C2 Systems Interoperability • Unlike most legacy entity level simulations OneSAF models are “C2 Aware” • All C2 messages are purposely sent/received by individual models as a result of simulation events • Two way C2 interface • Outbound: OneSAF provides the COP for C2 devices • Inbound: C2 Devices affect OneSAF models and provide information to the simulation operator • The linkage between OneSAF and the C2 network is facilitated by the Common C4I Adapter OneSAF 2.0 will feature the capability to create a massive COP on C2 systems using thousands of OneSAF low resolution entities By pairing the C2 Aware entities with low resolution wrap-around forces, a detailed BDE scenario can be simulated while accurately populating C2 systems Green = OneSAF Supported

13. DoD Modeling & Simulation ConferenceOneSAFBusiness Practices7 May 2007

14. Evolving Capabilities as a Community The goal is to put in place processes that don’t just enable collaborative development but rather encourage it, while still ensuring there is one SAF. Base program P3I Informal co-developers Customer work Base program A&I Formal co-developers … Version 1.0 Version 1.1 Version 1.x Version 2.0 The OneSAF open architecture will build business opportunities.

15. VERSION 2.0MAJOR ELEMENTS PM Enhancements PTR Fixes Domain Code OneSAF V2.0 International Code Domain Requirements Co-developer code

16. Current Co-Developer efforts (Post 1.0) • United States Marine Corps (USMC) –CACCTUS • Space and Missile Defense Command (SMDC) • Common Gunnery Architecture (CGA) • SE Core • Future Combat System (FCS) • Common Product Improvements • Environmental Runtime Component • OneSAF, WARSIM, CombatXXI, IWARS • C4I Adapter • OneSAF, WARSIM, SE Core, C3 Driver

17. OneSAF C2 Systems Interoperability • Common C4I Adapter • PEO STRI Common Component • Same code base used by multiple simulation systems • Developed and configuration controlled by PM OneSAF • Uses the same software found on tactical C2 devices to create and parse military messages • Performs translations between various message formats and handles complex C2 networking interfaces

18. CO-DEVELOPER OVERVIEW – CONTRIBUTING CODE OneSAF V1.0 OneSAF (OF) V1.0 SPACE & UO Fact Teams OneSAF (ABCA) V0.9 MSMO USMC CACCTUS OneSAF V1.1 (V1.5) IS&T IPT SE CORE UK OneSAF (I) V1. 0 MATREX Common Gunnery Architecture CA BLCSE JLCCTC (WARSIM) OneSAF (OF) V1.1 (V1.5) AS OneSAF V2.0 TRAININGCOMMONCOMPONENTS TBD TBD TNG IPT Delivered Baseline Under Test Baseline Future Baseline

19. OneSAF and USMC representation • Program was initiated to design, develop, produce, and deploy an improved Combined Arms Staff Training system for the United States Marine Corps (USMC) • Entity compositions: • CH-53E Sea Stallion Cargo Helicopter • EA-6B Prowler Fixed Wing Aircraft • Arleigh Burke Destroyer 5'54 Gun • USMC Scout/Sniper team • Behavior compositions: • Hasty Defence • Maintain Contact Reconnaissance • FDC- Maximum Ordnance Information Sent to the Forward Observer • FDC- Support for Variable Rate of Fire • FDC- Extending Fire Missions • FDC- Suppression of Indirect Fire by Indirect Fire • Nine-Line Close Air Support • Nine-Line Close Air Support – Cleared Hot Response • Nine-Line Close Air Support – Abort Mission • Nine-Line Close Air Support – Multiple Bomb Drop • Nine-Line Close Air Support – Bomb Delivery Profiles • Target Unit Ownership

20. OneSAF and Navy representation (1/2) Land-Sea Fire Support (Call For Fire) • Call For Fire from land based forward observer to Cruiser (CIC). • Cruiser’s CIC issues Fire Order to on-board weapon(s). • Indirect fire to land based target. • End of Mission from observer to Cruiser. Vessel IED emplacement • Suspect Vessel emplaces an IED on Cruiser. • If detection occurs from escorting/supporting Destroyer, direct fire engagement occurs with suspect vessel. Naval Anti-Air Engagement • Detection and Acquisition of Air threat (fast mover) • Direct fire Engagement with Air threat (fast mover) Naval Direct Fire Sea Engagement • Cruiser/Destroyer engagement with OPFOR vessels • K-Kill of vessel represented Weapon Systems Identified • MK-45, 5” Gun • Tomahawk • MK-15 Phalanx

21. OneSAF and Navy representation (2/2) RWA Ship Takeoff/Landing Watercraft Surface Attack FWA Ship Takeoff/Landing Naval Platforms Cruiser Ticonderoga (CG-47) Destroyer Arleigh Burke (DDG-51) Aircraft Carrier Nimitz (CVN-68)

22. OneSAF and Air Force engagements • Simulation and Analysis Facility (SIMAF) • Enhanced Air-Air Ground Linked Environment Simulation (EAAGLES) • Constructive-Virtual Common Architecture • Apprenticeship – place EEAGLES developer in the IDE integrated directly as part of team OneSAF.

23. OneSAF and SMDC representation • Space Intelligence, Surveillance and Reconnaissance • Unit: • BLUFOR Space Unit (Ground station and satellite (1 or more) • Behaviors: • Conduct Satellite Surveillance • ISR Space Fly Route • PKAD: • Forecast Satellite Image Collection Times • LEO Satellite Downlink Delay • Satellite Mobility • LEO Satellite Mobility Waypoint Aim point Calculation

24. DoD Modeling & Simulation ConferenceOneSAFDevelopment Practices7 May 2007

25. Establishing the Appropriate Environment Integrated Development Environment (IDE) Streamlined Acquisition Strategy Government PM is the “prime”

26. Elements of Agile MethodsCommunication, Co-location, Working Code • “Most effective communications is face-to-face.” • Development through OneSAF v1 release involved the co-location of contractors, gov’t and user teams. • Satisfy customer through early and continuous delivery of working software • OneSAF has had working code since Build 4 • Welcome changing requirements • Implementation of requirements not more than a Build ahead. • Code must be written to agreed-upon standards

27. Peer Reviews Integration of TPO/domain participation into the development cycle. Dependency meetings Coordination with internal task order activities Coordinate handovers from co-developers Discuss PTRs for upcoming release Engineering CCB Conduct technical assessment of integrations impacting the baseline (e.g., hardware/software baseline changes, external integration). Make recommendation to the CCB regarding content of the release baseline (i.e., v1.1, v1.5, v2.0…). User Engagement Points and Processes

28. DoD Modeling & Simulation ConferenceOneSAF Modeling Architecture and Infrastructure7 May 2007

29. People, Process and Architecture OneSAF Users OneSAF Lifecycle Process OneSAF PLAF User lifecycle requirements drove the development of the OneSAF Product Line Architecture.

30. Architectural Applications (OneSAF System Compositions) Leader andStaff Training System Composition SeamlessTraining System Composition Force and Organizations Analysis Tool System Composition Test and Evaluation System Composition Other System Compositions … OneSAF Product Layer Repository Manager Maintenance Environment SystemComposer Knowledge Eng. Env. Event Planner Model Composer Simulation Generator Technical Manager Simulation Core Simulation Controller C4I Adapter Analysis & Review Unit Composer AAR Management& ControlTool(SSDE) Sim. Config. & Asset Mgmt. Tool UnitModels Management & ControlTool Monitor & Control Services Data ManagementTool S/W Eng. Environment Military Scenario Development Environment OneSAF Component Layer SystemComposerTool KA/KETools Annotator Tool CM Tool EntityComposer EntityModels Federation Mgmt. Tool Translation Services Information Meta-Data Tool Federation Develop. Tool ModelVerif. Tool Data Collection Specification Tool Environment Database Generation Environment DefectTool Behavior Composer Behavior Models Connect Services Stealth Tool S/W Verif.Tool Performance Modeling Tool EnvironmentComposer Physical Models System Acct. Tool IconTool Network Loader Tool S/W InstallTool Environment Models BattlefieldEnum. Tool Benchmark Tool SystemDist. Tool OneSAF Component Support Layer CompositionServices EnvironmentRuntimeServices EnvironmentReasoningServices GUIServices Plan ViewDisplay DataCollectionServices SimulationServices Simulation Object RuntimeDatabase Modeling Services System RepositoryServices OneSAF Repository Component Layer KA/KERepository EnvironmentRepository SoftwareRepository System Composition Repository Military Scenario Repository Local ExerciseEnvironmentRepository Parametric & Initialization Repository Simulation Output Repository OneSAF Common Services Layer Middleware Services Monitor Services Time Services Name Directory Services Messaging Services Coordinate Services Interchange Services RTI DIS COEServices WWW JDBC/ ODBC ORB Live Range Adapter OneSAF Platform Layer Hardware Operating System Network OneSAF Product Line Architecture

31. OneSAF Modeling Goals OneSAF is a set of tools, data, and components for assembling simulations for training and analysis interoperable with live, constructive, and virtual system. Requirements: • Support a wide range of existing and future military operations. • Support multiple levels of resolution. • Support multiple user domains. • Support both training and analysis. • Interoperate with other simulations. As a result, composability is a pervasive design goal.

32. Fundamental Concepts: Model Compositions • Entities represent equipment platforms such as tanks, soldiers, and trucks. They are composed of physical models and behavior agents and are controlled by behavior models. • Units represent the command and control of organizations such as platoons, companies, and battalions. They are composed of behavior agents and are controlled by behavior models. • Composite behaviors are composed of primitive behaviors and other composite behaviors.

33. More Fundamental Concepts:Atomic Components • Primitive behaviors (PB) provide chunks of doctrinal functionality from which more complex behavior models (Composite) are built. Primitive behaviors interact with behavior agents. • Agents: • Behavior agents provide command and control capabilities such as planning, plan execution, and situation assessment. • Physical agents are the “middlemen” between behaviors, physical world, and physical models. • Models • Behavior models answer Behavior Agents’ questions and represent the reasoning of Agents. • Physical models provide physical capabilities such as mobility, weapons, vulnerability, sensing, and communications. They are the simulated platforms' effectors and perceptors and are the simulated world's physics.

34. Primitive Behaviors • Primitive Behaviors: chunks of atomic functionality: • PlanGroundMovement • MoveCrossCountry • ActivateEmissions • ConductResupply • SetEngagementCriteria • AssumeSectorOfFire • Primitive Behaviors may be semantically rich. • PlanGroundMovement handles movement modes (bounding overwatch, road march, etc.) • ConductResupply handles tailgate and service station. • Primitive Behaviors are not individually orderable.

35. Unit? PlanGround Movement Activate Emissions PlanGround Movement Order Sender MoveCross Country SetEngagement Criteria Assume SectorOfFire Conduct Resupply Activate Emissions A Notional, Non-doctrinalComposite Behavior true false

36. Example Agents[~20 low & ~60 medium resolution] • Behavior Agents: • Commander • Intel • Message • Operations • Driver • Direct Fire Weapons Controller • Fire Direction Center • Caller For Fire • ADA Target Handoff • Physical Agents: • Weapon • Radio • Sensor • Mobility • Transport • Vulnerability

37. Simulation ObjectRuntime Database(SORD) Client (Wrapper) Objects ClientObject Modeling Infrastructure ClientObject 1..* Defines Client Model Battlespace Participant a.k.a. Actor Actor Software Component ClientObject 1 Object Database Managers (ODM) Posted to Blackboard on Initialization Blackboard C2 Manager Sides & Forces Manager Entity Manager Unit Manager Control Measures Manager Application Management Manager Triggers Physical Capability Unit Entity RuntimeDataModel(RDM) TransportObject Use & are controlled by TransportObject Defines Transport Model TransportObject Trigger Behavior Agents (Controller) Object Database (ODB) Physical Agents (Controller) Composite Behaviors 1..* 1..* Behavior Models Physical Models Primitive Behaviors use use use Data Data Data Discovered method invocation Elements of the Modeling Infrastructure

38. DoD Modeling & Simulation ConferenceOneSAF Toolset7 May 2007

39. OneSAF Objective SystemComposition Toolkit Battlespace Composition System Composition Behavior Composer Entity Composer Unit Composer Scenario Composition System Composer Military Scenario Development Environment Select only the components needed Ease of Use in the MS Power Point environment

40. Behavior Unit Entity OneSAF Composition Tools

41. Management and Control Tool

42. Data Collection • The Data Collection Specification Tool (DCST) is used to specify the sources and data elements that are to be collected. • These data elements are written in XML format at run time to a file in the SOR.

43. After Action Review tool Scenario snapshots 3D viewer Data charts in MS Office format

44. OneSAF Summary • OneSAF offers a full and robust set of capabilities to a wide range of users. • PM OneSAF’s open source business model offers the opportunity to leverage the resources and talents of developers for the benefit of the DoD modeling and simulation community. • OneSAF is a highly configurable suite of systems for the generation of semi-autonomous forces. • System capabilities are exposed by powerful visual tools.

45. DoD Modeling & Simulation ConferenceQuestions?www.onesaf.netUsers ConferenceCome see our table-top demoDoug Parsonsdoug.parsons@us.army.mil7 May 2007

46. Back up charts

47. OneSAF provides the complete battlefield picture • Individual Combatant to Brigade Operations • Full range of BFA systems and operations • Semi- or Fully-Automated behaviors • Multi-resolution, validated models • Feature rich synthetic natural environment • Multi-resolution, embedded terrain • database capability (1:50k, 1:12.5k) • Weather and NBC effects • Enhanced urban environment • Ultra High Resolution Buildings • (multiple floors, walls, apertures, • stairwells, furniture) Southeast Region JRTC • Two-way connectivity to C4I devices – ABCS 6.4 • FBCB2 • MCS/MCS-L • AFATDS • ASAS-L • AMDWS Shughart Gordan MOUT Ft. Polk Ultra High Resolution Building

48. Standard Autonomous No articulating parts Sensors: All available, Best used (60 degree FOV), Presented area not used w/n ACQUIRE, Sample LOS (Ray Trace Urban) Sensors: All available, Used All or Best (360/60 degree FOV), ACQUIRE presented area/camouflage, Ray Trace LOS Articulating parts Vulnerability: Same as Medium fidelity Vulnerability: Medium fidelity • Weapon: • All available, • Not aimed (no slew), • Weapon accuracy/rate same as medium fidelity • Weapon: • All available, • Aimed (slew), • Weapon accuracy/rate based on AMSAA models Hitch/unhitch Mount/Dismount Hitch/unhitch Mount/Dismount Mobility: Way Point, Polygon crossing Mobility: Sum of Forces, earth skin Behavior: Template Formations, No Obstacle avoidance, No collision avoidance, No path planning, simple behaviors (move, fire, etc.) Behavior: Station Keeping, Obstacle avoidance, Collision avoidance, Path planning, Complex behaviors (move tactically, call for fire, occupy BP) C4I: No comms, entity has only its perception, 1 radio to generate emissions, no fusion C4I: Networks, entity has only its perception, all radios, data fusion (SA), Perfect/Propagation CSS CSS: Combat Loads, Supplies Consumed, Played/Magic medical, repair and re-supply CSS: Combat Loads, Supplies Consumed, Magic medical. Repair and re-supply Standard and Autonomous Resolution: Entities

49. Standard and Autonomous Resolution: Units Standard Autonomous • FS: • FWD Observer Agent (ID Targets Calls for fire), • FDC Agent (coordinates guns, messaging), • User may issue fire orders FS: Fire orders issue by user CSS: Magic • CSS: • Medical Agent, • Repair Agent, • User directs re-supply, tailgate or service station behavior does rest Mobility: No route or path planning, No Obstacle avoidance, No collision avoidance (Human designates route) Mobility: Route and path planning, Obstacle avoidance, collision avoidance C2: SA at unit level and shared with all entities, C2 Network (digital messaging) Command Relationships understood Support Relationships understood Tactical Relationships understood C2: SA at entity level limited to what that entity senses (Unit SA is in the human operator), C2 Network (superior/subordinate), Command Relationships understood • Behaviors: • Reaction at entity and unit level, • Complex orders (move tactically, ATK by fire, call for fire, occupy BP, control measures, etc.), • Station Keeping • Behaviors: • No reaction at unit level all reaction is at entity level, • No complex orders (move, shoot, change weapon status, etc., Template formations CSS

50. System Administrator(Data Manager, Configuration Manager,System Administrator) Analyst(AAR Analyst,ACR/RDA Analyst) Senior Controller / Exercise Controller Technical Controller KA/KE SME Software Developer Model Composer Model Validator Observer / Controller Scenario Developer Training Audience C4I Operator Simulation Controller(Low Overhead Driver User,Puckster) Database Developer(Environment Database Developer, Parametric Database Developer) OneSAF Users