Study Group on Assessment of the Need for Product Data Representation Standards ANPDRS

1
Study Group on Assessment of the Need for Product
Data Representation Standards (ANPDRS)

• 2004 Fall Simulation Interoperability Workshop
• Orlando, FL, USA
• September 23, 2004

Jim Coolahan Study Group Chair
2
ANPDRS Study GroupAgenda for Meeting
onThursday, September 23, 20040830 1200,
Flamingo Room

• 0830-0845 Introduction and welcome
• 0845-0900 Review of Terms of Reference
• 0900-1000 Discussion of summaries of related data
  standards efforts
• 1000-1030 BREAK
• 1030-1130 Discussion of final documentation of
  standards needs assessment
• 1130-1200 Writing assignments for final product
• 1200 Adjourn

3
System Acquisition and Product Development (SAPD)
Forum Motivation for the ANPDRS Study Groupfrom
the Spring 2003 SIW

• Explanation Information and data are a
  significant program cost that acquisition
  programs need to actively manage. Work on product
  data representations and information management
  is advancing in major programs (e.g., JSF). The
  need for coupling MS and information management
  with the systems engineering process is apparent.
• Recommendation The SAPD Forum PRP intends to
  formulate and submit a recommendation for a Study
  Group to Assess the Need for Product Data
  Representation Standards, with a first meeting
  targeted for the 2003 Fall workshop.

4
ANPDRS (Assessment of the Need for Product Data
Representation Standards) Study Group

• Leadership
• Chair Jim Coolahan
• Vice Chair Mike Haas
• Secretary Kim Larsen
• Purpose
• The ANPDRS SG will review existing methods of
  representing product data, identify significant
  gaps in product data representation standards and
  ongoing activities to address these gaps, and, if
  warranted, recommend SISO product group(s) to
  begin formulation of needed standards
• Product
• Final report, to include
• Bibliography of existing product data
  representation standards and methods
• List of, and justification of, areas in which new
  product data representation standards are
  warranted.
• If one or more SISO PDGs are recommended, draft
  Terms of Reference (TOR(s)) for the PDG(s).
• Schedule
• 2004 Spring SIW, Washington, DC interim
  bibliography of standards
• 2004 Fall SIW, Orlando, FL final report

5
ANPDRS Study GroupTypes of Members

• Full members SISO members who are committed to
  producing the Study Groups products, according
  to the schedule in the TOR.
• Jim Coolahan,
• Associate members SISO members who would like
  to express opinions on the topic, but cannot
  devote sufficient time to producing the products.
• Jim Hollenbach, Peter Eirich, Mike Haas, Tim
  Cordner,
• Affiliate members non-SISO members / members of
  other standards-related organizations who would
  like to collaborate with the SG.
• Steve Olson, John Reder,

6
ANPDRS Study GroupAgenda for Meeting
onThursday, September 23, 20040830 1200,
Flamingo Room

• 0830-0845 Introduction and welcome
• 0845-0900 Review of Terms of Reference
• 0900-1000 Discussion of summaries of related data
  standards efforts
• 1000-1030 BREAK
• 1030-1130 Discussion of final documentation of
  standards needs assessment
• 1130-1200 Writing assignments for final product
• 1200 Adjourn

7
ANPDRS (Assessment of the Need for Product Data
Representation Standards) Study Group

• Motivation The data required to represent
  systems and products in MS is broad and diverse,
  describing requirements, conceptual and physical
  design, manufacturing means, cost, system
  performance, and the products operational and
  support environment.
• The ANPDRS SG will
• Identify categories of MS needed for product
  development
• Define the forms of needed product data
  representations
• Identify and review existing methods of
  representing product data, including
• Standards produced by recognized national and
  international standards bodies
• Product data representations in use or in
  development by major US international military
  system acquisition programs, MS organizations
  and U.S. international commercial organizations
• Identify significant gaps in the existence of
  product data representation standards
• Survey ongoing activities by other organizations
  to address such gaps

Performance/Effectiveness Simulation
Product Modeling
HLA
STEP
SEDRIS
XML
8
ANPDRS Study GroupTerms of Reference (1 of 2)
Tasks

• Identify by major category the full range of MS
  applications needed for the development/acquisitio
  n of products.
• Define, in the context of these MS applications,
  the relevant aspects and forms of product data
  representations that might be needed.
