We use cookies and other similar technologies (Cookies) to enhance your experience and to provide you with relevant content and ads. By using our website, you are agreeing to the use of Cookies. You can change your settings at any time. Cookie Policy.

Blog: William McKnight Subscribe to this blog's RSS feed!

William McKnight

Hello and welcome to my blog!

I will periodically be sharing my thoughts and observations on information management here in the blog. I am passionate about the effective creation, management and distribution of information for the benefit of company goals, and I'm thrilled to be a part of my clients' growth plans and connect what the industry provides to those goals. I have played many roles, but the perspective I come from is benefit to the end client. I hope the entries can be of some modest benefit to that goal. Please share your thoughts and input to the topics.

About the author >

William is the president of McKnight Consulting Group, a firm focused on delivering business value and solving business challenges utilizing proven, streamlined approaches in data warehousing, master data management and business intelligence, all with a focus on data quality and scalable architectures. William functions as strategist, information architect and program manager for complex, high-volume, full life-cycle implementations worldwide. William is a Southwest Entrepreneur of the Year finalist, a frequent best-practices judge, has authored hundreds of articles and white papers, and given hundreds of international keynotes and public seminars. His team's implementations from both IT and consultant positions have won Best Practices awards. He is a former IT Vice President of a Fortune company, a former software engineer, and holds an MBA. William is author of the book 90 Days to Success in Consulting. Contact William at wmcknight@mcknightcg.com.

Editor's Note: More articles and resources are available in William's BeyeNETWORK Expert Channel. Be sure to visit today!

March 2007 Archives

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

Posted March 30, 2007 8:42 AM
Permalink | No Comments |

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

Posted March 29, 2007 1:24 PM
Permalink | No Comments |

I'll be giving a webinar on the Subject topic this Friday at 11:30 Eastern.

You can register here.

The abstract is:

Making effective use of information is a central focus of organizations both large and small in our contemporary competitive landscape. Information is an asset to exploit without restrictions on bringing in new data, manipulating that data, or accessing that data.

In this Web seminar, we will discuss the following:

* Multiple, complex applications serving a variety of users
* Data warehousing is evolving, with new demands and needs placed on robust data warehouses
* Exploding data size that will continue to explode with data types running the gamut beyond traditional alphanumeric types
* Master data requirements in the operational environment as well as the data warehouse
* The role of operational Business Intelligence within the information management architecture

It’s the most time-consuming, yet critically important, component of most corporate projects. For the past few decades data warehousing, and the struggles to centralize data, have been the center of the universe for information management professionals. Recent advances in information management technology such as Master Data Management, EII and operational Business Intelligence have allowed for a more nuanced, yet effective, strategy for information management to complement data warehousing. In this webcast, William McKnight, renowned information management architect, will outline the modern components of information management and help participants understand how to these innovations can be put to work in today’s ever more complex IT environment.

Posted March 20, 2007 10:37 AM
Permalink | No Comments |

I'm getting concerned about the data warehouse. It has served us well, but can the current profile of data warehouses out there handle the next 10 years or will widespread changes be necessary? Consider that most data warehouses out there are not best practices by definition and are therefore dumps of operational data where history collects and reports are run from. This only solves some of the challenges associated with going it alone with just operational data, which are:

Data access
Reporting capabilities
Concurrency between query and operational needs
Structure for data access
Data quality for data access
Data integration
Storage of history data

Notably, it is the concurrency and history issues that instigate many data warehouse programs. However, integration is largely limited to data sharing a common database instance - which is good, but leaves too much complexity to the data access layer, where the end users find the data access tools too complex already. Building summaries and making sense of the data warehouse structure and data, especially without metadata, which most DW lack adequate levels of, is exasperating so current users mostly skim the surface of their true needs.

Also, data quality is only addressed in data warehouse programs out there selectively. Many remain afraid to change operational data, even if it is wrong. It needs to be fixed operationally anyway, and that just isn't happening enough.

So, how is data warehousing supposed to fit into this new world of data explosion, real-time requirements and a need for process-orientation?

1. We can't continue to delay the calculation, assimilation and distribution of master data until the data warehouse
2. Business intelligence, as a discipline, must be extended beyond reporting and even dashboarding and get involved in business processes using enterprise information integration and operational business intelligence approaches; these open up the possibilities beyond post-operational, after-the-fact BI
3. We need to embed business intelligence in operational processes and try a lot harder to fix data quality in the operational environment; the longer action is delayed, the less valuable it is; this can be the equivalent value of thousands of end-user data access licenses

This world requires integration between business units. It requires the understanding that information is a most-important business asset.

Of course, we could improve our data warehouses too with data quality, metadata, deriving data and true integration. In reality, for most, this is needed as well as a change in direction that focuses on the augmentation of the data warehouse with these new concepts. Most data warehouse programs will see these changes come one way or another in the next few years.

Technorati tags: data warehouse, information management, enterprise informatoin integration

Posted March 16, 2007 1:00 PM
Permalink | 2 Comments |

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

Posted March 14, 2007 10:16 AM
Permalink | No Comments |
PREV 1 2


Search this blog
Categories ›
Archives ›
Recent Entries ›