Managing Command and Control Information Using...

Managing Command and Control Information Using a C2IEDM Based

Tasking Grammar

Dr. Michael HiebC4I Center

[email protected]

George Mason University

Content

1. Battle Management Language

2. The need for a C2 Grammar

3. A BML Tasking Grammar

4. Illustration by Example

5. Conclusion

DefinitionBML is an unambiguous language used for the command and control of forces and equipment conducting military operations.

BML is being developed as a standard representation of digitized C2 information for executable plans, orders, requestsand reports

SimulationSystems

Robotic Forces

C2 Systems

C2 Systems

Battle Management Language

• for military units, • for simulated forces, and• for future robotic forces.

Battle Management Language Representations

Division attacks on order in zone to seize OBJ SLAM.Division Mission

Form of maneuver: PenetrationMain effort: BLUE-MECH-BDE2,

on order BLUE-ARMOR-BDE1Supporting effort: BLUE-MECH-BDE1

BLUE-ARMOR-BN1Deep: NoneReserve: BLUE-AVN-BDE1Security: BLUE-CAV-SQN1Tactical Combat Force: BLUE-MECH-TM1

Division Concept of Operations

Tasks to Subordinates

Protect (Division Rear Area)DSAOn orderTactical Combat ForceBLUE-MECH-TM1

Protect (Division left flank)Zone (PL AMBER to PL BLUE)

On orderScreenBLUE-CAV-SQN1

Support (B-A-BDE1)ZoneOn orderFollow and Support (B-A-BDE1)

BLUE-ARMOR-BN1ReserveAA EAGLEOn orderOccupyBLUE-AVN-BDE

Seize (OBJ SLAM)ZoneOn orderFollows and Assumes (B-M-BDE2)

BLUE-ARMOR-BDE1Penetrate (MRR2)ZoneOn orderAttacksBLUE-MECH-BDE2Fix (MRR1)ZoneOn orderAttacksBLUE-MECH-BDE1

WhyWhereWhenWhatWho

US Army BML Proof of Principle

BML GUI

CAPES OTB

C4ISIXML – BML

Parser

BML acts as the common denominator

Multi-Source DatabaseAugmented with BML

Limited Demonstration of BML to NATOObjectives

Demonstrate the feasibility of a generic interface standard between C2 and M&S-type systemsShow limitations of current standards that must be addressed by the BML Working Group MSG-048Build experience to help structure the Technical Research Program

Demonstration Architecture

C2IEDM Augmentedwith APLET BMLC2IEDMC2IEDM++ DatabaseDatabase

CAPESCOA Definition

APLETSimulation

JSAFSimulation

Push CoA

Pull CoA

Push CoA

BML Web services


Command and

Control Systems

Modeling and

Simulation Systems

C2 Domain Language(s)

JC3IEDM

Peacekeeping BML

Logistics BML

Air BML

geoBML

Maritime BML

Ground BML

…


The Command and Control Information Data Exchange Model (C2IEDM) provides a standard Command and Control Vocabulary.


OBJECT-TYPE OBJECT-ITEM

ORGANIZATION -TYPE

MATERIAL-TYPE

PERSON -TYPE

FACILITY-TYPE

FEATURE-TYPE

ORGANIZATION

MATERIAL

PERSON

FACILITY

FEATURE

C2IEDM implements the principles of object-oriented programming

– Generalization and Specialization

– Inheritance of common attributes

New Information can be modeled by extending existing knowledge

C2IEDM – yet another data model?

C2IEDM was designed to support the unambiguous definition of information exchange requirements in the operational domain.

The contributions of data modeling experts as well as operational experts and users from more than 20 countries over more than 15 years ensure technical maturity and operational applicabilitybased on mutual agreement and multilateral consensus.

This makes the C2IEDM unique in the technical as well as the operational domain. Every recommended alternative must be measured against these criteria and achievements.

Army Deputy Chief of Staff G3/5/7 mandated the use of C2IEDM for Battle Command and M&S interfaces (Memo 28 Sep 2005).


Definition

The vocabulary must be well defined in the context of operations within an application domain to facilitate the generation of unambiguous executable tasks. BML must use a rigorous data standard so that underlying information systems (M&S or C2 Systems) can both exchange information, and facilitate coherent results and support automated reasoning. Therefore, it is desirable that BML implementations use the Multilateral Interoperability Programme (MIP) data model, the C2IEDM.

� BML vocabulary: C2IEDM / JC3IEDM


There is no “Formal” Language for Military Orders and Reports.

• In order to communicate one needs a language.• A language needs a vocabulary.• It also needs a grammar (to concatenate the lexical items)

and give meaning to the catenation.

The need for a C2 Grammar

• In order to communicate one needs a language.

• A language needs a vocabulary. The vocabulary is provided by the C2IEDM.

• The C2IEDM is not enough. (It is not a language).• A language also needs a grammar.



• A language needs a vocabulary.

• The C2IEDM is not enough. (It is not a language).

• A language also needs a grammar.


The C2IEDM is not enough.

• Military communications (orders, reports)

are not “formally” represented in the C2IEDM.

⇒ Doctrine is not carried through when communicating through C2IEDM.

However, this problem might be solved in future versions.


However, the C2IEDM is not a language.

It does not give enough meaning • to orders, requests, reports• - or more generally - to the tasks.


Tasks are listed and verbally defined in the C2IEDM table“action-task-category-code”

Example: advance In C2IEDM, version 6.1.5e, its meaning is given as:“To move forward towards an objective in some form of tactical formation.This is a transitional phrase between operations which may or may notresult in contact with the enemy.”

