David Chen IMS-LAPS University Bordeaux 1, France

1. BARRIERS DRIVEN METHODOLOGY FOR ENTERPRISE INTEROPERABILITY David Chen IMS-LAPS University Bordeaux 1, France

2. Guide the implementation of the interoperability • Avoid hazardous approaches (reduce time and cost to implement) • Capitalize good practices and solutions Developing Methodology :motivations & objectives To develop methodology

3. Enterprise interoperability Definition Interoperability Ex. ERP, SCM, PLM, Virtual enterprise,… application domain - Interoperability: the ability for two (or more) systems or components to exchange information and to use the information that has been exchanged (IEEE) Requirements, Generic concepts, experiences, principles, solutions validations and methodology Interoperability Ex. Concepts, metrics, models, framework research domain - Enterprise interoperability: the ability of interaction between enterprise systems. It is considered as significant if the interactions can take place at least at the three different levels: data, services and process, with a semantics defined in a given business context (IDEAS)

4. APPROACHES BUSINESS INTEGRATED BUSINESS UNIFIED PROCESS PROCESS FEDERATED METHODOLOGY ENABLING TOOLS CONCEPTUEL TECHNOLOGICAL ORGANISATIONAL INFRASTRUCTURE SERVICE SERVICE DATA DATA BARRIERS SOLUTIONS Basic Concepts Hypothesis and Research: - Enterprises are not interoperable because there exist barriers to interoperability - Barriers are incompatibilities of various kinds at the various enterprise levels - Identify common barriers to interoperability and solutions to remove barriers ENTERPRISE A ENTERPRISE B

5. Interoperability ontology (Naudet, 2007)

6. Components of the methodology

7. Interoperability concerns Interoperability approaches Interoperability barriers Interoperability Framework • Three basic dimensions: • - Interoperability concerns (represent interoperability aspects between two enterprises) • Business, • Process, • Service, • Data. • - Interoperability barriers (represent incompatibilities between two enterprises) • Conceptual (syntax & semantic), • Technological (platform & software), • Organizational (authority/responsibility & organization). • - Interoperability approaches (represent the ways in which the barriers are removed) • Integrated, • Unified, • Federated.

8. Interoperability knowledge/solution Template description

9. Company B Company A CONCEPTUAL CONCEPTUAL TECHNOLOGICAL TECHNOLOGICAL ORGANISATIONAL ORGANISATIONAL Iop Iop concerns concerns ++ +++ - BUSINESS BUSINESS BUSINESS BUSINESS +++ ++ - PROCESS PROCESS PROCESS PROCESS +++ - ++ SERVICE SERVICE SERVICE SERVICE +++ + + DATA DATA DATA DATA - +++ + + - ++ Interoperability measurement EIMM vs EIDM Critical Maturity model +++ ++ + Considerable Weak - None Interoperability compatibility measurement (EIDM) Interoperability potential Measurement (EIMM) Compatibility matrix Company A Company B Interoperability performance measurement (EIDM) Performance measures

10. Define objectives of Io and performance targeted; evaluate the feasibility and cost; project planning • Define needs of Io in terms of the levels of the enter- • -prise and approach (integrated, unified, federated) Definition of objectives and needs • Identify actors, applications and systems involved in interoperation • Detect barriers and problems to Io, measure existing Io degree, analyze strong and weak points Existing system analysis • Search and select available Io solution elements using the interoperability framework • Combine and construct a company specific Io solution Select and combine solutions • Implement and test the Io solution; perform a performance measure • Training company staff Implementation and test Structured approach

11. Project board Define objectives t Existing system Analysis Select/combine solutions Guide the study Implementation/test Assess solutions Project board To analyze & to validate (1) Synthesis group Synthesis group Main responsible people of the company To propose Group of specialists Interviews Perform the study and search for solution To validate Interviewees (provide information) Specialist group To provide information Structured groups /meetings Adopted from GRAI methodology

12. Shipper ATHENA A8 Scenario: Carrier-Shipper 1. Definition of objectives and needs Carrier A Carrier B Who is responsible? How is the process configured? Which applications? What’s the data structure? Sales Order Calculate Rate Delivery Calculate Rate Picking Generate Routing Code Generate Routing Code Packing Generate Label Generate Label [Provided by SAP for ATHENA A8] Shipment

13. Existing System Analysis – EIMM & EIDM Questionnaire EIMM uses Capability matrix to obtain Shipper

14. Critical +++ ++ + Considerable - Weak None - +++ - + - - - - - - - ++ Existing System AnalysisDetecting barriers FedEx Shipper

15. Carrier-Shipper Scenario Barriers

16. Interoperability knowledge/solutions repository

17. Select / Combine solutions Template: Data exchange barrier

18. Conclusions • Incompatibility is the fundamental concept used in defining the interoperability domain • Broad sense, not limited to ‘technical’ aspect but also ‘business’, ‘organization’, and concerns all levels of the enterprise • generic characteristic of the interoperability research, regardless of the content of information exchanged between two systems • Generic methodology, structured approach supported by Iop framework and Iop measurements, and Iop knowledge repository