<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Technology Failure [.com!] &#187; Utilities</title>
	<atom:link href="http://www.technologyfailure.com/category/utilities/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.technologyfailure.com</link>
	<description></description>
	<lastBuildDate>Sat, 11 Jul 2009 22:28:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>MIT Technology Review&#8217;s 2002 article on 10 Technology Disasters</title>
		<link>http://www.technologyfailure.com/2009/06/22/mit-technology-reviews-2002-article-on-10-technology-disasters/</link>
		<comments>http://www.technologyfailure.com/2009/06/22/mit-technology-reviews-2002-article-on-10-technology-disasters/#comments</comments>
		<pubDate>Mon, 22 Jun 2009 15:49:39 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[Disruption]]></category>
		<category><![CDATA[Life Threatening]]></category>
		<category><![CDATA[Lives lost]]></category>
		<category><![CDATA[Public Transportation]]></category>
		<category><![CDATA[Utilities]]></category>

		<guid isPermaLink="false">http://www.technologyfailure.com/?p=138</guid>
		<description><![CDATA[MIT Technology Review published an article 10 Technology Disasters back in 2002:

What do a 17th-century Swedish warship, an opulent Chicago theater and a Kansas City hotel &#8220;skyway&#8221; have in common? All met catastrophic ends&#8211;and they have important lessons to teach today&#8217;s innovators.

Here is a list of the examined examples, along with reference links to Wikipedia [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.technologyreview.com/">MIT Technology Review</a> published an article <a href="http://www.technologyreview.com/communications/12857/page1/">10 Technology Disasters</a> back in 2002:</p>
<blockquote><p>
What do a 17th-century Swedish warship, an opulent Chicago theater and a Kansas City hotel &#8220;skyway&#8221; have in common? All met catastrophic ends&#8211;and they have important lessons to teach today&#8217;s innovators.
</p></blockquote>
<p>Here is a list of the examined examples, along with reference links to Wikipedia (except for the AT&#038;T crash). </p>
<ul>
<li><a href="http://en.wikipedia.org/wiki/Vasa_(ship)">The Vasa sinking</a></li>
<li><a href="http://en.wikipedia.org/wiki/Hyatt_Regency_walkway_collapse">The Hyatt Regency walkway collapse</a></li>
<li><a href="http://en.wikipedia.org/wiki/Iroquois_Theater_fire">The Iroquois Theater blaze</a></li>
<li><a href="http://en.wikipedia.org/wiki/Eschede_train_disaster">The Eschede train derailment</a></li>
<li><a href="http://en.wikipedia.org/wiki/Ashtabula_River_Railroad_Disaster">The Ashtabula Creek Bridge wreck</a></li>
<li><a href="http://en.wikipedia.org/wiki/St._Francis_Dam">The St. Francis Dam burst</a></li>
<li><a href="http://en.wikipedia.org/wiki/Atlantic_Empress">The Atlantic Empress/Aegean Captain collision</a></li>
<li><a href="http://www.phworld.org/history/attcrash.htm">The AT&#038;T network crash</a></li>
<li><a href="http://en.wikipedia.org/wiki/Northeast_Blackout_of_1965">The 1965 Northeast blackout</a></li>
<li><a href="http://en.wikipedia.org/wiki/Air_France_Flight_4590">The Concorde crash</a></li>
</ul>
<p>We&#8217;ll take more in-depth looks at some of these and many other examples in future posts and articles.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.technologyfailure.com/2009/06/22/mit-technology-reviews-2002-article-on-10-technology-disasters/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Genesis Energy left some customers without power</title>
		<link>http://www.technologyfailure.com/2009/06/20/genesis-energy-left-some-customers-without-power/</link>
		<comments>http://www.technologyfailure.com/2009/06/20/genesis-energy-left-some-customers-without-power/#comments</comments>
		<pubDate>Sat, 20 Jun 2009 19:51:50 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[Billing]]></category>
		<category><![CDATA[Disruption]]></category>
		<category><![CDATA[Utilities]]></category>
		<category><![CDATA[Weather]]></category>
		<category><![CDATA[Genesis Energy]]></category>
		<category><![CDATA[New Zealand]]></category>

		<guid isPermaLink="false">http://www.technologyfailure.com/?p=95</guid>
		<description><![CDATA[Genesis Energy, a New Zealand power company, left some of their pre-pay customers without electricity. Notably, this was a weekend during which it was also snowing and hailing.

Genesis says a pre-paid power account cannot be shut off over the weekend and instead customers just go into debt.
But a computer error has made it impossible for [...]]]></description>
			<content:encoded><![CDATA[<p>Genesis Energy, a New Zealand power company, left some of their pre-pay customers without electricity. Notably, this was a weekend during which it was also snowing and hailing.</p>
<blockquote><p>
Genesis says a pre-paid power account cannot be shut off over the weekend and instead customers just go into debt.</p>
<p>But a computer error has made it impossible for customers nationwide to top up their accounts over the weekend, so at 8am Monday some were cut off without warning.
</p></blockquote>
<p>(From <a href="http://tvnz.co.nz/national-news/computer-error-cuts-off-pre-pay-power-2764847">TVNZ</a>)</p>
<p>Cutting off a customer&#8217;s power is pretty significant, particularly during cold weather conditions. And on weekends, when customers may not have a chance to recharge their account balance. That is obviously, why company spokespeople seemed convinced that such a thing would not happen.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.technologyfailure.com/2009/06/20/genesis-energy-left-some-customers-without-power/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Utility Billing Mistake in Palo Alto</title>
		<link>http://www.technologyfailure.com/2009/06/20/utility-billing-mistake-in-palo-alto/</link>
		<comments>http://www.technologyfailure.com/2009/06/20/utility-billing-mistake-in-palo-alto/#comments</comments>
		<pubDate>Sat, 20 Jun 2009 18:07:41 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[Billing]]></category>
		<category><![CDATA[Utilities]]></category>
		<category><![CDATA[California]]></category>
		<category><![CDATA[Palo Alto]]></category>

		<guid isPermaLink="false">http://www.technologyfailure.com/?p=82</guid>
		<description><![CDATA[Mercury News reports that 830 customers were double-charged for their utilities in May:

The mistake came as the utilities department switched to a new billing system that is part of Palo Alto&#8217;s broader SAP network, said Tom Auzenne, assistant director of utility costumer support services.
The double-billing was not a computer glitch but a human error, he [...]]]></description>
			<content:encoded><![CDATA[<p>Mercury News <a href="http://www.mercurynews.com/peninsula/ci_12653624">reports</a> that 830 customers were double-charged for their utilities in May:</p>
<blockquote><p>
The mistake came as the utilities department switched to a new billing system that is part of Palo Alto&#8217;s broader SAP network, said Tom Auzenne, assistant director of utility costumer support services.</p>
<p>The double-billing was not a computer glitch but a human error, he said. It affected some &#8220;bank draft&#8221; customers who give the city their bank account numbers so their payments can be withdrawn automatically each month.
</p></blockquote>
<p>Yes, there is definitely human error here. It is worth noting though that similiarly to the recent <a href="http://www.technologyfailure.com/2009/06/19/errors-on-mays-eletric-bills-in-texas/">utility billing case in Texas</a>, customers with automatic bill pay transfers were affected by this.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.technologyfailure.com/2009/06/20/utility-billing-mistake-in-palo-alto/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Errors on May&#8217;s eletric bills in Texas</title>
		<link>http://www.technologyfailure.com/2009/06/19/errors-on-mays-eletric-bills-in-texas/</link>
		<comments>http://www.technologyfailure.com/2009/06/19/errors-on-mays-eletric-bills-in-texas/#comments</comments>
		<pubDate>Fri, 19 Jun 2009 23:36:08 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[Billing]]></category>
		<category><![CDATA[Disruption]]></category>
		<category><![CDATA[Utilities]]></category>
		<category><![CDATA[Oncor]]></category>
		<category><![CDATA[Texas]]></category>
		<category><![CDATA[TXU]]></category>

		<guid isPermaLink="false">http://www.technologyfailure.com/?p=68</guid>
		<description><![CDATA[It looks like a computer error caused inaccuracies to occur on some Oncor&#8217;s retail providers&#8217; electric bills. Oncor&#8217;s service area covers apparently a third of Texas.

About 130,000 customers in the Oncor service area, including 6,000 with TXU Energy, may have received an inaccurate bill last month, utility officials say. Bills could be unusually high or [...]]]></description>
			<content:encoded><![CDATA[<p>It looks like a computer error caused inaccuracies to occur on some Oncor&#8217;s retail providers&#8217; electric bills. Oncor&#8217;s service area covers apparently a third of Texas.</p>
<blockquote><p>
About 130,000 customers in the Oncor service area, including 6,000 with TXU Energy, may have received an inaccurate bill last month, utility officials say. Bills could be unusually high or possibly low.</p>
<p>The error is blamed on an Oncor computer glitch that caused incorrect usage and billing numbers to get passed on to some of the 70 or so retail electric providers that get their power through Oncor lines. Oncor, which covers a third of Texas, says it quickly fixed the glitch.
</p></blockquote>
<p>(From <a href="http://www.star-telegram.com/business/story/1429387.html">star-telegram</a>)</p>
<p>Some companies passed the errors on to their customers, who ended up receiving wrong bills. At that point the situation also turned into a bit of a customer service fiasco:</p>
<blockquote><p>
 Officer Kovach said her bill jumped from its usual $230 to $386. She called and complained and was told that she would get a corrected bill in 10-12 days. But it never arrived. She called and asked what she owed but was never told, she said.</p>
<p>Then a second bill came, and it was even higher. She spent another 90 minutes on the phone, she said, and asked for a supervisor. The supervisor said the first bill didn’t get fixed because her original call wasn’t handled by a supervisor.</p>
<p>She remembers asking, &#8220;Can you guarantee me that you will not cut me off?&#8221;</p>
<p>&#8220;Well, Ms. Kovach, I can’t assure you that,&#8221; the supervisor said.</p>
<p>&#8220;You’ve got to be kidding me,&#8221; she replied. &#8220;Your computer messed up. It’s your error, and you can’t assure me that my electricity won’t be cut off?&#8221;
</p></blockquote>
<p>It sounds like the staff was not well equipped to deal with this issue and/or was not easily able to take control using their own computer system. This was particularly irritating for those people who had elected to pay their bills via automatic, electronic transfers, as wrong amounts ended up being paid automatically, sometimes more than once.</p>
<p>It would be interesting to get more technical detail that outlines the causes of the problems surfaced.</p>
<p>The lesson for consumers here is to (at least) pay close attention to billing summaries.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.technologyfailure.com/2009/06/19/errors-on-mays-eletric-bills-in-texas/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
