christine legner 1 , tobias vogel 1 , jan löhe 2 , christian mayerl 2
DESCRIPTION
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 PresentationTRANSCRIPT
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
[email protected], [email protected]
2 Universität Karlsruhe (TH), Institute of Telematics, Cooperation & ManagementP.O. Box 6980, 76128 Karlsruhe, Germany
226.02.-02.03.2007 KiVS
OVERVIEWOVERVIEW
Introduction
Background
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.)
Scenario Engineering Change Management – VDA 4965 ECM, OMG PLM Services
Constraints Process modeling with Event-Driven Process Chains (EPCs)
Advancing Business Networking
SOA For Automotive
SOA For Automotive
Advancing Business Networking
SOA For Automotive
SOA For Automotive
526.02.-02.03.2007 KiVS
Public Process Different process
variants
Process Interfaces Including functional and
non-functional description
Information Objects Engineering Change
Request
Messages Assembled by
information objects
Organization AOrganization A Organization BOrganization B
STEP 1 – Modeling Inter-Organizational Processes (Public View)STEP 1 – Modeling Inter-Organizational Processes (Public View)
Private Process A Private Process B
Public Process
Roles
Information Objects
Public Process
Co
mp
uta
tio
nal
Ind
epen
den
t M
od
el
VDA ECM Recommendation 4965
Roles Organizational
Coordinator, Participant Functional
626.02.-02.03.2007 KiVS
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
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.
Send Request_Comments
Receive Request_Comments
Request_ECR_Comment
Send Request_Comments
Receive Request_Comments
ECR_ID
Request_comments
ECR_HEADER
ECR_STATUS
ECR_GENERAL_
DETAIL
ECR_COMMENT(optional)
ECR_SPECIFIC_
DETAIL (optional)
Change Team Comment Performer
Nicht-funktionale Schnittstellenbeschreibung
Qualität – Ziel:Aufforderung zur Stellungnahme
Zeit – Deadline: dd.mm.yy hh:mm
Zeit – Projekttermin:dd.mm.yy – dd.mm.yy
Kosten – Prozesskostensatz:0.50
Flexibilität – bilaterale Erweiterung:MessageUser_definedPart
Flexibilitat – Fehlerbehandlung:Inform ECR Manager
Send Request_Comments
Receive Request_Comments
Request_ECR_Comment
Send Request_Comments
Receive Request_Comments
ECR_ID
Request_comments
ECR_HEADER
ECR_STATUS
ECR_GENERAL_
DETAIL
ECR_COMMENT(optional)
ECR_SPECIFIC_
DETAIL (optional)
Change Team Comment Performer
Nicht-funktionale Schnittstellenbeschreibung
Qualität – Ziel:Aufforderung zur Stellungnahme
Zeit – Deadline: dd.mm.yy hh:mm
Zeit – Projekttermin:dd.mm.yy – dd.mm.yy
Kosten – Prozesskostensatz:0.50
Flexibilität – bilaterale Erweiterung:MessageUser_definedPart
Flexibilitat – Fehlerbehandlung:Inform ECR Manager
726.02.-02.03.2007 KiVS
ManufacturerManufacturer SupplierSupplier
STEP 2 – Aligning Private to Public ProcessesSTEP 2 – Aligning Private to Public Processes
Modeling individual private processes
Mapping private to public process model
Defining synchronization points (Milestones)
Private Process A Private Process BPublic Process
Roles
Information Objects
Public Process
PrivateRoles
PrivateInformation Objects
Private Processes
PrivateRoles
PrivateInformation objects
Private Processes
Co
mp
uta
tio
nal
Ind
epen
den
t M
od
el
826.02.-02.03.2007 KiVS
STEP 2 – Synchronizing Private and Public Processes at MilestonesSTEP 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.
Inquiry of ECR
Creation of ECR
Technical Analysis
Commenting on ECR
Approval of ECR
Change Requested/
Setup Engineering Change Request
Grunddaten anlegen
Change Evalutation / Impact, check and approve feasibility
Change Approval
M3: Potential Solution identified
M3.1: Decision for ECR
M3.2: ECR Created
M3.3: ECR Detailed
M3.4: ECR Commented
M4: ECR Decided
ChM1M1
ChM3M3
ChM2M2
VDA
Org. 3
926.02.-02.03.2007 KiVS
Organization BOrganization BOrganization AOrganization A
Service-OrientedSystem A
Service-OrientedSystem B
Public Service Interface
STEP 3 – Developing Business ServicesSTEP 3 – Developing Business Services
Mapping public processes to business services and messages
Private Process A Private Process BPublic Process
Co
mp
uta
tio
nal
Ind
epen
den
t M
od
elP
latf
orm
Ind
epen
den
t M
od
el
ApplicationService
BusinessService
Taskflow
Workflow
Information Objects
PrivateInformation Objects
PrivateInformation Objects
Public Process
Private Processes
Private Processes
ApplicationService
BusinessService
Taskflow
Workflow
<XML Schema> <xs:element …/> <xs:element …/></XML Schema>
<WSDL> <WSDL:message> <WSDL:portType> <WSDL:binding></WSDL>
Messages
BusinessService
1026.02.-02.03.2007 KiVS
STEP 3 – Transforming Model Artifacts to SOA ArtifactsSTEP 3 – Transforming Model Artifacts to SOA Artifacts
Mapping information objects to messages
Describing business services with WSDL
Messages Info
rmat
ion
Ob
ject
s
BusinessServiceInterface
<WSDL> <WSDL:types> <WSDL:message> <WSDL:operation> <WSDL:interface> <WSDL:service></WSDL>
(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
[email protected], [email protected]
2 Universität Karlsruhe (TH), Institute of Telematics, Cooperation & ManagementP.O. Box 6980, 76128 Karlsruhe, Germany