

Business applications then are layered on top of the data object service layer by deploying or possibly reusing specific components associated with business processes. However, as the reliance of applications on the master data management environment increases, there are further requirements for data object services related to the level of service provided for application use, such as synchronization, serialization, embedded access control, integration, consolidation, and access. The MDM system architecture focuses on the core technical components to support the data life cycle. The challenge is that it is largely unstructured, and MDM systems have traditionally been designed around the processing of structured data.ĭavid Loshin, in Master Data Management, 2009 3.2.4 MDM Service Layer Architecture Because it is user-generated content, it can provide direct insight into a customer’s attitude toward products and services or readiness to buy or sell ( Oberhofer, Hechler, Milman, Schumacher & Wolfson, 2014). This problem is particularly acute for product MDM in companies with large volumes of online sales.Īnother channel that has become increasingly important, especially for CDI, is social media. Large volumes of network data can overwhelm traditional MDM systems. Multi-channel data sources are both a cause and effect of Big Data. Increasingly, MDM systems must deal with multiple sources of data arriving through different channels with varying velocity, such as source data coming through network connections from other systems (e.g. Talburt, Yinle Zhou, in Entity Information Life Cycle for Big Data, 2015 Multi-channel MDM
