Commentary

Richard Martin
 

Are CIOs Ready For 'Active Data Warehousing'?

Speaking to a packed room of CIOs at the InformationWeek 500 conference in Tucson, Ariz., this morning, Stephen Brobst, the CTO for Teradata, made a compelling case that the future of data warehousing lies in "activating" the data in storage to enable automated, near-real-time decision-making to increase business' revenue.

Speaking to a packed room of CIOs at the InformationWeek 500 conference in Tucson, Ariz., this morning, Stephen Brobst, the CTO for Teradata, made a compelling case that the future of data warehousing lies in "activating" the data in storage to enable automated, near-real-time decision-making to increase business' revenue.Making the point that new data loads are outpacing the ability of Moore's Law to keep up, Brobst outlined five stages of "maturity" for organizations grappling with this flood: reporting, analyzing, predicting, "operationalizing," and activating.

Most companies with traditional data storage and access systems, Brobst argued, are stuck in the first three stages and are faced with a "chasm" to cross to move into the final two stages, where data become integrated into daily, hourly business processes, accessible not just to corporate managers but to in-the-field decision makers, and finally "activated," that is, used to set off automatic triggers (when to make a specific offer to a specific customer speaking to a call-center rep, for instance).


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Brobst cited a Gartner studay that shows a quarter of existing businesses leading the way in those final two stages, while fully half of all U.S. businesses will be there in 12 months. Needless to say, new data-warehouse architectures, including Teradata's enterprise data warehouse products, will be required to achieve this singular, integrated, "activated" information vision.

I have three responses to this vision. One is that Brobst's diagnosis is much the same thing that Sun Microsystems CTO Greg Papadopoulos is describing when he talks about the "red shift": in the new world of exploding data quantities, the companies that are best able to marshal, integrate, and make use of data across departments and functions will enjoy double-digit growth in the coming years.

Second, I think both Brobst and Gartner are overly optimistic about the maturing process around data warehousing. The availability of effective, relatively inexpensive storage and networking tools notwithstanding, most companies I talk with are still stuck in Phase 1, reporting and collecting data from all their operations, and are only now moving into effective and relevant analytics around that information. As Brobst himself noted, "More than half cost of data warehousing is in data integration and cleansing -- it's an n-squared problem." Small and medium-sized businesses in particular are a long way from making near-real-time business decisions based on the volumes of data flooding their servers.

Third, the red shift or data explosion is going to have a profound effect on the position and perception of IT departments within organizations. Essentially, since the dot-com crash IT has been seen as a cost center, and one that is continually asked to do more with less. Innovation and revenue creation have given way to the necessary evils of cost-cutting and basic maintenance. Once Brobst's concept of the "active data warehouse" becomes a reality (and gets understood by CEOs), whole new landscapes of top-line growth and big new efficiencies will open up -- but only for CIOs who can conquer the data mountains now looming before them.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links