BML Operations Order and Geospatial Representations GMU BML - - PDF document

1

BML Operations Order and Geospatial Representations

GMU BML Symposium 2009

4 – 5 February 2009

John D. Roberts ACS, Inc. Shrewsbury, NJ, 732-460-9416 x22 jroberts@acsinc-nj.com

2

Briefing Agenda

• Part 1: BML Operations Order Schema
• Part 2: Geospatial Representation in JC3IEDM

2

3

BML – What is it?

Human/
 C4I
Device
 Human/
 C4I
Device
 Simulation
 Future
 Robotic

 Forces


BML
 BML
 OPORD OPORD


BML
 Msgs


BML is the unambigous language used to:

• Command and control forces and

equipment conducting military

• perations
• Provide for situational awareness

and a shared, common operational understanding of these operations

• BML is being developed as a

standard representation of digitized C2 information for executable plans, orders, requests and reports

4

BML – Four Basic Principles

• BML must minimize ambiguity
• BML must enable the full expression of a

commander’s intent

• BML must use the existing C4I data

representations when possible (C2IEDM/ JC3IEDM)

• BML – must allow all elements to communicate

information pertaining to themselves, their mission and their environment in order to create situational awareness and a shared, common operational picture

3

5

Military Decision Making Process (MDMP)

Receipt of Mission Mission Analysis Course of Action Development Course of Action Analysis Course of Action Comparison Course of Action Approval Orders Production

Inputs Outputs

OPLAN/OPORD/FRAGO

Approved COA

E x e c u t i

• n

Mission War game results Higher HQ order/plan/IPB Estimates, Facts, & Assumptions War game results, Task Org, CCIR COAs Restate Mission, Guidance/Intent, Estimates Decision Matrix Friendly/Enemy COAs Cmdrs’ Guidance (WARNO 1) IPB Products, Restated Mission, Guidance & Intent (WARNO 2) Decision Matrix Approved COA, CCIR, HPO Targets, (WARNO 3) 6

Army Operations Order

• Doctrinal Reference
• FM 5-0 Army Planning and Orders Production
• Appendix G – Plans and Orders
• OPORD/WARNO/FRAGO:
• 5 Primary Paragraphs + Other Supporting Info
• Format:

 Header  Task Organization  Situation  Mission  Execution  Service Support  Command and Signal  Annexes

4

7

BML OPORD Schema – Top Level

8

5 W’s – Who

5

9

5 W’s – What

10

5 W’s – When

6

11

5 W’s – Where

12

5 W’s – Why

7

13

Header Paragraph

14

Task Organization

8

15

Situation Paragraph

16

Mission Paragraph

9

17

Execution Paragraph

18

Overlays

10

19

GeoSpatial Representation in JC3IEDM

20

Some Background

• BTRA BC – US Army ERDC ATO managed by TEC
• Objective is to bring actionable geospatial information into the

hands of the Warfighter

• S/W and Framework to transform volumes of data produced by

terrain teams and sensors into information products and tactical decision aids for a deeper understanding of the battlefield.

• GeoBML is an extension of BML into the domain of

actionable geospatial information.

• It provides the semantic and syntactic bridge between the highly

specialized domain of terrain reasoning and analysis and the immediate needs of the operational Warfighter.

• Representation to facilitate putting tailored, high fidelity knowledge

into the hands of the Commander and his staff.

11

21

Tactical Spatial Object

• Tactical Spatial Object (TSO):
• An object developed with topographic support systems/applications

that directly supports the planning and execution of tactical military

• perations.
• Provides the specific set of geospatial information necessary to

support the decision maker

• Contains relationships to specific military operations, missions and

tasks and may also have distinct relationships to various types and echelons of military organizations.

• Classification:
• Tier 1 – Foundation Product
• Tier 2 – Mission or Task specific
• Tier 3 – Represent a Command Decision

22

TSO Tiers

• Tier 1 – Represent military value of terrain/weather based
• n doctrine (OAKOC). Computed without mission specific

