EIC and OAGi

1. EIC and OAGi Addressing the Challenges of Cross-Industry Interoperability

2. Agenda EIC and OAGi • Introduction to EIC • OAGi and EIC – a win win scenario • Share experiences: Business profiles • Outlook EIC testbed activities • Future collaboration

3. Interoperability is complex Inter-company processes include those that exist between multiple trading partner tiers, required to create a competitive supply chain Service Provider System Design House Electronics Value Chain Portal Chemical Supplier Email Logistics Provider IPC Technology Reseller Paper Fax CIDX WS-I Retail Contract Manufacturer System OEM Sub-Assembly Manufacturer ASIC Manufacturer RosettaNet ISA-95 EDIFACT Aerospace Spec2000 Indirect Supplier RosettaNet Distributor SWIFT EDI OAGi Automotive Banking Foundry Assembly & Test Portal

4. Interoperability Trends and Challenges • Competition of value chains (instead of companies) and increasing process integration within value chains • Business partners use different process and product models • Increase in the number and complexity of electronic business relationships • Lack of commonly accepted inter-company processes • missing process standards - public processes are vague or missing altogether • Low penetration of existing standards • Lack of m:n connectivity • Time and effort for setting up electronic collaboration with a larger number of partners • inconsistent implementation of standards • Dominance of human-human interface (phone, fax, e-mail) or human-machine-interface (portals) in B2B relationships • Bilateral agreements on electronic collaboration prevail

5. Collaboration Challenges in the Future

6. Framing the Problem 3. The proliferation of vertical standards has made even this movement difficult 1. Vertical standards organizations only move companies so far along this line Magic Quadrant Within and across industries Industry Standard 2. Other companies must follow the same path for this to work The format of the message is standardized by Industry standards organizations Standard Vertical standards Aligned business processes, standardized messages and connectivity automation • The reference model aligns the critical factors of integration on two axis – messages (semantics) and business processes • To simultaneously address cost and complexity, both messages and processes must be standardized Message Legacy installations of custom work processes and message structures Custom Point-to-point Business Process Standard Custom

7. Standards and the EIC The EIC defines a standardized business process and also selects the best vertical industry standards by defining a profile Standards Reference Model Magic Quadrant Within and across industries Industry Standard Standard Vertical standards Message Custom Point-to-point Business Process Standard Custom

8. Objective of the EIC The EIC defines and applies integration methodology and tools leveraging existing standards where possible to define common public business processes for achieving interoperability of networked organizations across multiple industries. The EIC approach • Addresses the business and technical aspects of a common public process • Leverages existing technology, applications, research and standards • Defines architectures, methodologies, guidelines, best practices, semantics and interfaces • Validates an Interoperability Profile by building prototype implementations of real-world business scenarios defined by precise requirements • Delivers tools, conformance testing, analysis, training and other services to facilitate broad adoption in the community

9. Deliverables • Interoperability Profiles • A common definition of a public process that is consensus-driven • An executable business process with defined interfaces • A concise definition of required business semantics • Guidelines, conventions and best practices for using the interoperability profile in ways that ensure low-friction integration across multiple networks • Reference implementations • Demonstrate profile-based interoperability in a production implementation • Use cases and usage scenarios based on customer requirements • Sample code and applications built in multiple environments • Methodology, Test tools and supporting materials • Tools that test profile implementations for conformance with the profiles • Supporting documentation and white papers

10. Agenda EIC and OAGi • Introduction to EIC • OAGi and EIC – a win win scenario • Share experiences: Business profiles • Outlook EIC testbed activities • Future collaboration

11. Sales Order Rate& Service Selection Shipment Track & Trace Cross-org. BP Packing Label Generation Packing Sales Order View Process Shipment Process Abstraction Concept – Carrier-Shipper Scenario WebServices Carrier Rate& Service Selection View Process Label Generation Track & Trace Shipper After Sales Sales Order Delivery Picking Packing Private Process Shipment WebServices

12. Value Proposition: End Users • Without standards, each information system would require point-to-point integration which requires a significant investment in time and capital • Reduce complexity • Define a common business process with broad acceptance in an industry or across industries • Select the best message standard necessary to support the business process from the hundreds of standards specifications • Reduce total cost of ownership • Leverage the analysis and design efforts embodied in the EIC deliverables • Broad adoption allows for the work to be reused in the next integration effort • Increase Flexibility • Faster configuration of new partners and change to business processes with better, faster and more complete information flow

13. Business Forum Community Processes Analysis Validation Scoping Definition • - Identify To-Be Scenario • Define solution to resolve interoperability • challenges Identify As – Is Interoperability Situation - Identify pain points and requirements - Prioritize requirements and select target scenario - Create a reference implementation of the Interoperability Profile • Forum Charter • Containing: • - scenario process description, • - goal of forum • Alternative funding • Standards involved Capability tablesdescribing provided interfaces of participating companies Gap tables to cover the interoperability issues of all partners in forum Interoperability Profile -describes how the problem can be solvedTechnical recommendationfor research or standards development orgs guidelines training tools test tools / test suites

14. Profiling Process Life Cycle Interest Group Forum Operations Initial Detailed scoping • Member Commitment • IP Policy • Planning for Detailed Scoping • Value Prop • Business Process • St-o-t-Art • Best practices • Detailed work plan Use Case Business Process IntOp Profile Use Case Business Process IntOp Profile Charter InteroperabilityProfile

