I look upon case management as more of a project management function, primarily in the area of planning. Allow me to explain. In our Enterprise Engineering Methodology (EEM), we had the ability to model the business logically and physically, thereby giving us the ability to do such things as performing an organization analysis and priority modeling. The latter being a prioritized listing of the enterprise's business objectives and their supporting projects. If the business changed, we could automatically recalculate the company's priorities (not to mention play "what if").
At the heart of our software was a Repository which housed all of the components about an organization, including business, systems, and data resources. As Jim Sinur will remember, we had the ability to perform an "impact analysis" on any information resource, be it a business component, systems or software, or data resources. By doing so, we could determine the effect of change on any component and prepare a more precise plan for implementing it.
For example, if the enterprise were to reorganize a part of a business, the Repository would list all of the people and machine resources involved, projects affected, systems, and data. Conversely, if we wished to change a data element, the Repository would list all of the records, files, inputs, outputs involved, not to mention programs and much more.
The intent of the Repository is to reduce redundancy of information resources and promote sharing. I cannot image simulation of any kind without such a tool.