Skip to Content

Uncovering the value of collaborative process modeling with SAP StreamWork

Uncovering the value of collaborative process modeling with SAP StreamWork

Most of you may be aware that the collaborative process modeling tool in SAP StreamWork is on public Beta as of late December 2011 and available to everyone who has an SAP StreamWork’s account to use it for free. With this great internal milestone past, I thought I would share some valuable scenarios and use cases where SAP customers (and also non-SAP customers) can get better results when using this collaborative process modeling tool.


What is collaborative process modeling?

Let’s start with a very brief introduction to this new component. The collaborative process modeling tool in SAP StreamWork is a web-based real-time tool for modeling business processes using the BPMN (Business Process Modeling and Notation) standard. It allows people through their browsers to model business processes and instantly share how these processes are created. Furthermore, the additional tools offered by SAP StreamWork (like discussions, tables, file sharing, inviting people to an activity) really strengthen the ad-hoc collaborative nature of this tool.


Where does the collaborative process modeling tool fit in the existing SAP solution eco-system?

The diagram below shows some implicit links with other SAP components.



From this figure it should be clear that the collaborative process modeling tool in SAP StreamWork is complementary to the modeling components from SAP already in existence. It just brings a greater deal of flexibility when it comes to sharing these models with more individuals within an organization.


The objective of this blog is to drill down into some of these implicit interconnections and show where the value is when using collaborative process modeling.


What are the different use cases?

The rest of this blog will concentrate on explaining different scenarios in which collaborative process modeling could be used highlighting benefits for each. The list of use cases follows:

  • SAP Business Suite core business process extensions
  • Green field business process definitions
  • Documentation and feedback repository of business processes 

Let’s walk each one of these cases in more detail.


SAP Business Suite core business process extensions

Some of you may be aware that the recent release of SAP Solution Manager 7.1 distributes a new component named Business Process Blueprinting (also known as BPB). This eclipse desktop-based editor allows connecting to the Solution Composer of SAP Solution Manager, query the Business Process Repository (BPR) and through a reverse engineering process render SAP Business Suite processes in BPMN. For starters, BPB offers the value of a graphical representation of the process, but it also sets up the stage for the baseline core process you want to extend.

Although the extension itself could be done in the BPB editor, it is also possible to use the collaborative process modeling tool for defining the details of these extensions linked to the core business process. Let’s suppose a new approval step is required where there are some complex rules as well as alignment across different stakeholders. This is not something that can be accomplished by a single business analysts mocking up the process. Using the collaborative process modeling tool, we can open a forum where the right stakeholders are invited to collaborate and sign off on what the process should be looking like. All these stakeholders need is a browser to see the actual model process and mark their comments and implement changes in this single source of truth. More importantly this is done instantaneously and live so all other stakeholders can see changes as they are made.

The value in this use case is better alignment across stakeholders and faster agreement on what the process should be looking like. Furthermore, this modeled extension can be linked back to the BPB core business process and also used as the baseline for implementing the extension in SAP NetWeaver Process Orchestration.


Green field business process

We just walked through the case in which the collaborative process modeling tool in SAP StreamWork is used to extend core processes organically using the SAP NetWeaver Process Orchestration solution. This will address a large set of the use cases SAP NetWeaver Process Orchestration is used for, but there are also other situations in which completely new processes need to be orchestrated.

Typically, these green field business processes go through an initial phase of requirements discovery, definition and alignment across different stakeholders. Traditionally, this has been done by IT leveraging SAP NetWeaver Developer Studio desktop-based BPM editors. This modeler really shows its value within the IT and development real, but something more flexible, lightweight and easier to use is required by non-techie savvies. This is where the tool for collaborative process modeling comes to the rescue.

The collaborative process modeling tool allows business analysts and less technical individuals to create a collaboration forum to document and discover the requirements for a business process to be implemented. The previously mentioned capabilities are met because the collaborative process modeling tool in SAP StreamWork:

  • Allows modeling business processes using a consistent standard: BPMN. This enables and enforces a notation consistency across modeling efforts across the organization.
  • Allows non-technical individuals to model business processes (a simplified BPMN palette is offered with the necessary core) fulfilling on the friendly and ease of use requirements.
  • Is lightweight since you just need a browser. Not even a plug-in need to be installed.
  • Offers a central place to collaboratively work on business processes benefiting from capabilities like instantaneous rendering of what others are doing on their browsers.
  • You can enjoy all the SAP StreamWork’s collaboration tools to make a decision is a particular business process needs to be implemented. If the decision is to implement the business process, this can be exported and imported into SAP NetWeaver Developer Studio to augment the process definition with the appropriate execution details.


