OAGI Briefing - UN/CEFACT Forum

Download Report

Transcript OAGI Briefing - UN/CEFACT Forum

Open Applications Group

Lunch and Learn UN/CEFACT Meeting March 16, 2006 OAGIS implementation of Core Components David Connelly

http://www.openapplications.org

Open Applications Group

Who we are

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 Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved

Original OAGi Scope from 1995

E N T E R P R I S E 5

A. To Extra-Enterprise Systems B. Between ERP Applications C. To Special Purpose Applications

What is OAGIS?

OAGIS

is Payloads and Business Processes

• Scenario is the process definition • Business Object Documents (BOD) are the messages in the Scenario CustomerParty SupplierParty ProcessPurchaseOrder AcknowledgePurchaseOrder ShowDeliveryReceipt ProcessInvoice ConfirmBOD Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved

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 15000-5 – TBG17 BIE/ABIE Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved

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 – Manufacturing – Credit Management – Sarbanes/Oxley & Control Value Chain Collaboration Applications Enterprise Management Applications Enterprise Execution Applications Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved

OAGIS BODs are a Language

• • • BODs are comprised of - Nouns - Verbs Nouns contain the business content Verbs describe the action

Verb BOD ProcessPurchaseOrder Noun 10

BOD History

• • • • • BOD and Meta Data Invented – 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 Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved

BOD History

The BOD Architecture

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 Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved

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 Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved

OAGIS Noun Examples

OAGIS Verbs

BOD ProcessPurchaseOrder Verb Noun

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) Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved

Verb Example

CustomerParty SupplierParty ProcessPurchaseOrder AcknowledgePurchaseOrder ShowShipment ShowDeliveryReceipt ProcessInvoice ConfirmBOD Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved

Rule Context

A Constraint Rule

21 BOD Instance

Using Constraints to Add Context

Application

BOD XML Schema BOD Constraints

OAGIS Extensibility

• OAGIS ® provides the user a unique form of extensibility to stretch the standard without breaking it.

Overlay Extensibility

Overlay Example

Overlay OAGIS ® Your BOD

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

OAGIS Components

OAGIS

Component Example

Header

PO BOD Assembled using Components

Line Party Address Contact Terms Charge Distribution Party Address Contact Terms Distribution Charge

Diagram Note:

OAGIS Architecture

Resources Meta Model Content

BOD Assembly Example

OAGIS ® BOD Verb Noun Component Component Field Component Compound Component Field Compound Field Field Compound Field Compound Field Field Field Field

Open Applications Group OAGIS

9 Implementation of UN/CEFACT Core Components

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 Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved

UN/CEFACT Endorsement

UN/CEFACT Standards Implemented in OAGIS

9 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 15000-5 – CCTS 2.01

UN/CEFACT TBG17 – ACCs and BIE/ABIEs as defined to this point.

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 Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved

Why did OAGIS implement CC?

• Will increase interoperability for enterprises – Encourages all business languages to be based on same concepts.

Why did OAGIS implement CC?

Building Bridges

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 Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved

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 Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved

OAGIS Component Libraries

OAGIS UN/CC Implementation Let’s Go Look

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 Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved

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

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 - ISO1500-5 Core Components Type Specification ISO - ISO20022 (UNIFI Financial Standard) ISO - ISO4217 - 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

Open Applications Group

Questions?

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 • • Emails Surveys • Luck We count downloads We track emails Probably know 10% of user base Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved

OAGIS Downloads

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 Model TM Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved

The Business Environment

Enterprise

Business Unit 1 Business Unit 2

Integration Back Bone

Business Unit n

A Case for a Canonical Model

From to

The mathematics of scaling up

For traditional point to point or integration: The number of possible connections among any number of items is n(n-1) for two way connections.

Number of components to integrate Apply traditional formula Cost of traditional integration @ 0.1 FTE n = 5 n = 10 n = 15 n = 20 5(4) = 20 10(9) = 90 15(14) = 210 20(19) = 380 2 FTEs 9 FTEs 21 FTEs 38 FTEs Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved

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 n = 5 n = 10 n = 15 n = 20 Best practices formula 5 * 2.0 = 10 10 * 2.0 = 20 15 * 2.0 = 30 20 * 2.0 = 40 Cost of best practices integration @ 0.1 FTE 1 FTE 2 FTEs 3 FTEs 4 FTEs Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved

Sample of Customers using the OAGIS Canonical Model

• • • • • • • • • • • TeliaSonera SKF Amersham Health Goodrich Aerospace Goodyear Tire Cisco IBM Boeing Ford General Electric Lucent Solution Provider specific Overlay Company Specific Overlay Vertical Content Overlay Vertical Content Overlay Vertical Content Overlay Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved

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 Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved

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 Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved

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 Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved

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 Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved

Some Automotive Adoption

Some Hi-Tech and Telecom Adoption

• • • • • • • • • • • • • Microsoft IBM Cisco Texas Instruments Motorola Qualcomm Intuit Lucent Slovak Telecom TeliaSonera British Telecom MCI Verizon Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved

Some Retail Adoption

• • • • • • • • • • Staples Best Buy Microage Nordstrom Lowes Coles-Meyers Australia Saks Home Depot Woolworths Australia Canadian Tire Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved

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 Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved

Some Aerospace Adoption

• • • •

Boeing Lockheed Martin Northrop Grumman Goodrich Aerospace

Some Services Adoption

• • • • • •

Disney Ameriquest The Hartford Standard and Poors ADP Salt River Project (Electricity)

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 Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved

End User Example

Lucent and OAGIS

® OAGIS ®

Lucent and OAGIS

® 70

US DOD

Community of OAGIS

Users Group

Campbells and OAGIS

® 73

From: [email protected]

Sent: Wednesday, June 04, 2003 11:41 PM To: Dave Chambless Cc: David Connelly; [email protected]; [email protected]

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 . . .

UK Ministry of Defense

Dubai eGovt.

SKF and OAGIS

® 76

From: [email protected]

Sent: Thursday, July 29, 2004 7:20 AM To: [email protected]

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: +46 99 9999999) (Email: [email protected]) ----------------------------------------------- Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved