In this scenario there is only one master data producing application. That is the data register. It can also be one of the existing source systems. All other applications are consuming this data from the data register and use this in their application processes. This includes the application functions for ERP and geo etc. Advantages - The service design is directly mapped in the data register. - Possibility to standardize the information model and service interfaces - Verification and business rules are implemented only in the dasset data register. - Real time alignment of the data only upon read/request - High availability only necessary for the data register. - Eventually no replication of data (depends on the maturity of the consuming systems) Disadvantages - Any change in data model in consumers leads to change in service, this should be aligned or require a large standardized datamodel in the service interface. - Information provisioning to applications needs to be redesigned which is a lot of work - Redesign of the full application landscape - High demand in performance and availability for the data register - Introduction of a single point of failure so extra non functional requirements in AIC

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.

MDM like function that aggregates all the data in a standardized data model

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