The Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD USA...

17
The Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD USA 20723-6099 2011 Fall Simulation Interoperability Workshop The Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD USA 20723-6099 The Representation of Operational Terms and Graphics in Simulation Standards: Emerging Results and Issues William Riggs JHU/APL September 20, 2011

Transcript of The Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD USA...

Page 1: The Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD USA 20723-6099 2011 Fall Simulation Interoperability Workshop.

The Johns Hopkins University

Applied Physics Laboratory

11100 Johns Hopkins Road

Laurel, MD USA 20723-6099

2011 Fall Simulation Interoperability Workshop

The Johns Hopkins University

Applied Physics Laboratory

11100 Johns Hopkins Road

Laurel, MD USA 20723-6099

The Representation of Operational Terms and Graphics in Simulation Standards: Emerging

Results and Issues

William RiggsJHU/APL

September 20, 2011

Page 2: The Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD USA 20723-6099 2011 Fall Simulation Interoperability Workshop.

2010 Fall Simulation Interoperability Workshop2010 Fall Simulation Interoperability Workshop2011 Fall Simulation Interoperability Workshop

Introduction

2

• Live-Virtual Constructive Architecture Roadmap Implementation (LVCAR-I) Project– Common Data Storage Formats (CDSF): Nine Categories

Geospatial data Manmade environmental features Unit order of battle/force structure Electronic order of battle/network Platform/weapons performance and/or characteristics Plans/scenarios Behavior (including organizational and individual) Logistics Event results

This paper describes the relationship between syntax of C-BML, JC3IEDM, MSDL and its impact on plans and orders incorporated in the initialization process.

Page 3: The Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD USA 20723-6099 2011 Fall Simulation Interoperability Workshop.

2010 Fall Simulation Interoperability Workshop2010 Fall Simulation Interoperability Workshop2011 Fall Simulation Interoperability Workshop

Context: Relationship of Selected Data Models to C4I and Simulation Environments

3

Page 4: The Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD USA 20723-6099 2011 Fall Simulation Interoperability Workshop.

2010 Fall Simulation Interoperability Workshop2010 Fall Simulation Interoperability Workshop2011 Fall Simulation Interoperability Workshop

Simulation Context

• From the CDSF perspective, composition of plans and orders prior to initialization of the simulation environment is the primary area of concern– 2009 Army Study “Army Initialization Tools and Processes Analysis Final

Report” provides a useful description of the complexity and difficulty associated with initializing C4I and Simulation systems

• Factors Driving the Initialization Problem– Changes in the Operations Process as the nature of contemporary war

evolves, and C2 processes adapt to these changes Evolving operational environments: Counterinsurgency, asymmetric conflict, “hybrid

war”

– Challenges intrinsic to the initialization of C4I systems and simulation environments in support of military exercises

Use of digital C4I systems continue to grow, down to the lowest tactical echelon.

– Unique data representation requirements to support the differential needs of human and unmanned actors that utilize and execute plans and orders

Computer-generated forces going “live”

4

Page 5: The Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD USA 20723-6099 2011 Fall Simulation Interoperability Workshop.

2010 Fall Simulation Interoperability Workshop2010 Fall Simulation Interoperability Workshop2011 Fall Simulation Interoperability Workshop

Methodological Overview

5

MCTL

1

Source Concepts

Conceptual Analysis and FusionProduct Recommendations

Emerging M&S standards for representation of plans and scenarios:

Military Scenario Definition Language (MSDL) –describes initial forces, missions and tasks found in Operational Plan and Orders (OPLAN/OPORD)

Coalition Battle Management Language – used to translate messages and topics to and from C4ISR environment, including unmanned systems

Both are used as part of M&S initialization

JC3IEDM

FM

1-02

AUTLUJTL

C2LG

JP 1-02

MSDL

CBML

The focus of this effort is to identify what semantic and syntactical changes need to be made to MSDL and CMBL to effectively express the full range of plans and orders used in LVC exercises

Page 6: The Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD USA 20723-6099 2011 Fall Simulation Interoperability Workshop.

2010 Fall Simulation Interoperability Workshop2010 Fall Simulation Interoperability Workshop2011 Fall Simulation Interoperability Workshop

