US/Canada Power Outage Task Force Event Timeline 303
bofus writes "The U.S./Canada Power Outage Task Force issued the Aug. 14, 2003 Sequence of Events at noon today. While no conclusions are drawn at this point, it does paint a pretty good picture of what happened and when it happened."
The blame game (Score:5, Interesting)
The blame will be put onderegulation and lack of government oversight.
Future Prevention (Score:4, Interesting)
Re:The blame game (Score:2, Interesting)
Re:Future Prevention (Score:2, Interesting)
MSBlaster.exe (Score:5, Interesting)
See:
this [pbs.org]or
this [automationtechies.com]or
this. [heise.de]
Bloomberg (Score:5, Interesting)
Neither responses were politically acceptable, however the media coverage of the blame game seemed to evaporate as soon as it was clear that it wasn't Canada's fault.
I found that more than a little interesting.
Late Night "Wacko" Talk Radio (Score:5, Interesting)
just my
Re:The blame game (Score:2, Interesting)
Anyway, severe load changes are likely to cause severe frequency changes, severe being +/- 10000 ppm or more. Naturally, this isn't helpful, and weird low-frequency feedback effects can happen as generators in different areas try to react to each other, and to the radically changing loads.
Disturbances Before Outage Itself (Score:5, Interesting)
Did anyone else notice a strobing effect in their fluorescent lighting in those 20-30 seconds before the full power outage? My understanding is that any sort of arc lamp (fluorescent, metal halide) will extinguish if the voltage sags beyond a certain point, so I doubt it could have been a voltage sag before the full blackout.
It almost seemed as if the power frequency itself had gone unstable...say from a nominal 60Hz to like 5Hz. Then again, with the modern electronic ballasts used today, who knows how they respond to a voltage sag. Maybe they strobe. Any one have any thoughts on this?
-Chris
Re:MSBlaster.exe (Score:2, Interesting)
Re:MSBlaster.exe (Score:5, Interesting)
I've still never understood this. I think most systems are actually based on NT, but maybe they are migrating to 2k now. Either way, the fact that these automation systems are based on a system like windows is very strange to me. OPC (the protocol used to communicate between sensors and databases) is based on DDE (or OLE), which seems so incredibly strange to me.
I've been developing a linux-based SCADA system. I took a look at quite a few systems, and I just didn't feel comfortable running any of them for a number of reasons. Stability and security being two major issues. Another was cost - these are being deployed in small installations, mostly for remote monitoring, which wouldn't typically have a SCADA system due to the cost. Between a mixture of existing open source software, some nice hardware, and in-house development (mostly me), the system has cost us about $20k to develop, which is less than it would cost to licence most software per site.
Anyways, that was a bit OT, but the point is, very early on we decided that deploying on windows would be a pain. These are all remote installations, with no one on site that can service them. If something goes down, I want to be able to remotely fix it as much as possible. I just don't feel comfortable deploying a remote windows system and relying on it to stay running, not to mention the fact that people's health could be affected (water treatment). To me, windows is not the proper platform to be using for this situation.
Re:The blame game (Score:2, Interesting)
Spin the thing by hand and see how easy it is to turn. Pretty easy. Now, short out the connections to the motor and you will find that it's considerably harder to turn it. There's some resistance to the turning there.
When you shorted out the leads on the motor (which is operating as a generator), you've increased the load on the generator from nothing to something very large. And, as that load increases, the generator gets harder to turn.
Since the frequency of AC power coming out of a generator is set by the speed at which the generator rotates, it's simple to see that if the load makes the generator harder to turn, it will slow down because of that load. That makes the frequency of the AC coming out go down.
Re:MSBlaster.exe (Score:3, Interesting)
Obligatory response: Woo-hoo! Linux all the way baby!
BTW, the EULA specifically prohibits NT and up from being used in "critical" situations where life and environmental damage are on the line. So it would be the utilities' fault, not Microsoft's.
Re:Future Prevention (Score:2, Interesting)
No, the trick is to USE the power plants in the same area that the load is located in. First Energy has at least 2 nuclear power plants in Northern Ohio and one of them was shut down. Energy companies are finding it cheaper to buy electricity on the open market instead of generating their own. Yes kids, de-regulation was a horrible mistake when you do it to public utility monopolies.
The blame game (Score:3, Interesting)
Tit for Tat.
Re:Disturbances Before Outage Itself (Score:2, Interesting)
So of course I shut down my Windows machine as fast as I could, as this isn't a beastly UPS by any means, and two computers on it won't last long. I'm skilled in the art of windows keyboard shortcuts, so shuting down was no problem. As far as writing code goes, I probably save the file I'm working on once at least every 60 seconds out of habbit, ctrl-s is your friend.
Kind of odd, when the power came back, the next day my central air conditioner wasn't working after I noticed it being hotter than blazes in my computer room. The circuit breaker for that had been tripped, none of the others were.
We had a flourescent tube that had been... (Score:3, Interesting)
Quebec's seperate and distinct power grid (Score:2, Interesting)
CNN (Score:1, Interesting)
Re:The blame game (Score:3, Interesting)
Roadmap? (Score:2, Interesting)