Date post: | 03-Jan-2016 |
Category: |
Documents |
Upload: | dwight-francis |
View: | 227 times |
Download: | 2 times |
10/25/20031Curt Garcia
UDEF IDsUDEF IDs and OAGI BODsOAGI 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
10/25/20032Curt Garcia
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)
10/25/20033Curt Garcia
Aerospace Industry Marketplace
All eBusiness communications and transactions take place between two broadly defined entities –
Buyers and Sellers
10/25/20034Curt Garcia
- 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
10/25/20035Curt Garcia
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
10/25/20036Curt Garcia
Contract Phases 0 – General Information1 – Requirements2 – Solicitation3 – Proposal/Evaluation 4 – Contract Award5 – Contract Performance6 – Delivery7 – Invoicing/Payment8 – Contract Closure
10/25/20037Curt Garcia
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…
10/25/20038Curt Garcia
from the Order… (shown: Electronic Document Access web-based Government Contract)
10/25/200310Curt Garcia
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/25/200311Curt Garcia
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
10/25/200313Curt Garcia
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
10/25/200315Curt Garcia
Proposed Aerospace Industry Standard eBusiness Architecture
Add
Pur
chas
eOrd
er
TP
PT
PA
CP
P
Add
Req
ues
tFor
Qu
ote
- 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
List
Rou
ting
Get
WIP
Sta
tus
Get
Del
iver
y
Pro
cess
Invo
ice
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
Add
Req
uis
ition
Add
Quo
te
Get
Invo
ice
10/25/200316Curt Garcia
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.
10/25/200317Curt Garcia
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)
10/25/200318Curt Garcia
• 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)
10/25/200319Curt Garcia
• 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)
10/25/200325Curt Garcia
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
10/25/200328Curt Garcia
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