1 / 10

XML Working Group

This working group aims to migrate schedule and cost standards to an XML format, meeting government contract requirements and facilitating data exchange between entities. Current efforts involve collaboration with industry associations for schema development. Future plans include creating deliverables conforming to development standards. The end goal is a library of XML components in an industry standard, enhancing data exchange neutrality and establishing a formal standard. The approach aligns with OMB Circular A-119's encouragement of voluntary consensus standards.

dunnk
Download Presentation

XML Working Group

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. XML Working Group Joan Ugljesa NDIA PMSCAugust 24, 2004 949-609-2999jugljesa@aim-pmcs.com

  2. Background • What’s the purpose of the working group? • Migrate the essence of the schedule and cost ANSI X12 transaction sets (806, 839) and UN/EDIFACT messages (PROTAP, PROCST) to an XML schema format • Intent is to: • Address formal government contract requirements • Facilitate data exchange between other related entities such as a prime and their subs

  3. What’s Happened So Far • PMSC meeting August, 2003 • Work group formed • PMSC meeting January, 2004 • Motion made and carried to take the formal standards path • Initiated contacts to determine best path forward

  4. What’s Happened So Far PMSC meeting April, 2004 • Reported on 2 possible paths: ANSI X12 and UN/CEFACT • Both in process of finalizing basic components needed to define standards-based schemas • Long development time frame • OSD PA&E provided point of contact with the Aerospace Industries Association (AIA) to further investigate their XML activities • AIA Electronic Enterprise Integration Committee • Dept. of Interior contact • xml.gov Emerging Technology Group is interested in development work/progress

  5. Current Plan • Actively pursuing best path forward • ebXML framework with OASIS and UN/CEFACT core components • Plus the Open Applications Group (OAGi) schema development rules • Complements AIA XML efforts • Working with OAGi to develop schemas for DoD purchase orders and contracting

  6. ebXML • ebXML is built on XML and other Internet standards to create an infrastructure for information and process based electronic business • Is open and free to anyone with interest • Based on process models encoded in XML • Supports any type of data • Provides framework and core components • Gaining momentum fast – merging many XML, Internet, and ISO standards efforts • Recognized by ISO

  7. About OAGi • Not for profit industry consortium • Standards development organization • Uses ebXML core components • Broad set of schemas are widely used nationally and internationally (9 year history) • Endorsed by and affiliated with other industry associations (AIA, European aerospace industry) • UN/CEFACT approved XML syntax payload • Practical, well proven, fast track approach to developing royalty free schemas • Good fit for project management data!

  8. What’s Next • Initial background materials provided for OAGi August working group meeting • May create a new working group or join existing one • Currently working membership issues and details • Must create a series of deliverables that conform to development approach and complete approval process • Once work begins, fast track approach means we can complete development within 5 to 8 months (typical development time) • Will incorporate latest updates to the CPR and IMS DIDs

  9. What’s the End Benefit? • A library of XML cost and schedule components defined in a broadly used industry standard • Software vendor neutral format • Established a formal standard that can be cited in contracts and requirements much like the ANSI X12 EDI transaction sets or the EIA/ANSI 748 EVMS standard • Follows OMB Circular A-119 which encourages agency use of voluntary consensus standards

  10. Resources

More Related