When it comes to aggregating data from dozens of systems to create master data files, nothing is more important than ensuring everyone in the your organization has what I would call a "master definition file."
There is no shortcut to master data management without it.
To be clear, I'm not talking about the kind of file cleanup you do when creating a data warehouse. Those kinds of definition files already exist, and they are more about making sure customer names are the same across the multiple systems that dump data into the warehouse. What I'm talking about is creating a common business glossary and common definitions across business and IT.
[ How important is data cleansing and validation? Read these tales of horror, and beware the perils of dirty data ]
This essential of master data management comes to mind because IBM, one of the premier middleware software companies, pitched me recently on what it calls "information middleware."
I spoke with Tom Inman, vice president of information-on-demand acceleration, and Michael Curry, director of product management and strategy for IBM InfoSphere, about IBM's approach to managing information.
As IBM defines it, "information middleware" is geared toward creating, managing, and delivering trusted information throughout the enterprise. It goes beyond establishing a business glossary, IBM says. But before any organization can even approach master data management, business users must have a set of agreed-on definitions for terms used throughout the organization.
The importance of agreement on terms
Suppose you work for a banking institution. Your organization will define risk according to a certain set of criteria. But what if your company merges with a life insurance company where age is a key metric to measure risk? The newly formed organization needs to agree on a new definition for risk.
Or consider planning and forecasting, for example. What is a lead? Who is a high-value customer? Definitions often vary from department to department.
Say, the manager of a retail clothing store decides that a customer who buys $10,000 worth of clothes a year is a high-value customer. But what if the returns department knows that this particular customer returns $7,000 worth of clothes per year and considers that same customer a fraud risk?
Having accurate information is critical.
What does "discharge date" for a patient mean? Is it when they walk out the door, or when the doctor signs off?