• No results found

“Top 10” MDM Evaluation Criteria 1 Data model

2. Business services 3. Identity resolution 4. Data governance 5. Architecture 6. Data management 7. Infrastructure 8. Analytics 9. Developer productivity 10.Vendor integrity

Infrastructure fracas will escalate as mega app vendors rush to dominate business services/processes & data models as high ground

#1 Criteria = Data Model

 Data model to support complex roles & relationships

Party (customer, supplier, employee) & product Reference – including price, location

Demographic profile – e.g., name, address, phone number, marital

status, etc.

Roles & relationships between parties – including B2B company

hierarchies & B2C householding

Additional related entities – e.g., entitlements, prices, & privacy

preferences

Data heritage, change history & survivorship

 Industry-specific (vertical) extensions

 Ability to import industry standard or custom-built

data models – e.g., IBM IAA, IBM BDW, OASIS CIQ, Siebel CIF, Hogan CIS, Dendrite

 Ability to support 3rd party hierarchy structures – e.g., D&B, Austin-

Tetra

 Vendor roadmap to “link” party & product domains

Depth & breadth of data model – plus ability to adapt statically & on-the- fly – provide a solid MDM foundation

#2 Criteria = Business Services

 External workflow engine & web services transaction support –

e.g., business process management (BPM)

 Rules engine

 E2E support with operational applications with accelerators for

complex transactions – e.g., new account origination & order to cash

 Business semantic-driven horizontal customer processes – e.g.

add party, change address, retire customers

 “Best practice” templates for both horizontal &

vertical customer – e.g., related processes

 Compatibility with existing infrastructure investments – e.g.,

Tibco, MQ-Series, etc.

 Standards – e.g., OMG’s Model-Driven Architecture (MDA), WS-

Coordination, WS-Transaction, & BPEL

 Vendor roadmap to process/policy hub solution via SOA

Functionality & extensibility of business services are critical evaluation criteria for MDM solutions – longer term “process hubs” are the goal

#3 Criteria = Identity Resolution

 Very high performance matching/aggregation/search

 Ability to generate or incorporate “universal” master keys or

global IDs

 Cross-reference management – e.g., 1:M support, enforcement of

cross-referencing

 Support for all identity types – e.g., individual, household,

organization

 Change detection & event mgmt – e.g., propagation

& validation, in-doubt resolution

 Support for privacy regulations – e.g., California SB-168 for

remediation of SSN off public documents

 E2E data mgmt processes to enforce data quality  Enable regulatory & privacy mandates

 Non-obvious/intrusive entity resolution

Smart matching plus effective human intervention – & automated actions – yield better identity management

#4 Criteria = Data Governance

 Process design capture tools

 Accelerators for people, process & technology integration – e.g.,

DG steering committees, process councils, & corporate/LOB data stewards

 Tactical data steward consoles  Integrated metrics

Based on recognition of issues at hand, an improving economy, & increasing regulatory requirements, businesses are now recognizing the opportunity to

take a more strategic view of data governance

#5 Criteria = Architecture

 Multi-modality architectures

 Virtual/registry  Persistence  Confederation

 Multi-modal use cases

 Analytical MDM  Operational MDM  Collaborative MDM

 Multi-modal security

 Profile access control

 Integration with security of DB, CRM & ERP  Role-based user rights mgmt

Given the generational evolution of MDM styles, it is vital to select a MDM solution specifically tuned

for a given set of long term MDM requirements

#6 Criteria = Data Management

 Consolidation & survivorship rules – e.g., intelligent merge/unmerge  Application- & role-level authorization

 Data cleansing

 Address cleansing & standardization  Pre-built integration to leading DQ tools  Closed loop-DQ

 Data profiling

 Central enforcement & tracking of DQ

 Integration with Web-enabled aggregator data  Complex, long running transaction

 Support for multiple master data types – e.g., reference,

transactions

 Comprehensive set of customer attributes for complete profile  History & audit trails

Goal is to create end-to-end data mgmt processes that may be invoked by other major customer facing subsystems in addition to CRM package

#7 Criteria = Infrastructure

 Scalability – e.g., in-memory or cache DBs; just-in-time aggregation  Manageability - e.g., system management & monitoring tools

 Accessibility – e.g., ability to service wide-range of performance levels  Availability – e.g., resilience to various failure situations such as

hardware & network outages; continuous data maintenance/ synchronization

 Rigorous multi-model support for all integration modes

 Real-time

 Tightly-coupled – e.g., COM, Java, CORBA)

 Loosely-coupled (IBM MQ Series, XML/HTTP, integration servers)

 Near real-time

 Loosely-coupled (IBM MQ AMI, XML/HTTP, integration servers)

 Batch

 EDI, RosettaNet

 Pre-packaged integration processes & templates

 Intelligent routing – e.g., alerts, content-based routing & pub-sub

As single point of failure asset, MDM internal infrastructure has all the requirements of mission-critical applications & must be evaluated so

#8 Criteria = Analytics

 Customer segmentation & targeting for cross-sell & up-sell  In-line analytics for closed-loop marketing

 Data profiling to manage “degree of trust” associated with

given master customer data source – e.g., completeness, uniqueness, accuracy, & lineage)

No longer are batch-oriented data marts or data w arehouses sufficient to provide fundamental analytics necessary to drive customer profitability &

value assessments (to enable JIT & differentiated service)

#9 Criteria = Developer Productivity

 Life-cycle approach

 Systems management tools

 Change management  Software distribution  Testing

 CMM compliance  Methodology

MDM ultimate goal is user-driven rules management, yet IT

professionals (data stew ards, et al) must set up & fine-tune this mission- critical infrastructure

#10 Criteria = Vendor Integrity

 References vs. proof-of-concepts

 Professional services – work done by IT vendor to assist in the delivery of

solution via methodology, process, skills transfer, etc.

 Quality  Breadth

 Customization

 Corporate agility – Ability to respond, change direction, etc. in

Responsiveness/Development Processes/Flexibility

 Personnel – Mix of skills, expertise, experience, etc.

 Leadership/available skills  Expertise/intellectual property

 Financials – Combo of financial resources, liquidity, etc.

 Access to capital  Profitability

 Growth rate

 Vendor pricing models

MDM solutions have all the requirements of mission-critical applications

vendors must be evaluated so

Ancillary MDM Solutions

Related documents