Open Applications Group Briefing January 2004 http www

Open Applications Group Who we are Not-For-Profit Industry Consortium to: Promote interoperability among Business Software Applications and To create and/or endorse one or more standards for easier business software interoperability Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 2

The Open Applications Group • OAGi is. . . The Open Applications Group, Incorporated • OAGIS is. . . The Open Applications Group Integration Specification Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 3

Open Applications Group • • This E 2 E goal is unique to OAGi All other SDO’s focus on B 2 B exclusively OAGi only does business languages OAGi does this for: – Outside the Enterprise (B 2 B) – Inside the Enterprise (A 2 A) – Down the Enterprise (A 2 E) • A 2 E is Application to Execution and Engineering Systems Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 5

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 -2003 Open Applications Group, Inc. All rights reserved 6

Umbrella • OAGi is an umbrella organization for building business languages for interoperability Copyright

By the Membership and for the Membership • • OAGi is owned by it’s members Open membership Anyone can join Must be a member to join or form a Workgroup • OAGIS work is supported by membership fees Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 8

Business Languages for Interoperability • OAGi focuses on business languages only • All work is based on OAGIS • No Duplicate efforts • Message architecture is consistent • Development Methodology is consistent • This eliminates the 2 to 3 year start -up and duplication of efforts Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 9

Forming Work Groups • • Any three members may form a Workgroup May be Domain Based May be Industry Based Work Group Types – OAGi Internal – External and Collaborative Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 10

OAGi Internal Work Groups • • • Core Components CRM XML Logistics XML Location Services Risk. ML (ICXML) Vision. ML Semantic Integration OAGi/NIST Test Bed Web Services – WS-I Member – WSDL for BODs Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 11

OAGi External Collaborative Workgroups • • • AIAG Odette STAR Automotive Aftermarket (AAIA) Heavy Truck ITA (German Technology Providers) OSCRE (Facilities Management) SWIFT/IFX/TWIST Payment Workgroup Korbitt - Korean B 2 B Test Bed Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 12

Workgroups Accessible on OAGi Web Site http: //www. openapplications. org Copyright © 1995 -2003

OAGIS Adoption • Tens of thousands of OAGIS Library Downloads since 1996 • Each Download contains all OAGIS Schemas • Use includes – B 2 B, 80% – A 2 A, 64% – C 2 B, 15% • Representing over 60 countries • 5 Continents Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 14

OAGIS in over 38 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 Pharmaceutical Insurance Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved • • • • • 15 Industrial Goods Manufacturing Logistics Medical Device Manufacturing Mining Oil Natural Gas Paint Paper Publishing Retail Shipping Software State and Local Government Telecommunications Tire Manufacturing Tobacco Trucking Universities Electric Utilities

OAGIS Live in 40 Known Countries • • • • Australia Austria Bahrain Belgium Canada Chile China Croatia Czech Republic Denmark Ireland Finland France Germany • • • • Holland Hungary India Israel Italy Japan Korea (South) Lithuania Mexico Netherlands (Holland) Norway Papua New Guinea Poland Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 16 • • • • Russia Saudi Arabia Singapore Slovenia Solvakia South Africa Spain Sweden Switzerland Turkey United Arab Emirates United Kingdom United States

OAGi Example XML Implementations • • • • • • • • • • • ADC Broadband Agilent Atofina Chemical ATT Wireless Bank of America B. Braun Mc. Gaw BE Aerospace Black & Decker Boeing CD Net Chicago Tribune Champion Paper Chesapeake Covisint Corio EUROFLUX Du. Pont Falconbridge Ford Motor Company Franklin Covey General Motors Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 17 Gilroy Foods Gold. Kist IBM ICI Paints IDS Scheer Labatt Ingersol Rand Johnson Controls Lockheed Martin Lucent Mrs. Smiths Pioneer Play by Play Qualcomm Quebec Government Random House Sasol Shell Steelcase US Air Force US DOD Xerox

