Christine Legner 1 , Tobias Vogel 1 , Jan Löhe 2 , Christian Mayerl 2

1. Transforming Inter-Organizational Business Processesto a Service-Oriented ArchitectureMethod and Application in the Automotive Industry Christine Legner1, Tobias Vogel1, Jan Löhe2, Christian Mayerl2 1 University of St. Gallen, Institute of Information ManagementMüller-Friedberg-Straße 8, 9000 St. Gallen, Switzerlandchristine.legner@unisg.ch, tobias.vogel@unisg.ch 2 Universität Karlsruhe (TH), Institute of Telematics, Cooperation & ManagementP.O. Box 6980, 76128 Karlsruhe, Germanyjan.loehe@cm-tm.uka.de, mayerl@ira.uka.de

2. 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

3. INTRODUCTION – Scenario and Questions Inter-Organizational Business Process • 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? Step 1 Organization A Organization B Private Process A Public Process Private Process B Step 2 Business Services Business Services Public Service Interfaces Service-Oriented System A Service-Oriented System B Step 3

4. 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)

5. STEP 1 – Modeling Inter-Organizational Processes (Public View) VDA ECM Recommendation 4965 Organization A Organization B Private Process A Public Process Private Process B Roles ComputationalIndependentModel Information Objects Public Process • Roles • OrganizationalCoordinator, Participant • Functional • Information Objects • Engineering Change Request • Messages • Assembled by information objects • Public Process • Different process variants • Process Interfaces • Including functional andnon-functional description

6. 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.

7. STEP 2 – Aligning Private to Public Processes • Modeling individual private processes • Mapping private to public process model • Defining synchronization points (Milestones) Manufacturer Supplier Private Process A Public Process Private Process B PrivateRoles PrivateRoles Roles ComputationalIndependentModel PrivateInformation objects PrivateInformation Objects Information Objects Private Processes Public Process Private Processes

8. Publ. Priv. Publ. Priv. Publ. Priv. 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)

9. STEP 3 – Developing Business Services Organization A Organization B • Mapping public processes to business services and messages Private Process A Public Process Private Process B PrivateInformation Objects PrivateInformation Objects ComputationalIndependent Model Information Objects Private Processes Public Process Private Processes Public Service Interface Service-Oriented System A Service-Oriented System B <XML Schema> <xs:element …/> <xs:element …/> </XML Schema> PlatformIndependent Model Taskflow Workflow Taskflow Workflow Messages BusinessService BusinessService <WSDL> <WSDL:message> <WSDL:portType> <WSDL:binding> </WSDL> BusinessService ApplicationService ApplicationService

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

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

12. 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

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

14. Transforming Inter-Organizational Business Processesto a Service-Oriented ArchitectureMethod and Application in the Automotive Industry Christine Legner1, Tobias Vogel1, Jan Löhe2, Christian Mayerl2 1 University of St. Gallen, Institute of Information ManagementMüller-Friedberg-Straße 8, 9000 St. Gallen, Switzerlandchristine.legner@unisg.ch, tobias.vogel@unisg.ch 2 Universität Karlsruhe (TH), Institute of Telematics, Cooperation & ManagementP.O. Box 6980, 76128 Karlsruhe, Germanyjan.loehe@cm-tm.uka.de, mayerl@ira.uka.de