2/4/09

1

Command Intent

Describes Produces Causes

Caused by Described by Produced by

Order Actions Effects DM Initial State

Perceived by

Perceives Produce End

State

Produced by

An Operational Decision Support Model using BML:

the Operations Intent and Effects Model

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

2/4/09

2

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.

OPORD

WARNO

Observation

Traditional – Decision Making and Planning

Company

Battalion

Squad

Platoon

Team

Brigade

Individual

Division

Corps Stra

tegi

c O

pera

tiona

l U

nit

Tact

ical

EBP

MARS

MDMP

GOP/OPP

PUT

MEDO

GOP/OPP

MDMP

EBAP

MARS

Senssing / Information Fusion (perception, comprehension, projection)

2/4/09

3

Networked-Enabled – Decision Making and Planning

Company

Battalion

Squad

Platoon

Team

Brigade

Individual

Division

Corps Stra

tegi

c O

pera

tiona

l U

nit

Tact

ical

EBP

MARS

MDMP

GOP/OPP

PUT

MEDO

GOP/OPP

MDMP

EBAP

MARS

Senssing / Information Fusion (perception, comprehension, projection)

Completed order

Initial

Observation

Intermediate order

Intermediate order

Two views of NEC Planning and Decision Making

  Dissemination •  orders and requests

  Collaboration •  horizontal and vertical

2/4/09

4

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)

DM Describes produces Causes

Caused by Described by Produced by

Order Actions Effects Initial State

Perceived by

Perceives

Command Intent

Produce End State

Produced by

2/4/09

5

SAw

SAw SAw Request

DM Initial State

Describes produces Causes

Caused by Described by Produced by

Order Actions Effects

Perceived by

Perceives

Command Intent

Produce End State

Produced by

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)

The Initial state are perceived by the DM process

and is the foundation for the process together with previous knowledge,

information assumptions etc.

DM Initial State

perceived by

Perceives Describes produces Causes

Caused by Described by Produced by

Order Actions Effects

Command Intent

Produce End State

Produced by

2/4/09

6

As an output from the DM process an intent is formalised representing a

desired End State

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.

DM Initial State

perceived by

Perceives

Command Intent

End State

Describes produces Causes

Caused by Described by Produced by

Order Actions Effects Produce

Produced by

End-State is reached by applying effects, i.e. Effects produce the End-

State

Effects DM Initial State

perceived by

Perceives

Command Intent

Produce End State

Produced by

Describes produces Causes

Caused by Described by Produced by

Order Actions

2/4/09

7

Effects are created by Actions

Causes

Caused by

Actions Effects DM Initial State

perceived by

Perceives

Command Intent

Produce End State

Produced by

Describes produces

Described by Produced by

Order

Actions and/or Effects are described in an order or a plan

Describes Causes

Caused by Described by

Order Actions Effects DM Initial State

perceived by

Perceives

Command Intent

Produce End State

Produced by

produces

Produced by

2/4/09

8

An order (request) is an explicit product from the decision maiking/

planning process Comment: The CI is explicit declared in

the Order. OPLAN/OPORD etc.

Describes produces Causes

Caused by Described by Produced by

Order Actions Effects DM Initial State

Perceived by

Perceives

Command Intent

Produce End State

Produced by

Collaborative Planning View

Planning Process View Command Intent

Produces Describes Produces End State Causes

Produced by Caused by Described by Produced by

Order Actions Effects DM Initial State

Perceived by

Perceives

Goal Command Intent Effects Actions Orders Requests Reports Expressives Capabilities

Informative

Command Intent Effects Actions Orders Requests Reports Expressives Capabilities

Orders Directing Request

Informative

Operations Intent and Effects Model

Orders Directing Request

2/4/09

9

Example

18

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 …

2/4/09

10

20

Coalition Battle Management Language

Simulation Systems C2 Systems

Robotic Systems

Live

Constructive

Virtual

BML

Virtual

JC3IEDM

Who What When Where Why

  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)

Shared Semantics between C2 and M&S via a Common Tasking Description

Commander and Staff

2/4/09

11

BML Represntation

C2 Plans & Orders

As Graphics

As Data

Protect (Division Rear Area)

DSA On order Tactical Combat Force

BLUE-MECH-TM1

Protect (Division left flank)

Zone (PL AMBER to PL BLUE)

On order Screen BLUE-CAV-SQN1

Support (B-A-BDE1)

Zone On order Follow and Support (B-A-BDE1)

BLUE-ARMOR-BN1

Reserve AA EAGLE On order Occupy BLUE-AVN-BDE

