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.

Despite the fact that architectural modeling is a very creative process, this does not alter the fact that repetitive tasks such as model validation but also the use of templates can be automated. What and how this automation is introduced is a work process.

Drawing up architectural models is on the one hand a creative activity, on the other hand it is a relatively error-prone process. This means that the tooling must optimally support the modeler when drawing up models.

Especially in large Architecture Repositories, a simple search based on various parameters and combinations is necessary. This also has added value in smaller repositories.

Partial models can be exported and imported to various formats. This includes general formats CSV, XLS, XML, but also more specific exchange formats such as XMI or AMEF. In addition, web service technology can also be applied to implement more interactive export and import of submodels.

Architecture Repositories quickly become extensive (many elements, diagrams and connections). That is why there must be functionalities that make it possible to easily find relevant sub-models. This is relevant for all stakeholders.

An Architecture Repository does not stand alone in an application landscape. Data must be exchanged to and from the architecture repository. Model transformation is almost always necessary.

Generic functionalities that are often relevant to all stakeholders for the architecture repository,