Classification of Terms Derived from CBML and C2LG Concepts

“Who” concepts: Permanent and temporary organizations that can be subject to orders and are responsible for their execution.

“What” concepts: Represent orderable actions.

“What” concepts: Represent the objects of ordered actions and the state changes resulting from the effects of such actions.

“Where” concepts: Spatially references including graphic symbols whose primitives are spatially referenced

“When” concepts: temporally references, or events that have a temporal reference (e.g. “Before Morning Nautical Twilight”).

“How” concepts: Represent implementation instructions associated with one or more actions.

“Why” concepts: Represent the rationale for ordered actions.

6

Page 7: The Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD USA 20723-6099 2011 Fall Simulation Interoperability Workshop.

2010 Fall Simulation Interoperability Workshop2010 Fall Simulation Interoperability Workshop2011 Fall Simulation Interoperability Workshop

Operation Terms – Sources and Distribution

7

Source Concepts Relevant Concepts

%Relevant

JP 1-02 3508 1654 47%

FM 1-02 2002 1198 60%

Common to JP 1-02 and FM 1-02

818 516 63%

Total 4692 2336 50%

Page 8: The Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD USA 20723-6099 2011 Fall Simulation Interoperability Workshop.

2010 Fall Simulation Interoperability Workshop2010 Fall Simulation Interoperability Workshop2011 Fall Simulation Interoperability Workshop

Operational Terms – Rough Order of Magnitude Classification

8

Classification JP 1-02 FM 1-02Common to

BothTotal

Who 439 188 88 539

What (Action) 314 333 142 505

What (Object) 827 605 264 1168

Where 224 238 93 369

When 82 67 42 107

How 230 162 56 336

Why 29 16 6 39

Multiples 470 390 167 693

% Multiples 28% 33% 32% 30%

Total 1654 1198 516 2336

Page 9: The Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD USA 20723-6099 2011 Fall Simulation Interoperability Workshop.

2010 Fall Simulation Interoperability Workshop2010 Fall Simulation Interoperability Workshop2011 Fall Simulation Interoperability Workshop

J3CIEDM and C2LG – “Actions”

9

ReferenceEnumerated "What"

Actions

JC3IEDM 445

C2LG (All) 152

C2LG (Ground Operations)

100

C2LG (Air Operations) 27

C2LG Crisis Relief 39

• Both quantitative and qualitative analysis reveals high degree of congruence of JP 1-02 and FM 1-02 terms with action expressions found in JC3IEDM and C2LG and…

• Also many of the same issues with respect to – Normalization– Complexity– Indirect Referencing

Page 10: The Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD USA 20723-6099 2011 Fall Simulation Interoperability Workshop.

2010 Fall Simulation Interoperability Workshop2010 Fall Simulation Interoperability Workshop2011 Fall Simulation Interoperability Workshop

Example: Normalization

• Host Nation Support: (DOD) Civil and/or military assistance rendered by a nation to foreign forces within its territory during peacetime, crises or emergencies, or war based on agreements mutually concluded between nations. See also civil-military operations. See FM 3-07. (FM 1-02)

• Subversive Political Action: "A planned series of activities designed to accomplish political objectives by influencing, dominating, or displacing individuals or groups who are so placed as to affect the decisions and actions of another government.“ (JP1-02)

• JC3IEDM action-event-category-code“The specific value that represents the general class or nature of activity prescribed

by an ACTION-EVENT”

– Providing host nation support (See above definition)

– Political execution: A putting to death of a person or group of persons for political reasons. (No directly equivalent term in either JP 1-02 or FM 1-02)

10

Page 11: The Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD USA 20723-6099 2011 Fall Simulation Interoperability Workshop.

2010 Fall Simulation Interoperability Workshop2010 Fall Simulation Interoperability Workshop2011 Fall Simulation Interoperability Workshop

Example: Complexity

Wave: a formation of forces, including ships, craft, amphibious vehicles or aircraft, required to beach or land about the same time. Waves can be classified by function: scheduled, on-call, or non-scheduled. Waves can also be classified by type of craft, e.g., assault, helicopter, or landing craft. (JP1-02)

