2006-09 an architecture for demonstrating the … architecture for demonstrating the interplay of...
TRANSCRIPT
Calhoun: The NPS Institutional Archive
Faculty and Researcher Publications Faculty and Researcher Publications
2006-09
An Architecture for Demonstrating the
Interplay of Emerging SISO Standards
Gustavsson, Per
Paper 06F-SIW-069, Fall Simulation Interoperability Workshop, Simulation Interoperability
Standards Organization, Orlando FL
http://hdl.handle.net/10945/31186
2006 Fall SIW10th Anniversary
An Architecture for Demonstrating the Interplay of An Architecture for Demonstrating the Interplay of Emerging SISO StandardsEmerging SISO Standards
Curtis L. Blais, NPS MOVES Institute, USACurtis L. Blais, NPS MOVES Institute, USAPaul Gustavson, SimVentions, USAPaul Gustavson, SimVentions, USAPer Gustavsson, EricssonPer Gustavsson, Ericsson, Sweden, Sweden
Steven Reichenthal, Boeing Corporation, USASteven Reichenthal, Boeing Corporation, USA
1010--15 September 200615 September 2006
Paper 06FPaper 06F--SIWSIW--069069
2006 Fall SIW10th Anniversary
OutlineOutline
•• SISO Standardization EffortsSISO Standardization Efforts•• Technical ChallengeTechnical Challenge•• Demonstration System RequirementsDemonstration System Requirements•• Initial Proposed Demonstration SystemInitial Proposed Demonstration System•• Recommended Course of ActionRecommended Course of Action•• Summary/ConclusionsSummary/Conclusions
2006 Fall SIW10th Anniversary
SISO Standardization EffortsThe following standards have progressed to Product Development status:
– Base Object Model (BOM) Interface Specification– Coalition - Battle Management Language (C-BML)– Core Manufacturing Simulation Data– Commercial Off-the-Shelf Simulation Package Interoperability– Distributed Interactive Simulation Extension– Environmental Data Representation Standards– High Level Architecture (HLA)-Evolved– Link 11 A/B Network Simulation Standard– Link-16 Simulation Standard– Military Scenario Definition Language– Real-Time Platform Reference (RPR Federation Object Model (FOM)– Simulation Reference Markup Language (SRML)– Verification, Validation and Accreditation Overlay to Federation Development
Goal: Develop a Composite environment featuring interoperability standards.
2006 Fall SIW10th Anniversary
Technical ChallengeDevelop a composite demonstration environment…
– For demonstrating implementations of emerging standards to educate the community about the new standard and to show the benefit gained for system interoperability from its introduction
– For development of demonstrations and prototypes to present the concept and value to the community of new standards initiatives
– For compliance testing planned for the proposed standard
– For showing compatibility of the product with other SISO standards
2006 Fall SIW10th Anniversary
Demonstration System Requirements
Show a how several SISO standards can interplay in the same environment.
Reuse and integrate current test beds for the selected standards
Define scenario that – reflects properties of being complex, but – is still easy to understand
2006 Fall SIW10th Anniversary
Initial Proposed Demonstration SystemInitial Proposed Demonstration System
•• Selected ComponentsSelected Components•• Base Object Model (BOM)Base Object Model (BOM)
•• Coalition Battle Management Language (CCoalition Battle Management Language (C--BML)BML)
•• Distributed Interactive Simulation (DIS) Distributed Interactive Simulation (DIS) –– Extensible Extensible Markup Language (DISMarkup Language (DIS--XML)XML)
•• Military Scenario Definition Language (MSDL)Military Scenario Definition Language (MSDL)
•• Simulation Reference Markup Language (SRML)Simulation Reference Markup Language (SRML)
•• Demonstration System ArchitectureDemonstration System Architecture
2006 Fall SIW10th Anniversary
Fede
rate
(SO
M)
BOMAssembly
BOM 1
BOM 3
BOM n
CompositeInterface
Composition
Sim / System A
Representation Fede
ratio
n(F
OM
)Federate B
Federate X
Federate A
Aggr
egat
ion
Model#1
Model#2
Model#3
Model#n
- or -
- or -Theater W
arfare
Representation
BOM 2
BOM Palette - x
Choose what fits conceptual model?
A
B
CX
State MachinesPattern of Interplay
Events
User Requirements
Simulation Components
Simulation Systems• foms• federates
BOM – A piece part of a conceptual model, simulation object model, or federation object model, which can be used as a building block in the development and/or extension of a simulation or federation.
Weapons
Effect
Radio
Comms
Repair
Resupply
Detect / Jam
Definition Concept Standards
Illustration
Base Object Model (BOM)
2006 Fall SIW10th Anniversary
Model Identification (Metadata)
Notes
Lexicon (definitions)
Object Model Definition
HLA Object Classes
HLA Object Class Attributes
HLA Object Classes
HLA Interaction Classes
HLA Interaction Class Parameters
HLA Interaction Classes
HLA Data Types
Conceptual Model
Pattern Of Interplay
State Machine
Entity Type
Event Type
Model MappingEntity Type Mapping
Event Type Mapping
Base Object Model (BOM) StructureEssential metadata needed so thatthe BOM can be described, discovered and properly reused
Conceptual entitiesand the events whichoccur among thoseentities as well as thestates attainable bythose entities.
Mapping of conceptual entities and events to object model object and interaction classes.
Notes and definitionssupporting any of theabove mentionedelements
Object classes,interaction classes,and datatypes used to perform the behavior describedin the conceptualmodel.
BOMs are intended to support REUSE and COMPOSABILTY!
Application Domain
Description
Use Limitation
Use History *
Keyword Taxonomy/Value *
Purpose
Release Restriction *
Security Classification
Modification Date
Version
Type
Name
Application Domain
Description
Use Limitation
Use History *
Keyword Taxonomy/Value *
Purpose
Release Restriction *
Security Classification
Modification Date
Version
Type
Name
References *
Other
GlyphTypeImageAlternate TextHeightImage
POCs *TypeNameOrganizationTelephoneEmail
References *
Other
GlyphTypeImageAlternate TextHeightImage
POCs *TypeNameOrganizationTelephoneEmail
* Multiples Allowed
Not all these piecesare required for defining a BOM…
2006 Fall SIW10th Anniversary
Object (Class Structure) BOM
Behavior (Conceptual)BOM
Object Model Definition
Object Model Definition
Notes
Lexicon (definitions)
Object Model Definition
HLA Object Classes
HLA Object Class Attributes
HLA Object Classes
HLA Interaction Classes
HLA Interaction Class Parameters
HLA Interaction Classes
HLA Data Types
Model Identification (Metadata)Model Identification (Metadata)
Model MappingEntity Type Mapping
Event Type Mapping
Conceptual Model
Pattern Of Interplay
State Machine
Entity Type
Event Type
Notes
Lexicon (definitions)
HLA Data Types
Example: RPR BOMs
2006 Fall SIW10th Anniversary
We also found a logical connection between the “patterns of interplay” being represented by the RPR FOM (going back to DIS PDU families) and the “HLA Interaction classes” that were defined. So we decided to keep the interaction classes with the conceptual model
Behavior RepresentationsWeapon EffectsLogistics SupportCollisionEntity State UpdateSimulation ManagementDistributed Emission RegenerationRadio CommunicationsEntity ManagementMinefieldSynthetic Environment
Behavior RepresentationsWeapon EffectsLogistics SupportCollisionEntity State UpdateSimulation ManagementDistributed Emission RegenerationRadio CommunicationsEntity ManagementMinefieldSynthetic Environment
Object RepresentationsEntity Object TypesEnv Object TypesMinefield Object TypesSignal Object Types
Object RepresentationsEntity Object TypesEnv Object TypesMinefield Object TypesSignal Object Types
We found the easy thing to do was pull out the HLA object classes into object groupings.
Remember this is just one way!!!
Example: RPR BOMs…
2006 Fall SIW10th Anniversary
BOM Illustration #1
Derived from RPR FOM
State MachinesPattern of Interplay
pattern actions
Weapons Effect
states
Federation Activities Federate Capability
2006 Fall SIW10th Anniversary
How Are BOMs To Be Used…Functionally?Profile
BOMs
BOM 1
BOM 2
BOM n
Conceptual ModelView
Object Model View
Weapons
Effect
Detect /
Jam
Radio
Comms
BOM zSup
plier
BOM b
BOM a
Platform
Human
BOM c
BOM d Radar
Munition
Logistics
CAP
SupportCollis
ion
BOMAssembly
CompositeInterface
Composition Representation
Federate B
Federate X
Federate A
Theater Warfa
re
Representation
Federationfor
Joint Training
Homeland Defense
Training FOM
Operation Freedom
Training FOM
Behavior (Conceptual)
BOMsObject(Class
Structure) BOMs
These can be swapped out as modules
New “Assemblies”can be “composed”
and (for HLA) turned into FOMs
2006 Fall SIW10th Anniversary
What it is / What it isn’t?Interface
– essential elements provided by a component or piece-part
• Conceptual Model– Patterns of Interplay– State Machines– Entities– Events
• Object Model– HLA Object Classes– HLA Interactions Classes
• Model Mappings– Template standard (SISO PDG)– language neutral notation (XML)
Implementation– Component / piece-part functionality
captured / contained independently– Examples…
• Source code / federate code, • Interpreted code
– SRML / JavaScript• Byte Code (java)• Binary Object
– Windows DLL,– COM (ActiveX),– Unix DSO, or
Benefits of interface/implementation separation
– allows BOMs to serve as building blocks for supporting composability– Includes the composition of
• object models, • federate capabilities, and / or• federation agreements
– Not only for HLA!
BOM BCI
BOMs however can serve as interface for such implementations
2006 Fall SIW10th Anniversary
Coalition Battle Management Language (C-BML)
An unambiguous language for expressing orders, commands, requests, and reports that can be understood and acted upon by live (real), constructive (simulated), and robotic (real or simulated) forces.
C2 System
SimulationSystem
C2 System
RoboticSystem
BML tasking:Command and ControlForces and Equipment
BML reporting:Provide forSituational Awareness
2006 Fall SIW10th Anniversary
Coalition Battle Management Language (C-BML)
Triangular View of C-BML
XMLWeb ServicesGrid Services
…
Terms rooted inMilitary Doctrine,
such asAAP-6 …
Command & Control Information ExchangeData Model C2IEDM/JC3IEDM
C-BMLDoctr
ine
Representation
Protocol
2006 Fall SIW10th Anniversary
Distributed Interactive Simulation –Extensible Markup Language (DIS-XML)
ProgrammingLanguage
Objects
IEEE-1278.1Binary Format
XML
Well-established, matureformat and protocol, but information not readily available to non-DIS applications
Opens the information inDIS packets to wide-spreadapplication using readilyavailable software tools
2006 Fall SIW10th Anniversary
Military Scenario Definition Language (MSDL)
Mechanism for loading military scenarios
Scenarios can be shared between simulations and C4I
Improve scenario consistency between federated simulations
2006 Fall SIW10th Anniversary
Military Scenario Definition Language(MSDL)
MSDL is defined by an XML Schema describing:– Options: Identify task organizations, data standards being used and application specific options – Environment: Time, terrain, weather, astronomy, and METOC graphics.– Force Structure: Specifies the sides of the battle to which specific forces are aligned.– Task Organizations: Identify units and equipment, where equipment generally equates to
entities in a simulation. – Installations: Identify military facilities.– Overlays: Provide a mechanism for linking Tactical Graphics to specific Overlays or Layers to
be placed on a tactical map display. – Tactical Graphics: Provide the definition of control measures (by referencing particular
Overlay entries).– Military Operations Other Than War (MOOTW) Graphics: MOOTW symbol
modifiers as defined in MIL-STD-2525B.– Threats: Specify non-military (threat) organizations, including characterization of the effects of
threat-based actions/activities.– Plan: Provides descriptive information on the scenario as well as executable courses of action.
Information includes an executive summary of the Operations Order (OPORD), scenario objectives, references to doctrine, and planning documents.
2006 Fall SIW10th Anniversary
Simulation Reference Markup Language (SRML)
General purpose, XML-based language and framework for precise, unambiguous, and executable descriptions of model behavior
Engine description uses the same language-independent features afforded by a common web browser
Add simulation behavior, load, and execute arbitrary XML documents
2006 Fall SIW10th Anniversary
SRML is patterned after HTML,The engine, like a Web browser, complements
HLA
Presentation Markup(HTML)
SimulationMarkup(SRML)
SRML Engine(Run Time
Infrastructure)
FederationMarkup
(OMT FOM)
HLA RTIRun Time
Infrastructure
Web Browser(Run Time
Infrastructure)
Inter-operability
Reuse
InterplayInterchangeInterchangeGoal:
InterfaceImplementImplementGoal:
2006 Fall SIW10th Anniversary
SRML Simulation Engine
Output
SRML Engine
ITEM Manager
SIM RandomGen
Sim Primitives
Math and Stat
SRML Engine
ITEM Manager
SIM RandomGen
Sim Primitives
Math and Stat
Remote ServicesOutput
Simulation Model
XML Document
Engine Capabilities:•Native XML foundation•Discrete event manager•Web access•Scripting•Plug-ins•Extensibility•Language independent API•Components•Model downloading
HLA
2006 Fall SIW10th Anniversary
SRML Benefits
Potential benefits from using SRML include:– Reduced cost– More accessibility– Interoperability through interchange– Develop a simulation once and load it into any capable
engine
2006 Fall SIW10th Anniversary
Proposed ScenarioObjective: Anti-Terrorism/Force Protection (AT/FP) of a
harbor Features: One or more unmanned surface vehicles (USVs),
unmanned air vehicles (UAVs), unmanned undersea vehicles (UUVs), and unmanned ground vehicles (UGVs)
Mission: To create a layered defense by patrolling a protected area and alerting response teams (also unmanned, for purposes of this scenario) when a contact is identified as suspect or hostile
Rationale: Such a scenario has clear implications to military planners as well as cross-over into the public Homeland Security arena. Whether live or simulated, robotic forces use precisely the same set of orders.
2006 Fall SIW10th Anniversary
Roles of Selected StandardsBOM – conceptual modeling of each of the entities (robotic platforms) and specification of interactions (patterns of interplay) among the entities; identification of object classes and interactions classes that can be used (mapped to conceptual model)
C-BML – specification of the orders given to each of the robotic platforms, either as scripted behaviors or goal-directed tasks
DIS-XML – runtime state updates that can be used for visualization of the scenario, logging of state changes, and entity messaging
2006 Fall SIW10th Anniversary
Roles of Selected Standards (cont’d)
MSDL – description of all initialization data regarding the locale, forces, force structures, environment, control measures and other information to preserve the scenario set-up for re-use
SRML – representation of entity behaviors and dynamic execution of actions and interactions of the entities.
2006 Fall SIW10th Anniversary
Initial Demonstration System Architecture
DISHLA
SRML Engine
ITEM Manager
SIM RandomGen
Sim Primitives
Math and Stat
MSDL Which SRML modelsWhich Real Entities
Which Other Sim partsFederates, Initial Plans
DIS-XML…
Remote Services
C-BML
Output
BOM
EWUSVRadar
UAV
UGV
Sonar Torpedo
Mine
Sensors WeaponsC2
UUV
AUV 62FSonar
UUV
TorpedoMine
VideoComm.
ARIESUUV
EWSAR/MTI
V-150UAV
EO/IR
EWEO/IR
ScanEagleUAV
BIO
TUGVUGV
WeaponSensors
SeaFoxUSV
SensorsWeapon
RoboSkiUSV
SensorsWeapon
System of System ModelSRML Engine
ITEM Manager
SIMSimulation Model
(XML-SRML)
RandomGen
Sim Primitives
Math and Stat
AUV 62FARIES
EWSAR/MTI
V-150UAV
EO/IR
SeaFoxUSVSenso
rsWeapons
OperationalC2/EW
UAV
UGV
USV
AUV/UUV
Fusion
UGVARV
WeaponSensors
DIS-XML
Simulation Model
C-BML
AUV 62FScanEagl
e
TUGV ARV
V-150
SeaFox RoboSki
ARIES
MSDL
SRML
BOM
BOM
EWUSVRadar
UAV
UGV
Sonar Torpedo
Mine
Sensors WeaponsC2
UUV
AUV 62FSonar
UUV
TorpedoMine
VideoComm.
ARIESUUV
EWSAR/MTI
V-150UAV
EO/IR
EWEO/IR
ScanEagleUAV
BIO
TUGVUGV
WeaponSensors
SeaFoxUSV
SensorsWeapon
RoboSkiUSV
SensorsWeapon
UGVARV
WeaponSensors
Simulation Model
C-BML
AUV 62F
ScanEagle
TUGV ARV
V-150
SeaFox RoboSki
ARIES
MSDL
SRML
BOM
2006 Fall SIW10th Anniversary
Initial Demonstration System Architecture
DISHLA
SRML Engine
ITEM Manager
SIM RandomGen
Sim Primitives
Math and Stat
MSDL Which SRML modelsWhich Real Entities
Which Other Sim partsFederates, Initial Plans
DIS-XML…
Remote Services
C-BML
Output
BOM
EWUSVRadar
UAV
UGV
Sonar Torpedo
Mine
Sensors WeaponsC2
UUV
AUV 62FSonar
UUV
TorpedoMine
VideoComm.
ARIESUUV
EWSAR/MTI
V-150UAV
EO/IR
EWEO/IR
ScanEagleUAV
BIO
TUGVUGV
WeaponSensors
SeaFoxUSV
SensorsWeapon
RoboSkiUSV
SensorsWeapon
System of System ModelSRML Engine
ITEM Manager
SIMSimulation Model
(XML-SRML)
RandomGen
Sim Primitives
Math and Stat
AUV 62FARIES
EWSAR/MTI
V-150UAV
EO/IR
SeaFoxUSVSenso
rsWeapons
OperationalC2/EW
UAV
UGV
USV
AUV/UUV
Fusion
UGVARV
WeaponSensors
DIS-XML
Simulation Model
C-BML
AUV 62FScanEagl
e
TUGV ARV
V-150
SeaFox RoboSki
ARIES
MSDL
SRML
BOM
C-BML
OperationalC2/EW
UAV
UGV
USV
AUV/UUV
Fusion
2006 Fall SIW10th Anniversary
Initial Demonstration System Architecture
DISHLA
SRML Engine
ITEM Manager
SIM RandomGen
Sim Primitives
Math and Stat
MSDL Which SRML modelsWhich Real Entities
Which Other Sim partsFederates, Initial Plans
DIS-XML…
Remote Services
C-BML
Output
BOM
EWUSVRadar
UAV
UGV
Sonar Torpedo
Mine
Sensors WeaponsC2
UUV
AUV 62FSonar
UUV
TorpedoMine
VideoComm.
ARIESUUV
EWSAR/MTI
V-150UAV
EO/IR
EWEO/IR
ScanEagleUAV
BIO
TUGVUGV
WeaponSensors
SeaFoxUSV
SensorsWeapon
RoboSkiUSV
SensorsWeapon
System of System ModelSRML Engine
ITEM Manager
SIMSimulation Model
(XML-SRML)
RandomGen
Sim Primitives
Math and Stat
AUV 62FARIES
EWSAR/MTI
V-150UAV
EO/IR
SeaFoxUSVSenso
rsWeapons
OperationalC2/EW
UAV
UGV
USV
AUV/UUV
Fusion
UGVARV
WeaponSensors
DIS-XML
Simulation Model
C-BML
AUV 62FScanEagl
e
TUGV ARV
V-150
SeaFox RoboSki
ARIES
MSDL
SRML
BOM DISDIS-XML
I’d like to see us marry up the RPR BOMs with the DIS-XML
2006 Fall SIW10th Anniversary
Initial Demonstration System Architecture
DISHLA
SRML Engine
ITEM Manager
SIM RandomGen
Sim Primitives
Math and Stat
MSDL Which SRML modelsWhich Real Entities
Which Other Sim partsFederates, Initial Plans
DIS-XML…
Remote Services
C-BML
Output
BOM
EWUSVRadar
UAV
UGV
Sonar Torpedo
Mine
Sensors WeaponsC2
UUV
AUV 62FSonar
UUV
TorpedoMine
VideoComm.
ARIESUUV
EWSAR/MTI
V-150UAV
EO/IR
EWEO/IR
ScanEagleUAV
BIO
TUGVUGV
WeaponSensors
SeaFoxUSV
SensorsWeapon
RoboSkiUSV
SensorsWeapon
System of System ModelSRML Engine
ITEM Manager
SIMSimulation Model
(XML-SRML)
RandomGen
Sim Primitives
Math and Stat
AUV 62FARIES
EWSAR/MTI
V-150UAV
EO/IR
SeaFoxUSVSenso
rsWeapons
OperationalC2/EW
UAV
UGV
USV
AUV/UUV
Fusion
UGVARV
WeaponSensors
DIS-XML
Simulation Model
C-BML
AUV 62FScanEagl
e
TUGV ARV
V-150
SeaFox RoboSki
ARIES
MSDL
SRML
BOM
SRML Engine
ITEM Manager
SIM RandomGen
Sim Primitives
Math and Stat
Remote Services
System of System ModelSRML Engine
ITEM Manager
SIMSimulation Model
(XML-SRML)
RandomGen
Sim Primitives
Math and Stat
AUV 62FARIES
EWSAR/MTI
V-150UAV
EO/IR
SeaFoxUSVSenso
rsWeapons
OutputSimulation Model
C-BML
AUV 62FScanEagl
e
TUGV ARV
V-150
SeaFox RoboSki
ARIES
MSDL
SRML
BOM
2006 Fall SIW10th Anniversary
Initial Demonstration System Architecture
DISHLA
SRML Engine
ITEM Manager
SIM RandomGen
Sim Primitives
Math and Stat
MSDL Which SRML modelsWhich Real Entities
Which Other Sim partsFederates, Initial Plans
DIS-XML…
Remote Services
C-BML
Output
BOM
EWUSVRadar
UAV
UGV
Sonar Torpedo
Mine
Sensors WeaponsC2
UUV
AUV 62FSonar
UUV
TorpedoMine
VideoComm.
ARIESUUV
EWSAR/MTI
V-150UAV
EO/IR
EWEO/IR
ScanEagleUAV
BIO
TUGVUGV
WeaponSensors
SeaFoxUSV
SensorsWeapon
RoboSkiUSV
SensorsWeapon
System of System ModelSRML Engine
ITEM Manager
SIMSimulation Model
(XML-SRML)
RandomGen
Sim Primitives
Math and Stat
AUV 62FARIES
EWSAR/MTI
V-150UAV
EO/IR
SeaFoxUSVSenso
rsWeapons
OperationalC2/EW
UAV
UGV
USV
AUV/UUV
Fusion
UGVARV
WeaponSensors
DIS-XML
Simulation Model
C-BML
AUV 62FScanEagl
e
TUGV ARV
V-150
SeaFox RoboSki
ARIES
MSDL
SRML
BOM
MSDL Which SRML modelsWhich Real Entities
Which Other Sim partsFederates, Initial Plans
DIS-XML…
2006 Fall SIW10th Anniversary
Initial Demonstration System Architecture
DISHLA
SRML Engine
ITEM Manager
SIM RandomGen
Sim Primitives
Math and Stat
MSDL Which SRML modelsWhich Real Entities
Which Other Sim partsFederates, Initial Plans
DIS-XML…
Remote Services
C-BML
Output
BOM
EWUSVRadar
UAV
UGV
Sonar Torpedo
Mine
Sensors WeaponsC2
UUV
AUV 62FSonar
UUV
TorpedoMine
VideoComm.
ARIESUUV
EWSAR/MTI
V-150UAV
EO/IR
EWEO/IR
ScanEagleUAV
BIO
TUGVUGV
WeaponSensors
SeaFoxUSV
SensorsWeapon
RoboSkiUSV
SensorsWeapon
System of System ModelSRML Engine
ITEM Manager
SIMSimulation Model
(XML-SRML)
RandomGen
Sim Primitives
Math and Stat
AUV 62FARIES
EWSAR/MTI
V-150UAV
EO/IR
SeaFoxUSVSenso
rsWeapons
OperationalC2/EW
UAV
UGV
USV
AUV/UUV
Fusion
UGVARV
WeaponSensors
DIS-XML
Simulation Model
C-BML
AUV 62FScanEagl
e
TUGV ARV
V-150
SeaFox RoboSki
ARIES
MSDL
SRML
BOM
2006 Fall SIW10th AnniversaryPlan of Action
The following is a preliminary set of tasks and possible timeline for preparing for the Spring SIW demonstration:
– October 2006: Kick-off meeting (teleconference) BOM, C-BML, DIS-XML, MSDL, and SRML
– November 2006: Finalize scenario details regarding types and quantities, behaviors and controlled (scripted or goal-driven). Initial MSDL description of the scenario. candidate workbenches, platforms, tools etc. to be used.
– December 2006: Develop BOM object model definitions and conceptual models of the entities. Refine the MSDL scenario description. Create C-BML expressions of the orders to be given to and executed by the autonomous vehicles.
– January 2007: Refine BOM patterns of interplay and state machine descriptions in coordination with SRML description of same.
– February 2007: Begin integration of various descriptions into executable environment, generating DIS-XML messages to drive independent visualization (e.g., NPS AUV Workbench).
– March 2007: Finalize integration of the various representations demonstrating use of the selected standards for the chosen scenario. Dry run Spring SIW demonstration narrative and actions.
– April 2007: Demonstration at Spring SIW.
2006 Fall SIW10th Anniversary
Recommendations
We invite other PDGs to consider how they can participate in the Spring demonstration.
We recommend that SISO consider – the concept of establishing a standing demonstration test
bed– that can be used by Product Development Groups – to demonstrate how emerging standards fit into the big
picture – to complement each other and address major
interoperability issues
2006 Fall SIW10th Anniversary
Summary/Conclusions
The proposed demonstration architecture will show capabilities of the BOM, C-BML, DIS-XML, MSDL and SRML working together for a common scenario.
Coordination of the effort will be challenging, particularly considering that most efforts supporting SISO are performed on a volunteer basis, but the near and long-term benefits to the community would be significant.
2006 Fall SIW10th AnniversaryQuestions?Questions?
Curtis BlaisCurtis Blais Paul GustavsonPaul GustavsonNPS MOVES InstituteNPS MOVES Institute [email protected]@nps.edu [email protected]@simventions.com
Per GustavssonPer Gustavsson Steven ReichenthalSteven ReichenthalUniversity of University of SkSköövdevde Boeing CorporationBoeing [email protected]@his.se [email protected]@boeing.com