Browse Prior Art Database

A method and system for dynamic case management through task pooling mechanism Disclosure Number: IPCOM000244672D
Publication Date: 2016-Jan-06
Document File: 6 page(s) / 123K

Publishing Venue

The Prior Art Database


A method and system for dynamic case management through task pooling mechanism

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 39% of the total text.

Page 01 of 6

A method and system for dynamic case management through task pooling mechanism

Adaptive or Advanced Case Management (ACM), is a method of automating and streamlining of case processing both formalized and ad-hoc. It helps your business to more effectively and efficiently create or open cases, monitor their progress, drive cases to completion, and gain insight for decision, risk, and productivity management. Advanced case management is more than BPM (Business Process Management) or Content Management; the best of ACM is that it is a combination of both these practices optimized for people-driven processes. ACM works on an ad-hoc basis to manage dynamic, unstructured processes. ACM can be especially effective for companies handling "untamed" business processes that lack structure. ACM's ultimate goal is helping such workers make faster, better and more accurate decisions.

A solution in any given Case Management system is designed by creating a set of solution parameters, a set of Case Types and a set of Tasks within those Case Types. Tasks are the logical units of work. If the same Task is required in another Case Type, it (Task) needs to be redefined. Multiple definitions of the same Task will present in multiple places and these tasks are tightly coupled with Case Types in the solution. All the Tasks within the Case Type need to be designed at the design time of the Case Type itself.

Therefore, in the present case management system, as a Task needs to be linked with case type at design time, there is not an option to create an ad-hoc case dynamically with a set of tasks already present in the system.

Example-1 (Re-usability : Only one copy of Task definition across multiple case types): Let's assume 'Address Verification' task is designed & added to a 'Loan issuance' Case Type and the same task is also designed & added to 'Credit Card Issuance' Case Type. If there are changes in the process of address verification, this task ('Address Verification') needs to be updated. Though it is the same task, having


Page 02 of 6

multiple definitions in different Case Types across different solutions in the domain, Administrator has to update in both the definitions individually which is tedious being manual and also error prone.

Example-2 (Dynamic Case Management requiring addition or deletion of Tasks at run-time): Let's assume a set of customers applied for a bank loan which takes a week time in general for all the verifications and approvals. Case worker launched an instance for each case, now the loan process is in progress. In the meantime, Bank regulations came up with a new extra mandatory verification/check that needs to be done for all the customers who are applying for the loans. In the current case management system, there is no way to add a new task to the running case instances as the task is tightly coupled with Case.

Example-3 (Dynamic case creation with a set of tasks):

Let's assume a high value credit card customer is offe...