I’m looking for the evolution from general verbal or written descriptions -> semi-formalized processes and representations that still use general-purpose tools, e.g. MSELs -> formalized, specialized, machine-readable formats, e.g. MSDL.

 

KLM

---

Katherine L. Morse, PhD

Principal Professional Staff

JHU/APL

11100 Johns Hopkins Road

Laurel, MD  20723-6099

(240)917-9602 (w)

(858)775-8651 (m) 

 

 

From: SAC-PDG-PSG-C2SIM <[log in to unmask]> on behalf of Douglas Reece <[log in to unmask]>
Reply-To: SAC-PDG-PSG-C2SIM <[log in to unmask]>
Date: Saturday, January 26, 2019 at 3:38 PM
To: "[log in to unmask]" <[log in to unmask]>
Subject: Re: History of scenario formats

 

Katherine:

 

So MSDL is an xml schema. To make an MSDL scenario, a puckster has to use a tool to enter data from a spreadsheet and export the xml... right? 

I'm not trying to be difficult, but trying to understand correctly what it is you're looking for, and not. 

 

Doug

 

On Sat, Jan 26, 2019, 5:04 PM Morse, Katherine L. <[log in to unmask] wrote:

If you’ve got a list of those, I’d love to have it. But it also might not be the case entirely. The process could be manual using pucksters with the pucksters reading from a spreadsheet of document.

 

KLM

---

Katherine L. Morse, PhD

Principal Professional Staff

JHU/APL

11100 Johns Hopkins Road

Laurel, MD  20723-6099

(240)917-9602 (w)

(858)775-8651 (m) 

 

 

From: SAC-PDG-PSG-C2SIM <[log in to unmask]> on behalf of Douglas Reece <[log in to unmask]>
Reply-To: SAC-PDG-PSG-C2SIM <[log in to unmask]>
Date: Saturday, January 26, 2019 at 8:43 AM
To: "[log in to unmask]" <[log in to unmask]>
Subject: Re: History of scenario formats

 

Katherine:

 

You mention a JTLS "proprietary" format. If you include those, then probably every constructive simulation product has a format that could be included as well.

 

Doug

 

On Fri, Jan 25, 2019, 5:44 PM Katherine L. Morse <[log in to unmask] wrote:

So, here's what I've found so far. If anyone has any other leads, I'd appreciate having them.

One of the earliest scenario generators was the Training Scenario Generator (TSG), developed for a NASA space shuttle flight controller simulation [Loftin 1987]. As early as 1997 [Bowers], attempts were made to automatically generate training scenarios (event-sets) from a database of individual training requirements (events).

The Joint Theater Level Simulation (JTLS) [Rolands], begun in 1983 [Wikipedia], has a proprietary scenario database.

Joint Exercise Management Module (JEMM) [NATO] is a web-based application designed to support exercise planners, control organizations, and analysts in the design, conduct, and analysis of training and exercise events. JEMM focuses on Main Events List/Main Incidents List (MEL/MIL) scripting and management. JEMM was first deployed in 2004.

The Joint Training Data Services (JTDS) for the Joint Live, Virtual, Constructive (JLVC) Federation, first released in 2007 [Bowers], provides data inputs to scenario generation. Scenarios are stored in JLVC-specific Order of Battle System (OBS) XML format to be read at federation initialization. [This suggests that only the OOB is stored in the scenario file and not runtime events

Coalition Battle Management Language (C-BML) [SISO 2014] is a standard language for expressing and exchanging plans, orders, requests, and reports across command and control (C2) systems, live, virtual and constructive (LVC) modeling and simulation (M&S) systems, and autonomous systems participating in Coalition operations. It describes the data model as a subset of Joint Consultation Command and Control Information Exchange Data Model (JC3IEDM) and specifies the information exchange content and structure in the form of an XML schema. C-BML is properly a runtime data exchange model for expressing events during simulation execution rather than a scenario specification language.

It wasn’t until the advent of Military Scenario Definition Language (MSDL) [SISO 2006] that effort shifted to defining a tool-independent scenario format. The MSDL XML schema is based on the schema of the same name developed for the OneSAF Objective System (OOS). The result of this effort is the MSDL standard [SISO 2015].

There are references to Army Warfare System (AWARS) Millennium Challenge 2002/Combined Arms Planning and Execution System (MC2/CAPES) scenarios, but no evidence of a prescribed format.

KLM
---
Katherine L. Morse, PhD
Principal Professional Staff
JHU/APL
11100 Johns Hopkins Road
Laurel, MD  20723-6099
(240)917-9602 (w)
(858)775-8651 (m)

########################################################################

To unsubscribe from the SAC-PDG-PSG-C2SIM list, click the following link:
https://discussions.sisostds.org/index.htm?SUBED1=SAC-PDG-PSG-C2SIM&A=1

 


To unsubscribe from the SAC-PDG-PSG-C2SIM list, click the following link:
https://discussions.sisostds.org/index.htm?SUBED1=SAC-PDG-PSG-C2SIM&A=1

 


To unsubscribe from the SAC-PDG-PSG-C2SIM list, click the following link:
https://discussions.sisostds.org/index.htm?SUBED1=SAC-PDG-PSG-C2SIM&A=1

 


To unsubscribe from the SAC-PDG-PSG-C2SIM list, click the following link:
https://discussions.sisostds.org/index.htm?SUBED1=SAC-PDG-PSG-C2SIM&A=1



To unsubscribe from the SAC-PDG-PSG-C2SIM list, click the following link:
https://discussions.sisostds.org/index.htm?SUBED1=SAC-PDG-PSG-C2SIM&A=1