1. Rawlins EDI Consulting1 Future EDI - What comes after X12 and EDIFACT? Michael C. Rawlins

2. Rawlins EDI Consulting2 Tools Tools

3. Rawlins EDI Consulting3 What comes after X12 and EDIFACT? n Where are we now? n Defining “What” to exchange n New ways “How” to do it n Pioneers

4. Rawlins EDI Consulting4 Where are we now? n Systems evolution n How we do it now

5. Rawlins EDI Consulting5 Evolution of Applications Custom Development Packaged Applications BatchOn-LineInteractive Stand Alone InterfacedIntegrated“Componentized”

6. Rawlins EDI Consulting6 Evolution of Business Systems Stand Alone Systems LANS, WANS, VANS Internet Mainframes and Minis PCsDistributed Computing Client/ Server Network Computing

7. Rawlins EDI Consulting7 How We Do It Now Batch, Custom Interfaces, VANs

8. Rawlins EDI Consulting8 “What” n Functional Requirements u Open-edi and OO-edi u Other OO Analysis Approaches u Dictionary or Repository Based Approaches n Non-Functional Requirements

9. Rawlins EDI Consulting9 Defining Functionality n Functional Requirements = Processing and Data n Standards = Codified Functional Requirements Processes Documents Data

10. Rawlins EDI Consulting10 From Open-edi to OO-edi Open-edi Reference Model Reference Guide “Next Generation of UN/EDIFACT” OO-edi Standards Report Draft Report

11. Rawlins EDI Consulting11 Open-edi Definition “The application to application exchange of any predefined and structured data for business purposes without human intervention and without prior agreement”.

12. Rawlins EDI Consulting12 Open-edi Key Concepts n Separate “What” from “How” n Business Operational View (BOV) - “What” n Functional Service View (FSV) - “How” n Scenario - Defines: u Roles u Information to be exchanged u Characteristics of the exchange

13. Rawlins EDI Consulting13 Evolution of Analysis Techniques NapkinsNarrative Text Structured Analysis Information and Process Modeling Object Modeling

14. Rawlins EDI Consulting14 Why OO-Analysis? Traditional Analysis Processing Data ? OO Analysis Object Class Processing: “Methods” Data: “Attributes”

15. Rawlins EDI Consulting15 OO-edi Outline n Develop Open-edi using OO techniques n BOV (“What”) Only n Object Modeling via UML n Focus on application vendors, not end users

16. Rawlins EDI Consulting16 Future OO-edi Standards n Standards will define: u Standard object classes u Interactions among objects n Scenarios will specify: u Roles u Objects and methods u Services required of FSV

17. Rawlins EDI Consulting17 Object Management Group n Cross-Industry Consortium n Responsible for CORBA standard n Defining Common Business Objects n Developing Electronic Commerce Architecture

18. Rawlins EDI Consulting18 Microsoft n Partnering with application vendors n Developing industry based solutions n Notable examples: u Value Chain Initiative u Insurance

19. Rawlins EDI Consulting19 Dictionaries and Repositories n BSR - ISO Basic Semantic Repository n UDEF - CALS Universal Data Element Framework n BEACON - ICARIS Project “Object Nexus”

20. Rawlins EDI Consulting20 Non-Functional Requirements n “Quality” or “System” Requirements, Goals n Examples u Trading Partner Mandates u Low Cost u Reliability u Modifiability and Flexibility n Tradeoffs

21. Rawlins EDI Consulting21 Impact of Non-Functional Requirements n Can Determine Success or Failure n Will Dictate “How”

22. Rawlins EDI Consulting22 Example: The Analysis Process

23. Rawlins EDI Consulting23 “How” n Objects n Distributed Objects n OO-edi Implementation n BSI n XML

24. Rawlins EDI Consulting24 Standards!Standards!!Standards!!!

25. Rawlins EDI Consulting25 Why Objects? Without ObjectsWith Objects

26. Rawlins EDI Consulting26 EDI by Distributed Objects n OMG’s CORBA n Microsoft DCOM n Java RMI

27. Rawlins EDI Consulting27 OO-edi Implementation

28. Rawlins EDI Consulting28 BSI

29. Rawlins EDI Consulting29 BSI Vs. X12

30. Rawlins EDI Consulting30 XML - eXtensible Markup Language n Derived from SGML n Web and Document Centric n More powerful than HTML u Template document types u Data tags: <SHIP_DATE>19981101</SHIP_DATE>

31. Rawlins EDI Consulting31 XML for EDI n Use XML formats and tools for EDI n Primary Implementations: u Web based X12 or EDIFACT u Browser based Exchanges u Application to Application

32. Rawlins EDI Consulting32 XML for EDI via Browser Catalog Purchasing ZX-3111 World Wide Widgets

33. Rawlins EDI Consulting33 XML/EDI via Applications

34. Rawlins EDI Consulting34 XML/EDI Development n XML/EDI Group n X12 XML/EDI n EDIFACT XML/EDI n Open Financial Exchange (OFX) n Open Trading Protocol (OTP) n Proprietary - SAP and others

35. Rawlins EDI Consulting35 Pioneers n Network Management Forum n ACORD

36. Rawlins EDI Consulting36 NMF CIGP n Industry: Telecommunications n Purpose: Exchange operations information between carriers n What: Defined by object modeling n How: Common Interconnection Gateway Platform supporting many technologies

37. Rawlins EDI Consulting37 ACORD ObjX n Industry: Insurance n Purpose: Exchange information among agents and insurers n What: Defined by object modeling n How: Microsoft’s COM/DCOM now, Java and OMG’s CORBA later

38. Rawlins EDI Consulting38 What Next? n Many emerging technologies n Standards lagging behind n Babble, Esperanto, or BabbleFish? ?

39. Rawlins EDI Consulting39 What to Do? n Identify your Requirements, particularly Non-Functional Requirements n Start planning strategy n Standards - monitor, participate n Talk with application vendors ?

40. Rawlins EDI Consulting40 For More Information n www.metronet.com/~rawlins/future.html n rawlins@metronet.com ?