Specifying Scenarios Using the Military Scenario Definition Language

1
Specifying Scenarios Using the Military Scenario
Definition Language

• 04F-SIW-068
• Robert Franceschini
• Science Applications International Corporation

2
What is a Military Scenario?
3
Simulation Scenario vs. Operational Scenario
4
Simulation Scenario Execution
Simulation
Execute Simulation Scenario
Replan
Execute Monitor
Plan SimulationScenario
Execute
Monitor
Start simulation devices. Install simulation
scenario specification on simulation
devices. Start (pause, resume, stop)simulation
scenario. Shutdown simulation devices.
Receive progress reports (simulation device
status and story status). Compare actual to
expected outcomes.
5
Scenario Description Concept

• A scenario description is the framework of a
  story that plays out over time. A scenario
  description provides enough information to get
  the story going, and supports the story by
  periodically providing unexpected events.

Set the scene actors ( motivations),
location, situation
Scenario Description
Event 1
Event 2
Event n
Forces/Sides, Units, Equipment (
Plans), Environment, Overall Situation
Scenario Execution
Event 1
Event 2
Event n
Time
6
Scenario Description Contents

• A scenario description should contain
• An initial situation description to set the
  stage.
• Location and environment.
• Players in the scenario (sides, units, equipment,
  etc.).
• What each of the players plans to do (on a
  per-player basis).
• Anything else (for example, relevant events from
  the past).
• A master events list
• Anything that materially changes the initial
  description in a way that would not normally
  happen according to the plans.
• Might extend to important events that occur
  according to plan (such as firing orders, etc.).

7
Current State of the Art
Self-contained system

• No standard for communication between planning
  and execution, which increases life cycle costs
  because
• Planned scenarios cannot be shared, so there is
  one planning system per execution system
• Lack of interoperability between simulation and
  C4I systems

Planning
Execution
Solve communications between planningand
execution for each pair of systems
Planning
Execution
Point communications solution
8
MSDL Background

• MSDL is the Military Scenario Development
  Language.
• MSDL is being developed by OOS to provide
  simulations with a mechanism for loading Military
  Scenarios.
• As a standard, MSDL is not being developed for
  simulation alone. The intent is for MSDL to
  define Military Scenarios that are independent of
  the application of that scenario.
• MSDL relies on military standards for data types,
  enumerations, precision, etc.

9
Definition of a Military Scenario

• In Block B of OOS development SIMCI held a
  workshop of Scenario Generation. In this
  workshop two definitions of the Military Scenario
  were documented. One definition identifies the
  Ontology the MSDL as a language. The second
  provides for the scope of MSDL within that
  Ontology.
• Ontology of a Military Scenario - A Military
  Scenario is bounded by the situation at one
  instant in time combined with the COA about to be
  taken in context to that situation.
• Military Scenario Military_Situation(t0)
  Course_of_Action(t1)

10
Definition of a Military Scenario Contd

• Within the defined Ontology, MSDL is scoped by
  the requirement to remain application
  independent. SIMCI identified a Military
  Scenario as including
• Core Data that all military scenarios must
  included.
• Common Data that any military scenario might
  include.
• Custom Data that is custom or application
  specific.

Custom
Common

• MSDL includes both the Core and Common portions
  of a Military Scenario

Core
11
MSDL Concept
Scenario Repository
CCIR HHQ Plan (MSDL) Intel Terrain Staff
Estimates SOPs ROEs METT-TC
Scenario
Planning
Execution
MSDL
MSDL
MSDE, C2PC, etc.
MSDL format
OneSAF, OTB, AWARS, etc.
12
This is a general case. A particular
configuration might use only one planner, no
COA Evaluator, and no Scenario Integrator.
Course of Action
Score
MSDL
CCIR HHQ Plan (MSDL) Intel Terrain Staff
Estimates SOPs ROEs METT-TC
Planned Scenario Part
MSDL
Course of Action
Score
Complete Scenario
MSDL
Splitter
Scenario Integrator
MSDL
Planned Scenario Part
MSDL
Course of Action
Score
MSDL
Planned Scenario Part
MSDL
13
This is a general case. A particular
configuration might use either simulation or
operational branches.
Course of Action
Score
MSDL
Planned Scenario Part
MSDL
MSDL
Simulation (virtual/constructive)
ScenarioInstantiator
MSDL
Operations/Live
MSDL
Course of Action
Score
MSDL
Planned Scenario Part
MSDL
14
Sources of MSDL Content (Core/Common)

• Situation
• The Military Situation is defined as the METT-TC
  in JP 1-02 as
• mission, enemy, terrain and weather, time,
  troops available and civilian
• Course of Action
• In Block B, the Course of Action data is
  graphically represented by Overlays and Tactical
  Graphics (graphic representation).
• Course of Action is being implemented in Block C
  to include the synchronization of actions to be
  executed. The execution matrix and MDMP are
  being used to develop this data model.

15
MSDL Concepts

• The MSDL schema provides for an interchange
  format of military Scenarios.
• However, the schema alone is not sufficient to
  communicate a common understanding of that data.
  
• There are a number of concepts which provide that
  common understanding. Many of those concepts are
  contained in the MIL STD 2525B document. The
  others are presented here for common
  understanding
• Scenario Perspective
• Command Relations
• Forces and Sides
• Radio Nets
• Enumerations

16
MSDL Concepts Forces and Sides

• The Forces and Sides data in MSDL provide a high
  fidelity means for defining complex relationships
  between Forces on different sides of a Military
  Scenario (conflict).
• For conventional scenarios a BLUFOR/OPFOR model
  can be built into the Force/Side data, or
  Affiliation can be set to Friend or Hostile to
  identify units as belonging to the conventional
  BLUFOR or OPFOR sides.

17
MSDL Concepts Scenario Perspective

• In order to identify the Affiliations of Units
  from the Force Side data, a perspective must be
  taken such that the Relationship between Sides
  can be used to identify the affiliations between
  Units
• PlanningUnitHandle Provides the basis for a
  perspective. The Relationships of the Side above
  the Planning Units highest superior dictate the
  affiliation of all units.
• NOTE These rules only apply if the scenario is
  following a Force/Side model. If Forces and
  Sides are not used, the Affiliation of units and
  equipment identify each as belonging to the
  BLUFOR or OPFOR side.

18
MSDL Schema Overview

• Options
• Plan Course of Action.
• Environment Terrain and Weather.
• Forces and Sides Force Structure.
• Units Task Organizations
• Equipment Equipment of the units.
• Installations Installations (facilities etc).
• Overlays Tactical Overlays.
• Tactical Graphics Of unit plans.

19
COA

• Each COA represents a branch on the plan.
• Each COA stands alone, but can branch to other
  COAs.
• COA Types
• ADMIN/LOGISTICS ORDER
• AIR MISSION
• AIR TASKING ORDER
• BATTLE COMMAND ORDER
• CONVENTIONAL FIRE MISSION
• FIRE SUPPORT PLAN
• FIRE SUPPORT ORDER
• FRAGO
• GROUND MEDEVAC MISSION
• OPORD
• SIGNAL ORDER

20
For details, please visit www.onesaf.org