Standardization becomes more possible by using various repository standards such as the use of templates, model validation, and limiting use based on metamodels. In fact, a repository offers more opportunities to limit the modeler's freedoms.

Models are centralized in the repository, which is usually a relational database. This makes it easier to gain and maintain insight into connections.

An agile approach can be supported by reusing models and using repository functionalities such as publication of content, reuse of (partial) models, etc. However, this does require a special design of the model

By using an architecture repository, work processes can be centralised, described and automatically supported by the available functionalities.

When using architectural documents you often see that partial models are copied. In an architecture repository this is not necessary and use can be made of existing (partial) models in the repository.

Consider the data qualitiesuniqueness, topicality, accuracy and validity that prove difficult to realize when fragmented in architectural documents.

By using an architecture repository, a new architecture approach is introduced that makes the architecture process and the products more efficient. These goals are related to the outcome achieved by the capabilities. Diagram is based on the ArchiMate Motivation extension.