SISO Standards Activity Committee RPR FOM Status Report Fall 2001 Simulation Interoperability Worksh

1
SISO Standards Activity CommitteeRPR FOM Status
ReportFall 2001Simulation Interoperability
WorkshopRichard SchafferRPR FOM PDG Chair

• September 10, 2001
• 0900-0920
• Biscayne Room
• Orlando, Florida

2
Overview

• Whats the RPR FOM?
• RPR FOM 1.0
• RPR FOM 2.0
• History
• Plans
• RPR FOM Activities at this Workshop

3
What is the RPR FOM?

• A Reference FOM for the Real-time, Platform-level
  simulation community
• Goals
• Facilitate transition of DIS implementations to
  the HLA
• Maintain interoperability among DIS simulations
  once they are transitioned

Guiding Principle Provide an intelligent
translation of DIS to a Reference FOM. Dont try
to improve DIS beyond what come naturally from
the use of HLA features. RPR 1.0 IEEE1278.1
-1995 Functionality RPR 2.0 IEEE1278.1a -1998
Functionality RPR 3.0 Anticipated DIS 3.0
functionality
4
Whats a Reference FOM?

• Defined by the SISO Reference FOM Study Group
• Chartered by SAC / CC at Fall 97 SIW
• Report released at Spring 98 SIW Available at
• http//www.sisostds.org/doclib/doclib.cfm?SISO_CID
  _15
• Identified 5 Categories
• Template
• Common Foundation
• Key features
• Complete FOM including associated meta data.
• Provides a fundamental level of interoperability.
• Supported by multiple communities.
• Extensible.
• Example RPR FOM
• Procurement
• Base OM
• Hierarchical OM

5
Components of the RPR FOM

• The FOM
• HLA 1.3 OMT format
• Maintained in Aegis OMDT
• Distribution includes PDF, OMT DIF, .omd, .fed,
  and Word revision history
• The Guidance, Rationale, and Interoperability
  Modalities for the RPR FOM
• Microsoft Word and PDF files

6
IEEE 1278.1-1995 Functions

• Entity information/interaction
• Entity State
• Collision
• Warfare
• Fire
• Detonation
• Distributed Emission Regeneration
• Electromagnetic Emission
• Designator
• Radio Communications
• Transmitter
• Signal
• Receiver

• Logistics
• Service Request
• Resupply Offer
• Resupply Received
• Resupply Cancel
• Repair Complete
• Repair Response
• Simulation Management
• Start/Resume
• Stop/Freeze
• Acknowledge
• Action Request
• Action Response
• Set Data
• etc.

7
RPR FOM 1.0 Structure

• Like any FOM, the RPR FOM includes the following
  tables
• Object Class Structure
• Interaction Class Structure
• Attribute
• Parameter
• Enumerated Datatype
• Complex Datatype
• Routing Space - not specified
• Lexicon (Object Class, Interaction, Attribute,
  and Parameter Definitions)

8
Purpose of the GRIM

• Adds a set of usage rules above and beyond those
  specified in the Object Model Template.
• Mapping between RPR FOM and DIS.
• Increased support for default fields.
• Guidance and rational needed for extensibility.
• Create meaningful rules for "compliance" and
  "compatibility.
• These terms have no meaning without a set of
  testable shall rules.
• Of course, as a reference FOM, users are free to
  change theses practices to meet their own
  development needs.
• However, deviations may not have a-priori
  interoperability with other systems based on the
  RPR FOM.

9
Contents of the GRIM

• General FOM Guidance and Rational
• RPR FOM Class Structure
• Provides mapping from RPR FOM back to DIS
• Guidance, rational, and modalities provided in
  text.
• RPR FOM Interaction Structure
• Similar in format to Class Structure sections.
• Breaks down Interactions into Families for ease
  of description.
• Mapping from DIS to the RPR FOM
• Needed to support transition of legacy DIS
  systems to HLA

10
What Should the FOM Object Class Structure Look
Like?
Entity

• Example 1 JPSD

