In my last article (www.ariscommunity.com/users/frank-weyand/2009-08-14-bpm-tool-future-how-should-it-look) I discussed the extension of a BPM tool with functionality for "daily work", so the frontiers between BPM tools for documentation and tools providing ERP functionality vanish.
So, furthermore, I name it "BPM platform".
If we've got a BPM platform providing the possibility not only to document processes but also to execute them (by programming or modelling executable processes), the next logical question is: who will provide new processes for the platform?
Rising of a new market?
At this point, there could be a whole new market for the BPM platform. Logically, the "owner" of the running instance is able to do the implementation of new processes concerning his/her own needs. In addition, there will be a market for BPM experts and consultants to help the customer to do so.
But, equivalently to software development, this would be individual "development" (well, not software, but processes). But also, equivalently, since there exist "standard software", why couldn't be there also "standard processes"
Standard processes - best practices, executable on your BPM platform
Let's say, BPM experts develop a whole business scenario using the BPM platform. Using the features of the platform for testing and analyzing, these processes can be simulated, calculated, tested and quality approved.
And then - sold. So it is not standard software, but standard processes developed by BPM experts and - by continuous improvement - be best practices.
Why "plugins"?
In the headline, I wrote "Process plugins". I liked to use the term "plugins" because that describes it IMHO perfectly: you've got a system running, and you can add additional business scenarios like plugins. You buy them, you import/install/deploy them and you can run them. That's it.
So, like it is quite usual in the ERP market, it can also be possible to have such a market growing for a BPM platform. I think, we can be quite curious what future will bring for the BPM market.