JC3IEDM: No direct reference to a wave (e.g. as a task-formation-type-category-code attribute of the TASK-FORMATION-TYPE entity.– However the JC3IEDM ACTION-TASK: action-task-timing-hour-

code attribute contains this definition for the “H” value (as in H-Hour): (2) In amphibious operations, the time at which the first waterborne

wave of an amphibious assault lands on a beach.

11

Page 12: The Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD USA 20723-6099 2011 Fall Simulation Interoperability Workshop.

2010 Fall Simulation Interoperability Workshop2010 Fall Simulation Interoperability Workshop2011 Fall Simulation Interoperability Workshop

Example: Indirect Reference (1) Orbit Point: A geographically or electronically defined location used

in stationing aircraft in flight during tactical operations when a predetermined pattern is not established. See also holding point." (JP1—02)– JC3IEDM Representation: CONTROL-FEATURE-TYPE: control-feature-

type-category-code: orbit point (2) Patrol Base: The point of origin of a patrol where all equipment not

required for the patrol is left. All supplies necessary for resupplying the patrol and additional medical supplies and assistance are staged at this location. (FM 7-7) (FM 1-02 )

JC3IEDM Representation: – TASK-FORMATION-TYPE: task-formation-type-category-code: patrol

Definition: A TASK-FORMATION-TYPE that is a detachment of ground, sea, or air forces sent out for the purpose of gathering information or carrying out a destructive, harassing, mopping-up, or security mission.

– FACILITY-TYPE facility-type-category-code: Military base/facility– Definition: A facility that is used as a military base.

12

Page 13: The Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD USA 20723-6099 2011 Fall Simulation Interoperability Workshop.

2010 Fall Simulation Interoperability Workshop2010 Fall Simulation Interoperability Workshop2011 Fall Simulation Interoperability Workshop

Uniform Joint Task List: Suggested Action Verbs

13

Strategic National

Strategic Theater

Operational Tactical

Advise Arrange AccomplishAdvocate Acquire

Carry-outConduct Conduct Conduct ConductControl Control DetermineCoordinate Coordinate DevelopDesign Develop DesignDirect Direct Employ Employ

Harmonize Incorporate ExecuteInfluence Integrate

Manage MonitorOrganize Organize Operate

Propose PerformPlan Plan Plan PlanProvide Provide

Support SupportSynchronize Synchronize

Page 14: The Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD USA 20723-6099 2011 Fall Simulation Interoperability Workshop.

2010 Fall Simulation Interoperability Workshop2010 Fall Simulation Interoperability Workshop2011 Fall Simulation Interoperability Workshop

Comparison of Task Nomenclature (Attack)

14

Task ID Task NameNTA 1.5.3 Conduct Attack (Navy)TA 1.2.3 Conduct Amphibious Assault Operations (Joint)

ART 7.1.2 Conduct an Attack (Army)ART 7.5.1 Attack by Fire an Enemy Force or Position (Army)

ART 7.5.15 Fix an Enemy Force (Army)

Page 15: The Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD USA 20723-6099 2011 Fall Simulation Interoperability Workshop.

2010 Fall Simulation Interoperability Workshop2010 Fall Simulation Interoperability Workshop2011 Fall Simulation Interoperability Workshop

Summary and Conclusion

Military natural language continues to evolve at a rapid pace– OOTW and COIN offer significant challenges– Future operating environments are complex and highly

uncertain Both simulation standards (e.g. C-BML, MSDL) and C4I data

models (JC3IEDM) are pressed to keep up with this evolution– Inadequacies in existing data models and standards impact both

simulation environments and C4I systems during exercise initialization

SISO Product Development Groups (e.g. C-BML, MSDL) should consider:– Acceleration of work schedules– Tighter integration of data models– Additional venues for collaboration

15

Page 16: The Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD USA 20723-6099 2011 Fall Simulation Interoperability Workshop.

2010 Fall Simulation Interoperability Workshop2010 Fall Simulation Interoperability Workshop2011 Fall Simulation Interoperability Workshop

Questions and Feedback

16

Page 17: The Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD USA 20723-6099 2011 Fall Simulation Interoperability Workshop.

2010 Fall Simulation Interoperability Workshop2010 Fall Simulation Interoperability Workshop2011 Fall Simulation Interoperability Workshop

Backup Slides

17