- BPM is defined as the overall management philosophy, which frames the enterprise as consisting of a set of end-to-end business processes. These processes, in combination, deliver value to the organisation's clients. Improving the enterprise means architecting, improving, and managing these processes for better outcomes.
- BPMS is a collection of software tools and systems engineering practices based on process management thinking. BPMS realises the modelling, automation, execution, and monitoring of business processes on a common, single-instance runtime platform, often through the use of open, well-defined service contracts (such as web services).
Some vendors equate workflow tools to BPMS, which is not necessarily the case. An enterprise BPMS often involves implementing a workflow. However, the key notion is that modelling and executing business transactions as processes yields predictability and transparency.
My work has inspired me to pursue writing a pracademic paper on common quality criteria and heuristics for enterprise BPMS implementations, particularly concerning roles, values, expected outcomes, actual outcomes, pitfalls, and general performance improvements. What worked and why? What didn't work out as expected? What business criteria should the CIO and solution architect focus on when planning or building the business case for BPMS? How did can one ensure a higher quality BPMS?
Granted, several IT governance frameworks already provide generic measures and KPI's. What I am interested in is the process- and IS-specific criteria and measures relating directly to BPMS programs.