XML Working Group
Joan Ugljesa
NDIA PMSC
May 3, 2006
949-609-2999
[email protected]
Topics





May, 2006
Background
Review development steps and current
plan
Current work product
Current events
List of URLs
2
Background

What’s the purpose?




May, 2006
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
3
What’s 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

May, 2006
Consistent, standard approach means you save
time and money
4
UN/CEFACT Development Steps
1.
2.
3.
4.
5.
6.
7.
8.
May, 2006
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
5
Development Plan
UN/CEFACT Project Proposal
Complete – Presented 9/05
UN/CEFACT Business Process Use Cases
First edition complete –
Presented 9/05
DCMA/Boeing St. Louis Proof of Concept
Initial draft XML schema for trial use
Complete 3/06
UN/CEFACT Business Requirements
Specification
Complete
UN/CEFACT Requirements Mapping Specification
Presented at 3/13-17/06
UN/CEFACT meeting
Draft XML schema for trial use ready for
implementation verifications
Draft schemas available now
Implementation Verifications – Boeing, NG, others
to be determined
Began 3/06
Complete by 9/06
UN/CEFACT Published Schemas
10/06 or 3/07 UN/CEFACT
Meeting
May, 2006
6
Current Work Products

Business Requirements Specification
(BRS) – approved


Requirements Mapping Specification
(RMS) – detail data model, beginning
harmonization process


May, 2006
Report approved status to XML.gov*
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
7
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
May, 2006
8
BRS/RMS - Information Areas

Produce targeted schemas for specific data
exchange purpose


Includes:





May, 2006
Can be used alone or combined
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
9
Current Events

Have conducted in depth reviews of the
Business Requirements Specification and
data model contents with various project
management software vendors* including:






May, 2006
Artemis
Business Engine (MPM)
C/S Solutions
Dekker
Welcom/Deltek
Also provided draft schemas for review and
comment
* Primavera is scheduled for May 11
10
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:



May, 2006
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
11
AIA EEIC Standards Development
“Radar Screen ”
Adopt
existing
standard
Position of
unadopted
blips is
provisional
FIPS
201 TSCP
SAML
EIA-927
PLCS
Certipath
STEP
PKI
Monitor
external
development
GECA
•
X12
Supplier
EDI
Template
• UID
GTPA
Supplier
UID
Adopted
Candidate
Boost
Aero
Track
UDEF
PM/EVM
Clickable
GTPA
May, 2006
AIA Guidelines
IADFA
Template
AIA
development
Active AIA Project
RFID
ebXML
Participate in
external
development
As at 2006-02-27
12
Resources
XML.gov
xml.gov
xml.gov/cop.asp (community of practice)
AIA
www.aia-aerospace.org
UN/CEFACT
www.unece.org/cefact/index.htm
UN/CEFACT TBG6
http://webster.disa.org/cefact-groups/tbg/wg/tbg6_main.cfm
Working group
documents
Available on the DAU web site:
https://acc.dau.mil/ndiaxml
Note: you must be a member of the Earned Value
Community of Practice to access the web site
May, 2006
13