Current registration function with storage and processing of the master and reference data

Transformation of the data as stored in the asset data registration and transformation into a model for messages (CGMES, data marts or file formats).

Validation of data based on the data entered into the system and possibly on the existing data stored in the master data registration. It is essential that all data received from the acquisition/registration service is processed in these functions before being stored in the data registry

Validations of data via input screens by users

Functionality to publish the data as stored in the data registration for use by different types of consumers.

Application functionality that supports Data Management and governance processes. Consider data quality processes, data ownership and data security policies, etc.

Physical storage of the data in a (relational) database.

Data modeling and meta modeling for example models based on UBL and government models. These models are used for data storage, but also for data integration, transformation and validation

Transformation of data into various protocols, for example for the implementation of web services, REST, but also into a format that can be read for reporting

Processing data before it is stored and processing data upon retrieval

Machine-based validation of the data entered into the system, as well as based on timely intervals within the stored data. This is implemented in a kind of control machine.

Fully automated file transfer without manual processing of the data

Transfer of files that are manually processed and possibly modified before being deployed to the data store

Import and manual transformation of office documents such as Excel sheets etc.

SOAP/XML web services including JSON/REST

Web services based on specific exchange formats such as AMEF, BPMN and XMI for sending data to consuming systems

User interfaces for users to interact with the data stored in the registry

Web architecture interface for retrieving architecture models in a visual representation selection and representation functionality

Forms and reporting interfaces in which users can request asset data in an interactive manner

Publishing asset data to different types of user interfaces

Unmanaged and user-driven export of asset data to various office documents including CSV and XML.

Application interfaces for application to application integration. This includes fully automated system integration processes, ETL implementations and automated and managed file transfers.

Data entry via screens and diagrams for users

ETL processes for the transformation of data from relational to relational databases or structured files

Application integration interfaces for machine 2 machine integration

special ETL process to transform specific data from the source to the master data. For example, consider an ETL process based on XMI, AMEF or BPMN exchange formats

SOAP/XML web services including JSON/REST

(Traditional) ETL for transforming and transferring data from relational registers and consumers. For NoSQL transformations, a similar ETL setup is often used and therefore this is not further specified

special ETL process to transform specific data from the source to the master data. For example, consider an ETL process based on XMI, AMEF or BPMN exchange formats from the architecture repository to the consuming information systems.

Controlled and often secure device for transferring data from the register for the benefit of consumers

Message-based transfer of geo data, for example based on AMEF, BPMN, XMI via web services

Logical services that publish the data from the register to various register data consumers

Logical service for the import of data for other systems