Geospatial Battle Management Language (geobml)

Transcription

1 Geospatial Battle Management Language () Geo-environmental Information Response to et-centric and Distributed Operations Objective of Geo-environmental Information To increase the agility of Battle Command and the Military Decision Making Process (MDMP) through the effective characterization and application of geo-environmental data, information and knowledge across the greatest extent of the force addressing the full spectrum of employment Current Force Future Force 1

2 Motivation for a Stove-piped geospatial and environmental data was not integrated across Battle Command enclaves Maps became the dated wallpaper for the Common Operating Picture trophy of integrated, common doctrinal geospatial concepts and lexicon How do we reach our customers. Re-invigorate relevance Belief that geo-environmental information should be an integral component of Battle Command and MDMP Fundamental enabler or constraint in military operations rmy Technology Objective common decision tools and information Emergence of et-centric concepts Distributed decision making need for a unifying context and meaning for all information types to be shared System of Systems use in Battle Command requires a common semantic foundation, shared and represented for both the soldier and the system to ensure effective interoperability et-centric Battle Command rchitecture (Geo-environmental Information Perspective) Warfighter Machine Interface WMI Services Presentation Visualizer Builder Core PIs Presentation Tailor Collaboration Presentation WMI Primitives Logon Translation Interface Role Report Generator gent QOS uthorizer Terminal Window Emulators Control Operator/ Interface ccount Intelligent Operator O/S Interface Monitor Embedded Training Training Common Components Domain pplications LDSS Maintenance Maintenance Planner Supply Supply Planner Distribution Distribution Planner Force Health Force Health Protection Protection Planner Incoming Rear rea Order Security Processor Threat Commander/ Monitor Soldier Spt Human Human Resources Resources Planner Situational Understanding Readiness Situation Monitor Refinement Weather Threat Service Refinement SU Toolset SU Fusion/ Presentation Process Battlespace Refinement Object Battle State Priority ssessor Planning & Preparation irspace Plan Planner ssessor CO Ground Planner Space Sensor Planner Planner Fires & Objective Effects Planner Planner Maneuver Comms Planner etwork Survivability Planner Planner Security Terrain Planner nalyzer ir Defense Rehearsal Planner Services R Simulation Services Mission Execution Incoming ction Order Requestor Processor Task Policy Editor Organizer Order otification Report & Unmanned uthorizer Payloads MGV Control Remote UV Control Operations Unattended UGV Control Munitions UGS Control Control irspace Ground Control Space Control Fires & Effects Conflict Control Control Level 1 Fusion Distributed Fusion Fusion Engine Exploitation Tools PS-MRS Vehicle Embedded FPSIM Consumption Reasoner Reasoner Maintenance LRU Reasoner Interface nomaly Data Detector Collection Service Solider Interface Decision ccuracy Consumption Simulated Model Fault Generator Generator Data FPSIM Management Generator Decision ccuracy LRU Evaluation Simulator etwork Management etwork Configuration Planning Policy Integrated Event Correlation Spectrum Fault Monitor Performance ccounting Key Management Security Interface dapter Common Management etwork System Picture Sensor Data Management SDM Kernel (External Control, Sensor rbitration SDM Sensor Framework (Plug-in Control, Monitoring on-organic U Sensor Sensor Plug-ins Plug-ins SDM Utilities Linux Interface Java Interface OpenGL Interface POSIX Interface X-Window Extensions (e.g. BIT) SOSCOE ICS Operating System Task Integration etwork COTS DI 2

3 Mission received from higher HQ or deduced by commander/staff Higher HQ order/plan/ipb Staff estimates Facts & ssumptions Restated mission Cdr s guidance Cdr s Intent Staff estimates & products Enemy COs Enemy COs CO statements / sketches Staff COs Geo-environmental Information Role: Military Decision Making Process (MDMP) Inputs Receipt of Mission Mission nalysis Course of ction Development Course of ction nalysis Outputs Cdr s initial guidance Warning order 1 Initial IPB products Restated mission Cdr s intent and guidance Warning order 2 Staff products Battlefield framework Preliminary movement CO statements and sketches War game results Task organization Mission to subordinate units CCIR War game results Establish criteria Decision matrix pproved CO Course of ction Comparison Course of ction pproval Orders Production Decision matrix pproved CO with revised - Cdr s intent - CCIR Warning Order 3 High pay-off target list OPL/OPORD/FRGO Commander's intent - Mission, Enemy, Terrain, Troops, Time & Civil (METT-TC) etwork Centric Challenges (Design Constraints) Potential value of a et-centric force is theoretically 2 Metcalf s Law So the bigger the force the better my situational awareness..right? There are some assumptions that must be met 1. There is real potential in all transactions Geo-information product has utility to the functional MDMP processes of the recipient. automated systems and soldiers 2. ll interactions have positive value s a function of value: Knowledge > Information > Data Maximize OHIO / information should be ready to use 3. -way interactions create the most value Design geo-information product utility for the broadest set of Battlefield Functional reas (BFs), their systems and processes 4. There will be both dense and sparse islands of interaction Design for varying organizational topologies Derived from: etwork Centric Warfare, Developing and Leveraging Information Superiority lberts, Garstka and Stein,

4 Interoperability (geospatial Battle Management Language ()) is an Unambiguous Language Both domain specific and cross-cutting Defined by the role of actionable geo-information in the C2 Provides Unification across Doctrine and terms Explicit vocabulary and grammar Specific context mapped to operations, missions and tasks Explicit Representation Consistent extension to Standard framework / exchange model Computational structure Both necessary and sufficient for shared, common understanding Protocols Explicit structure for transmission / sharing Doctrine: FMs, RTEPs UTL and UJTL Doctrine Protocols Representation Informational Sufficiency - MDMP Explicit Computational Representation For ctionable Geospatial Information Geo-Environmental Extension to Joint Consultation, Command & Control Information Exchange Data Model () XML Web Services Grid Services C4ISR Sensor Fusion rchitectural Framework (Terrain and Weather) Battle Command/Mission Execution Planning and Preparation Situation Understanding C2 Training / Modeling and Simulation Fusion Level Commercial Joint Mapping Toolkit et Centric Enterprise Services Enterprise GIS rchitecture Photogrammetry nd Spectral Technology R Format / Encoding W D T Exploitation Technology nalytic Technologies Decision Tools Decision Tools U I Geographic Context Tactical Context Mission Context K Situational Context D Representation Representation Information Knowledge F E O Format/Encoding F Format/Encoding O Format/Encoding R W Format/Encoding R S L Models C Models M Models Models T E T D S T G I D E O I G Bandwidth Tier 1 Tier 2 ctionable Information Tier 3 4

5 Tier 1 Information Products 1st principle qualities or military value of terrain and weather effects on military operations Value or use is independent of mission Information Products OCOK atural Obstacles, Cover and Concealment, Observation, Key terrain Maneuver etworks Weather impacts on mobility and sensor performance Tier 1 reflects Gigabytes of data and analysis transformed into a few Megabytes of information Still too large for Reference Tier 1 in Off- and On-Road Connected Graph Vehicle Speeds Formation Speeds Observation & Fields of Fire Directional Concealment Tier 2 Information Products Products suitable for a specific unit/force type/echelon or multiple force types to perform well defined military tasks or actions consistent with a mission or objective Value or use based upon mission or objective Information Products OCOK venues of pproach Routes / xis of dvance Battle, ttack, ssault and ttack by Fire and Indirect Fire Positions ssembly and Engagement reas Tier 2 reflects Megabytes nalyzing impact Multi-force Routing Unit Capacity!. Battle Compartment!. Direct Fire Positions 5

6 Tier 3 Information Products Products suitable for a specific unit/force type/echelon or multiple force types to perform well defined military tasks or actions specific to a mission or objective and refined by the current situation Use based upon known and predicted situation Information Products Specific products selected as part of the OPL and OPORD Tier 3 reflects Kilobytes nalyzing impact Control Graphics (OPL/OPORD) Tier 2 ttack By Fire Positions Enemy Situation Tier 3 ttack By Fire Positions 2525B Symbology Geo-Environmental Products ( Use and Findings Regarding the )) Leverages the core semantics of Comprehensive Geospatial elements are basic Information and Geometry Very well documented Tables and ttribution Relationships llows for domain extension Empowered by a robust grammar experience Initial pproach: Reference/map Tier geo-products from to a Enterprise geo-database For OPLS and OPORDs: minimal set of extensions required within the ction Capability Object-Type OBJECT-TYPE ORGIZTIO -TYPE MTERIL-TYPE PERSO -TYPE FCILITY-TYPE FETURE-TYPE Reporting Data Location Object-Item OBJECT-ITEM ORGIZTIO MTERIL PERSO FCILITY FETURE 6

7 Demonstration rchitecture (June 2006) Web Service Interface Commanders Support Environment C2IEDM Tasks Graphics Units OTB Route Planner Battlespace Terrain Reasoning & nalysis System BML GUI JBML Service rchitecture ( FY08 Incorporation of ) 1 WSDL Geospatial Domain Knowledge 3 XSD FILES fully defines domain language Web Service Exchange Interface 2 XML/WSDL XML/WSDL BML Domain-Configured Service 8 4 PI BML Base Service Who, What, Where, When, Why 6 PI XML/WSDL 5 Reference Implementation middleware common to all BML domains BML Common Data ccess Software 7 SQL Domain Specific Extensions Database on- Geospatial Databases 7

8 Reference Implementation (Distributed Battle Command and Experimentation) X GS DB Fall 2007 BC System - BML & Bde Terrain nalysis Cell w/ Geo-Spatial DB (DTSS / BTR and CJMTK) Fall 2008 II II II BC System - JBML & -CJMTK M&S (Joint/ Coalition) BC System - JBML & -CJMTK M&S (Joint/ Coalition) BC System - JBML & -CJMTK M&S (Joint/ Coalition) Way head C2 Services Layer GeoBML BML GIS Services Layer GeoBML M&S Services Layer MIPDEM Geospatial HL/DIS GML 8

9 Summary Way head GeoBML Technical Partnerships Forming ERDC, ESRI, GMU, Systematic, Inc. and MÄK Technologies becoming a standard TEC/ERDC business process Current partners are not interested in being the sole source of the capability Open invitation to interested parties ew domains emerging where we hope to infuse Joint BML (ir and aval (USMC)) Coalition BML (MSG-048) Logistics (ERDC) Experimentation addressing content, exchange efficiencies Task based architectural options: Products Tiers vs Imagery-based Making it Real How do we move forward: US rmy, JFCOM, DIS or MIP Single process or multiple threads. One time or increments BML Conference Battle Management: Interoperability for C2, Simulation and Geospatial Services Date: October 16-17, 2007 Location: GMU Prince William Campus, Manassas Sponsored by: US rmy Engineer Research and Development Center George Mason C4I Center ESRI MÄK Technologies Systematic Software Engineering, Inc. 9