Ah yes, it's BPM... but which BPM is it?
Arch BPM blogger-cum-analyst Sandy Kemsley
references an interesting conversation she had with some webMethods customers at Software AG's Integration World event where the customers "pooh pooh the BPM vendors who don't provide the whole integration stack". To me, this is interesting because (as Sandy calls out) "these customers are coming from the traditional EAI-type usage of webMethods".
One of the challenges in the growing market for Business Process Management (BPM) technology is the fact that there are many different technology providers bringing tools to the market, and each has its own technology background and heritage customer set with its own expectations. In truth, there isn't "one BPM".
What makes things particularly challenging is that it's very difficult to find a vendor that can truly support a rich range of different types of processes from the perspective of modelling, analysis and optimisation; while at the same time supporting complicated integration requirements. The task is particularly difficult if you're looking for an elegant technology solution with no duplication (some vendors can point to good coverage of all the main functional requirements today, but they can only do this by bundling overlapping and poorly-integrated products and technologies together).
It's a bit of a simplification, but broadly speaking, vendors fall into a "business process specialist" camp, where sophisticated modelling, monitoring and optimisation tools are provided; or a "process integration" specialist camp, where the main centre of gravity is being able to orchestrate services and applications in relatively sophisticated ways. The smaller, specialist vendors (such as Lombardi, Pegasystems, Singularity, Appian) fall into the former camp; the larger, generalist vendors (such as IBM, Software AG, TIBCO, Oracle) fall into the latter camp.
Next spring we'll be launching a major research programme looking at the discipline of BPM and the technology you need to support it - but until then the most pithy advice I think that can be given to an organisation looking to purchase BPM technology is:
Understand what, exactly, you want to do with BPM. Understand the key characteristics of the processes you're trying to improve, and equally importantly, who's driving the work - is it business people, IT people or both?Unfortunately, getting to the bottom of things is not as simple as saying "I need a human-centric BPMS" or "I need an integration-centric BPMS".
UPDATE: Some folks from BEA got in touch, and asked "why isn't BPM in your list"? I had no idea I was so influential! ;-) So, for the record... BEA is an interesting BPM vendor, as it has some integration-focused history with its WebLogic Integration capabilities, but it's garnered a much more interesting position by buying former BPM specialist Fuego. It now straddles both camps - as, strictly speaking, does TIBCO (following its acquisition of Staffware).
To make things fair, I should perhaps call out some other vendors not mentioned in the original list above: Adobe, Cordys, DST, EMC Documentum, Fujitsu Software, Global 360, Handysoft, Intalio, K2, MEGA, Metastorm, Microsoft, Proforma, SAP, Savvion, Ultimus, Vitria...
Labels: BPM
