Our thoughts are in the form of process, so I proclaim now that we should communicate and articulate them as processes.  procper makes this possible, easy, and fun.  While we are still in stealth mode, contact us to find out how.

Process Visualization

Process visualization can be interpreted as meaning many things, but one tangential reference we find particularly relavent is for “flow visualization”.  As described in Wikipedia, “flow visualization is the art of making flow patterns visible.”  Though this is a term meant for fluid dynamics, the concept is really similar to what we are doing with procper.  By presenting processes in an amazingly intuitive fashion, we are making [work]flow or business process patterns visible.

In turn, individuals and organizations can make better business decisions.  Contact us using the form to your left if you would like to learn more.

BPEL for Process Modeling

Of course, as varied as they may be, there are reasons organizations are succumbing to “BPEL for modeling”. Below I have provided a couple of contributing factors and misconceptions that I have witnessed:

• The budgets for the SOA/BPEL project were requisitioned by IT and they did not plan appropriate time from the business community for process modeling.
• The processes are believed to be “IT processes”, and business process modeling is not needed.
• Processes change, and the cost to maintain both business and BPEL models individually will be high.
• BPEL modeling is “good enough”. Besides, nobody looks at business process models after they are initially designed.
• And the most common: Initially, structured business process modeling was followed, but it was not kept in sync with the BPEL model [for a variety of reasons] and the two diverged.

The list goes on. However, the fact remains that BPEL is a business process execution language, not a modeling language.  Not surprisingly, using it for modeling has serious implications.

• For organizations that did initially set out to perform business process modeling separate from BPEL, only to later diverge, the reality of what is being executed (BPEL) compared to what was agreed/communicated is now also out of sync.  It could be argued that this is worse than never modeling in the first place.  
• For the places that decided to just go ahead and model using BPEL, their models are generally not easily understood by the business, or even people in IT that don’t understand BPEL. They certainly don’t put the organization in the position of easily documenting, updating, and communicating/disseminating process information.
• And for those of you who still think your IT processes do not need to be documented clearly for the business to understand, you will someday.

So, put the BPEL hammer down for a minute, back away from it, and take a look at BPMN and other business process modeling options.  [Sincere Plug] But, if you are stuck with BPEL for modeling processes, procper is the only tool that will allow the business to wrap their arms around the processes you have modeled.  procper is the tool of choice for communicating and disseminating your process  models, regardless of the languages/tools chosen, including BPEL.

The objective of BPMN is to support business process management for both technical users and business users by providing a notation that is intuitive to business users yet able to represent complex process semantics.

Specifically, BPMN sets out to integrate business process with technology by providing an approach that allows for mapping to process execution language like BPEL (Business Process Execution Language).  As technology becomes engrained in every facet of business and as business processes become engrained into technology solutions, BPMN finds itself in a uniquely well-positioned environment.

Future plans for BPMN are to further define this “notation” and turn it into detailed specifications.  This will, of course, help minimize the gaps between the varying  interpretations of BPMN that exist today. Software vendors will have more clarity when conforming to the BPMN standard, allowing for faster development turn-arounds as well as easier and intuitive integration.

Given its unique positioning, existing uptake and momentum, and active continuous improvement, BPMN has a fair number of variables in its favor as it works to become the de facto BPM standard.