1. Open Applications Group
Lunch and Learn UN/CEFACT Meeting March 16, 2006 OAGIS implementation of Core Components
David Connelly

2. Open Applications Group
Introduction
How the OAGIS standard implemented Core Components
How people are using OAGIS
OAGIS Adoption

3. Open Applications Group
Who we are
The Open Applications Group is a not-for-profit, open, and fully independent Open Standards Organization.

4. OAGi Genesis Founded in November, 1994 Originally by ERP Vendors
Focused on how they can integrate together better
Identified common content as biggest missing piece

5. Original OAGi Scope from 1995T R P I S
A. To Extra-Enterprise
Systems
B. Between ERP Applications
C. To Special Purpose Applications

6. What is OAGIS?

7. OAGIS® is Payloads and Business Processes
Scenario is the process definition
Business Object Documents (BOD) are the messages in the Scenario

8. OAGIS® 9 - Current Version
Released April 5, 2005
Over 10 total years in the field
70 Business Scenarios
434 Messages (BODs)
77 Nouns (Common Objects) defined
12 Verbs Defined
More localization for more International support
UN/CEFACT/ISO compliant
ISO 11179
CCTS 2.01/ISO
TBG17 BIE/ABIE

9. Current Scope of OAGIS® 9.0 Content
eCommerce
e-Catalog
Price Lists
RFQ and Quote
Order Management
Purchasing
Invoice
Payments
Manufacturing
MES
Shop Floor
Plant Data Collection
Engineering
Warehouse Management
Enterprise Asset Mgmt.
Logistics
Orders
Shipments
Routings
CRM
Opportunities
Sales Leads
Customer
Sales Force Automation
ERP
Financials
Human Resources
Credit Management
Sarbanes/Oxley & Control
Value Chain Collaboration Applications
Enterprise Management Applications
Enterprise Execution Applications

10. OAGIS BODs are a Language
Noun
Verb
ProcessPurchaseOrder
BOD
BODs are comprised of
Nouns
Verbs
Nouns contain the business content
Verbs describe the action

11. BOD History BOD and Meta Data Invented XML DTDs Shipped
June 1995
XML DTDs Shipped
February 1998
XML XDR Shipped
December 1999
XML Next Gen XSD Shipped
March 2002
UN/CEFACT CC XML Shipped
May 2005

12. BOD History 5 generations of technology already
Reinforces the importance of syntax neutrality

13. The BOD Architecture
The Business Object Document Basic Architecture. All BODs are comprised of an Application Area and a Data Area.

14. BOD Architecture BOD is technical architecture
Provides a message container
Enables the meta model
Common look, feel, and behavior
Enables a high level of re-use
Enables the extensibility mechanisms
Provides a faster learning curve for the user
OAGIS Open Development Methodology calls for 6 pieces of data when describing the Scenario. These are laid out below. You can show an example in the OAGIS documentation if you start at a scenario # 49 or above.

15. OAGIS Nouns Nouns are consistent like Common Objects 78 in OAGIS 9
Can be Documents
Can be Control Data
Can be any content needed in a message
Behavior is affected by Verbs
Verbs are described in next section
Self explanatory

16. OAGIS Noun Examples PurchaseOrder Invoice Shipment Quote
RequestForQuote
ProductionOrder
MaintenanceOrder
Self explanatory

17. OAGIS Verbs
Noun
Verb
ProcessPurchaseOrder
BOD

18. OAGIS® Verbs? Nouns may need to be different at execution
The Verbs help drive these constraints
Example
SyncPurchaseOrder
CancelPurchaseOrder
OAGIS constrains the Nouns with XPath portion of XSL (Not XSLT portion)
Self Explanatory

19. Verb Example
In many scenarios, the first phase is to synchronize the data before processing transactions. This shows Synchronizing the Item Master and the Inventory Amounts before processing an Available-to-Promise transaction scenario.

20. A Constraint Rule
Rule Context
Test
Message

