In this scenario the master data register collaborates with the various data producing application functions. This means that when data is modified in one of the systems these modifications are shared between all collaborating functions. Therefore the integration between these data producers is essential in this scenario
An interesting scenario in this is where the Data Register is only used as a key store or key cabinet and the detailed data is kept in the other source systems
Advantages
- Data is gathered directly from source systems and thus it is always accurate and real time.
- Data can be stored within the source systems in a specific format supporting the business processes within these systems
- Differences in availability between consumers and sources can be handled by the Data Register
- Reuse of screens, workflows and validations in the source systems
- Data standardization within the Data Register
- Introduction of a key store or key cabinet.
Disadvantages
- Managing the synchronization between systems is an extra piece of work and complexity.
- Replication of data
- Complex data transformations from sources to register and back
Versie | 1.0 | Creatie datum | 02-05-2021 |
ERP (or EAM) functionality for the registration of data within a number of highly standardized processes using asset data.
Auteur | Bert Dingemans |
Alias | |
Stereotypes | ApplicationFunction |
Details van ERP |
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
Auteur | Bert Dingemans |
Alias | |
Stereotypes | ApplicationFunction |
Details van Geo |