Base Object Model

1
Base Object Model (BOM) Study Group
SAC Status Report Monday, Sept 18, 2000
2
BOM SG Involvement

• Contacts
• Paul Gustavson (SG Chair), pgustav_at_dv.synetics.co
  m
• John Hancock, jhancock_at_artistech.com
• Graham Shanks (CC POC), GrahamShanks_at_compuserve.co
  m
• Michael O'Connor (SAC POC)michael.oconnor_at_itt.com
  
• Others
• Chris Stapleton (IST)
• Bob Lutz (JHU APL)
• Judy Schandua (CACI)
• Steve Goss (Synetics)

3
Recap -Why a Study Group?
SISO focuses on facilitating simulation
interoperabilityand component reuse across the
DoD, other government, and non-government
applications - SISO Web Site
4
Recap - Why a Study Group?
The BOM methodology promotessimulation
interoperabilitythrough component reuse and
has the potential of expediting Federation
Development
worthy of further study
5
BOM - Conceptual Goals

• Encourages Reuse of Simulation Components
• Reduces FOM construction time and effort
• Provides greater FOM flexibility
• Promotes FEDEP automation
• meta-data matching
• incremental/iterative development
• collaboration
• Makes simulation interoperability easier for
• DoD
• Other government
• Non-government applications

2001 SISO Inc Goals - Start At Least Standard
Development Outside our Normal Constituency
6
BOM SG TOR Issues To Investigate

• Study Definition.
• Determine level of BOM interest in the SISO
  community.
• Suggest any unique means of acquiring,
  qualifying, maintaining, and distributing BOMs.
• Investigate salient characteristics and unique
  qualities required to describe BOMs (ie.
  meta-data)
• Investigate BOMs capability to satisfy and/or
  augment elements of the FEDEP.
• Explore the various types of BOMs that might be
  used.
• Develop an estimate of resources required to
  support the standardization of a typical BOM
  Reference FOM.
• If additional sponsorship (funding) or sufficient
  volunteers are available, build a prototype BOM
  set.

7
BOM SG Schedule

• March 2000 -
• Initial BOM SG Kick Off at Spring 2000 SIW
• March 2000 - March 2001 -
• SG to meet (via teleconference) bi-monthly
• build/test BOM set
• April 2000 -
• Call For Papers
• September 2000 -
• Interim BOM SG Meeting at Fall 2000 SIW
• Report Status to SAC
• March 2001 -
• Complete SG report
• Present SG Report at Spring 2001 SIW

• GOALS
• Commmunity participation / SG involvement
• Determine the level of BOM interest to the SISO
  community
• Discuss how BOMs might be employed to satisfy
  SISO goals, methods, and mechanisms.
• Capture the thoughts, opinions and insights of
  the best and the brightest.

8
BOM SG Schedule

• March 2000 -
• Initial BOM SG Kick Off at Spring 2000 SIW
• March 2000 - March 2001 -
• SG to meet (via teleconference) monthly
• build/test BOM set
• April 2000 -
• Call For Papers
• September 2000 -
• Interim BOM SG Meeting at Fall 2000 SIW
• Report Status to SAC
• March 2001 -
• Complete SG report
• Present SG Report at Spring 2001 SIW

• ACCOMPLISHMENTS
• BOM Background Tutorial
• Reviewed BOM SG TOR
• Discussion Panel
• Interest in EncapsulatingBehavior
• Interest in other arenas / communities
• 52 Attendees
• 10 SG Team Interest

9
BOM SG Schedule

• March 2000 -
• Initial BOM SG Kick Off at Spring 2000 SIW
• March 2000 - March 2001 -
• SG to meet (via teleconference) monthly
• build/test BOM set
• April 2000 -
• Call For Papers
• September 2000 -
• Interim BOM SG Meeting at Fall 2000 SIW
• Report Status to SAC
• March 2001 -
• Complete SG report
• Present SG Report at Spring 2001 SIW

• DISCUSSIONS
• Benefits BOMS provide
• Community interest in BOMs
• 1516 (OMT) Support
• How extensible?
• Behavioral BOMs
• Design Patterns
• Repositories
• SISO Product(s)?
• Standard
• Guidance
• Reference Products (PDG)

3x
10
BOM SG Schedule

• March 2000 -
• Initial BOM SG Kick Off at Spring 2000 SIW
• March 2000 - March 2001 -
• SG to meet (via teleconference) monthly
• build/test BOM set
• April 2000 -
• Call For Papers
• September 2000 -
• Interim BOM SG Meeting at Fall 2000 SIW
• Report Status to SAC
• March 2001 -
• Complete SG report
• Present SG Report at Spring 2001 SIW

• RESULTS
• BOMs Go Beyond HLA
• Two Definitions
• HLA BOM
• Simulation Interoperability BOM
• Two BOM Categories
• Interface BOM
• Encapsulated BOM
• How To Build A BOM
• Ways To Use BOMs

3x
11
BOM SG Schedule