Platform
Munition
Land
Air
AntiArmor
BattlefieldSupport
ATACMS
Guided
Tank
AFV
...
...
BAT P3I
M1
T72
T54
Example 2 STOW
Entity
Transmitter
...
11
Object Class Structure
Attributeless class to support DM filtering on
the equivalent of the DIS Entity Type's "domain"
field
To fully support this form of DM filtering,
federates shall publish all objects at the leaf
nodes of the RPR FOM. If a RPR FOM leaf node is
subclassed, then the federate may publish objects
at the newly created leaf nodes. A leaf node is
defined as the lowest level available in the
object class hierarchy table (no subclasses). In
contrast, class subscription should be used at
the highest level (farthest from the leaf nodes)
that supports all of the attributes and DM
filtering required by the receiving federate.
12
Whats a SISO Product Development Group?

• Chartered by the SISO Standards Activity
  Committee (SAC) in response to a Standards
  Nomination
• Three major components
• Drafting Group (DG)
• Assigned Reviewers (AR)
• Volunteer Reviewers (VR)
• Overseen by a Technical Area Director (TAD)

13
Key Elements of Standard Nomination

• Problem/Issue Achieve DIS level of a priori
  interoperability
• Approach Common Foundation RFOM as a SISO
  Standard
• Versions
• Version 1 IEEE 1278.1-1995 functionality
• Version 2 IEEE1278.1a-1998 functionality
• Version 3 DIS 3.0 functionality
• Prototypes
• UK MoD program
• UCF Gateway
• Commercial vendor (MaK Technologies)
• SISO Impact RPR FOM depends on the HLA and must
  be coordinated.
• Community Discussion History
• Origin at 14th DIS workshop
• Meetings at all SIW workshops, interim meetings,
  TCs, reflector
• Candidate Members
• Conference Forums

6/98 - EXCOM approves RPR FOM Standards Nomination
14
Two Stage RPR FOM 1.0 Balloting Process
Process specified in Standards Development
Handbook for SISO Standards, section 4.8.
15
PDG History

• RPR FOM 1.0 Kickoff Meeting - 7/22-23/98
• RPR FOM 0.4 0.5 Released - 8/4
• RPR FOM 0.6 Released - 10/14
• Final Change Requests for RPR FOM 0.7 - 10/29
• Final ARs for Balloting approved by SAC - 11/20
• AR Balloting begins - 11/25
• RPR FOM GRIM Ballot closes - 12/23/98
• Comment Resolution Meeting - 1/78/99
• RPR FOM 0.8beta GRIM 0.8v1 drafts released -
  3/10/99
• Invitation to join Community Ballot Group issued
  - 4/2/99
• Invitation to join Ballot Group closes - 5/4/99
• RPR and GRIM 0.9 released to Community Balloting
  - 5/14/99
• Community Balloting begins - 5/19/99

16
Ballot Group Membership

• 73 Members
• Balanced e-mail domains
• 34 .com
• 28 .mil .gov
• 7 .edu
• 4 other
• Non-US
• Australia
• Germany
• Italy
• Scotland

• Individual institutions
• U.S. Military - 17
• Army - 8
• Air Force - 6
• Navy - 3
• Large Contractors - 17
• SAIC - 5
• Boeing - 4
• Lockheed Martin - 4
• Raytheon - 4

17
RPR FOM 1.0
Passed Community Balloting
75 response, with 75 of responders affirmative
required

• Standards numbering scheme
• GRIM is the Standard SISO-STD-001-1999
  Guidance, Rationale, and Interoperability
  Modalities for the Real-time Platform Reference
  Federation Object Model, Version 1.0
• FOM supports the GRIM SISO-STD-001.1-1999
  Real-time Platform Reference Federation Object
  Model
• Identification SISO-ADM-001-1999 SISO Product
  Identification Summary

18
RPR FOM 1.0

• Official publication announced by SAC EXCOM on
  11/19/99 via SISO-ADMIN
• http//www.sisostds.org/doclib/cat_display.cfm?id_
  number49
• Available on SISO web page
• http//www.sisostds.org/doclib/doclib.cfm?SISO_CID
  _59

19
RPR 2.0 Status Overview

• What is RPR FOM 2.0?
• Adds IEEE 1278.1a-1998 functionality to RPR FOM
  1.0
• Updates to IEEE 1516 IF Spec
• Updates to IEEE 1516 OMT if tools widely
  available
