Tag Archives: multi-domain MDM
Informatica supports Agile Data Integration for Agile BI with best practices that encourage good data governance, facilitate business-IT collaboration, promote reuse & flexibility through data virtualization, and enable rapid prototyping and test-driven development. Organizations that want to successfully adopt Agile Data Integration should standardize on the following best practices and leverage Informatica 9.1 to streamline the data integration process, improve data governance, and provide a flexible data virtualization architecture.
1. The business and IT work efficiently and effectively to translate requirements and specifications into data services (more…)
One of the hottest areas of master data management (MDM) is using high quality master data to drive revenue by supporting sales and channel operations. Informatica customers have racked up some terrific successes using MDM to generate a single, reliable view of customer and account information—and here’s a key reason why.
With Informatica MDM and Informatica Data Quality, sales and channel personnel gain hands-on control of customer data, product data and channel partner data and the relationships between this data. Those customer-facing teams no longer need to spend most of their time hunting for information in the CRM system, SFA system, billing system, partner management and other systems and reconciling it in spreadsheets. And they don’t need to wait on IT to round up and deliver the data they need right away.
If you’re wondering how this works, check out our six-minute how-to demo on MDM for customer account and channel partner management. This new demo offers a practical, step-by-step walk-through of how a sales, marketing and channel operations personnel can evolve from trying to sort through the clutter of contradictory data from multiple systems to leveraging a single, actionable customer account data set that powers a 360-degree customer view in their CRM system so they can improve customer acquisition and retention.
Retailers have long recognized the value of a single customer view, but the emergence of multichannel research and shopping has made achieving that ideal more difficult. Today’s consumers hopscotch across online, in-store, call center, social media, mobile, and other channels—how can retailers keep up?
If you have a single view of your retail customer, you can assess channel buying preferences and tailor marketing accordingly. You can deliver the personalized and consistent experience that discriminating consumers expect across all touchpoints. And you can take advantage of the unique cross-sell and up-sell opportunities that multichannel environments offer.
For instance, if Jane buys a $2,000 leather couch in a store and you can match her information to the email address she registered three months earlier at your Web site, you’re in a great position to pitch matching pillows with a personalized email.
But, as outlined in a new Informatica executive brief, siloed data systems for point of sale (POS), e-commerce, call centers, and more make it difficult for retailers to achieve a single customer view. The brief includes survey results from a leading research organization, including the following statistics:
- 92 percent of retailers don’t integrate customer data from all channels
- 68 percent of companies cite improving customer data integration as a top priority for 2010
- Less than 25 percent of retailers extend personalized loyalty programs across all channels
Just this week, leading research firm Gartner, Inc. published its 2010 predictions for MDM. There is one prediction related to multidomain MDM that I found particularly interesting. It mentions that the number of companies shopping for multidomain MDM solutions has increased. Now, why is that?
To get some insight into MDM purchasing and implementation trends, we simply need to look at companies that began their MDM journey in the past five years, especially those companies that started off with a single domain, such as customer data. Many of these MDM pioneers have since expanded their implementation to other domains such as finished products, materials, price, employees, and so on. But how did they do that? By using the same multidomain MDM platform? Or by separately implementing distinct single-domain MDM applications, such as one for customer data and another for product data?
Gartner contends that no vendor has a comprehensive multidomain MDM technology that handles all different industry use cases using different data domains. A true statement if you are purchasing an “MDM application.” Similar to packaged applications, like ERP or CRM which manage back-office or front-office operations, purpose-built “MDM applications” that focus on a single data domain for a certain industry can, in fact, only handle use cases that are specific to that data domain. So, Gartner is right in saying that a customer that uses “MDM applications” will have to work with different MDM vendors and technologies.
However, this should not be the case if you use an “MDM platform.” We can think about the situation as similar to database or web server technology; these technologies are pretty horizontal and flexible enough to address just about any use case in any industry. In the same way, a multidomain “MDM platform” is flexible enough to accommodate any data domain, and has the ability to cleanse, enrich, match, merge, and display data relationships across multiple domains.
What I don’t agree with in the Gartner predictions is the statement that only large vendors will provide “stronger” multidomain MDM. In my experience, these vendors are largely packaged application vendors, and coming from that heritage, they currently sell different single-domain “MDM applications.” While they talk up “multidomain MDM,” their customer base tells a different story – they have to use multiple distinct MDM applications because no single MDM application can accommodate diverse use cases involving different data domains. In contrast, Siperian has customers in different verticals using our multidomain “MDM platform” to manage multiple data domains on the same platform. Our customers don’t need different “MDM applications” because they’re fully capable of implementing multidomain MDM on their single Siperian platform.
Stay tuned for my forthcoming blog discussing the differences between the “MDM application” and “MDM platform” approaches for cross-industry, multidomain MDM use cases.
In the meantime, what do you think?