Responsible for the use and deployment of the models in the architecture repository. Has a coordinating and controlling task for all modeling roles involved in the architecture. Monitors the consistency of the architecture repository and provides modellers with information and training on the use of the architecture repository.

Creates models in the architecture repository such as building blocks, solution architectures and base plates etc.

Move duplicates to the Trash, then create a baseline, then delete the elements from the Trash. Due to the baseline, they are still present (in XML format) but no longer visible in the repository.

Inform modellers about (de)duplication process.

The duplicate report is created for each package and is sent to the people who have created duplicates in their work folders so that they can correct duplicates if it appears that these elements should continue to be recognized as a new element in their own package. This is a solution to a homonym problem. If it is a duplication, automatic deduplication can take place.

Create a baseline for the package with the date as version number and duplication as description. A baseline is a copy of the package contents in XML format.

There are duplicates in the repository, this is evident when running a report or because there are warnings about duplicate elements.

Possibility to correct the duplications made by the modelers before the automated deduplication is carried out.

Duplicate report is emailed to the modelers involved or they are asked to activate it themselves based on their own work package.

Duplications can easily occur in the repository, despite the messages generated by the IDEA AddOn. This process describes how to de-duplicate in an architecture repository in which multiple modelers work together.

Run the deduplication routine in the IDEA addon, including the subpackages if desired (enable the check mark in the screen).