Managing Command and Control Information Using a C2IEDM Based - PowerPoint PPT Presentation

Managing Command and Control Information Using a C2IEDM Based Tasking Grammar Dr. Michael Hieb C4I Center George Mason University mhieb@gmu.edu

Content 1. Battle Management Language 2. The need for a C2 Grammar 3. A BML Tasking Grammar 4. Illustration by Example 5. Conclusion

Battle Management Language Definition BML is an unambiguous language used for the command and control of forces and equipment conducting military operations. BML is being developed as a standard C2 C2 representation of digitized C2 information Systems Systems for executable plans, orders, requests and reports Simulation Systems • for military units, • for simulated forces, and Robotic • for future robotic forces. Forces

Battle Management Language Representations Division Mission Division attacks on order in zone to seize OBJ SLAM. Division Concept of Operations Form of maneuver: Penetration Main effort: BLUE-MECH-BDE2, on order BLUE-ARMOR-BDE1 Supporting effort: BLUE-MECH-BDE1 BLUE-ARMOR-BN1 Deep: None Reserve: BLUE-AVN-BDE1 Security: BLUE-CAV-SQN1 Tactical Combat Force: BLUE-MECH-TM1 Tasks to Subordinates Who What When Where Why BLUE-MECH-BDE1 Attacks On order Zone Fix (MRR1) BLUE-MECH-BDE2 Attacks On order Zone Penetrate (MRR2) BLUE-ARMOR-BDE1 Follows and Assumes (B-M- On order Zone Seize (OBJ SLAM) BDE2) BLUE-AVN-BDE Occupy On order AA EAGLE Reserve BLUE-ARMOR-BN1 Follow and Support (B-A- On order Zone Support (B-A-BDE1) BDE1) BLUE-CAV-SQN1 Screen On order Zone (PL AMBER to PL Protect (Division left flank) BLUE) BLUE-MECH-TM1 Tactical Combat Force On order DSA Protect (Division Rear Area)

US Army BML Proof of Principle BML GUI XML – BML C4ISI Parser Multi-Source Database Augmented with BML CAPES OTB BML acts as the common denominator

Battle Management Language Limited Demonstration of BML to NATO Objectives � Demonstrate the feasibility of a generic interface standard between C2 and � M&S-type systems Show limitations of current standards that must be addressed by the BML � Working Group MSG-048 Build experience to help structure the Technical Research Program � Demonstration Architecture � APLET Simulation Push CoA Push CoA Pull CoA BML Web services CAPES JSAF COA Definition Simulation C2IEDM Augmented with APLET BML + Database C2IEDM + C2IEDM Database

Battle Management Language C2 Domain Language(s) Ground BML Maritime BML Modeling Command Air BML and and geoBML Simulation Control Logistics BML Systems Systems Peacekeeping BML … JC3IEDM

Battle Management Language The Command and Control Information Data Exchange Model (C2IEDM) provides a standard Command and Control Vocabulary. C2IEDM implements the principles OBJECT-TYPE OBJECT-ITEM of object-oriented programming – Generalization and ORGANIZATION -TYPE ORGANIZATION Specialization MATERIAL-TYPE MATERIAL – Inheritance of common attributes PERSON -TYPE PERSON FACILITY-TYPE FACILITY New Information can be modeled FEATURE-TYPE FEATURE by extending existing knowledge

Battle Management Language 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 applicability based 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).

Battle Management Language 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

The need for a C2 Grammar 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.

The need for a C2 Grammar • In order to communicate one needs a language. • A language needs a vocabulary. • The C2IEDM is not enough. (It is not a language). • A language also needs a grammar.

The need for a C2 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.

The need for a C2 Grammar However, the C2IEDM is not a language. It does not give enough meaning • to orders, requests, reports • - or more generally - to the tasks.

The need for a C2 Grammar 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 not result in contact with the enemy .” This meaning is for humans, not for machines.

The need for a C2 Grammar In the C2IEDM, structure is provided but grammar is missing … “ Advance from assembly area Alpha to phase line Tulip !” action-task action-resource • Unit2 = Receiver advance • Route organisation- action-association part of action-objective • Unit1 = Sender • Destination obligatory for “advance”

The need for a C2 Grammar • In order to communicate one needs a language. • A language needs a vocabulary. • The C2IEDM is not enough. (It is not a language). • A language also needs a grammar.

The need for a C2 Grammar The functionality of a grammar includes 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 expression from 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.

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.

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.

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. �

Development of a Formal BML Grammar 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)

Development of a Formal BML Grammar 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.

Development of a Formal BML Grammar 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.