OAGi Organization, Workgroups, and OAGIS as the Unifier CRM XML Risk Markup Language Logistics XML Parts Ordering Inventory Visibility OAGIS Canonical Business Language Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 18

Benefits of OAGIS-based Work • Fast start up – Rich body of work gives an excellent starting point – Technical Architecture in place – Development Methodology in place – IP Policy in place – Eliminates the 2 year start up – Can begin content work immediately • Common Architecture – – Technical Architecture - BOD Application Architecture Framework Independence No competing standards under the umbrella Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 19

What is OAGIS? Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved

OAGIS is Process Definitions and Payloads • Scenario is process definition • Business Object Documents (BODs) are messages within the Collaboration • Freely downloadable at: http: //www. openapplications. org Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 21

OAGIS Scenarios are Processes • Scenarios may be large or small – Processes, Activities, Tasks, etc. • Scenarios are expressed in UML • Scenarios serve as a library of re-useable processes • Organizations are welcome to modify to fit their requirements Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 22

OAGIS Scenarios Page one of three • • • • • 1. 0 General Ledger to Sub-Ledger Scenario Description. . 2. 0 General Ledger to Budget. 3. 0 Order Management to Accounts Receivable 4. 0 Order Management to Accounts Receivable 5. 0 Order Management to Accounts Receivable 6. 0 Order Management to Accounts Receivable 7. 0 Purchasing to Accounts Payable 8. 0 Purchasing to Accounts Payable 9. 0 Project Accounting Synchronization 10. 0 Feeder Applications to Project Accounting 11. 0 Human Resources Integration 12. 0 Purchase Order Process 13. 0 Plant data Collection – Warehouse Management (Cycle Counts) 14. 0 Plant Data Collection – Warehouse Management (Issues) 15. 0 Plant Data Collection – Warehouse Management (Transfers) 16. 0 Plant Data Collection – Warehouse Management (Receipts) 17. 0 Plant Data Collection – Warehouse Management (Production Orders) 18. 0 Plant Data Collection – Warehouse Management (Work in Process) 19. 0 Plant Data Collection – Warehouse Management (Shipping) 20. 0 Plant Data Collection – Warehouse Management (Time and Attendance) Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 23

OAGIS Scenarios Page two of three • • • • • 21. 0 22. 0 23. 0 24. 0 25. 0 26. 0 27. 0 28. 0 29. 0 30. 0 31. 0 32. 0 33. 0 34. 0 35. 0 36. 0 37. 0 38. 0 39. 0 40. 0 Manufacturing to Purchasing – Receiving and Inspection in Manufacturing (Publish/Subscribe Model) Manufacturing to Purchasing – Receiving and Inspection in Manufacturing (Request/Replay and Publish/Subscribe) Manufacturing to Purchasing – Receiving and Inspection in Purchasing (Request/Reply and Publish/Subscribe) Manufacturing to Order Management – Financials with Logistics, (Make to Order, Build to order) Manufacturing to Order Management – Financials with Logistics, (Engineer to Order, Configure to order) Manufacturing to Order Management – Financials with Logistics, (Mixed Mode Manufacturing) Manufacturing to Order Management – Financials with Manufacturing, (Make to Order, Build to Order) Manufacturing to Order Management – Financials with Manufacturing, (Engineer to Order, Configure to Order) Manufacturing to Order Management – Financials with Manufacturing, (Mixed Mode Manufacturing) Invoice Matching, Matching in Purchasing, Invoices entered in Purchasing Invoice Matching, Matching in Purchasing, Invoices entered in Accounts Payable (Publish/Subscribe) Invoice Matching, Matching in Purchasing, Invoices entered in Accounts Payable (Request/Reply) Invoice Matching, Matching in Accounts Payable, Invoices entered in Accounts Payable (Publish/Subscribe) Invoice Matching, Matching in Accounts Payable, (Request/Reply) Synchronize Sales Orders for Shipping Sales Force Automation to Order Management, Updating orders in Order Management Sales Force Automation to Order Management, Inquiring on orders in Order Management Sales Force Automation to Order Management and Shipping Supply Chain Integration, Manufacturing to Purchasing, Order Management, Billing, Shipping, and Financials Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 24

