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: Claudia Imhoff Subscribe to this blog's RSS feed!

Claudia Imhoff

Welcome to my blog.

This is another means for me to communicate, educate and participate within the Business Intelligence industry. It is a perfect forum for airing opinions, thoughts, vendor and client updates, problems and questions. To maximize the blog's value, it must be a participative venue. This means I will look forward to hearing from you often, since your input is vital to the blog's success. All I ask is that you treat me, the blog, and everyone who uses it with respect.

So...check it out every week to see what is new and exciting in our ever changing BI world.

About the author >

A thought leader, visionary, and practitioner, Claudia Imhoff, Ph.D., is an internationally recognized expert on analytics, business intelligence, and the architectures to support these initiatives. Dr. Imhoff has co-authored five books on these subjects and writes articles (totaling more than 150) for technical and business magazines.

She is also the Founder of the Boulder BI Brain Trust, a consortium of independent analysts and consultants (www.BBBT.us). You can follow them on Twitter at #BBBT

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

I attended a most interesting “night school” at the Data Warehousing Institute’s conference this week in San Diego. It was taught by Sid Adelman and dealt with the new accounting requirements that companies assign a “fair value” to their data warehouses and BI environments. Read on about this controversial and confusing new accounting practice.

Did you know that you and your accountants must put a fair value upon your data warehousing environment that includes not only the software and hardware but the intangible value it brings to your company (better decisions, timely reporting, quality data, etc.)? Yes, it is true. The new FASB (Financial Accounting Standards Board) rules requiring that data warehouses show up on your balance sheet as an asset will kick in fully in 2006. At that time, it becomes “the law” to record the full value of this critical company asset just as you just record the value of your inventory, capital assets such as buildings, financial assets, and so on.

Yikes! Where do you begin to estimate (yes – it is a statistical estimate at best) the asset value of BI? The key is to determine the future value of the data warehouse and be able to express that in today’s dollars. According to FASB, “Assets are probable future economic benefits obtained or controlled by a particular entity as a result of past transactions or events” (FASB Concept Statement No. 6).

Let’s start with the easy stuff – you know with relative accuracy the cost of the hardware and software, consulting and contracting resources costs, and employee costs (the number of hours they worked on creating the BI components times their loaded hourly rate). These are “hard” dollars that you spent on the construction of the data warehouse and its associated marts or applications.

But what about the other benefits of the warehouse that are not so easily valued? These include such things as the benefits garnered from its usage like lowered costs or expenses, better marketing of your customers, more productivity from analysts, reduced fraud, better quality data for decision making, etc. How do you put a fair value estimate on these?

Other considerations are the data quality improvements, meta data, data models, enhancements to the warehouse, value of integrated data, the performance and availability capabilities. Each of these increases the fair value of this asset. Note though that poor data quality is just as important in decreasing the value of the warehouse!

Note – some things cannot be capitalized and must be expensed. These include maintenance costs, training, ongoing administration and support, the cost of the help desk and – significantly – a failed data warehouse project!

And, as if that were not a big enough headache, you or your accountants must determine the useful life of the warehouse. This is the time frame that will be used to amortization this asset. Do you amortize it over three years? Five years? Perhaps ten?

For more information on this subject, read Sid Adelman’s complete article entitled "Capitalizing the Data Warehouse".

Posted August 17, 2005 12:03 PM
Permalink | 1 Comment |

1 Comment


I am picking this up a little late, I see that you posted this back in August. Where would we be without Google!

This is a fascinating concept, not just for accounting reasons you point out but also for my current project. The definition of the value of a data warehouse. You mention the following value statements:

Lowered costs or expenses
Better marketing of your customers
More productivity from analysts
Reduced fraud
Better quality data for decision making
Data quality improvements
Meta data
Data models
Enhancements to the warehouse
Value of integrated data
The performance and availability capabilities.

Do you have any metrics to support these statements? E.G. Why does a data warehouse reduce costs or expenses?

Can you point me anywhere?

Best regards

Ben Lockett

Leave a comment


Search this blog
Categories ›
Archives ›
Recent Entries ›