21. Using Constraints to Add Context
BOD Instance
Application
Validating Parser
BOD XML Schema
XSL Processor
BOD Constraints

22. OAGIS Extensibility
OAGIS® provides the user a unique form of extensibility to stretch the standard without breaking it.
This is the recommended approach to extensibility for OAGIS.

23. Overlay Extensibility
OAGIS® uses three technologies to enable Overlay extensibility
Global Elements
Namespaces
Substitution Groups
This is the recommended approach to extensibility for OAGIS.

24. Overlay Example Overlay OAGIS® Your BOD
This is a fictional picture of how an overlay plugs into OAGIS. The overlay uses all the base functions from the OAGIS library and just adds or changes the parts that are specific to the vertical. This preserves the horizontal backbone (CANONICAL MODEL) and enables excellent fit for vertical industries.

25. Lite BODs for Specific Use Cases
OAGIS® also enables you to “extrude” Lightweight BODs
Canonical stays in place
Extrude from the class libraries
Maintain at the library level
Use lightweight BODs for lightweight services
Lite BODS
OAGIS® CANONICAL BODS

26. OAGIS Components Started with this concept in 1995
OAGIS Building Blocks
Nouns Comprised of Components
Used to “Assemble” the BODs
OAGIS Core Components are the basic building block for OAGIS BODs. OAGi has been building their own since Over 50 per cent of all new BODs are constructed from existing OAGIS Components.

27. OAGIS® Component Example
This is an XML Code example of the Amount Compound.

28. PO BOD Assembled using Components
Header
Terms
Contact
Party
Charge
Distribution
Diagram Note:
- Required = Solid boxes
- Optional = Dashed boxes
Line
POSubLine
POLineSchedule
Address
PO BOD Assembled using Components
This usually gives the audience a very good idea of an overall BOD from a structure perspective. Each box is a component that is used to assemble the BOD. You can note that the dotted lines on the multiple boxes denote more than one occurrence and also when occurrences are optional or required. The solid lines denote required component instances.

29. OAGIS Architecture
Resources
Meta Model
Content

30. BOD Assembly Example

31. Open Applications Group
                                     
Open Applications Group
OAGIS® 9 Implementation of UN/CEFACT Core Components

32. Early OAGi UN/CEFACT Efforts
Involved with ebXML Since inception in November 1999
Participated in most of meetings
Focused on Business Process and Core Components
Part of ebXML Proof of Concept in Vienna
OAGIS Contribution to CC in 2001

33. UN/CEFACT Endorsement

34. UN/CEFACT Standards Implemented in OAGIS® 9

35. UN/CEFACT Standards Implemented in OAGIS® 9
Conformance to UN/CEFACT ATG2 Naming and Design Rules.
Where we deviate it is to meet the functional needs of OAGIS and OAGi member requirements.
ISO – CCTS 2.01
UN/CEFACT TBG17 – ACCs and BIE/ABIEs as defined to this point.

36. Why did OAGIS implement CC?
Business Decision
Technical Decision

37. Why did OAGIS implement CC?
OAGIS® Users asked for it
Automotive Supply Chain
Aerospace Supply Chain
Defense Industry
Two largest software vendors have adopted it
SAP
Oracle
OAGIS® convergence initiatives
ISA SP95
HR-XML
UN/CEFACT

38. Why did OAGIS implement CC?
Will increase interoperability for enterprises
Encourages all business languages to be based on same concepts.
Defines grammar rules
Defines key naming conventions
Defines key common content (Components)

39. Why did OAGIS implement CC?
The right thing to do
OAGIS® participation in MoU MG asks for it
Good citizen in standards world

40. Building Bridges

41. UN/CEFACT Standards implemented in OAGIS 9
Strategy
All TBG17 Approved ACCs (as of 02/05) available
Subset of TBG17 Approved ACCs implemented in Components.xsd
Most stable ACCs identified for implementation
ACCs also evaluated for compatibility with OAGIS design rules
19 ABIEs in OAGIS 9
Based on 18 TBG17 Approved ACCs

