Commentary

Going Green Merits Yellow Light

The green rush is in full swing. But like overzealous forty-niners soiling themselves over a chunk of pyrite, companies are discovering there's a lot of fool's green mixed in with the good stuff.

The green rush is in full swing. But like overzealous forty-niners soiling themselves over a chunk of pyrite, companies are discovering there's a lot of fool's green mixed in with the good stuff.In their haste to replace IT and telecom equipment with new, eco-friendlier technologies, companies are finding themselves face to face with higher equipment costs, marginal energy savings, dubious profitability, and worse.

AT&T is in this last category. A series of equipment fires sparked by explosions of (green) backup batteries in its U-verse network cabinets culminated in a Christmas 2007 explosion in Wisconsin. The company is now replacing 17,000 lithium-metal-polymer batteries.


More Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

It isn't clear what the problem was, or whether it was directly linked to a flaw in lithium-metal-polymer technology, to a design error, to a manufacturing glitch, or something else. But once deemed safe by independent experts, the batteries "have failed at least four times now," reports LightReading.

The batteries were manufactured by a Canadian company called Avestor, which, unfortunately for AT&T, folded in October of 2006 and isn't around to help figure out what went wrong.

"It's no small task to change out the batteries in thousands of remote cabinets, especially when many of them are already powered up and handling working U-verse subscribers. It looks like a multimillion-dollar job," industry analyst Kermit Ross told LightReading.

Going green is an admirable goal. So is cutting costs. So is investing in new technologies. But the life-lesson cherished by cynics everywhere bears repeating: Behind every good intention lurks an unintended, unfavorable consequence.


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