DataFlux Launches New MDM Product

Loraine Lawson

DataFlux has made something of a name for itself in Master Data Management as offering a solution that lets you build as you go. Recently, I read Forrester's and Gartner's most recent reports on MDM, thanks to MDM vendor Siperian, which is offering them for free download on its site. Both reports reference DataFlux's gradual or modular approach to building MDM. In part, that's because DataFlux's CDI Solution incorporated MDM, while still focusing primarily on customer data integration.


This week, DataFlux announced a new offering called qMDM. It's a major upgrade of the previous MDM offering, with more support for hierarchy management -- an area for which DataFlux had previously received criticism from Gartner - plus a master repository manager, which helps with metadata, identity management and built-in support for data governance.


To provide some context, let's take a quick look at the MDM market as it stands now. Basically, there are 8-10 major MDM vendors, depending on whom you ask. The big players, meaning they hold the largest share of the market, are IBM, Oracle and SAP. Siperian and Initiate Systems are considered "best of breed." Sun Microsystems, Tibco Software, D& B Purisma and DataFlux also make Gartner's list, with Forrester adding VisionWare. In its 2008 "Magic Quadrant for MDM for Customer Data," Gartner ranks DataFlux as a niche player.


One thing that's interesting about this new release is that DataFlux qMDM can be used for customer, product or organizational data sets. This makes the MDM framework "more adaptable to data domains beyond those that are customer focused, such as finances and inventory," according to this vnunet article about the new product.


There are two products sets - DataFlux qMDM Solution for Customer Data and DataFlux qMDM Solution for Product Data. Traditionally, MDM solutions have either been for customer data or product data -- not both. DataFlux says the product sets can be integrated. IBM lead the charge on this evolution last year when the company unveiled its Master Data Management Server.


Karen Leightell, the senior product manager for IBM's Master Data Management Solution Group, told me the next step for MDM would be a single MDM product that could handle both product and customer data. That's something I suspect you'll see more of in the coming year and it's worth considering before you invest.


One thing DataFlux does not plan to change, however, is its support for a phased-in approach to MDM. Scott Gidley, DataFlux's CTO and a founder, told vnunet:

"This product is a natural evolution of DataFlux technology, and we built it to meet the needs of enterprises who are struggling with the commonly accepted 'all or nothing' approach to MDM that is prevalent in the market."

Of course, this modular approach to implementing MDM technology is not universally accepted. Ravi Shankar, the senior director of product marketing at Siperian, makes a persuasive case for deploying a complete solution, but focusing on gradually introducing MDM by addressing targeted business problems, in this DM Review article. (Free user registration required to read.) I suspect the modular approach will appeal to many organizations, but, again, that's something you'll need to consider.


The vnunet article also notes that DataFlux customers will be able to add qMDM to existing implementations, reusing their already-established data governance rules and data quality routines.


MDM is still very much in the early adopter phase, but Forrester predicts this will change within the next 18 to 24 months -- when MDM enters the mainstream. So far, MDM deployments are done at global enterprises, and there's some debate over whether that will change.

Subscribe to our Newsletters

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


Add Comment      Leave a comment on this blog post
Oct 23, 2008 1:31 PM Vincent McBurney Vincent McBurney  says:
IBM is also introducing a tool for managing complex hierarchies as part of the Cognos suite - but based on technology from the MDM Server. It will have a Cognos interface or an MDM Server interface. Hierarchy data is nasty to maintain - especially when you have inconsistent hierarchies and multiple versions. Reply
Oct 27, 2008 1:46 PM Charles Greenberg Charles Greenberg  says:
Hi, Lorraine,Thank you for a nice article. I hope it is OK to add on here to your list of vendors. OneData from Data Foundations, where I work, is a well-received enterprise MDM product for all domains - Customer, Product, Vendors, etc. and manages hierarchies and metadata well. If you would like additional details, I would be glad to send them to you. Reply
Oct 30, 2008 11:00 AM Cliff Longman Cliff Longman  says:
Hi Loraine,I'd like to agree with the sentiment of introducing enterprise MDM in small bite-sized-chunks.With this in mind, we have had significant success driving the MDM technology from a business model. This means two things:1) There is configuration, but no customization required to introduce each new subject area2) The inter-relationships between subject areas can be introduced easliy to join up the subjects into a whole pictureAn example of the second point might be maintaining rate books in an Insurance company - this is a relationship between PRODUCT and CUSTOMER, and requires careful governance as rates need to be reported to regulators...Thank you for the interesting angle in the piece above Reply

Post a comment





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




Subscribe Daily Edge Newsletters

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

Subscribe Daily Edge Newsletters

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