Environmental Data Coding Specification EDCS Product Development Group PDG

1
Environmental Data Coding Specification (EDCS)
Product Development Group (PDG)

• 23 September 2004
• Bob Richbourg
• rrichbou_at_ida.org

2
EDCS PDG

• Day Thursday, 23 September 2004
• Time 130
• Location Biscayne
• Status
• PDG Reference product intended to be available at
  this SIW
• ISO has not yet released the EDCS for public
  review
• Activity Brief review of PDG COA

3
PDG Membership Status

• Technical Area Director Peggy Gravitz
• PDG Officers
• Chair Bob Richbourg, Institute for Defense
  Analyses
• Vice Chair / Secretary Dale Miller,
  Lockheed-Martin Information Systems
• Drafting Group (one established)
• Paul Foley, NGA
• Annette Janett, LMIS
• David Jodeit, ITT
• Dale Miller, LMIS
• Bob Richbourg, IDA
• Virginia Dobey, SAIC / DMSO
• Ron Moore, SAIC
• Membership Open to anyone who subscribes to the
  EDCS PDG reflector

4
ISO/SISO Development Relationships
Product V.1
Product V.2
SISO Products (Reference Guidance)
Product V.n
SISO Product References Adds MS-specific
Elaborations and Implementation Details
to International Standard
SISO PDG
Difference Assessment Revised Product Draft
Proposed Revisions
. . .
SISO PDG
Product Draft V.n1
SISO Proposed Extensions (via TAD to
National Standards bodies)
ISO Draft
International Standard
Draft International Standard (DIS)
Committee Draft (CD)
Working Draft (WD)
Final Committee Draft (FCD)
5
Recommendation Last PDG Meeting

• Provide SISO Reference Products
• Drafting Group produces a final SIW paper when
  EDCS advances to International Standard
• Continue to provide opportunities for comment on
  the EDCS
• Implement a SISO product maintenance mechanism
  (which could be done in cooperation with the
  SEDRIS Organization) to capture necessary
  (expedient) changes to the EDCS which will be
  submitted to the ISO for registration

6
Appropriate Type of SISO Product?

• Reference Products Sources of information that
  provide a passive input to models and
  simulations. May also be an aid to research
• -- Include, e.g., reports prepared by Study
  Groups, Data Dictionaries, Lexicons and the SIW
  Proceedings
• Administrative Products Developed by SISO to
  guide the operations and practices of the
  organization
• -- Examples include the SISO Vision document and
  the SISO Policies and Procedures

7
SISO Products (continued)

• Guidance Products Documents that can control
  the development, integration, and use of common
  reference data in some portion of the Modeling
  and Simulation community
• Guidance Products are similar to Standards in
  that they describe SISO Best and Current
  Practices
• A recommended development process is an example
  of a Guidance Product

8
SISO Products (continued)

• Standards Products Formally approved documents
  that reflect consensus agreements on products,
  practices, or operations, as required, by
  simulation industry applications
• Interoperability with a SISO Standard shall
  require full compliance to document
  specifications
• SISO Standards are stable and well-understood,
  technically competent, have multiple,
  independent, and interoperable implementations
  with substantial operational experience, enjoy
  significant public support, and are recognizably
  useful in some or all parts of the simulation
  community
• An example is the RPR FOM

9
SISO Product Development Process

• 1. Activity Approval (DONE)
• 2. Product Development ( first drafting group
  work is in process)
• 3. Ballot Product (Not required for Reference
  Administrative Products)
• 4. Product Approval (SAC, CC, EXCOM as
  applicable)
• 5. Distribution and Configuration Management
• 6. Periodic Review

10
The Approval Process
Discussion ...
11
Product Development Phase
During this step, the product is developed. This
is typically accomplished by members from the
community who volunteer for the effort. The
volunteers establish a clear understanding of the
product to be developed. In the case of unclear
or ambiguous information, the volunteers contact
the product proponent or the SAC member
designated as the Technical Area Director (TAD)
for the effort to obtain additional information.
The volunteers execute the plan and schedule to
accomplish the product development as established
during the activity approval process.
Modifications must be approved by consensus of
the product development volunteers, the SAC, and
the EXCOM.
12
Making a Product - Initial Efforts
Drafting Group - This group is responsible for
evaluating and evolving a draft product
circulating the product for review responding to
comments by reviewers and responding to the SAC
on scope, schedule, and technical issues. DG
membership normally ranges from 5 - 7. Drafting
group membership is assigned by the SAC.
13
Making a Product - Reviews

• Assigned Reviewers - This group is responsible
  for concentrated review and comment on all
  products, including interim products. There are
  10 - 20 Assigned Reviewers. The members are
  recommended by the Drafting Group and approved by
  the SAC.
• Volunteer Reviewers - This group is responsible
  for overall review of the product. The Volunteer
  Reviewers review any draft of the product and
  provide comments to the Drafting Group.
  Volunteer Reviewer membership is unlimited in
  size and is open to the MS community and all
  interested parties.

14
The Drafting Group Composition

• DG Editor  The Drafting Group Editor is selected
  from the PDG membership by the PDG Chair TAD
• The DG Editor is responsible for developing a
  component based on direction from the PDG
• The DG Editor assigns specific tasks to DG
  members, collects input, and integrates it into
  the component
• The DG Editor reports the efforts of the DG to
  the PDG
• DG Member  A DG Member provides input in the
  development of the draft Product or component.
• The default DG Membership shall be the PDG
  membership. However, this may be unworkable.
  The PDG may develop a narrower definition of DG
  membership, and submit it for SAC approval.