• History
• Previous FOM and GRIM versions
• Key Events at Spring workshop
• Update Key events since Spring Workshop
• Now Sessions at this workshop
• Next Assigned reviewer ballot

20
IEEE 1278.1a-1998 Functions (1 of 2)

• Entity information/interaction
• Collision-Elastic
• Entity State Update
• Distributed Emission Regeneration
• Underwater Acoustic
• IFF/ATC/NAVAIDS
• Supplemental Emission/Entity State
• Radio Communications
• Intercom Signal
• Intercom Control

• Entity Management
• Aggregate State
• IsGroupOf
• Transfer Control Request
• IsPartOf
• Minefield
• Minefield State
• Minefield Query
• Minefield Data
• Minefield Response NACK
• Non-Real Time Protocol

21
IEEE 1278.1a-1998 Functions (2 of 2)

• Synthetic Environment
• Environmental Process
• Gridded Data
• Point Object State
• Linear Object State
• Areal Object State
• Live Entity
• TSPI
• Appearance
• Articulated Parts
• LE Fire
• LE Detonation

• Simulation Management with Reliability
• Start/Resume-R
• Stop/Freeze-R
• Acknowledge-R
• Action Request-R
• Action Response-R
• Data Query-R
• Set Data-R
• Data-R
• Event Report-R
• Comment-R
• etc.

22
Previous RPR FOM 2.0 drafts

• Draft 1 3/22/99
• Extracted from pre-RPR 1.0 drafts
• Aggregate Entity
• Environmental Process
• Draft 2 10/22/99, added drafts of
• IFF (object classes but no attributes)
• Underwater Acoustics
• Gridded Data

23
Previous RPR FOM 2.0 drafts

• Draft 3 1/26/00, added drafts of
• Synthetic Environment (Point, Linear Areal)
• Collision-Elastic
• Intercom
• Minefield PDUs
• Supplemental Emission/Entity State
• Draft 4 2/11/00
• Incorporates most actions from 1/00 meeting
• Includes 32 Change blocks

24
Previous RPR FOM Drafts

• Draft 5 12/22/00
• Completes action items from 1/00 and 2/00
  meetings
• Adds support for
• SIMAN with Reliability
• IsPartOf (as attribute)
• SIMAN Record PDUs
• IFF Layer 2, etc.
• Responsibility of GRIM
• Live Entity PDUs
• Is Group Of
• Transfer Control

• Draft 6 3/22/01
• Incorporates the 10 change requests approved in
  January, 2001 teleconferences
• Outstanding actions
• Review Update Enumerations
• Review Update Lexicon
• Drop orphan protocols (Intercom Point, Linear,
  and Areal Synthetic Environment)
• 8 Changes Requests to be resolved

25
Previous GRIM Drafts

• GRIM v.1 for RPR FOM 2.0D4
• Nearly complete coverage of RPR FOM 2.0 draft 4
  except
• IFF
• Intercom
• Supplemental Emission/Entity State
• Non-real time
• Needs revision history and other formalizations
• New section Procedures (Transfer of Control)

26
Key Developments at Spring SIW

• Reviewed RPR FOM 2.0 draft 6
• Processed 8 FOM Change Requests
• Orphan Protocol redeemed Point / Linear / Areal
• 1516 OMT Tiger Team Report
• 1516 Transition Strategy
• Make draft 7 1516 buffer compatible
• PDG Officer changes
• Graham Shanks retires as FOM Editor, becomes
  assistant Editor
• Michael OConnor becomes FOM Editor, after
  serving as assistant
• Adam Faier becomes assistant FOM editor
• Sean Reilly retires as GRIM Editor
• Jeff Fischer become GRIM Editor, after serving as
  assistant
• Ron Bertin joins Bob Case as assistant GRIM Editor

27
Challenges in converting RPR FOM to IEEE 1516 OMT

• Top-level arrays without length fields Array
  Length fields that do not immediately precede the
  array data.
• Array Length fields that are not 32 bits
  integers.
• Variant Record discriminant fields that do not
  immediately precede their alternatives.
• Length fields will be added when converting the
  any type and the string type to the XML
  predefined types HLAASCIIstring and
  HLAopaqueData.

28
Transition Strategy Details

• Three options debated in Spring
• 1 Maintain RPR FOM 1.0 compatability as long as
  possible then convert to 1516 format.
