Mastering Master Data??

Hi Fellow Architects,


Master Data has almost become a boring topic these days but I still find that many orgnaizations have not yet either harnessed the power of their master data or else have not really turned the corner on the "Master Data Project" which is now becoming an unwieldy expensive never ending project. 

I was wondering if any of you have had success stories in this space and have been able to come up with some simple best practices on tocpics related to master data such as the following -

a) how do you determine what is valuable information to be mastered and what not to?

b) how do you determine if the master data continues to be of relavance to the enterprise?

c) how the profile of master data has changed in the world of social networking etc.?


Your feedback is always welcome!!
--
Best Regards.

surekha -

Comments

  1. Mike GAugust 15, 2012 at 8:47 AM

    Master data boring? Never! Sure it looks like boring static data to the casual observer, but like tectonic plates shifting very slowly underneath the ground that rarely but catastrophically cause fun things like volcanoes, earthquakes and tsunamis, calm surfaces often hide instability with potentially huge consequences if not addressed head on.

    Valuable data worth the cost / complexity of mastering fit into one of two categories: either broadly used data that analysts complain about frequently due to the pain it causes, or data that is so obvious and well known to leadership as being part of the information landscape, that they take it for granted, and whatever state the data is in, good or bad, they don’t bother trying to improve things even if they should. The first type, painful data, requires discovery sessions to find out where info consumers spend their time doing inefficient master data copy/pasting/ sorting/merging/ cleansing/synching/etc via desktop tools like excel, access, etc, on a regular basis. The second type, obvious data, are by definition known at the highest levels of the organization, but the conversations about this data might occur at a similarly high level of abstraction (eg ‘Customer’ as opposed to a specific Customer Identifier or Classification), so drill down will be required to get to what the valuable data is and what issues are associated with it.

    Determining ongoing relevance is not an objective measure. Just because a particular code or hierarchy is used in many places doesn’t mean anyone cares about it or perhaps users even going out of their way to not use it. I have seen master data attached to newly developed reports only because that data was on legacy reports and the decision makers don’t want to run the risk of doing harm by taking something out they don’t know is being used anymore. Even worse, I’ve seen a case where a particular code is used for summarization in a report, and users in more than 1 group spend significant and ongoing manual effort breaking out the detail into an alternate summarization more useful to them. The best way to measure ongoing relevance is to find the data with formal or informal governance processes around them that manage change and notify appropriate parties of impact – or conversely, find the data where the most trouble seems to keep popping up – if people didn’t care, they wouldn’t complain. In these areas, if there is not formal governance in place, there should be – this will keep your master data both valuable and of ongoing relevance.

    ReplyDelete

Post a Comment

Popular posts from this blog

Issues with Server Virtualization

Virtualization has been considered a great way to maximize utilization of server resources by increasing server density. In addition, this concept is considered to be very key to green IT initiatvies as it reduces the number of compute resources needing to be supported in a data center thus reducing the cooling and power costs. Having said that, there seems to be a performance downside to virtualization. Given that a virtual machine (VM) is yet another layer of indirection the server HW this layer negatively impacts the performance any time there is a need for the application to access IO Channels, SAN disc and other network resources. This is especially so when the application code is either running inside of a JVM or an application server container such as a JEE container, .NET CLR or even a web server servlet container. In all cases, performance profiles of an application seem to vary whether the application is running inside of a virtual layer vs. directly on the physical server. V
Read more

Data Aggregation & Data Discovery - Part I

A lot of talk has been heard lately about the concept of data lake.  Variously known as, data refinery, data factory etc.  I find it interesting that we now hear logical architectural terms that speak to the concepts and to the purpose of the big data technologies such as Hadoop / HDFS and Apache distributed database technologies such as HBase / Cassandra .    This may be indicative of a shift.  What I am not sure of is does this mean that there is a level of maturity that has been achieved by this suite of open source technologies? Or could  this point to the fact that these technologies have practical applications that solve enterprise scale problems? Or does it show that enterprises have realized that they are no longer able to just deal with "structured data" and that a vast majority of information lies in the space of "unstructured content" leaving them no choice but to venture into the realm of big data technologies?  Not really sure!   The fact re
Read more

What is the definition of a strategic partnership with a vendor?

In this post I try to outline a few features of what I would consider a strategic partnership with a service provider or a technology vendor.  These are thoughts that I have distilled from years of experience (good and bad) with my vendor partners.  Hence this aspect of doing business cannot be overlook and not the least of these is the "cost" of doing business. Here are a few key attributes, not necessarily in any particular order of preference. 1) the strategic partner relationship has to go beyond a transactional one to that of a more long term one 2) the strategic partner has to have skin in the game - they have to be measured with your success criteria - they can succeed only if you do 3) the strategic partner has to be willing to "share" their technology roadmap with you 4) the strategic partner has to allow you to re-shape their technology roadmap to meet your needs 5) the strategic partner relationship has to include making their test labs, test gear, pr
Read more