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

Geo viewer intereface for the retireval of asset data in combination with geographical selection and representation functionality

Application integration interfaces for machine 2 machine integration

SOAP/XML webservices including eventually REST services

ETL implementations specific for the transfer of geo data (for example FME)

Forms and reports interfaces in which users can retrieve asset data in an interactive manner

Fully automated file transfer without manual handling of the data

Message based transfer of geo data for example based on WMS/WFS/WMTS or GML over webservices

Transfer of files that are manually handled and eventually modified before implementation in the data storage

Import and manual transformation of office documents like excel sheets etc.

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

Modification of data via (webbased) screens. This includes geo based screens

Publication of asset data to various user interface types

User interfaces for human interaction with the data stored in the data registration

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

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

Transformation of data to various protocols, for example for the implementation of webservices, REST but also to a format readable for reports

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

Functionality to publish the data as stored in the data registration for use of various consumer types.

Validations when data is entered by hand (via screens etc)

Actual registration function with storage and processing of the master data

Machine based validation of the data entered in the system but also based on timely intervals within the stored data. This is implemented in a kind of rule engine.

Processing of data before it is stored in the data storage and when the data is retrieved from the storage

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

Logical service for the import of data from other systems and sources

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

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

Application functionality that support data management and governance processes. Think about data quality processes, data ownership and data security policies etc.