Transforming Inter-Organizational Business Processes to a Service-Oriented Architecture Transforming Inter-Organizational Business Processes to a Service-Oriented Architecture Method and Application in the Automotive Industry Christine Legner 1, Tobias Vogel 1, Jan Löhe 2, Christian Mayerl 2 1 University of St. Gallen, Institute of Information Management Müller-Friedberg-Straße 8, 9000 St. Gallen, Switzerland 2 Universität Karlsruhe (TH), Institute of Telematics, Cooperation & Management P.O. Box 6980, Karlsruhe, Germany

KiVS2 OVERVIEW Introduction Background Our Approach  Step 1 – Modeling Inter-Organizational Processes  Step 2 – Aligning Private to Public Processes  Step 3 – Developing Business Services Conclusion Outlook

KiVS3 INTRODUCTION – Scenario and Questions How to model inter-organizational business processes? How to align private processes to a common public process? How to map model artifacts onto components of a SOA? Organization A Organization B Inter-Organizational Business Process Private Process A Private Process B Service-Oriented System A Service-Oriented System B Public Process Step 1 Step 2 Step 3 Public Service Interfaces Business Services Business Services

KiVS4 BACKGROUND – “SOA For Automotive” Project Industrial project, funded by participants Objectives  Service-oriented architecture for inter-organizational processes  Flexibility of an SOA for m:n industrial cooperation  Maturity of Web service technologies Core Web service standards (SOAP, WSDL, UDDI) 2nd generation of Web service specifications (WS-Security, WS-Transaction, etc.) Scenario  Engineering Change Management – VDA 4965 ECM, OMG PLM Services Constraints  Process modeling with Event-Driven Process Chains (EPCs)

KiVS5 Public Process  Different process variants Process Interfaces  Including functional and non-functional description Information Objects  Engineering Change Request Messages  Assembled by information objects Organization A Organization B STEP 1 – Modeling Inter-Organizational Processes (Public View) Private Process APrivate Process B Public Process Roles Information Objects Public Process Computational Independent Model VDA ECM Recommendation 4965 Roles  Organizational Coordinator, Participant  Functional

KiVS6 STEP 1 – Modeling Roles, Information Objects and Processes with Event-Driven Process Chains (EPCs) Roles  Organizational – Coordinator (Process owner) and Participant (Involved party)  Functional – Engineering Change Manager, Comment Performer, Approver, etc. Public Process and Interface  ECR process with interface (including functional and non-functional description) Information Objects  Building blocks for the Engineering Change Request, e.g. ECR_id, ECR_header, ECR_detail, etc.

KiVS7 Manufacturer Supplier STEP 2 – Aligning Private to Public Processes Modeling individual private processes Mapping private to public process model Defining synchronization points (Milestones) Private Process APrivate Process BPublic Process Roles Information Objects Public Process Private Roles Private Information Objects Private Processes Private Roles Private Information objects Private Processes Computational Independent Model

KiVS8 STEP 2 – Synchronizing Private and Public Processes at Milestones Private Milestones > Public VDA ECM Milestones  Retain private milestones Private Milestones < Public VDA ECM Milestones  Add private milestone according to public milestone Private Milestones ≠ Public Milestones  Adjust private to public milestones (M3.2 ECR Created, M3.4 ECR commented, M4 ECR Accepted) Publ. Priv. Publ. Priv. Publ. Priv.

KiVS9 Organization B Organization A Service-Oriented System A Service-Oriented System B Public Service Interface STEP 3 – Developing Business Services Mapping public processes to business services and messages Private Process APrivate Process BPublic Process Computational Independent Model Platform Independent Model Application Service Business Service Taskflow Workflow Information Objects Private Information Objects Public Process Private Processes Application Service Business Service Taskflow Workflow Messages Business Service

KiVS10 STEP 3 – Transforming Model Artifacts to SOA Artifacts Mapping information objects to messages Describing business services with WSDL Messages Information Objects Business Service Interface (m) mandatory (o) optional (e) extension (na) not applicable

KiVS11 STEP 3 – Prototypical Implementation Using BEA Web Logic Public Interface of Business (Web-)Service Private (Web-)Services Orchestration of Private (Web-)Services triggered by the Public Business Service

KiVS12 CONCLUSION Ingredients of inter-organizational process models  Roles (organizational and functional), information objects, processes  Separation of internal (private) and inter-organizational (public) processes Interfaces between private and public processes  Milestones at the interface between private and public processes  Starting point for deriving public business services Development of business services  Mapping information objects to messages  Description of business services using WSDL Necessary prerequisites  At computational independent business level VDA ECM Recommendation 4965 as applied in the project „SOA For Automotive”  For interoperability at systems level Standardized Web service technologies

KiVS13 OUTLOOK Transformation of models  Mapping EPC business process models to Business Process Execution Language (BPEL)  Using meta models and markers to automate the transformation Organization A Organization B Inter-Organizational Business Process Private Process A Private Process B Service-Oriented System A Service-Oriented System B Public Process Public Service Interfaces Business Services Business Services

Transforming Inter-Organizational Business Processes to a Service-Oriented Architecture Transforming Inter-Organizational Business Processes to a Service-Oriented Architecture Method and Application in the Automotive Industry Christine Legner 1, Tobias Vogel 1, Jan Löhe 2, Christian Mayerl 2 1 University of St. Gallen, Institute of Information Management Müller-Friedberg-Straße 8, 9000 St. Gallen, Switzerland 2 Universität Karlsruhe (TH), Institute of Telematics, Cooperation & Management P.O. Box 6980, Karlsruhe, Germany