• Considering the stated range of MS applications,
  identify and perform a review of existing methods
  of representing product data, including
• Standards produced by recognized national and
  international standards bodies and organizations
  (e.g., ISO, NIST, IEEE, etc.) and
• Product data representations in use or in
  development by
• major US and international military system
  acquisition programs (e.g., Joint Strike Fighter
  (JSF), Future Combat Systems (FCS), DD(X), etc.)
• MS organizations and
• U.S. and international commercial organizations.
• Identify significant gaps in the existence of
  product data representation standards, for which
  having such standards would improve the
  interoperability of system acquisition and
  product development MS applications.
• Survey ongoing activities by other organizations
  to address such gaps.
• If warranted, recommend the establishment of one
  or more SISO Product Development Groups (PDGs) to
  begin formulation of standards within the purview
  of SISO.

9
ANPDRS Study GroupTerms of Reference (2 of 2)
Products

• A bibliography of existing and emergent product
  data representation standards and methods,
  including the standard name, governing
  organization, and area of applicability (draft
  due Spring 2004)
• Final report (due Fall 2004), including
• List of committee membership, committee process,
  and organizations surveyed
• Final bibliography of existing product data
  representation standards and methods and
• List of, and justification of, areas in which new
  product data representation standards are
  warranted.
• If one or more SISO PDGs are recommended, draft
  Terms of Reference (TOR(s)) for the PDG(s).

10
ANPDRS Study GroupAgenda for Meeting
onThursday, September 23, 20040830 1200,
Flamingo Room

• 0830-0845 Introduction and welcome
• 0845-0900 Review of Terms of Reference
• 0900-1000 Discussion of summaries of related data
  standards efforts
• 1000-1030 BREAK
• 1030-1130 Discussion of final documentation of
  standards needs assessment
• 1130-1200 Writing assignments for final product
• 1200 Adjourn

11
Scope of Products to be AddressedWhere did we
draw the line?

• Military hardware systems

• Commercial hardware products (vehicles, )

• Military software systems (C4ISR, )

• Commercial software products (games, )

• Biochemical products (drugs, refined oil, )

• Document products (standards, )

12
Standard
Template for Summaries of Existing Standards

• Description
• ANPDRS Applicability
• Product Development MS Categories Supported
• Responsible Organization
• Date Published
• Current Status
• For More Information

13
Name of Standard

• Short text summary of standard 2-3 sentences.
  What does it apply to? Who uses it?
• Why applicable to ANPDRS 1-2 sentences
• Which category of Product Development MS
  applications does this support? Choose from list
  on next page / levels, applicability on following
  page.
• Responsible org (IEEE, NDIA, etc.)
• Date of standard
• Current status (draft, final, approved, in
  review, any updates pending)
• For more information List POC or URL

14
Categories of Product-Development MS Applications

• Campaign simulations (M)
• Mission simulations (M)
• Engagement simulations (M)
• Engineering simulations (C/M)
• System cost models (M/C)
• Logistics simulations (M)
• Business process models (C)
• Economic models (C)
• Supply chain models (C)
• Natural environment models (C/M)
• Human behavior (C/M)
• Virtual prototypes (C/M)

• CAD tools
• PDM tools
• Manufacturing simulations
• Acquisition cost models (C/M)
• Architecture models

Strawman applicability legend M military C
commercial
15
Level vs Application
See Pascal Cantots slides, previously
distributed, for more information on levels and
application
16
A Way to Categorize Data Representations(from JW
Hollenbach)
17
Tentative List of Standards and Assignments

• XML schema (Tina)
• Metadata standards / registry (Kenn)
• JSF JAMIS metadata development (Roy)
• UML (XMI) (Kim)
• CORBA (Tim J.)
• IDEF (Tina)
• SEDRIS (Peter)
• EDCS (Peter)
• HLA OMT (Jim C.)
• DTED (Kim)
• IEEE/EIA 12207 (Tommy)
• ISO/IEC 15288 (Tommy) (deleted in April 2004
  assessed as not data-related)
• French MOD operational data (Pascal)
• CADM (for DoDAF) (Roy)
• Machine shop data model (Tina)
• Defense standards program (Crash)
• SRML (Jim C.)
• DoDAF (Crash)
• STEP/PDES (Tina)

?
?
?
?
?
?
?
?
18
Standard XML Schema