42. UN/CEFACT Standards implemented in OAGIS 9
ABIEs Implemented Included
Project
AllowanceCharge
Calculation
Tax
Authorization
Payment Authorization
Term
Person
Status
Dimension
HazardousMaterial
Location
Communication
Preference
Contact
TimePeriod
TemperatureRange
CurrencyExchange
Price

43. OAGIS Component Libraries
UN/CEFACT
IST/ISO

44. OAGIS UN/CC Implementation Let’s Go Look

45. OAGi Participation in UN/CEFACT
TMG – Techniques and Methodology Group
CCTS: Core Component Technical Specification
BCSS: Business Collaboration Schema Specification
CCMA: Core Component Message Assembly
TBG – International Trade and Business Process Group
TBG17: Core Component Harmonization
ATG – Applied Technologies Group
ATG2: XML Naming and Design Rules Technical Specification

46. Garret Minakawa, Oracle Corporation
Special Thanks
Initiated the move for OAGi to adopt the UN/CEFACT Core Components efforts.
Created the OAGi CC Workgroup, leading it to ensure that OAGIS is compliant with UN/CEFACT.
Initiated the role and represents OAGi on UN/CEFACT TBG17.
Worked with UBL and UN/CEFACT ATG2 to establish a common set of schema modules for CCTS; the basis for building Core Components.
Initiated the task and became OAGi ISO TC 154 Liaison.  This is the E-Commerce Group at ISO.
Garret Minakawa, Oracle Corporation

47. Standards within the OAGIS® Standard
W3C - URI/URL W3C - XML Schema 1.0 Part 1 W3C - XSL Schema 1.0 Part 2.0 W3C - XML Style Language W3C - XML Path Language (XPath) Version 1.0 ISO - ISO11179
ISO - ISO Core Components Type Specification ISO - ISO20022 (UNIFI Financial Standard) ISO - ISO Currency Codes ISO - ISO639 - Language Codes UN/CEFACT ATG2 Naming and Design Rules - NDR UN/CEFACT Harmonized Core Components – TBG17 MIME Media Type Code UNECE Unit Code OMG UML 2.0

48. Open Applications Group
Questions?

49. Knowledge of OAGIS® Adoption
Difficult to know full adoption number
OAGIS® is free and the download only requires a registration
We learn from
Word of mouth s
Surveys
Luck
We count downloads
We track s
Probably know 10% of user base
The world is responding and has overwhelmingly shown this through their use of OAGIS and XML.
We have over 8000 unique names on our mailing list. And these have not come just from North America.

50. OAGIS Downloads 100,000+ downloads over last 8 years
Representing over 60 countries
The world is responding and has overwhelmingly shown this through their use of OAGIS and XML.
We have over 8000 unique names on our mailing list. And these have not come just from North America.

51. Drivers for OAGIS® Implementations
B2B beyond traditional EDI
Supply Chain Management
Supply Chain Visibility
Collaborative Engineering and Manufacturing
Increasing demand to connect internal processes to external processes
Service Oriented Architecture
Requires Business Service Definitions
Emerging understanding of the benefit of a Canonical ModelTM

52. The Business Environment
Integration Back Bone
Business Unit n
Supplier
Customer
Business Unit 1
Business Unit 2
Enterprise
This is a VERY important slide. It depicts the business environment where an organization may decide to address the integration problem by selecting a single vendor for all business applications. This is no longer enough. This is because no single organization can control their customers and suppliers technical environments .
And what about when the organization does acquisitions or divestitures. Therefore the organization needs to plan for “plugging in” suppliers, customers, and internal divisions quickly, as cheaply as possible, and with as little disruption as possible.
This environment makes a compelling case for everything the rest of this class covers. This is “WHY OAGIS”.

53. A Case for a Canonical Model
From <many to many> to <many to one>
Many companies have a “spaghetti” diagram. We have several different drawings all depicting the same issue. . The left side of this is one version. The right side of this slide depicts a single language approach, not a middleware solution.

