Dr. Dobb's is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


Channels ▼
RSS

Adventures In X-treme Web 2.0


IT isn't our main business; it's an enabler. A leading specialty retailer with annual sales of $200 million, EMS has more than 75 stores, a seasonal catalog, and a growing online presence.

We design and sell a wide variety of gear and clothing for outdoor enthusiasts. To ensure we always have what customers need for their adventures, BI software helps managers determine which products are in demand and make sure they're in stock.

In 2005, soon after I came on board, we created a merchandising dashboard available to most employees throughout the organization. We built the dashboard in about three months using Information Builders' WebFOCUS 7.1.3 platform, and rolled it out across the organization in four weeks.

The architecture is straightforward: We use Information Builders iWay integration technology to access point-of-sale information on an IBM AS/400 computer and load it into a Microsoft SQL Server data mart. From there, WebFOCUS presents the data through a series of dashboards that users can view via their Web browsers.

In this way, decision-makers can quickly access a unified, high-level view of key performance indicators (KPIs) such as sales, inventory, and margin levels, and drill down to granular detail that analyzes specific transactions. They deemed the BI environment an instant success.

Now we're enhancing this dashboard to create a multifunction employee workbench called E-Basecamp. We want it to contain all the information relevant to corporate goals, integrated with productivity tools and role-based content customized to each individual user. Finally, we want to bring it to life by interweaving Web 2.0 technologies for collaboration among internal and external stakeholders. We'll launch this new version early this year.

Our company uses about 20 operational metrics to govern the fundamental health of the business. For example, managers in the merchandising area have to stay on top of inventory positions and stock turns. E-commerce managers monitor hour-by-hour Web traffic and conversion rates. Each area of the business relies on the dashboard to learn when certain KPIs are out of tolerance range. We make this easy with a color-coded system of red, yellow, and green alerts to indicate metrics that are over, under, or at plan.

In response to customer requests, we're also experimenting with embedding RSS feeds into the dashboard to drive more focused inquiries. In addition to providing a structure for decision-making, the idea is to encourage online conversations and information-sharing. If certain items sell better than others, it should be easy to analyze the transaction characteristics and selling behaviors that produce these results, then cascade that knowledge throughout the organization.

Did You Know

Blogs and wikis can be great collaboration tools, but they open a can of worms when it comes to intellectual-property and patent rights.

Bad blogs can blast IP, says Ilan Barzilay, an attorney at Wolf, Greenfield & Sacks, P.C., a Boston firm specializing in intellectual-property law. "If an overenthusiastic employee inadvertently discloses a company trade secret on his or her blog, the company loses its rights forever—any competitor can now legally use your former secret," he says. The law firm advises businesses to discourage most blogging on company time, and also to make sure that employees clearly understand the difference between personal and company information. — Paula Klein

For example, while cruising around our merchandise dashboard, one of our buyers observed an upward spike in footwear sales at a store. Investigating further, he learned that the employees there had perfected a multistep sales technique that included recommending socks designed for specific uses, such as hiking or running, along with an inner sole that could be custom fitted to each customer. Our BI dashboard made it easy to analyze the data to see what was selling, then drill down to see why. Not only did the buyer discover what prompted the growth in sales, he suggested that we formalize the practice across the chain. As a result, over a one-year period we saw a 57% increase in same-store sales in the footwear category and a 61% increase in the gross margin for that category.

The challenge now is figuring out how to encourage these collaborative interactions throughout the company and make them almost automatic. The goal is to let any dashboard user pose a hypothesis and invite commentary, almost like a notepad alongside the dashboard. That's the type of capability BI is supposed to provide.

Our dashboard examines Web visitors and sales by hour. We've successfully tied that data to an RSS feed so managers don't have to visit a Web page to view the latest numbers—the information now pops up on their desktops automatically.

We also plan to create a wiki that will let the user community test and refine hypotheses. In particular, we want our associates to share tips and best practices and initiate dialogues. If certain items sell better than others, the associates should be able to analyze the transaction characteristics and selling behaviors that produce the results, then use the collaborative tools to extend that insight throughout the organization.

One way we plan to do this is by creating blogs around a piece of data or a key metric. Blogs are a great way to post information to a Web site on a regular basis and invite comments. Many tools make it easy to archive, search, and categorize blogs for easy reference.

For example, if sales per payroll hour hover at $125 most months and suddenly drop to $75, a store manager might want to post an explanation or inquiry concerning the anomaly. A blog attached to a metric might reveal that payroll hours were higher that week to handle additional back-office work. Keeping comments in a blog lets readers observe patterns they might have overlooked using data analysis alone.


Related Reading


More Insights






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

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's 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 or spam. Dr. Dobb's 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.