• Description The purpose of a schema is to define
  and describe a class of XML documents by using
  these constructs to constrain and document the
  meaning, usage and relationships of their
  constituent parts data types, elements and their
  content, attributes and their values, entities
  and their contents and notations. Schema
  constructs may also provide for the specification
  of implicit information such as default values.
  Schemas document their own meaning, usage, and
  function. Thus, the XML schema language can be
  used to define, describe and catalogue XML
  vocabularies for classes of XML documents.
• ANPDRS Applicability Formal specification
  language. Supports data transfer among
  applications.
• Product Development MS Categories Supported
  Potentially across all categories for data
  transfer.
• Responsible Organization World Wide Web
  Consortium (W3C)
• Date Published 1998, and following
• Current Status
• XML Schema Part0, Part1, and Part2, 2001 W3C
  Recommendation
• XML Schema 1.0 Formal Description, 2001 W3C
  working draft.
• The XML Schema Working Group is currently working
  to develop a set of requirements for XML Schema
  1.1, which is intended to be mostly compatible
  with XML Schema 1.0 and to have approximately the
  same scope.
• The Working Group has also done work on the
  post-schema-validation Infoset. There has also
  been work on a formal description of W3C XML
  Schema.
• A number of drafts and working documents are
  available to W3C Members at the Working Group's
  page.
• For More Information C. M. Sperberg-McQueen of
  W3C/XML Schema Working Group. www.w3.org/XML/Schem
  a

19
Standard IDEF (1 of 2)

• Description IDEF is an acronym meaning ICAM
  DEFinition, where ICAM is an acronym for
  Integrated Computer Aided Manufacturing.
  Developed by the US Air Force. IDEF is the common
  name for referring to classes of enterprise
  modeling languages. IDEF is more than just a
  collection of language definitions, it also
  describes a method that goes with a particular
  language. At present, the following IDEF
  languages and methods have been defined.
• IDEF0 Function Modeling Method
• IDEF1 Information Modeling Method
• IDEF1X, IDEF1X97 Data Modeling Method
• IDEF3 Process Description Capture Method
• IDEF4 Objected-Oriented Design Method
• IDEF5 Ontology Description Capture Method
• IDEF0 function modeling is designed to represent
  the decisions, actions and activities of an
  existing or prospective organization or system.
  IDEF0 graphics and accompanying texts are
  presented in an organized and systematic way to
  gain understanding, support analysis, provide
  logic for potential changes, specify requirements
  and support system-level design and integration
  activities.
• IDEF1X97 consists of two conceptual modeling
  languages. The key-style language supports
  data/information modeling and is downward
  compatible with the US government's 1993
  standard, FIPS PUB 184. The identity-style
  language is based on the object model with
  declarative rules and constraints. IDEF1X97
  identity style includes constructs for the
  distinct but related components of object
  abstraction interface, requests, and
  realization utilizes graphics to state the
  interface and defines a declarative, directly
  executable Rule and Constraint Language for
  requests and realizations. IDEF1X97 conceptual
  modeling supports implementation by relational
  databases, extended relational databases, object
  databases, and object programming languages.
  IDEF1X97 is formally defined in terms of first
  order logic. A procedure is given whereby any
  valid IDEF1X97 model can be transformed into an
  equivalent theory in first order logic. That
  procedure is then applied to a meta model of
  IDEF1X97 to define the valid set of IDEF1X97
  models.

20
Standard IDEF (2 of 2)

• ANPDRS Applicability Enterprise modeling
  language and methods.
• Product Development MS Categories Supported
  Business process models, supply chain models,
  architecture models, manufacturing simulations.
• Responsible Organization IEEE, NIST, KBSI
• Date Published 1978, and following
• Current Status
• In December 1993, NIST released IDEFØ as a
  standard for Function Modeling in FIPS
  Publication 183 and IDEF1X as a standard for
  Data Modeling in FIPS Publication 184 (FIPS
  stands for Federal Information Processing
  Standard)
• In 1998, IEEE published
• IEEE Std 1320.1-1998, Standard for Functional
  Modeling Language-Syntax and Semantics for IDEFO.
• IEEE Std 1320.2-1998, Standard for Conceptual
  Modeling Language-Syntax and Semantics for
  IDEF1X97.
• For More Information IEEE Computer
  Society/Software Engineering Standards Committee
  IDEFinfo_at_kbsi.com ieeexplore.ieee.org/Xplore/DynW
  el.jsp www.idef.com

