Base Object Model BOM Product Development Group

1
Base Object Model (BOM)Product Development Group

• PDG Officers
• Paul Gustavson Acting Interim Chair
• Larry Root Proposed Chair
• Bob Lutz Proposed Vice-Chair
• Jane Bachman Proposed Secretary
• PDG Editors
• Paul Gustavson Proposed DG Lead Editor
• Steve Reichenthal
• Steve Goss
• Jean-Louis Igarza ?
• John Hancock ?
• PDG Team Member(s) (Provide a list of
  individuals that are currently or may/should/will
  be involved in the development of this product)
• in addition to the names identified above
• Chris Rouget (SAC TAD)
• Chris Turrell
• Phil Zimmerman
• Chris Stapleton
• Mark McAuliffe
• Katherine Morse

2
Product Type and Description

• Product Type (Standard, Guidance, Reference,
  Administrative)
• Standard Product providing a specification for
  Base Object Models (BOMs)
• Product Description (Provide a brief bullet
  point description of the product and components
  as necessary)
• BOMs are specifically identified in the FEDEP as
  a potential facilitator for providing reusable
  object model components used for rapid
  construction/modification of simulations and
  simulations spaces.
• open standardization of BOMs is essential for
  establishing a technology capability that
  facilitates
• interoperability,
• reusability and
• composability. 
• a standardized product defining the format and
  syntax specification, based on XML, will be
  defined for describing the basic elements of a
  BOM.
• additional XML standards (i.e. Schemas) currently
  available will be identified and applied to
  support the various BOM dimensions and BOM
  ontology.
• composition of individual BOMs for defining a
  simulation or simulation environment produces a
  Mega-BOM. 
• A Mega-BOM carries with it the meta-data
  associated to BOMs plus the dependency and
  interrelationships between BOMs.
• BOM specification should include methodology for
  establishing Mega-BOM based on RAD software
  component philosophy  
• Guidance for transformation a Mega-BOM to a FOM
  (for HLA backward compatibility) to be included

3
Community Description and Need

• MS Community (Describe the MS Community that
  will use and benefit from this product)
• Intended for the distributed simulation community
  including but not limited to those that use the
  HLA
• Operational Viewpoint
• BOMs are anticipated to support military and
  commercial markets in the area of
  experimentation, analysis, training (i.e.
  advanced distance learning), and acquisition
• Communities include defense, education, medical,
  manufacturing and entertainment.
• Technical Viewpoint
• useful to simulation developers who need to
  rapidly compose interoperable simulations and
  simulation environments.
• anticipated that an outcrop of simulation
  component developers will emerge offering
  third-party BOM components for usage and
  distribution.
• Supportive BOM tools and collaborative web
  services are expected to emerge
• Community Need (Provide brief bullet point
  details and discussions for the need in the
  community.)
• Need initially identified within the FEDEP and
  OMT documentation describing need for piece
  parts in composing FOMs and SOMs.
• Reference FOM Study Group recognized the need for
  component-like approach for FOM/SOM development
  (1998).
• Recently, operational community has shown greater
  interest in a component-like approach for
  supporting simulation interoperability activities
• DMSO (Composable MS Workshop summer 2002)
• eXtensible Modeling and Simulation Workshop
  (XMSF)

To allow maximum utility and flexibility,
modeling and simulation environments will be
constructed from affordable, reusable components
interoperating through an open systems
architecture. DMSO Perspective (Vision),
September 2002, Phil Zimmerman
4
Maturity, Schedule and Activities

• Product Maturity (Provide brief bullet points
  on the maturity of the product.)
• BOM concept born within the Reference FOM study
  group in 1998
• BOM SG formed following RFROM SG (finished Spring
  2001)
• Produced Final Report
• Produced BOM Methodology Strawman (BMS)
• BOM SG products and subsequent White Papers are
  basis for standard being proposed
• Other Work being leveraged
• OMT 1516
• Simulation Reference Markup Language (SRML)
• Various XML Standards / Approaches (to support
  various BOM Dimensions)
• Lessons learned / approaches from software
  component world (ActiveX, JavaBeans, VCL/CLX)
• Others MDA, XMSF, XMI, NCES
• Schedule (Major Milestones Provide brief
  schedule of product development milestones.)
• Spring 2003 SIW Formal Kick-off for PDG /
  Drafting Group
• Summer 2003 DG Face-to-Face (location/date TBD)
• Fall 2003 SIW Initial BOM strawman
• Spring 2003 SIW - Community Feedback (CFPs)
• Fall 2004 SIW Push for Community Balloting
• Reviewed Annually for 5 years