Published in DM Review in November 2000.|
Printed from DMReview.com
Meta Data and Data Administration: Meta Data ROI: Specific Guidelines for Your Companyby David Marco
This column represents the third and concluding portion of my three- part series on defining the return on investment (ROI) that a meta data repository can provide to your company. The formulas that I will present in this article are meant to be used as guidelines; the results that you experience on your project will differ. Now that I'm finished with the legal disclaimer, on to the calculations.
In building these formulas, I have attempted to err on the side of being overly conservative. There are several companies that are achieving more favorable ROI percentages than the ones that I will present. On the other hand, those companies that do not properly define their meta data objectives and do not correctly build their repositories attain much worse results. Before you start counting your profits, there are two paradigm shifts that must occur. First, the key to attaining a positive ROI is that the people must act on the information that meta data provides. This is especially critical for the business users that access the business meta data. Second, as with the business users, the IT (information technology) staff must be willing to change the way that they build their systems in order for technical meta data to achieve a positive ROI.
We will walk through six business and technical meta data ROI formulas. Examples of how meta data is used to accomplish these formulas were discussed in my September and October DM Review columns.1 To use these formulas, you will need to know your company's corporate revenue, cost of data warehousing, total IT budget and the projected cost of your meta data repository project. For the examples discussed in this article, I will use the values shown in Figure 1.
Business Meta Data ROI Formulas
There will be three business meta data ROI formulas that we will examine. Each of these business meta data ROI methods is summarized in Figure 2.
The first is "Business Meta Data for the Data Warehouse" listed in the Sep-tember column as "Meta Data Driven Business User Interface." This technique integrates business entity/ attribute definitions into data warehouse/data mart reports, and business meta data report names and definitions. This improves the accuracy of our business users' decision making, reduces training costs for new employees and increases end-user confidence in the IT systems.
Second is "Data Quality Tracking and Reporting," which incorporates data quality statistics directly into data warehousing/data mart reports. These data quality statistics improve decision making in our business intelligence system and increase end-user confidence in our IT systems.
The third is "Business Meta Data for Operational Systems." Like "Business Meta Data for the Data Warehouse," this technique improves decision making in our operational systems, prevents IT systems mistakes, improves data quality at its source and reduces training on IT systems.
Technical Meta Data ROI Formulas
There are three technical meta data ROI formulas that we will examine: data warehouse impact analysis, operational impact analysis and the removal of redundant data/processes. Each of these technical meta data ROI methods was presented in detail in the October 2000 DM Review column and are summarized in Figure 3.
Data warehouse impact analysis reduces the impact of system changes to the data warehouse environment and limits unproductive developer work. It also reduces development errors, lowers the impact of IT staff turnover and speeds up the time to market for new data warehouse enhancements.
Operational impact analysis reduces the IT impact of new systems development and changes to existing IT systems. Operational impact analysis limits unproductive work, reduces errors, lowers the impact of staff turnover and speeds up the time to market for new IT systems.
Once a meta data repository is properly built, it enables a corporation to easily identify redundant data and system processes. This is a critical issue that gets much less exposure than is properly warranted. It is important to understand that some data redundancy is appropriate; however, it has been my experience that most companies needlessly store each data field redundantly four times. Companies that are proactive in using their technical meta data to remove this redundancy can save well more than my estimate of 15 percent of their IT budget.
Please feel free to send me your comments on this article at my e-mail address below. If you want to interactively walk through a meta data ROI worksheet, go to www.EWSolutions.com/book.asp. Just remember that anything worthwhile will not be easy, and that is certainly the case in building a meta data repository. Work hard, be disciplined in your development efforts and you can achieve great results.
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.
Copyright 2005, SourceMedia and DM Review.