Mea Culpa – yes, like others in this space, the challenge is keeping the blog going. Usual story of not managing to keep the clones working properly while I am sleeping. Lots of things to start sharing here … and now that I am out from under the endless train of deliverables and trainign courses, I should be able to find the odd bit of time.
The reason for this long awaited posting … I felt I wanted to pick up on discussions emerging in the BPM space – driven by Henk de Man’s presentation at the OMG meeting last week. He was talking to the need for better modeling approaches to support Case Handling (or Case Management depending on your perspective).
Like James Taylor (name now corrected), I thought Henk’s presentation was also interesting. And as I pointed out during the session, a great many processes should be viewed in the Case Handling context. Readers might also be interested in the papers I produced that discuss these sorts of issues. But really getting at it from the pov of the Customer and Processes – “Business Processes and Customers – Difficult Domains to Integrate” available in the White Papers section of the BPM Focus web site.
The core of Henk’s presentation was that BPMN style modeling is not much help when trying to capture the essence of Case Handling. His own product has a strong Case Handling orientation and uses “States” and “Events” to enable some of the flexibility that Case Handling apps demand. In my experience, the key differentiating factor (between a tranditional workflow/BPMS app and Case Handling) is that the emphasis is with Case – it may have many processes and documents associated with it.
I suggested to him that he investigate Role Activity Diagrams (a way of modeling at how the Roles involved change state as a result of the actions and interactions that occur). This is perhaps much more appropriate for the state based view he was hankering after. The best reference on this is Martyn Ould’s book “Business Process Management – A Rigorous Approach”
But all should understand that Case Handling approaches have been around for a very long time. They are everywhere you look once you get it in your head. Think of these:
- Government – State and local government, NGOs, Police, Justice (investigations), Land mgt …
- Financial Services
- Insurance – Every claim is an exception
- Banking – Trade exception handling, premium account management
- Healthcare – From clinical provision to administrative management and payment
- Oil & Gas Exploration- Knowledge workers spread thinlyaround the world
- Pharmaceuticals – Clinical trials, compound development, marketing campaign management
- Virtually all “professions
- Wide range of Small to Medium sized contexts
- All sort of Procurement situations
- Customer Contact Centers – across virtually all industries, where they validate, identify work items and then resolve … here 80% of all calls are WISMO (What Is the Status of My Order)
- Even the weekly Staff Meeting is a kind of case handling situation if you look at it from a process point of view.
All of them have continually unfolding, evolving scenarios. That is where BPM needs to concentrate its efforts. The transactional space that has characterised efforts to date is really pretty straight forward. Case Handling involves synchronous interaction with users, long running case resolution situations, multiple process fragments, knowledge work, …
Interesting vendors in this space are few and far between. At one level it is big systems implementations such as Cordys, Pega and Graham Technology. But there is a simpler more accessible level that is best characterised by folks like Itensil (in my mind one of the most itneresting I have come across). I am sure, that with care you could implement TIBCO, Appian and Lombardi to build effective Case Handling situations, but it is really a quesiton of adopting the right style of design thinking. And with more and more of these vendors offering SaaS delivery mechanisms, I think we are going to see an ever increasing level of innovation in this area.