Business Intelligence Network business intelligence resources

Blog: William McKnight

Main

March 25, 2008

MDM ROI and Justification at the MDM Summit

I'll be speaking on "MDM ROI and Justification" at the MDM Summit this Sunday, March 30 from 6:30 - 8:00 in the night school program at the San Francisco Hilton.

Why would you want to do such a thing? No, I don't mean come to the session, I mean MDM itself. Come to find out. The top six frameworks for MDM justification will be presented. Link.

September 27, 2007

Office 14 and MDM

Leave it to Microsoft to make technology inexpensive and easy. Quite possibly (i.e., link) Office 14 will begin to include the Stratature Master Data Management (MDM) acquisiton. Microsoft has helped to demystify data warehousing and data mining and now begins to do the same with MDM.

For the MDM market, this is a partial verification and will expose MDM to a wider audience. Those who are opposed to Microsoft philosophically or don't believe it will scale will go elsewise for their tool.

Tools are a start, but can obfuscate the need to address data quality, still the largest impediment to information management success.

Continue reading "Office 14 and MDM" »

June 9, 2007

Microsoft Buys Stratature For Master Data Management

Link to article. I guess my entry from May 24 was timlier than I thought. This really legitimizes master data management as a force. Stratature had not made great strides, but it does have a nice complement of the requisite MDM functionality that I discuss in my fullday MDM course including the hub, publish/subscribe, and modeling facilitation. Although Stratature hasn't made short-lists in my recent MDM strategies with Fortune clients, I expect its presence to increase now.

I expect more midsize companies to now get involved in MDM and, over time, for the price points for enterprise MDM software to settle.

Continue reading "Microsoft Buys Stratature For Master Data Management" »

May 19, 2007

Where to put your enterprise master data

What’s on my mind tonight is where companies are putting their enterprise master data and I do think ‘enterprise’ is the key word here. It takes proactive planning, and a dedicated project, to build true enterprise master data in any environment – even those with a heavy ERP footprint who may have done some level of ‘mastering’ there already.

1. In the data warehouse – This is the place where most master data comes together today due to the proliferation of data warehouses and the intense focus during the build of those data warehouses to build a master, shared (conformed) view of each business dimension. Usually most of this master data actually is mastered in the operational environment, but doesn’t come together or get integrated until it reaches the data warehouse. If you were consciously trying to fix master data problems within your operational environment, you would prefer to pull it together in the operational environment and make the data warehouse another feed of the data.
2. In pieces throughout the operational environment – This is leaving the master data in place throughout the operational environment, identifying it as such and arranging for the access to that data from wherever it is needed. This virtualization strategy can create performance issues upon query and can also limit integration possibilities. And finally you are adding functionality to environments that they were not built for.

Continue reading "Where to put your enterprise master data" »

March 30, 2007

Master Data Management Strategy Quips

I was recently posed a good set of questions by Dan Lindstedt on MDM. I thought I’d share my quippy answers with you.

- Where do you ‘master’ the master data? Strategy: MDM hub feeding operational systems and the DW
- How do you model master data? Strategy: Like a dimensional model’s dimensions; hierarchical
- What master data do you distribute? Strategy: Break all master data into ‘subject areas’ and distribute full subject areas (changed data only)
- Does 3rd party data constitute master data? Strategy: Absolutely. If it’s not transactional and it helps to explain the subject, it’s master data.
- What style of MDM should we use? Strategy: It depends, but usually a hub has had the best value proposition so far.
- Use a tool or do homemade MDM? Strategy: It depends, but usually should be a more later-stage decision than it usually is

Technorati tags: Master Data Management, CDI

March 29, 2007

Who owns Master Data Management?

I spoke at the CDI Institute conference Monday and this question was on the minds of the attendees, many of whom were just starting off their MDM program.

