der-hosting-capacity-mitigation

Name: der-hosting-capacity-mitigation
Author: Power-Agent

56stars12forks

How to install der-hosting-capacity-mitigation?

power-agent/powerskills/der-hosting-capacity-mitigation

$npx -y skills add Power-Agent/PowerSkills --skill der-hosting-capacity-mitigation

Installs into the current project.

Summary

Senior power-engineer playbook for distribution DER integration limits. Use whenever rooftop or utility-scale PV, storage, or other DERs push a feeder into voltage rise, reverse power flow, thermal limits, or protection desensitization — or when the question is how much more DER

Files · 1

View on GitHub

SKILL.md

1	# DER hosting capacity mitigation
2
3	Start by identifying the binding constraint, not by assuming it: hosting capacity is set by whichever of voltage, thermal, or protection binds first on this feeder.
4
5	## Preferred action order
6	1. Confirm the binding constraint with feeder snapshots at minimum load / maximum generation (OpenDSS, pandapower): voltage rise along the feeder, reverse flow at the substation, element loading, and regulator behavior.
7	2. Use inverter capability first: Volt-VAR and Volt-Watt curves, fixed power-factor settings, or export limits — these are cheap, fast, and usually recover significant headroom.
8	3. Adjust feeder controls next: regulator and LTC setpoints (including reverse-power mode behavior), capacitor switching coordination with the new flow patterns.
9	4. Re-check protection: reduced relay reach from DER infeed, sympathetic tripping, fuse-recloser coordination, and anti-islanding behavior under high DER output.
10	5. Reinforce last: reconductoring, an added regulator, phase rebalancing, or load/DER transfers — and quantify the hosting-capacity gain per upgrade so the cheapest sufficient fix wins.
11
12	## Working rules
13	- Study the minimum-load, maximum-generation snapshot; peak-load studies systematically miss DER constraints.
14	- Voltage rise and protection usually bind before thermal on weak feeders — do not stop at a loading check.
15	- Validate any fix across the daily profile (or a time-series run), not a single snapshot; Volt-VAR that fixes noon can misbehave at dusk.
16	- Legacy regulators may misoperate under reverse flow; check their mode explicitly before relying on them.
17	- Route persistent voltage problems to `voltage-violation-mitigation` and persistent loading problems to `thermal-overload-mitigation` once the DER-specific levers are exhausted.
18
19	## Deliver
20	- The binding constraint (voltage, thermal, protection) with the numbers and the snapshot that exposed it.
21	- The mitigation sequence applied, from inverter settings to reinforcement.
22	- The resulting hosting capacity and the first upgrade that buys the next increment.

People who liked this also viewed

6 picks

Type

der-hosting-capacity-mitigation

56stars12forks

View on GitHub

How to install der-hosting-capacity-mitigation?

power-agent/powerskills/der-hosting-capacity-mitigation

$npx -y skills add Power-Agent/PowerSkills --skill der-hosting-capacity-mitigation

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# DER hosting capacity mitigation
2
3	Start by identifying the binding constraint, not by assuming it: hosting capacity is set by whichever of voltage, thermal, or protection binds first on this feeder.
4
5	## Preferred action order
6	1. Confirm the binding constraint with feeder snapshots at minimum load / maximum generation (OpenDSS, pandapower): voltage rise along the feeder, reverse flow at the substation, element loading, and regulator behavior.
7	2. Use inverter capability first: Volt-VAR and Volt-Watt curves, fixed power-factor settings, or export limits — these are cheap, fast, and usually recover significant headroom.
8	3. Adjust feeder controls next: regulator and LTC setpoints (including reverse-power mode behavior), capacitor switching coordination with the new flow patterns.
9	4. Re-check protection: reduced relay reach from DER infeed, sympathetic tripping, fuse-recloser coordination, and anti-islanding behavior under high DER output.
10	5. Reinforce last: reconductoring, an added regulator, phase rebalancing, or load/DER transfers — and quantify the hosting-capacity gain per upgrade so the cheapest sufficient fix wins.
11
12	## Working rules
13	- Study the minimum-load, maximum-generation snapshot; peak-load studies systematically miss DER constraints.
14	- Voltage rise and protection usually bind before thermal on weak feeders — do not stop at a loading check.
15	- Validate any fix across the daily profile (or a time-series run), not a single snapshot; Volt-VAR that fixes noon can misbehave at dusk.
16	- Legacy regulators may misoperate under reverse flow; check their mode explicitly before relying on them.
17	- Route persistent voltage problems to `voltage-violation-mitigation` and persistent loading problems to `thermal-overload-mitigation` once the DER-specific levers are exhausted.
18
19	## Deliver
20	- The binding constraint (voltage, thermal, protection) with the numbers and the snapshot that exposed it.
21	- The mitigation sequence applied, from inverter settings to reinforcement.
22	- The resulting hosting capacity and the first upgrade that buys the next increment.

People who liked this also viewed

6 picks

Type