Basics
BPM (Business Process Management) deals with the identification, design, documentation, implementation, control and improvement of business processes. Various notations are provided to help map business processes in a visual format. BPMN (Business Process Model and Notation) is currently very popular and widely used, which is why CURSOR-BPM uses the BPMN version 2.0. CURSOR-BPM offers two process models for visual mapping: the business and the implementation model. The business model supports the functional user in the creation of documentation and process descriptions, and also supports IT as a template for the technical implementation. The required process definitions for automation are created by IT in the implementation model. Both models communicate with BPMN in the same "language", but still cater to the differing languages and requirements of the functional user and IT. The process becomes more accessible for both parties and communication is simplified.
The aim of the BPM engine embedded in the CRM system is to create a standardized map of all CRM-related business processes. The integration of third party systems (ERP, DMS, etc.) can be modeled and implemented via appropriate interface points. The user is guided through the various work steps and will not have to consult the company's process documentation for each work instruction or workflow. The company management can monitor these processes strategically, while the BPM process manager oversees the operative process management. The BPM analyst or administrator can examine and optimize processes as part of an ongoing professional CIP (Continuous Improvement Process).
Processes and containers for the administration of the process models, the data and external resources.
The term "process" has many meanings. Please note the extended definition for administration in CURSOR-BPM. Here, a "process" is not the same as the process definition as a BPMN model. Instead, the "process" here is a container, which holds the data definition, the various BPMN models and links to external resources.
BPMN
BPMN is short for Business Process Model and Notation.
BPMN is a standardized description language for processes, which defines the notation (symbols) and the syntax (XML). A process can therefore in this format be exchanged between differing systems. That applies specifically for the business model. The implementation model contains custom add-ons, which require the existence of CRMs for their workability. BPMN recognizes for the main part events, tasks, gateways and sequence flows as elements of the workflow control.
The range of elements of CURSOR-BPM contains the following:
|
Group |
Symbol |
Name |
Description |
|---|---|---|---|
|
Events (Event) |
|
Neutral start event |
A neutral start event triggers a process. There is no specifically assigned behavior as to how the triggering occurs. This can be added to the description of the element. |
|
|
|
Conditional start event |
Process start is tied to a condition. The process will start if the condition is met. |
|
|
|
Multiple start event |
The process reacts to all (non-manual) start events, once the condition is met. |
|
|
|
Message intermediate in event |
The intermediate in event interrupts the process and waits for the arrival of a message, e.g. an email. |
|
|
|
Message intermediate out event |
The intermediate out event sends messages to the CRM system: these are executed as action types. |
|
|
|
Timer intermediate event |
The process will wait for a predetermined period of time to continue the process and/or to interrupt a user action. |
|
|
|
Transaction intermediate event |
The intermediate event interrupts the process execution and continues it asynchronously in a new transaction. |
|
|
|
Neutral end event |
This end event symbolizes the end of the process. It does not contain any results or follow-on processes. |
|
|
|
Cancel end event |
This end event symbolizes the cancellation of the process. It does not contain any results or follow-on processes. |
|
|
|
Message end event |
With the end of the process messages will be sent to the CRM system: these are executed as action types. |
|
Actions (Task) |
|
Action |
A task (or action) represents a unit, which has to be processed at that point. A neutral action can be used for any task. An itemization is done via the description of the element. |
|
|
|
User task |
A user task requires an interaction of the user with the process. |
|
|
|
Script task |
Executes logics as script tasks in the process. |
|
|
|
Mass data task |
A task for working mass data in script logic, serial letters or serial mails. |
|
|
|
Sub process |
A sub process is a standalone process, to which sub tasks can be outsourced. A sub process can only be accessed from within another process. |
|
Gateways (Gateway) |
|
Exclusive gateways |
A gateway governs the sequence flow and therefore the process workflow. Gateways are used for the separation and merging of individual sequence flows. |
|
|
|
Event-based gateway |
The sequence flow follows the intermediate event occurring first. |
|
Sequence flow (Flow) |
|
Sequence flow |
The sequence flow visualizes the process workflow. It also allows the mapping of alternative process workflows. Sequence flows contain the conditions that apply for each flow. |
|
|
|
Default flow |
The default flow is the same as the default process workflow. It is used if no other sequence flow condition is fulfilled. |
|
Swim lanes (Swim lanes) |
|
Pools |
Pools are used for the differentiation of process participants. They generally represent an organization. |
|
|
|
Lanes |
Lanes are used for subdividing pools and allow a structuring of the organization, the process and the systems. |
|
Phases |
|
Phases |
Phases are used for structuring time periods and information in processes. They are a CURSOR-specific extension and not part of the BPMN standard version. They inform the user in CRM about the incident during process execution. The process will generally progress through various phases. A CRM user will not be confronted with the BPMN model; instead, he will see a simple visualization of the progress based on the current phase of the relevant process ID. That is why it is crucial that each process phase has a unique and clear phase name. Choose short and concise titles, as the later visualization is restricted to a default length (single line). The documentation for the phase will later be displayed to the user as a help text. |
Process engine Activiti
A technical platform, i.e. a process engine, is used for the modeling and execution of processes defined via BPMN.
In CURSOR-BPM, the process engine Activiti is used. Activiti is a workflow and business process management (BPM) platform. It is designed to handle business processes. At its core is a powerful and robust "BPMN 2 Process Engine" for Java. It is an Open Source app under the Apache license. Activiti runs on a server, in a cluster or in the cloud for any Java application. Activiti is lightweight and offers a variety of access services:
-
Identity Service: User and group administration
-
Repository Service: Access to deployed processes
-
Runtime Service: Access to running process instances
-
Task Service: User task administration
-
History Service: Logging and reporting of process data
Links
-
Process Management - https://en.wikipedia.org/wiki/Process_management
-
BPM - http://www.eabpm.org/
-
BPMN - https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation
-
BPM Engine - http://www.activiti.org/
Server data display
Just like the way that the title bar is displayed in CRM, the title bar in BPM shows the relevant server name and port, e.g. CURSOR-BPM (production system:18443). The display makes it easy to identify the various apps when you are working with separate systems (e.g. production, test or consolidation version).