In the past few posts we examined opportunities for designing a service layer for master data. The last note looked at the interfacing requirements between the master layer and the applications lying above it in the technology stack. Exposing accessibility to master data through the services approach opens new vistas
In a tiered approach to facilitating master data integration, the most critical step is paving a path for applications to seamlessly take advantage of the capabilities master data management (MDM) is intended to provide. Those capabilities include unique identification, access to the unified views of entities, the creation of new entity
Let’s say that you have successfully articulated the value proposition of incorporating a master data capability into a customer’s business application. Now what? If you are not prepared to immediately guide that customer in an integration process, the probability is that a home-brew solution will be adopted as a “temporary”
In my previous post, I suggested that if we were to better articulate how master data management (MDM) is typically used, we could develop the components of solution templates that can speed the integration process. In this post, we’ll start to look at some common ways that the capabilities that
In my three previous posts, I pondered whether unlimited data could limit data silos (i.e., whether offering users the enterprise data management equivalent of unlimited data streaming could curb their enthusiasm for creating data silos), or if streaming past the limits of unlimited data could create more data silos if users became frustrated with the practical
In my two previous posts, I pondered whether unlimited data could limit data silos (i.e., whether offering users the enterprise data management equivalent of unlimited data streaming could curb their enthusiasm for creating data silos) or if streaming past the limits of unlimited data could create more data silos if users
In my last post, we explored the integration of entity resolution technology as a core component of a master data management (MDM) application, and I raised the question as to whether the rampant phase of acquisition and integration of entity resolution tools companies into MDM solutions providers implied that the
Master data management is an application framework comprising a number of different information management practices and services. And the core of most party-oriented (e.g. customer/employee/vendor, etc.) master data management systems is some mechanism for entity resolution, which fundamentally is intended to identify connections between data instances that refer to the
If you've been following this thread of posts on entity resolution, you'll recall that we have differentiated between the full integration of entity resolution within a master data management system from the other (perhaps operational) uses that do not require a master data index. While the examples we've looked at
In my previous post, I outlined the main components needed for a phased approach to MDM. Now, let's talk about some of the other issues around approaching MDM: data governance and the move to enterprise MDM. Where does governance come in? Throughout your MDM program, it's important that deep expertise
