Process Modeling
BPMN 2.0 Process Modeling | |
|---|---|
Modeling processes according to the modeling standard BPMN 2.0 | Celonis Process Management supports the BPMN 2.0 modeling standard, enabling all business processes to be modeled, defined, and optimized transparently and in a uniform language. |
Extend processes with data objects and attributes (eBPMN 2.0 extension) | With the eBPMN 2.0 extension, further objects/object connections and standard attributes can be displayed. This offers the user different process detailing, publishing, and evaluation possibilities. |
Semantically guided modeling | The user is guided through the modeling process according to the BPMN 2.0 semantics. Only standard-compliant predecessor and successor objects are displayed for selection, so the initial training effort is to be classified as low. |
Modeling process interfaces | A process interface refers to a predecessor or successor process. They are usually used to connect processes at the same level. |
Modeling standardized process steps (Best Practice Tasks) | Repetitive, standardized process steps can be managed centrally in the repository and used in processes as often as required. |
Initially record processes in tabular form (automatic generation of graphics) | Processes are recorded quickly and clearly in the table view and can be checked immediately in the graphical view. |
Maintain and detail processes in tables (automatic graphics generation) | Processes are efficiently revised in the table view, or further details are added. |
Connect more objects with tasks (eBPMN) | Advanced BPMN 2.0 modeling, which includes the following objects: Requirements, Standards, Risks, Controls, etc. |
Maintain additional attributes | Further standard attributes can be maintained. See Standardized Meta-Model. |
Differentiate roles according to the duty to cooperate (RASCI) | Roles are categorized according to their responsibilities according to the RASCI method. Alternatively, the RACI method (without "S") can be selected (optional). |
Differentiate groups according to the duty to cooperate (RASCI) | Groups are categorized according to their responsibilities using the RASCI method. Alternatively, the RACI method (without "S") can be selected (optional). |
Connect process interfaces in the start and end event. | At the beginning and end of a process flow, predecessor or successor processes (usually at the same level) can be referenced. |
Link predecessor and successor processes | Processes can be assigned to predecessor and successor processes to clarify their position in the overall process landscape. |
Show BPMN Icons on process flow objects. | The process flow objects additionally display the symbol icons of the BPMN 2.0 modeling standard (optional) graphically. |
Store audit results | Audits are created as projects and assigned to the process world. Audit results and recommendations for action can also be stored. |
Advanced Process Modeling | |
|---|---|
Model and orchestrate end-to-end processes (E2E) and business transactions (scenarios) | End-to-end processes and comprehensive business transactions can be represented by logically sequential processes necessary to fulfill a specific customer need. |
Automatically update process layout during process modeling (Auto-Layout function) | The Auto-Layout function automatically updates the individual process flow objects and arranges them accordingly. |
Generate different process layouts automatically. | Possible process layouts are horizontal and vertical swimlane, horizontal and vertical lean process graphics (Lean), detailed process representation (eBPMN) with all object connections, horizontal and vertical swimlanes for IT systems (Application Swimlane), compressed process representation with all objects in matrix form (Process Matrix), and individually configurable profiles. |
Free graphical design of processes and process maps (HTML editor) | Symbols, text fields, shapes, or process flow objects can be modeled graphically and linked to the process house. Images can also be added. |
Upload and graphically visualize process workshop images. | Process workshop images (movement symbol slides) can be uploaded, edited, and saved as graphics. |
Locking and unlocking process processing | Exclusive editing of processes prevents simultaneous editing by several people and thus avoids possible data inconsistencies (optional). |
Language Management | |
Translate diagram and object details. | A dialog window allows easy and fast text input of process and object details in different languages. |
Automated translation of diagram and object details (Online Translation Service) | An integrated translation service makes it possible to translate process and object details at the push of a button. |
Automatic translation function with DeepL or Microsoft Translator | The integration of DeepL or Microsoft Translator guarantees automatic translation. Further translation services can be connected. |
Process maturity level | |
Determine the degree of process maturity. | Process maturity can develop in different stages (percentage from 'defined' to 'continuously optimized'). Thus, the maturity level of a process organization can be determined. This value is displayed both as an attribute and as a graphical dashboard. |
Aggregate process maturity level | The stored process maturity levels are aggregated and displayed on the upper level (structural process level). |
Process Validation | |
Validate process semantics (check modeling errors) | Before release, the application of BPMN 2.0 semantics is checked, and modeling errors are pointed out. If essential information is missing, the release workflow cannot be started, and warnings can be ignored. |
Evaluation of object links | |
|---|---|
Display connected objects in the process in a table | All objects connected to a process ('dependencies') are displayed in a table. From this view, connected objects can be edited efficiently and quickly and sent directly to the release. |
Audit Trail | |
Display life cycle diagrams (audit trail) of all process versions. | An audit trail is used for quality assurance and shows the entire history of process status changes. It is presented as a life cycle diagram in an audit-compliant manner. |
Versioning | |
Change attributes in released processes or objects | Certain attributes can be changed in released processes (only possible for selected user roles) |
Variant Management | |
Create possible variants in the administration area. | The administrator specifies possible variants, e.g., for countries, product groups, or similar. (variant portfolio). |
Create variants | The editor selects a new variant from the variant portfolio. The original process becomes the master. |
Modeling variant processes | After the variant is selected from the variant portfolio, the specific process flow of the variant is modeled. |
Complete localization of variant processes | A variant process is completely localized (is a standalone variant independent of the master) |
Localize individual process flow objects of a variant process. | Individual process flow objects can be localized, i.e., individual steps are variant-specific. |
Completely de-localize variant processes | The localization of variant processes is resolved. |
De-localize individual process flow objects of a variant process. | The localization of individual process flow objects is resolved. |
Update variant processes | When the master process is changed, the non-localized (not changed) process flow objects are automatically updated by the master process. |