OAGIS Scenarios Page three of three • • • • • • 41. 0 42. 0 43. 0 44. 0 45. 0 46. 0 47. 0 48. 0 49. 0 50. 0 51. 0 52. 0 53. 0 54. 0 55. 0 56. 0 57. 0 58. 0 59. 0 60. 0 61. 0 Customer Service Integration, Field Service, No Returns Manufacturing to Order Management, Financials with Manufacturing, Make to Order with Credit Checking Manufacturing to Purchasing, Receiving and Inspection in Manufacturing, Request/reply Model Production Synchronization Purchase Order Integration Production Routing synchronization Human Resources Integration Hr to Time Data Collection Engineering Changes Scenario Description ERP to Finite Scheduling and Manufacturing Execution Scenario Description Computerized Maintenance Management System (CMMS) to Field Devices Catalog Exchange Scenario Description Price. List Exchange Scenario Description Item Unit-Of-Measure (UOM) Integration Scenario Buyer and Supplier RFQ - Quote Scenario Description Forecast Exchange Scenario Description - Revision 001 Production to Manufacturing Execution Scenario Description Supply Chain Execution Scenario Description Ledger Actuals Scenario Description Vendor Managed Inventory (Consumption) Scenario Description Full Cycle Purchasing (non-production) Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 25

OAGIS BODs are a Language • OAGIS BODs use XML to define a common business language for businesses to use. • This language is used to exchange information between business applications and businesses. Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 26

OAGIS BOD Definition • The OAGIS Business Object Document (BOD) Architecture defines the common XML structure and behavior definition for all OAGIS Messages. • The OAGIS BOD Definition defines the layout or structure of a specific message to be used. • The OAGIS BOD Instance is an occurrence of a live message that contains real data in the format defined in the schema above. • The term BOD is often used as a generic term used to describe either BOD Definitions or BOD Instances. Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 27

POORDERHDR PARTNER Core Components (each box is a component) ADDRESS CONTACT OAGIS BOD – (Payload is entire structure) POTERM CHARGE DISTRIBUTN POORDERLIN PARTNER Business View of BOD ADDRESS CONTACT POTERM DISTRIBUTN Diagram Note: - Required = Solid boxes - Optional = Dashed boxes CHARGE DISTRIBUTN POSUBLINE POLINESCHD Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 28

OAGIS Core Components • OAGi has been building these “core components” building blocks since 1995 • OAGIS Nouns are comprised of these Core Components • Used to “Assemble” the BODs • Usually only 50% or less of a new BOD has to be built. • Most new BODs re-use at least 50% of existing work. Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 29

OAGIS Core Components • OAGi is committed to supporting the UN/CEFACT TBG 17 CC Harmonization Process • OAGi members are actively engaged with the UN/CEFACT efforts Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 30

The BOD Architecture Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved

BOD Application Area Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved

BOD Architecture Verb Noun Copyright © 1995 -2003 Open Applications Group, Inc. All rights

OAGIS Architecture Resources Which Content Includes Copyright © 1995 -2003 Open Applications Group, Inc.

BOD Assembly Example Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved

OAGIS Nouns • • Nouns are consistent like Common Objects 62 in OAGIS 8 (70 in 9. 0) Can be Documents Can be Control Data Can be any content needed in a message Behavior is affected by Verbs are described in next section Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 36

OAGIS 8. 0 Nouns • • • • BOD Bill. Of. Material Catalog Chart. Of. Accounts Consumption Costing. Activity Credit. Status Delivery. Receipt Dispatch. List Electronic. Catalog Employee. Time Employee. Work. Schedule Engineering. Change. Document Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved • • • • 37 Exchange. Rate Field Financial. Document Inspection Inventory. Balance Inventory. Count Inventory. Issue Inventory. Movement Inventory. Receipt Invoice Item. Cross. Reference Item. Master Journal. Entry Ledger