54. The mathematics of scaling up
For traditional point to point or <many to many> integration:
The number of possible connections
among any number of items is n(n-1)
for two way connections.
Number of
components
to integrate
Cost of traditional
0.1 FTE
Apply traditional
formula
2 FTEs
9 FTEs
21 FTEs
38 FTEs
n = 5 5(4) = 20
n = (9) = 90
n = (14) = 210
n = (19) = 380
This shows the math of the cost of doing things how we tend to do them today. Show how this point to point model scales very high very fast. The currency valuations refer to a fully loaded person with salary, overhead, benefits, etc. Average is 100K. Could be more, could be less, but the number is a good basis to show cost.

55. The mathematics of scaling up
For best practices integration:
The number of possible connections among any number is n * 2.0
Number of
components
to integrate
Best practices
formula
Cost of best practices
0.1 FTE
n = * 2.0 = 10
n = * 2.0 = 20
n = * 2.0 = 30
n = * 2.0 = 40
1 FTE
2 FTEs
3 FTEs
4 FTEs
This shows the math of the cost of doing things how we could be doing them. Show how this model scales flat and scales slowly. The currency valuations refer to a fully loaded person with salary, overhead, benefits, etc. Average is 100K. Could be more, could be less, but the number is a good basis to show cost.
Make the point that this is the goal and it usually needs to be done by drawing a line in the and and starting all new work towards this model as we are NOT recommending people rip out their stuff that is working today. This model works for B2B and A2A.

56. Sample of Customers using the OAGIS Canonical Model
TeliaSonera
SKF
Amersham Health
Goodrich Aerospace
Goodyear Tire
Cisco
IBM
Boeing
Ford
General Electric
Lucent

57. Industry Collaborations
UN/CEFACT – United Nations
ISO- International Standards Organization
MoU MG – Memorandum of Understanding Management Group
IEC TC57 WG14 – Electric Utility Standards
KIEC – Korean e-Commerce Consortium
NIST – National Institute of Standards & Technology
AIAG – Auto Supply Chain North America
Odette – Auto in Europe
ITA – Information Technology in Germany
STAR – Auto Retail North America
AAIA – Auto Aftermarket North America
RV Industry – North America
AIA – Aerospace North America
AECMA – Aerospace Europe
OSCRE – Facilities Management
VISION Industry
HR-XML – HR Content, world-wide
SP95 – Enterprise Controls
ARTS (Retail)
STEP – Engineering world-wide
IFX – Interactive Financial Exchange
SWIFT
TWIST
Comptia/EIDX – Electronics and Computer Industry
WS-I
OASIS
Tax-XML
UBL

58. OAGIS live users in 41 known countries
Australia
Austria
Bahrain
Belgium
Brazil
Canada
Chile
China
Croatia
Czech Republic
Denmark
Ireland
Finland
France
Germany
Holland
Hungary
India
Israel
Italy
Japan
Korea (South)
Lithuania
Mexico
Netherlands (Holland)
Norway
Oman
Papua New Guinea
Poland
Russia
Saudi Arabia
Singapore
Slovenia
Slovakia
South Africa
Spain
Sweden
Switzerland
Turkey
United Arab Emirates
United Kingdom
United States

59. OAGIS live users in over 40 industries
Aerospace
Agri-Business
Automotive Manufacturing
Automotive Retail
Automotive Aftermarket
Banking
Brewing
CPG
Chemical
Computer Hardware
Computer Software
Consumer Goods – Electronics
Defense
Distributors
Federal Government
Food Manufacturing
Furniture Manufacturing
Medical Device Manufacturing
Mortgage
Pharmaceutical
Insurance
Industrial Goods Manufacturing
Logistics
Medical Device Manufacturing
Mining
Oil
Natural Gas
Paint
Paper
Publishing
Retail
Shipping
Software
State Government
Local Government
Telecommunications
Tire Manufacturing
Tobacco
Trucking
Universities
Electric Utilities
NOTE: This list is not complete. We need to update it before publishing as Final. (02/10/2003)

60. Some eGovernment Implementations
Dutch Ministry of Finance
UK Ministry of Defense for Logistics
UK Post (Mail)
UK Network Rail
KIEC (Korea)
Dubai eGovt
Govt. of Oman
USAF
US DLA

61. Some Automotive Adoption
General Motors
Ford Motor Company
Volvo
Volkswagon
Toyota
Honda
Nissan
Covisint

62. Some Hi-Tech and Telecom Adoption
Microsoft
IBM
Cisco
Texas Instruments
Motorola
Qualcomm
Intuit
Lucent
Slovak Telecom
TeliaSonera
British Telecom
MCI
Verizon

63. Some Retail Adoption Staples Best Buy Microage Nordstrom Lowes
Coles-Meyers Australia
Saks
Home Depot
Woolworths Australia
Canadian Tire

64. Some General Manufacturing Adoption
Ingersol Rand (Ireland)
General Electric
SKF (Sweden)
Black and Decker
Campbells Soup (Australia)
British and American Tobacco
Siemans
Johnson and Johnson
Engelhard
Cargill
Emerson
AAC Comos (Netherlands)
Agilent

65. Some Aerospace Adoption
Boeing
Lockheed Martin
Northrop Grumman
Goodrich Aerospace

66. Some Services Adoption
Disney
Ameriquest
The Hartford
Standard and Poors
ADP
Salt River Project (Electricity)

67. Some OAGIS Vendor Adoption
Oracle
SAP (partial)
IBM
ExpiditeBiz
Microsoft
iBASEt
iConnect
Covisint (Compuware)
HK Systems
Catalyst
Brooks Software
Camstar
Compiere
Tibco
Scala
QAD
iWay
webMethods
Websphere
Camstar
Kaba Benzing
Wonderware
Baan
WiPro
EDS

68. End User Example

69. Lucent and OAGIS®
OAGIS®

70. Lucent and OAGIS®

71. US DOD

72. Community of OAGIS® Users Group

73. Campbells and OAGIS® From: paul_xxxxxxxxx@arnotts.com
Sent: Wednesday, June 04, :41 PM
To: Dave Chambless
Cc: David Connelly;
Subject: RE: Campbell Soup and the Open Applications Group
Hello Dave,
Thanks for the invitation to join OAG. At Campbells Asia Pacific (I am
based in Sydney, Australia) we have already adopted OAGIS as our message
content schema (canonical form) in our EAI projects. We are a Tibco shop,
and leverage the toolset for both B2B and A2A integrations. We reviewed
ebXML for the initial B2B integration with a 3PL that was our first EAI
project, but since the particular trading partner in question did not have
a messaging framework in place enabling the infrastructure level
interoperability, we leveraged the default Tibco framework (tibXML) as the
most appropriate alternative because it is simpler to implement and to
deploy and was sufficient for the 3PL integration.
The principle we've adopted is that all messages hitting the Tibco message
"bus" will be mapped into a standard "canonical" XML content schema - OAGIS
- to ensure future reuse of any data published on the bus.
We found OAGIS supported most of the B2B transactions we needed for 3PL . . .

74. UK Ministry of Defense

75. Dubai eGovt.

76. SKF and OAGIS® From: xxxxx.xxxxxxx@skf.com
Sent: Thursday, July 29, :20 AM
To:
Subject: An XML question
Dear Sir,
Good afternoon!
I am trying to learn as much as I can about XML.
The company I work for have chosen OAGIS 8 as the XML standard.
I am not an IT programmer - I am a 'user'
Please could you just help me to understand the basic differences difference between XML and EDIFACT ?
Thank you very much in advance
Kind regards, Chris
Chris McCulloch
SKF Logistics Services
AB SKF Gothenburg//Sweden
(Tel: ) (

77. Thanks and Questions?