Your SlideShare is downloading. ×
RDM field reports   aaron zornes (new york city - october 2013) v4 print
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

RDM field reports aaron zornes (new york city - october 2013) v4 print

674
views

Published on

overview of commercial Reference Data Management (RDM) tools

overview of commercial Reference Data Management (RDM) tools

Published in: Technology

1 Comment
0 Likes
Statistics
Notes
  • Be the first to like this

No Downloads
Views
Total Views
674
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
43
Comments
1
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Examples:
    Hierarchy of products in production at all my customers in the aerospace industry in Japan
    Or, Hierarchy of costs centers associated with distribution in the Province of Ontario in the country of Canada
    Example of shared semantics – Turkey the product, may not mean the same thing as Turkey the country.
  • BACK STORY:
    - For many software vendors and Global 5000 enterprises, Reference Data Management (RDM) is a relatively new offspring of Master Data Management (MDM) functionality. 
    - RDM provides the processes and technologies for recognizing, harmonizing and sharing coded, relatively static data sets for “reference” by multiple constituencies (people, systems, and other master data domains). 
    - Such a system provides governance, process, security, and audit control around the mastering of reference data. 
    - In addition, RDM systems also manage complex mappings between different reference data representations and different data domains across the enterprise. 
    - Most contemporary RDM systems also provide a service-oriented architecture (SOA) service layer for the sharing of such reference data.
    - Prior to the availability of commercial RDM solutions, organizations built custom solutions using existing software such as RDBMS, spreadsheets, workflow software (business process management or BPM) and other tools. 
    - Such systems often lacked change management, audit controls, and granular security/permissions. 
    - As a result, these legacy solutions have increasingly become compliance risks. 
    - Because reference data is used to drive key business processes and application logic, errors in reference data can have a major negative and multiplicative business impact.
    - Mismatches in reference data impact on data quality affect the integrity of BI reports and also are a common source of application integration failure. 
    - Just as businesses no longer build their own CRM, ERP, and MDM systems, so too are organizations beginning to acquire commercial RDM solutions, which can be easily tailored or configured and have the full ongoing support of a major software vendor. 
    - Increasingly, many large enterprises have begun to make RDM their initial test case or proof-of-concept for their MDM evaluations.
    - As a consequence, MDM vendors are rushing to market RDM solutions to apply an MDM approach for centralized governance, stewardship and control. 
    - Clearly, managing “simple” reference data will prove to be a key sales entry point for large enterprises and their MDM vendors. 
    - Additionally, RDM can be expected to become a "ramp up" point of entry for many organizations planning for CUSTOMER, PRODUCT master and other domains, as well as an entry point into master data governance.
    - Moreover, RDM is needed in both operational and analytical MDM use cases where the capability is often used to provide attributes, hierarchies and KPIs.
  • An easy example of adaptations are customized hierarchies. For example, the geographic hierarchy used by:
    Finance may remake the geographic hierarchy to reflect the corporations legal organization (operating units vs. tax havens)
    ERP system/Supplier management may organize their countries / localities by manufacturing facilities
    Shenzhen vs. Hanoi vs. Canton, OH
    Sales economically similar countries (developed vs. middle income vs. emerging)
    OECD Countries
  • Coming to market during 2013-13 are RDM solutions characterized by multiple, diverse levels of integration with market-dominant MDM hubs (IBM, Informatica, Oracle, SAP) as well as repackagings of existing mid-market MDM capabilities to address RDM business needs (e.g., Microsoft's RDM product for Microsoft Master Data Services and Oracle's ongoing sales campaign for Oracle Hyperion DRM, etc.).
  • USD US Dollar American Samoa, British Indian Ocean Territory, Ecuador, El Salvador, Guam, Haiti, Marshall Islands, Micronesia, Northern Mariana Islands, Palau, Panama, Puerto Rico, East Timor, Turks and Caicos Islands, United States, Virgin Islands
    Reference data intersects with multiple domains (and other reference data sets). Often these relationships involve multi-cardinality. In our trivial example, unlike JPY and CNY, USD (like the Euro) is used as the official currency in multiple countries. More complex examples would include financial reporting. The US is currently transitioning from GAAP to IFRS; this requires the adoption of a new rules that affect how accounts are classified and treated (in essence new reference data with the same identifiers, but different rules). This means that the chart of accounts of an organization, organized for GAAP, will need to be remapped and new hierarchies created for IFRS. The need to document reference data, and their complex connections to other domains requires the platform to have robust data / semantic modeling.
  • When dealing with reference data, simple versioning is often not enough. This is because there are relationships between versions. The platform needs to be able to model inter-temporal relationships.
    In the example beneath, without maintaining the linkages between versions, an analyst would not necessarily recognize that 2013.221114-8 were split from 2007.221119 (perhaps assuming, based on the description that 221119 and 2221114 were equivalent because they both mention solar power. We see the issue in reverse with 2013.31124 which is a union of 2007.311222-3. However, we cannot treat this relationship as a database-style foreign key because novel additions in a later would not necessarily have an antecedent in the prior edition.
  • Managing versions is not always a matter of going back in the past. When we think about private reference data (financial and organizational hierarchies, employee organizational changes) it is often modified when corporate actions / change takes place. For the organization, understanding how changes to this reference data affects not only downstream applications, but other linked domains is important. This is especially true when making modifications to hierarchies because often identifiers are re-used between periods.
    This means that the platform needs to support not just past, but also the ability to simulate and assess the impact of future changes.
    Current period hierarchies are necessary, but insufficient for performance analysis. Transactional data records the attributes, identifiers and hierarchies that were official at the time of their of execution. This reference data changes over time (especially in cases of reorganization). This means that the analytical system needs to have access to current and prior versions of reference data. Without consistent definitions (or translations) the analysis will be comparing apples to oranges. Access to future versions (due to reorgs) can be useful for when modeling the impact of change.
  • Coming to market during 2012-13 are RDM solutions characterized by multiple, diverse levels of integration with market-dominant MDM hubs (IBM, Informatica, Oracle, SAP) as well as repackagings of existing mid-market MDM capabilities to address RDM business needs (e.g., Microsoft's RDM product for Microsoft Master Data Services and Oracle's ongoing sales campaign for Oracle Hyperion DRM, etc.).
  • Transcript

    • 1. Product Evaluation Criteria & Field Reports for the Leading RDM Solutions 8 th Annual MDM & Data Governance Summit New York City October 20-22, 2013 Aaron Zornes Chief Research Officer The MDM Institute aaron.zornes@tcdii.com www.linkedin.com/in/aaronzornes @azornes +1 650.743.2278
    • 2. MDM Working Definitions Master Data Management (MDM) Master Data Management (MDM) Authoritative, reliable foundation for data used across many applications & constituencies with goal to provide single view of truth no matter where it lies. Customer Data Integration Customer Data Integration (CDI) (CDI) Processes & technologies for recognizing a customer & its relationships at any touch-point while aggregating, managing & harmonizing accurate, up-to-date knowledge about that customer to deliver it ‘just in time’ in an actionable form to touch-points. Product Information Mgmt Product Information Mgmt (PIM) (PIM) Processes & technologies for recognizing PRODUCT, SUPPLIER, & PRICING master data CDI is mandatory first step for most organizations on journey to MDM © 2013 The MDM Institute www.the-MDM-Institute.com
    • 3. MDM Working Definitions - continued Multi-Entity Master Data Management (MDM) Multi-Entity Master Data Management (MDM) An MDM solution to concurrently manage multiple, diverse master data domains (customers, accounts, products) across intraand extra-enterprise business processes Master Reference Data Management (RDM) Master Reference Data Management (RDM) Non-volatile reference data shared across the enterprise in context within applications (& possibly within the industry via “exchanges”); examples: units of measure; currency rates; calendars; other look-up tables Large enterprises assume MDM = multi-entity MDM when evaluating software; RDM remains a key variable among the vendors as few vendors are enabled (yet) © 2013 The MDM Institute www.the-MDM-Institute.com
    • 4. What is Reference Data? Reference data =“coded, semantically stable, relatively static data sets shared by multiple constituencies” (people, systems, & other master data domains) Industry Customers Geo Cost / Revenue Acct Sales Person Business Unit ID Product In the logical view, private & public forms of reference data connect domains & application; consistent values (& semantics) required for multi-domain views & hierarchies © 2013 The MDM Institute www.The-MDM-Institute.com
    • 5. Why Reference Data? Why Now?   Errors in reference data will ripple outwards affecting quality of master data in each domain, which in turn affects quality in all dependent transactional systems RDM needed in both operational & analytical MDM use cases where capability often used to provide attributes, hierarchies & KPIs Inconsisten t Reporting Transaction Failure Regulatory Non-compliance Systemic Failure Central role of reference data means RDM becoming “starting point” for many organizations planning MDM & MDG © 2013 The MDM Institute www.The-MDM-Institute.com
    • 6. RDM Prologue     In addition to MDM functionality, RDM systems also manage complex mappings btw different reference data representations & different data domains across the enterprise Manual or custom RDM often lack change management, audit controls, & granular security/permissions Because reference data is used to drive key business processes &application logic, errors in reference data can have a major negative & multiplicative business impact Mismatches in reference data impact on data quality affect the integrity of BI reports and also are a common source of application integration failure Just as businesses no longer build own CRM, ERP, &MDM systems, so too are organizations beginning to acquire commercial RDM, which can be easily tailored or configured & have full ongoing support of major software vendor © 2012 The MDM Institute www.the-MDM-Institute.com
    • 7. Reference Data Categories Multi-Domain RDM Use Cases Public (External) SemiPrivate? (Shared) Countries & Subdivisions (FIPS10) Currencies (ISO 4217) Time Zones (ISO 8601) Industry Classification (NAICS, ISIC) Customized Public Reference Standards (e.g. customized D&B) Real-Time / Transactional RDM Use Cases Security Prices SWIFT BIC Codes (Payments) ICD-9/10 Codes (Healthcare) ACORD/ISO Codes (Insurance) Shared Private Data (Finance) Legal Entities Chart of Accounts Organizations Employees Private (Internal) (i.e., much of HR & Finance Data) © 2013 The MDM Institute www.The-MDM-Institute.com Reference data required for transaction processing
    • 8. Why Manage Reference Data Independently? (“Hub of hubs”? Federated vs. Centralized?) Industry Geo Geo Customers Sales Person Geo ERP Cost / Revenue Acct Finance (NAICS, ISIC) (ISO3166, FIPS) Business Unit ID Geo Geo HR Geo Product Geo BI/Analytics In the logical model, reference data connects domains & applications; in implementations local copies exist for each consumer; challenges include: governance, synchronizing, versioning, & custom hierarchies/internationalizations © 2013 The MDM Institute www.The-MDM-Institute.com
    • 9. Critique of Current Approaches for Multi-Domain Reference Data RDM Solution Drawback Recommendation Custom-built, manual solutions Heavy TCO burden Avoid unless reference data demands are truly unique Spreadsheets Difficult to govern, secure, version, & audit; no modeling, poor hierarchy management Poor cross-domain support, no classification mapping, few enterprise integration options Distribute data in spreadsheets; govern data in RDM solution Repurpose hierarchy management solution (MSFT MDS, ORCL DRM) Customize existing domain-specific MDM (Customer or Product) Rudimentary data modeling, lifecycle mgmt capabilities, & governance features (esp. authoring & workflow) ERP / Enterprise Limited governance, versioning, Application distribution; also reference data customized use in app may have limited appeal in other systems Real-time / industryPremium priced R/T RDM specific RDM solutions do not represent good © 2013 The MDM Institute economic sense www.The-MDM-Institute.com Seek out multi-domain RDM solution with hierarchy management Use multi-domain RDM solution to maintain connections & govern/update into CDI & PIM via data services Master in external platform. RDM can be used to govern baseline set, versions and adaptations Leverage R/T RDM solutions for R/T use cases (trading, claims processing, payments)
    • 10. “Top 10” RDM Technical Evaluation Criteria 1. 2. 3. 4. 5. Administration of diverse reference data types Ability to map reference data Management of reference data sets Architecture/performance Hierarchy management over reference data sets 6. Connectivity/integration 7. Import & export 8. Versioning support 9. Security & access control 10. E2E lifecycle management Coming to market are RDM solutions characterized by multiple, diverse levels of integration w/ market-dominant MDM hubs as well as repackagings of existing mid-market MDM solutions – HOW TO EVALUATE? © 2013 The MDM Institute www.The-MDM-Institute.com
    • 11. “Administration of Diverse Reference Data Types” RDM Top 10 Eval Criteria #1 Private Ref Data Public Ref Data From R. Thompson,/Credit Suisse, “Multidomain Enterprise Reference Data,” 7th Annual MDM & Data Governance Summit New York 2013 RDM solution should support a wide mix of data structures from name:value pairs to hierarchies (see criteria #5). © 2013 The MDM Institute www.The-MDM-Institute.com
    • 12. “Ability to Map Reference Data” – pt. 1 (cross-domain mapping) LOCATIONS FINANCE Issuing Country (ISO3166) USA CHN JPN LOCATION & FINANCE RDM Top 10 Eval Criteria #2 Name ISO 4217 Code US Dollar USD Yuan Renminbi CNY Japanese Yen JPY Official Currency USD USD USD USD USD USD USD USD USD USD USD USD USD USD USD USD CNY JPY © 2013 The MDM Institute ISO3166 ASM IOT ECU SLV GUM HTI MHL FSM MNP PLW PAN PRI TLS TCA USA VIR CHN JPN ISO 3166 Name Code USA United States of America CHN People’s Republic of China JPN Japan ASM American Samoa IOT British India Ocean Terr. ECU Ecuador SLV El Salvador GUM Guam HTI Haiti MHL Marshall Islands FSM Micronesia MNP Northern Mariana Islands PLW Palau PAN Panama PRI Puerto Rico TLS East Timor TCA Turks and Caicos Islands VIR Virgin Islands RDM solutions need to preserve values & mappings between reference data sets – both in domain and across domains. www.The-MDM-Institute.com
    • 13. “Ability to Map Reference Data” RDM Top 10 – pt. 2 (temporal referential integrity) Eval Criteria #2 2013 VERSION 2013 NAICS 311224 221114 221115 221116 221117 221118 2007 VERSION Description Soybean and Other Oilseed Processing Solar Electric Power Generation Wind Electric Power Generation Geothermal Electric Power Generation Biomass Electric Power Generation Other Electric Power Generation Description 311223 Other Oilseed Processing 221119 MERGE 2007 NAICS 311222 Other Electric Power Generation - solar electric power generation Soybean Processing SPLIT RDM solution needs to maintain links between versions, creating a migration path between versions of reference data. “ Crosswalks” are important for understanding how something changed. © 2013 The MDM Institute www.The-MDM-Institute.com
    • 14. “Mgmt of Reference Data Sets” ( Governance workflows) RACI Sequence of interactions R Permissions Responsibilities Ac l tab n ou c s rtie a ep R A A A RDM Top 10 Eval Criteria #3 Tasks Update sales hierarchies Change industry classifications Approve hierarchies and effective dates Approve industry classifications Approve merge into effective dated User Rogers Romanova Stark Banner Fury An RDM solution needs to support governance workflows; includes defining: responsible & accountable parties (including systems), permissions & area of responsibility for each party (field, instance, container level), how parties interact/tasks, & auditing/history… © 2013 The MDM Institute www.The-MDM-Institute.com
    • 15. “Hierarchy Management Over RDM Top 10 Reference Data Sets” Eval Criteria #5 Viewing customers by industry classification SIC Codes Customer & SIC Code Mapping Viewing drugs by Active Ingredient interactions and ICD10 Codes ICD-10 Codes Active Ingredients & ICD10 Mapping Active Ingredients & Product Mapping RDM solution should harness relationships between reference data sets & existing party or thing data to create hierarchies © 2013 The MDM Institute www.The-MDM-Institute.com
    • 16. “Versioning Support” (a.k.a. time travel) Cost Centers (as-of 2013 Q2) Cost Centers (Current) RDM Top 10 Eval Criteria #8 Cost Centers (Effective 2013 Q1) RDM solution needs versioning & “as of” / effective dating to support recall of reference data values, relationships or hierarchies. (versioning has *major* implications for analytics/ BI!) © 2013 The MDM Institute www.The-MDM-Institute.com
    • 17. Reference Data Management Strategic Planning Assumption    Through 2013, reference data will emerge as a key entry point for enterprises & in turn unduly influence choice of MDM for Customer, Product & other domains; large enterprises will continue to mandate that REFERENCE data be part of MDM platform's native entity types During 2013-14, MDM vendors will begin to market RDM to apply an MDM approach for centralized governance, stewardship & control; Sis will move into this market via OEMing of Informatica & IBM MDM into "securities master" mkt under pricing umbrella of GoldenSource By 2015, pervasive, low cost RDM will be commoditized via the efforts of Ataccama, Microsoft & Oracle Managing “simple” reference data will prove to be a key sales entry point for MDM vendors © 2013 The MDM Institute www.The-MDM-Institute.com MDM MILESTONE
    • 18. Competition for Multi-Domain RDM   Custom-built, manual solutions Hierarchy management system adaptations   Custom MDM domain type   Lack of data modeling flexibility, rudimentary lifecycle management capabilities & limited data governance features, esp. authoring & workflow Multi-domain RDM   Do not readily support publish-subscribe, classification mapping, etc. RDBMS vs. semantic/OODBMS Purpose-built or industry-specific RDM  Premium priced real-time RDM solutions do not represent good economic sense Seek out multi-domain RDM solution providers that understand & have experience addressing complexity of reference data © 2013 The MDM Institute www.The-MDM-Institute.com
    • 19. “Top 10” RDM Technical Evaluation Criteria Re-Cap 1. 2. 3. 4. 5. Administration of diverse reference data types Ability to map reference data Management of reference data sets Architecture/performance Hierarchy management over reference data sets 6. Connectivity/integration 7. Import & export 8. Versioning support 9. Security & access control 10. E2E lifecycle management © 2013 The MDM Institute www.The-MDM-Institute.com
    • 20. Reference Data Management Case Study: Mega Financial Svcs Provider - DnB NOR ASA Business Issues     Need to manage reference data provided by external standard bodies Reference data changes managed manually No clear ownership of reference data across the business Reference data must be entered, updated & managed in multiple places, yielding duplication & introducing errors Solution      Manage & consolidate Reference Data for data warehouse load Manage MDM code tables & map MDM codes to legacy systems codes Publish reference data (changes) to consuming systems Provide governance, process, security, audit control around reference data mastering Apply commercial software (IBM RDM Hub Asset) rather than build RDM is major step in longer term transformation of the bank to move from silo-driven business & IT culture to become “ONE – Group” © 2013 The MDM Institute www.the-MDM-Institute.com
    • 21. Reference Data Management Case Study: Mega Financial Svcs Provider – BNP Paribas Business Issues    Need to integrate reference data into the bank's service-oriented architecture (SOA) infrastructure Lack of harmonization & propagation of reference data across the bank's groups (lines of businesses) Need to streamline the Data Governance process via a cross-business governance (group-level) Solution  Evolve MDM capabilities      Manage scope     "Think big but start small" orientation Provide a controlled perimeter for master data & processes Centralize the data governance function Create value at the MDM level (point of truth = point of creation) Identify what’s in MDM and what’s not & what is RDM Manage master data & processes independently without requiring strong coupling with the business Keep unstructured or transactional data out of MDM scope Apply commercial software (Orchestra Networks EBX) rather than build RDM is a key enabler of its MDM Shared Services Center COE whose charter is to provide shared enterprise data services © 2013 The MDM Institute www.the-MDM-Institute.com
    • 22. MDM Institute Field Reports – RDM     Aprimo LRDM (Teradata) ASG ROCHADE (Metadata-driven RDM) Ataccama RDM IBM RDM Hub  Informatica RDM  Kalido  Microsoft RDM (to be announced)  Oracle Hyperion DRM  Orchestra EBX  Profisee  SAP MDG-R  Software AG WebMethods OneData ** General-purpose or multi-domain RDM, not industry-specific solutions such as capital markets, pharma, e.g., AIM, Asset Control, Eagle, Golden Source , Kingland Systems 360 Data, and RSD © 2013 The MDM Institute www.the-MDM-Institute.com
    • 23. Reference Data Management “Top 10” Technical Evaluation Criteria 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. Ability to map reference data Administration of reference data types Management of reference data sets Architecture Hierarchy management over sets of reference data Connectivity Import and export Versioning support Security & access control E2E lifecycle management Understanding scope, diversity & limitations of nascent RDM offerings is challenging © 2013 The MDM Institute www.the-MDM-Institute.com
    • 24. Field Report: IBM MDM Reference Data Mgmt Hub Strengths Caveats  Purpose-built,  Lack of BPM integration commercially proven RDM & workflow (needs configurable workflow)  Utilizes IBM MDM  Lacks Cloud architecture foundation & SaaS offering  Full function with strong  Perception of excessive taxonomy support & software stack foundation mappings  Missing adapters for  Ease of deployment, other IBM software implementation, & use (Discovery, etc.) & other  Market momentum1 major apps such as Oracle & SAP 1 – Achmea, ANZ Bank, BCBS of North Carolina, CIT, Citi Mortgage, DnB NOR ASA, IBM Office of the CIO, LabCorp, RBS Citizens, Standard Bank of South Africa and The CIT Group © 2013 The MDM Institute www.the-MDM-Institute.com
    • 25. Field Report: Orchestra Networks EBX5 for RDM Strengths ● Robust solution for centralized DG, mgmt, stewardship & distribution of reference data ● Enterprise-scalable RDM1 ● Strong taxonomy support, hierarchy mgmt & mappings Caveats ● Nascent AP & LA presence ● Growing (but small) # of consultancies ● New Business Glossary / Information (good for counterparty risk mgmt) Gov (Q4) ● Model-driven ease of ● Vulnerability in rapidly deployment, implementation, & evolving mkt crowded use with mega vendors & (built-in process flows + semantic DB underpinning) nouveau MDM vendors ● Unique/built-in support for intertemporal references, private ● Under invested in mktg reference data (esp. Fin, HR) 1- Citi, Credit Agricole, BNP Paribas, Credit Suisse, National Bank of Canada, McDermott International, Sabre, Michelin... ● Cloud based, SaaS option © 2013 The MDM Institute www.the-MDM-Institute.com
    • 26. Field Report: Software AG webMethods OneData Strengths Caveats  Robust solution for centralized DG,  Nascent market mgmt, stewardship, & distribution of presence enterprise reference data  Shortage of  Proven multi-domain RDM1 knowledgable  Deep cross-referencing/hierarchy consultancies  SaaS capabilities capabilities w/impact analysis  Strong taxonomy support/ mappings not marketed  Under invested in for public & private reference data  Can ingest customer metadata models marketing & UI wraps around model 1 – Allianz, Avon Products, Chubb  Model-driven ease of deployment, Insurance, General Electric, Givaudan, Nokia, Parexel, Pepsico, SwissGrid, Wellpoint, implementation, & use (integration w/ BPM for SOA & MDM deployment)  Stable, deep pockets vendor © 2013 The MDM Institute … 2 www.the-MDM-Institute.com 2 – 2012 est. revenue $1.2B, 5K employees, 70 countries
    • 27. BOTTOM LINE  RDM is major IT initiative being undertaken by large # of marketleading global 5000 enterprises  Both as IT discipline & COTS software solution, RDM solutions are being brought to market at an increasing pace   Repackagings of existing mid-market MDM capabilities (MSFT RDM product for MSFT MDS, ORCL DRM, etc.)  Best of breed multi-domain RDM (Ataccama, Orchestra Networks, Profisee, Software AG, …)   Mega vendor MDM hubs (IBM, INFA, ORCL, SAP) Expect to pay between US$250K-US$1M for commercial solution RDM is good entry-level project to show success for initial MDM investment which can be built on as a data governance model Seek out multi-domain RDM solution providers that understand & have experience addressing complexity of reference data © 2013 The MDM Institute www.the-MDM-Institute.com
    • 28. MDM & Data Governance Summit™ Conference Series MDM & Data Governance Summit New York Sheraton Times Square ▪ October 20-22, 2013 MDM & Data Governance Summit Singapore Marina Bay Sands Resort ▪ October 31-November 1, 2013 • MDM & Data Governance Summit Shanghai 2014 Shanghai International Convention Center ▪ Spring 2014 • • MDM & Data Governance Summit Europe 2014 Radisson Portman BLU - London ▪ May 19-21, 2014 MDM & Data Governance Summit Asia-Pacific 2014 Doltone House, Darling Island Wharf – Sydney ▪ May 2014 • MDM & Data Governance Summit Tokyo 2014 Belle Salle Iidabashi First – Tokyo ▪ June 2014 MDM & Data Governance Summit Toronto The Carlu ▪ June 2014 MDM & Data Governance Summit San Francisco Hyatt Fisherman’s Wharf– San Francisco ▪ July 2014 “More MDM programs get their successful start at MDM & Data Governance Summits than anywhere else” © 2013 The MDM Institute www.the-MDM-Institute.com
    • 29. Aaron Zornes Founder & Chief Research Officer www.the-MDM-Institute.com aaron.zornes@tcdii.com www.linkedin.com/in/aaronzornes +1 650.743.2278 @azornes Authoritative Independent Relevant © 2013 The MDM Institute www.The-MDM-Institute.com
    • 30. About the MDM Institute  Founded in 2004 to focus on MDM business drivers & technology challenges  MDM Advisory Council™ of 150 Global 5000 IT organizations with unlimited advice to key individuals, e.g. CTOs, CIOs, data architects   MDM Road Map & Milestones™ annual strategic planning MDM Alert™ newsletter MDM Market Pulse™ surveys  MDM Business Council™ website access & email support to 35,000+ members    monthly MDM Fast Track™ one-day public & onsite workshop rotating quarterly through major North American, European, & Asia-Pacific metro areas MDM & DATA GOVERNANCE SUMMIT™ annual conferences in London, Madrid, NYC, San Francisco, Singapore, Sydney, Tokyo & Toronto assumptions About Aaron Zornes  Most quoted industry analyst authority on topics of MDM, RDM & Data Governance  Founder & Chief Research Officer of the MDM Institute  Conference chair for Information Mgmt’s MDM & Data Governance Summit conferences  Founded & ran META Group’s largest research practice for 14 years  M.S. in Management Information Systems from University of Arizona “Independent, Authoritative, & Relevant” © 2013 The MDM Institute www.The-MDM-Institute.com
    • 31. MDM Institute Advisory Council Representative Members  3M Advisor agrees to provide Institute’s Bell Canada consultants with advice & insight regarding Caterpillar Cisco Systems the use of MDM software & related business Citizens Communications processes at Advisor’s convenience COUNTRY Financials Educational Testing Services Advisor agrees to participate in at least one GE Healthcare Honeywell fifteen (15) minute survey teleconference call Information Handling Services every sixty (60) days Intuit JC Penney Optionally, Advisor may respond to the biMcKesson Medtronic monthly survey request via email or InternetMicrosoft based survey fulfillment Motorola National Australia Bank Results of such MDM market research Nationwide Insurance Norwegian Cruise Lines surveys shall be aggregated by the Institute Novartis & made available to all Advisory Council Polycom Roche Labs members Rogers Communications Scholastic In no case, shall any Advisor-specific survey SunTrust information be made available to other Sutter Health Visa parties unless Advisor has specifically Westpac agreed to the release of such information in Weyerhaeuser writing 150 organizations who receive unlimited MDM advice to key • • • • • •  • • • • •  • • • • •  • • • • • • •  • • • • • • individuals, e.g. CTOs, CIOs, & MDM project leads © 2013 The MDM Institute www.The-MDM-Institute.com
    • 32. How to Leverage the MDM Institute  Kick start the “MDM evaluation process”    Fine tune in-process MDM strategies   Due diligence on reference checking & contract details Stay ahead of curve via MDM Business Council    Attend public workshop Bring workshop on-site Re-qualify every 6 months via survey Receive MDM Alerts & access to Web-hosted research Increase your knowledge & negotiating strengths via MDM Advisory Council Membership   Participate in monthly email surveys & receive updated industry scorecard Receive monthly MDM consultation via telephone “Independent, Authoritative, & Relevant” © 2013 The MDM Institute www.the-MDM-Institute.com