Editing Business process modeling (section)

=== Model consolidation ===
This is about checking whether there are any redundancies. If so, the relevant sub-processes are combined. Or sub-processes that are used more than once are outsourced to support processes. For a successful model consolidation, it may be necessary to revise the original decomposition of the sub-processes.

''Ansgar Schwegmann and Michael Laske'' explain: "A consolidation of the models of different modeling complexes is necessary in order to obtain an integrated&nbsp;... model."<ref name="SCHWEGMANN-LASKE" /> <sup>(Chapter 5.2.4 Model consolidation) ← automatic translation from German</sup> They also list a number of aspects for which model consolidation is important:
* "Modeling teams need to drive harmonization of models during model creation to facilitate later consolidation."
* "If an object-oriented decomposition of the problem domain is carried out, it must be analyzed at an early stage whether similar structures and processes of different objects exist."
* "If a function-oriented decomposition of the problem domain is undertaken, the interfaces between the modelled areas in particular must be harmonized."
* "In general, a uniform level of detail of the models" (in each decomposition level) "should be aimed for during modeling in order to facilitate the comparability of the submodels and the precise definition of interfaces."
* "After completion of the modeling activities in the teams of the individual modeling complexes, [the] created partial models are to be integrated into an overall model."
* "In order to facilitate the traceability of the mapped processes, it makes sense to explicitly model selected business transactions that are particularly important for the company and to map them at the top level.&nbsp;... Colour coding, for example, can also be used to differentiate between associated organizational units."<ref name="SCHWEGMANN-LASKE" /> <sup>(Chapter 5.2.4 Model consolidation) ← automatic translation from German</sup>