Transcript Transforming Cross-Organizational Business Processes to Service

Transforming Inter-Organizational Business Processes
to a Service-Oriented Architecture
Method and Application in the Automotive Industry
Christine Legner1, Tobias Vogel1, Jan Löhe2, Christian Mayerl2
1
2
University of St. Gallen, Institute of Information Management
Müller-Friedberg-Straße 8, 9000 St. Gallen, Switzerland
[email protected], [email protected]
Universität Karlsruhe (TH), Institute of Telematics, Cooperation & Management
P.O. Box 6980, 76128 Karlsruhe, Germany
[email protected], [email protected]
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
26.02.-02.03.2007 KiVS
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
 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?
26.02.-02.03.2007 KiVS
3
BACKGROUND – “SOA For Automotive” Project
SOA
For
For Automotive
Automotive
Advancing Business Networking
 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)
26.02.-02.03.2007 KiVS
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

Private Process B
Roles


Organizational
Coordinator, Participant
Functional

Information Objects


26.02.-02.03.2007 KiVS
Assembled by
information objects
Public Process

Engineering Change
Request
Messages



Different process
variants
Process Interfaces

Including functional and
non-functional
description
5
STEP 1 – Modeling Roles, Information Objects and Processes
with Event-Driven Process Chains (EPCs)
Phase
Coordinator
Request Receiver
Participant
Interface
Request_ECR_
Comment
Send
Request_Comments
Decision Team
ECR Creator
Change Team
Requestor
Analysis
Performer
Partner
Receive Request_
External
Comment
Comments
Approval
Performer
Distribution List
Performer
M3.2 ECR Created
Request_
XOR
comments
Rollback to Analysis
Technical Analysis of ECR
Prepare ECR
For Analysis
Nicht-funktionale
Schnittstellenbeschreibung
XOR
ECR_ID
Send Request_Details
Send
Request_Comments
ECR_HEADE
R
Receive
Respond_Details
Respond_Details
ECR_STATU
S
ECR_
Select Notfication
GENERAL_
List & Send
Notify_ECR_Update
DETAIL
Notify_ECR_Update
XOR
Select Notification
AND
XOR
Rollback to
Analysis



ECR_
COMMENT
M 3.3 ECR Detailed
(optional)
Notify_ECR_Rolled_
back_to_Analysis
Notify
_ECR_canceled
Zeit – Projekttermin:
dd.mm.yy – dd.mm.yy
Kosten – Prozesskostensatz:
0.50
Flexibilität – bilaterale
Erweiterung:
MessageUser_definedPart
Flexibilitat – Fehlerbehandlung:
Inform ECR Manager
Recieve
Notify_ECR_Update
Recieve
Notify_ECR_Rolled_
back_to_Analysis
Receive
Notify_ECR_cancel
ed
ECR Canceled
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

26.02.-02.03.2007 KiVS
List & Send
ECR_
Notify_ECR_Rolled_
back_to_Analysis
SPECIFIC_
DETAIL
Send
(optional)
Notify_ECR_canceled
Analyse Affected
Objects
Zeit – Deadline:
dd.mm.yy hh:mm
Send
Respond_Details
Comment
Performer
Consolidate Technical
Analysis
OR
Receive
Request_Details
Receive Request_
Comments
XOR
Change Team
Qualität – Ziel:
Aufforderung zur Stellungnahme
Request_Details
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
Roles
Private
Roles
Private
Information
objects
Information
Objects
Private
Information
Objects
Private
Processes
Public
Process
Private
Processes
Manufacturer
Supplier
 Modeling individual private processes
 Mapping private to public process model
 Defining synchronization points (Milestones)
26.02.-02.03.2007 KiVS
7
STEP 2 – Synchronizing Private and Public Processes at Milestones
Publ.
Priv.
Publ.
Priv.
Publ.
Priv.
26.02.-02.03.2007 KiVS
 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)
8
Computational
Independent Model
STEP 3 – Developing Business Services
Private Process A
Private Process B
Private
Information
Objects
Information
Objects
Private
Information
Objects
Private
Processes
Public
Process
Private
Processes
Service-Oriented
System A
Platform
Independent Model
Public Process
Taskflow
Public Service
Interface
Messages
Workflow
Business
Service
Application
Service
Organization A
Business
Service
<XML Schema>
<xs:element …/>
<xs:element …/>
</XML Schema>
<WSDL>
<WSDL:message>
<WSDL:portType>
<WSDL:binding>
</WSDL>
Service-Oriented
System B
Taskflow
Workflow
Business
Service
Application
Service
Organization B
 Mapping public processes to business services and messages
26.02.-02.03.2007 KiVS
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
 Mapping information objects to messages
 Describing business services with WSDL
26.02.-02.03.2007 KiVS
10
STEP 3 – Prototypical Implementation Using BEA Web Logic
Orchestration of
Private (Web-)Services
triggeredPublic
by theInterface
Business
(Web-)Service
Public of
Business
Service
26.02.-02.03.2007 KiVS
Private
(Web-)Services
11
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

26.02.-02.03.2007 KiVS
Standardized Web service technologies
12
OUTLOOK
Inter-Organizational Business Process
Private
Process A
Public
Process
Business
Services
Service-Oriented
System A
Private
Process B
Business
Services
Public
Service Interfaces
Organization A
Service-Oriented
System B
Organization B
 Transformation of models
 Mapping EPC business process models to Business Process
Execution Language (BPEL)
 Using meta models and markers to automate the transformation
26.02.-02.03.2007 KiVS
13
Transforming Inter-Organizational Business Processes
to a Service-Oriented Architecture
Method and Application in the Automotive Industry
Christine Legner1, Tobias Vogel1, Jan Löhe2, Christian Mayerl2
1
2
University of St. Gallen, Institute of Information Management
Müller-Friedberg-Straße 8, 9000 St. Gallen, Switzerland
[email protected], [email protected]
Universität Karlsruhe (TH), Institute of Telematics, Cooperation & Management
P.O. Box 6980, 76128 Karlsruhe, Germany
[email protected], [email protected]