Defining ownership as the entity that would actually come up with the rules for the sourcing, quality and presentment of the data, as opposed to the entity that would actually build the rules into the systems, my answer is Data Stewardship. Specifically, it's the business data stewards, who are representing the business rules to the IT/consulting build team for MDM. I have written extensively elsewhere about stewardship, but it is essential to MDM success. Hopefully those stewardship programs that were built for data warehousing can carry over to the MDM extensions many are now planning for their information management environment, as evidenced by the conversations I had on Monday.

Technorati tags: Master Data Management, CDI , Data Stewardship

March 14, 2007

CDI-MDM ROI & Justification

I'll be speaking at the CDI-MDM Summit March 26 in San Francisco on the topic of "CDI-MDM ROI & Justification."

The abstract...

Data integration is required to synchronize master data in order to get a single consistent view of an enterprise's core business entities like customers, products, suppliers, and employees. Yet many executives question economic payback. IT professionals must calculate and present the business value of MDM in terms business executives can understand. Unfortunately, most IT professionals lack the knowledge required to develop comprehensive cost-benefit analyses and return on investment (ROI) measurements. This session provides a framework for the research, measurement, and presentation of the economic value of a proposed or existing CDI-MDM initiative, including practical advice about how to calculate ROI, which formulas to use, and how to collect necessary information. Topics include:

* Determining indirect ROI
* Calculating the most common forms of ROI
* Justifying MDM programs versus justifying projects

Technorati tags: Master Data Management, CDI , ROI

June 7, 2006

Yes, we are doing Master Data Management

How do you know if you're doing master data management/MDM? Well, first of all, it's unlikely that you're NOT doing some forms of managing master data in your organization. Master data is compiled for a variety of purposes in an organization, usually with limited sharing across those purposes and applications. Somewhere on the path of beginning to share, an organization will take a specific focus on that process. That focus may cause focuses (foci?) on any of the following:

- The quality of the data
- Widespread buy-in to the data
- Organizational ownership of the data
- Creation of workflow processes to collect multi-group input to the build of that data
- Apportionment of all enterprise data into managable chunks ("subject areas")
- Inventory of the various places that data is stored
- Ranking of the value of the various places that data is stored
- Creation of a unique database to store that data

At some point on this journey, an organization will come to the realization that there is an industry for this - the MDM industry - and adapt that terminology. This usually coincides with some budgetary allotment for the activities - the MDM budget of course.

Of course, that's one way a company comes to this realization. The other way is being exposed to the MDM industry and looking for its value to the organization, doing some top-down planning and beginning to engage these activities. Either way, each company should understand why they are doing MDM and where the ROI will come from. Though many will eschew this part of the process, it's important.

The (relatively) easy way to show the value is by showing how centralizing function will save on the myriad of pockets of like activity throughout the organization. I've blogged about MDM justification before. This blog is meant to lead into that one by elaborating on the MDM journey that many are going through.

April 17, 2006

Why have a centralized MDM strategy?

If you try to comprehend everything there is to read and hear on MDM these days, you will find yourself going in circles. Therefore, I'll say that whatever you believe about what MDM is, justification is going to be necessary to establish it as a discrete project, over and above establishing the master data that you will do so out of necessity for various other projects. I view MDM as not really an option, we all need to manage our master data. However, making it a discrete project is currently under consideration for many.

So why have a centralized MDM strategy instead of just establishing individual data marts/databases for each need - as would be the case without any aspects of a top-down MDM strategy. There are 3 basic reasons. The first 2 have to do with efficiency/TCO and the last has to do with ROI.

1. Systems Impact:
Impact: The inability to do the next project that needs the operational system data or the removal of an extract stream currently in operation supporting a project. In other words, numerous overlapping extracts takes its toll on those systems you extract master data from. Perform that once and reuse many times.

2. MDM methodology and tools competence:
Impact: The carrying costs for additional headcount and tools to support multiple groups with MDM competencies. As previous said, however, it is going to be a challenge sorting through the approaches out there. Look for help to a non-software vendor who has an adaptable, experience-based approach.

