Foremost of the concerns faced in these massive sized MDM implementations are Data qualities being poor, non linear structure of data, disparate legacy systems and home grown systems with redundant data.  Size does matters. Remember Godzilla warring against miniature humans. So how much data volume do you define as massive, in Master Data management project? Is this volume 100 million or 500 million? What does it takes to ease pain points for organization taking the path for huge data volume based MDM projects? Do we use ETL or ELT tools for managing such massive data volumes?

The MDM Book of Knowledge needs to be opened and leaves turned to dig into collective leanings for managing huge data volume inherent MDM projects. Preferably Data Governance lead MDM projects requires definition of process to address data issues around management of initial data streams, cut over streams and conversion streams. I am sure this blog will help the MDM community to connect on experiences around massive data management project. I am all ears and listening to your comments

]]> http://jairajkumar.wordpress.com/2009/09/18/massive-data-management-in-master-data-management/feed/ 0 jairajkumar http://jairajkumar.wordpress.com/2009/07/13/analytical-master-data-management-driven-through-meta-data/ http://jairajkumar.wordpress.com/2009/07/13/analytical-master-data-management-driven-through-meta-data/#comments Mon, 13 Jul 2009 16:33:50 +0000 jairajkumar http://jairajkumar.wordpress.com/?p=3 ]]> Master Data Management (MDM) is typically associated with having a centralized data hub for managing your customer, product, location, vendor and account details. Almost all hubs are typically used for transactional or collaborative style of implementation. Recently I was involved in a work involving an Analytical MDM. An MDM from the Oracle Product stack, to address the vertical domain for Health industry called the Oracle Life Sciences Hub (LSH).

Really impressed by the product literature, I was eager to note how the Meta data captured in a centralized system was used to manage the data transformation across the staging tables to the operational data store to the strategic data mart. The product built around the Oracle E-Business suite is fully integrated for utilizing Meta data for transformation and value domain management. It also has the ability to create data mart of the fly. Oracle has taken a strategic move to break away from the other MDM product vendors, me-too hub perspective to take on the leading pharmacy MDM product the Initiate Patient hub. In case you want to read more about the same visit my blog at  (http://www.ukocn.com/blogs/jairajak/analytical-master-data-management-driven-through-meta-data)

Hats off to the Oracle team!! Master Data management and Meta data management is now getting intertwined for ease of “information management”. The future is here now.