So I missed the document last year from Forrester titled “Smart Process Applications Fill A Big Business Gap” but I have just read the Forrester Wave for Smart Process Apps. My overriding impression is one of the creation of another solution paradigm to confuse an already crowded marketplace. It is not that long ago that I blogged about the difference between ACM and DCM, just over two years to be precise, and the interesting thing is that the technology world in this space has evolved a little during that time but there certainly has not been change enough to warrant the creation of yet another term. I will go back to the document from August 2012 which passed me by but some of the content is reproduced in the Wave and I want to focus on the Key Attributes of a Smart Process App:
1. Imported or embedded awareness of data relevant to the business activity. So what we are saying here is that there must be data associated with the business activity which is captured at some stage of the business process, right? Anything new here?
2. Document capture, document output, and document management. So these are the basic capture, manage and output stages of Document Management.
3. Embedded analytical tools designed for the business activity. So this will provide the reporting and data analytics on the specific business activity which has been created.
4. A collaboration platform for people to create content needed for the activity. An interesting pattern here as it deviates a little from the first three which are slightly more prescriptive. This is much less predictable and much more aligned with the Adaptive Case Management pattern which I have previously described. A good example of a solution incorporating a collaboration platform could be Grants Management where the Grant application would be subjected to a number of reviews where the reviewers provide a number of comments and share opinions on the Grant application.
5. BPM tools for executing the steps involved in the activity. This would involve classic BPM including workflow, tasking and potentially a rules engine.
I look back at the posts on ACM and DCM, which were already addressing a confused market and review the features above and there is very little difference. In fact some of the products which address the DCM or ACM market will be the same for the Smart Process Apps, typically the likes of EMC, OpenText, Kofax and IBM.
One of the comments in a previous post was:
My advice, don’t implement based on the label. Understand what you’re trying to achieve and assess the solutions and options which are available to you. Its not rocket science!
I don’t see any difference here. You need to understand the core business and technical capabilities which you need to address and evaluate the products which can help you achieve those. It is true that it is not rocket science but the sheer number of players in this space means it is getting harder as there is convergence. Two years ago we would not have been comparing Salesforce.com and EMC as players in this space but the products are moving closer. The one thing I would recommend, and it is something I will comment on more, is the growth of already built applications or accelerators within the products. Companies such as IBM and EMC are adding an increasing number of solutions to their portfolio, addressing problem domains in multiple industries such as Life Sciences and Energy and Utilities. These solutions provide much more predictable results for customers and the solution providers themselves.
So while there is a lot in the report which is confusing and repeated from previous reports there is an underlying message which is important and which is driving change in this area of technology. Solutions and Solution Accelerators are increasing, call them Case Management or Smart Process Apps, and there is an increasing amount of choice in the market. Ultimately this can only be a good thing for consumers and we should see an increase in successful projects based on these technologies as a result.