15. Analyst Consultations: • Are the challenges real? Are other organizations addressing the challenges? • Does the forum process sound reasonable? • Is the approach feasible? • Is the business model reasonable? Profiles: • “Reference Model” for Business Profiles • When addressing an interoperability profile, the EIC needs to focus on business requirements down to technology not vice versa for identifying “optimal” (not “best”) solutions. • Beware that “Standards” have been used as a marketing and commercial weapon and have frequently been manipulated so the press and analysts to a certain extent have “Standards Fatigue”. • Need to clearly articulate and reiterate that it is about business integration. • Recommended using an eclipse like iterative model of freezing a base set of processes for contributors to build off of, then rejoin to review best set of changes to enhance the next level base. Target Members • Need to differentiate what type of CIO we are addressing—those that are technology v. business oriented. • Value proposition for solution providers needed to be right sized for small, medium and large businesses stressing the strength and advantages of an ecosystem Long term Value. • The greatest value of profiling workgroups will be at the intersection of where different forums meet.

16. EIC Pilot - Background • In order to define the methodology and organization of EIC Business Forums, the initiative “SOA For Automotive”, started by University of St. Gallen (HSG) in October 2005, has been attributed the status of EIC Pilot in Q2/2006. • “SOA For Automotive” involves 6 Automotive companies, andaims at improving interoperability in OEM - supplier relationships by • Creating a common understanding of the cross-organizational engineering change management process; • establishing a clear semantic for Engineering change documents; • leveraging Web Services and SOA concepts for implementation. • Initiated by University of St. Gallen, adopted by the ATHENA research project, representing as a pilot the EIC concept • Targets of the EIC Pilot are • to define a methodology for Business ProcessForums • To serve as proof of concept for future business process forums System

17. EIC Profile: the ECM scenario supplier Automotive manufacturer (OEM) private private Public process architecture 1 process architecture Derive the public process 2 2 Map the public process to private processes Send Request_Details ReceiveRequest Details business process business process ReviewDetails DistributeAnalysis Task Analyse Affected Objects EliminateRedundancy ConductAnalysis Task Receive Respond_details SendRespond_details CheckConistency CheckAnalysis Task Map public process interfaces onto business services ConsolidateTechnical Analysis service description 4 private private (SOA based) integration architecture (SOA based) integration architecture WSDL 3 3 Semantics desktopintegration desktopintegration servicerepository service repository Specify artefacts of the service-oriented target architecture Map service-oriented target architecture to enterprises’ architectures information system information system workflow workflow businessservice businessservice applicationservice applicationservice message 5 5 application architecture application architecture

18. C.f. Roland Merrick (IBM): Interoperability Profiles for Collaborative Business Processes

19. EIC Profile Templatehttp://www.eic-community.org/Templates/InteroperabilityProfile.html

20. Example: EIC Profile for Engineering Change Management available as EIC Profile document

21. Agenda EIC and OAGi • Introduction to EIC • OAGi and EIC – a win win scenario • Share experiences: Business profiles • Outlook EIC testbed activities • Future collaboration

22. Motivation for a Global Testbed Initiative(Initiators: CEN, EIC, ETSI, NIST, KorBIT, AIAG, IAI) • e-Business interoperability typically requires that a full set of standards are implemented • from open internet and Web Services standards to industry-level specifications and e-business frameworks • There are only limited and scattered testing facilities. • As testing facilities are typically provided by one of the standard developing organizations, they have a rather narrow focus on a particular standard.

23. Overall Objectives of the Global Testbed Initiative(Initiators: CEN, EIC, ETSI, NIST, KorBIT, AIAG, IAI) • Concept for a global e-business interoperability test bed • Definition key components of a global e-business interoperability test bed • Outline of a testing methodology • Development of a roadmap for deploying a global e-business interoperability test bed • Available test expertise and facilities world wide • Worldwide requirements and global collaboration model

24. Global eBusiness Interoperability Test Bed Methodologies – Scope Phase 1: Concept and roadmap An analysis of the benefits, risks, tasks, requirements, required resources of a global e-Business interoperability test bed based on business cases; Development of alternative approaches to architecting and implementing global e-Business interoperability test bed; A recommended architecture and process to develop the test bed that follows from the requirements analysis and with clear rationale; An assessment of requirements from key international stakeholders, including of the resource commitment needed to complete the test bed development tasks. • Phase 2: Realization • implementation of the test-bed as shared testing facility based on the suggested collaboration model • provisioning of testing services to industry users, software vendors and SDOs

25. Global eBusiness Interoperability Test Bed Methodologies Project Organization Expert & Stakeholdercommunity Project team Automotive Requirements Users Project convenor Test bed architect. & collab. model SDOs Projectsteering Project secreteriat eBIF IT Vendors / Integrators Test bed architecture (Experts 1-4) CEN/ISSS Requirements Construction EIC Users ETSI Test bed architect. & collab. model Project initiators Review & Validation ofdeliverables Business teams SDOs Industry require-ments / Use cases: Automotive Construction Furniture (Experts 5-7) NIST IT Vendors / Integrators AIAG IAI Requirements Furniture Overall concept, methodology andcollaboration model(Experts 8-9) Users OtherSDOs:ISO, UN/CEFACT, … Test bed architect. & collab. model SDOs Application vendors IT Vendors / Integrators Industry users

26. Agenda EIC and OAGi • Introduction to EIC • OAGi and EIC – a win win scenario • Share experiences: Business profiles • Outlook EIC testbed activities • Future collaboration

27. EIC – Collaboration with OAGi EIC members to join OAGi Key objective: Jointly collaborate within OAGi and contribute to process orchestration activities Complement standardisation with process profiles as future delivery model Collaborate in Process Workgroups Key objective: Share experiences and best business practises, Introduce templates Interlink between industry and research Key objective: bring research activities closer to the industry alliances Automotive Pilot: Engineering change management profile Key objective: provide meta models and methodologies for business documents that are exchanged between cooperating business partners. The documents are the external representation of internal Business Objects Business Protocols define the interaction between partners and specify which documents are exchanged in which order.