OAGIS 8. 0 Nouns • • • • Item. Cross. Reference Item. Master Journal. Entry Ledger. Actual Ledger. Budget Ledger. Transaction. Document Location Maintenance. Order Match. Document Match. Failure Match. Ok Party Payable Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved • • • • 38 Personnel Pick. List Planning. Schedule Price. List Product. Availability Production. Order Product. Requirement Project. Accounting Purchase. Ledger. Invoice Purchase. Order Quote Receivable Request. For. Quote Requisition

OAGIS 8. 0 Nouns • • • • • Resource. Allocation Routing Sales. Order Sequence. Schedule Shipment. Planning. Schedule Shipment. Schedule Supply. Chain. Execution Time. Reporting Unit. Of. Measure. Group WIPConfirm Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 39 WIPMerge WIPMove WIPRecover WIPSplit WIPStatus

OAGIS Verbs • Approach derived from Object Orientation • Nouns may need different attributes at execution time • OAGi invented the Verb to provide this capability. • OAGIS constrains the Nouns using XPath portion of XSL (Not XSLT portion) • Example – Sync. Purchase. Order – Cancel. Purchase. Order Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 40

Verbs Constrain the Nouns • Nouns are Consistent as Common Objects • Nouns may need to be different at execution • OAGIS constrains the Nouns with XPath portion of XSL (Not XSLT portion) • The Verbs drive these constraints • Example – Sync. Purchase. Order – Cancel. Purchase. Order Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 41

OAGIS Verbs • • • • Acknowledge Cancel Change Confirm Get Show Get. List

OAGIS Verb Rules Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved

OAGIS Verb XSL Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved

Validated against Verb OAGIS Schema adherence to BOD Constraints Using a standard XSL Processor BOD XML Schema Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved XSL Processor Validating Parser Using a. Instance standard BODXML Instance BOD schema-validating parser Checked for Constraining the Noun BOD Constraints 45 Application

Overlay Extensibility • Unique to OAGIS • Non-invasive extensibility • Use two new XML Schema features – Name Space – Substitution Group • Uses OAGIS as base • Enables the Workgroup to build only new or unique content • Finished schema is customized for End -User Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 46

Overlay Example Overlay OAGIS Your BOD Copyright © 1995 -2003 Open Applications Group, Inc.

Extensibility Benefits • • Non-intrusive to the standard Leverages work of OAGIS base More customized approach for user Less re-work for re-application at next release • Easier to manage Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 48

Current Scope of OAGIS Content • e. Commerce – – – e-Catalog Price Lists RFQ and Quote Order Management Purchasing Invoice – – Plant Data Collection Engineering Warehouse Management Enterprise Asset Mgmt. Value Chain Collaboration Applications • Manufacturing Enterprise Management Applications • Logistics Enterprise Execution Applications – Shipments • CRM – Customer – Sales Force Automation • ERP – – Financials Human Resources Manufacturing Credit Management Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 49

Current OAGIS Release • OAGIS 8. 0 – – – – Full XML Schema, 4 th Generation for OAGIS Approx 60 Scenario Definitions Approx 200 Messages Approx 62 nouns Approx 19 Verbs Approx 190 Core Components Actually the 18 th Release • 8+ years in maturing Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 50

Framework Independence • OAGIS is framework independent • The separation of the message architecture from the framework is critical to enable cross environment deployment Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 51

OAGIS fits with eb. XML • Communication Layer (T&R) ü eb. XML Transport • Partner Agreements (CPP, CPA) ü Format - eb. XML • Process Definitions (BPSS) Format – eb. XML ü Content - OAGIS ü • Syntax ü OAGIS Tags • Meaning of Information ü OAGIS Dictionary Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 52

OAGIS and SOAP • SOAP Overlaps with BOD Application Area – – Sender, Date. Time, Digital Signature BOD does not assume SOAP BOD has to remain neutral BOD may be used without SOAP • Strategies for Use – Use Application Area for business applications – Don’t use Application Area as an envelope – Make sure you use Date. Time and BODId at least Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 53

