Transcript XML Working Group

XML Working Group
Joan Ugljesa
NDIA PMSC
April 25, 2007
[email protected]
949-722-7659
Topics





Review background and end objective
Review where we are in the development
process
Current Events
Where to find materials
List of reference URLs
April, 2007
2
Background

What’s the purpose?




April, 2007
Replace the existing (and limiting) 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 an industry recognized 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 schedule, cost, and auxiliary XML data
components (data model and schemas) that can be
used by the project management community
worldwide regardless of industry
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
environment

April, 2007
Consistent, standard approach means you save time and
money
4
Schema Information Areas

Targeted schemas for specific data exchange



Targeted schemas include:





April, 2007
Can be used alone or combined
Flexible – can be tailored to project needs
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
5
UN/CEFACT Development Steps
1.
2.
3.
4.
5.
6.
7.
8.
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
April, 2007
6
Development Plan
UN/CEFACT Project Proposal
Complete – Presented 9/05
UN/CEFACT Business Process Use Cases
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, Updated 12/06
UN/CEFACT Requirements Mapping Specification (data
model)
Complete, Updated 12/06
Harmonization complete 11/06
Draft XML schema for trial use (implementation
verifications)
Draft schemas are available, subject
to change pending candidate
release in June, 2007
Implementation Verifications
Began 3/06, continue through 9/07
Industry Guidelines
Still working on approach
UN/CEFACT Published Schemas (candidate release)
June, 2007
Final published in September, 2007
April, 2007
7
Where We Are/What’s Next

Official schemas produced




In the meantime, have opportunity to complete
implementation verifications prior to the September, 2007
UN/CEFACT meeting




Delay in producing candidate release schema because of
UN/CEFACT changes to base standard (naming and design
rules and other internal procedures)
Best case scenario: available May, 2007
Most likely: June, 2007
Allows us to make minor modifications to the data model as the
schemas are more thoroughly tested
OSD Central Repository will be an integral part of the process
Last step: submit for final ratification at the next biannual
UN/CEFACT meeting (September 2007)
Final schema/data model will be publicly available on the
UN/CEFACT web site

April, 2007
There is no fee or other requirement to be able to access or use
8
Current Events


DCMA Web Design Group is actively working with
NASA Huntsville to use the UN/CEFACT XML
schemas
DCMA is working with OSD on the Central Repository
pilot for contractor reports (CPR/CSDR)


7 ACAT I programs (Boeing, LM, NG, Raytheon)
Have mapped CCDR reporting requirements to UN/CEFACT
data model


UN/CEFACT schemas will be standard means to provide
data to the repository


April, 2007
Minor code adds/modifications required to support
Initial May 15 deadline
DCMA plans to use UN/CEFACT schemas to feed trip wire
reporting
9
Current Events

Working with software vendors to incorporate support
for the data model/schemas

OSD Central Repository activities have created additional
momentum





Dekker
Deltek
Planview (MPM)
Primavera
Still need industry guidelines – may be able to
address as part of the OSD Central Repository
activities

April, 2007
Anticipate availability of commercially available tools that
support the data model and schema that can assist in the
implementation and use
10
Using Web Services and XML to Exchange Data
(DCMA/Boeing Pilot)
Service Partner
(Prime Contractor)
Data
Submission
Application
Prime user prepares data in
application, converts to
UN/CEFACT XML
Service Provider / Customer
(DCMA)
DCMA Web Service
Transfer
XML
Data
Convert
UN/CEFACT XML
for application use
Notify
User
Customer user
(DCMA or agency)
analyzes data in
application of choice
Service Partner
(Supplier)
Prime Web Service
Customer user (prime)
analyzes data in application
of choice
Notify
Prime
User
Convert
UN/CEFACT XML
for application use
Transfer
XML
Data
Data
Submission
Application
Supplier user prepares data
in application, converts to
UN/CEFACT XML
Goal: Eliminate disparate formats and media, create collaborative environment
to improve data flow through the entire supply chain
April, 2007
11
Means to Exchange Data

Transport mechanisms or means to get an XML
instance document from point A to point B

DCMA/Boeing pilot used a web services approach to
exchange the data



Recognize that there is more than one way to exchange files
(path of least resistance)



April, 2007
This is a more advanced transport mechanism that can require
some development effort depending on the normal
mechanisms a company is using to exchange data with
external parties (including legacy EDI transactions)
When fully integrated provides a means to verify the data and
automatically pull data into an application system
E-mail attachment
Post to web site (may require access controls)
May require means to acknowledge receipt and acceptance
or to encrypt the data
12
Where to Find Materials

CORE.gov (Community Organization and
Registration Environment)


Provides collaboration site to support the Federal Enterprise
Architecture and other cross-agency initiatives including
XML.gov
DCMA is government sponsor for posted materials

Chris Hassler - UN/CEFACT Project Editor
 [email protected] (you will need this e-mail address to
register with CORE.gov)
 310-900-6005

April, 2007
Draft schemas for trial use posted here along with
complementary supporting materials (under the DCMA
Community)
13
Other URLs for Reference
CORE.gov
https://collab.core.gov/CommunityBrowser.aspx
Note: will need to register with CORE.gov, then ask to participate in
DCMA Community
XML.gov
xml.gov
xml.gov/cop.asp (community of practice)
UN/CEFACT
www.unece.org/cefact/index.htm
UN/CEFACT TBG6
http://www.cen.eu/uncefactforum/TBG/TBG6/tbg6.htm
Working group history
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
Please note change in contact information: [email protected], 949-722-7659
April, 2007
14