• March 2000 -
• Initial BOM SG Kick Off at Spring 2000 SIW
• March 2000 - March 2001 -
• SG to meet (via teleconference) monthly
• build/test BOM set
• April 2000 -
• Call For Papers
• September 2000 -
• Interim BOM SG Meeting at Fall 2000 SIW
• Report Status to SAC
• March 2001 -
• Complete SG report
• Present SG Report at Spring 2001 SIW

• Not Done
• Strawman Methodology Specification Guidance on
  How To Build / Use
• Build/Test BOMsSeeking Appropriate Project
• Allocate Responsibilities
• Gain More Involvement

3x
12
(No Transcript)
13
BOM SG Schedule

• March 2000 -
• Initial BOM SG Kick Off at Spring 2000 SIW
• March 2000 - March 2001 -
• SG to meet (via teleconference) monthly
• build/test BOM set
• April 2000 -
• Call For Papers
• September 2000 -
• Interim BOM SG Meeting at Fall 2000 SIW
• Report Status to SAC
• March 2001 -
• Complete SG report
• Present SG Report at Spring 2001 SIW

• PAPERS RECEIVED
• 00F-SIW-013
• 00F-SIW-019
• 00F-SIW-045
• 00F-SIW-083
• 00F-SIW-102
• 00F-SIW-121

3x
14
BOM SG Schedule

• March 2000 -
• Initial BOM SG Kick Off at Spring 2000 SIW
• March 2000 - March 2001 -
• SG to meet (via teleconference) monthly
• build/test BOM set
• April 2000 -
• Call For Papers
• September 2000 -
• Interim BOM SG Meeting at Fall 2000 SIW
• Report Status to SAC
• March 2001 -
• Complete SG report
• Present SG Report at Spring 2001 SIW

• PAPERS RECEIVED
• 00F-SIW-013
• 00F-SIW-019
• 00F-SIW-045
• 00F-SIW-083
• 00F-SIW-102
• 00F-SIW-121

3x
15
BOM SG Schedule

• March 2000 -
• Initial BOM SG Kick Off at Spring 2000 SIW
• March 2000 - March 2001 -
• SG to meet (via teleconference) monthly
• build/test BOM set
• April 2000 -
• Call For Papers
• September 2000 -
• Interim BOM SG Meeting at Fall 2000 SIW
• Report Status to SAC
• March 2001 -
• Complete SG report
• Present SG Report at Spring 2001 SIW

• AGENDA
• 1830 - Welcome
• 1835 - State of BOM SG
• 1900 - Paper Summaries
• (019,013, 121)
• 1930 - Discussion Panel
• Concepts/Questions from Papers
• Potental BOM Users
• Entertainment Update
• 1516 / XML Update
• 2030 - Wrap-Up

3x
16
BOM SG Schedule

• March 2000 -
• Initial BOM SG Kick Off at Spring 2000 SIW
• March 2000 - March 2001 -
• SG to meet (via teleconference) monthly
• build/test BOM set
• April 2000 -
• Call For Papers
• September 2000 -
• Interim BOM SG Meeting at Fall 2000 SIW
• Report Status to SAC
• March 2001 -
• Complete SG report
• Present SG Report at Spring 2001 SIW

• What Now?
• Keep Pushing it!
• Call for Papers
• Reflector / Message Board?
• Telecons
• Seek BOM Development Opportunities / Funding
• Extend BOMSG Life to Fall 2001
• Interim Meeting in March
• Methodology Document
• SISO BOM Standardization

3x
17
BOM SG Objectives

• Explore the potential of BOMs
• Investigate technical and operational issues
  (e.g. How difficult is it to create and use a
  BOM?)
• Develop case for SISO BOM standardization and
  policy (ie. Products)
• Recommended Practice - BOM Methodology
• Reference Products - BOM Components/Packages

For the purpose of facilitating simulation
interoperability through component reuse
18
Base Object Model (BOM) Study Group
Open Meeting Wednesday, September 20, 2000 630
PM 830 PM Biscayne Room

• Come and Be a Part of the Group thats Creating a
  New Methodology for Simulation Component Reuse
• Take a Fresh Look at Federation Object Model
  Construction!
• Enable Rapid and Efficient FOM Development.
• Support and Promote Simulation Component Reuse.
• Streamline Simulation Interoperability.

19
BOM Origination

• FEDEP
• Describes FOM Reuse
• Recommends Reuse of FOM Piece-Parts
• SISO RFOM Study - S98
• Uncovered Formalized BOMs
• BOM SIW Papers
• 98F-SIW-034
• 99S-SIW-115
• 99S-SIW-185

20
What is a BOM?
HLA BOMs -A single aspect of federation
interplaythat can be used as a building block of
FOMs and SOMs SISO Reference FOM Study Group
- Spring 98
Simulation Enterprise BOMs - A single aspect of
simulation interplaythat can be used as a
building block in the construction of
Interoperable Environments SISO BOM Study
Group - Fall 2000

• The Basic Idea
• a BOM is a single set of Object Model data, and
  provides a distinct way to represent individual
  simulation interaction components components
  that can be used to build or modify a federation.
• The Basic Premise
• the design and development of interoperable
  environments should begin with the exploration
  of reusing available simulation object model
  components