power-inverters-storage-markets-and-datacenters
Use when working on the modern grid: inverters, renewables and the inertia problem including grid-following versus grid-forming and other inverter-based-resource realities, storage technologies and their roles, markets and dispatch, writing grid software including the character of the domain and why OT security is not IT security, and datacenter power from the facility down to what software engineers actually control.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 5
- Forks
- 3
01 前言 Front Matter
- name
- power-inverters-storage-markets-and-datacenters
- description
- Use when working on the modern grid: inverters, renewables and the inertia problem including grid-following versus grid-forming and other inverter-based-resource realities, storage technologies and their roles, markets and dispatch, writing grid software including the character of the domain and why OT security is not IT security, and datacenter power from the facility down to what software engineers actually control.
03 SKILL.md 正文
Power Engineering: Inverters and Renewables, Storage, Markets, Grid Software, and Datacenter Power
Part 4 of 5 of the Power Engineering reference (plugin
power-engineering), covering §8–§12. Sibling skills:power-ac-fundamentals-generation-and-grid(§0–§3),power-system-analysis-and-protection(§4–§5),power-scada-ems-and-protocols(§6–§7),power-reference(§13–§18). Section numbers are shared across the set; a reference written as §N →skillpoints into that sibling skill.Currency: Circuit theory and power system analysis are settled; the inverter-dominated grid and datacenter load growth moved fast. See §15 →
power-referencefor both, dated.
Scope. Complements an electrical-engineering reference, which is circuit-level — components, op-amps, PCB layout, signal integrity. ⚠️ This is grid scale: kilovolts and megawatts, and the software that runs it.
⚠️ GOTCHA boxes mark what kills people, destroys equipment, or causes blackouts.
The three ideas that organize the whole field:
- ⚠️ Generation must equal load, continuously, everywhere. The grid stores almost nothing. Frequency IS the balance signal — it falls when load exceeds generation and rises when it doesn't, in real time, across a continent (§1.4 →
power-ac-fundamentals-generation-and-grid).- ⚠️ Reactive power is not "wasted" power — it's a separate commodity that must also balance, and it's local. Real power flows across a system; reactive power doesn't travel well, so voltage is a local problem and frequency is a global one (§1.2 →
power-ac-fundamentals-generation-and-grid).- ⚠️ Protection is the fastest software in the system and it acts on trust. A relay decides in milliseconds to disconnect equipment, and it must be right — a false trip causes an outage, a missed trip destroys equipment or kills someone (§5 →
power-system-analysis-and-protection).
§8. Inverters, Renewables, and the Inertia Problem
⚠️ This is the defining engineering transition in power systems, and it is not primarily about intermittency — it's about the loss of physics-based stabilization.
8.1 The mechanism
A synchronous generator's rotating mass stores kinetic energy that opposes frequency change automatically. ⚠️ As one source puts it well: the beauty of that system was its simplicity — the stored rotational energy required no control systems, no communication networks, and no human intervention.
⚠️ Replace those machines with inverter-based resources (IBRs) and that mechanical buffer disappears. Documented consequences:
- Reduced inertia → larger frequency deviations and higher RoCoF for the same disturbance.
- ⚠️ Reduced short-circuit strength → falling Short-Circuit Ratio (SCR), which breaks
protection (§5 →
power-system-analysis-and-protection) and can cause grid-following inverters to lose synchronization entirely. - Subsynchronous resonance and oscillation risk from converter control interactions.
8.2 Grid-following vs grid-forming
⚠️ The distinction to understand:
- Grid-following (GFL) — ⚠️ operates as a controlled current source, deriving synchronization from grid voltage via a PLL and injecting commanded P and Q. This worked precisely because the grid's stability was guaranteed by other means. ⚠️ The paradox that's now acute: GFL's own success displaced the machines that made it viable.
- Grid-forming (GFM) — ⚠️ operates as a voltage source, generating the frequency and amplitude reference rather than following one. Can run islanded, provides synthetic inertia, primary frequency response, voltage regulation, and ride-through, and improves stability under low SCR. Some can black start, with additional design work for inrush current.
⚠️ Control approaches: droop, virtual synchronous machine (VSM) / virtual synchronous generator control, and adaptive inertia injection with virtual damping — which points at something conceptually important: ⚠️ future grids may be intentionally designed around the fast, programmable response of GFM inverters rather than trying to replicate rotating-machine dynamics. Stability through software-defined control rather than inertia-heavy mechanical systems.
⚠️ GOTCHA — GFM inverters are not the silver bullet they're sometimes presented as, and the deployment evidence is sobering. ⚠️ In the UK's Stability Pathfinder procurement rounds, GFM inverters were largely unsuccessful in winning contracts — only around 12% of the UK's contracted inertia will be met by GFM inverters by 2026, with the rest going to synchronous machines, dominated by synchronous condensers. ⚠️ A synchronous condenser is a spinning machine that generates no power — it exists purely to provide inertia and reactive support. The market's revealed preference has been to add back rotating mass. Germany's 2026 market-based inertia procurement, which differentiates remuneration by technology type, may produce a different answer — and it's genuinely uncertain whether GFM remuneration will be sufficient.
8.3 Other IBR realities
Curtailment, the duck curve (⚠️ midday solar depresses net load, then a steep evening ramp — the ramp rate is the operational problem, not the energy), forecasting as a first-class operational input, and ⚠️ hosting capacity limits on distribution feeders — reverse power flow from rooftop solar breaks assumptions built into voltage regulation and protection.
⚠️ Standards are catching up: IEEE 1547 for DER interconnection, IEEE 2800 for transmission-connected IBRs, and NERC guideline revision work explicitly addressing IBR fault performance. ⚠️ Interconnection requests in 2026 increasingly ask whether equipment is grid-forming capable.
§9. Storage
| Technology | Duration | ⚠️ Notes |
|---|---|---|
| Li-ion BESS | ⚠️ ~1–4 h | Dominant; fast, and duration-limited |
| Pumped hydro | 8–24 h+ | ⚠️ ~95% of world storage capacity; geography-limited |
| Flow batteries | 4–12 h | Decoupled power and energy |
| Compressed air, thermal | Long | Niche |
| Hydrogen | Seasonal | ⚠️ Poor round-trip efficiency |
⚠️ Batteries are inverter-interfaced (§8), which means their grid services are a software question: frequency regulation (⚠️ the highest-value early application, because they're faster than any generator), energy arbitrage, capacity, synthetic inertia via GFM control, black start, and T&D deferral.
⚠️ The one that matters for software: state of charge is a hard constraint that couples decisions across time. A battery dispatched greedily for regulation revenue can be empty when the capacity obligation lands. Every storage optimization is a temporal one, and cycling degrades the asset — so the objective function has to include degradation cost or it will destroy the battery profitably.
§10. Markets and Dispatch
Unit commitment — ⚠️ which units to turn on over the next day, a mixed-integer
program with minimum up/down times and startup costs.
Economic dispatch — how much from each committed unit, continuously.
Optimal power flow (OPF) — ⚠️ dispatch subject to the physical network constraints of
§4.1 → power-system-analysis-and-protection. AC OPF is non-convex and hard; DC OPF is what most markets actually clear on.
LMP (locational marginal price) decomposes into energy + congestion + losses — ⚠️ which is why prices differ between buses, and why congestion is visible as a price signal rather than only as an engineering limit. Negative prices occur when must-run generation and inflexible renewables exceed load.
Market structure: day-ahead and real-time, ancillary services (regulation, spinning and non-spinning reserve, voltage support, black start — ⚠️ and increasingly inertia, §8.2), and capacity markets.
⚠️ For a software engineer, the notable property: this is a large-scale optimization running on a schedule with hard deadlines and real money attached. ⚠️ A market clearing that doesn't converge in time is an operational emergency, not a failed job.
§11. Writing Grid Software
11.1 The character of the domain
⚠️ Timescales span twelve orders of magnitude, and which one you're in dictates everything:
µs–ms protection, GOOSE, sampled values ⚠️ hard real-time, safety-critical
ms–s inverter control, AGC
s–min SCADA, state estimation
min–h dispatch, markets
h–yr planning
⚠️ Reliability expectations are extreme: control-room systems target very high availability, field devices run for 20+ years, and the cost of a wrong answer is measured in outages and lives. This is much closer to avionics and automotive practice (see those references) than to web engineering.
11.2 ⚠️ Security — OT is not IT
NERC CIP in North America is a mandatory, auditable, fineable standard covering asset identification, security management, personnel and training, electronic security perimeters, physical security, system security management, incident response, recovery, configuration change management, and supply chain risk. ⚠️ The OT/IT differences that catch software engineers out:
- Availability outranks confidentiality — ⚠️ the reverse of most IT threat models.
- ⚠️ You cannot patch on Tuesday. Devices may not be patchable at all, and taking them out of service requires a switching order.
- ⚠️ Air gaps are largely mythical in practice — segmentation, unidirectional gateways and rigorous perimeter control are the real controls.
- Legacy protocols with no authentication (§7 →
power-scada-ems-and-protocols) mean network position is authorization, which is exactly why segmentation carries the load. - ⚠️ Ukraine 2015/2016 and Industroyer/CRASHOVERRIDE are the reference cases — grid
malware that spoke the protocols in §7 →
power-scada-ems-and-protocolsnatively.
11.3 Practice
Testing: simulation against a network model, hardware-in-the-loop with real relays
(⚠️ real-time digital simulators are standard for protection validation), replay of
recorded disturbances, and model validation against actual event data — ⚠️ which is
where a lot of models are found wanting after a real disturbance.
Tools: PSS/E, PowerWorld, PSCAD/EMTP (⚠️ electromagnetic transient simulation —
required for inverter control studies, because phasor-domain tools miss the fast
dynamics), OpenDSS and GridLAB-D (distribution), PYPOWER, pandapower, PowerModels.jl,
MATPOWER (⚠️ the open research stack), GridPACK, Grid2Op for RL work.
Data: CIM (§7 → power-scada-ems-and-protocols), historians, PMU archives, and ⚠️ an obsession with time
synchronization — PTP/IEEE 1588 and GPS, because sequence-of-events analysis after a
disturbance depends entirely on trustworthy timestamps.
§12. Datacenter Power
⚠️ The part of this document most software engineers will actually touch — and the
industry has crossed a threshold where compute demand is now a first-order power system
problem (§15.2 → power-reference).
12.1 The facility
Utility feed → transformer → switchgear → UPS → PDU → rack PDU → PSU → server
↕ ↕
generator battery/flywheel
Redundancy notation: N (no redundancy), N+1, 2N (⚠️ fully duplicated), 2N+1. Tier I–IV (Uptime Institute) — ⚠️ Tier III is concurrently maintainable, Tier IV is fault tolerant, and the distinction is whether a single failure during maintenance takes you down.
UPS topologies: double-conversion (⚠️ best isolation, worst efficiency), line- interactive, and eco/multi-mode which bypasses conversion when input is clean. Generators for extended outages (⚠️ and the fuel contract is the real constraint, not the generator).
⚠️ PUE (Power Usage Effectiveness) = total facility power / IT equipment power. 1.0 is perfect; hyperscale runs near 1.1; older enterprise 1.5–2.0.
⚠️ GOTCHA — PUE measures facility overhead, not useful work. ⚠️ A facility at PUE 1.05 running inefficient inference wastes more energy per useful output than a facility at higher PUE running efficient workloads. PUE cannot see software efficiency at all, which is why "tokens per watt" style metrics are the ones that matter to the people reading this. Optimizing PUE while ignoring compute efficiency is optimizing the denominator you don't control.
12.2 What software engineers control
⚠️ Rack density is the current design driver — modern AI racks reach ~140 kW, against a traditional ~5–15 kW, which is why liquid cooling moved from exotic to standard. ⚠️ Air cooling runs out well below current GPU rack densities.
Levers that are actually software decisions:
- ⚠️ Utilization. An idle server draws a large fraction of peak. Consolidation and autoscaling are power engineering.
- Efficiency per unit of work — model choice, quantization, batching, caching. ⚠️ The largest lever, and invisible to every facility metric.
- Carbon-aware scheduling — ⚠️ shift flexible work in time or geography toward low-carbon grid conditions. Real, and limited to genuinely deferrable workloads.
- ⚠️ Demand flexibility — and this is now a grid-interface question, not just an
internal one (§15.2 →
power-reference).
04 同仓库更多 Skills
white-paper-writing
Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks "how should I structure this" for a long-form document.
prose-technical-mechanics
Use when editing or writing prose at a technical/mechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.
prose-mechanics
Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate/Jamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix "AI-sounding" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.
narrative-structure
Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or "how should I structure this story/pitch/presentation" request.
legal-brief-writing
Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic/neurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.
journal-publishability-criteria
Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs/paper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.