Download presentation
Presentation is loading. Please wait.
Published byDwight Francis Modified over 9 years ago
1
Curt Garcia10/25/20031 UDEF IDsOAGI BODs 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
2
Curt Garcia10/25/20032 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)
3
Curt Garcia10/25/20033 Aerospace Industry Marketplace All eBusiness communications and transactions take place between two broadly defined entities – Buyers and Sellers
4
Curt Garcia10/25/20034 - 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
5
Curt Garcia10/25/20035 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
6
Curt Garcia10/25/20036 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
7
Curt Garcia10/25/20037 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…
8
Curt Garcia10/25/20038 from the Order… (shown: Electronic Document Access web-based Government Contract)
9
Curt Garcia10/25/20039 …to the Delivery (shown: WAWF web-based Acceptance Document)
10
Curt Garcia10/25/200310 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
11
Curt Garcia10/25/200311 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
12
Curt Garcia10/25/200312
13
Curt Garcia10/25/200313 Open Application Group Integration 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.orghttp://www.openapplications.org
14
Curt Garcia10/25/200314 Here’s how it looks with all the pieces put together…
15
Curt Garcia10/25/200315 Proposed Aerospace Industry Standard eBusiness Architecture AddPurchaseOrder TPP TPA CPP AddRequestForQuote - 2 - Solicitation - 3 - Proposal / Evaluation - 4 - Contract Award - 5 - Contract Performance - 7 - Billing / Payment - 8 - Contract Closure - 6 - Delivery Universal Data Element Framework (UDEF) Naming Convention ListRouting GetWIPStatus GetDelivery ProcessInvoice 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 - 1 - Requirements - 0 - General Information AddRequisition AddQuote GetInvoice
16
Curt Garcia10/25/200316 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.
17
Curt Garcia10/25/200317 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)
18
Curt Garcia10/25/200318 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 DoD Business Management Modernization Program (BMMP)
19
Curt Garcia10/25/200319 Two relevant policies –Unique Item Identification (UID) Policy Memorandum signed 7/29/2003 –XML Registration Policy Memorandum signed 4/22/2002 DoD Business Management Modernization Program (BMMP)
20
Curt Garcia10/25/200320 Unique Item Identification (UID)
21
Curt Garcia10/25/200321 XML Registration
22
Curt Garcia10/25/200322
23
Curt Garcia10/25/200323
24
Curt Garcia10/25/200324
25
Curt Garcia10/25/200325 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
26
Curt Garcia10/25/200326
27
Curt Garcia10/25/200327
28
Curt Garcia10/25/200328 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
29
Curt Garcia10/25/200329 Questions?
Similar presentations
© 2024 SlidePlayer.com. Inc.
All rights reserved.