Mike Howells's Blog

Tag: Ameren

  • The Grid Behind the Grid

    The Grid Behind the Grid

    Part 2 of a series on what I learned by accident when I started paying attention to my electricity bill.

    After Post 1 went up, the question I couldn’t stop turning over was this: if the 10 PM cutoff on my Ameren bill maps to actual physics on a continental-scale grid, then what does that grid actually look like? Not in a metaphorical sense. Mechanically. What is the thing on the other side of my wall outlet, and how does it stay running?

    I went looking, and the answer turned out to be more remarkable than I expected, and also more fragile than I expected. By the end of what I learned, I had stopped thinking of the grid as a robust piece of infrastructure that occasionally fails, and started thinking of it as something closer to a precision-balanced machine that succeeds every day for reasons that aren’t obvious until you understand them.

    This post is about that machine. It’s also about the time it almost broke, what we did to prevent that from happening again, and why something very similar is now happening on purpose, at scale, in ways that the people building it may not fully appreciate.

    A bicycle, going exactly ten miles per hour

    The single most useful way I’ve found to think about how the grid works is this:

    Imagine you’re riding a bicycle, and someone tells you that you must maintain exactly 10 miles per hour. Not 9.99, not 10.01. Exactly 10. Forever. The route ahead has hills you can’t see coming. When the road slopes up, you have to pedal harder. When it slopes down, you have to ease off, or maybe even brake. And if at any point you drift more than half a percent off speed, the bicycle disintegrates.

    That’s the grid.

    The “speed” in this metaphor is frequency. In North America, the grid runs at 60 cycles per second, also written as 60 Hz. Every generator on the grid spins at exactly this frequency, all the time. The frequency is the speed of the bicycle, and it has to stay locked at 60 Hz the way the bike has to stay locked at 10 mph.

    What makes this difficult is the hills, which are changes in demand. Every time someone turns on an air conditioner, opens a refrigerator, or starts a dishwasher, the grid encounters an uphill. The bicycle has to pedal harder. Every time someone turns off a load, the grid encounters a downhill, and has to ease off. And all of this is happening continuously, across millions of customers, every second.

    Grid operators tolerate about ±0.05 Hz of deviation from 60 Hz before they start getting nervous. That’s about 0.08% off speed. If the frequency drifts beyond roughly ±0.5 Hz, less than 1% off, protective equipment starts tripping generators offline to keep them from damaging themselves. That’s the bicycle disintegrating. Once a few generators trip, the remaining ones have to carry their load, which usually pushes frequency further out of bounds, which trips more generators. The cascade can run faster than anyone can intervene.

    So the bicycle has to stay at exactly 10 mph, on terrain it can’t see, with a margin of error under one percent, or it falls apart.

    Now imagine the bicycle is the size of a continent.

    Half a continent, in perfect sync

    The grid I’m part of, here in Missouri, is connected to a synchronous network called the Eastern Interconnection. It covers everything from the Rocky Mountains east to the Atlantic, plus most of eastern Canada. Roughly 39 states and 5 Canadian provinces.

    Every generator in that footprint, from a nuclear plant in Florida, to a coal plant in Ohio, to a wind turbine in Manitoba, to the natural gas plant down the road from my house, is spinning at exactly the same frequency, in exactly the same phase, every second of every day.

    That sentence took me a while to absorb when I first read it. Not approximately the same frequency. Not averaged over a minute. Right now, this exact second, hundreds of thousands of rotating machines spread across thousands of miles are all turning together in perfect synchronization. If they fell out of sync, the system would tear itself apart in seconds.

    This is achieved through what’s called synchronous coupling. When a generator is connected to the grid, the grid itself acts like a giant flywheel pulling it into line. A generator trying to speed up gets resisted by the inertia of every other generator. A generator trying to slow down gets pulled back by them. All those spinning turbines are mechanically locked together, by electromagnetism, into a single coordinated machine the size of half a continent.

    That machine is what we mean when we say “the grid.” Not the wires. The wires are just the connections between the rotating parts of the bigger machine.

    The thing that coordinates the bicycle

    Coordinating this machine in real time is the job of regional grid operators. The one that handles my electricity is called MISO, the Midcontinent Independent System Operator. MISO doesn’t own generators or transmission lines. It’s a coordinator, a market operator, and a referee.

    What MISO does, in simplified terms, is run an auction. Every five minutes, MISO collects bids from generators across its footprint, fifteen states’ worth of them, and figures out the cheapest mix of plants to run to meet projected demand for the next five minutes. The cheapest generation wins. That coal plant in Illinois, that wind farm in Iowa, that gas plant in Louisiana, all bidding into a single market that picks the lowest-cost combination.

    Underneath that five-minute market is something faster and more nervous. Every four seconds, MISO sends signals to specific generators telling them to ramp up or down a little, to keep the system frequency locked at 60 Hz. This is called Automatic Generation Control, and it’s how the bicycle stays at exactly 10 mph in real time. If frequency starts drifting up, MISO tells some generators to ease off. If it drifts down, MISO tells others to push harder.

    And underneath that, faster still, is the inertia of the machines themselves. When a sudden change hits the grid, the spinning mass of every connected generator absorbs the shock automatically, for the first few seconds, before any human or computer can react. That stored kinetic energy is what gives operators time to respond at all.

    So the grid is layered. Spinning inertia handles the millisecond response. AGC handles the four-second response. The five-minute market handles the minute-to-minute economic dispatch. Human operators handle the longer-term decisions about which plants to bring online or shut down across hours and days.

    It works, almost all of the time. But not always.

    The seven seconds it almost all came apart

    On August 14, 2003, a transmission line in northern Ohio sagged in the heat of an afternoon and touched a tree. That single point of contact tripped the line offline. On most days, that’s a routine event. The grid is designed to handle the loss of any single component without cascading failure.

    But on this particular day, the monitoring software at FirstEnergy, the Ohio utility responsible for that section of grid, had crashed. Operators didn’t know the line had failed. They didn’t take corrective action. Power that had been flowing on the tripped line had to find another path, so it flowed onto adjacent lines, overloading them, until they tripped too. Now more lines were down, and the remaining ones had to carry even more power, until they tripped, until a 3,500 megawatt power surge slammed across the regional grid in a direction operators hadn’t planned for.

    What happened next is one of the strangest and most important things I learned in all of this.

    The grid didn’t fail because it ran out of electricity. There was plenty of generation. What collapsed was something more subtle. As lines tripped offline, the ones still standing couldn’t sustain the voltage that the system needed to keep functioning. Voltage started sagging across the region. Generators saw the sagging voltage and started disconnecting themselves to avoid being damaged.

    Within seconds, the cascade of generators tripping offline created the very crisis the system was designed to avoid. The grid depended not only on real power, but on something called reactive power, an invisible supporting force that maintains voltage across the transmission system and allows electricity to actually flow. When reactive power support failed, the grid could no longer deliver electricity to customers, even though plenty of real power was still being generated.

    The cascade ran across the Northeast in about seven seconds. By the time it stopped, 265 power plants had shut down, over 500 generators had tripped offline, and 55 million people from Detroit to New York to Toronto were in the dark. It took several days to fully restore service.

    The lights went out, not because we ran out of electricity, but because we ran out of the ability to deliver it.

    What we did about it, and what we missed

    The 2003 blackout fundamentally changed how the North American grid is regulated. Before 2003, the reliability standards that grid operators followed were voluntary. After 2003, the U.S. Energy Policy Act of 2005 made those standards mandatory and enforceable, with serious financial penalties for violations. The body that writes those standards, NERC, the North American Electric Reliability Corporation, gained real teeth.

    The grid genuinely got more robust. Better monitoring. Better automated controls. Sensors called synchrophasors that measure grid state thirty times per second across thousands of locations. Operators today have visibility that operators in 2003 could not have imagined.

    We have not had another 2003-scale cascade in the Eastern Interconnection in the more than twenty years since. That’s not nothing. That’s a real achievement.

    But the regulators built that achievement to defend against a particular kind of failure. The 2003 cascade started with a tree branch and a software bug. The whole regulatory regime is oriented toward preventing transmission failures from cascading into voltage collapses.

    It is not oriented toward what happens when a brand new category of customer voluntarily disconnects from the grid in milliseconds, in coordinated waves, by design.

    The thing that already happened, that no one told you about

    On July 10, 2024, in northern Virginia, a piece of relatively routine grid equipment failed. A surge arrester, a device that protects transmission lines from voltage spikes, malfunctioned on a 230 kV line. The transmission line itself didn’t go down catastrophically. The system handled the equipment failure the way it was designed to: it briefly dipped the voltage on that line a few times in rapid succession, called a multi-shot reclose, while the line attempted to recover.

    This is the kind of event that happens dozens of times a year on the U.S. grid. Operators barely notice. The grid absorbs the disturbance and moves on.

    Except this time, sixty data centers were watching.

    The data centers detected the brief voltage dips and, doing exactly what their internal protection systems were designed to do, instantly disconnected themselves from the grid and switched over to their on-site backup power. All of them. In milliseconds. Across twenty-five different substations.

    The total load that vanished from the grid in that moment was about 1,500 megawatts. The equivalent of three large power plants suddenly going offline, except in reverse: instead of generation disappearing, customers disappeared. The grid suddenly had 1,500 megawatts of generation with nowhere to send it. Frequency started climbing. Automated controls had to scramble to dial back generation across the region before something worse happened.

    This event was not widely reported in the general press. It was the subject of a January 2025 NERC incident review that I doubt anyone outside the industry has read. But here is what NERC concluded from it: the way large data centers behave during routine grid disturbances was not anticipated by the planning studies, and current grid stability margins may not be sufficient to handle this new class of customer at the scale they are about to be deployed.

    In May of this year, NERC issued a rare Level 3 alert, the kind of alert reserved for genuinely serious grid reliability concerns, warning that uncoordinated disconnections of large computational loads pose a stability threat to the bulk power system. NERC simulations have suggested that a coordinated disconnection of 2,000 megawatts of data center load, well within the size of a single planned hyperscale campus, could destabilize 20 percent of the Eastern Interconnection. Fifty million people could lose power.

    That is the same scale of blackout as 2003. From the same kind of mechanism: a voltage disturbance, cascading. Except this time, the trigger wouldn’t be a tree branch. It would be a hyperscaler’s protection equipment doing exactly what it was designed to do.

    Where this is going

    I started this post by saying I had stopped thinking of the grid as robust infrastructure and started thinking of it as a precision-balanced machine. I want to be careful about what I mean by that. The grid is not on the edge of collapse. It works, every day, with extraordinary reliability, because of decades of engineering and regulatory effort. The bicycle stays at 10 mph.

    But the conditions the bicycle has to ride through are changing faster than the bicycle is being upgraded. The grid was built and regulated for a world where customers consumed power smoothly and predictably. We are now connecting customers, very large ones, who consume power in ways that the grid was not designed to handle, and we are doing so at a pace that grid planners cannot keep up with.

    Next Sunday, I want to write about the scale of what’s coming. Not the Virginia incident, but the buildout that’s about to dwarf it. Hyperscalers are no longer building data centers in tens of megawatts. They are building campuses in gigawatts. Plural. And they are building these campuses faster than the grid that’s supposed to serve them can be expanded.

    The result is a collision that’s just starting to play out, with implications that are going to reach all the way to your electric bill. I’ll get into it next week.

    Next Sunday: Why AI Might Not Get the Power It Needs. The collision between the AI data center boom and a grid that can’t keep up.

  • What My Electric Bill Taught Me About the Coming Grid Crisis

    What My Electric Bill Taught Me About the Coming Grid Crisis

    Part 1 of a series on what I learned by accident when I started paying attention to my electricity bill.

    It started with a dishwasher.

    Earlier this year, I switched my Ameren Missouri service over to a rate plan called Ultimate Saver. The pitch was straightforward: pay less for electricity if you can shift your usage away from peak hours. I’m not particularly frugal, but I’m curious about systems, and the structure of the plan was interesting enough that I wanted to understand it.

    What I didn’t expect was that trying to figure out when to run my dishwasher would pull me into a rabbit hole about how the entire North American power grid works, and into a slowly unfolding crisis that I think most people don’t realize is happening.

    This is the first of four posts about what I found. It starts small, with my own electric bill, and gets progressively bigger from there. By the end of the series I’ll be writing about why the AI data center boom is colliding with physical reality, and what that means for everyone who pays an electric bill.

    But first, the dishwasher.

    The plan that made me think

    Ultimate Saver has two parts that work independently of each other, which took me a while to untangle.

    The first part is time-of-use energy pricing. On weekdays, electricity costs more during two on-peak windows, 6 to 8 AM and 6 to 8 PM, and less during all the off-peak hours in between and around them. Weekends are entirely off-peak. So far, so simple: don’t run the dryer during dinner on a Tuesday.

    The second part is a demand charge. This one is weirder. Once a month, Ameren looks at every single hour of my electricity use between 6 AM and 10 PM, every day of the month, weekends included, and finds the one hour where I drew the most power. Whatever that peak hour was, in kilowatts, gets multiplied by a per-kW rate and added to my bill. One bad hour can dominate the demand charge for the entire month.

    When I first read this, I thought it was a gimmick. After spending some time with it, I think it might be one of the more honest pricing structures a utility has ever offered me.

    Here’s why. The cost of providing electricity isn’t really about how much energy you use over a month. It’s about how much capacity the grid has to maintain to serve you when you need it. A house that uses 1,000 kilowatt-hours spread evenly across a month is much cheaper to serve than a house that uses the same 1,000 kilowatt-hours but spikes hard for a few hours every evening. The first house lets the utility size its infrastructure to a steady average; the second house forces the utility to build for the peak and let that capacity sit idle most of the time.

    A demand charge takes that hidden reality and makes it visible. The price signal it sends is, basically: please don’t all hit the grid at once.

    Figuring out my own house

    Once I understood the structure, I started thinking about my own appliances. The big draws in a house like mine are the air conditioner, the electric dryer, the dishwasher (especially the heated dry cycle), the oven, and to a lesser extent things like the microwave.

    The AC was the puzzle to start with, because in summer it runs almost constantly. But here’s the thing about my thermostat: it’s set to 74°F during the day and drops to 70°F at 10 PM, when we go to bed. That means the AC’s most intense work, the pulldown from 74 to 70, happens right at 10 PM, the exact moment the demand-tracking window ends. The AC’s biggest single hour of the day falls outside the window that gets billed.

    So my real demand exposure during cooling season is the AC holding 74°F somewhere in the late afternoon, plus whatever else I happen to run on top of it. The pulldown is free.

    This made everything else simpler. If the AC’s contribution to demand is roughly fixed during the day, then the question becomes: what else am I stacking on top of it, and when?

    The dryer and the dishwasher, it turns out, are completely flexible. Nobody cares whether the dishwasher runs at 8 PM or 11 PM. Nobody cares whether the dryer finishes at 7 PM or 1 AM. These are appliances we treat as “run them whenever,” but their actual draw is significant. The dishwasher’s heated dry cycle and the dryer’s heating element are both heavy loads. Running them on top of an AC that’s already working hard in the late afternoon is exactly the kind of stacking that sets a new monthly demand peak.

    So I started running them after 10 PM. The dishwasher gets loaded throughout the evening and I just start it on my way to bed. The dryer is less convenient but still workable.

    It’s not a dramatic lifestyle change. It’s a small habit shift. But it removes both appliances from demand tracking entirely, and it captures the off-peak energy rate, which is a fraction of the on-peak rate. Two benefits for one decision.

    The question that broke the dam

    After a few weeks of this, a question started bothering me.

    Why 10 PM?

    The number is so specific. Not midnight, not 9 PM, not the time the sun sets. 10 PM, every day, weekends included. It’s the same number that ends the demand window and roughly the same time the on-peak energy pricing ends on weekdays. Ameren clearly chose it for a reason. But what reason?

    The easy answer is “that’s when people go to bed.” But that’s not really an answer. Lots of people don’t go to bed at 10 PM. And anyway, why would a utility care exactly when its individual customers go to bed? Utilities don’t bill at the individual scale; they think in aggregate.

    The real answer, I started to suspect, had to do with the grid itself.

    So I went looking.

    What I found when I looked at the actual data

    Ameren Missouri is part of a regional grid operator called MISO, the Midcontinent Independent System Operator. MISO coordinates electricity across 15 states and one Canadian province, from Minnesota down to Louisiana. They publish real-time operational data on their public website: how much electricity is being generated, where it’s coming from, how it’s flowing between regions, what the forecast looks like for tomorrow.

    I pulled their load curve for a normal weekday this spring. The shape of it is striking. Demand bottoms out around 4 AM at roughly 58,000 megawatts across the entire MISO footprint. It starts climbing around 6 AM as people wake up, grows steadily through the morning and afternoon, peaks around 6 to 7 PM at about 88,000 megawatts, and then, here’s the part that mattered to me, drops fast.

    By 8 PM, load is down 3,000 megawatts from peak. By 9 PM, it’s down 6,000. By 10 PM, it’s down 10,000. By 11 PM, it’s down 14,500 megawatts from the evening peak.

    Between 6 PM and 10 PM, the grid sheds roughly the equivalent of an entire nuclear fleet’s worth of demand. By the time the demand-charge window closes at 10 PM, the grid has genuinely entered a different operating regime. Expensive natural gas peaker plants that had to fire up to meet the evening peak can throttle back. Cheaper baseload generation, nuclear, coal, wind, handles the overnight load comfortably. The system is no longer stressed.

    That’s why 10 PM. It’s not about when I go to bed. It’s about when the grid as a whole stops needing to scramble. The number maps to physics, not to convenience.

    When I saw that, really saw it, in the actual hourly data, something shifted for me. The rate plan stopped feeling like a marketing structure and started feeling like a window into a real system. My dishwasher decision was a tiny instance of a much larger problem the grid is constantly solving.

    And the closer I looked at that larger problem, the more interesting it got. And the more concerning.

    Where this is going

    I want to tell you what I found, because I think most people have no idea how much is changing right now in the systems that quietly power their lives.

    Over the next three Sundays, I’ll be posting the rest of this series.

    Next week, I’ll write about what MISO actually does. How a continental-scale power grid manages itself in real time, what the 2003 Northeast Blackout taught us about how this can fail, and why every appliance you own is connected to a machine spanning half a continent that has to stay in perfect synchronization, every second of every day.

    The week after, I’ll get into what I now think is the most important undercovered story in the country: the collision between the AI data center boom and the physical infrastructure that has to power it. The companies building these data centers are starting to give up on the public grid entirely, with consequences that will eventually show up on your electric bill, whether you’ve heard about any of this or not.

    And in the final post, I’ll bring it back to where this started. What all of this means for someone like me, an ordinary Ameren customer running a dishwasher at 10 PM, and what we can actually do about it.

    I didn’t expect to spend this much time thinking about my electricity. But the more I understand about the system on the other side of my wall outlet, the more I think it’s one of the most important things I’ve ever paid attention to.

    The dishwasher was just the beginning.

    Next Sunday: The Grid Behind the Grid. What MISO actually does all day, and why the lights have to go out exactly as often as they do (which is more often than you think).