Portals eNewsletters Web Seminars dataWarehouse.com DM Review Magazine
DM Review | Covering Business Intelligence, Integration & Analytics
   Covering Business Intelligence, Integration & Analytics Advanced Search
advertisement

RESOURCE PORTALS
View all Portals

WEB SEMINARS
Scheduled Events

RESEARCH VAULT
White Paper Library
Research Papers

CAREERZONE
View Job Listings
Post a job

Advertisement

INFORMATION CENTER
DM Review Home
Newsletters
Current Magazine Issue
Magazine Archives
Online Columnists
Ask the Experts
Industry News
Search DM Review

GENERAL RESOURCES
Bookstore
Buyer's Guide
Glossary
Industry Events Calendar
Monthly Product Guides
Software Demo Lab
Vendor Listings

DM REVIEW
About Us
Press Releases
Awards
Advertising/Media Kit
Reprints
Magazine Subscriptions
Editorial Calendar
Contact Us
Customer Service

Meta Data & Knowledge Management:
Data Stewardship Framework, Part 3

  Column published in DM Review Magazine
February 2003 Issue
 
  By David Marco

In this month's installment of my data stewardship series, we will examine the most common data stewardship activities.

The specific activities of the data stewardship committee will vary from one organization to another and from industry to industry. No two data stewardship committees are exactly the same; however, the following are the most common data stewardship activities: data domain values; data quality rules, validation and resolution; business rules/security requirements; business meta data definitions; and technical data definitions.

The data stewards that work on these different activities will be primarily working with meta data; however, there will be occasions when they may need to work with actual data. In the following section, I will walk through these common data stewardship activities and provide a set of guidelines and best practices around them. Also, I will discuss the typical data stewards that accomplish these tasks. It is important to note that sometimes there are people that are highly knowledgeable on the data and the business policies around the data, even though they do not belong to the particular stewardship group that I mention for the activity. For example, in your company there may be technical stewards that are as knowledgeable on the business policies and data values as any of the "official" business stewards. Thus, even though I state in my guidelines that the business stewards should be creating the business meta data definitions, you would obviously want these technical stewards working with the business stewards to create the business meta data definitions.

Additionally, for all of the activities discussed, the chief steward will play a critical role in ensuring that these activities are properly completed. A good chief steward will make sure that the technical and business stewards work thoroughly and expediently. The chief steward understands how easy it is for these groups to fall into "analysis paralysis" and will act as a project manager/guide. Most importantly, the chief steward will aid these people in any needed (and you will need it) conflict resolution for the different data stewardship tasks.

Once the business stewards have defined their key data attributes, they need to define the domain values for those attributes. For example, if one of the attributes is state code, the valid domain values would be the two-character abbreviations of the states (e.g., CA, FL, IL, NY, etc.).

As with all of the data stewardship tasks, this meta data will be stored in the meta data repository. It is highly recommended that a Web-based front end be developed so that the business stewards can easily key in this vital meta data.

In many cases, data modelers have inputted attribute domain values into their modeling tool (e.g., Erwin, Silverrun, System Architect). If this process has occurred in your company, you can create a process to export that meta data from the modeling tool into the meta data repository. This will provide the business steward a good starting point in the process to enter domain values.

Data quality is the joint responsibility of the business and technical stewards. The business steward defines data quality thresholds and data error criteria. For example, the data quality threshold for customer records that error during a data warehouse load process may be two percent. Therefore, if the percentage of customer records in error is greater than two percent, the data warehouse load run is automatically stopped. An additional rule can be included that states if the number of records in error is one percent or greater but less than two percent, a warning message is triggered to the data warehouse staff; however, the data warehouse run is allowed to proceed.

It is the responsibility of the technical steward to ensure correct implementation of the data quality rules. In addition, the technical steward will work with the business steward on the specific data quality threshold and data error criteria.

Business rules are some of the most critical meta data within an organization. Business rules describe how the business operates with its data. A business rule will describe how the data values have been derived, calculated, if the field relates (cardinality) to other fields, data usage rules/regulations and any security requirements/limitations around a particular entity or attribute within a company's systems. For example, a healthcare insurance company may have a field called "POLICY_TREATMENTS." This field may list the specific medical treatments that a policyholder may have undergone. The business rule for this field could be that it is an alphanumeric, 20-byte field, with a "system of record" from "System A." In addition, there may be security requirements on this field. Most health insurance companies provide coverage to their own employees. Therefore, the security requirements for this field may be that the IT department is not allowed to view this field or associate it with any fields that would identify the policyholder. When security rules such as these are broken, the corporation experiences a great deal of legal exposure.

...............................................................................

For more information on related topics visit the following related portals...
Content Management.

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.

Solutions Marketplace
Provided by IndustryBrains

Manage Data Center from Virtually Anywhere!
Learn how SecureLinx remote IT management products can quickly and easily give you the ability to securely manage data center equipment (servers, switches, routers, telecom equipment) from anywhere, at any time... even if the network is down.

OMG Presents: BPM Think Tank 2006
BPM Think Tank puts you together with leading BPM experts for highly interactive roundtables. It features case studies, the state-of-the-art from business and technology viewpoints, and directions for future innovation. Arlington, VA, May 23-25, 2006

Increase Your Existing Data Center Capabilities
Robert Frances Group believes that the enterprise data center is undergoing significant and sustained transformation?and that Azul Systems has delivered on a new approach to delivering processing and memory resources to enterprise applications...

Design Databases with ER/Studio: Free Trial
ER/Studio delivers next-generation data modeling. Multiple, distinct physical models based on a single logical model give you the tools you need to manage complex database environments and critical metadata in an intuitive user interface.

Free EII Buyer's Guide
Understand EII - Trends. Tech. Apps. Calculate ROI. Download Now.

Click here to advertise in this space


View Full Issue View Full Magazine Issue
E-mail This Column E-Mail This Column
Printer Friendly Version Printer-Friendly Version
Related Content Related Content
Request Reprints Request Reprints
Advertisement
advertisement
Site Map Terms of Use Privacy Policy
SourceMedia (c) 2006 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.