Seize (OBJ SLAM)

Zone On order Follows & Assumes (B-M-BDE2)

BLUE-ARMOR-BDE1

Penetrate (MRR2) Zone On order Attacks BLUE-MECH-BDE2

Fix (MRR1) Zone On order Attacks BLUE-MECH-BDE1

Why Where When What Who

22

Formalizing Intent

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

CI (Expanded Purpose) (Key Tasks) [End State]

2/4/09

12

23

Representation of Effects for Collaboration

 [End State] No Event-Report NKN Mortar-Fire label-ES2.2 SKAVSTA airport (X18 Y63) start at Date-Time-5 Fact label-ES2.3

 Effect: Suppress Mortar-Fire (Why in-order-to EVerb Action|Affected)

 Effect Why Verb Affected Executer Likelihood Label   “Why” from military doctrine (or civilian) (e.g. Suppress Mortar, Provide Stability,

Support Judicial System, Take that Hill)   “Verb” is an action that provides the wanted effect (e.g. Destroy, Disrupt)   “Affected” is the object that the action is targeted to.   “Executer” is the object that are performing the action (e.g. Specific, arch-type)   “Likelihood” describe the likelihood such action performed by executer will generate

the effect described by WHY.

24

Determine Actions from Effects

Effect Why Verb Affected Executer Likelihood Label

E in-order-to Suppress Mortar-Fire Destroy EnyCoy with MechInfCoy 60% E in-order-to Suppress Mortar-Fire Destroy EnyCoy with [2 Jas39 Gripen] 90%

E in-order-to Suppress Mortar-Fire Disrupt EnyCoy with MecInfCoy 60% E in-order-to Suppress Mortar-Fire Disrupt EnyCoy with [2 Jas39 Gripen] 20%

E in-order-to Suppress Mortar-Fire Divert EnyCoy with MecInfCoy 40% E in-order-to Suppress Mortar-Fire Divert EnyCoy with [2 Jas39 Gripen] 10%

2/4/09

13

Expressives

Example: If the commander in the example has the style of using low violence. Expressives [Use of power and force] Low Disrupt or Divert is defined to be less violent than Destroy according to doctrine

E in-order-to Suppress Mortar-Fire Destroy EnyCoy with MechInfCoy 60% E in-order-to Suppress Mortar-Fire Destroy EnyCoy with[2 Jas39 Gripen] 90%

E in-order-to Suppress Mortar-Fire Disrupt EnyCoy with MecInfCoy 60% E in-order-to Suppress Mortar-Fire Disrupt EnyCoy with [2 Jas39 Gripen] 20%

E in-order-to Suppress Mortar-Fire Divert EnyCoy with MecInfCoy 40% E in-order-to Suppress Mortar-Fire Divert EnyCoy with [2 Jas39 Gripen] 10%

Expressives Style Value

CI (Expanded Purpose) (Key Tasks) [End State] (Expressives)*

Contributions

 Formalism to support planning applications.

 Designed to be general to include military and civil operations

 Develop tools and infrastructure for the operations domain

2/4/09

14

Thank you for your attention

? per.m.gustavsson@saabgrpup.com

Awareness…

TA 

Who is there? 

What are they up to? 

What will they do? 

LA 

Who is there? 

What are they up to? 

What will they do? 

GA 

Transitory Awareness (TA) 

Local Awareness (LA) 

Global Awareness (GA) 

Who is there? 

What are they up to? 

What will they do? 

TA overlap LA overlap 

GA overlap 

Hom

ogen

ous – Inform

a3on

 sou

rces and

 represen

ta3on

s – he

terogene

ous 

Less                                Timespan, C2 Span, area of interest, etc.                          More 

What do they want? and Why? 

What do they want? and Why? 

What do they want? and Why? 

Enhanced from Hone 2006

2/4/09

15

Intuitive decision making / Skilled based

MSDL Scenario Editor using BML

2/4/09

16

Intent

32

The nature of Expressives

• Experience • Risk Taking • Use of power and

force • Diplomacy

• Ethics • Norms • Creativity • Unorthodox behavior

Style of the commander with respect to:

Bidrag en serie av

grammatiska produktions-

regler

2/4/09

17

JC3IEDM

C2LG GUI WISE Connectivity SLB BML

BML WS

BML WS

WISE DOB DOB

WISE BML WS

JSAF BML WS

BLACK-CACTUS – C4ICenter

Bidrag en design och implement-

ation

MSDL SISO/IEEE C-BML SISO/IEEE geoBML OneSAF NMSG – 048

2/4/09

18