Data Warehousing TCO & ROI Reports

I've been getting some calls for studies outlining the costs, ROI and/or the TCO for large data warehouses. Below is a list of reports that I have found:

- Start with Harrah's use of BI, They are one of the leaders in BI.

ROI Case Study: Teradata Harrrah's Entertainment

- Next check out Sun's comparison, it has some good data, by Ventana

Data Warehousing Total Cost of Ownership Research on Sun Microsystems and NCR Teradata

- And then check out some of these:
- ROI Case Study: Enterprise Data Warehouse Intermountain Healthcare
- Realizing Data Warehouse ROI
- Data Warehouse Justification and ROI
- TCO Starts With the End User
- Realizing Data Warehouse ROI
- Have you Created a Monster?

Data Modeling and Business Insight

Success of a project, both short-term and long-term, ultimately comes down to business insight, strategy, sound linkage between the business goals and the technical objectives, and the tactical execution of the project. Given my deep understanding of information and database technology, I’m naturally biased towards business analysis, and data modeling as the foundation for a successful project. But don’t take my word for it. Larissa Moss of Method Focus and Steve Hoberman have written an excellent summary of the importance of data modeling as a foundation for business insight.
   Alternate URL:  The Importance of Data Modeling as a Foundation for Business Insight .

(Teradata non-working link:The Importance of Data Modeling as a Foundation for Business Insight.)

Another good read is Data Modeling in System Analsys by Shuang Gao.  Alternate download: Data Modeling in System Analysis. If you are finding you need some additional points to justify upfront analysis for your agile or spiral approach, this might be a good starting point.

Excellent execution can save a bad idea

In the corporate world today, and perhaps others, the idea, the concept, is idolized, while sadly, the ability to execute is more likely than not taken for granted. And this will ultimately lead to an organization’s demise. Google was not the first to do Internet searches – their design and execution in improving the results lead to their success. YouTube was not the first to do online video. But they were the best at making it easy – and thus the design and execution, and not just the idea lead to success. Microsoft is often criticized for rarely having any new ideas. Perhaps justified, but what they do is execute better than others. Again, their success is due to the dirty work of execution, not the idea.

During the first Internet wave, those companies with sound execution (the dirty work) appear to have succeeded more often, while those with just an idea, and poor execution seem to have failed. The trend is clear - Excellent execution can save a bad idea, but all ideas are doomed with poor execution. The question is, do you get it? Does your competitor?

A Great, Free Prototype and Documentation Tool

Amazingly, this free tool is still available for download (as of May 4, 2016) . I first discovered it back in 2008. I'm not sure it has been updated recently, but it's still an excellent tool for layout workflows, and other aspects of systems design. If you are still looking for a design tool, this is a good place to start.

It's a free, community edition tool to build software prototypes, design workflows and document requirements. It’s called Prototype Composer. And as of this writing, Serena is giving the tool away for free. ( after requesting, they send you an email to download the tool)

While it does have a few shortcomings, overall it is easy to learn, easy to work with, and does a very nice job of combining GUI wire-frames with a business workflow. In the end, you get a working “demonstration-only” prototype, and numerous word documents (template driven) that document the project, the GUI requirements, and the workflow process, among others.
The one major complaint I have is that the prototype can only be run from within the Prototype Composer. There is no ability to export the project as a sample web site. Hopefully, this will be part of their product enhancement in the future.

Vendors and the Black Box Vision

I am endlessly amazed that organizations continue to focus on technology tools as magic black boxes. True, some of the tools are magical, but only if they are understood, and focused on solving the business problem. Vendor demo’s show amazing results, but hide the hard work to get the tools up and running, along with the even more important work of assessing the businesses needs, organizing the information, and targeting problems, issues and results.

To some extent, the vendors drive the problem. Their goal is to sell the tools, and they do a good job of selling -- perhaps too good a job. No matter how excellent the tool, organizations still need a plan, architectural drawings and construction blue prints, before they start building. The tech vendors may have the best, most cutting edge Bobcat or backhoe, but you still do not ask the crane operator to design and construct the building. Except in technology. And we wonder why so many projects fail?