1 / 29

UDEF IDs and OAGI BODs as elements of an Aerospace Industry Standard eBusiness Architecture

UDEF IDs and OAGI BODs as elements of an Aerospace Industry Standard eBusiness Architecture. A business scenario using Universal Data Element Framework IDs and Open Applications Group, Inc. Business Object Documents. Presentation Objective.

roz
Download Presentation

UDEF IDs and OAGI BODs as elements of an Aerospace Industry Standard eBusiness Architecture

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. UDEF IDsandOAGI BODsas elements of an Aerospace Industry Standard eBusiness Architecture A business scenario using Universal Data Element Framework IDs and Open Applications Group, Inc. Business Object Documents 1

  2. Presentation Objective • To create a small pilot effort to model an end-to-end procurement making use of advanced technologies (data transfer via XML transactions) • This model procurement would utilize Universal Data Element Framework (UDEF) IDs and Open Applications Group, Inc. Business Object Documents (BODs) 2

  3. Aerospace Industry Marketplace All eBusiness communications and transactions take place between two broadly defined entities – Buyers and Sellers 3

  4. - Contracts - • Most Buyers and Sellers exchange goods and services for money via mutually binding contracts • In fact, many companies in the Aerospace Industry are known as Defense Contractors • Contracts may be known as Orders, Purchase Orders, Purchase Agreements, or other terms, but all the terms reference a common semantic meaning 4

  5. Contract Life Cycle • The life cycle of a contract may be represented by a series of hierarchical, sequential processes divided into 9 phases • General Information (to establish identity); and • 8 Sequential Contract Process Steps 5

  6. Contract Phases 0 – General Information 1 – Requirements 2 – Solicitation 3 – Proposal/Evaluation 4 – Contract Award 5 – Contract Performance 6 – Delivery 7 – Invoicing/Payment 8 – Contract Closure 6

  7. Universal Data Element Framework (UDEF) IDs • UDEF IDs will provide a common data dictionary for most business data • Example: Requisition Number, Part Number, Contract Number, Shipment Number, etc. • Contract Data – UDEF IDs will provide consistent data labels throughout the entire procurement process… 7

  8. from the Order… (shown: Electronic Document Access web-based Government Contract) 8

  9. …to the Delivery(shown: WAWF web-based Acceptance Document) 9

  10. Different Names for the Same Data • In the preceding Form Based examples, the data required is known by different names • DD1155 Order for Supplies or Services • Block 1 is “Contract/Purchase Order No.” • DD250 Material Inspection & Receiving Report • Block 1 is “Proc. Instrument Iden. (Contract)” • Information contained in both “fields” • SP045103M4427 10

  11. The UDEF ID Solution • UDEF IDs are comprised of an Object and a Property divided by an underscore • The UDEF ID for Contract Number is “e.2_12.8” which is • Object: Contract Document • Property: Alphanumeric Identifier 11

  12. 12

  13. Open Application GroupIntegration Specification (OAGIS) 8.1 • OAGIS 8.1 contains Business Object Documents (BODs) that include Verbs (e.g. Get, List, Process) and Nouns (Purchase Order, Invoice, etc.) • It also contains XML Schema, constraint XSL, and example XML documents • “Content Focused” (from OAGI presentation) • “ebXML is the envelope / OAGIS is the letter” • Learn more at http://www.openapplications.org 13

  14. Here’s how it looks with all the pieces put together… 14

  15. Proposed Aerospace Industry Standard eBusiness Architecture Universal Data Element Framework (UDEF) Naming Convention - 3 - Proposal / Evaluation - 4 - Contract Award - 7 - Billing / Payment - 8 - Contract Closure - 0 - General Information - 2 - Solicitation - 5 - Contract Performance - 6 - Delivery - 1 - Requirements TPP TPA CPP ListRouting GetDelivery AddQuote GetInvoice GetWIPStatus ProcessInvoice AddRequisition AddPurchaseOrder AddRequestForQuote OAGIS 8.1 Business Object Documents (BODs) based on ebXML standard UDEF – Use the same name for the same data element (e.g. Contract Number) across the entire Contract Life Cycle OAG BODs – Use established XML schema and documents (and extend where necessary) to achieve rapid e-commerce capability 15

  16. DoD Business Management Modernization Program (BMMP) • In July, 2001, the Secretary of Defense established the Business Management Modernization Program (BMMP) to transform and modernize the Department of Defense (DoD) business and Financial Systems • This initiative has been designated as one of the top ten reform priorities for the Department • The above comments are from the BMMP Transition Plan dated 6 June 2003. 16

  17. DoD Business Management Modernization Program (BMMP) • Seven BMMP Domains • Acquisition (ACQ) • Finance, Accounting Operations & Financial Mgmt (ACC/FIN) • Human Resources Management (HRM) • Installations & Environment (I&E) • Logistics (LOG) • Strategic Planning & Budgeting (SPB) • Technical Infrastructure (TI) 17

  18. DoD Business Management Modernization Program (BMMP) • Relevant Domains for this presentation and their designated Owners • Acquisition (ACQ) • Ms. Deidre Lee • Finance, Acctg Ops & Financial Mgmt (ACC/FIN) • Ms. JoAnn Boutelle • Logistics (LOG) • Ms. Diane Morales • Technical Infrastructure (TI) • Ms. Priscilla Guthrie 18

  19. DoD Business Management Modernization Program (BMMP) • Two relevant policies • Unique Item Identification (UID) • Policy Memorandum signed 7/29/2003 • XML Registration • Policy Memorandum signed 4/22/2002 19

  20. Unique Item Identification (UID) 20

  21. XML Registration 21

  22. 22

  23. 23

  24. 24

  25. Remember the Paper Forms • The first thing required to become “paperless” is to start out “paperful.” • Gather information from the legacy forms-based processes • Roughly speaking, the UDEF IDs represent the blocks on the forms and OAGIS 8.1 BODs represent the entire form as well as its exchange with another party 25

  26. 26

  27. 27

  28. Recommended “Next Steps” • Create small pilot effort to model end-to-end procurement of small spare supply unit (e.g. cable assembly) • Work with appropriate BMMP Domains to inventory all forms and processes currently in use to transfer data • Create and register UDEF IDs for all the necessary blocks • Make sure not to create redundant UDEF IDs for different form blocks which have the same semantic meaning (e.g. “PIIN” vs. “Purchase Order No.”) • Work with OAGI to create necessary extensions to existing Business Object Documents 28

  29. Questions? 29

More Related