A Model for Processes, Enterprise Architecture and IT
Companies use models in various departments, to find as many answers to corporate questions as possible. What may sound trivial can only hardly be realized, due to complex connections between the departments. Purpose of an integrative model is to find valuable answers on a cross-departmental scale.
The goal in creating models of an organization is to build a sound basis for answers - for example, about the status of a company or to discover problems in specific work activities. To this end, they are applied in various areas of the company, especially in classical business process management (BPM), which uses process models to describe the activities in a company. In addition to process modeling, there are other modeling approaches in related subject areas such as enterprise architecture management (EAM) and functional-technical IT.
The procedure for the description, as well as the notations used, often differ between departments. These differences cause problems in the evaluation. For example, when comparing a process map and an enterprise architecture, it is difficult to draw meaningful conclusions. However, to accurately
describe the current state of activities and structures in a company, it is necessary to analyze across departments.
The integrative approach links the process models from BPM with EAM and IT. This combination of different domains of modeling has an enormous potential for benefits. It makes the diverse elements that have interaction points and interfaces in the company jointly observable by making their object types (processes, roles, applications, etc.) available across domains. Due to the large number of possible objects and interfaces, a targeted, integrative model is difficult to design. How can process models be successfully integrated with EAM and IT?
Overlaps and differences between the BPM, EAM and IT view
Figure 1 shows the similarities in content, but also the differences between the notations, which must be overcome. If, for example, EAM content is recorded, then it is inevitable that elements from the other areas must also be included. The same applies to a single process model or a description of the IT architecture. When modeling processes and especially when implementing the integrative approach, it is crucial to avoid redundancies. For this purpose, the modeler determines exactly which content belongs to which area when creating the design.
The central task of mapping functional-technical IT is to document the content that an organization needs to design, implement, and operate IT solutions. The documentation and description requirements of this IT solution (e.g., SAP introduction, robotic process automation or process mining) form the basis to define the model.
Digitization (the digital representation of previously analogously stored data sets) and in particular digital transformation (the exploitation of digital offers to increase corporate success and to open up new potentials) are currently the buzzwords for sustainable management and have given this area additional significance. Even if other buzzwords dominate the discussion in the future, the goal of functional-technical IT modeling will remain: To introduce and operate software and hardware in a problem-related and promising manner.
For this very reason, the technical content of individual IT processes should have the same importance as process models and EAM content. The advantages of novel solutions such as process mining and robotic process automation can only be exploited if knowledge of the individual processes and organization-wide correlations is available. Further examples are such topics as digitalization strategy or IT governance.
In various forms, process modeling, enterprise architecture and functional-technical IT modeling often deal with similar information content. For example, as a first step towards implementing an IT project, the IT analyst needs detailed information about the business context for which he is to design a tailored solution. He must determine and describe this business and technical information. In the next phase, this knowledge forms the basis for management to classify and evaluate the significance of the new solution for the overall corporate strategy.
A comprehensible documentation and communication of the information towards the management level as well as the business and IT departments is essential. Only if the three perspectives BPM, EAM, and IT are linked via an integrative model approach, the modeling provides accurate answers and opens up the possibilities for efficient business planning.