HLA Object Model Data Dictionary Population and Use SIW99S172

1
HLA Object ModelData DictionaryPopulation and
UseSIW-99S-172

• Randy Robertson, Margie Dey, and Roy Scrudder
• Applied Research Laboratories
• The University of Texas at Austin
• [phone]
• scrudder_at_arlut.utexas.edu

2
Questions to be Answered Today

• What is the Object Model Data Dictionary (OMDD)?
• Why should I use the OMDD?
• What will I find in the OMDD?
• How were OMDD contents developed?
• How does use of the OMDD fit within the FEDEP?
• How do I use OMDD contents?
• What usage has the OMDD seen to date?

3
Object Model Data Dictionary

• A web-based repository of common content for the
  creation of HLA SOMs and FOMs
• Assists users in
• Developing object models using common data (by
  downloading OMDD data to use with OMDT)
• Relating simulations to real world systems
• Will be maintained/ supported by DMSO on a
  long-term basis

4
Options for Object Model Content

• HLA is defined as an architecture it does not
  mandate standards for the content of FOMs and
  SOMs.
• Options for specifying object model contents
  include
• 1. Single, structured object model for all
  simulations
• Approach used by Distributed Interactive
  Simulation (Protocol Data Units)
• 2. Constrain all object model contents to a set
  of standards
• 2a. Limit the number of FOMs and SOMs that can be
  used, or
• 2b. Limit the allowable content for FOMs and SOMs
• 3. Provide a set of object model components for
  construction of FOMs and SOMs
• Provide as set of reusable components
• Dont constrain object model builders to only use
  components from that set
• 4. Allow unconstrained and unguided specification
  of object model contents

5
Object Model Content Tradeoffs
High
3. Extensible Set of OM Contents
1. Single Object Model
2a. Restricted Set of Object Models
2b. Restricted Object Model Contents
Ease of Object Model Construction and Reuse
4. Unconstrained OM Content
Low
Flexibility in Constructing Object Models to
Federation Needs
Low
High
6
Object Model Data Dictionary Rationale

• An OMDD approach provides a flexible set of
  common semantics and syntax for construction of
  complete FOMs and SOMs that
• Enhance the readability and understandability of
  FOMs and SOMs by using standard terminology
• Results in reusable FOMs and SOMs (in whole or in
  part)
• Results in SOMs that are easy to integrate into
  FOMs since they use common terminology
• Allows object model developers the flexibility to
  specify FOM and SOM contents when the OMDD does
  not have suitable components

7
Object Model Data Dictionary Contents

• Object Classes
• Names, definitions, notes, sources, and
  associated terms
• Interaction Classes
• Names, definitions, notes, sources, and
  associated terms
• Attributes/parameters
• Names, definitions, notes, sources, and
  associated terms
• Data type and units of measure (multiple
  representations)
• Complex data types
• Names, fields, and sources
• Enumerated data types
• Names, enumerators, representations, notes,
  sources, and enumerator synonyms

Object Classes
Interaction Classes
Attributes/ Parameters
Attr/Param Representations
Complex Data Types
Enumerate Data Types
CDT Fields
Enumerations
8
Object Model Data Dictionary Content Development
Object Model Data Dictionary
Object Model Components
Common Semantics and Syntax
FOMs and SOMs
Authoritative DD sources

• OMDD contents have been developed based on
• Real-time Platform Reference (RPR) FOM
• Engineering Federation FOM
• Joint Training Confederation (JTC) FOM
• Modular Semi-Automated Forces (ModSAF) SOM
• Eagle SOM
• Joint Theater Level Simulation (JTLS) - GCCS -
  NC3A FOM
• Synthetic Theater of War (STOW) 97 FOM

9
Object Model Data Dictionary Population Status -
February 1999

• OMDD population has continued at a steady rate
  since contents were first published in March 1998
• Current population statistics (as of 15 March
  1999)

10
HLA Federation Development andExecution Process
(FEDEP)
Program Objectives
Initial Planning Documents
Define Federation Objectives 1
Requirements
Develop Federation Conceptual Model 2
Federation Scenario
Available Resources
RTI RID File
Federation Objectives Statement
Federates
Federation Development Plan
Design and Develop Federation 3
Federation Conceptual Model
Integrate and Test Federation 4
Federation Requirements
The FEDEP identifies and describes the sequence
of activities necessary to construct an HLA
federation.
FOM
Execute Federation and Prepare Results 5
FED
Scenario Instance
Testing Data
Test Evaluation Criteria
Tested Federation
User Feedback
Corrective Actions
Reusable Products
11
Design and Develop Federation
Federation Scenario
Federation Requirements
Federation Development Plan
Initial Planning Documents
FOM
Design Federation 3.1
Develop Federation 3.2
FED
Identified Federates
Scenario Instance
SOMs
Object Model Library
Modified Federates
FOM
Supporting Resources
Federation Conceptual Model
Object Model Data Dictionary
Data Dictionary Elements
Federation Scenario
Other Resources
12
HLA Object Model Tools Suite
Object Model Development Tool
RTIs
FED
Data Dictionary Elements
FOMs SOMs
Object Model Library
Object Model Data Dictionary System
FOMs SOMs
HLA OM Dev Tools Mod 2, Update 1 31 Aug 98
12
13
OMDDS Operational Interfaces
OMDDS User (via Web Browser)
Internet
Central OMDDS Server
OMDD DIF File
OMDDS Database
OMDD Content User (via OMDT)
14
Identifying and Using OMDD Contents

• The OMDD System is available via the HLA Home
  Page (http//hla.dmso.mil) under the Federation
  Development Process and Tools link
• 1. Search and browse the OMDD contents
• 2. Copy selected items to your individual export
  area (use the Utilities to create a User ID the
  first time)
• 3. Export all or part of your individual export
  area to an OMDD Data Interchange Format DIF file
• 4. Set your OMDT to use the OMDD DIF file
  (ToolsPreferences menu for DMSO OMDT)
• 5. Include OMDD components in your FOM or SOM

OMDD
Search Results
Export
OMDD DIF File
Export Area
Copy
OMDT
Browse Results
15
Object Model Data Dictionary SystemUsage
Statistics

• OMDD usage continues to grow at a steady pace
• From 1 April 1998 through 11 March 1999

• Export area statistics represent a snapshot on
  11 March 1999, not a cumulative count of items
  exported

16
Conclusions

• Use of the OMDD supports the FEDEP
• Supports development of FOMs and SOMs using an
  OMDT through reuse of names, lexicons, data
  representations, and enumerations
• Provides access to standards-based contents for
  the construction of FOMs and SOMs
• Relates simulations to real world systems (OMDDS
  contents are mapped to Defense Data Dictionary
  System)
• Improves the understandability and reusability of
  FOMs and SOMs through the use of common names,
  lexicons, data representations, and enumerations