info (i.e., independent of METT-TC. Examples include Maneuver Network, Cover & Concealment, Choke Points.

• Tier 2 – Derived from foundational data. Candidate

products associated with specific missions and tasks by unit type & echelon and require METT-TC. Examples include ABF Positions, Battle Positions, Engagement Areas.

• Tier 3 – Increasing mission and task focused. Chosen from

candidate Tier 2’s and represent a command decision. Contain operational attributes and are associated with a specific plan/order. Can have an associated Graphical Control Measure (GCM).

12

23

Representing TSOs to Warfighter

• Provide access to via C2 Operational Database

(i.e., C2IEDM/JC3IEDM)

• Data Replication via DEM
• Tying Plan/Order directly to TSO
• Tier 1 & Tier 2 TSOs too large and complex to

store in Operational Database – store reference with associated attributes/metadata.

• Store TSO Product itself in SDE database as it

is designed for storage Geographic data.

24

Initial Implementation – C2IEDM

• Control Feature Object
• Separate set of

attributes for Tier 1 and Tier 2/3.

• bject-item
• bject-item-id

category-code feature feature-id category-code control-feature control-feature-id category-code geographic-feature geographic-feature-id … meteorologic-feature meteorologic-feature-id …

13

25

New Implementation – JC3IEDM

REFERENCE reference-id reference-approval-datetime reference-content-category-code reference-creation-datetime reference-description-text reference-electronic-source-text reference-file-size-quantity reference-format-text reference-language-code reference-lifecycle-code reference-medium-type-code reference-originator-text reference-physical-size-text reference-primary-location-text reference-publication-datetime reference-releasability-text reference-short-title-text reference-title-text reference-transmittal-type-code reference-validity-period-begin-datetime reference-validity-period-end-datetime reference-verification-code reference-version-text security-classification-id

Reference Table

26

TSO Core Attributes

Attribute Description TSOUniqueID A unique identifier used to reference the TSO reference instance RefNum A reference number used to identify the specific type of TSO GeographicArea List of lat/lon coordinates defining the polygon that the TSO falls within Version Represents TSO Engine version used to generate this reference CreationTime Represents the date/time the TSO was created ExpirationTime Represents the date/time the TSO expires Description Human readable text string describing the TSO StoredLocation Provides the path to the SDE container/workspace w/o credentials DataSetName SDE TableName and/or FeatureClass (1 or more) DataSetDesc Text String describing each DataSetName (1 or more) POC-Info TSO POC info: Organization, Name, Address & Phone ConfidenceFactor A measure of the goodness of the TSO (methodology TBD) SecurityClass Identification of the security classification for the TSO product Keywords Set of 0 or more keywords associated with TSO used for Discovery

14

27

TSO Core Attributes (con’t)

• TSO Specific Metadata
• Provide further descriptive information not included

in core attributes

• 0 or more number of attribute/value pairs
• TSO Type Unique.
• Defined by TSO Engine Developers

JC3IEDM Reference Table

REFERENCE reference-id reference-approval-datetime reference-content-category-code reference-creation-datetime reference-description-text reference-electronic-source-text reference-file-size-quantity reference-format-text reference-language-code reference-lifecycle-code reference-medium-type-code reference-originator-text reference-physical-size-text reference-primary-location-text reference-publication-datetime reference-releasability-text reference-short-title-text reference-title-text reference-transmittal-type-code reference-validity-period-begin-datetime reference-validity-period-end-datetime reference-verification-code reference-version-text security-classification-id

CreationTimeStamp Description StoredLocation DataSetDisplayName DataSetName CreationTimeStamp ExpirationTimeStamp Version

TSO Core Attributes

15

New JC3IEDM Tables – For TSOs

TSO

tso-id tso-unique-id tso-reference-number tso-confidence-factor

REFERENCE

reference-id reference-approval-datetime reference-content-category-code ….

TSO-SPECIFIC-ATTRIBUTE

tso-id tso-specific-attribute-ix tso-specific-attribute-name tso-specific-attribute-value

TSOUniqueID RefNum ConfidenceFactor Metadata Attribute Metadata Value

Geographic Area

LOCATION location-id location-category-code … POINT point-id … ABSOLUTE-POINT absolute-point-id … GEOGRAPHIC-POINT geographic-point-id geographic-point-latitude-coordinate geographic-point-longitude-coordinate geographic-point-latitude-precision-code geographic-point-longitude-precision-code LINE-POINT line-id … LINE line-id VERTICAL-DISTANCE vertical-distance-id vertical-distance-reference-code vertical-distance-dimension vertical-distance-precision-code vertical-distance-datum-text REFERENCE reference-id … OBJECT-ITEM

• bject-item-id
• bject-item-category-code

… CONTROL-FEATURE control-feature-id control-feature-category-code … OBJECT-ITEM-REFERENCE-ASSOCIATION

• bject-item-id

reference-id … FEATURE feature-id feature-category-code … OBJECT-ITEM-LOCATION

• bject-item-id

location-id …

16

31

POC Information

• Point-of-Contact information about originator or creator
• f TSO.
• Spread across 3 JC3IEDM tables

TSO Core Attribute JC3IEDM Representation Table Attribute

POCOrganization OBJECT-ITEM

• bject-item-name-text

POCName OBJECT-ITEM

• bject-item-name-text

POCAddress PHYSICAL-ADDRESS physical-address-street-text PHYSICAL-ADDRESS physical-address-postal-box-text PHYSICAL-ADDRESS physical-address-city-text PHYSICAL-ADDRESS physical-address-postal-code-text POCPhone ELECTRONIC-ADDRESS electronic-address-name-text

32

Security Classification

• security-classification-id field in Reference

table provides association to Security- Classification table.

REFERENCE reference-id … security-classification-id SECURITY-CLASSIFICATION security-classification-id security-classification-level-code security-classification-policy-text security-classification-caveat-text TSO …. TSO-SPECIFIC-ATTRIBUTE …

SecurityClassification

17

Associated Plan/Order

PLAN-ORDER plan-order-id plan-order-category-code PLAN-ORDER-COMPONENT plan-order-id plan-order-component-index PLAN-ORDER-COMPONENT- CONTENT plan-order-id plan-order-component-index … PLAN-ORDER-COMPONENT-CONTENT-REFERENCE plan-order-id plan-order-component-index plan-order-component-content-reference-index plan-order-component-content-reference-category-code plan-order-component-content-reference-datetime reference-id REFERENCE reference-id … TSO …. TSO-SPECIFIC-ATTRIBUTE …

Questions ?