Modern AI data centers consume enormous amounts of power, and it looks like they will get even more power-hungry in the coming years as companies like Google, Microsoft, Meta, and OpenAI strive towards artificial general intelligence (AGI). Oracle has already outlined plans to use nuclear power plants for its 1-gigawatt datacenters. It looks like Microsoft plans to do the same as it just inked a deal to restart a nuclear power plant to feed its data centers, reports Bloomberg.
Personally? I don’t think this is a bad idea. The less they drain from the grid, the less they consume fossil fuel.
The reactor isn’t active right now, and they are a PWR design, and like the 1979 incident showed, they do fail safely.
So long as Microsoft pays for the operation of the plant? Seems reasonable to me if they’re going to consume an assload of energy with or without public support.
we could use that extra energy to offset a bunch of existing carbon emissions now. This is still waste. If it’s going to be started up again, and its energy used for something useless, it’s waste.
If it also shifts their current load off the existing grid, that might be beneficial.
Microsoft would do it with or without the power plant. Make no mistake about that.
The same argument could be said if they made a 1GW solar farm, or any other form of power generation. Unless you have a way to legislatively prevent Microsoft from producing their own energy or prevent acquisition of decommissioned plants, I don’t see how you can prevent waste.
Is it going to be started up again?
If M$ doesn’t invest into this for their own purposes, is it still going to be started up? Or is your position that M$ should be investing in a nuclear power plant for the good of the world?
Because while I can agree with the idea, we all know that would never happen. So if it was never going to be started up again, we are at 0 gain or loss no matter what they do with it.
And that’s ignoring the fact that they are apparently intending on using that energy anyway.
it would be a missed opportunity in the sense of “if they can allow it to be turned it back on to waste its power on this dead-end tech, why couldn’t it have been allowed to operate again (earlier) for reasons we actually need?”
I’m not putting the blame on microsoft here, even though it might seem that way. But it’s not microsoft who need to give the go-ahead for this to happen. It’s the higher ups who decided to give the capacity to microsoft.
Yes it was still going to be used, but they could have been paying out the ass for it, which could fund other projects.
It operated for a long time profitably. It ceased operations in 2019 because it became unprofitable, largely because Methane undercut it. Methane should cost a lot more, but they don’t have to pay for negative externalities. Nuclear has to contain all of its waste, and handle it carefully.
as opposed to just spewing it out in the air? (carbon 14 is a thing, those things emit a lot more radioactivity to the environment)
I’m not saying they should not contain it. I’m saying other sources should have to. We only force one energy source has to pay for the cost of all of its waste. Why is that? It’s only to the benefit of dirty energy.
If there were plans for it to be used, then I’m with you. But if I’m being honest, I’d put money on the original plan consisting of letting it sit there for decades to come without being used.
And “paying out the ass” is what they will likely be doing, just to the private corpos that own the plant. It’s not government run, the money would never circle back to taxpayers beyond normal taxation.
that’s what I’m complaining about. If there can be plans now, why was the original plan just “let it rot”?
Greed? ¯\_(ツ)_/¯
I don’t think you’re going to get the answer you want here. But I’d be willing to bet M$ is dropping the $$$ for whatever retrofits and repairs need to be done, with the agreement being they get the power near cost for a set duration.
Obviously that’s speculation on my part, but would explain the situation quite cleanly.
That argument presupposes that the reactor would otherwise be brought back into operation, which I don’t think is necessarily the case.
I remember I had to do the 3 mile Island incident as part of my university degree. Apparently one of the biggest problems was that the control interface was hard to understand for the human operators.
So I guess if they just replaced the control system with a modern computer that would fix most of the problems. Obviously not a Windows system, otherwise we’ve just got the same issue all over again.
Introducing new Clippy For Reactors.
“It looks like you are trying to prevent a nuclear meltdown. I can help with that.”
It was the SCADA view right? A lot of SCADA software is basically running on top of windows, though you typically would never see the desktop. Ignition at least is cross platform, but that is because the server is Java and Jython. A big part of why things are running on windows is due to OPC, which was traditionally all DOM and .NET. It is basically a standard communications protocol and is what allows your HMI/SCADA to communicate with PLCs. Otherwise, you use proprietary drivers and native PLC specific protocols.
SCADA programming/design is kind of an art and is usually written by an either an overworked engineer or someone who had far too much time on their hands. You basically build screens using specialized software, hook up buttons and UI elements to PLC signals, and pass some signals from the UI to the PLC. They are all heading in the Edge/iot/cloud/web based/techno-babble direction these days…
Ignition, programming software is free!: https://inductiveautomation.com
Some other random ones I have seen or used in the past: https://www.siemens.com/global/en/products/automation/simatic-hmi/wincc-unified.html https://www.aveva.com/en/products/intouch-hmi/ https://www.rockwellautomation.com/en-us/products/software/factorytalk/operationsuite/view.html
“is usually written by an over worked engineer”
I’m in this post and I don’t like it.
But really these scada systems are rarely well defined by the time implementation happens. Often the architect has a great plan, but by the time it’s passed to a manager, a non-software engineer, to the product engineer to the automation team to the contractor the end result is “X data is pushed in With Y form and we use either a,b,or c date time stamp any nobody knows”
It continued operating for decades after the event. I’m sure they already solved that issue. It can still be improved I’m sure though.