bml
play

BML: the Operations Intent and Effects Model Command Intent - PDF document

Jul 08, 2023 •221 likes •417 views

2/4/09 An Operational Decision Support Model using BML: the Operations Intent and Effects Model Command Intent Perceived by Initial End DM Effects Order Actions Perceives Produces Describes Causes Produce State State Described by

  1. 2/4/09 An Operational Decision Support Model using BML: the Operations Intent and Effects Model Command Intent Perceived by Initial End DM Effects Order Actions Perceives Produces Describes Causes Produce State State Described by Caused by Produced by Produced by Per M. Gustavsson per.m.gustavsson@saabgroup.com GMU BML Symposium 2009 February 5, 2009 Outline An Operational Decision Support Model using BML: the Operations Intent and Effects Model A retrospect Collaborative Decision Support Operations Intent and Effects Model Example of BML Grammar Contributions 1

  2. 2/4/09 A retrospect Changed Environment • From force on force in a designated area towards anytime, anywhere, anyhow Adaption of Technology Political cooperation • Partnership for Peace, International Security Assistant Force (ISAF), EU expansion Economic considerations (Personal, Physical, Environmental) Social acceptance of Technology and Cooperation Collaboration and Cooperation is needed. • With a Network-Centric approach systems are enabled to be interconnected in a dynamic and flexible architecture to support multi-lateral, civilian and military missions. The constantly changing environment require commanders to plan for more flexible missions that allow organizations from various nations and agencies to join or separate from the teams performing the missions, depending on the situation. Traditional Directed Command and Control is moving towards Self Synchronization of teams. Traditional – Decision Making and Planning Strategic GOP/OPP WARNO MDMP Corps OPORD MARS Operational EBP Observation Division GOP/OPP MDMP MARS Brigade EBAP Battalion MEDO Tactical Company Platoon PUT Squad Unit Team Individual Senssing / Information Fusion (perception, comprehension, projection) 2

  3. 2/4/09 Networked-Enabled – Decision Making and Planning Strategic Initial GOP/OPP MDMP Intermediate order Corps MARS Operational Intermediate order EBP Division Completed order GOP/OPP MDMP Observation MARS Brigade EBAP Battalion MEDO Tactical Company Platoon PUT Squad Unit Team Individual Senssing / Information Fusion (perception, comprehension, projection) Two views of NEC Planning and Decision Making Dissemination • orders and requests Collaboration • horizontal and vertical 3

  4. 2/4/09 Intent Commander’s Intent is an intent describing military focused operations developed by a small group, e.g. staff, and a commander. Even though there is no limit to use it in other domains, for this work it is limited to the military domain. Common Intent is an intent that is shared and understood by all participants, i.e. there is no discrepancy between the intent of participating humans. Common Intent is an idealized view of intent. Common Mission Intent is a workable version of Common Intent in that it directed for a specific situation, bounded by participating organization, space and time. For the operation at hand the intent is common but other intent and goals of the participating humans may differ. Command Intent is an intent developed and exchanged amongst commanders and staff at multiple levels in an organization or even across organizations. Practically Command Intent is a Common Mission Intent developed in cooperation amongst participating commanders and staffs at more than one level. An external order, request or Intent is sent to a system (including humans and/or technology) Command Intent Perceived by Initial End DM Effects Order Actions Perceives produces Describes Causes Produce State State Described by Caused by Produced by Produced by 4

  5. 2/4/09 The DM process Require a SAw (depending on previous knowledge the order, request or Intent etc.) The output from the SAw process is an awareness product describing the Initial State for the Decision Maker(s) Command Intent Perceived by Initial End DM Effects Perceives Order Actions produces Describes Causes Produce State State Described by Caused by Produced by Produced by SAw SAw Request SAw The Initial state are perceived by the DM process and is the foundation for the process together with previous knowledge, information assumptions etc. Command Intent perceived by Initial End DM Effects Order Actions Perceives produces Describes Causes Produce State State Described by Caused by Produced by Produced by 5

  6. 2/4/09 As an output from the DM process an intent is formalised representing a desired End State Command Intent perceived by Initial End DM Effects Produce Perceives Order Actions produces Describes Causes State State Described by Caused by Produced by Produced by Even though the CI is explicit it could be that this CI product is Implicit and made explicit in the order, i.e. a thought of minds. For the purpose of this work the CI and ES however needs to be explicit in a collaborating environment. End-State is reached by applying effects, i.e. Effects produce the End- State Command Intent perceived by Initial End DM Effects Order Actions Perceives produces Describes Causes Produce State State Described by Caused by Produced by Produced by 6

  7. 2/4/09 Effects are created by Actions Command Intent perceived by Initial End DM Effects Perceives Order Actions produces Describes Causes Produce State State Described by Caused by Produced by Produced by Actions and/or Effects are described in an order or a plan Command Intent perceived by Initial End DM Effects Order Actions Perceives produces Describes Causes Produce State State Described by Caused by Produced by Produced by 7

  8. 2/4/09 An order (request) is an explicit product from the decision maiking/ Comment: The CI is planning process explicit declared in the Order. OPLAN/OPORD etc. Command Intent Perceived by Initial End DM Effects Perceives Order Actions produces Describes Causes Produce State State Described by Caused by Produced by Produced by Operations Intent and Effects Model Orders Directing Collaborative Planning View Request Planning Process View Goal Command Intent Command Intent Command Intent Perceived by Effects Effects Actions Actions Orders Orders Requests Initial End Requests DM Effects Perceives Produces Order Describes Actions Causes Produces State State Reports Reports Expressives Expressives Capabilities Capabilities Produced by Described by Caused by Produced by Informative Informative Orders Directing Request 8

  9. 2/4/09 Example Command Intent (dissemination) In a five paragraph Operations Order (OPORD) a section is named Commander’s Intent Commander’s Intent include Expanded Purpose, Key Tasks and desirerd End-State (US Field Manual 5.0) End-State The harbor in OXELÖSUND (X06 Y74) (SPOD) is operative and our sea assets can use it without risking being affected from sea, air or ground. SKAVSTA airport (X18 Y63) (APOD) is operative and usable to our air assets. Direct fire, SAM or mortars can not affect the airport. Brigade has at least one main supply route open from the SPOD to the APOD. etc … 18 9

  10. 2/4/09 Coalition Battle Management Language Battle Management Language is the unambiguous language used to command and control forces and equipment conducting military operations and to provide for situational awareness and a shared, common operational picture. (Carey et.al 2001) Commander Who Simulation Systems and Staff What C2 Systems When Live Where Virtual Why Virtual Constructive BML Robotic Systems JC3IEDM Shared Semantics between C2 and M&S via a Common Tasking Description 20 10

  11. 2/4/09 BML Represntation C2 Plans & Orders Who What When Where Why BLUE-MECH- Attacks On order Zone Fix (MRR1) BDE1 BLUE-MECH- Attacks On order Zone Penetrate (MRR2) BDE2 BLUE-ARMOR- Follows & On order Zone Seize (OBJ As Graphics BDE1 Assumes (B-M- SLAM) BDE2) BLUE-AVN-BDE Occupy On order AA EAGLE Reserve BLUE-ARMOR- Follow and On order Zone Support (B-A- As Data BN1 Support (B-A- BDE1) BDE1) BLUE-CAV-SQN1 Screen On order Zone (PL AMBER Protect (Division to PL BLUE) left flank) BLUE-MECH- Tactical Combat On order DSA Protect (Division TM1 Force Rear Area) Formalizing Intent CI  (Expanded Purpose) (Key Tasks) [End State] SKAVSTA airport (X18 Y63) (APOD) is operative and usable to our air assets. Direct fire, SAM or mortars can not affect the airport. [End State]  Status-Report own status-general APOD Operational SKAVSTA airport (X18 Y63) start at Date-Time-5 Fact label-ES2.1 [End State]  Status-Report own status-general AirAssets Operational SKAVSTA airport (X18 Y63) start at Date-Time-5 Fact label-ES2.2 [End State]  No Event-Report NKN Mortar-Fire label-ES2.2 SKAVSTA airport (X18 Y63) start at Date-Time-5 Fact label-ES2.3 22 11

Recommend

More recommend