Approach for Inter Organisational BPM

Question

Hi All,
I am doing Masters Dissertation in Collaborative BPM. My research topic is the evaluation of three approached for collaborating BPM across value chain.
Explanation of these approaches:
Centralise CBPM: Ownership of Collaborative System is with one Central Organisation and Other Partners Participate in this collaboration through various UI such as portal. Example, Collaboration between the automobile manufacturer and dealer were automobile manufacturer provides portal for dealer to place order, manage its customer and handle warranty and recalls.
Decentralise CBPM: In this approach every partner provides communication technology like Web Services for its Business Partner for collaboration. The ownership is decentralise and more flexible
Peer-to-Peer CBPM: In ideal condition in this approach every Partner should have the same technology which is developed for handling collaborative Business Processes. In this case the same modelling facility is available across the value chain.
I found below critical aspects for evaluating these three approaches:
1] Autonomy
2] Collaborative process Modelling
3] Monitoring, Controlling, and Analysis
4] “Plug and Play” based Platform for Collaboration (Includes Security, Web Service and various adapters for communication and Language Support like Java for easy custom enhancement)
5] Governance
I kindly request you all to post your views about pros and cons for evaluating these approaches from the aforementioned critical aspects.
I welcome your questions and appreciate your valuable guidance.
Thank you ,
Regards,
Ganesh Sawant

Answer 1

PROS:
Using the Webservices you can trigger the BPM Process and pass the values from the web dypro component which will available for the end user and pass it on to the BPM Proess.
We can use EJB as a webservice, where the automated activity in the BPM can output the value based on the logic in the EJB Function. We can manage the automated activity which runs in the back ground of the process as per our logic and returns the value to the next task.
CONS
Using Webservices in the various activity with fewer data is not advisable as it takes longer time to deploy the process. And any change in the data in the webservices requires regularly re importing of the web services.