Scenario model data service

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

Version 1.0
Created date 02-05-2021
View Diagram in readmode