Magic Quadrant for Master Data Management of Customer Data Solutions
Organizations selecting a solution for master data management of customer data still face challenges. Overall, functionality continues to mature, but some of the well-established vendors' messages are getting more complex. Meanwhile, less-established vendors continue to build up their credentials.
Master data management (MDM) of customer data solutions are software products that:
- Support the global identification, linking and synchronization of customer information across heterogeneous data sources through semantic reconciliation of master data.
- Create and manage a central, database-based system of record or index of record for master data.
- Enable the delivery of a single customer view (for all stakeholders) in support of various business benefits.
- Support ongoing master data stewardship and governance requirements through workflow-based monitoring and corrective action techniques.
- MDM (see Note 1 for a definition) implementations and their requirements vary in terms
- Instantiation of the customer master data — varying from the maintenance of a physical "golden record" to a more virtual, metadata-based, "indexing" structure.
- The usage and focus of the customer master data — ranging across use cases for design (information architecture), construction (building the business), operations (running the business), and analytics (reporting the business).
- Different organizations' structures spanning small, centralized teams through to global, distributed organizations.
- The latency and accessibility of the customer master data — varying from real-time, synchronous reading and writing of the master data in a transactional scenario between systems, to message-based, workflow-oriented scenarios of distributed tasks across the organization and legacy style batch interfaces moving master data in bulk file format.
Organizations use MDM of customer data solutions as part of an MDM strategy, which in itself should be part of a wider enterprise information management (EIM) strategy. An MDM strategy potentially encompasses the management of multiple master data domains, such as customer, product, asset, person or party, supplier and financial masters. As the name suggests, MDM of customer data solutions focus on managing customer data — a form of "party" data, whereas MDM of product data focuses on managing product data — a form of "thing" data. There are no other discrete Magic Quadrants for other master data domains, due to the relatively low level of discrete market interest to govern those data domains in comparison to customer and product data.
We are routinely asked whether we have an overall MDM Magic Quadrant but, while we continue to keep this under review, we still believe that it is premature, because MDM needs are very diverse (see "The Five Vectors of Complexity That Define Your MDM Strategy"), leading to different market segments and the majority of the buying activity and evaluations still focused on initiatives for specific master data domains. In addition, although many MDM solutions are marketed as multidomain MDM, they don't always conform to our definition of multidomain MDM technology (see Note 2) and we find that they have many gaps in their capabilities and experience in handing every data domain (see "A View of Master Data Management Vendors' Experience In Handling Multiple Master Data Domains" and "A View of Master Data Management Vendors' Experience in Handling Multiple Master Data Domains, Part 2").
Gartner's Magic Quadrant for Master Data Management of Customer Data Solutions provides insight into the portion of the constantly evolving packaged MDM systems market that focuses on managing customer data to support CRM and other customer-related strategies. It positions relevant technology providers on the basis of their Completeness of Vision relative to the market, and their Ability to Execute on that vision.
Source: Gartner (October 2012)
Headquarters: Armonk, New York, U.S.
In the MDM market IBM offers InfoSphere Master Data Management v.10.0, generally available since October 2011 (with a July 2012 release adding Reference Data Management capabilities) that comprises four options: Standard, Collaborative, Advanced and Enterprise Editions. Version 10.0 is the first step in a multiyear convergence road map that unifies and integrates IBM's three prior MDM products — InfoSphere MDM Server, InfoSphere MDM Server for Product Information Management (PIM) and Initiate Master Data Service (MDS) — and IBM is working on further integration to create a single software stack that includes the key capabilities of each product, together with common UIs, workflow, services, data stores, and metadata. Price points for InfoSphere MDM vary by industry, by data domain (individual, organization, account, product, custom) and by the number of managed records per data domain type.
In this Magic Quadrant we are evaluating IBM's InfoSphere MDM Standard Edition and Advanced Edition separately. While IBM is progressively building a single stack, end-user organizations are faced with a choice between multiple offerings that are positioned differently. Standard Edition is derived from the prior product Initiate MDS, and focuses specifically on registry style "system of reference" implementations, whereas Advanced Edition is derived from a combination of the prior products Initiate MDS and InfoSphere MDM Server and provides support for all MDM implementation styles. Collaborative Edition does not meet the inclusion criteria for MDM of customer data solutions and Enterprise Edition is a bundling of the whole portfolio.
Customer Base (licensed to manage customer data): Estimated at 210 for InfoSphere MDM Advanced Edition
- Broad information management strategy includes strong MDM portfolio: InfoSphere MDM Advanced Edition is part of IBM's Information Management portfolio that includes business intelligence (BI), performance management, information integration, warehousing and management, content management, and data management. This is an attractive proposition for organizations looking for a wide range of information management functionality from a single, highly viable vendor, and InfoSphere MDM leverages other products from within the Information Management group — such as InfoSphere Information Server and the InfoSphere BigInsights and InfoSphere Streams "big data"-related products. IBM positions InfoSphere MDM as the enabler of trusted information across the organization and is rationalizing its multiple MDM offerings into a single increasingly consistent product set with upgrade opportunities, making its capabilities more logical and more leveragable. We estimate that IBM's total MDM revenue in 2011 was $301 million.
- Strong market momentum: IBM's MDM customer base continues to grow, benefiting from the vendor's large sales and marketing organization, and its large customer base. We estimate that at the end of 1Q12 IBM had a total of over 700 licensed MDM customers with over 510 customers managing customer data and 210 of those running Advanced Edition. We estimate that IBM's 2011 revenue related to MDM of customer data was $196 million, including $127 million for Advanced Edition. Gartner estimates that Advanced Edition is the clear market leader in terms of revenue in the market for MDM of customer data solutions. Advanced Edition is particularly strong in financial services and IBM maintains a strong global balance of clients.
- The convergence of two very capable MDM offerings: InfoSphere MDM Advanced Edition provides a powerful combination of IBM's two prior MDM products for managing customer data (Initiate MDS and InfoSphere MDM Server) which represented, respectively, strong solutions for lighter, registry-focused implementations and high-end, transaction-driven, centralized implementations that create and maintain a physical system of record in service-oriented architecture (SOA) environments. Advanced Edition provides support for all MDM implementation styles and the MDM workbench gives the ability to create and manage custom data domains. This capability is leveraged in the latest release to provide reference data management capability. In v.10 IBM is starting to show its ability to leverage key functionality across prior products and to introduce common capabilities for the long term. For example, it has ported the Initiate MDS probabilistic matching engine across to the InfoSphere MDM Server engine and has created the InfoSphere MDM Application Toolkit, which can generate MDM applets for integration into new or existing applications. IBM is also increasingly leveraging IBM BPM Express to create and consume customer master data.
- Good prepackaged data model and services: The InfoSphere MDM Server engine within Advanced Edition contains a very capable and extensible prepackaged party data model (with accompanying capabilities to store light product and account data) and provides the capability to model new data domains as required. The Advanced Edition has good support for hierarchy management and location data and has rich prebuilt functionality in a multilevel business service library. The new Adaptive Services Interface (ASI) provides easy graphical mapping tools to allow customers to expose tailored Web services that meet their needs for the content and terminology of the service. Advanced Edition has steadily improving data stewardship facilities which include task management capabilities to assist data stewards and data steward managers with the workflow and allocation of tasks. Role-based UIs have capabilities such as graphical data visualization and hierarchy management, and customers can leverage the UI Generator to extend the existing UIs and to generate new ones.
- Complexity and inconsistencies within the new InfoSphere MDM product: At first sight, the IBM InfoSphere MDM go-to-market story is simple; there is one product with multiple editions. But as you look beneath the surface it gets more complex and the inconsistencies — in terms of underlying technologies, UIs and workflows that result from three separate MDM acquisitions — become more obvious. These inconsistencies will continue to confuse and create complexity for prospects and current customers until the different editions are fully integrated from an external perspective and share common underlying services. In the meantime, organizations will need to carefully think through the implications of starting to manage customer data with a lightweight registry style and then moving to a prepackaged physical data model with out-of-the-box business services. This is likely to be a more complicated journey than it seems at first, with the need to either run the instances side by side and or to make a migration.
- Challenging future product convergence road map: IBM has shared a road map with its clients for how it will integrate the three prior MDM products into a single stack with three embedded MDM engines. IBM plans to provide a single database instance for all master data and metadata; a single application instance (within an application server container); a single services layer; a single installation, configuration and maintenance layer, and a single UI layer for governance. This will be a multiyear journey as IBM provides increasing integration between the different "engines" and creates common shared services. Version 10.0 is a good first step, though it still requires multiple instances and the tooling around the different prior products remains inconsistent, and there is a risk that IBM could devote too much of its energies to the convergence road map — as opposed to innovation in domain-specific areas.
- Prepackaged approach is not for everyone and functionality is behind in some areas: Although Advanced Edition is a very capable product with a prepackaged out-of-the-box data model and services library, some organizations are looking for a more client-driven data modeling approach. IBM does offer a "platform" version of Advanced Edition called Custom Domain Hub Stand-Alone, but not many customers are leveraging it yet. Also, IBM has more work to do in areas such as embedded analytics, master data stewardship, business rules governance and business process management (BPM)/workflow integration. Although some of this may be available in one of the other editions, it is not yet available to all in a consistent fashion. On the multidomain front, all editions can support multiple domains to a degree but there are different limitations in each. The beginnings of the InfoSphere MDM and big data story are promising, but there is no out-of-the-box integration to social CRM applications. There is no multitenant software as a service (SaaS) strategy with Advanced Edition, although partners have launched cloud-based infrastructure as a service (IaaS) offerings with IBM, and Advanced Edition currently lacks out-of-the-box integration with SaaS applications.
- Customer references scored relatively low in several areas: IBM provided a full set of references for both InfoSphere MDM Standard Edition (the former Initiate MDS) and InfoSphere MDM Advanced Edition (which includes the former InfoSphere MDM Server as well as InfoSphere MDM Standard Edition). Advanced Edition gained average to above average customer satisfaction scores for most product categories, with high marks for its support for multiple architectural styles as well as performance and scalability. Conversely, it scored lower with respect to its support for internal workflow and data stewardship, and its support for data quality facilities. Advanced Edition also scored relatively low on the transparency of its pricing structure. IBM earned relatively average marks for its support of Advanced Edition, performing better on post-sales than pre-sales, and the most positive references continue to mention the direct involvement of IBM Labs resources during the initial implementation as a critical success factor.
Headquarters: Armonk, New York, U.S.
In the MDM market IBM offers InfoSphere Master Data Management v.10.0, generally available since October 2011 (with a July 2012 release adding Reference Data Management capabilities), that comprises four options: Standard, Collaborative, Advanced and Enterprise Editions. Version 10.0 is the first step in a multiyear convergence road map that unifies and integrates IBM's three prior MDM products: InfoSphere MDM Server, InfoSphere MDM Server for PIM and Initiate MDS. IBM is working on further integration to create a single software stack that includes the best capabilities of each product, together with common UIs, workflow, services, data stores and metadata. Price points for InfoSphere MDM vary by industry, by data domain (individual, organization, account, product, custom) and by the number of managed records per data domain type.
In this Magic Quadrant we are evaluating IBM's InfoSphere MDM Standard Edition and Advanced Edition separately. While IBM is progressively building a single stack, end-user organizations are faced with a choice between multiple offerings that are positioned differently. Standard Edition is derived from the prior product Initiate MDS and focuses specifically on registry style "system of reference" implementations, whereas Advanced Edition is derived from a combination of the prior products Initiate MDS and InfoSphere MDM Server and provides support for all MDM implementation styles. Collaborative Edition does not meet the inclusion criteria for MDM of customer data solutions and Enterprise Edition is a bundling of the whole portfolio.
Customer Base (licensed to manage customer data): Estimated at 300 for InfoSphere MDM Standard Edition
- Broad information management strategy includes strong MDM portfolio: InfoSphere MDM Standard Edition is part of IBM's Information Management portfolio that includes BI, performance management, information integration, warehousing and management, content management and data management. This is an attractive proposition for organizations looking for a wide range of information management functionality from a single, highly viable vendor and InfoSphere MDM leverages other products from within the Information Management group — such as InfoSphere Information Server for Data Integration and the InfoSphere BigInsights and InfoSphere Streams big data-related products. IBM positions InfoSphere MDM as the enabler of trusted information across the organization and is rationalizing its multiple MDM offerings into a single, increasingly consistent product set with clear upgrade opportunities — making its capabilities more logical and more leverageable. We estimate that IBM's total MDM revenue in 2011 was $301 million.
- Registry style, fast time to value and strong market momentum: InfoSphere MDM Standard Edition provides a registry-style "system of reference" implementation approach. In this distributed authoring implementation style, ownership stays with the authoring application; however, Standard Edition can match and link, storing the original source records in the hub and generating virtual golden records on the fly. Standard Edition has a reputation for fast time to value and a relatively low service-to-software cost ratio, because it is less invasive than other implementation styles and requires less governance agreement within the organization. It is also more suitable for multi-organizational data sharing, such as in government and healthcare. We estimate that at the end of 1Q12 IBM had a total of over 700 licensed MDM customers with over 510 customers managing customer data and 300 of those running Standard Edition. We estimate that IBM's 2011 revenue related to MDM of customer data was $196 million, and that included $68 million for Standard Edition.
- Excellent scalability and steadily gaining common functionality: Standard Edition has strong references with proof points for extremely high volumes of business-to-consumer (B2C) data, with subsecond latency and high transaction rates. It has data model and Web services flexibility, a highly rated probabilistic matching capability (selected by IBM as the default option across all of its MDM editions), integration with a range of data quality tools, and good measurement and monitoring facilities. Standard Edition provides basic workflow, partially based on IBM BPM Express (which is bundled with the product), for data stewards to visualize and manage consumer and organizational data. It leverages the InfoSphere MDM Application Toolkit capability, for building composite applications and MDM applets that can be embedded in existing applications — such as salesforce.com.
- Strong vertical industry focus, especially in healthcare and government: Standard Edition is very strong in the healthcare provider enterprise master patient index (EMPI) and healthcare information exchange markets, and has a strong partner ecosystem. It also continues to do well in government (at national and local levels), particularly in meeting entity resolution requirements. IBM sells Standard Edition into a range of industries beyond healthcare and government, where it is suitable for distributed authoring requirements requiring a lightweight registry-style solution. Increasingly, IBM positions Standard Edition in the context of a later upgrade to Advanced Edition if and when a physical system of record is required. IBM provided a good set of references for Standard Edition and they were generally very positive. Standard Edition achieved slightly above average customer satisfaction scores for performance, scalability and availability, and average scores for its understanding of the business application of its technology, understanding of the industry vertical and providing a stream of new technology innovation.
- Complexity and inconsistencies within the new InfoSphere MDM portfolio: At first sight, the IBM InfoSphere MDM go-to-market story is simple, there is one product with multiple editions. But as you look beneath the surface it gets more complex and the inconsistencies — in terms of underlying technologies, UIs and workflows — that result from three separate acquisitions become more obvious. These inconsistencies will continue to confuse and create complexity for prospects and current customers until the different editions are fully integrated from an external perspective and share common underlying services. In the meantime, organizations will need to carefully think through the implications of starting to manage customer data with a lightweight registry style if they want to move to a prepackaged data model with out-of-the-box business services at a later stage. This complexity also requires that prospects and clients work closely with IBM staff to ensure that the appropriate MDM editions are identified and acquired.
- Challenging future product convergence road map: IBM has shared a road map with its clients for how it will integrate the three prior MDM products into a single stack with three embedded MDM engines. IBM plans to provide a single database instance for all master data and metadata; a single application instance (within an application server container); a single services layer; a single installation, configuration, and maintenance layer, and a single UI layer for governance. This will be a multiyear journey as IBM provides increasing integration between the different "engines" and creates common shared services. Version 10.0 is a good first step, though it will probably take another couple of releases before it delivers a consistent user experience with seamless integration behind the scenes; in the interim, integration and standardization work is likely to consume significant development resources.
- Standard Edition is not positioned for transactional centralized style: Prior to its acquisition by IBM, Initiate Systems was steadily improving facilities
for customers to build up a data model and implement a more physical system of record
form of MDM. However, there was a change of strategy after the IBM acquisition. The
result has been that although Standard Edition is a very good product, it is limited
in scope and ambition and only targets a segment of the overall market. If an organization's
vision is to evolve its MDM capabilities over time — from a registry to a more physical
golden record approach — it would need to upgrade to Advanced Edition; IBM currently
provides two options:
- To run Standard Edition side-by-side with the InfoSphere MDM Server engine, and have Standard Edition act as an identity hub generating composite records for physical storage in the other instance.
- To "migrate" to the InfoSphere MDM Server engine, data model and services library.
- For Initiate MDS customers that hoped to leverage a single MDM product the future has become more complex and many are closely watching the road map.
- Multidomain implementations are limited and pricing clarity and resource availability are issues: Standard Edition's core competency is with party data, including customer data. It can potentially model other domains but, so far, has only done this opportunistically — typically in the context of specific industry requirements. Also, Standard Edition is targeted mainly at operational use cases and doesn't tend to be seen in analytical MDM use cases which typically require a physical system of record. IBM provided a full set of references for InfoSphere MDM Standard Edition. References scored Standard Edition's product capabilities at an average to above average level across the majority of categories, but gave below average marks for manageability and security facilities, as well as IBM's responsiveness to requests for new features. Several references reported substantial expense and scheduling issues in obtaining skilled consulting resources from IBM (with some attributing this to lack of a local presence with these skills), and a lack of transparency around IBM's pricing structure. While multiple references expressed a basic understanding of an interest in the newer product road map to Advanced Edition, they also voiced relief that Standard Edition is still being offered as a stand-alone product because they have no plans to upgrade in the near future.
Headquarters: Redwood City, California, U.S.
Informatica positions Informatica MDM (based on technology derived from the Siperian acquisition in 2010) under the moniker of Universal MDM, and claims the ability to handle all multidomain, multistyle, multideployment and multiuse requirements on a single platform. However, in September 2012 Informatica acquired Data Scout to provide Informatica Cloud MDM, a multitenant SaaS offering, based upon Force.com and specifically for salesforce.com users, and then on 1 October 2012 Informatica announced the voluntary public takeover offer for Heiler Software, a vendor of product information management (PIM) software. Informatica MDM together with Informatica's data integration and data quality tools offerings, make up the Informatica 9.5 Platform. Informatica MDM v.9.5 became generally available in June 2012. Pricing is by data domain, then the number of records per data domain. Informatica Data Controls Optoin costs extra and is licensed on the basis of the number of users.
Customer Base (licensed to manage customer data): Estimated at 195
- Informatica has good vendor viability and good MDM momentum: Informatica has good vendor viability and global reach. It had total company revenue of $783 million in 2011. It sees MDM as key to its growth strategy, is strongly promoting MDM and has been growing its MDM business with great success. It is increasingly able to cross-sell its MDM, data integration and data quality products and to sell multidomain MDM deals. We estimate that Informatica's 2011 MDM revenue was $79 million (a 32% growth rate), with revenue related to MDM of customer data of $65 million (a 26% growth rate). We also estimate that at the end of 1Q12 Informatica had a total of 204 licensed MDM customers, with 195 of them managing customer data, and that it had 147 customers licensed to master multiple data domains.
- Multiple industries and strong partner ecosystem: Informatica MDM has customers spread across many industries including financial services, retail and manufacturing, and has a particular strength in life sciences. Informatica is attractive to potential MDM service provider partners and it has several partners, such as Accenture, Capgemini, Cognizant and Wipro, developing both horizontal and vertical industry assets on top of Informatica MDM. Informatica is also a leader in supporting the packaging of design assets (for example, data models, data and integration services and UIs), from successful implementations by their clients and partners, for reuse as starting points in new implementations. The Informatica Marketplace, an online application store, is increasingly serving as a delivery vehicle for this collateral.
- Flexible MDM product capable of supporting multiple domains: Informatica MDM is a client-driven MDM solution with strength in flexible data modeling and hierarchy management. It supports multiple data domains, including party, product and location data, plus reference data, in a single product, but its core strength is managing party data. It has good proof points with B2C and B2B customers, and has several sites running very large volumes of customer records, indicating good performance and scalability. Informatica MDM supports both the registry implementation style (that is, match and link creating an index) and the implementation styles that instantiate a physical "golden record" in a single product. Most customers use coexistence style in a distributed authoring scenario.
- Continuing innovation: Informatica continues to innovate. For example, Informatica Data Controls provides a framework for developing MDM-based applets that can be embedded in existing applications. Informatica MDM is available in the cloud through partners in an IaaS deployment, and a multitenant SaaS deployment option in the public cloud is planned for 2013 — although for salesforce.com users the strategy now is to offer Informatica Cloud MDM based on the Data Scout acquisition. In the social networking area Informatica MDM 9.5 provides a prebuilt connector to Facebook which invokes a Facebook application, allowing the enrichment of internal master data with social data. Additionally, Informatica 9.5 provides location-based master data access functions on tablets and other mobile devices, and in the big data area there are plans to release a matching capability for Hadoop within the Informatica MDM product at end 2012. The longer term road map includes a facility called Semantic Master that creates a best version of the truth across structured and unstructured data.
- Behind the megavendors in terms of overall MDM revenue, customer base size and business process knowledge: Informatica is still significantly behind the megavendors — IBM, Oracle and SAP — in terms of overall MDM revenue and numbers of MDM customers. It cannot leverage the extensive customer bases or direct sales operations that the megavendors have, or their degree of account control. Nor can it leverage their breadth of solution set, or their depth of industry-specific business process knowledge, and it can't provide potential one-stop-shop integrated solutions across business applications (as in the case of Oracle and SAP), BI, middleware and database technologies. There are also concerns about Informatica's overall license revenue shortfalls in 2Q12 and 3Q12.
- The client-driven data model MDM story doesn't suit everyone: Although Informatica MDM provides a high degree of flexibility, it doesn't offer the same degree of industry-specific prepackaged data model, business services or internal workflow facilities that some other products provide. This could mean that organizations using Informatica MDM may expend more effort in building up functionality, rather than in configuring prepackaged facilities; it depends on how well the prepackaged facilities fit the requirements. Informatica does provide some horizontal and vertical industry templates, for example insurance and pharmaceuticals, as a way to start in the party data model area. The use of these templates is expanding and there is a plan to include preconfigured business rules and services, but there is still a way to go. Informatica Marketplace would be used to distribute these assets.
- Not universal MDM yet and product gaps need filling: Although Informatica MDM is a strong product and has made a lot of progress in the customer domain, it still has some way to go in meeting all the MDM requirements of every industry, every data domain, every use case, every implementation style and every organizational structure (that is, what Gartner calls multivector MDM). Although it has an increasing number of customers licensed for multiple domains, Informatica MDM's core competency is still in managing party data and its revenue and experience is heavily skewed toward that. It also needs to fix some basic MDM functionality issues. For example, although Informatica OEMs and embeds Fujitsu's Interstage BPM technology within Informatica Data Director it needs to go further in providing the preconfigured UIs and sophisticated collaborative workflow that business users need to author and manage many data domains, types of data and usage scenarios. It also needs to continue to evolve its data stewardship application capabilities.
- Customer references score well for company issues, but less well for some product issues: Informatica provided a full set of references and we had a good response rate. Overall (in the online survey), compared to last year, there was an improvement in customer satisfaction with its capabilities as a vendor — in areas such as understanding of the business application of the MDM solution and understanding of vertical industries — but there was a decline in some product-related issues. In particular, it was clear that the references are looking for a better UI application for data stewards, business users and IT users, for improved workflow facilities and for better monitoring, measurement and reporting on the status of master data quality. There was also feedback that real-time response times need improving.
Headquarters: Redwood Shores, California, U.S.
Oracle has a strong, though complex, portfolio of domain-specific MDM products that include prepackaged data models. Gartner estimates that Oracle now has over 1,500 licensed MDM customers, including 650 customers managing customer data. The MDM portfolio includes three products that address MDM of customer data solution needs: Oracle Fusion Customer Hub (FCH), Oracle CDH and Oracle Siebel UCM. These three MDM products are positioned for different segments of the market and Oracle is progressively moving all three products onto a common MDM technology platform, although the data models and other aspects of the solutions will remain different. Oracle CDH Release 12.1.3 became generally available in October 2011. We expect the next major release to become available in late 2012/early 2013. Pricing is available on Oracle's website and is shown as Oracle Customer Hub. For B2C, CDH is priced per person record; for B2B, per organization record. When CDH is co-deployed in an existing E-Business Suite (EBS) instance, the per-record pricing is reduced by 50%. Licensing any of the MDM of customer data solutions also gives organizations the rights to the others. Unlike in previous years, Oracle choose not to provide customer references for Oracle CDH this year.
In this Magic Quadrant we are evaluating Oracle CDH and Siebel UCM separately, because end-user organizations are faced with a choice between multiple Oracle MDM offerings that are positioned differently. Oracle CDH is targeted at existing Oracle EBS customers, whereas Siebel UCM is targeted at a much wider set of market segments and industries. Oracle FCH (which has been available since 1Q11) still doesn't meet our inclusion criteria (we estimate that its 2011 revenue was only $3 million) and is therefore not evaluated.
Customer Base (licensed to manage customer data): Estimated at 345
- Oracle has a strong MDM portfolio covering multiple data domains and use cases: Oracle has a broad range of MDM assets which organizations can leverage to manage multiple domains and use cases. MDM is strategic for Oracle and it had total estimated MDM revenue of $221 million in 2011. This represents a growth of 34% from 2010. We estimate that Oracle's 2011 revenue related to MDM of customer data was $103 million (versus $87 million in 2010), with Oracle CDH accounting for $25 million.
- Oracle CDH can be a good fit for EBS customers and can form part of a multidomain solution: Oracle CDH is specifically targeted at organizations with investments in Oracle's EBS applications, and particularly appeals to B2B product-oriented organizations. It can form part of a multidomain MDM solution, because CDH can be deployed with Oracle Product Hub, Supplier Hub and Site Hub in a single instance since it shares a common data model. Oracle is continuing the long-term development of Oracle CDH under the Oracle Applications Unlimited program and Gartner estimates that Oracle had 345 CDH customers at the end of 1Q12.
- Good packaged data model and improving functionality: Oracle CDH has a rich prepackaged party data model, derived from EBS. CDH is increasingly leveraging more components of Oracle Fusion Middleware (OFM) and the evolving standard MDM technology platform. The net effect is that the functionality continues to improve. For example, Oracle CDH r.12.1.3 leverages OFM 11g as the native applications server, GoldenGate real-time replication, and is starting to leverage Oracle Enterprise Data Quality (based on the Datanomics technology). Future versions plan to leverage MDM Analytics and the Data Governance Manager. Most implementations tend to be in the consolidation or coexistence styles.
- Customer references are generally happy: While no new information on references was submitted by Oracle for 2012, the status of the CDH product appears — based on our knowledge of the customer base and client inquiries — relatively consistent with what was reported by references in 2011. In the 2011 online survey, Oracle's references gave above-average customer satisfaction scores for sales and product support, understanding the business application of CDH, and meeting its clients' vertical industry MDM needs. Also in 2011, customers gave it a below average score when asked if the pricing structure made it easy to understand, predict and manage the future costs of usage. Oracle's references gave high marks to the CDH product for its integration and synchronization capabilities; manageability and security facilities; and performance and scalability. Multiple references reported performance issues when mastering over 100,000 customer records in the hub.
- Not the top selling product: From Gartner's viewpoint, Oracle CDH has taken second place to Siebel UCM for several years in terms of investment and sales and marketing focus. Now that Fusion Customer Hub is getting established in the market, we believe that it will also overtake CDH in terms of focus. Oracle CDH still has a large customer base, but growth in customer numbers had slowed significantly and maintenance revenue is increasingly important. In the short term, Oracle CDH remains a viable product for EBS customers, but in the long term CDH customers should plan for a migration to Fusion Customer Hub when it has gained greater maturity.
- Only sold to EBS users and low level of investment by third parties: Oracle CDH is only sold to EBS customers and therefore only addresses a segment of the market, so we seldom hear about Oracle CDH in open evaluations. Oracle tends to sell Oracle CDH in the manufacturing, hi-tech and retail industries, often with other MDM hubs and as part of a multidomain deal. It doesn't have a great deal of experience in industries like financial services, communications, life sciences and government. As a result, there is little investment by third-party external service providers (ESPs) in building vertical industry solutions on top of Oracle CDH.
- Functionality is behind best in class in several areas: Oracle CDH has fallen behind Siebel UCM and best-in-class vendors in a number of areas, including data quality technology, data governance facilities and support for hierarchy visualization and management. We haven't seen Oracle CDH win business in large transactional, centralized-style or registry-style environments and it needs a better collaborative workflow facility for centrally authoring data. There are no plans for multitenant SaaS deployment in the cloud or integration with social CRM and other aspects of Oracle's Customer Experience (CX) strategy.
- Investment is mainly focused on leveraging the standard MDM technology platform: Overall we aren't seeing innovation and Oracle's investments in Oracle CDH are mainly directed toward leveraging Oracle Fusion Middleware and Oracle's standard MDM technology platform. This will modernize the underlying technology and will add a degree of new functionality, such as better data quality tooling, where Oracle is increasingly leveraging and tightly integrating enterprise data quality. Although there is a increasing degree of convergence with Oracle's other solutions for MDM of customer data, Oracle CDH will remain based on the Trading Community Architecture (TCA) party data model and the EBS-era Oracle Applications Framework, as opposed to the newer Oracle Application Development Framework (ADF) that Oracle Fusion Applications and Oracle Fusion MDM uses.
Headquarters: Redwood Shores, California, U.S.
Oracle has a strong, though complex, portfolio of domain-specific MDM products that include prepackaged data models. Gartner estimates that Oracle now has over 1,500 licensed MDM customers, including 650 customers managing customer data. The MDM portfolio includes three products that address MDM of customer data solution needs: Oracle FCH, Oracle CDH and Oracle Siebel UCM. These three MDM products are positioned for different segments of the market and Oracle is progressively moving all three products onto a common MDM technology platform, although the data models and other aspects of the solutions will remain different. Licensing any of the solutions for MDM of customer data also gives organizations the rights to the others. Siebel UCM is Oracle's lead solution for MDM of customer data and UCM v.8.2 r.4 became generally available in February 2012. We expect the next major release to become available in late 2012/early 2013. UCM pricing is available on Oracle's website, where it is shown as Oracle Customer Hub. For B2C, UCM is priced per person record; for B2B, per organization record. There are also a number of options with UCM. When UCM is co-deployed in an existing Siebel CRM instance, the per-record pricing is reduced by 50%.
In this Magic Quadrant we are evaluating Oracle CDH and Siebel UCM separately because end-user organizations are faced with a choice between multiple Oracle MDM offerings that are positioned differently. Oracle CDH is targeted at existing Oracle EBS customers, whereas Siebel UCM is targeted at a much wider set of market segments and industries. Fusion Customer Hub (which has been available since 1Q11) still doesn't meet our inclusion criteria (we estimate that its 2011 revenue was only $3 million), so is not evaluated.
Customer Base (licensed to manage customer data): Estimated at 285
- Oracle has a strong MDM portfolio covering multiple data domains and use cases: Oracle has a broad range of MDM assets which organizations can leverage to manage multiple domains and use cases. MDM is strategic for Oracle and it had a total estimated MDM revenue of $221 million in 2011. This represents a growth of 34% from 2010. We estimate that Oracle's 2011 revenue related to MDM of customer data was $103 million (versus $87 million in 2010), with Siebel UCM accounting for $76 million. Siebel UCM can be complemented by other Oracle MDM products, such as Oracle Product Hub, Oracle Supplier Hub, Oracle Site Hub and Oracle Hyperion DRM to enable management of multiple master data domains and use cases.
- Siebel UCM is still the best selling product in the MDM portfolio: Siebel UCM is still Oracle's best selling solution for MDM of customer data and is the most important offering in Oracle's entire MDM portfolio on the basis of product revenue. It has continuing market momentum and benefits from significant R&D investment. UCM supports Oracle's CX strategy and the industry solution product lines for financial services, telecommunications, media, utilities, large-scale retail and government. UCM appeals to organizations, especially B2C organizations, with long-term strategic commitments to Oracle applications and technology — especially if they have Siebel CRM.
- Strong momentum, verticalization and proven scalability: Oracle continues its success in selling Siebel UCM, and we estimate that Oracle had 285 UCM customers at the end of 1Q12. Siebel UCM has an impressive number of commitments from blue-chip names across geographies and industries, with particular strength in telecommunications, hi-tech and the public sector, and increasing strength in financial services. Oracle can provide a good number of references and UCM has impressive performance and scalability — including live transactional workloads managing more than 100 million consumers. Oracle has vertical industry variants of Siebel UCM, such as airlines, public sector social services, life sciences, healthcare, higher education and wealth management, either through its own developments or with partners.
- Multiple solutions for MDM of customer data, including Oracle Fusion MDM: Oracle has three offerings in the market for MDM of customer data; Oracle Fusion MDM, Oracle CDH and Siebel UCM. Oracle is careful to position these differently, but it is a complex situation that can be confusing for prospects and sometimes Oracle makes general claims — such as multidomain and SaaS capability — that don't apply to all products. Although Siebel UCM is currently the lead product, by 2014 Oracle Fusion MDM is likely to have become Oracle's premier MDM product for customer data. Gartner believes that many Siebel UCM customers will never migrate to Oracle Fusion MDM, but those new and existing customers who do want to eventually migrate should mitigate the disruption by leveraging the latest UCM releases which increasingly build on the standard MDM platform and OFM. Oracle's stated strategy is one of coexistence between Siebel UCM and Oracle Fusion MDM.
- Good party model for customer data, but not designed for multidomain: Siebel UCM is based on a good party model, although Oracle claims that Fusion Customer Hub's party model is better and Siebel UCM does not support "thing" or "place" data to an extent that would allow it to be the basis of a broad multidomain MDM strategy. The Oracle strategy is to provide packaged MDM hubs on a data domain basis, so to achieve support for multiple data domains organizations would have to purchase MDM products based on different technologies and residing in different instances. Also, Siebel UCM is behind the best-in-class products in providing out-of-the box collaborative workflows for authoring data, potentially required for managing business customer data, although Oracle BPM Suite is preintegrated with Siebel UCM for SOA-based business processes. Finally, UCM supports a range of architectural styles, but it lacks sufficient proof points for "virtual" registry-style implementations — where only an index is created and managed.
- Packaged data model doesn't appeal to everyone and still has some gaps: Siebel UCM comes with a rich prepackaged data model and set of business services. For many organizations, especially those that have Siebel CRM, it is a good fit for their requirements. However, other organizations want a client-driven data model approach and don't feel that UCM provides the level of flexibility that they want. Data Governance Manager provides monitoring and profiling facilities, but like other MDM vendors Oracle still has more work to do in governing master data throughout the life cycle. On the data quality technology front, Oracle will continue to depend on one of its closest MDM competitors, Informatica, until the data quality tooling based on the Datanomic technology matures further. Finally, UCM is not available in a multitenant version for SaaS in the cloud and, although there is increasing convergence with Oracle Fusion MDM, UCM will always be based on a different data model and a range of different technologies including the Siebel Application Server, Siebel Tools and the new Siebel UI.
- Customer references scored below average in several non-product-related areas: Oracle provided a full set of references for UCM. Oracle's references appear generally happy with UCM's product capabilities. In the online survey, Oracle earned average customer satisfaction scores for understanding the business application of UCM and its clients' vertical industries, for road map visibility and for continuous technology innovation. However, Oracle scored below average for responsiveness to new feature requests and understanding of master data governance. Oracle's references also gave it below-average marks when asked if the pricing structure made it easy to understand, predict and manage the future costs of usage. The product also scored below average for reporting of master data quality metrics. Oracle scored in line with the average for sales support and after-sales care, but below average for organization and process change management support.
Headquarters: Paris, France; U.S. Office: Boston, Massachusetts, U.S.
Orchestra Networks' EBX platform provides multidomain data-modeling facilities, based on a semantic approach, including the ability to create and manage complex hierarchies in a workflow usage pattern. EBX v.5.2 can also support relational schemas for higher volume transactional usage patterns. The product has been more widely used for product and internal organization data, but now the number of organizations using it to manage B2B customer master data is growing and it has an innovative hybrid architecture for tackling both workflow and transaction-oriented requirements. Pricing is based upon the number of MDM instances, for example one instance for production and another for development.
Customer Base (licensed to manage customer data): Estimated at 28
- Flexible data model with multischema support: Orchestra Networks' EBX platform provides flexible, browser-based and very accessible data modeling facilities for both creation and maintenance functions — based on XML schemas. The latest release of EBX5 can also support relational schemas for higher-volume, transactional usage patterns which are typical with MDM of B2C customer data use cases. The two schema modes may also be used in combination in a single hub instance. EBX contains native support for data versioning to support "as of" data access, as well as robust version management for the data model itself.
- Good workflow, multidomain and hierarchy management capabilities: Orchestra Networks' MDM business was initially based mainly on managing product and employee data, but now an increasing number of customers are managing customer master data (particularly in the B2B space), mainly in a workflow-oriented operational MDM use case with central authoring. EBX's powerful hierarchy management and workflow capabilities have led to its use as the B2B customer MDM tool of choice in several organizations, even in cases where a different vendor has been selected as the B2C customer MDM tool. The ability to support both the semantic (XML) and relational schemas in a single instance is directly applicable to multidomain scenarios, where the appropriate schema type could be used for each domain: for example, using the XML schema to manage product data and the relational schema to manage B2C customer data.
- Strong in France and growing customer base in North America: Orchestra Networks has a strong client list in France, and an increasing amount of its revenue comes from North America — particularly in the financial services vertical. Gartner estimates that at the end of 2011 Orchestra Networks had a total of 75 licensed MDM customers. We estimate that it has 28 customers managing customer data, four managing supplier data, 24 managing human capital data, 12 managing location data, 47 licensed to manage product data, eight managing asset data and 22 managing financial data. We estimate that Orchestra Networks has 60 customers licensed for multiple data domains. We estimate that Orchestra Networks' total 2011 MDM revenue was $10.7 million, with $4.2 million for MDM of customer data.
- Attractive pricing model and cloud-based deployment option: Unlike many MDM software vendors, Orchestra Networks does not charge for its software based on the number of source data records being mastered in an on-premises deployment. EBX is generally licensed on a per-instance basis (with graduated charges based on whether instances are production or development), with per-project licenses being sold for smaller initial implementations focused on particular initiatives. This typically has the effect of bringing EBX's average initial cost to the client to a point lower than the market average. Orchestra also offers a cloud deployment option, smartdatagovernance.com, which starts at a reasonable subscription price (although there is a per-source record component that should be considered) and is based on the same EBX software used for on-premises implementations — making it easier to move to on-premises should the client desire to do so.
- Still a small player in the MDM of customer data market: Even with some significant recent gains, Orchestra Networks remains a relatively small vendor in the MDM marketplace, and particularly in the market for MDM of customer data. This means that there is a higher viability risk and, due to its functional capabilities, it could become an acquisition target for some of the larger vendors if they perceive some of EBX's technology as filling functional gaps in their own products. Also, Orchestra Networks does not have a global presence, being mainly present in France, the U.K. and the U.S., or in-depth resources and a partner network.
- Needs more experience with B2B and is relatively unproven in large-scale B2C: Although clearly gaining traction in verticals with robust B2B customer data MDM requirements, Orchestra Networks has only recently started to directly address the needs of the B2C customer data market: which often has high data volumes, and less complex data models and transactional usage patterns. The dual-mode object cache and relational capability in EBX5 are designed to meet these needs. Orchestra Networks needs to build up experience with this new facility and this new market segment, including concentrating more on B2C-centric data services requirements (such as robust matching and merging) either natively or via best-of-breed vendor partners, as well as the emerging adjacent areas of integration with social data and mobile access to master data.
- Behind best in class in some aspects of MDM of customer data solution functionality: EBX can leverage third-party data quality tools, but for matching it uses its own algorithms. These are less capable than the matching provided by leading data quality tools. Although Orchestra Networks can provide some references with high data volumes, these are generally not for B2C customer data and do not require many of the native functions and use-case fulfillment of a true B2C implementation — such as robust matching algorithms and merge management in a high volume environment.
- Weak references for mastering customer data: Orchestra Networks was able to provide several references mastering party data, but on further interaction with these contacts it became apparent that several of these were not conventional customer data. Moreover, it is clear that EBX installations for customer data are still firmly planted in the B2B arena (and in hierarchy management within that), although the potential for growth in the B2C market is evident. The few references that responded to the online survey gave Orchestra Networks average scores for its understanding of the business application of EBX and vertical industry requirements, and above-average marks for transparency of pricing structure and support for data governance — as well as for its sales and support processes. They gave EBX above-average customer satisfaction scores for data modeling and hierarchy management, its data stewardship use interface, and for manageability, security and availability. These same references scored EBX as below average for monitoring, measurement and reporting on the status of master data quality.
Headquarters: Walldorf, Germany
SAP's Enterprise MDM portfolio includes Master Data Governance (MDG) and NetWeaver MDM and it plans to introduce a third product, called Master Data Services (MDS), into ramp up in 4Q12. The products are typically purchased as part of an Enterprise MDM bundle, and SAP Data Services and SAP Information Steward complement both NetWeaver MDM and MDG. MDG has been developed in-house within SAP and it has finance, material, vendor and customer variants, with SAP MDG EhP6 — including MDG-Customer (MDG-C) — becoming generally available in May 2012. Pricing metrics for MDG include data domain type, number of records and usage scenario.
In this Magic Quadrant we are evaluating MDG and NetWeaver MDM separately because end-user organizations are faced with a choice between multiple SAP offerings that are positioned differently. Initially, MDG was positioned as an application-specific data stewardship application for managing application data in SAP's Enterprise Resource Planning (ERP) application, and was seen as complementing NetWeaver MDM. However, now the majority of MDG deployments also use it as a stand-alone MDM hub to create and maintain master data and other ERP data centrally. It provides an alternative to NetWeaver MDM, which is now positioned as a multidomain MDM solution capable of consolidating and harmonizing master data where there is distributed authoring.
Customer Base (licensed to manage customer data): Estimated at 150
- Large and loyal user base looking for one stop shopping: SAP has a large and loyal user base, particularly in product-oriented industries. Many of these organizations are looking for a single vendor to supply them with core business applications and application infrastructure. Unlike NetWeaver MDM, MDG is a homegrown MDM solution from SAP based on Web AS ABAP and is more immediately familiar to the long term SAP user. Although new, MDG-C has made a fast entry into the market and has gained rapid acceptance from SAP users. We estimate that SAP has already licensed MDG-C to approximately 150 customers and already has approximately 10 live implementations. We estimate that MDG-C in stand-alone hub form generated revenue of $6 million in 2011 and this revenue is growing rapidly.
- Excellent integration with SAP's ERP application and technologies: MDG provides native integration with SAP ERP and leverages the SAP ERP Business Partner data model, the ERP UI, and the existing ERP business logic and configuration for creation and validation of ERP data — including master data. It also leverages SAP Data Services for data quality and data enrichment, and SAP's Business Rules Framework (BRF+), and organizations can use Business Add-Ins (BAdIs) to include custom ABAP code in MDG's processes. Organizations can use SAP's Data Replication Framework (DRF) to distribute the master data, life cycle support is provided by SAP Solution Manager and there is integration via Application Link Enabling (ALE) and NetWeaver Process Integration (PI) — but not with SAP NetWeaver BPM.
- Multidomain MDM capability with extensibility, focused on central authoring: SAP leverages the MDG Application Framework to create its own data-domain-specific MDG offerings, but it is also available to customers for them to extend the predelivered data models and to build their own MDG applications based on their own master data models. Unlike NetWeaver MDM, MDG is based on a relational model and can leverage relational facilities better. SAP also plans to port it to its Hana database (in addition to making MDS available on Hana). It is designed to support centralized authoring, either through its own internal workflow (with versioning and staging areas) or, potentially, in a transactional manner through Web services.
- Good data quality and data stewardship capabilities, plus UI choice: MDG leverages other SAP technologies and standards. For example, integration with SAP Information Steward provides data profiling and dashboarding facilities and there is tight integration with the SAP Data Services matching engine. There is a choice of UI between the SAP Enterprise Portal and the SAP NetWeaver Business Client. SAP MDG uses its native workflow capability to route approvals for master data changes within the master data process itself, and can also be part of cross-enterprise business process workflow managed by SAP NetWeaver BPM.
- Confusing MDM portfolio and MDG-C is still young in the market: SAP now positions the two products, NetWeaver MDM and MDG-C (based on different core technologies) for different parts of the MDM market, and MDS will be positioned for yet another part of the MDM market. MDG-C is positioned not just as an application-specific data stewardship tool for SAP ERP, but can also function as a stand-alone MDM hub suitable for workflow-based central authoring of ERP or master data, or both. The result is some confusion within the SAP customer base as organizations try to work out which SAP product, or which combination of products, will best meet their needs and, if they choose MDG, whether to implement as a stand-alone hub or co-deploy it with SAP ERP. SAP has been steadily extending the scope of MDG since it first appeared in 2010 to manage financial master data, but MGC-C, the prepackaged variant that manages customer data, only became generally available in 1Q12.
- Mainly appeals to SAP customers, but still immature: MDG-C will only appeal to SAP-centric organizations with investment in SAP's Business Suite. The degree of integration with SAP ERP and associated technologies is positive for committed SAP customers, but it is unlikely to be a contender in non-SAP-centric heterogeneous environments because it would need to be agnostic with respect to application data models and integration technologies. MDG-C can integrate indirectly (via SAP ERP) or directly with SAP CRM, although neither is the classic MDM hub-and-spoke architecture due to the dependency on SAP ERP. Due to its newness, it has not yet been leveraged to provide industry variants and there isn't a strong partner ecosystem building assets on top of it.
- Not designed for distributed authoring and functionality gaps: MDG-C is not designed to support distributed authoring situations that require consolidation and harmonization of the data (unlike NetWeaver MDM and MDS). It is also not designed for transaction-oriented, centralized implementation style requirements in high-volume B2C use cases: as are often seen in financial services, communications and government. Although cloud, social and mobile are present in SAP's overall vision, SAP MDG-C is not available in a multitenant form for MDM SaaS and there is no prepackaged leveraging of social data yet. Finally, it needs to continue to improve the prepackaged facilities for data stewards to manage the life cycle of master data.
- Needs more in-depth customer references: SAP didn't provide a full set of references for MDG-C because it is still relatively new. There are live customers, but we didn't have the opportunity to talk with them. While there appears to be a significant degree of interest in MDG on the part of the current SAP ERP customer base (including those clients already using NetWeaver MDM), we also hear concerns from current NetWeaver MDM clients that have significant investments in process orchestration with NetWeaver BPM and now see much of this master data life cycle maintenance functionality provided by MDG's native workflow.
Headquarters: Walldorf, Germany
SAP's Enterprise MDM portfolio includes MDG and NetWeaver MDM and it plans to introduce a third product, MDS into ramp up in 4Q12. The products are typically purchased as part of an Enterprise MDM bundle and SAP Data Services and SAP Information Steward complement both NetWeaver MDM and MDG. Historically, NetWeaver MDM (which is based upon technology from the A2i acquisition in 2004) has been SAP's lead MDM offering and used to be positioned as a multidomain MDM solution that met all MDM requirements. The latest version of NetWeaver MDM, v.7.1 SP08, has been generally available since October 2011. However, since MDG-C became generally available in 1Q12, SAP has changed the positioning of NetWeaver MDM and MDG appears to have become the lead offering. Pricing metrics for NetWeaver MDM include data domain type, number of records and usage scenario.
In this Magic Quadrant we are evaluating MDG and NetWeaver MDM separately because end-user organizations are faced with a choice between multiple offerings that are positioned differently. Initially, MDG was positioned as an application-specific data stewardship application for managing application data in SAP's ERP application, and was seen as complementing NetWeaver MDM. However, the majority of MDG deployments now also use it as a stand-alone MDM hub to create and maintain master data and other ERP data centrally. It provides an alternative to NetWeaver MDM, which is now positioned as a multidomain MDM solution capable of consolidating and harmonizing master data where there is distributed authoring.
Customer Base (licensed to manage customer data): Estimated at 770
- Large and loyal user base looking for one-stop shopping: SAP has a large and loyal user base, particularly in product-oriented industries. Many of these organizations are looking for a single vendor to supply them with core business applications and application infrastructure. SAP estimates that it has licensed NetWeaver MDM to over 1,700 customers, up from over 1,400 in mid-2011. It also claims that approximately 770 of those MDM customers are licensed to manage customer data and that there are 290 live implementations managing customer data. We estimate that SAP had revenue related to MDM of customer data of $37 million (out of a total MDM software revenue of $187 million) in 2011.
- Leverages other SAP technologies: SAP has brought its various information management assets together under the EIM banner, and it sees NetWeaver MDM as a key part of that strategy. NetWeaver MDM is also one of the key Orchestration technologies that enable both the mainstream, on-premises Business Suite applications and the newer, on-demand applications, such as Business ByDesign. NetWeaver MDM leverages other parts of the EIM portfolio, such as SAP Information Steward which is designed to help organizations understand and analyze the trustworthiness of their information and SAP Data Services — a strong data quality tool.
- Flexible, multidomain MDM capability with mainly B2B experience: NetWeaver MDM has a flexible, customizable, domain-neutral data model and a large number of multidomain references. It provides a prepackaged version of the Business Partner data model — as found in Business Suite, and the older Customer data model from SAP ERP, and includes its Rapid Deployment Solution for customer data integration (CDI) which is composed of a set of bundled software and services. Most of NetWeaver MDM's experience is with managing B2B business partner data in consolidation and coexistence styles with distributed authoring, or in workflow-oriented, centralized-authoring situations.
- Good data quality, UIs, workflow and custom data stewardship: SAP has leveraged other SAP technologies and standards. For example, NetWeaver BPM, which includes the business rule engine, is leveraged to provide a sophisticated workflow capability for collaborative authoring and data stewardship. Also, NetWeaver MDM can now generate Web-based data stewardship UIs for business users that are based on Web Dynpro and do not require the SAP Portal. There is tight integration with BusinessObjects' Data Services matching engine and leverage of other BusinessObjects' technologies for dashboarding and reporting, and data quality. In the online survey, SAP and NetWeaver MDM received above average scores for SAP's understanding of the business application of NetWeaver MDM.
- Momentum slowing as MDG-C enters the market: Where once SAP positioned NetWeaver MDM as meeting all needs for MDM of customer data, it now positions the two products (NetWeaver MDM and MDG-C) based on different core technologies for different parts of the market, and it will soon introduce a third product (MDS) for high-volume consolidation implementation-style requirements. NetWeaver MDM is now positioned for distributed authoring situations requiring data consolidation and harmonization; MDG-C is now positioned not just as an application-specific data stewardship tool for ERP Central Component 6.0 (ECC6), but also a stand-alone MDM hub suitable for workflow-based central authoring. The result is some confusion within the SAP customer base as organizations try to work out which product or which combination of products will best meet their needs, and what to do about their existing investments in NetWeaver MDM and associated workflow assets. Another result is that SAP's sales momentum around NetWeaver MDM has slowed and we estimate that revenue related to MDM of customer data for NetWeaver MDM in 2011 was $30 million, versus $38 million in 2010.
- Mainly appeals to SAP customers and has restricted B2C support: NetWeaver MDM mainly appeals to SAP-centric organizations that have bought into the company's application and application infrastructure vision. SAP makes few shortlists in non-SAP-centric heterogeneous environments. In addition, NetWeaver MDM isn't currently suitable for supporting high-volume, transaction-oriented B2C use cases (with centralized authoring or registry style) in financial services, communications and government. To meet this requirement, SAP was planning to introduce a port of NetWeaver MDM on its Hana in-memory database management system (DBMS), but has now decided to create a totally new product, MDS, for that purpose instead.
- Functionality continues to improve, but is still not best in class: SAP has significantly improved NetWeaver MDM over the past few years, though some customers say that it has made the product too complex and heavy in infrastructure terms and that the nature of the in-memory object model makes it difficult to build out complex hierarchies and difficult to leverage the data externally. SAP needs to continue to improve the prepackaged facilities for data stewards to manage the life cycle of master data, by integrating Information Steward. Although cloud, social and mobile are present in SAP's overall vision, NetWeaver MDM is not available in a multitenant form for MDM SaaS and there is no prepackaged leveraging of social data yet. Finally, although SAP is now offering initiative-specific QuickStart packages, such as for physician marketing spend analysis, it doesn't have a strong partner ecosystem building assets on top of NetWeaver MDM.
- Customer references scored below average in several areas: In the online survey, its references gave above-average customer satisfaction scores for sales process support, data quality facilities and UI functionality, although SAP received below-average marks for new user training and onboarding. SAP received above-average marks for its understanding of the business application of MDM for customer data (including governance) and road map visibility, and average scores for understanding its references' vertical industry MDM needs, providing a continuous stream of technology innovation, new feature responsiveness, and total cost of ownership (TCO). SAP received below-average ratings for pricing transparency, internal workflow capability and its ability to monitor, measure and report on master data quality.
Headquarters: Cary, North Carolina, U.S.
Under the DataFlux brand, SAS Institute offers three alternative approaches to MDM:
- Build — Leveraging DataFlux Data Management Platform.
- Template driven — Leveraging DataFlux MDM Foundations, which comprises selected components of the DataFlux Data Management Platform plus added capabilities to deliver a single domain batch-based hub.
- Buy — Leveraging qMDM, the full MDM product.
In this Magic Quadrant we focus on the qMDM packaged MDM of customer data solution, although it is also possible to deploy a limited MDM solution using MDM Foundations. Version 3.1 of qMDM became generally available in June 2012, and SAS operates a subscription software licensing model. Pricing varies according to the complexity of the implementation.
Customer Base (licensed to manage customer data): Estimated at 46
- Strong company and continuing focus on MDM: DataFlux, which used to operate with a great deal of autonomy, is now fully integrated into its parent company SAS Institute. DataFlux is kept as the brand for SAS's data management technologies. The DataFlux R&D and professional services teams have been fully integrated into their SAS counterparts. The management consulting arm and thought leadership group (both acquired through the 2011 acquisition of Baseline Consulting) continue to operate independently. SAS will exercise greater control over DataFlux-centric marketing, sales, consulting and product development activities, and SAS's larger and more global sales force will potentially be able to ramp up the sales of the DataFlux branded products. There is also the potential to generate synergy between the DataFlux MDM products and SAS solutions and analytic applications.
- Broad product set across data quality, data integration and MDM: The qMDM package is based on the DataFlux Data Management Platform, which provides an integrated set of data quality and data integration technologies. The idea of an integrated product set covering data quality, data integration and MDM will be an attractive proposition to many organizations. SAS is a leader in the data quality tool market (see "Magic Quadrant for Data Quality Tools") and in the data integration tools market (see "Magic Quadrant for Data Integration Tools"); however, it has yet to achieve such substantial penetration in the packaged MDM solutions market. DataFlux had more than 3,200 customers, mostly for data quality tools. The focus on MDM is increasing and SAS claimed to have 196 MDM customers at the end of 1Q12. However, half of these customers are leveraging the simpler MDM Foundations product and we estimate that only 77 customers are using the qMDM package, with 46 of them managing customer data.
- Graduated approach to MDM: SAS offers organizations a graduated approach to deploying MDM infrastructure, providing data quality and data integration tools to enable a customized build approach, batch-based MDM support for a single data domain with the Master Data Foundations bundle, or the more advanced packaged qMDM solution, depending on the organization's maturity in data management and governance. This enables an organization to start relatively small and to evolve toward addressing more challenging MDM needs, which can be useful when an organization has resource constraints or doesn't feel ready to tackle the data governance challenges of full-blown MDM.
- Continuing investment and steadily improving product: SAS's qMDM product shows continuing investment, and is an increasingly capable product for MDM of customer data. It has a flexible entity-based data model that can potentially be leveraged to model multiple data domains, though DataFlux has the most experience with customer data. The qMDM product has excellent data quality and data-profiling facilities, and includes a business rule engine. It has good dashboarding, monitoring and reporting facilities. There are plans to integrate qMDM further with the DataFlux Business Data Network metadata capability and DataFlux Federation Server. The strengthened relationship with the SAS R&D organization, known for building sophisticated analytics tools, has the potential to bring further robustness and maturity to the DataFlux tools.
- SAS is best known for analytics and DataFlux was still small in the packaged MDM solutions market: Whereas DataFlux had enjoyed great success with its data quality products in both operational and analytical use cases. SAS is mainly known for its analytics and doesn't have the typical background of the major players in the operational MDM market. Also, before it was consolidated into SAS, DataFlux hadn't achieved nearly the same impact in the MDM market as it had done in the data quality tools market. It was more comfortable with these tools markets and a component-based build approach to MDM, rather than selling a packaged MDM solution. We estimate that DataFlux's 2011 revenue from solutions for MDM of customer data, for operational MDM, was only $4.2 million; well behind the market share leaders, though the increased marketing focus and integration in SAS is starting to increase the deal flow.
- Not all customer references were for qMDM and qMDM references rated many capabilities as below average: SAS provided a full set of references, but almost half were based on implementations leveraging its data quality tools (DataFlux Data Quality Integration Platform) and taking a "build" approach, as opposed to the implementation of the packaged qMDM solution. In the online reference survey, qMDM received below-average scores for its data modeling and hierarchy management capabilities; its data stewardship UI; its integration and synchronization capabilities; internal workflow; performance and scalability; monitoring, measurement and reporting on the status of master data quality; support for multiple use cases; and native support for the information architecture role.
- Some functionality gaps, needs to prove transactional capability: Relative to best-in-class vendors, DataFlux still needs to provide greater life cycle management around the data model. There are plans to improve hierarchy management capabilities and some components of the Master Data Manager UI in a 2012 release. Most qMDM implementations are consolidation and coexistence style, and although DataFlux has begun some larger transactional implementations, they are not yet fully live. To compete with the strongest players in the market, it needs to demonstrate qMDM across a range of implementations and vertical industries. It lags behind other vendors in terms of internal workflow and integration with BPM systems, and multidomain experience. Also, it hasn't shown innovation in the areas of MDM applets, cloud deployment and MDM and social data.
- Needs to demonstrate global execution and stronger partnerships: SAS's international MDM revenue continues to rise; however, it still needs to demonstrate its ability to execute as a strong global player in the market for MDM of customer data solutions. We don't hear of qMDM on many shortlists; competitors rarely mention it and ESPs don't often talk of having projects with qMDM, nor are they building assets on top of qMDM. In addition to providing its own professional services, SAS needs to leverage its substantial partner network to assist in more complex MDM implementations and to build up mind share.
Headquarters: Palo Alto, California, U.S.
Tibco Software's positioning is to enable real-time visibility, understanding and action. It sees its MDM technology as part of a platform — together with middleware, analytics, BPM and data quality — that enables business optimization and real-time intelligence. It offers an MDM product currently called Tibco Collaborative Information Manager (CIM). CIM v.8.2.1 became generally available in December 2011 and v 8.3, which will be rebranded as Tibco MDM, is due for release in December 2012. The Tibco CIM product was originally developed as a solution for MDM of product data, but it has evolved into a multidomain MDM system and is suitable for centralized authoring and collaborative workflow and real-time transactional scenarios. Pricing is both per CPU and per named user, and both project-based and enterprise licenses are available. A single license covers all data domains, unless specifically restricted within the contract.
Customer Base (licensed to manage customer data): Estimated at 54
- Leveraging the Tibco customer base and overall value proposition: Tibco had total company revenue of $920 million in 2011 and we estimate that it has over 4,000 customers in total. It is able to leverage that base for MDM sales. Tibco is best-known for its SOA middleware, such as its enterprise service bus (ESB), and BPM. Its vision is focused on enabling interactions and business processes and gaining "the two second advantage," and this means that foundational capabilities like MDM and analytics are essential. It usually sells Tibco MDM as part of the overall value proposition around integration, BPM and analytics. Tibco is also increasingly selling its MDM technology as part of an integrated loyalty system and real-time analytics and decisioning solution based on customer master data.
- Increased internal visibility for MDM: Tibco has realized the importance of MDM. It now has high-level visibility within the company, and is seen as a strong growth opportunity. We estimate that in 2011 Tibco's MDM of customer data revenue grew by over 100%. The majority of customers use Tibco CIM to manage product data, but it is increasingly being used to manage customer, organization, counterparty and employee master data. In the area of MDM of customer data, Tibco MDM has had particular success in the telecom industry, in retail and consumer packaged goods, and in the gaming and hospitality sectors. Tibco now has 223 customers licensed for Tibco MDM, including 54 licensed to manage customer data. Although not enough customer references responded to our reference checking, those that did respond gave good marks for both vendor- and product-related issues.
- Flexible multidomain product, with good workflow: Tibco CIM is a multidomain MDM system, with flexible client-driven data modeling, strong workflow and process-modeling capabilities for collaborative central authoring of data. It can also be called by external BPM tools, such as Tibco ActiveMatrix BPM, and is increasingly being used in real-time transactional scenarios. Tibco MDM supports survivorship and versioning. Tibco is starting to provide prepackaged data model templates, both horizontal (for example, a B2C party model) and vertical (for example, a telco model). It is also having sales success with prepackaged BPM and MDM solutions such as its Concept to Cash solution for telcos.
- The product continues to improve: Tibco CIM v.8.2 included major improvements in the data quality area with the embedding of the Netrics matching engine and the integration of Trillium Software's data profiling, cleansing and standardization technologies. Version 8.2 also contained improvements to MDM Studio (Tibco's Eclipse-based data and process modeling environment), making modeling more graphical and real time. There was also increased use of Spotfire, to provide MDM data discovery facilities, and an analytics dashboard called Visual MDM. Tibco is providing strong innovation in the MDM area. For example, master data can be cached in Tibco ActiveSpaces, an in-memory data grid, and in the longer term there is a plan to use ActiveSpaces to host an in-memory master data database. Tibco is providing integration with social networking sites, both external (such as Twitter) and internal (such as Tibbr), though this is not yet productized, and smartphones and tablet devices can now be used for data stewardship and life cycle management processes.
- A growing, but still a relatively small presence in the market: Tibco CIM is positioned for multidomain MDM and historically most of its experience and revenue was related to managing product data. The number of Tibco MDM implementations licensed to manage customer data is increasing, but Tibco still has further to go to compete with the market leaders. With an estimated total MDM revenue of $51 million in 2011, Tibco's revenue related to software for MDM of customer data, of $15 million in 2011, is still small compared to the market share leaders. Although Tibco increasingly aims to sell to the business with an overall business value proposition, it still positions itself as a supplier of infrastructure and there is more work to do in reaching both the business audience and the information management audience. Lastly, Tibco seems behind in the strength of its ESP relationships, both for generating business and for the creation of assets on top of Tibco MDM, and although it is bringing out vertical industry templates it is again behind the leaders in this area.
- Needs more references performing transactional usage: Tibco CIM was originally built for workflow-style, central-authoring scenarios. It leverages an in-memory object model with application level, as opposed to relational DBMS (RDBMS) level, locking, concurrency control and transaction logging. Tibco has clear ambitions to address demanding real-time operational environments with Tibco CIM and this aligns with the company's vision. However, although Tibco now has CIM customers that are managing very large volumes of customer data this tends to be in a consolidation or coexistence implementation style. There a few customers leveraging Tibco CIM in high-volume transactional scenarios with central authoring, but Tibco needs to generate a larger set of public references in this area to give stronger proof points.
- Behind in functionality terms in some areas: Tibco CIM v.8.2 improves the product, but it is still behind best-in-class products for MDM of customer data in a number of areas. For example, although the use of Spotfire has improved the hierarchy visualization, profiling, dashboarding and out-of-the-box reporting, there is room for further improvement — such a providing a better out-of-the-box UI and better workflow-based authoring and data stewardship capabilities. There are plans for this in the forthcoming 8.3 release and beyond. Additionally, although the Visual MDM capability has the potential to be a differentiator, it has only fairly recently been aggressively marketed to clients or prospects. There needs to be greater consistency between UIs and workflow/BPM engines. Tibco seems to have no strategy for provision of MDM applets. Lastly, Tibco does not promote any strategy for MDM in the cloud, because it doesn't currently see the demand, but it claims that Tibco CIM has had a multitenancy capability for a long time and that this can be leveraged in private clouds with Tibco Silver Fabric.
- Still needs a stronger set of customer references: Tibco's references for solutions for MDM of customer data are a great improvement on last year (in terms of numbers, the level of response to the online survey and the customer satisfaction scores in the online survey) and customers are speaking about their MDM experiences at the TUCON customer event. However, we would still like to get positive feedback from more references across a range of different uses cases and scenarios (particularly high-volume transactional scenarios) to be able to conclusively report that Tibco and its CIM product are successfully meeting organizations' requirements across that range of use cases and scenarios.
Headquarters: Glasgow, U.K.; U.S. Office: Newton, Massachusetts, U.S.
VisionWare is a small MDM vendor offering the MultiVue product that leverages Microsoft technologies, such as .NET, Silverlight and SQL Server. The MultiVue v.3.1 product is positioned for operational MDM and was made generally available in February 2012. MultiVue is priced according to the industry, commercial or public sector, and type of opportunity. There is a base MultiVue license plus additional costs based on the number of source applications, without restriction on the number of records or users.
Customer Base (licensed to manage customer data): Estimated at 85
- Attractive MDM solution for Microsoft users: VisionWare's products are attractive to resource-constrained organizations that are Microsoft-centric. MultiVue is based solely on Microsoft technologies, such as .NET, SQL Server and BizTalk. The company has very competitive pricing and its MDM products are mainly used to manage information on individual parties and households, as opposed to businesses. It has little competition in this Microsoft-centric part of the MDM of customer data solutions market, except Microsoft itself — for those enterprises wanting to build on Master Data Services (MDS) — and Profisee's Maestro, which both lack strong operational MDM facilities. VisionWare sells via a mixture of direct and indirect sales, with partners such as HP, Serco and Xerox. It is also embedded in Microsoft's health and human services (HHS) and eligibility, justice and public safety (LJS) frameworks.
- Strength in the government market and expanding geographical presence: VisionWare has a strong domain knowledge of the local government market and an increasing number of customers in healthcare provision and law enforcement. It focuses on key opportunity areas in these industries that require a single view of the citizen, patient or individual, such as HHS, health insurance exchange (HIX), health information exchange (HIE), LJS, citizen services systems and cross-domain document sharing systems in healthcare. VisionWare had 85 customers at the end of 1Q12, the majority are in the U.K., but the North American business is growing and now generates over 20% of the business. VisionWare also has two customers in South Africa, via a partner. MultiVue is increasingly being leveraged for enterprisewide MDM requirements, as opposed to just meeting the needs of specific initiatives.
- Good facilities and strongly leverages Microsoft technologies: VisionWare MultiVue has a flexible data model, allowing modeling of other data domains in addition to customer data. It also includes data profiling, analysis and internal workflow capabilities. MultiVue's sweet spot is where data is authored in a distributed fashion, then brought to a central hub for matching. A single view is created through merging the different versions to create a composite record. It uses VisionWare's own capable probabilistic matching and cleansing technology, and its data integration technologies. Implementations are scaling to hold data on more than 6 million unique customer entities, and benchmarks on commodity hardware indicate scalability well beyond that. The Prism facility, based on Silverlight, provides good visualization and analysis of parties and relationships. In v.3.1 VisionWare introduced a data governance facility called Chroma that enables the management of master data changes throughout the life cycle and across systems.
- Good feedback from customer references: Customer references continue to be a strong point for VisionWare. It provided a full set of references, the majority of which were in local government services. In the online survey, VisionWare gained one of the highest ratings for customer satisfaction of all vendors. Under vendor-related issues, it was rated highly for its understanding of the references' vertical industry needs and for its TCO, although references did feel that it could be more responsive in providing new features. MultiVue's product capabilities were also rated above average, including in areas such as flexibility of data modeling, loading, integration and high availability. It also received high marks for the sales process, implementation and after-sales support.
- Still a small company with flat revenue: VisionWare is a small, but profitable, U.K. company, with estimated total company revenue of $6 million in 2011, down from $7 million in 2010. We estimate that its 2011 revenue from solutions software for MDM of customer data was $4.4 million, down from $5 million in 2010. So far, it has not been able to leverage the growth of the MDM market, although it claims that 2011 was a year for investment in the North American operation that will pay off in future years. VisionWare needs to further ramp up sales, particularly through indirect channels, to achieve the necessary growth momentum in the market for MDM of customer data. At this size and lack of growth, VisionWare has a higher viability risk than larger vendors, and it could be an acquisition target as the MDM market continues to consolidate during the next few years.
- Only a small presence outside government and limited geographical coverage: VisionWare's business is concentrated in government, with a growing presence in healthcare and law enforcement. It has had only minor success so far in commercial organizations and this does not seem to be a focus for it now. To be viewed as more than a niche player it needs a wider spread of business across verticals, and domain expertise across those sectors. The company also has limited geographical coverage. It is strongest in the U.K. and has a growing presence in North America plus a partner in South Africa, but VisionWare is not currently offering MultiVue in any other geographies.
- Long-term risk of conflict with Microsoft: VisionWare has successfully leveraged its Microsoft relationship; however, Microsoft itself is now an MDM player with SQL Server 2012 MDS (although only as an MDM platform). Microsoft is encouraging partners such as VisionWare to offer MDS-based MDM solutions, although the takeup has been slow and partners like VisionWare have been disappointed with MDS from the technical perspective. However, in the long term — as Microsoft continues to improve MDS and Data Quality Services (DQS) — it should become more of a complete and capable MDM solution, and VisionWare will need to find ways to add value and differentiate itself. In the short term, VisionWare is safe because the current version of MDS lacks key facilities and the customer takeup has been slow; in the longer term, however, it could become more difficult should Microsoft make a decision to throw more weight behind its MDS offering.
- Restricted to Microsoft environments and has gaps in functionality: VisionWare's MultiVue is restricted to running on Microsoft SQL Server and strongly leverages Microsoft .NET technologies. It would not be suitable for organizations with Java Platform, Enterprise Edition standards, or IBM or Oracle RDBMS mandates. From a functionality point of view, VisionWare needs to provide better support and proof points for central authoring of data (transactional and workflow use cases) to create and maintain a physical golden record. It also needs additional functionality, such as more comprehensive hierarchy management and integration with additional reference data suppliers (such as D&B) to be considered more for B2B use cases. MultiVue also lacks out-of-the box integration with third-party data integration and data quality tools. It has a multitenant capability but is not yet being marketed for private cloud, and VisionWare is waiting for Microsoft Azure to become more complete and mature before offering MultiVue in the public cloud.
We review and adjust our inclusion criteria for Magic Quadrants and MarketScopes as markets change. As a result of these adjustments, the mix of vendors in any Magic Quadrant or MarketScope may change over time. A vendor appearing in a Magic Quadrant or MarketScope one year and not the next does not necessarily indicate that we have changed our opinion of that vendor. This may be a reflection of a change in the market and, therefore, changed evaluation criteria, or a change of focus by a vendor.
IBM InfoSphere MDM (Standard Edition), Orchestra Networks, SAP Master Data Governance for Customer (MDG-C)
For inclusion based on market traction and momentum, vendors should have:
- Generated at least $4 million in total software revenue (licenses and maintenance) related to MDM of customer data solutions in the past four quarters.
- Active sales and support activities globally; that is, in at least two of the following geographic regions: Americas, Europe and Middle East, Africa, Asia, and Australasia.
- Active sales, support and customers in multiple industries.
Though not part of the inclusion criteria, we also collect and/or estimate additional data to ascertain the level of activity and stability of each vendor in the market. This includes, but is not limited to:
- At least 12 live customer references for MDM of customer data solution functionality.
- At least eight new customers for MDM of customer data Solutions in the past four quarters.
- Sufficient professional services to fulfill customer demand during the next six months.
- Enough cash to fund a year of operations on current burn rate — that is, companies spend their cash reserves if the year of operations is cash-flow-negative.
This Magic Quadrant excludes:
- Vendors that solely focus on analytical (downstream) MDM requirements.
- Vendors reselling another vendor's MDM of customer data solution without extending the functionality.
- Hosted services, marketing service providers or data providers that provide trusted reference data external to the enterprise, but don't provide an MDM for customer data solution that specifically meets the definition.
For MDM software vendors that are active in the MDM of Customer Data Solutions market, but have not met the inclusion criteria, see Note 3.
Some vendors have multiple products in the MDM of customer data solutions market; in these cases, each product has been evaluated separately against the inclusion criteria. The primary goal of our research is to deliver what will be most useful to our end-user clients in their decision making at the time of publication. In this regard, the number of dots in a Magic Quadrant is determined based on the inquiries and client interactions that our analysts' undertake, plus their expert knowledge, and aims to reflect what Gartner clients are seeing or experiencing and the decisions that they having to make.
On that basis we have decided to provide multiple evaluations (and therefore multiple dots) for IBM, Oracle and SAP this year. Although IBM has an overall product offering called InfoSphere MDM, within which the different technology bases are converging, this overall product is made up of multiple editions which have significant differences and Gartner clients are having to make decisions about which edition best meets their requirements. To aid that process we have evaluated the InfoSphere MDM Standard and Advanced Editions separately. We also continue to rate Oracle Siebel UCM (sometimes known as Oracle Customer Hub) and Oracle CDH (sometimes known as Oracle EBS Customer Hub) separately, because although they too are increasingly leveraging common infrastructure components they are positioned differently, as alternatives. There could have been a third dot for Oracle as Oracle FCH is another separate product with different positioning, but although it is generally available it didn't meet the revenue inclusion criteria for the Magic Quadrant this time and we estimate that it has less than five live customer sites. Lastly, we have also introduced a second dot for SAP. For many years NetWeaver MDM has been SAP's only MDM product, but now we find that MDG-C when deployed in a stand-alone hub form is effectively an alternative to NetWeaver MDM; we also have an increasing number of clients trying to understand its relative positioning and capabilities.
As part of the Magic Quadrant process, we sought the views of vendors' reference customers via an online survey. The survey included requests for feedback on vendor maturity (for example, understanding industry verticals, provision of innovation, responsiveness to new requests, TCO and pricing) and product capabilities (for example, flexibility in data modeling, support for data quality, UI support for data stewardship, internal workflow and support for multiple architectural styles). More than 100 organizations, representing all the featured vendors' reference bases, were contacted. Not surprisingly, the references were generally pleased with their vendors and products, but they gave relatively low marks in some areas which we have detailed in the analysis of each vendor. Some of the issues may be historic, because not all organizations are on the latest product versions.
MDM of Customer Data Solutions Product Description
This market is characterized by packaged software solutions that bring together a range of technologies and capabilities that help sustain the idea of a "single golden record" for customer master data. This is the primary focus of this market analysis. The range of functional capabilities included in these products includes:
- Data modeling capabilities — The applicability of the data model to your organization is a fundamental requirement.
- Model the complex relationships between the internal application sources inside the organization, its business and consumer customers, as well as intermediaries and other parties, with the ability to handle complex hierarchies.
- Map to the master customer information requirements of the entire organization.
- Be configurable, customizable and extensible, but also upgradable.
- Support industry-specific requirements, as well as multiple hierarchical and aggregated views associated with customer data structures related to consumer systems etc. This is particularly important across operational and analytical MDM requirements.
- Provide a base for the required workload mix and level of performance.
- Be expressed using commonly accepted logical data model conventions with associated metadata.
- Information quality management capabilities — A good data model is of little value unless it contains accurate, up-to-date data
for a customer. The MDM of customer data solution should:
- Have strong facilities, in batch and real-time mode, for profiling, cleansing, matching, linking, identifying and semantically reconciling customer master data in different data sources to create and maintain a "golden record." These facilities may be provided by the MDM of customer data solution vendor or by offering tight integration with products from specialist data quality partners.
- Configure rules for comparing and reconciling semantics across data sources, matching and linking the data, and managing the merging and unmerging of records with support for full auditability, survivability and data lineage.
- Ensure that business rules and associated metadata related to data cleansing are sufficiently visible to satisfy compliance requirements.
- Loading, integration and synchronization capabilities — The MDM of customer data solution needs to provide facilities for loading the customer
data in a fast, efficient and accurate manner. There will also be a need for integration
middleware, including publish and subscribe mechanisms, to provide a communication
backbone for the bidirectional flow of customer data between the central repository
and the spoke systems: be they copies or subsets of the repository, or remote applications
(coexistence style). These facilities may be provided by the MDM of customer data
solution vendor or by offering tight integration with products from specialist middleware
partners. The MDM of customer data solution should support, as necessary, the MDM
implementation styles that each use loading, integration and synchronization in different
ways, by being able to:
- Leverage a range of middleware products to data sources, including legacy data sources, and expose industry-standard interfaces
- Support integration with different latency characteristics and styles (for example, real time and batch)
- Support integration with downstream BI and analytical requirements
- Business services and workflow functionality — Many organizations will plan to use the new customer master database as the basis for new operational (both transaction- and workflow-oriented) and analytical applications. In the SOA world of enterprise architecture, service-oriented composite business applications may consume MDM of customer data solution business services through Web services standard interfaces. The MDM of customer data solution should protect and complement the data layer with a layer of business services for accessing and manipulating the customer data that is built for an SOA environment, and exposing Web services interfaces.
- Additionally, many implementations of MDM focus on not only how systems interact (that is, transaction scenarios) but more on how business users collaborate in the authoring and management of master data. As such, the MDM of customer data solution needs to support a flexible and comprehensive workflow-based capability — in order to model data services as well as user interaction across applications and data stores where master data is stored and used.
- Performance, scalability and availability capabilities — If the MDM of customer data solution supports operational and analytical applications
and is tightly integrated with established systems and new applications, serious demands
are likely to be made on its performance, scalability and availability. The MDM of
customer data solution should have:
- Proof points (preferably through live references) of different aspects of performance and scalability that match your current and future requirements
- Appropriate availability characteristics regarding planned and unplanned downtime
- Manageability and security capabilities — The availability of facilities for management and controlled access of the MDM of customer data solution, such as facilities for reporting on activity in the solution. Also, the ability to integrate the solution, with common system management and security tools.
- On the security and data privacy management front, the ability to:
- Manage the policies and rules associated with potentially complex privacy access rights
- Configure and manage different rules of visibility, providing different views for different roles
- Stewardship Support and Services — The MDM of customer data solution needs to support a range of capabilities for
the day-to-day operation and management of MDM. The resulting focus of this will be
the role of the (business led) data steward. Among the different user roles that interact
with MDM, the data steward requires a suitable UI whereby these services are provided.
These services will include, but not be limited to:
- Analytics and performance measures related to a range of processes and activities taking place within MDM, from the running of batch data loads, to execution of workflows against benchmarks, to data quality of active master data, to business process benchmarks, to business value provided by MDM.
- Status and management tools for the chief steward to monitor to-do lists of users to ensure effective action takes place across MDM.
- Systemwide master/meta models to help identify what users, roles, applications and systems are responsible for what master data, and the state of the master data and/or business rules that are generating exceptions in that data.
- Workflow services — to interrogate and provide revisions to current MDM workflows.
- Business rules services — to interrogate which rules are used by MDM and to provide suggested enhancements to such business rules; also used to determine under which circumstances source preference is revised to give preference to the most-dependable source.
- A range of user interfaces on PCs, smartphones and tablets.
- Technology and architecture considerations — MDM of customer data solutions should be based upon up-to-date, mainstream server, PC and mobile device technologies, and be capable of flexible and effective integration with a wide range of other application and infrastructure platform components (whether from the same vendor or not) within end-user organizations.
- MDM of customer data solutions should be capable of:
- Flexible configuration into a range of implementation styles in terms of instantiation, latency and use of customer master data to enable it to satisfy different use-case scenarios such as the consolidation, registry, coexistence and centralized scenarios.
- Architecturally supporting global rollouts and localized international installations.
- Supporting both on-premises and in the cloud deployment styles, including SaaS.
- Supporting integration with big data sources and having the ability to perform entity resolution within those sources, whether relational or non-relational and structured or unstructured in nature.
Gartner analysts evaluate technology providers on the quality and efficacy of the processes, systems, methods or procedures that enable IT provider performance to be competitive, efficient and effective, and to positively impact revenue, retention and reputation. Ultimately, technology providers are judged on their ability and success in capitalizing on their vision.
Software products offered by the vendor that compete in/serve the MDM of customer data solutions market. This includes product capabilities, quality, feature sets and skills, whether offered natively or through OEM agreements/partnerships as defined in the market definition and detailed in the subcriteria.
Vendors will be measured on the ability of the product release to support the following MDM of customer data solution subcriteria.
- Data modeling capabilities
- Information quality management capabilities
- Loading, integration and synchronization capabilities
- Business services and workflow functionality
- Performance, scalability and availability capabilities
- Manageability and security capabilities
- Stewardship support and services
- Technology and architectural considerations
Viability includes an assessment of the MDM of customer data solution vendor's financial health, the financial and practical success of the business unit or organization in generating business results in the market, on a global basis, and the likelihood of the organization or individual business unit to continue to invest in development of the product, continue offering the product and advancing the state of the art within the organization's portfolio of products.
The vendor's capabilities in all MDM of customer data solutions related pre-sales activities, on a global basis, and the structure that supports them. This includes deal management, pricing and negotiation, pre-sales support and the overall effectiveness of the sales channel.
Market Responsiveness and Track Record
Ability to respond, change direction, be flexible and achieve competitive success as opportunities develop, competitors act, customer needs evolve, and market dynamics change within the MDM of customer data solutions market. This criterion also considers the vendor's history of responsiveness.
The clarity, quality, creativity and efficacy of programs designed to deliver the vendor's message, on a global basis, in order to influence the MDM of customer data solutions market, promote the brand and business, increase awareness of the products and establish a positive identification with the product/brand and organization in the minds of buyers. This "mind share" can be driven by a combination of publicity, promotional, thought leadership, word-of-mouth and sales activities.
Relationships, products and services/programs that enable clients to be successful, on a global basis, with the products evaluated. This includes implementation and support and the way customers receive technical and account support. It also includes a measure of clients' success in implementing MDM for customer data solutions — customer references and TCO.
With the increasing hype around multidomain MDM, we also look for demonstrated proof — via proof of concepts, customer evaluations or live implementations — of multidomain/multiprovince capability.
The ability of the organization to meet its goals and commitments. Factors include the quality of the organizational structure, including skills, experiences, programs, systems and other vehicles that enable the organization to operate effectively and efficiently on an ongoing basis. This criterion was previously not explicitly rated and had a weighting of "No Rating." This year we have changed this to a "Low" rating to maintain consistency with the "Magic Quadrant for Master Data Management of Product Data Solutions."
Source: Gartner (October 2012)
Gartner analysts evaluate technology providers on their ability to convincingly articulate logical statements about current and future market direction, innovation, customer needs, and competitive forces and how well they map to the Gartner position. Ultimately, technology providers are rated on their understanding of how market forces can be exploited to create opportunity for the provider.
Ability of the vendor to understand buyers' needs and translate these needs into products and services. Vendors that show the highest degree of vision listen and understand buyers' wants and needs, and can shape or enhance those wants with their added vision. Vendors should demonstrate a strategic understanding of MDM for customer data solution opportunities (for example, new application functionality or customer segments) and ongoing vendor market dynamics (for example, consolidation trends) on a global basis, and translate these needs into products and services. Additionally, an understanding of the wider implications and position of MDM for other kinds of master data within an organization's multidomain, multi-use-case, and multi-implementation style program; also the relationship to enterprise information architecture (EIA) and EIM initiatives are valuable to customers taking the strategic view.
A clear, differentiated set of MDM of customer data solution messages consistently communicated throughout the organization and externalized globally through the website, advertising, customer programs and positioning statements. Intersection with multidomain MDM and wider MDM and industry challenges, as expressed by Gartner clients, is important.
Vendor's strategy for selling the MDM of customer data solution that uses a vendor or partner global network of direct and indirect sales, marketing, service, and communication affiliates that extend the scope and depth of market reach, skills, expertise, technologies, services and the customer base.
Offering (Product) Strategy
A vendor's approach to product development and delivery should emphasize differentiation, functionality, methodology and feature set as they map to current and future requirements. The vendor's published "statement of direction" (or Gartner's understanding of it) for the next two product releases needs to keep pace with, or surpass, Gartner's vision of the MDM of customer data solution market. Gartner's main product-oriented criteria focus on:
- Data modeling capabilities
- Information quality management capabilities
- Loading, integration and synchronization capabilities
- Business services and workflow functionality
- Performance, scalability and availability capabilities
- Manageability and security capabilities
- Stewardship support and services
- Technology and architectural considerations
The vendor needs to offer a MDM of customer data solution that can be configured into a range of architectural styles, in terms of instantiation, latency, search and usage of customer master data, to allow it to satisfy different use case scenarios, such as the consolidation, registry, and centralized style scenarios, leading up to hybrid models such as coexistence style.
The vendor needs to show how an MDM of customer data solution supports the wide range of user cases from business design (construction-centric MDM), business operations (operational MDM) and BI (analytical MDM). Most vendors focus on one use case so vendors need to demonstrate how they intend to support the growing convergence in requirements across these use cases.
The vendor must also understand major technology/architecture shifts in the market and communicate a plan to leverage them, including migration issues that may affect customers on current releases. Specifically, the vendor should have a vision to support mainstream software infrastructure technology, as opposed to a proprietary stack, and have an evolutionary path toward SOA.
The soundness and logic of a MDM of customer data solution vendor's underlying business proposition. Vendors should have a well-articulated strategy for revenue growth and sustained profitability. Key elements of strategy include the sales and distribution plan, internal investment priority and timing, and partner alliances, such as with ESPs.
Vendor's strategy to direct resources, skills, and offerings to meet the specific needs of individual market segments, including verticals. Included are reviews of the vendor strategy for meeting the needs in specific vertical industries such as banking, manufacturing, communications and government.
Vendors need to be able to lead this market and, in so doing, provide customers with an innovative solution and approach to service customer needs in a complex, heterogeneous environment. Innovation here implies leading the way with MDM of customer data issues today and in the future. Understanding of, and support for, the most complex and broadest set of MDM of customer data environments and the growing requirements of multidomain and multi-use-case MDM in general is looked for. New this year will be a focus on how the vendor plans to support key initiatives such as cloud, social data and other kinds of big data, and mobile, in the context of MDM.
Vendor's strategy to direct resources, skills and offerings to meet the specific needs of geographies outside the "home" or native geography, either directly or through partners, channels and subsidiaries, as appropriate for that geography and market. Includes sales, marketing and support for complex global companies.
Source: Gartner (October 2012)
Vendors in the Leaders quadrant have strong results and delivery capabilities, and will continue to have them. They typically possess a large, satisfied customer base (relative to the size of the market) and enjoy high visibility in the market. The size and financial strength of the Leaders enable them to remain viable in a challenging economy. Leaders have mature offerings and track records of successful deployments, even in the most-challenging environments, across all geographies and in many vertical industries. Leaders have the strategic vision to address evolving client requirements; however, they're not always the best choice.
Challengers demonstrate a clear understanding of today's MDM of customer data solutions market, but they have not demonstrated a clear understanding of the market direction or are not well-positioned to capitalize on emerging trends. They often have a strong market presence in other application areas. There are no vendors rated as challengers this year's Magic Quadrant.
Visionaries display healthy innovation and a strong potential to influence the direction of the MDM of customer data solutions market, but they are limited in execution or demonstrated track records. Typically, their products and market presence are not yet complete or established enough to reach Leaders status.
Niche Players do well in specific segments of the MDM of customer data solutions market, or have a limited ability to be innovative or outperform other vendors in the market. They may be focused on a specific functionality, domain or industry, or have gaps relative to broader functionality requirements. Niche Players may have limited implementation and support services, or have not achieved the necessary scale to solidify their market positions.
Gartner's Magic Quadrant for MDM of customer data solutions provides insight into the portion of the packaged MDM solution market that focuses on how organizations master and share a "single version" of customer data with multiple views of it across the organization. Achieving a single version of master data is a key initiative for many organizations and in this Magic Quadrant we are take "customer" data to include consumers, business customers, channel/trading partners, prospects, citizens, constituents, people of interest, healthcare professionals, patients and counterparties, but we do not include other "parties" such as human resources and suppliers. This analysis positions MDM of customer data solution vendors (and their products) on the basis of their Completeness of Vision relative to the market, and their Ability to Execute on that vision.
The four market share leaders (based on Gartner revenue estimates) — IBM, Informatica, Oracle and SAP — continue to consolidate their positions with Tibco making a lot of progress to take fifth place in market share, but the MDM portfolios of the megavendors (that is, IBM, Oracle and SAP) have become more complex as they try to meet a greater range of the various MDM demands created by end-user organizations. IBM is focusing on a convergence road map for its multiple products; Oracle is also converging onto common middleware and MDM technology infrastructure; and SAP now has two products in this space — NetWeaver MDM and MDG — with a third, MDS, in the works. Informatica continues to do well in the MDM market and recently acquired Data Scout for cloud MDM, while Tibco has put new emphasis on MDM and is becoming more of a force in the MDM of customer data market. DataFlux has been consolidated into its parent company and is now the brand for SAS Institute's data management portfolio, and VisionWare continues to provide a distinct Microsoft-based value proposition. Orchestra Networks is seeing strong growth and is entering the MDM of customer data solution Magic Quadrant for the first time. Other vendors, such as Ataccama, Information Builders, Kalido, Microsoft, Software AG, Talend and Teradata are also active in the market, but their presence is still too small to be included in the Magic Quadrant. A key feature of the last year has been vendors, such as Heiler, hybris, Riversand and Stibo, that historically focused on product data starting to adopt a more multidomain position and therefore become more relevant to the MDM of customer data solutions market.
Use this Magic Quadrant to understand the MDM of customer data solutions market segment, and how Gartner rates the leading vendors (and their offerings) in that market. Draw on this research to evaluate vendors based on a set of objective criteria that you can adapt to your particular situation. Gartner advises organizations against simply selecting vendors in the Leaders quadrant. All selections are buyer-specific, and vendors from the Challengers, Niche Players or Visionaries quadrants could be better matches for your requirements. See "Magic Quadrants and MarketScopes: How Gartner Evaluates Vendors Within a Market."
Although important, selecting an MDM for customer data solution is only part of the MDM challenge. To succeed, you should put together a balanced MDM program that creates a shared vision and strategy, addresses governance and organizational issues, leverages the appropriate technology and architecture, and creates the necessary processes and metrics for your customer data system (see "The Seven Building Blocks of MDM: A Framework for Success" and "The Five Vectors of Complexity That Define Your MDM Strategy").
MDM is a technology-enabled discipline in which business and IT work together to ensure the uniformity, accuracy, stewardship, semantic consistency and accountability of the enterprise's official, shared master data assets. Master data is the consistent and uniform set of identifiers and extended attributes that describes the core entities of the enterprise, such as customers, prospects, citizens, suppliers, sites, hierarchies, and chart of accounts.
The business drivers for creating a single view of the customer include:
- Compliance and risk management drivers, such as "know your customer," anti-money laundering or counterparty risk management in banking, or Sunshine Act compliance in life sciences. These initiatives tend to have the hardest benefits and they are mandatory.
- Cost optimization and efficiency drivers. Very often these drivers are associated with business transformation initiatives and end-to-end business process improvement. These have tangible benefits and are a good fit for organizations' needs during an economic downturn.
- Growth in revenue and profitability drivers. Examples are improvement in cross-sell, upsell and retention, together with improvements in the customer experience. These can be more difficult to measure, but are a major focus when the economy is going well.
However, most large enterprises have heterogeneous application and information management portfolios, with fragments of often inaccurate, incomplete and inconsistent data residing in various application silos. No single system contains the single view of the customer or is designed to manage the complete life cycle of the customer master data.
The ability to create, maintain and leverage a single, trusted, shareable version of customer master data is increasingly seen as an essential requirement in commercial and noncommercial organizations to support business processes and business decision making. When creating and managing customer master data, many organizations and vendors originally thought that CRM, ERP or vertical industry application systems would solve the problem of inconsistent master data spread across multiple systems; however, CRM, ERP and vertical industry systems weren't designed for that task, and often there are multiple CRM or ERP systems in an enterprise. Many organizations have now invested in creating a new central system to master the customer data, with the majority (an estimated 80%) of organizations buying packaged MDM of customer data solutions, as opposed to building the capability themselves.
Investment in MDM of customer data solutions continues to occur across all vertical industries and government. Service industries (such as financial services and healthcare) and government tend to focus mainly on the customer data domain (except for some sectors of financial services that deal heavily with securities), whereas product-oriented industries tend to be interested in a wide set of data domains (such as product, supplier and customer). There is global interest and investment in MDM of customer data solutions, mainly by large enterprises.
The products featured in this Magic Quadrant initially were first-generation MDM solutions (focused on a single master data domain). We then saw the evolution into second-generation MDM solutions (able to demonstrate the ability to manage multiple domains, but mainly within the same province such as party or thing). And now we see third-generation MDM solutions (able to demonstrate the ability to manage any master data domain and province) starting to build up their maturity.
In terms of new MDM capabilities, the past year has seen particular emphasis on adding or improving data stewardship and governance facilities, including data profiling, workflow, data visualization and manipulation, dashboards and reporting. Better user interfaces and workflows for business users, including increased leveraging of BPM technology and MDM applets, which allow existing applications to leverage MDM-hub-based data, have been introduced. The leading vendors are starting to meet some of the challenges of what Gartner calls the Nexus of Forces (see "The Nexus of Forces: Social, Mobile, Cloud and Information"). Some are starting to provide support for social networks ("The Impact of Social and Other 'Big Data' on Master Data Management"), mobile (data stewardship applications are starting to become available on tablets), cloud computing (see "The Advent of Master Data Management Solutions in the Cloud Brings Opportunities and Challenges") and aspects of big data. The megavendors have a lot of focus on convergence road maps to bring together their disparate offerings.
Gartner estimates that total software revenue for packaged MDM solutions was $1.5 billion in 2011, an increase of 15% from 2010, versus a 9.75% growth rate for the overall enterprise software market (see "Forecast: Enterprise Software Markets, Worldwide, 2011-2016, 3Q12 Update"). Within those overall figures we estimate that the market for MDM of customer data solutions was $503 million in 2011, an increase of 14% from 2010. In "Forecast: Master Data Management, Worldwide, 2010-2015," we projected a five-year compound annual growth rate (CAGR) of nearly 20% for both the overall MDM and the MDM of customer data software markets through 2015. We estimate that IBM is the market share leader in the MDM of customer data solutions market (based on sales of InfoSphere MDM Standard Edition and Advanced Edition), with estimated total software revenue of $196 million. Oracle is in second place (based on sales of its Oracle CDH, Oracle FCH and Siebel UCM products) with estimated revenue of $103 million. Informatica is in third place with estimated revenue of $65 million, SAP is in fourth place with estimated revenue of $37 million (based on sales of NetWeaver MDM and stand-alone hub deployments of MDG-C) and Tibco is in fifth place with estimated revenue of $15 million. Together, we estimate that these top five market share leaders account for over 80% of the MDM of customer data solutions market.
Unlike previous years, the last year has not been characterized by acquisitions, except for Informatica's recent acquisition of Data Scout, but we continue to see the after effects of acquisitions: some vendors are promoting convergence road maps to overcome disparate product and technology mixes, while others are still ramping up in, what is to them, a new market. The MDM portfolios of the megavendors (IBM, Oracle and SAP) are complex. This is a largely a result of trying to meet all the various multivector demands within the MDM market. IBM is focusing on a convergence road map for its portfolio of products that come under the InfoSphere MDM banner; Oracle is also converging its multiple MDM products onto a common middleware and MDM technology infrastructure; and SAP now has two products in this space (NetWeaver MDM and MDG-C) with a third (MDS) in the works. Informatica MDM continues to do well in the MDM market and Tibco, which has put new emphasis on MDM, accelerated its MDM revenue by an estimated 120% in 2011. Other established contenders such as DataFlux (now subsumed into its SAS Institute parent) and VisionWare continue to feature in the market, but have not broken out of their established positions. Orchestra Networks is seeing strong growth and features in the MDM of customer data solution Magic Quadrant for the first time this year. Other vendors, such as Ataccama, Information Builders, Kalido, Microsoft, Software AG, Talend and Teradata are also active in the market, but their presence is still too small to be included in the Magic Quadrant. A particular feature of the last year has been vendors, such as Heiler, hybris, Riversand and Stibo, that historically focused on managing product data starting to adopt a more multidomain position and become more relevant to the MDM of customer data solutions market. The approach taken by several of these vendors is to develop an MDM customer data implementation at one or more of their existing clients, capitalizing on an established relationship. We still wait for Microsoft to have a major impact on the MDM market with its SQL Server Master Data Services technology.
In this year's Magic Quadrant, the Leaders quadrant consists of three vendors — IBM, Informatica and Oracle (with Siebel UCM). IBM InfoSphere MDM has strong momentum in the market and it provides a range of options for organizations requiring different implementation styles. Both the Standard and Advanced Editions have had great success in the market over the past 12 months with Standard Edition strong in meeting registry-style MDM requirements and Advanced Edition (which includes Standard Edition) good for maintaining a physical system of record — particularly in high-volume transactional environments — as well as offering a registry-style starting point. Siebel UCM continues to be Oracle's lead product for MDM of customer data while Fusion Customer Hub continues to mature. Siebel UCM substantially outsells Oracle CDH, which is now only sold to Oracle EBS customers, and UCM continues to benefit from R&D investment, particularly around Oracle's CX strategy. Informatica MDM continues to do well and it has done a good job in scaling up its MDM business. Its messaging has played well with buyers trying to find a single MDM product to meet all their MDM needs, although its overall MDM positioning will be more complex following the Data Scout and Heiler Software acquisitions.
Tibco has entered the Visionaries quadrant this year on the basis of its greater understanding of the market and increased business focus during the past year. We have no vendors in the Challengers quadrant.
There are a number of vendors in the Niche Players quadrant. Our analysis has positioned Oracle's CDH in this quadrant because it is only positioned for established Oracle EBS customers in product-oriented industries; it has a much lower sales traction compared to Siebel UCM and the Oracle sales force is now pitching Oracle FCH in preference. We have moved SAP NetWeaver MDM down from the Challengers quadrant in view of the fact that SAP is now giving greater prominence to MDG-C and will be introducing MDS for high-volume, real-time transactional B2C environments. SAS Institute DataFlux has a steadily improving MDM of customer data solutions product in the shape of qMDM; it is focusing more on the "buy" rather than the "build" market now, but it's a long way behind the market leaders in market presence. VisionWare is holding its position in the public sector and healthcare industries and is a good option in the Microsoft .NET segment of the market. Lastly, Orchestra Networks enters the Magic Quadrant for the first time, but needs to build up its MDM of customer data solutions customer base, particularly in the B2C area, if it is to progress further.
While the overall view of this year's Magic Quadrant appears similar to that of a mature software market, the complex nature of the MDM discipline has led to a situation where there are still vendors entering the Magic Quadrant for the first time (for example Orchestra Networks) or getting near to entering (for example Ataccama and Kalido). In addition, many vendors are now branching out to manage additional master data domains. However, during the same period, client and prospect enterprises have become more educated in the depth and complexity of the expertise and management required by successful MDM implementations, and are somewhat more likely to rely on a market leader. As the overall market continues to grow, there are likely to be sufficient revenue opportunities to keep the Niche Players viable, but they will continue to face a challenge in entering the Leaders' quadrant.
MDM is a technology-enabled discipline in which business and IT work together to ensure the uniformity, accuracy, stewardship, semantic consistency and accountability of the enterprise's official, shared master data assets. Master data is the consistent and uniform set of identifiers and extended attributes that describes the core entities of the enterprise, such as customers, prospects, citizens, suppliers, sites, hierarchies and chart of accounts.
- It can be implemented in a single instance.
- The data model is uniform or is interoperable and able to manage cross-domain intersections.
- The workflow and UI elements are uniform or interoperable.
- It supports at least one use case, implementation style and organization/governance model, for specific industry scenarios.
- Ataccama (Headquarters: Stamford, Conneticut, U.S. Development Center: Prague, Czech Republic. Website: www.ataccama.com). Ataccama is a Czech vendor with an MDM product called Master Data Center (MDC) v.7.0.5, which has been generally available from May 2012 and includes Ataccama's data quality tool product called Data Quality Center (DQC). The vendor has a total of 24 MDC customers using the MDC product, with 19 managing customer data. Historically, most of Ataccama's customers have been in central and eastern Europe, and Canada, but it is now expanding into the German and U.S. markets. Ataccama also has an OEM relationship with Information Builders, which resells MDC and DQC.
- D&B (Headquarters: Short Hills, New Jersey, U.S. Website: www.dnb.com). D&B is best known for providing information and insight on business customers. It is generally regarded as the leading supplier in the B2B area, with the most worldwide coverage (more than 212 million businesses). D&B's hosted data service (D&B Optimizer) can be used to bring structure to business data by persistently identifying legal entities via D&B D-U-N-S Numbers and providing an understanding of legal entity hierarchies, and it also has two newer data as a service (DaaS) offerings called D&B Direct and D&B360. D&B Direct is an API which makes it possible to access D&B's business information from any application or platform, while D&B360 is an integrated out-of-the box offering that delivers real-time matching at the entry point against D&B's database for MDM and CRM products. D&B also used to be a player in the MDM solutions market with the Purisma Data Hub MDM solution, but in 2010 announced that although this product will continue to be supported, there will be no further proactive sales or development of the product. D&B is now focused on being a DaaS integrator into MDM solutions and applications such as CRM, ERP and sales force automation (SFA).
- Information Builders (Headquarters: New York, U.S. Website: www.informationbuilders.com). Information Builders' iWay product division provides an MDM solution called Master Data Center (MDC). MDC includes some core technology licensed from Ataccama that has been augmented by Information Builders' own technologies. In addition, Information Builders is creating a set of vertical industry applications based on MDC, called Omni Framework. The first offering is Omni-Patient, a combination of an enterprise master person index (EMPI) with prepackaged models designed specifically for the healthcare industry. Information Builders now has a total of 11 MDM customers, including 10 managing customer data. Its value proposition is based on the combination of its integration, MDM, data quality tools, BI and reporting technologies and now (in addition), the Omni Framework applications. Information Builders can also leverage its extensive global presence.
- Heiler Software (Headquarters: Stuttgart, Germany. Website: www.heiler.com). Heiler Software is a public German vendor that focuses on helping retailers, distributors and manufacturers to manage complex product data (structured, as well as unstructured) through complex supply chains, from suppliers through to multiple selling and interaction channels, particularly e-commerce channels, with customers. Its main focus is product data, offering Heiler Enterprise product information management (PIM) Suite v.6.0, but it is steadily building up its ability to manage multiple data domains, including support for customer data. On 1 October 2012 Informatica announced its intention to acquire Heiler Software.
- hybris (Headquarters: Munich, Germany. Website: www.hybris.com). A Germany-based software vendor, hybris sells to enterprises with requirements related to e-commerce, catalog, print/media and multichannel integration. It focuses mainly on managing product master data across multiple channels, although an increasing number of its customers are also using it to manage customer, supplier and asset master data. We estimate that, at the end of 2011, hybris had a total of 152 licensed MDM customers, with 21 of them managing customer data. We estimate that hybris's MDM total software revenue was approximately $15.3 million in 2011. Almost 55% of its revenue comes from Europe-based customers, with 40% now from North America.
- Kalido (Headquarters: Burlington, Massachusetts, U.S. Website: www.kalido.com). Historically, Kalido focused on the BI world, and its MDM customers typically used it for multi-subject-area analytical MDM use cases, such as dimension and hierarchy management. Now, Kalido MDM 9 is applicable to both analytical- and workflow-oriented operational MDM requirements. Kalido provides what it calls a "business centric" MDM solution and its vision is to provide organizations with the ability to model all domains and enable management by both business and IT users, giving them universal access. Gartner estimates that, at the end of 2011, Kalido had a total of 72 licensed MDM customers. We estimate that 24 feed master data only to the data warehouse, and 32 are feeding (or plan to feed) master data to at least one operational system. Of the customers that feed operational systems, we estimate that Kalido has 14 managing customer data. Kalido's 2011 MDM total software revenue is estimated to be $11 million.
- Microsoft (Headquarters: Redmond, Washington, U.S. Website: www.microsoft.com). SQL Server 2012, generally available since April 2012, includes an MDM platform called Master Data Services (MDS) that is available with SQL Server Business Intelligence and Enterprise Editions. MDS is a multidomain MDM platform, with hierarchy management and version control that will enable customers to build their own MDM solution and manage a variety of data domains. The SQL Server 2012 release included enhancements to MDS that enabled business users to manage their own changes to their master data elements from within a new Excel add-in and it also included Data Quality Services (DQS), based on Microsoft's Zoomix acquisition, to provide data cleansing and matching capabilities.
- Pitney Bowes Software (Headquarters: Stamford, Conneticut, U.S. Website: www.pb.com/software). Pitney Bowes provides multichannel solutions that enable lifetime customer relationships by integrating data management, location intelligence, sophisticated predictive analytics, rule-based decision making and cross-channel customer interaction management to increase the value of every customer engagement. It entered the MDM market in June 2012 with the release of 8.0 of its data management platform, Spectrum. The Spectrum MDM solution provides a unique and innovative approach to the MDM market, that potentially gives it advantages in modeling and querying networked master data (such as complex relationships and hierarchies), including support for social and big data with built-in analytics and, according to the company, a rapid and agile implementation of MDM.
- Riversand (Headquarters: Houston, Texas, U.S. Website: www.riversand.com). Riversand's mission is to help organizations master their own information supply chain (implying a multiple-domain strategy), with a specific focus on customer-centric industries needing product and asset master data. Riversand targets the energy, oil and gas, consumer goods and retail, distribution and manufacturing industry segments. Riversand's MDM solution is called MDMCenter. Gartner estimates that, at the end of 2011, Riversand had a total of 38 licensed MDM customers, including three customers managing customer data.
- Semarchy (Headquarters: Lyon, France. Website: www.semarchy.com). Semarchy is a small French vendor, calling itself "the Data Convergence Company," that entered the MDM market in 4Q11. It claims that its Convergence for MDM v.1.3 product offers an "Evolutionary MDM" capability and is therefore better able to meet the ever-changing demands of the business than competing products. Other key characteristics of Semarchy's approach include logical data modeling, iterative development and being non-invasive.
- Software AG (Headquarters: Darmstadt, Germany. Website: www.softwareag.com). Software AG entered the MDM market in 4Q10 with the acquisition of Data Foundations, a small U.S. vendor whose OneData product was an MDM platform with a drop-in data model, fully configurable and extendible, that manages multiple domains of master data, reference data, hierarchies and metadata, and analytical and operational MDM use cases — all integrated in the same instance. Software AG renamed the product webMethods OneData and has been releasing new versions at frequent intervals with v.8.4 released in January 2012. Gartner estimates that Software AG has 25 MDM customers and that its 2011 MDM revenue was $3.6 million. The vendor's positioning in the market is around "process-driven MDM.
- Stibo Systems (Headquarters: Aarhus, Denmark and Atlanta, Georgia, U.S. Website: www.stibosystems.com). Until 2007 Stibo focused on catalog publishing tools and services, but since then it has focused on MDM, primarily the MDM of product data. Its product offering, STEP MDM, with v.5.3 generally available since June 2012, is very capable for retail, distribution, manufacturing, automotive, and travel/hospitality organizations that need to master product data in a centralized product repository, with collaborative workflow requirements. We estimate that, at the end of 2011, Stibo Systems had a total of 180 licensed MDM customers, including five customers managing customer data.
- Talend (Headquarters: Suresnes, France and Los Altos, California, U.S. Website: www.talend.com). Talend is an open-source vendor and its MDM solution, Talend MDM, leverages open-source technology, including Talend's own data integration and data quality products. It is employed mainly in operational use cases and can provide flexible, multidomain data-modeling facilities, based on XML schemas and a native XML datastore. Talend MDM is available as a free downloadable Community Edition (Talend Open Studio for MDM) and a commercially-licensed Enterprise Edition (Talend Enterprise MDM). We estimate that Talend has a total of 58 Enterprise MDM customers, including an estimated 38 of them managing some form of "party" data. We estimate its 2011 MDM software revenue at $6 million.
- Teradata (Headquarters: Miamisburg, Ohio, U.S. Website: www.teradata.com). Teradata sees MDM as an integral part of data warehouse solutions, and views data mart consolidation as an ideal opportunity to achieve data synchronization with analytical MDM; however, it also supports workflow-oriented operational MDM use cases with central authoring. Teradata MDM has the most experience in managing product and supplier data, not customer data. Teradata MDM v.3.2, which became generally available in June 2012, introduced customer reference data management capabilities. The previous version, 3.1, generally available in March 2011, included Lookup Reference Data Management (LRDM) capabilities. We estimate that Teradata has a total of 23 MDM customers, including five managing customer data. In addition, over half of Teradata's 1,400 data warehouse customers use Teradata for aspects of customer data management. We estimate its 2011 MDM software revenue at $3 million.
- Vinculum (Headquarters: Singapore. Website: www.vinculumgroup.com). Vinculum is a venture-funded Indian company that focuses on supply chain issues in the retail, CPG and manufacturing industry verticals with some major customers — mainly in Asia/Pacific. It has an MDM solution called Vin MDM that entered the MDM market in 2011 and can support products, suppliers and customers. Vin MDM uses an industry-specific, rule-based approach to identify data inconsistencies across the master data. It claims that this allows for rapid data cleansing and fast implementations.
There is a range of vendors and solutions focused on the banking industry, including Asset Control, GoldenSource and Kingland Systems, and they are described more fully in "Banker's Guide to Reference and Related Investment Data Management Software."
NextGate (Headquarters: Monrovia, California, U.S. Website: www.nextgate.com). This company focuses on the healthcare market and has a product line called MatchMetrix, which provides MDM, EMPI, provider registry and directory, terminology registry, and other registry products that support single-view, accountable care organization (ACO), and HIE initiatives. NextGate's senior personnel gained their experience in the master index space at SeeBeyond and Sun Microsystems, where they implemented master index and integration products and solutions.
Cegedim Relationship Management. (Headquarters: Paris, France. Website: www.cegedim.com/rm). This company (formerly known as Cegedim Dendrite) has an MDM product called Nucleus 360, which is offered to life sciences companies looking to build a single view of healthcare professionals, organizations and related affiliation hierarchies. Nucleus 360 is provided in multiple deployment options: service, hosted and on-premises with full-scale global deployment options. The service option (Nucleus as a Service) is popular, and is increasingly being sold in combination with OneKey (Cegedim's healthcare professional and organization reference database and data governance service) and AggregateSpend360 (a spend compliance reporting solution). The combination is aimed at providing an end-to-end approach to master data governance, locally and globally.
- IBM Cognos (Software Business Unit) (Headquarters: Armonk, New York, U.S. Website: www.ibm.com). IBM Cognos Business Viewpoint v.10.1, which is part of the Cognos 10 suite, enables business users to collaboratively create, maintain, govern and share dimensions and hierarchies for use across BI and performance management applications. It is data-domain-neutral.
- Oracle (Hyperion DRM) (Headquarters: Redwood Shores, California, U.S. Website: www.oracle.com). Oracle offers a product called Oracle Hyperion Data Relationship Management (DRM). It is a data-model-neutral solution that focuses on managing change in hierarchical structures and building consistency in the relationships among information assets, such as general ledger accounts, cost centers and related entities. DRM is typically used for analytical MDM; however, because it is data-model-agnostic and contains the capabilities to author new data and write it back, it can be used in an operational MDM context, and not just with financial data. In addition, customers are increasingly using Oracle Hyperion DRM as a reference data management solution as well to manage types, codes, business taxonomies and complex relationships and mappings.
There are different implementation styles for MDM systems. They provide different capabilities, require different levels of architectural and governance commitment, and are applicable to different situations.
- The consolidation style achieves a single version of master data mainly for lookup or BI purposes. Master data is authored in the source systems, then copied to the central "hub" where it undergoes a match-and-merge process to create a golden copy. There is no explicit goal to clean up the source master data when errors are found in the process of consolidation. There is no publishing or use for the data in any operational systems, only in BI environments. A complication emerges once such a data source is used as a source for new applications that create new data as a result; this implies a different focus for governance of the master data. Therefore, the style shifts from consolidation to one of the other styles where there is an explicit desire to fix source data.
- The registry style matches and links master data from source systems to create and maintain a central index into the master data. Different versions of the truth are held in the index and, at runtime, the system assembles a point-in-time composite view. This style is a relatively noninvasive, virtual approach and requires less governance agreement relative to the styles that maintain a physical golden record.
- The centralized style supports a centralized repository of all the master data for authorship, storage and validation, and is the most invasive style, due to the change in application and information architecture. This is commonly desired when there is a high demand for automated integration between source systems and MDM infrastructure. It handles two main scenarios: where access to the "hub" by "spoke" applications is transactional and could be very demanding, and where authoring and access to the hub is via collaborative workflow.
- The coexistence style recognizes that master data may be authored and stored in different systems across a heterogeneous and distributed environment. It creates greater consistency and data quality across systems, and rapid access to a single version (publishing that view to subscribing systems). This style is much more complex than the other styles because it is not really one style. Some instances represent simple publish/subscribe models (ERP pushes data out to a best-of-breed application), while others (newly emerging) mix and match where individual attributes persist that, combined at runtime (i.e., transaction request), represent the master data.
Ability to Execute
Product/Service: Core goods and services offered by the vendor that compete in/serve the defined market. This includes current product/service capabilities, quality, feature sets, skills and so on, whether offered natively or through OEM agreements/partnerships as defined in the market definition and detailed in the subcriteria.
Overall Viability (Business Unit, Financial, Strategy, Organization): Viability includes an assessment of the overall organization's financial health, the financial and practical success of the business unit, and the likelihood that the individual business unit will continue investing in the product, will continue offering the product and will advance the state of the art within the organization's portfolio of products.
Sales Execution/Pricing: The vendor's capabilities in all presales activities and the structure that supports them. This includes deal management, pricing and negotiation, presales support, and the overall effectiveness of the sales channel.
Market Responsiveness and Track Record: Ability to respond, change direction, be flexible and achieve competitive success as opportunities develop, competitors act, customer needs evolve and market dynamics change. This criterion also considers the vendor's history of responsiveness.
Marketing Execution: The clarity, quality, creativity and efficacy of programs designed to deliver the organization's message to influence the market, promote the brand and business, increase awareness of the products, and establish a positive identification with the product/brand and organization in the minds of buyers. This "mind share" can be driven by a combination of publicity, promotional initiatives, thought leadership, word-of-mouth and sales activities.
Customer Experience: Relationships, products and services/programs that enable clients to be successful with the products evaluated. Specifically, this includes the ways customers receive technical support or account support. This can also include ancillary tools, customer support programs (and the quality thereof), availability of user groups, service-level agreements and so on.
Operations: The ability of the organization to meet its goals and commitments. Factors include the quality of the organizational structure, including skills, experiences, programs, systems and other vehicles that enable the organization to operate effectively and efficiently on an ongoing basis.
Completeness of Vision
Market Understanding: Ability of the vendor to understand buyers' wants and needs and to translate those into products and services. Vendors that show the highest degree of vision listen and understand buyers' wants and needs, and can shape or enhance those with their added vision.
Marketing Strategy: A clear, differentiated set of messages consistently communicated throughout the organization and externalized through the website, advertising, customer programs and positioning statements.
Sales Strategy: The strategy for selling products that uses the appropriate network of direct and indirect sales, marketing, service, and communication affiliates that extend the scope and depth of market reach, skills, expertise, technologies, services and the customer base.
Offering (Product) Strategy: The vendor's approach to product development and delivery that emphasizes differentiation, functionality, methodology and feature sets as they map to current and future requirements.
Business Model: The soundness and logic of the vendor's underlying business proposition.
Vertical/Industry Strategy: The vendor's strategy to direct resources, skills and offerings to meet the specific needs of individual market segments, including vertical markets.
Innovation: Direct, related, complementary and synergistic layouts of resources, expertise or capital for investment, consolidation, defensive or pre-emptive purposes.
Geographic Strategy: The vendor's strategy to direct resources, skills and offerings to meet the specific needs of geographies outside the "home" or native geography, either directly or through partners, channels and subsidiaries as appropriate for that geography and market.