Download
beyond web services n.
Skip this Video
Loading SlideShow in 5 Seconds..
Beyond Web Services PowerPoint Presentation
Download Presentation
Beyond Web Services

Beyond Web Services

139 Views Download Presentation
Download Presentation

Beyond Web Services

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Beyond Web Services OracleWorld 2003 Using OAGIS as a Standard Business Language for Enterprise Integration David Connelly, CEO, Open Applications Group, Inc. www.openapplications.org

  2. Agenda • Open Applications Group Introduction • Trends in Global Business Integration • Open Applications Group Standard • OAGIS as a Canonical Model • A Business Language for Web Services

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

  4. Open Applications Group E2E = B2B + A2A + A2ETM Everywhere to Everywhere Integration

  5. OAGI Activities • Technical Activities • 6 XML Work Groups • Out Reach Activities • Working with Industry • Interoperability Activities • NIST Test Bed • Services and Training • OAGIS Help to Users

  6. Oracle and OAGi To be completed • Oracle is a founding member • Major supporter of OAGi • Building OAGIS into Oracle Applications • What else to say? • Which applications use OAGIS? • When is Oracle going to Schema? • When is Oracle going to Web Services • Who at Oracle can I contact?

  7. Trends in Global Business Integration

  8. Need for Integration 82% of IT Professionals say that integrating existing systems is their way to improve business processes Source: Information Week, Aug. 27, 2001

  9. Demand for Integration Customers’ top strategic software platform project over the next year

  10. The Challenges • Multiplicity of applications across enterprise fulfilling the same function • No enterprise wide application and information architecture • Inflexible architecture • Several versions of “enterprise-objects” such as Product, Customer, etc

  11. Enterprise BusinessUnit n BusinessUnit 2 BusinessUnit 1 Supplier Customer Integration Back Bone Business Environment

  12. The Focus • Agility • Lower cost of ownership

  13. Current State of Integration • Mostly at the data level • Mostly point to point • Custom program interfaces or flat file exchange • Grows at exponential rate

  14. EDI Views • EDI is not disappearing soon • 1st Generation B2B • Suited mainly for big companies • Still largest B2B environment • Organizations generally don’t remove systems that work

  15. A Vision of Plug and Play Connected!

  16. 95% 5% Semantic Importance • Interoperability requires interfaces to be standardized. Only 5% of the interface is a function of the middleware. The other 95% is a function of the application semantics. (Gartner Group) Application Integration Semantics Messaging and Transport Services

  17. XML Emerging • XML is a successor to EDI • XML defines the data as it is being transmitted • XML is technology neutral • More powerful capabilities for integration • Emerging tools supporting it

  18. Why XML? • XML provides a much richer data capability than other approaches • XML enables more advanced types of eBusiness connections and application integration • XML tools provide more options for interoperability • XML is designed for the web and Web Services • XML is less expensive than EDI • Brings in your smallest trading partners at a very low entry cost • EDI for the masses

  19. EDI Views • EDI is not disappearing soon • 1st Generation B2B • Suited mainly for big companies • Still largest B2B environment • Organizations generally don’t remove systems that work

  20. We are about here XML Adoption Curve • Out of experimental stage • Fully into early adoption • Less talk, more action • It is not too late

  21. What is OAGIS?

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

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

  24. Example Scenario– Catalog and Price List

  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.

  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.

  27. OAGIS BOD Definition • The OAGIS BOD Architecture is defined in the OAGIS Design Guide – A Word Documentor on web site in HTML. • The OAGIS BOD Definitions are defined in XML Schema, in a text file such as: • ProcessPurchaseOrder.XSD • Equivalent to 850 definition • The OAGIS BOD Instances (occurrences) are defined in XML files that are pure text: • ProcessPurchaseOrder.XML • Equivalent to an 850 occurrence

  28. Sample BOD Definitions • ProcessPurchaseOrder • CancelPurchaseOrder • AcknowledgePurchaseOrder • ShowShipment • ProcessInvoice • GetInventoryCount • GetCredit • SyncProductionOrder

  29. The BOD Architecture

  30. BOD Application Area

  31. Verb Noun BOD Data Area

  32. Core Components (each box is a component) POORDERHDR PARTNER ADDRESS CONTACT POTERM Business View of BOD Definition CHARGE DISTRIBUTN POORDERLIN PARTNER ADDRESS CONTACT POTERM DISTRIBUTN CHARGE DISTRIBUTN POSUBLINE Diagram Note: - Required = Solid boxes POLINESCHD - Optional = Dashed boxes Business View of BOD

  33. OAGIS Extensibility • Scenario Extensibility • Scenario extensibility enables the use of the Scenarios as a base library of processes. • BOD Extensibility • UserArea extensions provide for optional elements within each OAGIS component to carry any necessary additional information. • Overlayextensions provide the ability to have extensions show up in-line with OAGIS defined fields, compounds, and components. This is not possible with DTDs.

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

  35. OAGIS BOD Benefits • Ensures common look, feel, and behavior of all XML messages in the repository • Enables common components and common dictionary • Guarantees a high level of re-use • Enables the extensibility mechanisms • Provides a faster learning curve

  36. Current Version • OAGIS 7.2.1/8.0 • 7.2.1 is DTD • 8.0 is XSD • Functional Equivalence • 60 Collaboration Definitions • Support for SOAP, ebXML, RNIF, BizTalk • 201 XML Message Definitions • Actually the 16th Version • 8+ years in maturing • Available for Free http://www.openapplications.org/downloads/oagidownloads.htm

  37. OAGIS Content • eCommerce • e-Catalog • Price Lists • RFQ and Quote • Order Management • Purchasing • Invoice • Manufacturing • Plant Data Collection • Engineering • Warehouse Management • Enterprise Asset Mgmt. • Logistics • Shipments • CRM • Customer • Sales Force Automation • ERP • Financials • Human Resources • Manufacturing • Credit Management Value Chain CollaborationApplications EnterpriseManagement Applications EnterpriseExecutionApplications

  38. OAGi Work Groups • CRM XML • Logistics XML • RiskML • Location Services • Core Components • Semantic Integration

  39. Forming Work Groups • Any Three Members • May be Industry-Based • May be Domain Based • Work Group Types • Regular • Collaborative • Self-Governing

  40. Industry Collaborations • UN/CEFACT – United Nations • ISO- International Standards Organization • MoU MG – Memorandum of Understanding Management Group • KIEC – Korean e-Commerce Consortium • NIST – National Institute of Standards & Technology • AIA – Aerospace North America • AECMA – Aerospace Europe • STAR – Auto Retail North America • AIAG – Auto Supply Chain North America • AAIA – Auto Aftermarket North America • Odette – Auto in Europe • RV Industry – North America • HR-XML – HR Content, world-wide • SP95 – Enterprise Controls • ARTS (Retail) • STEP – Engineering world-wide • IFX – Interactive Financial Exchange • EIDX – Electronics and Computer Industry • IEC TC57 WG14 • Footwear Industry

  41. Tens of thousands of OAGIS Library Downloads since 1996 Each Download contains all OAGIS Schemas Use includes B2B, 80% A2A, 64% C2B, 15% Representing over 60 countries 5 Continents OAGIS Adoption

  42. Some OAGIS Contributors STAR

  43. OAGIS Live in 40 Known Countries • Holland • Hungary • India • Israel • Italy • Japan • Korea (South) • Lithuania • Mexico • Netherlands (Holland) • Norway • Papua New Guinea • Poland • Russia • Saudi Arabia • Singapore • Slovenia • Solvakia • South Africa • Spain • Sweden • Switzerland • Turkey • United Arab Emirates • United Kingdom • United States • Australia • Austria • Bahrain • Belgium • Canada • Chile • China • Croatia • Czech Republic • Denmark • Ireland • Finland • France • Germany

  44. OAGIS Used in over 37 Known Industries • Industrial Goods Manufacturing • Logistics • Mining • Oil • Natural Gas • Paint • Paper • Publishing • Retail • Shipping • Software • State and Local Government • Telecommunications • Tire Manufacturing • Tobacco • Trucking • Universities • Electric Utilities • 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 • Insurance

  45. OAGIS as a CANONICAL MODEL

  46. Enterprise BusinessUnit n BusinessUnit 2 BusinessUnit 1 Supplier Customer Integration Back Bone Business Environment

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

  48. Number of components to integrate Cost of traditional integration @ 0.1 FTE Apply traditional formula 2 FTEs 9 FTEs 21 FTEs 38 FTEs n = 5 5(4) = 20 n = 10 10(9) = 90 n = 15 15(14) = 210 n = 20 20(19) = 380 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.

  49. 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 n = 10 10 * 2.0 = 20 n = 15 15 * 2.0 = 30 n = 20 20 * 2.0 = 40 1 FTE 2 FTEs 3 FTEs 4 FTEs

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