Will Master Data Management and ETL Overlap?

Loraine Lawson

I was chatting today with Andy Hayler. Hayler co-founded the data warehousing/master data management company Kalido, but recently launched the consultancy, The Information Difference, with Dr. David Waddington, a former chief IT Systems Architect. Hayler described the company as a "boutique version of Gartner or Forrester" devoted solely to researching master data management.

 

He contends integration vendors need to sit up and pay attention to what's going on with MDM, because MDM technology could eliminate the need for some of the point-to-point, hard-coded integration ETL solutions currently provide:

"...the integration vendors need to understand what's happening in the MDM world, because a piece of their world is changing and I think they need to ideally become part of that solution. If MDM does continue to grow and be widely implemented, and you're an integration vendor and you don't participate in that world, you're going to lose at least some of your potential application. This is why SAP, Oracle Microsoft and IBM have all bought MDM vendors. All four have realized if they don't have MDM at the heart at their own offerings, then some of their proprietary applications start to be hollowed out. I don't' think it's fully dawned on all the integration vendors."

I thought of his comments when I saw this IT-Director article on expressor software, a new ETL-based data integration solution profiled by Philip Howard, a data management research director with Bloor Research.

 

Howard points out that many functionalities for existing ETL products have been tacked on, but expressor was designed to incorporate these functionalities from the get-go. That's its first advantage. The second is that it uses semantics, which means the tool can figure out "customer no" "customer ID" and "customer_no" are all the same thing -- without you having to manually connect the dots. It ships with a slew of similar semantic equivalents, saving you a lot of time and trouble, he writes.

 

Howard seems to anticipate expressor to be disruptive to existing players, such as Informatica, Business Objects and IBM.

 


To me, that functionality sounds very similar to what MDM offers. Perhaps this could be another sign of cross-pollination between MDM and ETL?

 

MDM is still young, and Hayler said no one has a mature, complete solution. MDM will undergo further consolidation and mergers, both as a technology and a market. A recent article on SearchOracle.com took a look at some current big-name MDM offerings, and I think it reflects Hayler's assessment. It's a good read, particularly if you're involved in or about to start an MDM initiative.

 

But if you're only thinking about MDM, does this mean you should wait? Well, it depends on your needs, obviously. But even if you don't want to invest in the technology, a recent report from the Aberdeen Group suggests it's probably worth your company's time to look at the practice of master data management.

 

MDM the practice is already showing positive results in manufacturing firms, according to an Manufacturing Computer Solutions' article on the Aberdeen study. Aberdeen found manufacturers who pursued "one version of the truth" -- which is MDM's goal -- improved customer satisfaction scores, operated more efficiently and decreased the time it took to get data to the business.



Add Comment      Leave a comment on this blog post
May 23, 2008 8:22 AM John Russell John Russell  says:
I agree with you that there is an emerging cross-pollination between MDM and ETL. And you are right that there are similarities between our semantic data integration system and off-the-shelf MDM solutions, albeit we classify our product as general purpose data integration infrastructure software rather than domain-specific MDM software. We look at MDM as a specific data integration scenario. Prior to the debut of off the shelf MDM solutions this processing was maintained in ETL applications and at one time MDM was considered to be a subset of data integration. The birth of MDM as a paradigm is the result of one simple fact: that todays mainstream ETL vendor solutions arent able to address the MDM customer needs effectively and efficiently. All current ETL tools lack the ability to semantically rationalize physical metadata towards common business terms an important capability that is built into todays MDM solutions and is now becoming available via our patent-pending expressor semantic data integration system. We expect customers to continue to use CDI and PIM solutions for domain-specific MDM initiatives and consider us as a viable alternative for general purpose MDM integration projects that cannot be solved with these specialized solutions. Reply

Post a comment

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

null
null

 

Subscribe to our Newsletters

Sign up now and get the best business technology insights direct to your inbox.