XML Working Group

1
XML Working Group

• Joan Ugljesa
• NDIA PMSCMay 3, 2006

949-609-2999jugljesa_at_aimcorp.biz
2
Topics

• Background
• Review development steps and current plan
• Current work product
• Current events
• List of URLs

3
Background

• Whats the purpose?
• Replace the existing ANSI X12 Electronic Data
  Interchange (EDI) transaction sets (806 and 839)
  with an XML equivalent
• Provide means to exchange schedule, cost, and
  related auxiliary data in a standard format
• Address formal government contractual
  requirements
• Facilitate data exchange for all parties
  subcontractors, prime contractors, customers,
  program offices, internal management

4
Whats the End Objective?

• A library of XML schedule, cost, and auxiliary
  data components (XML schemas) that can be used by
  the project management community
• Formal, published international standard (ISO,
  UN/CEFACT) that can be cited in contracts and
  requirements
• Software vendor neutral format
• Prevent new projects from reinventing the wheel
  use standards based XML components in a web
  services environment
• Consistent, standard approach means you save time
  and money

5
UN/CEFACT Development Steps

• Project definition
• Use Case Description (participants, process)
• Use case as UML model (basis for data model), UML
  activity diagram (sequence of events)
• Business Requirements Specification with high
  level data models
• Requirements Mapping Specification (detailed data
  description)
• Add any missing core components (ISO standard)
• Harmonization
• Schemas generated based on CEFACT design rules

- Complete - In UN/CEFACT review process
6
Development Plan
7
Current Work Products

• Business Requirements Specification (BRS)
  approved
• Report approved status to XML.gov
• Requirements Mapping Specification (RMS) detail
  data model, beginning harmonization process
• Initial review May interim meeting
• Subsequent review August interim meeting

Purpose of XML.gov is to support the directives
in the E-Government Act of 2002, means the
schemas will eventually be part of their federal
database of registered components
8
BRS - Business Process

• The Participants
• Customers
• Government Agency
• Contractor
• Internal Management
• Data Sources
• Supplier
• Contractor
• Government Agency Program Office

Types of data exchange interactive, data
subsets, and complete set
9
BRS/RMS - Information Areas

• Produce targeted schemas for specific data
  exchange purpose
• Can be used alone or combined
• Includes
• Schedule data activities, milestones,
  relationship details, resource assignment details
• Cost data - Budget, actual, earned value,
  estimate (cumulative/at complete or time phased)
• Contract and project summary data
• Funding data
• Auxiliary data reporting structures, calendars,
  resources, thresholds

10
Current Events

• Have conducted in depth reviews of the Business
  Requirements Specification and data model
  contents with various project management software
  vendors including
• Artemis
• Business Engine (MPM)
• C/S Solutions
• Dekker
• Welcom/Deltek
• Also provided draft schemas for review and comment

Primavera is scheduled for May 11
11
Current Events

• AIA eBusiness Steering Group (eBSG)
• Monitoring progress of standards development,
  proof of concept activities
• Offering assistance with adoption and
  implementation
• Normal process for this group
• Identify standards that the industry can use
• Recommend adoption
• Provide guidelines or recommendations on use

NDIA PMSC has the opportunity to assist in the
development of these guidelines
12
AIA EEIC Standards Development Radar Screen
FIPS 201
Active AIA Project
EIA-927
TSCP
Adopt existing standard
SAML
AIA Guidelines
IADFA

• Supplier
• UID

PLCS
Certipath
Monitor external development
Position of unadopted blips is provisional
STEP

PKI
X12 EDI
GECA Template
GTPA Template
RFID
Supplier UID
UDEF
ebXML
PM/EVM
Adopted
Clickable GTPA
Participate in external development
AIA development
Candidate
Boost Aero
Track
As at 2006-02-27
13
Resources