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.

Temporarily remove the locks from the production package otherwise these elements will not be updated in status.

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

Inform modellers about (de)duplication process.

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.

Elements are moved to the relevant packages, for example from workbook to project package or to project2production.

To the place in the repository tree structure based on a function under Design -} Package -} Manage -} Update. This allows you to recursively change the contents of the repository, including the diagrams and the elements, the status indicating how elements can be (re)used in the new solutions. You can then use the legend with the status colors by setting it to active to put in your diagram. This makes it easy to see what the status of an element is based on the colors.

The modeler places the diagrams, packages and entities that he/she considers relevant for use as generic entities in the production package. This means that the entities can be used by other modelers in their own solutions and diagrams. This makes the elements part of the baseline architecture.