3. Enterprise Subject Areas:
Impact: Having one set, as opposed to many sets, of master data for important, widespread subject areas of the business provides enormous efficiency advantages for all other system development. Furthermore, it enables ROI-producing programs that would otherwise be unobtainable - as in customer-specific, information-based cross-selling.

April 1, 2006

Justifying and Implementing Master Data Management

The latest buzzword in information management - and by extension, business intelligence (BI) - is master data management (MDM). You may hear this phrase and stated goal of creating a single version of the truth and wonder, "Haven't we been here before?" or, "We already do that in the data warehouse, right?" You may be correct on both counts. MDM has become hot due to the perfect storm of:

The continued struggle organizations face in managing their master data,
The need to master the data in the operational environment, and
Vendor momentum with service-oriented architecture (SOA)-based software designed to systemize the rough spots.

For the rest of this feature article I wrote for the latest DM Review, please see www.dmreview.com/article_sub.cfm?articleId=1051165. Feel free to comment on it here.

March 4, 2006

MDM is not just another data mart

Calling master data management just another data mart, as some has done, is flawed on many levels. Probably most importantly, it implies that mart is fed from the data warehouse. Since the data warehouse should contain master data, not mere duplicates of dirty operational data and data marts should be cut for discrete query and application purposes, what purpose would a master data data mart serve? Master data is more about distribution to those operational systems that need it, as opposed to master data query.

Fix master data in the operational environment and feed it to the data warehouse. That way, all systems have access to master data. The data warehouse is too far down in the data lifecycle, and historically has been a poor instrument as a data distribution source, to be effective. If data warehousing met MDM needs, there wouldn't be a clamor for a different way with more applicability to modern business.

Master data management in the operational environment can comprise a virtual management structure or a physical structure. And keep in mind MDM is more than data storage and distribution. It's a holistic approach that includes data quality, data stewardship, third party data, enterprise quality modeling, ROI AND data management and distribution. This is why you have so many vendors at the MDM party. Most contribute a piece, like maybe the appetizer or dessert, but few contribute full MDM. It's really a process more than a technology. Contact me to learn about the experience- and success-based approach to MDM I've developed with my clients for my firm.

Continue reading "MDM is not just another data mart" »

November 9, 2005

Upcoming webinar on Master Data Management

On November 17th at 2:00 ET, I will be giving a webinar on the B-EYE-Network with Mark Smith of Ventana Research titled "Justifying and Implementing Master Data Management for the Enterprise." You can sign up for it at this link.

Here is the abstract:
More complex and demanding business environments are forcing more heterogeneous systems environments. Data integration is required to synchronize master data to get a single, consistent view of an enterprise’s core business entities like customers, products, suppliers and employees. Effective master data for any subject area requires input from multiple applications and business units; and enterprise master data needs a formal management system. Business approval, business process change and capture of master data at optimal, early points in the data lifecycle are essential to achieving true enterprise master data.

Continue reading "Upcoming webinar on Master Data Management" »

August 27, 2005

BI Trends: Master Data Management

At Scott Humphrey’s Fourth Annual Pacific Northwest Business Intelligence Summit the last weekend of July, I shared a panel with Claudia Imhoff, Jill Dyche and Colin White (covered here by Claudia as well.) Between the panel and the esteemed attendees from the who’s who and the up-and-coming in business intelligence, we covered the bases of business intelligence today and looked ahead to the future. I view it as the best barometer for the BI market.

Continue reading "BI Trends: Master Data Management" »

BI Trends: Master Data Management

At Scott Humphrey’s Fourth Annual Pacific Northwest Business Intelligence Summit the last weekend of July, I shared a panel with Claudia Imhoff, Jill Dyche and Colin White (covered here by Claudia as well.) Between the panel and the esteemed attendees from the who’s who and the up-and-coming in business intelligence, we covered the bases of business intelligence today and looked ahead to the future. I view it as the best barometer for the BI market.

Continue reading "BI Trends: Master Data Management" »