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 and Data Administration:
Evaluating Meta Data Tools

  Column published in DM Review Magazine
December 2000 Issue
 
  By David Marco and Michael G. Needham

A special thanks to Mike Needham for his invaluable contribution to this month's column.

Today with so much emphasis being placed on empowering the business users to do more with less information technology (IT) help and enabling the IT organization to produce better results faster, it is no surprise that meta data has become one of the hottest issues of the day. In order to leverage all of the meta data from the disparate sources that exist in your organization, you need a way to gather it into a central location (repository). This is where meta data integration tools come into the picture. Utilizing these tools, you can integrate your enterprise meta data into the repository and make it available to all the different user groups in your company. But, how do you determine which tool is right for your organization? There is a wide variety of tools on the market that claim to solve all of your meta data problems; but, as we all know, the vendor hype may not be a reality. This column will help you to objectively evaluate meta data tools.

Meta Data Sources

Within any organization there are going to be different sources of meta data. Meta data integration tools can integrate meta data from three broad source categories, each of which requires varying levels of integration complexity. It is important to identify all sources of meta data that you need to integrate into the repository. Figure 1 lists various meta data integration tool vendors.

Vendor Meta Data Integration Tools
Computer Associates PLATINUM Repositiory Open Enterprise Edition (UNIX)
PLATINUM Repository MVS
Informix Business Solutions Meta Stage
Unisys Universal Repository
Allen Systems Group ASG Rochade
Oracle Oracle Repository
Figure 1: Meta Data Integration Tool Vendors

The three classifications of meta data sources are certified, generic and non-supported sources.1 A certified source is a source that the meta data integration tool can directly read, properly interpret and load into the correct attributes of the meta model without changing the model. An example of a certified source is a CASE (computer-aided software engineering) tool such as ERwin. Most meta data integration tools are certified for several vendor tools. A generic source is a source in a common format (i.e., tab delimited, space delimited or comma delimited) that the tool can read, cannot interpret and may require a meta model change. Most tools support one or more generic meta data sources. An example of a generic meta data source is data that is stored in databases and spreadsheets. The last source of meta data is the non-supported source which is neither certified nor generic and may require extensive analysis to produce an in-house solution to access. The non- supported meta data source cannot be read or interpreted by the meta data integration tool.

Once you have classified the meta data sources available, you will be able to quickly determine the complexity of your project and if the tools you're evaluating support all of your sources. Figure 2 lists some of the more common meta data sources and how they are typically classified. (Your specific implementation may differ.)

Meta Data Sources Meta Data Description Type Model Extension
CASE Tool Physical and logical models, domain values, technical entity definitions and technical attribute definitions Certified No
Extraction/Transformation Tool Technical transformation rules Certified No
Custom Data Dictionary Business attribute and entity definitions Non-Supported No
Microsoft Excel Data steward's list Generic Yes
Reporting Tool Access patterns and frequency of use Generic Yes
Figure 2: Example Meta Data Sources

Vendor Tool Interview Process

After determining your requirements, you are ready to begin the tool vendor interview process. By conducting some research using product information that is readily available on the Internet and in industry magazines and journals, you can narrow the field of potential vendors and products to those vendors that have tools that meet your general criteria. Once you've prepared a preliminary list of vendors, you're ready to start interviewing and evaluating. Try to have the vendor come on site and use your existing meta data sources rather than evaluating on the basis of the vendor's demos.

To objectively look at all of the criteria, you should use a weighted vendor checklist to perform a tool analysis. The vendor checklist allows you to come up with a numerical score based on the criteria you specify. Figure 3 is a small excerpt of a completed checklist outlining the kinds of questions that need to be answered when evaluating meta data tools. By using an in-depth checklist, you be able to get an unbiased view of how the tool fits your company's needs as well as the tool's strengths and weaknesses.

Section/Description Weight % Met Score Comments
Technical Requirements
What programming requirements are required to support the proposed meta data repository solution (e.g., script, SQL, etc.)? 9 .75 8.4 Learning curve required.
How does the product allow multiple meta data developers to work simultaneously with the same DSS project? 6 1 6 What memory and processing requirements are needed for each user? How does the vendor suggest calculating these needs?
Meta Data Management
Is the meta data repository tool active or passive in controlling the processes of the DSS environment? If active, explain. 7 .3 21 What agents and/or triggers can be used to make the repository proactive?
Figure 3: Excerpt from Weighted Vendor Checklist

Once the checklist is complete, you can look at the scores to see just how well or how poorly a product performed. The higher the score, the better that tools fits your needs. Always remember that every company has its own unique meta data requirements and that nothing is perfect. Be prepared to compromise along the way; but if you keep your requirements and priorities clearly in mind – and manage to ignore the bells and whistles that vendors will wave in front of you – you can't go wrong.

References
1. Marco, David. "Meta Data Integration: Fitting Square Pegs in Round Holes." DM Review. September 1998. P. 26.

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

For more information on related topics visit the following related portals...
Meta Data.

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.

Michael G. Needham is a data warehouse architect and contributing author to Building and Managing the Meta Data Repository. In his current role as data architect at Enterprise Warehousing Solutions, he is responsible for the design and implementation of decision support system architectures for the data warehousing and business intelligence areas. Needham has more than 10 years of experience in the IT industry. He can be reached at MNeedham@EWSolutions.com.

Solutions Marketplace
Provided by IndustryBrains

Verify Data at the Point of Collection: Free Trial
Protect against fraud, waste and excess marketing costs by cleaning your customer database of inaccurate, incomplete or undeliverable addresses. Add on phone check, name parsing and geo-coding as needed. FREE trial of Data Quality dev tools here.

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.

Data Mining: Levels I, II & III
Learn how experts build and deploy predictive models by attending The Modeling Agency's vendor-neutral courses. Leverage valuable information hidden within your data through predictive analytics. Click through to view upcoming events.

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.