In this scenario there is no data register but all master data is stored within the data producers like ERP and geo functions. However for the data consumers the data is available via the asset data services in a standardized manner. This means that when a consumer needs asset data this is requested via the data services and collected from the various data producing applications. The implementation of the data services handles the standardization of the master data model and the data exchange protocol Advantages - Real time alignment of the data. - Single Point of Truth and Maintenance - No replication of data (and the involved complexity) - Reuse of existing user interfaces, validations and (hidden) integrations Disadvantages - The service design should not enhance the data so the application might have to be redesigned. - Any change in data model in sources leads to change in service, this should be aligned. - Verification and business rules are implemented in source systems. - High availability and performance needs for all the producing systems - Complex model transformations within the service layer to transform for specific producer system model to the required model by the consumers - Releases of the source systems become more complex because of the new dependencies in the data services

ERP (or EAM) functionality for the registration of data within a number of highly standardized processes using asset data.

Application and database integration like webservices, file transfer, database links, views etc. In a later phase we will model the various integration methods and model these in detail

Abstract architectural entity for the register data consumers, all user interfaces and data integrations are an master data consumer

Logical application function for the storage and transformation of master data in various source function and the data register function

Other MDM data producing application functions like the delivery of office files etc.

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

All kinds of user interfaces in which an user can consume data via a (graphical) user interface. Examples of user interfaces are reports, forms, portals graphs, geoviews etc.

Geo functionality and register in combination with the extraction of asset data in combination with geo data and maps