Transforming Inter-Organizational Transforming Inter-Organizational Business Processes Business Processes to a Service-Oriented Architecture 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 [email protected], [email protected]2 Universität Karlsruhe (TH), Institute of Telematics, Cooperation & Management P.O. Box 6980, 76128 Karlsruhe, Germany [email protected], [email protected]
14
Embed
Christine Legner 1 , Tobias Vogel 1 , Jan Löhe 2 , Christian Mayerl 2
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 - PowerPoint PPT Presentation
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Transforming Inter-Organizational Business ProcessesTransforming Inter-Organizational Business Processesto a Service-Oriented Architectureto a Service-Oriented Architecture
Method 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, Switzerland
Our Approach Step 1 – Modeling Inter-Organizational Processes Step 2 – Aligning Private to Public Processes Step 3 – Developing Business Services
Conclusion
Outlook
326.02.-02.03.2007 KiVS
INTRODUCTION – Scenario and QuestionsINTRODUCTION – 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 AOrganization A Organization BOrganization B
Inter-Organizational Business Process
PrivateProcess A
PrivateProcess B
Service-OrientedSystem A
Service-OrientedSystem B
PublicProcess
Step 1
Step 2
Step 3 PublicService Interfaces
BusinessServices
BusinessServices
426.02.-02.03.2007 KiVS
BACKGROUND – “SOA For Automotive” ProjectBACKGROUND – “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.)
Request Receiver ECR Creator Decision Team Change Team
Phase
Tech
nica
l Ana
lysi
s of
ECR
Send Request_Details
Receive Respond_Details
SendRespond_Details
Receive Request_Details
Analyse AffectedObjects
Consolidate TechnicalAnalysis
Prepare ECRFor Analysis
M3.2 ECR Created
M 3.3 ECR Detailed
Respond_Details
Request_Details
XOR
XOR
XORRollback to Analysis
ORSelect Notfication
List & Send Notify_ECR_Update
Notify_ECR_Update Recieve Notify_ECR_Update
Send Notify_ECR_canceled
Receive Notify_ECR_cancel
ed
Notify _ECR_canceledXOR
ECR Canceled
XORSelect Notification
List & Send Notify_ECR_Rolled_
back_to_Analysis
Notify_ECR_Rolled_back_to_AnalysisAND
Recieve Notify_ECR_Rolled_
back_to_Analysis
Rollback to Analysis
InterfaceParticipant
Distribution ListComment Performer
External Approval Performer
Analysis Performer
Requestor
PartnerCoordinator
Request Receiver ECR Creator Decision Team Change Team
STEP 1 – Modeling Roles, Information Objects and ProcessesSTEP 1 – Modeling Roles, Information Objects and Processes with Event-Driven Process Chains (EPCs) 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.
(m) mandatory(o) optional(e) extension(na) not applicable
1126.02.-02.03.2007 KiVS
STEP 3 – Prototypical Implementation Using BEA Web LogicSTEP 3 – Prototypical Implementation Using BEA Web Logic
Public Interface of Business (Web-)Service
Private (Web-)Services
Orchestration ofPrivate (Web-)Services
triggered by the Public Business Service
1226.02.-02.03.2007 KiVS
CONCLUSIONCONCLUSION
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
1326.02.-02.03.2007 KiVS
OUTLOOKOUTLOOK
Transformation of models Mapping EPC business process models to Business Process
Execution Language (BPEL) Using meta models and markers to automate the transformation
Organization AOrganization A Organization BOrganization B
Inter-Organizational Business Process
PrivateProcess A
PrivateProcess B
Service-OrientedSystem A
Service-OrientedSystem B
PublicProcess
PublicService Interfaces
BusinessServices
BusinessServices
Transforming Inter-Organizational Business ProcessesTransforming Inter-Organizational Business Processesto a Service-Oriented Architectureto a Service-Oriented Architecture
Method 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, Switzerland