A domain model for mergers and acquisitions will save us.
The clash of domains
Two companies shall be merged. Two workforces and two administrations have to be aligned, changed and integrated. The first problem that comes up is corporate language and a missing joint domain model and integration plan for people involved but also for applications, companies, locations and countries.
Domain models are semantic models that show objects and their relationship in a specific domain. For the M&A domain there will be representations of the M&A strategy, the business case, the integration plan and of course, of both companies to be merged. In addition we need a model of the integration project and all the tasks to be carried out in the different phases of the M&A process. The domain model does not only cover company data, but also data about the M&A process, the involved people and other attributes of the integration like goals and objectives and how they are measured.
Mapping out phases and tasks in the M&A process
Soon , the PMI workgroup of the German M&A association will publish a reference model for all tasks in the M&A process. Here is a short preview of what will be included:
Phases: are part of the M&A process like a due diligence phase or the phase between sign and close.
Tasks: describe the activities to be carried out during the M&A process. Plus there will be goals and objectives for each task that steer the execution of the tasks and measure success.
Concepts: Describe the domain data of the different companies, like companies, departments, the project management domain
Wow, that might be a lot of data types to be modeled, how can you ensure consistency? It all comes together on a task level. Tasks are executed to transform companies to reach an end state, called goal. Goals and objectives will be different by merger and companies involved.
In our case the goal is that the organizations are integrated. Success is measured with two objectives: integration success is maximized and risk is minimized.
phase: merger integration
goal: buyer and target organizations are integrated.
objectives: integration success is maximized, risk is minimized.
task description: Resources for the project will be allocated.
and the integration project will be executed.
concepts: target, buyer, organization, budget, project plan, resources
Domain model APIs foster integration of tool vendors
Domain models can be used to drive transparency in the heterogenous world of M&A tools. Tool vendors can easily show the coverage of tasks within the domain model
The description of phases, tasks, concepts, goals etc. will be formalized and can be easily used to generate API descriptions that could be used to integrate different tools in the M&A process like data rooms, project management tools etc. So stay tuned for more progress.