Admin at 13:04, 18 January 2017

2017-01-18T13:04:22Z

Admin: Created page with "{{DISPLAYTITLE:Case Management}} Category:Case_Management"

2016-09-12T08:44:33Z

Created page with "{{DISPLAYTITLE:Case Management}} Category:Case_Management"

New page

{{DISPLAYTITLE:Case Management}}
[[Category:Case_Management]]

← Older revision		Revision as of 13:04, 18 January 2017
Line 1:		Line 1:
−	{{DISPLAYTITLE:Case Management}}	+	{{DISPLAYTITLE: Case Management Modelling and Notation - A how to guide on the new OMG standard}}
−	[[Category:~~Case_Management~~]]	+	== Case Management ==
		+	Case management is not about making processes more flexible; it is about empowering the workers by providing them with access to all the information about the case and giving them the discretion to plan the case execution, and decide which tasks to execute for a particular case instance.
		+
		+	In a BPM system the process designer encode the business goal to be accomplished in the model of the process; therefore the workers executing activities in the process do not need to be aware of the business goal. In a case management system, in the other hand, the case worker is in control of the business goal. In BPM, the system is responsible to accomplish the business goal and uses workers to achieve that goal. In a case management system, the workers are responsible for the business goal and use the system as a tool to accomplish that goal. Case management relies more in the worker's judgment than in control flow.
		+
		+	On its introduction to case handling, Aalst et al. describe four problems of the workflow approach that also applies to BPM. These problems describe how the workflow system constraint the workers, and relegate data to a secondary concern.
		+
		+	<em>The four problems are:</em>
		+	*The work is straight-jacketed into activities. Everything that does work in a process is modeled by an activity restricting the workers flexibility.
		+	*Routing is used for both distribution and authorization; therefore workers can only access the work and data they are assigned to do and nothing else.
		+	*Introduce context tunneling by focusing on the control flow and relegating data to a secondary concern.
		+	*Focus is on what should be done instead of what can be done, creating inflexible processes.
		+
		+	Case management and in particular CMMN solve those problems by formalizing the concept of a case file that contains case data. Data is more important than control flow, and therefore the state of a case dependent more on the case data state than on the control flow state. In most instances, case data is represented by documents, because workers commonly interact by using documents like spreadsheets, presentations, word processor documents, voice recordings, videos, pictures, etc.
		+
		+	Therefore, in most situations the case data will be documents that are used by the workers to accomplish their business goal. In CMMN case data can be mapped to documents and folders via the Content Management Interoperability Services (CMIS) . Although, CMIS is not required for a CMMN implementation, the use of a content management system is useful to support knowledge workers.
		+
		+	The focus on knowledge workers is an important component of a case management system. The ability to add, modify, or remove data from a case file at any time during the process is a key feature of a case management system. This introduces the need to provide collaboration technology like groupware as part of the case management runtime. Although CMMN does not prescribe the runtime environment, collaboration technology is useful to support knowledge workers.
		+
		+	<u>The four problems described by Aalst et al.4 are addressed in CMMN as follows:</u>
		+	*Not all the work that happens in a case is modeled. In particular the interaction of workers with the case file and case data may not be modeled, or be partially modeled. In most situations, we don’t model how the data gets into the case. This solves the straight-jacketed into activities problem of BPM. Case data can be added, removed, modified by the case workers at any time during the processing of a case without the need of an activity.
		+	*Work distribution is independent from authorization; therefore case workers can be authorized to access the case file and its data even when they don't have work assigned. Case workers can search for cases they are assigned to, and they can interact with the data contained in that case file. This solves the routing is used for both distribution and authorization problem, and introduces the requirement for collaboration technology for case workers to collaborate and interact with case instances.
		+	*Case data, and not control flow, is the focus of a case management system. Case workers have always access to the case file and all the case data, solving the context tunneling problem. The interaction of case workers with case data may trigger additional tasks or activities in the case.
		+	*By allowing runtime planning and manually activation of tasks, case management focuses on what can be done. Tasks are enabled based on the case data available rather than on the tasks that have already been executed. Workers could collaborate via case data like comments and notes.
		+
		+	As described, case management is a paradigm shift from control flow to a data and worker centric paradigm. The expectation that workers will interact directly with the case file and case data reduces the need to fully model the process. Workers will be involved in case planning, will make decisions on what tasks should be executed, and will be able to add, remove, or modify case data for a particular case instance. Providing this level of flexibility and support to knowledge workers requires a combination of technologies, including BPM, collaboration, and content management technologies.
		+
		+
		+	[[Category: Case Management]]

LEAD Reference Content:Case Management - Revision history

Admin at 13:04, 18 January 2017

Admin: Created page with "{{DISPLAYTITLE:Case Management}} Category:Case_Management"