Embed Size (px)
Citation preview
April, 2007 2
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 3
Background What’s the purpose?
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
April, 2007 4
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 Consistent, standard approach means you save time and
money
April, 2007 5
Schema Information Areas Targeted schemas for specific data exchange
Can be used alone or combined Flexible – can be tailored to project needs
Targeted schemas include: 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
April, 2007 6
UN/CEFACT Development Steps1. Project definition*2. Use Case Description (participants, process)* 3. Use case as UML model (basis for data model), UML activity
diagram (sequence of events)*4. Business Requirements Specification with high level data
models*5. Requirements Mapping Specification (detailed data
description)*6. Add any missing core components (ISO standard)*7. Harmonization*8. Schemas generated based on CEFACT design rules
* - Complete
April, 2007 7
Development PlanUN/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
Complete, Updated 12/06
Harmonization complete 11/06UN/CEFACT Requirements Mapping Specification (data model)
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 8
Where We Are/What’s Next Official schemas produced
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
In the meantime, have opportunity to complete implementation verifications prior to the September, 2007 UN/CEFACT meeting 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 There is no fee or other requirement to be able to access or use
April, 2007 9
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 Minor code adds/modifications required to support
UN/CEFACT schemas will be standard means to provide data to the repository
Initial May 15 deadline DCMA plans to use UN/CEFACT schemas to feed trip wire
reporting
April, 2007 10
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 Anticipate availability of commercially available tools that
support the data model and schema that can assist in the implementation and use
April, 2007 11
ConvertUN/CEFACT XMLfor application use
TransferXMLData
NotifyPrimeUser
Using Web Services and XML to Exchange Data (DCMA/Boeing Pilot)
Service Provider / Customer(DCMA)
Service Partner (Supplier)
Service Partner (Prime Contractor)
Prime user prepares data in application, converts to
UN/CEFACT XML
Supplier user prepares data in application, converts to
UN/CEFACT XML
Customer user (DCMA or agency) analyzes data in
application of choice
Customer user (prime) analyzes data in application
of choice
DataSubmissionApplication
DataSubmissionApplication
Prime Web Service
ConvertUN/CEFACT XMLfor application use
TransferXMLData
NotifyUser
DCMA Web Service
Goal: Eliminate disparate formats and media, create collaborative environmentto improve data flow through the entire supply chain
April, 2007 12
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 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
Recognize that there is more than one way to exchange files (path of least resistance)
E-mail attachment Post to web site (may require access controls)
May require means to acknowledge receipt and acceptance or to encrypt the data
April, 2007 13
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 Draft schemas for trial use posted here along with
complementary supporting materials (under the DCMA Community)
April, 2007 14
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.govxml.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