21
Standard HLA Object Model Template

• Description The High Level Architecture (HLA)
  Object Model Template (OMT) provides a means of
  specifying objects, attributes, interactions,
  etc., that are pertinent to the execution of an
  interoperable simulation compliant with the HLA.
• ANPDRS Applicability Applicable to creating
  interoperable simulations
• Product Development MS Categories Supported All
  categories of simulations
• Responsible Organization IEEE (for IEEE 1516)
  DMSO (for 1.3)
• Date Published 2000 (IEEE 1516) 1998 (1.3)
• Current Status IEEE 1516 is active, update
  beginning in 2004 1.3 is in its final form and
  will not be updated
• For More Information Contact IEEE for copy of
  IEEE 1516 see DMSO web site (http//www.dmso.mil)

22
Standard IEEE/EIA 12207

• Description This standard is IEEE/EIA further
  development of the original standard ISO/IEC
  12207 Standard for Information Technology
  Software Life Cycle Processes.
• ANPDRS Applicability Simulations are most of the
  time also software, therefore processes for
  Acquisition, Supply, Development, Operation and
  Maintenance of software should be applicable.
• Product Development MS Categories Supported
• All categories involved in simulation
  development.
• Responsible Organization Institute of Electrical
  and Electronic Engineers, Inc.
• Date Published 1998
• Current Status Final
• For More Information contact IEEE Standards
  Department, 445 Hoes Lane, P.O. Box 1331,
  Piscataway, NJ 08855-1331, USA

23
Standard Machine Shop Data Model

• Description The machine shop data model
  specification, currently under development at
  NIST, is documented using UML and XML. The model
  provides neutral data interfaces for integrating
  machine shop software applications with
  simulation. It describes mechanisms for
  describing data about organizations, calendars,
  work, resources, schedules, parts, process plans,
  and layout within a machine shop environment.
• ANPDRS Applicability Information model, related
  to manufacturing
• Product Development MS Categories Supported CAD
  models, manufacturing simulations
• Responsible Organization NIST
• Date Published Under development since 2002
• Current Status Looking for a standards body
• For More Information Contact Chuck McLean (NIST)

This has evolved into the SISO Core
Manufacturing Simulation Data (CMSD) PDG that
first met on 9/21/04.
24
Standard STEP (ISO 10303) / PDES (1 of 2)

• Description ISO 10303, STEP (STandard for the
  Exchange of Product model data), is an
  international standard for the computer-interpreta
  ble representation and exchange of product data.
  The objective is to provide a mechanism that is
  capable of describing product data throughout the
  life cycle of a product, independent from any
  particular system. ISO 10303 is organized as a
  series of parts, each published separately.
  These parts can be grouped into infrastructure
  components and industry specific information
  models
• Overview and fundamental principles (Part 1)
• Description methods and implementation methods
  (Parts 11-40)
• A library of general purpose information models
  for things like geometry, topology, product
  identification, dates, times, etc. (the 40-series
  parts)
• A library of special purpose information models
  for things like draughting, finite element
  analysis, kinematics, etc. (the 100-series parts)
  
• Industry-specific application protocols that are
  built from the library of general models (the
  200-series parts)
•         Test data and criteria for the
  200-series parts (the 300-series parts)
•         Reusable groups of information resource
  entities (the 500-series parts)
•  
• NOTE PDES (Product Data Exchange using STEP) is
  not a standard. It is the U.S. organizational
  activity that supports the development and
  implementation of the international standard
  STEP. The goal of PDES is to ensure that
  requirements of U.S. industry are incorporated
  into STEP. The PDES effort is primarily a
  voluntary activity coordinated through the
  IGES/PDES Organization (IPO). The IPO works with
  ISO where STEP development is being coordinated
  internationally.
• ANPDRS Applicability Description and
  implementation methods. Common resources and
  application protocols. Directly applicable to
  representing data associated with
  design/development of products.

25
Standard STEP (ISO 10303) / PDES (2 of 2)

• Product Development MS Categories Supported CAD
  tools, PDM tools, manufacturing simulations.
• Responsible Organization ISO/TC184/ SC4
• Date Published 1984, and following
• Current Status

ISO 10303-11994   Edition 1 ISO 10303-111994  
Edition 1 ISO 10303-111994/Cor 11999   Edition
1 ISO/TR 10303-121997   Edition 1 ISO
10303-212002   Edition 1 ISO 10303-221998  
Edition 1 ISO 10303-232000   Edition 1 ISO
10303-242001   Edition 1 ISO/TS 10303-272000  
Edition 1 ISO/TS 10303-282003   Edition 1 ISO
10303-311994   Edition 1 ISO 10303-321998  
Edition 1 ISO 10303-342001   Edition 1 ISO
10303-412000   Edition 2 ISO 10303-411994  
Edition 1 ISO 10303-411994/Cor 11999   Edition
1 ISO 10303-421994   Edition 1 ISO
10303-422003   Edition 3 ISO 10303-421994/Cor
32001   Edition 1 ISO 10303-431994   Edition
1 ISO 10303-432000   Edition 2 ISO
10303-431994/Cor 11999   Edition 1 ISO
10303-431994/Cor 22000   Edition 1 ISO
10303-442000   Edition 2 ISO 10303-441994  
Edition 1 ISO 10303-441994/Cor 11999   Edition
1 ISO 10303-451998   Edition 1 ISO
10303-451998/Cor 11999   Edition 1 ISO
10303-461994   Edition 1 ISO 10303-461994/Cor
11999   Edition 1 ISO 10303-461994/Cor 22002  
Edition 1 ISO 10303-471997   Edition 1
ISO 10303-471997/Cor 12000   Edition 1 ISO
10303-491998   Edition 1 ISO 10303-502002  
Edition 1 ISO 10303-1011994   Edition 1 ISO
10303-1011994/Cor 11999   Edition 1 ISO
10303-1042000   Edition 1 ISO 10303-1051996  
Edition 1 ISO 10303-1051996/Cor 12000   Edition
1 ISO 10303-1051996/Cor 22000   Edition 1 ISO
10303-2011994   Edition 1 ISO 10303-2021996  
Edition 1 ISO 10303-2031994   Edition 1 ISO
10303-2031994/Cor 11996   Edition 1 ISO
10303-2031994/Cor 21998   Edition 1 ISO
10303-2031994/Amd 12000   Edition 1 ISO
10303-2042002   Edition 1 ISO 10303-2071999  
Edition 1 ISO 10303-2071999/Cor 12001   Edition
1 ISO 10303-2092001   Edition 1 ISO
10303-2102001   Edition 1 ISO 10303-2122001  
Edition 1 ISO 10303-2142001   Edition 1 ISO
10303-2162003   Edition 1 ISO 10303-2242001  
Edition 2 ISO 10303-2251999   Edition 1 ISO
10303-2272001   Edition 1 ISO 10303-2322002  
Edition 1 ISO/TS 10303-3042001   Edition
1 ISO/TR 10303-3072000   Edition 1 ISO/TS
10303-3241999   Edition 1 ISO/TS
10303-3322002   Edition 1
ISO/TS 10303-3042001   Edition 1 ISO/TR
10303-3072000   Edition 1 ISO/TS
10303-3241999   Edition 1 ISO/TS
10303-3322002   Edition 1 ISO 10303-5012000  
Edition 1 ISO 10303-5022000   Edition 1 ISO
10303-5032000   Edition 1 ISO 10303-5042000  
Edition 1 ISO 10303-5052000   Edition 1 ISO
10303-5062000   Edition 1 ISO 10303-5072001  
Edition 1 ISO 10303-5082001   Edition 1 ISO
10303-5092001   Edition 1 ISO 10303-5102000  
Edition 1 ISO 10303-5112001   Edition 1 ISO
10303-5121999   Edition 1 ISO 10303-5132000  
Edition 1 ISO 10303-5141999   Edition 1 ISO
10303-5152000   Edition 1 ISO 10303-5172000  
Edition 1 ISO 10303-5172000/Cor 12002   Edition
1 ISO 10303-5182002   Edition 1 ISO
10303-5192000   Edition 1 ISO 10303-5192000/Cor
12000   Edition 1 ISO 10303-5201999   Edition
1 ISO 10303-5212003   Edition 1 ISO/TS
10303-10012001   Edition 1 ISO/TS
10303-10022001   Edition 1 ISO/TS
10303-10032001   Edition 1 ISO/TS
10303-10042001   Edition 1 ISO/TS
10303-10052001   Edition 1 ISO/TS
10303-10062001   Edition 1 ISO/TS
10303-10072001   Edition 1 ISO/TS
10303-10082001   Edition 1 ISO/TS
10303-10092001   Edition 1
26
Standard GEIA-927 Common Data Schema for
Complex Systems

• Description This standard embodies a data model
  that spans the entire lifecycle for complex
  systems as seen from the viewpoints of various
  stakeholder disciplines. It will provide a
  mechanism for the interchange of data between
  heterogeneous tool sets and for managing
  relationships between data elements that exist in
  different discipline domains. The schema will be
  used by individuals at levels ranging from PEO to
  individual analysts.
• ANPDRS Applicability Since the standard deals
  primarily with product data representation, it
  falls squarely in the center of the field of
  interest for ANPDRS.
• Product Development MS Categories Supported
  GEIA-927 will support many, if not all, of the
  Product Development MS applications.
  Repositories based on 927 can provide the
  requisite data to power a wide range of MS
  activities at different levels.
• Responsible Organization Government Electronics
  and Information Technology Association (GEIA)
• Date Published to be published 4Q 2004
• Current Status Committee draft
• For More Information John Reber, 703-691-7772,
  jreber_at_tridsys.com

27
ANPDRS Study GroupAgenda for Meeting
onThursday, September 23, 20040830 1200,
Flamingo Room

• 0830-0845 Introduction and welcome
• 0845-0900 Review of Terms of Reference
• 0900-1000 Discussion of summaries of related data
  standards efforts
• 1000-1030 BREAK
• 1030-1130 Discussion of final documentation of
  standards needs assessment
• 1130-1200 Writing assignments for final product
• 1200 Adjourn

28
ANPDRS Study GroupAgenda for Meeting
onThursday, September 23, 20040830 1200,
Flamingo Room

• 0830-0845 Introduction and welcome
• 0845-0900 Review of Terms of Reference
• 0900-1000 Discussion of summaries of related data
  standards efforts
• 1000-1030 BREAK
• 1030-1130 Discussion of final documentation of
  standards needs assessment
• 1130-1200 Writing assignments for final product
• 1200 Adjourn

29
Standards Needs Assessment Gaps and Rationale

• Manufacturing Simulation Data Standards
• Rationale See rationale for new CMSD PDG
• Campaign/Mission Scenario Data Representations
• Rationale Several efforts need this, including
  OneSAF (MSDL effort), and OPNAV (Navy Common Data
  Base)
• (emerging) Missile (friendly and threat) data
  representations

30
Standards Needs Assessment Recommendations

• Manufacturing Simulation Data Standards
• SISO should support the development of these
  standards through the new Core Manufacturing
  Simulation Data (CMSD) PDG
• Campaign/Mission Scenario Data Representations
• To be complete, this must get support from all
  U.S. Services, and must permit modeling of joint
  and coalition scenarios
• One or two initial separate efforts are underway,
  but may not have critical mass this is a large
  effort, and in a relatively small community of
  interest
• May be a candidate for Joint effort / advocacy
  between SISO and MORS (Military Operations
  Research Society)
• (potential) Missile Data Representations

31
ANPDRS Study GroupAgenda for Meeting
onThursday, September 23, 20040830 1200,
Flamingo Room

• 0830-0845 Introduction and welcome
• 0845-0900 Review of Terms of Reference
• 0900-1000 Discussion of summaries of related data
  standards efforts
• 1000-1030 BREAK
• 1030-1130 Discussion of final documentation of
  standards needs assessment
• 1130-1200 Writing assignments for final product
• 1200 Adjourn

32
Outline for Final Study Group Report
33
Action Item Timeline

• Transmit meeting summary to SISO (Jim C.
  9/27/04)
• Publish meeting results to ANPDRS reflector (Jim
  C. 9/28/04)
• Sections for final report (all writers send to
  Jim C. 10/15/04)
• Publish draft on ANPDRS reflector (Jim C.
  11/1/04)
• Comments due (all send to Jim C. 11/15/04)
• Publish report to SAC (Jim C. 12/1/04)

34
ANPDRS Study GroupAgenda for Meeting
onThursday, September 23, 20040830 1200,
Flamingo Room

• 0830-0845 Introduction and welcome
• 0845-0900 Review of Terms of Reference
• 0900-1000 Discussion of summaries of related data
  standards efforts
• 1000-1030 BREAK
• 1030-1130 Discussion of final documentation of
  standards needs assessment
• 1130-1200 Writing assignments for final product
• 1200 Adjourn