Transcript Military Scenario Definition Language

Military Scenario Definition Language
Standardization Overview
Presented by Maj Kevin Galvin
Authors: Jeff Abbott & Rob Wittman
For additional info see paper 06S-SIW-018
Agenda
• Introduction
• SISO Study Group to Product Development
Group
• MSDL Drafting Group Schedule and Activity
• As Time Allows
– FY05 MSDL Development Activity
Snapshot
• MATREX Activity
• OneSAF Objective System (OOS) Activity
2
Problems/Issues
• The close coupling of
scenario development tools
and simulations
– limits third party tool
development and
– automated sharing of
scenarios between
simulations and between C4I
devices.
• Assumptions,
interpretations, and typos
are introduced as Military
personnel or Subject Matter
Experts create and handover scenario products for
input into specific
simulations and C2
databases.
Simulation
Scenario #1
Simulation #1
Simulation
Scenario #2
Simulation #2
•
•
TYPO
!
DATA +
ERROR
S
Military
Scenario
3
Need For Common MSDL Specification
Scenario Development Tool #1
MSDL Formatted
Documents
Simulation
Scenario #1
Simulation #1
Scenario Development Tool #2
Military Scenario
Repository
Simulation
Scenario #2
Simulation
Scenario #3
Simulation #2
Simulation #3
4
MSDL Architectural Characteristics
• Separation of Code from Data
– MSDL XML Schema explicitly defines
allowable data types, constraints,
enumerations, and hierarchical
relationships
• Use of Industry Standards
– World-Wide Web Consortium (WC3)
XML
• Application Independence
– Community wide access for tools to
develop or modify military scenarios
– Community wide access to use existing
military scenarios
C2PC
• Separation of Concerns
– MSDL focuses on military scenario
information not on application specific,
exercise control specific, or other
simulation initialization areas
5
MSDL High Level Design
• Military Scenario is:
Current Situation(tn)
+ Course of Action(tn+1)
= Military Scenario(tn)
• Core, Common and Custom
scenario data
– MSDL includes Core and
Common data
• MIL STD 2525B
• AUTL
• Other standards & doctrine
Custom
Common
Core
– Custom is only included if it can
be abstracted away through a
common data model
6
SISO Study Group to Product Development
Group
7
Product
Development
Group Kickoff
5 April 2006
MSDL SISO Standardization
• MSDL SG approved by SISO in
Spring, 2005
• Participants represent a wide body
of interest, including:
Mtg 6
I/ITSEC
Orlando
29 Nov. 2005
Mtg 4
George Mason
Univ, VA
3 Aug. 2005
17 Participants
– Representatives from over 5 different
nations
Mtg 2
Orlando, FL
– Over 100 participants at SG meetings 8-10 June 2005
35 Participants
– Industry, Academia, Government
– 98 participants on MSDL SG reflector
• Active coordination with C-BML SG
has brought about harmonization of
plans for Product Development
Group (PDG)
• Product Nomination approved by
SAC 27 Feb. 2006 and EXCOM
March 8, 2006
Mtg 5
Fall SIW
Orlando, FL
22 Sept. 2005
Mtg 3
Euro-SIW
Toulouse, France
29 June 2005
27 Participants
Mtg 1
Spring SIW
San Diego, CA
6 April 2005
56 Participants
8
MSDL Study Group Vetted Products
Military Scenario
Scenario
Study Group
Universal Joint Task List
NBC
C3
CS
Sea Defense
Surface
Weather
Ground
Terrain
X
X
B
X
B
X
X
B
X
B
X
B
X
B
B
B
X
B
B
X
X
X
B
X
Army
O
P
P
P
P
P
P
P
P
P
P
Army, SOF
Army
Army
Army, SOF
Int'l, Air
Force, Sea,
SOF
Int'l, Army,
Air Force,
Sea
Joint/Int'l
Joint
Joint
Army
Joint/Int'l
Army, Air
Force
Joint
Coalition
Navy,
Marine,
Army
Army
O
O
X
O
B
X
P
X
X
X
P
X
X
B
X
P
X
X
B
X
P
X
X
B
X
X
P
X
X
B
X
P
X
X
X
P
X
X
B
B
X
P
X
X
B
X
P
X
X
B
X
B
X
P
X
X
B
X
X
X
X
X
X
X
X
C
X
X
X
X
B
X
X
X
X
B
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
MAK
JCOFA
RD3
OPTI Metrics
AWARS
C3 Driver
ATT Group
ATT Group
Simventions
Simventions
PEO STRI
UK MOD
CTIA
X
P
X
X
X
B
X
X
X
X
X
X
X
X
X
X
X
X
B
X
X
X
X
X
X
X
X
X
X
B
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
B
X
X
X
X
X
X
X
X
X
X
X
X
Urban
AD
Army
Army
GEO BML
IMASE (ISGT)
WARSIM
ERDC
CAE
Ocean
FS
OneSAF
RDECOMMATREX
ACSIS
CSS
INTEL
• Definitions
Definitions
MCM
JFCOM
NSC
OPTIMetrics
TRAC
TRAC
MAN (Sea)
MAK
Technology
MAN (Air)
PEO
C3T/ARL:UT
ERDC
ATEC
PEO STRI
ERDC
CAE
MAN
(Ground)
PEO STRI
RDECOM
Doctrine
• Domain Spreadsheet
Environment
X
B X
Space
Operating Systems
Organization Program/Projec Domain
t/System
X
X
X
B B
X
X
X
X
C
X
X
X
X
C
X
X
X
X
X X
X
C
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X X
P = Producer, C = Consumer, B = Both, X = Interest, but undefined, O or blank No
Interest
• Review Process
• MSDL Specification Comment
Form
• Version .01 of the MSDL
Specification
MSDL Problem
Change Request
Form
MSDL Spec V .01
XML Schema
Data Dictionary
HTML Description
9
Execution
Initialization
C4I
Real
Infrastructure
Software
e.g. Middleware
Unit
Model
Soldier
Model
Robotic
Force
Tank
Real
Developed by Per Gustavsson
C-BML
<Initialize>
<Who> TANK
<WHAT>MOVE TACTICALLY
<WHERE> POS
<WHEN> TIME
<EXECUTE>
A Series of C-BML orders
C-BML, MSDL
MSDL
C4I
Model
Intention
Situation
Object
Signal
Evaluation
10
MSDL Draft Group Schedule (Draft)
ID
1
1.1
1.2
1.3
2
2.1
2.2
2.3
3
3.1
3.2
3.3
4
4.1
4.2
4.3
Task/Schedule Item
Conduct DAR-01/02 on Units/Equipment & Forces/Sides
Present DAR
DG Comments on DAR-01/02
Disposition comments, entering unclosed comments as
Conduct DAR-03/04 on Overlays & Tactical Graphics
Present DAR
DG Comments on DAR
Disposition comments, entering unclosed comments as
Conduct DAR-05/06 on Environment & Installations
Present DAR
DG Comments on DAR
Disposition comments, entering unclosed comments as
Conduct DAR-07/08 on MOOTW & Threats
Present DAR
DG Comments on DAR
Disposition comments, entering unclosed comments as
June
1-Jun
15-Jun
Review DAR-01/02
DAR-01/02
Comment
PCRs
Review DA
DAR-03/04
PCRs
PCRs
PCRs
11
Product Development Plan
• Specifies a common understanding of the development
cycles.
– Build/Development Cycles
Next Cycle (PCR)
SG Version
Candidate Extension DAR & Test
Verification
& Validation
Extension
Selection
Product
Updates
New Version
– Development Process
• Decision Analysis & Review Study
• Peer Reviews & Comments/Defects Resolution
• Problem Change Reports
– Process is Posted in the DG file area
• Changes in progress to make the process DG specific
12
Decision Analysis and Resolution (DAR)
documents
• Purpose
– Decision Analysis and Resolution Studies provide a common
understanding of decision made in moving the standard
forward.
• How Many
– 10 have been planned for acceptance of the study group version
(OneSAF MSDL development efforts).
– 2+ have been identified in addition the content in the SG
version.
• Rate of Production
– Objective of two per month was optimistic.
– Six have been released.
• When do we ballot
– Spring to Summer of 2007 balloting will occur for the initial
version 1.0
13
FY05 MSDL Development Snapshot
Modeling Architecture for Technology Research,
and Experimentation (MATREX) Activity
15
MSDL-MATREX C4ISR FACT Collaboration
CSAP&T
MSDE
MSDL
Phase I: Data Identification
MSO
HLA
CSAT
Phase II: Interface
Development
Control
Phase III: Business Rule Development
RC
for Populating Data
HLA RTI
RC
Fed 1
Fed 6
RC
RC
Fed 2
Fed 7
Fed 3
Sub-Fed
Fed 4
Fed 8
RC
Fed 5
Fed 9
Fed …
RC Indicates links through which remote creates are sent.
Simulation configuration data is also sent to all federates.
16
MATREX Additions to the MSDL Schema
• Name
• Date Time Group (DTG)
• TargetList:
Defines the structure of
a list of all the identified targets.
• Munitions: Defines the structure of a
list of all munitions associated with the
AGM.
• WeaponTargetPairing: Defines
the structure of a list of all weapon
(ammunition) target pairs.
• TargetSets:
Defines the structure of
a list of target sets that identify the
relative worth of sets of targets.
17
OneSAF Objective System (OOS) Activity
18
One Semi-Automated Forces (OneSAF) Objective
System (OOS)
•A composable, next generation CGF
•Represent a full range of operations, systems, and control processes (TTP)
•Entity up to brigade level
•Variable level of fidelity
•Supports multiple Army M&S domain (ACR, RDA, TEMO) applications.
Automated
Composable
Extensible
Interoperable
HLA & DIS
Capable
Capable of replacing legacy entitybased simulations: BBS,
OTB/ModSAF, CCTT/AVCATT SAF,
Janus, JCATS MOUT
Software only
Platform Independent
Field to:
•RDECs and Battle Labs
•National Guard armories
•Reserve training centers
•All active-duty brigades
•and battalions
•All FCS platforms
19
MSDL & The OOS Product Line Architecture
Framework
CAPES
C2PC
OneSAF Reuse Direction &
Guidance – Mandated using the
CCTT Commander’s Exercise
Initialization Toolkit (CEIT) as
starting point for OneSAF Military
Scenario Development Capability.
MSDL Schema, example, and
presentation available at
www.onesaf.org.
20
MSDE
21
Scenario Generation Phase Using ACSIS
Generated Data
C4I Devices
MCS
FBCB2
ASAS
FAADC2I
ACSIS
Military Scenario
(MSDL)
BCS3
AFATDS
OOS
Event Planner
(MSDE)
Military
Scenario
Repository
Military
Scenario
(MSDL)
OOS
Simulation
Controller
(MCT)
Military
Scenario
(MSDL)
OOS
C4I
Adapter
Short-Term Plan:
• Start with an ACSIS generated MSDL compliant file that has data
consistent with a C4I Data Load.
• Import data into MCT without modification and create simulation specific
file.
• Import data and initialize C4I Adapter .
22
ACSIS Proposed Extensions to MSDL (1/2)
• PlatformRoleInstance
– URN
– Role_Name
– IpAddress
– OR_Name
– EmailAddress
– BFASystem_Type
– BFA_Version
– EPLRS_RSID
– CommunicationsNetReferences
23
ACSIS Proposed Extensions to MSDL (2/2)
• CommunicationNetReference
– CommunicationNetType
– CommunicationNetid
– UnitOwnerHandle
24
MSDL Schema & 5 Ws
• Options
• Plan & COA
– Who, What, When, Where, Why
• Environment
– Where, When
• Force Structure
– Who
• Task Organizations
– Who
• Installations
– Where
• Overlays
• Tactical Graphics
– Where
• MOOTW Graphics
– What, When, Where
• Threats
25
MSDL & the 5Ws
• The UnitActivity element ties all this together
– Who – Units
– What – Task & COA Handle
– When – Trigger (Handle)
– Where – Trigger (Handle)
– Why – Task
26
MSDL & Why
• The Why element is specified by the
WhyEnumeration in the Task of a Unit Activity.
– Enumeration – restricted to values from Army Universal Task
List (AUTL)
– ActivityType – restricted to C2IEDM actions type enumerations
– WhyEnumeration – restricted to enumerations based on FM
101-5-1
27
MSDL Schema Refinement
• Original
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
MilitaryScenario.xsd
Units.xsd
Equipment.xsd
CoursesOfAction.xsd
CommandRelations.xsd
CommonElements.xsd
Plan.xsd
ForceSide.xsd
Installations.xsd
METOC.xsd
MILSTD2525B.xsd
MOOTW.xsd
Options.xsd
TacticalGraphics.xsd
Threats.xsd
Dcr.xsd
• Current
–
–
–
–
–
MilitaryScenario.xsd
UnitEnumerations.xsd
EquipmentEnumerations.xsd
TaskEnumerations.xsd
msdlElements.xsd
28
Questions?
Maj Kevin Galvin
C-BML Chair
[email protected]
Dr. Rob Wittman
OneSAF Architect
[email protected]
Jeff Abbott
MSDE Lead
[email protected]