• 2 Convert v2d6 to 1516 format then store result
  in 1.3 OMT format as v2d7.
• 3 Convert to 1516 but maintain 1.0 compatible
  (much work and may not be viable).
• Unanimous decision 2 Reformat RRP FOM 2.0 draft
  7 so that the 1516 and 1.3 versions marshall data
  compatibly. This breaks compatibility with RPR
  FOM 1.0.

29
Key events since Spring SIW

• 4/6/01 Final RPR FOM 2.0 Change Request Deadline
• 4/17/01 TC to resolve FOM Change Requests
• Addressed 10 CRs -- 2 tabled for next TC
• 4/24/01 Follow-up Change Request TC
• CR 21 Transfer of Control
• CR 25 Lexicon changes
• 5/1/01 RPR FOM 2.0 Draft 7 released
• 5/14/01 GRIM for RPR FOM 2.0 draft 7 released
• 5/21/01 AR Ballot Release TC - Small changes
  identified -- voted to AR ballot with updated docs

30
Key events since Spring SIW (cont)

• 5/22/01 RPR FOM 2.0 Draft 8 released
• 5/23/01 Editor identifies holes in four
  Interactions in Section 7 (Intercom, Synthetic
  Environment, SIMAN-R, Minefield)
• 5/29/01 GRIM 2.0 Draft 8 v.1 released
• 5/30/01 - RPR FOM 1.0 PDG awarded 2001 NTSA MS
  Award in the Cross Function Category - 8 PDG
  attendees
• 9/9/01 GRIM 2.0 Draft 8 v.2 released (SIMAN-R and
  Intercom need work)

31
RPR FOM Virtual Forum

• Goals
• Support for 1.0
• Provide virtual forum to discuss use and
  extensions
• Support for 2.0
• Lessons learned from use of 1.0, other FOMs, etc.
• Seed concepts for 3.0
• Hot Topics this Fall
• Hard Real Time Simulation and RPR FOM 3.0
• Use of SEDRIS EDCS in RPR FOM 3.0

32
Virtual Forum Agenda
Tonight! (September 10) in Sanibel

• 1900 Introduction Welcome Richard Schaffer
• 1910 RPR FOM 2.0 PDG Update Michael OConnor/Jeff
  Fischer
• 1925 01F-SIW-093 - Hard Real-Time Simulation
  Using HLA Thom McLean
• 1945 Paper Discussion
• 1955 PANEL DISCUSSION RPR FOM 3.0, EBV, and
  EDCS Paul Foley / Annette Janett /Michael
  OConnor/ Jeff Fischer

33
Product Development Group Working Session

• Tuesday, 9/11, 900am - 500pm in Pelican (in the
  Tower)
• Agenda
• Key Item Complete GRIM for AR Ballot release.
• Final Review of GRIM
• Assigned Reviewer schedule

34
PDG Leads

• Technical Area Director David McKeeby
• Chair Richard Schaffer
• Secretary Douglas Wood

• FOM Team
• Editor Michael OConnor
• Adam Faier
• Graham Shanks

Standards (GRIM) Team Editor Jeff Fischer Bob
Case Ron Bertin
35
9 RPR FOM 2.0 Assigned Reviewers

• Jeff Fischer (AMEWAS), FOM only
• Len Granowetter (MaK)
• Reed Little (CMU SEI)
• Steve Monson (Boeing)
• Dr Peter Ryan (DSTO)
• Steven Sheasby (Raytheon)
• Grant Tudor (Adacel)
• Chris Turrell (ABTechnologies)
• Doug Wood (MaK)

36
We need your Participation!

• Join the PDG!
• Help complete GRIM 2.0 on Tuesday!
• Become aVolunteer reviewer in the Assigned
  Reviewer Ballot!
• Become a balloter for the Community ballot!

37
How to contact us

• Web Page http//www.sisostds.org/stdsdev/rpr-fom/
  index.htm
• Minutes of meetings TCs, Standards Nomination
• RPR FOM 1.0 standard RPR FOM 2.0 drafts
• Submit or view Change Requests
• Reflector
• SISO-RPR_at_itcenter.org -- Sign up on SISO Web site

38
Questions
39
The End