This meaning is for humans, not for machines.


action-taskadvance

organisation-action-association

• Unit1

In the C2IEDM, structure is provided but grammar is missing …“Advance from assembly area Alpha to phase line Tulip!”

action-resource • Unit2• Route

• Destination

action-objective

= Sender

part of

= Receiver

obligatory for “advance”



• A language needs a vocabulary.• The C2IEDM is not enough. (It is not a language).

• A language also needs a grammar.


The functionality of a grammarincludes the following three aspects:

• Assign the appropriate structure to language expressions.

• Provide the set of structures that are valid for expressions of the language.

• Determine how to calculate the meaning of an expressionfrom the meaning of its parts.


Development of a Formal BML Grammar

What kind of Grammar do we want ?What properties should the Grammar have ?

• Its vocabulary is based on the C2IEDM.• It respects “constituency” as inspired by the 5Ws

but reaches beyond. • It grants the calculability of concatenated meaning.• It is lexical-driven.


What kind of Grammar do we want ?What properties should the Grammar have ?

• Its vocabulary is based on the C2IEDM.• It respects “constituency” as inspired by the 5Ws

but reaches beyond. • It grants the calculability of concatenated meaning. • It is lexical-driven.


What kind of Grammar do we want ?

In linguistics, there four predominate phrase structure grammars:

• Government-binding Theory (GB)

• General Phrase Structure Grammar (GPSG)

• Head-Driven Phrase Structure Grammar (HPSG)

• Lexical Functional Grammar (LFG)


What kind of Grammar do we want ?

Lexical Functional Grammar (LFG) has all the properties we asked for. Thus, our BML Grammar is designed as a LFG variant.


LFG-References

Basic:• Kaplan, R.M. and Bresnan, J. (1982). Lexical-Functional

Grammar: A formal system for grammatical representation.

In: Bresnan, J. (Ed.), The Mental Representation of Grammatical Relations. Cambridge, MA: MIT Press.

Reprinted in: Dalrymple, M., Kaplan, R.M., and Maxwell III, J.T. (Eds.), Formal Issues in Lexical-Functional Grammar. Stanford, CA: CSLI, 1995.

Advanced:• Bresnan, J. (2001). Lexical Functional Syntax. Malden,

MA: Blackwell.

A BML Tasking Grammar

The production rules for the basic expressionshave the following general form:

B → Verb Tasker Taskee (Affected | Action)Where Start-When (End-When) Why Label (Mod)*

“Verb” is an action, normally a task;“Tasker” is a “Who”, the unit which commands the task;“Taskee” is a “Who”, the unit which executes the task;“Affected” is a “Who”, the unit which is affected by the task;“Action” is another action/task affected by the task;


The production rules for basic expressionshave the following general form:


“Where” is a “location phrase”;the “When”s are “time phrases”;“Why” is a terminal symbol giving the purpose of the action;“Label” is a label given to the task in order allow it to be referred in other basic expressions.


The production rules for basic expressionshave the following general form:


Whether there is “Affected” or “Action” is determined bythe verb. This is indicated by the round brackets. TheVerb also determines the kind of Where (At-Where orRoute-Where) to be used.


Rules for basic expressions (examples)(“verbs” are taken from LC2IEDM-table “action-task-category-code”)

B → advance Tasker Taskee Route-Where Start-When (End-When) Why LabelB → ambush Tasker Taskee Affected At-Where Start-When (End-When) Why LabelB → assist Tasker Taskee Action At-Where Start-When (End-When) Why LabelB → attack Tasker Taskee Affected Route-Where Start-When (End-When) Why LabelB → block Tasker Taskee Affected At-Where Start-When (End-When) Why LabelB → defend Tasker Taskee (Affect.) Route-Where Start-When (End-When) Why Label

Rules for constituents (examples)

Start-When → start Qualifier1 Point_in_TimeStart-When → start Qualifier2 Action

Qualifier1 → { AFT, ASAP, ASAPNL, ASAPNL, AT, BEF, NLT, NOB }

(“qualifier terms” are taken from C2IEDM-table “action-task-start-qualifier-code”)

Illustration by Example

Example: MIP-Exercise, Ede, NL, Nov. 2003

Extract of an (Section 3b) by MND-West (SP) to

13 NL MECH BDE:PH 1a: Fast Tactical March to PL TULIP by ROUTE DUCK.PH 1b: Defense in depth sector EAST, blocking penetration ALFA.PH 1c: Assist the rearward passage of the 12 (SP) CAV. RGT.PH 2: On order attack in direction ECHO.PH 3: Be prepared to conduct peace support ops

along the border within boundaries.

Illustration by Example

Translation to BMLmarch MND-West(SP) MECH_BDE13(NL)

along DUCK start nlt phase1a label_3_11;defend MND-West(SP) MECH_BDE13(NL)

at EAST start nlt phase1b label_3_12;block MND-West(SP) MECH_BDE13(NL) MIR320(ZB)

at TULIP start nlt phase1b label_3_13;assist MND-West(SP) MECH_BDE13(NL) label_3_57

at EAST start nlt phase1c label_3_14;

withdraw MND-West(SP) CAV_REG12(SP)to EAST start nlt phase1c label_3_57;

Conclusion

We need a grammar such that not only humans can “understand” BML, but such that modern Information Technology systems can understand it as well.

Such a grammar can be rigorously defined

according to standard Linguistic principles for

generation of, validation of and processing of

Command and Control Information.

Thanks for Your Attention !

Questions and Comments are appreciated.

Managing Command and Control Information Using...

Documents

Transcript of Managing Command and Control Information Using...