Portals eNewsletters Web Seminars dataWarehouse.com DM Review Magazine
DM Review | Information Is Your Business
   Information Is Your Business Advanced Search

Business Intelligence
Corporate Performance Management
Data Integration
Data Quality
Data Warehousing Basics
Master Data Management
View all Portals

Scheduled Events

White Paper Library
Research Papers



DM Review Home
Current Magazine Issue
Magazine Archives
DM Review Extended Edition
Online Columnists
Ask the Experts
Industry News
Search DM Review

Tech Evaluation Center:
Evaluate IT solutions
Buyer's Guide
Industry Events Calendar
Software Demo Lab
Vendor Listings

About Us
Press Releases
Advertising/Media Kit
Magazine Subscriptions
Editorial Calendar
Contact Us
Customer Service

Metadata Management & Enterprise Architecture:
Managing Metadata for the Business, Part 4: Enable Knowledge Management

  Column published in DMReview.com
May 1, 2006
  By David Marco

One of the most vital functions of any managed metadata environment (MME) is to provide the technical architecture and processes to manage corporate knowledge. All corporations strive to become more intelligent. To attain a competitive advantage, a business needs its IT systems to manage more than just its data; they must manage knowledge (that is, metadata). As a corporation's IT systems mature, they progress from collecting and managing data to collecting and managing knowledge. Knowledge is a company's most valuable asset, and an MME is the key technological backbone for managing a company's corporate knowledge.1

George Bernard Shaw once said, "The greatest problem in communication is the illusion that it has been accomplished." Executives often do not realize how neglecting to properly manage the company's knowledge (metadata) can negatively affect their bottom-line profits, or they are under the illusion that proper communication and understanding are occurring. This couldn't be further from the truth.

Adhere to Regulatory Requirements

Every industry has its own dizzying array of regulatory requirements. Corporations must be able to meet these requirements, because the penalties can be severe. They range from large monetary fees to felony charges levied against senior executives within the organization. Many companies look to an MME architecture to assist them in meeting these requirements. Because most information in a company is stored electronically, an MME can greatly assist an organization in tracking, monitoring and recording changes to its data and documents.

Enable Enterprise Applications

Without an enterprise-wide MME, your organization does not have a common understanding of the data across its systems. How do you build an enterprise-wide application - that is, a customer relationship management (CRM), data warehousing or enterprise resource planning (ERP) system - without an enterprise-view understanding of the data? The answer for most companies is that they can't. This is why many research firms state that CRM initiatives fail more than 90 percent of the time. In fact, Tom Siebel proclaimed, "There's no market for CRM ... It's not there. There are a lot of companies trying to get into the space ... But they are going after a market that doesn't exist."2

Realistically, this is not the case because there is a clear business need to understand and manage all of a customer's touchpoints. Why does the man who marketed CRM the most and made the most money from it claim that it is dead? Maybe it is because these CRM initiatives are highly complex and as a result have created a large number of expensive failures. These failures, along with a compressed IT economy, may have caused companies to abandon CRM. Personally, I don't expect Siebel Systems to stop making CRM software. On the other hand, I interpret Tom Siebel's comments to mean that we have to get ready for a new term for the same old thing.

In my January 2000 column for DM Review, I gave predictions for the future of the data warehousing industry. In writing this column, I realized that the most important thing I could do was make sure that my predictions were accurate. Therefore, the first prediction was that most large government agencies and Global 2000 companies would spend a great deal of time and money rebuilding their data warehousing investments. This was a simple prediction to make. During the 1990s, corporations raced to build their data warehouses as quickly as they could. In their zeal to do this, many organizations neglected to build the architecture necessary to grow their systems over time. In many cases, these companies built independent data marts, which are directly sourced from operational systems without a data warehouse. These companies also neglected to implement an MME. Without an MME, it is exceedingly difficult, if not impossible, to maintain and enhance a data warehouse.

This is especially true if a company has implemented multiple, disparate data warehousing systems. Having multiple data warehouses can lead to the following problems:

  • Duplicate data,
  • Duplicate reports and queries,
  • Increased strain on operational batch windows and
  • Multiple versions of the truth.

An MME addresses the excessive IT redundancies in this type of environment and acts as the glue that binds the data warehouses together. This makes MMEs even more vital in a cluttered environment.

Global 2000 companies spend billions of dollars analyzing existing data warehousing systems for requirements and business rules, which have long been forgotten and should have been initially managed in the MME. These same companies will continue to invest equally large expenditures into CRM and other enterprise-spanning applications. If you do not properly manage your metadata, you will have a very difficult time implementing enterprise-wide systems.

MMEs may not be as glamorous as CRM applications, but these projects deliver real value as opposed to the 90 percent-plus failure rate. Running a successful business is about concentrating single-mindedly on the fundamentals and executing those fundamentals.


  1. For more information on knowledge management, refer to Chapter 11 of my book Building and Managing the Meta Data Repository. John Wiley & Sons, 2000.
  2. "Tom Siebel's Vision for the Software Industry - Part 1." The Siebel Observer, 2003.

For more information on related topics visit the following related portals...
Enterprise Achitecture and Metadata.

David Marco is an internationally recognized expert in the fields of enterprise architecture, data warehousing and business intelligence and is the world's foremost authority on meta data. He is the author of Universal Meta Data Models (Wiley, 2004) and Building and Managing the Meta Data Repository: A Full Life-Cycle Guide (Wiley, 2000). Marco has taught at the University of Chicago and DePaul University, and in 2004 he was selected to the prestigious Crain's Chicago Business "Top 40 Under 40."  He is the founder and president of Enterprise Warehousing Solutions, Inc., a GSA schedule and Chicago-headquartered strategic partner and systems integrator dedicated to providing companies and large government agencies with best-in-class business intelligence solutions using data warehousing and meta data repository technologies. He may be reached at (866) EWS-1100 or via e-mail at DMarco@EWSolutions.com.

E-mail This Column E-Mail This Column
Printer Friendly Version Printer-Friendly Version
Related Content Related Content
Request Reprints Request Reprints
Site Map Terms of Use Privacy Policy
SourceMedia (c) 2007 DM Review and SourceMedia, Inc. All rights reserved.
SourceMedia is an Investcorp company.
Use, duplication, or sale of this service, or data contained herein, is strictly prohibited.