Transforming InterOrganizational Business Processes to a ServiceOriented 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 2 University of St. Gallen, Institute of Information Management Müller-Friedberg-Straße 8, 9000 St. Gallen, Switzerland christine. legner@unisg. ch, tobias. vogel@unisg. ch Universität Karlsruhe (TH), Institute of Telematics, Cooperation & Management P. O. Box 6980, 76128 Karlsruhe, Germany jan. loehe@cm-tm. uka. de, mayerl@ira. uka. de

OVERVIEW n Introduction n Background n Our Approach o Step 1 – Modeling Inter-Organizational Processes o Step 2 – Aligning Private to Public Processes o Step 3 – Developing Business Services n Conclusion n Outlook 26. 02. -02. 03. 2007 Ki. VS 2

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

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

STEP 1 – Modeling Inter-Organizational Processes (Public View) VDA ECM Recommendation 4965 Computational Independent Model Public Process Roles Private Process A Information Objects Public Process Organization B Organization A n Private Process B Roles o o Organizational Coordinator, Participant Functional n Information Objects o n 26. 02. -02. 03. 2007 Ki. VS Engineering Change Request Messages o n Assembled by information objects Public Process o n Different process variants Process Interfaces o Including functional and non-functional description 5

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

STEP 2 – Aligning Private to Public Processes Computational Independent Model Private Process A Public Process Private Process B Private Roles Private Information objects Information Objects Private Processes Public Process Private Processes Manufacturer Supplier n Modeling individual private processes n Mapping private to public process model n Defining synchronization points (Milestones) 26. 02. -02. 03. 2007 Ki. VS 7

STEP 2 – Synchronizing Private and Public Processes at Milestones Publ. Priv. n Private Milestones > Public VDA ECM Milestones o Publ. Priv. 26. 02. -02. 03. 2007 Ki. VS Retain private milestones n Private Milestones < Public VDA ECM Milestones o Add private milestone according to public milestone n Private Milestones ≠ Public Milestones o Adjust private to public milestones (M 3. 2 ECR Created, M 3. 4 ECR commented, M 4 ECR Accepted) 8

Computational Independent Model STEP 3 – Developing Business Services Private Process A Private Process B Private Information Objects Private Processes Public Process Private Processes Service-Oriented System A Platform Independent Model Public Process Taskflow Workflow Business Service Application Service Organization A Public Service Interface Messages Business Service <XML Schema> <xs: element …/> </XML Schema> <WSDL: message> <WSDL: port. Type> <WSDL: binding> </WSDL> Service-Oriented System B Taskflow Workflow Business Service Application Service Organization B n Mapping public processes to business services and messages 26. 02. -02. 03. 2007 Ki. VS 9

Messages Information Objects STEP 3 – Transforming Model Artifacts to SOA Artifacts (m) mandatory (o) optional (e) extension (na) not applicable <WSDL> <WSDL: types> <WSDL: message> <WSDL: operation> <WSDL: interface> <WSDL: service> </WSDL> Business Service Interface n Mapping information objects to messages n Describing business services with WSDL 26. 02. -02. 03. 2007 Ki. VS 10

STEP 3 – Prototypical Implementation Using BEA Web Logic Orchestration of Private (Web-)Services triggered. Public by the. Interface Business (Web-)Service Public of Business Service 26. 02. -02. 03. 2007 Ki. VS Private (Web-)Services 11

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

OUTLOOK Inter-Organizational Business Process Private Process A Public Process Business Service-Oriented System A Private Process B Business Services Public Service Interfaces Organization A Service-Oriented System B Organization B n Transformation of models Mapping EPC business process models to Business Process Execution Language (BPEL) o Using meta models and markers to automate the transformation o 26. 02. -02. 03. 2007 Ki. VS 13

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 2 University of St. Gallen, Institute of Information Management Müller-Friedberg-Straße 8, 9000 St. Gallen, Switzerland christine. legner@unisg. ch, tobias. vogel@unisg. ch Universität Karlsruhe (TH), Institute of Telematics, Cooperation & Management P. O. Box 6980, 76128 Karlsruhe, Germany jan. loehe@cm-tm. uka. de, mayerl@ira. uka. de