Public Description (Wiki Format)
Adaptive Case Management (ACM) is information technology that exposes structured and unstructured business information (business data and content) and allows structured (business) and unstructured (social) organizations to execute work (routine and emergent processes) in a secure but transparent manner.
ACM involves three distinctive paradigm shifts:
1. ACM is a productive system that deploys not only the organization and process structure but through backend interfaces becomes the system of record for the business data entities and content involved. All processes are completely transparent as per access authorization and fully auditable.
2. ACM enables non-technical business users in virtual organizations to seamlessly create/consolidate processes from business entities, content, social interactions, and business rules. ACM can be unstructured or strict.
3. ACM moves the process knowledge gathering in the life cycle from the template analysis/modeling/simulation phase into the process execution. The ACM system collects actionable knowledge (no discussion necessary how) based on process patterns created by business users.
For a complete description of Adaptive Case Management, please refere to the book Mastering the Unpredictable .

What is the difference between Adaptive Case Management (ACM), and Busienss Process Management (BPM)?
Abstract: ACM and BPM
Business process management approaches the problem of improving the work of an organization from a strongly process centric point of view. The first thing you think about is the process. In a certain way, it is the process which defines whether two instances are similar or not.
Data flow into and out from the process. The process represent the goal of a particular sequence of actions, but that goal is not itself an information resource. the process instance contains process relevant data, as well as application data, but it is generally assumes that that daate is a copy of data that has its source elsewhere. This is the main point about "integration" of the process into other information resources.
BPM might be visualize in this diagram:
ACM also tries to improve the performance of an organization, but instead of considering the process primary, it is the case information that is primary. This information is an information resource, which will be accessed over the length of use, and in many situations will become the official record (system of record) for that work.
There can be processes, but the processes are brought to the case, and run in the context of the case, rather than the other way around.
An ACM system might be envisioned as this:
Both approaches deal with
At a technical level these are similar or even identical. But at a methodological level, how you approach a given problem, they are opposite ends of a spectrum.
In BPM, the process is primary, and so normally the process is predetermined and static, while the data flow through it. With ACM, it is the data that is primary, which tends to remain persistent for a long time, possibly forever, but it is processes which are brought to it. In many cases with ACM the processes are not even fully predefined, but can be defined on the fly.
The net result is that BMS and ACM are useful for different kinds of business situations.