OAGIS and Web Services WSDL • Web Services standardizes – – Shape of the plugs (SOAP) Shape of the outlet (WSDL) Current over the wire (OAGIS XML) WS-Security will be the ground SOAP WS Security Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 54 OAGIS XML

OAGIS is Framework Independent eb. XML is the envelope OAGIS is the payload Web Services is the envelope Your Envelope is the envelope Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 55

Using OAGIS XML as a Canonical Model Copyright © 1995 -2003 Open Applications Group,

Business Environment Business Unit 1 Business Unit n Business Unit 2 Integration Back Bone

A Case for a Canonical Model From <many to many> to <many to one>

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 Apply traditional formula Cost of traditional integration @ 0. 1 FTE n=5 5(4) = 20 2 FTEs n = 10 10(9) = 90 9 FTEs n = 15 15(14) = 210 21 FTEs n = 20 20(19) = 380 38 FTEs Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 59

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 integration @ 0. 1 FTE n=5 5 * 2. 0 = 10 1 FTE n = 10 10 * 2. 0 = 20 2 FTEs n = 15 15 * 2. 0 = 30 3 FTEs n = 20 20 * 2. 0 = 40 4 FTEs Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 60

Side by side comparison <many to many> growth <many to one> growth 4 FTEs

Lucent SOA with OAGIS Canonical Model Copyright © 1995 -2003 Open Applications Group, Inc.

Agilent Enterprise Integration Model Service & Support e. Business Order Generation Broadvision en. Commerce Blade Runner Order Fulfillment Oracle Apps Merging Companies’ Applications Packaged, Legacy OAGi Canonical Model TIBCO Bus (RVRD) Reference Systems Product Supplier Customer Price Company Information Finance Information Management SAP/Oracle People. Soft Functional Applications Legal, GTT, WPS. . . Data Warehousing Reporting Legacy Systems Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved HR 63 Intranet Content Xpedio/ Blade. Runner / Filenet

Sample of Customers using the OAGIS Canonical Model • • • Agilent Amersham Health Emerson Motors Ford General Electric Power Goodyear IBM Lucent US Air Force Weyerhauser Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 64

Development Methodology Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 65

Development Methodology • • Demand driven Projects led by members Virtual teams Work done by email and teleconference between meetings • Repeatable process Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved 66

OAGi Open Development Methodology Project Definition Review & Approval Construction Activities - Propose Project Build Project Definition Choose Team Get CTO Approval Set up Yahoo Group - Deliverables (PL) Deliverables (PL, TM) - Project Definition - Project Team - Yahoo Group - Business process modeling BOD message development Dictionary development XML Schema development XML message examples development - Teleconferences with project team - Construction Phase review to OAGi technical meeting - OAGi architectural review Integration Scenario(s) BOD documentation Dictionary updates XML Schemas (DTDs) XML message examples Copyright © 1995 -2003 Open Applications Group, Inc. All rights reserved Activities - Review deliverables with OAGi Architect - Review final deliverables with working team and ask for vote. - Present to OAGi Technical team and ask for vote - Finalize changes based on voting results - Turn deliverables over to OAGI architect - CTO presents to OAGi Board for final approval Deliverables (PL, TM) - Approved versions of the following: - Integration Scenario(s) - BOD documentation - Dictionary updates - XML Schemas (DTDs) - XML message examples 67 Roles: PL - Member Project Leader TM - Team members OA - OAGi Architect CTO - OAGi CTO Publication Activities - OAGi Architectural review for consistency, etc. - Editing by OAGi architect - Final testing of XML deliverables - Combine all project content together - Complete any defect removal necessary - Complete any requested enhancements not in a specific project - Publish to OAGi web site. Deliverables (OA, CTO) - Final versions of the following: - Integration Scenario(s) -UML Sequence Diagram -UML Collaboration Diagram - BOD documentation - Dictionary updates - XML Schemas (XSD) - XML message examples