1906752a2ad8bae1143dea4c8ce406e5.ppt
- Количество слайдов: 55
Do. D Modeling & Simulation Conference One Semi-Automated Forces (One. SAF) Doug Parsons US Army, PEO STRI 7 May 2007
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 Capable of replacing legacy entitybased simulations: BBS, OTB/Mod. SAF, CCTT/AVCATT SAF, Janus, JCATS MOUT Platform Independent Field to: RDECs / Battle Labs National Guard Armories Reserve Training Centers All Active Duty Brigades and Battalions 2
Army’s Mission for One. SAF Address Three critical needs One. SAF MCT Reduce duplication of investments by eliminating the Army’s need for multiple simulations BBS OTB/Mod. SAF CCTT SAF AVCATT SAF Janus JCATS MOUT DIS and HLA ‘out of the box’ - Federation Development Tool; SOM-FOM mapping Foster interoperability and reuse Meet M&S requirements of the future force Reuse and Common Components - C 4 I 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 Army Transformation - Brigade Combat Teams Future Combat Systems Contemporary Operating Environment - Urban environment, terrorist activities 3
The One. SAF Community – Army Modeling and Simulation Domains 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 One. SAF 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 C 4 I devices - Streamlined scenario generation - Composable entities, units, behaviors - Ability to use 3 rd party components ity Ent t n Cou Fide lity 4
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. Low Medium High 5
One. SAF Initial Army Fielding Battlelabs School houses Training centers Academies Simulation centers Research centers OCONUS 11 Sites ACR - 16 Sites RDA - 40 Sites TEMO - 44 Sites 6
One. SAF Community – Multi Service, Do. D 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 Cooperative Development of One. SAF Baseline with Allies Code developed by foreign partners will be rolled into the U. S. baseline. - United Kingdom Foreign Military Sales Associated with the purchase of hardware, software, training, technical expertise, etc. Early Joint & Multi-Service Engagements USMC CACCTUS Training System USAF SIMAF (EAAGLES), AFAMS, JFCOM Current and Pending FMS Cases - Australia - Canada - Czech Republic - Denmark - Slovakia - South Korea 7
Do. D Modeling & Simulation Conference One. SAF System Capabilities 7 May 2007
One. SAF Design Supporting a Full Range of Operations Composable Units, Entities, and Behaviors with Multiple Levels of Resolution Complete Simulation Solution Humanitarian Assistance 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 C 4 I devices 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 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 9
One. SAF Modeling the Contemporary Operating Environment § § § Multiple sides (25) Changeable/Asymmetric relationships – – Friendly Hostile Suspect Neutral Some crowd modeling § § § 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 10
One. SAF Objective System Synthetic Natural Environment Enhanced Terrain Representation • Multi-resolution terrain databases; High resolution (1: 50 k), Very-high resolution (1: 12. 5 k) • 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 planning within buildings - routes through apertures, line of sight through apertures Bullets passing through walls 11
One. SAF C 2 Systems Interoperability • Unlike most legacy entity level simulations One. SAF models are “C 2 Aware” – All C 2 messages are purposely sent/received by individual models as a result of simulation events • Two way C 2 interface – Outbound: One. SAF provides the COP for C 2 devices – Inbound: C 2 Devices affect One. SAF models and provide information to the simulation operator • The linkage between One. SAF and the C 2 network is facilitated by the Common C 4 I Adapter One. SAF 2. 0 will feature the capability to create a massive COP on C 2 systems using thousands of One. SAF low resolution entities By pairing the C 2 Aware entities with low resolution wrap-around forces, a detailed BDE scenario can be simulated while accurately populating C 2 systems Green = One. SAF Supported 12
Do. D Modeling & Simulation Conference One. SAF Business Practices 7 May 2007
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 P 3 I Informal co-developers Customer work Base program A&I Version 1. 0 Formal co-developers Version 1. 1 … Version 1. x Version 2. 0 The One. SAF open architecture will build business opportunities.
VERSION 2. 0 MAJOR ELEMENTS PM Enhancements PTR Fixes Domain Code One. SAF V 2. 0 International Code Domain Requirements Co-developer code 15
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 • One. SAF, WARSIM, Combat. XXI, IWARS – C 4 I Adapter • One. SAF, WARSIM, SE Core, C 3 Driver 16
One. SAF C 2 Systems Interoperability • Common C 4 I Adapter – PEO STRI Common Component • Same code base used by multiple simulation systems – Developed and configuration controlled by PM One. SAF • Uses the same software found on tactical C 2 devices to create and parse military messages • Performs translations between various message formats and handles complex C 2 networking interfaces 17
CO-DEVELOPER OVERVIEW – CONTRIBUTING CODE One. SAF V 1. 0 SPACE & UO Fact Teams USMC CACCTUS One. SAF (OF) V 1. 0 One. SAF (ABCA) V 0. 9 MSMO One. SAF V 1. 1 (V 1. 5) IS&T IPT SE CORE UK Common Gunnery Architecture One. SAF (I) V 1. 0 MATREX CA One. SAF (OF) V 1. 1 (V 1. 5) JLCCTC (WARSIM) One. SAF V 2. 0 TBD AS TRAINING COMMON COMPONENTS TBD Delivered Baseline BLCSE Under Test Baseline Future Baseline TNG IPT
One. SAF 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-53 E Sea Stallion Cargo Helicopter EA-6 B 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 – 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 19
One. SAF 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 20
One. SAF 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) 21
One. SAF 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 One. SAF. 22
One. SAF 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 23
Do. D Modeling & Simulation Conference One. SAF Development Practices 7 May 2007
Establishing the Appropriate Environment Streamlined Acquisition Strategy Government PM is the “prime” Integrated Development Environment (IDE) 25
Elements of Agile Methods Communication, Co-location, Working Code • “Most effective communications is face-to-face. ” – Development through One. SAF v 1 release involved the colocation of contractors, gov’t and user teams. • Satisfy customer through early and continuous delivery of working software – One. SAF 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 26
User Engagement Points and Processes 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. , v 1. 1, v 1. 5, v 2. 0…). 27
Do. D Modeling & Simulation Conference One. SAF Modeling Architecture and Infrastructure 7 May 2007
People, Process and Architecture One. SAF Users One. SAF Lifecycle Process One. SAF PLAF User lifecycle requirements drove the development of the One. SAF Product Line Architecture. 29
One. SAF Product Line Architectural Applications (One. SAF System Compositions) Leader and Staff Training System Composition Seamless Training System Composition Force and Organizations Analysis Tool System Composition Test and Evaluation System Composition Other System Compositions … One. SAF Product Layer System Knowledge Composer Eng. Env. Event Planner Model Composer Simulation Generator Technical Manager Management & Control Tool (SSDE) Sim. Config. & Asset Mgmt. Tool Simulation Core Simulation Controller C 4 I Adapter Analysis & Review Repository Maintenance Manager Environment One. SAF Component Layer System Composer Tool KA/KE Tools Military Scenario Development Environment S/W Eng. Data Management Monitor & AAR Management Environment Control & Control Tool Services Annotator Tool CM Entity Tool Composer Information Federation Translation Federation Models Environment Data Defect Model Meta-Data Behavior Mgmt. Tool Services Develop. Tool Database Collection Tool Verif. Tool Composer Connect Behavior Generation Specification S/W Verif. Tool Performance Models Environment Tool Stealth Tool Services Tool Modeling Tool Composer System Physical Icon Acct. Tool Models Network Tool S/W Install Loader Tool Environment Tool Battlefield Models Enum. Tool Benchmark System Tool Dist. Tool Unit Composer Environment Runtime Reasoning Services One. SAF Component Support Layer Composition Services KA/KE Repository Environment Repository GUI Services Software Repository Plan View Display System Composition Repository Unit Models Data Collection Services Simulation Services Military Scenario Repository Simulation Object Runtime Database Local Exercise Environment Repository Modeling Services Parametric & Initialization Repository System Repository Services Simulation Output Repository One. SAF Repository Component Layer Monitor Services Time Services Name Directory Services Messaging Services Coordinate Services Interchange Services One. SAF Common Services Layer One. SAF Platform Layer Hardware Operating System RTI DIS COE JDBC/ WWW Services ODBC Middleware Services ORB Live Range Adapter Network 30
One. SAF Modeling Goals One. SAF 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. 31
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 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. 32
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 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. 33
Primitive Behaviors • Primitive Behaviors: chunks of atomic functionality: – – – Plan. Ground. Movement Move. Cross. Country Activate. Emissions Conduct. Resupply Set. Engagement. Criteria Assume. Sector. Of. Fire • Primitive Behaviors may be semantically rich. – Plan. Ground. Movement handles movement modes (bounding overwatch, road march, etc. ) – Conduct. Resupply handles tailgate and service station. • Primitive Behaviors are not individually orderable. 34
A Notional, Non-doctrinal Composite Behavior true Plan. Ground Movement Order Sender Unit? false Activate Emissions Plan. Ground Movement Move. Cross Country Set. Engagement Criteria Assume Sector. Of. Fire Conduct Resupply Activate Emissions 35
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 36
Elements of the Modeling Infrastructure Battlespace Participant a. k. a. Actor Client (Wrapper) Objects Simulation Object Client Runtime Database Modeling Object Client Defines 1. . * Actor Software Client Object Client Infrastructure (SORD) Model Object Component 1 Object Database Managers (ODM) Posted to Blackboard on Initialization Sides & Control Application C 2 Entity Unit Forces Measures Management Triggers Manager Physical Capability Manager Entity Unit Use & are controlled by Composite Behaviors Manager Runtime Data Transport Model Object Transport (RDM) Object Trigger Manager Defines Transport Model Behavior Object Database (ODB) Physical Agents (Controller) 1. . * Primitive Behaviors Manager 1. . * Behavior Models Physical Models use use Data Discovered method invocation 37
Do. D Modeling & Simulation Conference One. SAF Toolset 7 May 2007
One. SAF Objective System Composition Toolkit Battlespace Composition System Composition Behavior Composer Entity Composer Unit Composer Scenario Composition Military Scenario Development Environment Ease of Use in the MS Power Point environment System Composer Select only the components needed 39
One. SAF Composition Tools Entity Behavior Unit 40
Management and Control Tool 41
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. 42
After Action Review tool Scenario snapshots 3 D viewer Data charts in MS Office format 43
One. SAF Summary • One. SAF offers a full and robust set of capabilities to a wide range of users. • PM One. SAF’s open source business model offers the opportunity to leverage the resources and talents of developers for the benefit of the Do. D modeling and simulation community. • One. SAF is a highly configurable suite of systems for the generation of semi-autonomous forces. • System capabilities are exposed by powerful visual tools. 44
Do. D Modeling & Simulation Conference Questions? www. onesaf. net Users Conference Come see our table-top demo Doug Parsons doug. parsons@us. army. mil 7 May 2007
Back up charts 46
One. SAF 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: 50 k, 1: 12. 5 k) • Weather and NBC effects • Enhanced urban environment • Ultra High Resolution Buildings (multiple floors, walls, apertures, stairwells, furniture) Two-way connectivity to C 4 I devices – ABCS 6. 4 • FBCB 2 • MCS/MCS-L • AFATDS • ASAS-L • AMDWS Southeast Region JRTC Ft. Polk Shughart Gordan MOUT Ultra High Resolution Building 47
Standard and Autonomous Resolution: Entities Standard No articulating parts Vulnerability: Same as Medium fidelity Autonomous Sensors: All available, Best used (60 degree FOV), Presented area not used w/n ACQUIRE, Sample LOS (Ray Trace Urban) Articulating parts Vulnerability: Medium fidelity Sensors: All available, Used All or Best (360/60 degree FOV), ACQUIRE presented area/camouflage, Ray Trace LOS Weapon: • All available, • Not aimed (no slew), • Weapon accuracy/rate same as medium fidelity Hitch/unhitch Mount/Dismount Mobility: Way Point, Polygon crossing Behavior: Template Formations, No Obstacle avoidance, No collision avoidance, No path planning, simple behaviors (move, fire, etc. ) C 4 I: No comms, entity has only its perception, 1 radio to generate emissions, no fusion C S CSS: Combat Loads, Supplies Consumed, S Magic medical. Repair and re-supply Weapon: • All available, • Aimed (slew), • Weapon accuracy/rate based on AMSAA models Hitch/unhitch Mount/Dismount Mobility: Sum of Forces, earth skin Behavior: Station Keeping, Obstacle avoidance, Collision avoidance, Path planning, Complex behaviors (move tactically, call for fire, occupy BP) C 4 I: Networks, entity has only its perception, all radios, data fusion (SA), Perfect/Propagation CSS: Combat Loads, Supplies Consumed, Played/Magic medical, repair and re-supply 48
Standard and Autonomous Resolution: Units Standard FS: Fire orders issue by user CSS: Magic Autonomous FS: • FWD Observer Agent (ID Targets Calls for fire), • FDC Agent (coordinates guns, messaging), • User may issue fire orders 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 C 2: SA at entity level limited to what that entity senses (Unit SA is in the human operator), C 2 Network (superior/subordinate), Command Relationships understood C 2: SA at unit level and shared with all entities, C 2 Network (digital messaging) Command Relationships understood Support Relationships understood Tactical Relationships understood Behaviors: • No reaction at unit. C level all reaction is at entity level, • No complex orders (move, shoot, change weapon status, S etc. , Template formations S Behaviors: • Reaction at entity and unit level, • Complex orders (move tactically, ATK by fire, call for fire, occupy BP, control measures, etc. ), • Station Keeping 49
One. SAF Users Software Developer System Administrator (Data Manager, Configuration Manager, System Administrator) Technical Controller Senior Controller / Exercise Controller Scenario Developer KA/KE SME Observer / Controller Model Composer Training Audience Model Validator Database Developer (Environment Database Developer, Parametric Database Developer) Simulation Controller Analyst (Low Overhead Driver User, (AAR Analyst, Puckster) ACR/RDA Analyst) C 4 I Operator 50
One. SAF Lifecycle Phases 2: Product Line Development 3: Product Line Deployment & Install 4: Event Planning 14: Retrieval 1: Knowledge Acquisition / Engineering 15: Product Line Maintenance 5: Database Development 13: Archival One. SAF Repositories 1 -3, 15: Product Line Development, Deployment & Maintenance phases 4 -8: Pre-Event phases 9 -11: Event phases 12 -14: Post-Event phases 12: Post. Execution Analysis/AAR One. SAF Software 11: Simulation Execution 10: Systems Test & Verification 9: Simulation Configuration 6: Software Development 7: Model Composition 8: Scenario Generation 51
Interoperability One. SAF instances interoperate via: – Internal protocol (One. SAF messaging services or C 4 I Adapter) – External protocol (HLA or DIS) 52
One. SAF File System Layout onesaf PAIR SOR Parametric and Initialization Repository System Output Repository SWR Software Repository SYSTEM BINDIR = onesaf/SWR/bin/services/sys/composition COMPDIR = onesaf/PAIR/compositions 53
What’s in … ? • PAIR: – PAIR/compositions: Unit, entity, behavior compositions – PAIR/enum: Open enumeration definitions – PAIR/icons: Iconic representations – PAIR/mi/formation. Data: Formation definitions • SOR: – SOR/cache: Pre-compiled versions of data – SOR/collected. Published. Data: Data collection output – SOR/log: Logging output 54
What’s in … ? • SWR: – SWR/bin: Startup scripts for important applications – SWR/bin/services/sys/composition: Location of the runtimeloader and composer scripts – SWR/docs: Various forms of system documentation – SWR/lib: Software in system-loadable format – SWR/SCR: System component repository – SWR/src: Source code • SYSTEM: – SYSTEM/difs: Data interchange formats – SYSTEM/properties: Configurable load-time properties 55