This is what I prepared using 2008 data. Will be refreshing the same shortly with 2009 reports. Comments/Thoughts are welcome

1. Gartner EIM Leaders

3. Vendors must have generated revenue from a minimum of 10 verifiable distinct organizations with data warehouse DBMSs in production.

4. Customers in production must have deployed enterprise-scale data warehouses that integrate data from at least two operational source systems for more than one end-user community (such as separate business lines or differing levels of analytics).

5. Support for these data warehouse DBMS products must be available from the vendor — we consider open-source DBMS products from vendors that control or participate in the engineering of the DBMS (see "The Growing Maturity of Open-Source Database Management Systems").

6. Data warehouse DBMSs or DBMS products that support an integrated front-end tool, but which can also open their DBMS to competing applications, are included if access is achieved via open-access technology, as opposed to custom-built application programming interfaces (APIs).

7. Vendors participating in the data warehouse DBMS market must demonstrate their ability to deliver the necessary infrastructure and services to support an enterprise data warehouse.

8. Products that include unique file management systems embedded in the front-end tools, or that exclusively support an integrated front-end tool, do not qualify for this Magic Quadrant.

10. Range of connectivity/adapter support (sources and targets): native access to relational DBMS products, plus access to nonrelational legacy data structures, flat files, XML, and message queues.

11. Mode of connectivity/adapter support (against a range of sources and targets): bulk/batch and change data capture.

12. Data delivery modes support: bulk/batch (ETL-style) delivery, plus at least one additional mode (federated views, message-oriented delivery or data replication).

13. Data transformation support: at a minimum, packaged capabilities for basic transformations (such as data type conversions, string manipulations and calculations).

14. Metadata and data modeling support: automated metadata discovery, lineage and impact analysis reporting, and an open metadata repository including mechanisms for bidirectional sharing of metadata with other tools.

15. Design and development support: graphical design/development environment and team development capabilities (such as version control and collaboration).

16. Data governance support: ability to interoperate at a metadata level with data profiling and/or data quality tools.

17. Runtime platform support: Windows, Unix or Linux operating systems.

18. Service enablement (ability to deploy functionality as services conforming to SOA principles).

20. Generate $20 million or more total software revenue* from BI platform software sales annually or, in the case of open-source BI platform software, generate $20 million total company revenue annually.

21. Have customers that have deployed the vendor's BI platform as their enterprise BI solution and, in the case of vendors that also supply transactional applications, the BI platform is routinely used by organizations that do not use its transactional applications.

23. Functionality

24. Vendors in this market should provide:

25. Packaged applications to support common CRM decisions, such as customer segmentation, cross-sell or customer churn prevention, with data-mining-driven insights

26. A user interface suitable for business users (such as campaign, segment, product, sales or service managers) to perform analyses

27. The capability to access data from heterogeneous sources, particularly those with information about customer interactions and transactions (such as customer data warehouses, call centers, e-commerce or Web-site-tracking systems), as well as third-party data providers that supply customer-related information (such as demographic or market spending information)

28. Robust data-mining algorithms to provide reliable and scalable insights into a variety of types and volumes of customer data

29. The capability to make the results of the analysis available to the appropriate constituencies, such as senior executives, functional managers, salespeople or call center agents

30. Market Presence

31. At least 10 reference customers using their data-mining applications in support of CRM

34. Document imaging repository capabilities. Document imaging consists of two components. The document capture (scanning hardware and software, optical and intelligent character recognition technologies, and forms processing) portion can be carried out via native capabilities, or through a formal partnership with a third-party solution such as Kofax, EMC Captiva or Datacap. But the vendor must also be able to store images of scanned documents in the repository as "just another" content type in a folder and route them through an electronic process.

35. Records management. The minimum requirement is an ability to enforce retention of critical business documents based on a records retention schedule. Higher ratings are given for certified compliance with standards such as the Department of Defense (DOD) Directive 5015.2-STD, The National Archives (TNA), Victorian Electronic Records Strategy (VERS) and Model Requirements for the Management of Electronic Records (MoReq).

36. Workflow. The minimal requirement is simple document review and approval workflow. Higher points are given to those with graphical process builders, and serial and parallel routing.

37. Web content management. The minimum requirement is a formal partnership with a WCM provider. Native capabilities score higher than partnerships.

39. The vendor must have achieved at least $3 million in annual portal-related product and service revenue during 2007.

40. The vendor must provide sales and support for the portal product in at least two of the following five geographic regions: North America; Latin America; Europe, the Middle East and Africa (EMEA); Japan; and the Asia/Pacific (APAC) region.

41. The vendor must be able to sell an enterprise portal for deployment in a variety of scenarios, including B2E, B2B and B2C.

43. For inclusion based on market traction and momentum, vendors should have:

44. At least 10 live customer references for MDM of customer data product functionality

45. At least seven new customers for MDM of customer data products in the past four quarters

46. Generated at least $8 million in total software revenue (licenses and maintenance) related to MDM of customer data systems in the past four quarters

47. For inclusion based on near-term viability, vendors should have:

48. Sufficient professional services to fulfill customer demand during the next six months

49. Enough cash to fund a year of operations at the current burn rate — that is, if the year of operations is cash-flow-negative, then companies spend their cash reserves

50. This Magic Quadrant excludes:

51. Vendors whose MDM of customer data related revenue are too small or that focus on a limited geographical region

52. Vendors that focus on a single vertical industry market

53. Vendors that focus solely on analytical (downstream) MDM requirements

54. Marketing service providers (MSPs) or data providers that provide an external customer data reference database service, but don't provide an on-premises MDM of customer data product

55. For software vendors and MSPs that have been excluded for these reasons, see Note 3.

57. The MDM of product data market continues to mature. To reflect this, we have raised the bar for inclusion criteria relative to the updated Magic Quadrant. We include specialist vendors, as well as large enterprise software vendors, with a product in the market, along with additional vendors that Gartner views as having a unique vision or position in the market, even if they do not fully meet all the inclusion criteria:

58. Market traction and momentum — The vendor should have:

59. At least 12 live customer references for MDM of product data product functionality

60. At least eight new customers for MDM of product data products during the past four quarters

61. Generated at least $8 million in total revenue (licenses and maintenance) related to MDM of product data product software during the past four quarters

62. Near-term viability — The vendor should have:

63. Sufficient professional services to fulfill customer demand during the next six months

64. 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

65. Exclusion Criteria

66. This Magic Quadrant excludes:

67. Vendors focused on a single vertical industry market or single geographical region

68. Vendors that focus solely on analytical (downstream) MDM requirements

69. Vendors reselling another vendor's MDM of product data product, unless they exceed the revenue minimum for inclusion (see above)