From Operational Process to Process Automation
When it comes to digitalization, process management and automation make the task considerably easier. The transparency that they provide to business processes and the IT landscape, including evaluation/assessment and automation, lays the groundwork for rapid and efficient digital transformation.
Various perspectives exist for describing business processes. Operational business process models are used to optimize operational activities within a company or between business partners, while process automation models can be used for technical planning, implementation, and control of corporate information systems. Each of these approaches targets a different goal, but they can easily be combined through use of the tools included in the BIC family of products, thereby enabling both operational business process management as well as process automation. Before presenting potential scenarios for combining operational and technical modeling, it is necessary to first explain
the fundamental interrelationship between business process models and automation models. Figure 1 shows the various phases and interrelationships involved in moving from process modeling to automation. Of particular consideration are the following phases: Operational Process Modeling, IT Process Modeling, IT Design, Implementation, and Execution. In each of these phases, it is important to distinguish between dynamic and static content. Dynamic content includes information regarding timed logistical processes; in contrast, static content generally consists of definitions of the business objects or data objects being processed as well as professional or technical services.
In the final step, during the execution phase, the solution that has been developed will be put into operation within the customer-determined run-time environment and infrastructure.
|Dynamic Modeling||Static Modeling|
|1||0 › 1||Modeling of the operational process models using EPC or BPMN||0 › 2||Modeling of the business objects using structure diagrams|
|2||1 › 3||Creation of IT process model through detailing individual activities from the operational business process model using EPC or BPMN and indentification of professional services required||2 › 4||Creation of technical IT objects through detailing of the business objects, using structure diagrams or the IT architecture|
|3||3 > 6||Creation of BPMN process skeletons based on the IT process created||4 > 7||Creation of technical data definitions based on the technical IT object definitions generated|
|5 > 8||Draft of the services required based on the identification, with the aid of ArchiMate notation, of professional service needed|
|4||6 > 9||Automated transfer of the BPMN skeletons for finalization in the BIC Process Execution development environment||7 > 10||Generation of data definitions based on the technical data definitions|
|8 > 11||Generation of services required based on the BPMN diagram created|
|5||9 > 12||Transfer of the executable BPMN processes to the run-time environment||10 > 13||Transfer of the data definitions created to the run-time evironment|
|8 > 11||Transfer of the services implemented to the run-time evironment|
|6||9 > 6||Inputting of the BPMN processes, now expanded with technical implementation information, into the modeling tool||10 > 7||Inputting of the data definitions, now expanded with technical implementation information, into the operational modeling tool|
|14 > 5||Automatic updating of the service repositories with the new, professionally-relevant services|
Table 2: Steps in Mixed Integration