The value in this use case comes from involving the business community early on and generating alignment early in the requirements phase. More importantly, the output of this exercise becomes the contract of what needs to be implemented by IT. This implicitly minimizes disconnects due to miss-understanding and miss-communication.


Documentation and Feedback repository of business processes 

The previous two use cases help organization speed up their business process discovery process as well as generating better alignment of business and IT than other traditional methods. This in itself would be enough value for a solution to exist.

However, there is also lot of value to uncover and explore when using the collaborative process modeling tool in SAP StreamWork as an easy to access repository of business processes. We mentioned that it is possible to export business processes from thetool into SAP NetWeaver Developer Studio, but the counterpart import action is possible as well. This opens the door to sharing business processes to the user community for general awareness and documentation purposes. More importantly, it opens a rich feedback channel for end users and process owners to collaborate. As SAP StreamWork activities allow inviting any person registered on it, this could be used internally within an organization as well as with an external audience.

In this context, there is a great potential of using the collaborative process modeling tool for a more open governance process. Sky is pretty much the limit.




The value in this use case is better transparency as to how business processes work in an organization. It also opens the door for a very dynamic feedback channel shared across the interested community. Good and best practices can be documented in a central place and real-time. All interested parties (including newcomers) would benefit from general shared knowledge rather than locking tribal knowledge.



I personally hope you feel encouraged by the tremendous potential of using collaborative process modeling in all these different scenarios and use cases. At SAP we believe there is more value still to uncover by leveraging the collaborative process modeling tool in SAP StreamWork as outlined on this blog. If you have some personal experience in any of these use cases or others, we would love to hear about them.

You must be Logged on to comment or reply to a post.
    • Fabio,
          You are most welcome. I personally believe there are many other use cases where collaboration at the process modeling level could help. Specially when aligning understanding in a more ad-hoc and unstructure collaboration way. Specially these days when people works in many cases remotely, this type of technology would definitively help !


  • Hi Eduardo,

    Great blog, really like where SAP is heading with this integrated approach on procesmodelling and collaboration. Is there however a (planned) integration between BPB and NWDS? I would imagine BPB being the single source of truth for both the collaborative business to model  level or phase as you will (Streamwork) as well as model to execute level (NWDS). You mention the integration between Streamwork and NWDS for (re)documentation purposes, but i believe these tools both support a own lifecycle for processes without a real process repository, where as BPB could support the whole lifecycle and actually has a process repository to support that. What's your opinion on that?

    • Hi Jeroen,
          Thanks for your comments and questions. This blog was posted to generate this dialog and I personally appreciate your comments on this. Generally speaking, we are striving to have a strategy with a single source of truth and part of this is already materializing as you say when BPM is connected with BPB. As of today with Generally available versions, you have a dedicated BPB editor and then you can consume these assets later on from NWDS (using the Solution Manager integration). In NW Process Orchestration 7.31 (or 7.3 EHP1), the BPB eclipse plugins will be included in NWDS so you would not necessarily need to use 2 different editors. We are aggregating everything under the NWDS umbrella.
          Moving forward we want to eliminate the need to export/import from StreamWork and leverage a central repository where all these assets are connected so the collaboration is better coordinated, synchronized and assets are more naturally transitioned through the lifecycle. Expect some news on this front in the near/mid term future. Using BPR as the single source of truth is one of the options we are analyzing, but we also recognized that this may be narrowing our solution as instead we could still connect all these different repositories and federate a view that connects all this processes together.
          Bottom line, we look forward to make the interaction and collaboration amongst all these 3 components more seamless, eliminate hurdles and provide consistency regardless of the editor or choice.
          Hope this clears out some of the questions you had.


  • Hi Eduardo,

    Thanks for this blog, it helps to have some example use cases to consider. While reading it I saw an analogy with photo sharing. A few years ago photo sharing websites came up where you could publish a static set of pictures for a selected community to view. Generally commenting and discussing the photos was not easy. Nowadays however many people share photos via Facebook with all the possibilities this has for liking, commenting, tagging, making suggestions and having a much more dynamic experience. For me this is similar to process modeling tools in the past that were specialist in nature, focused only on the pure modeling and difficult to share with users. It looks like this component integrated with Streamwork is a big step to finally getting collaborative modeling out into the open where it can become much more of a dynamic "natural" process for the business and IT to work together on. The reverse integration from Streamwork back into the NW toolset for actually creating the code objects is the icing on the cake.

    Looking forward to seeing how this evolves.



    • Thanks Marcus. I think the analogy makes perfect sense. In the past, things used to follow a more rigorous model and now things are more open and collaborative in nature. Needless to say that the times are shrinking every day. So you need a mode dynamic platform and StreamWork definitively offers this. Glad you like our story. We'll keep bringing more and more of these to our customer base.