Integrated Resource Plan Drafter

Use when a load-serving entity (LSE) — investor-owned utility, municipal utility, electric cooperative, or community choice aggregator (CCA) — needs to draft an Integrated Resource Plan (IRP) for a state public utility commission (PUC) or equivalent regulator. Guides scoped intake of filing utility, LSE type, jurisdiction (CPUC, WA UTC, OR PUC, NV PUCN, MT PSC, CO PUC, MN PUC, NC UC, VA SCC, etc.), filing cycle, statutory / PUC-decision authority, prior IRP docket and decision, due date, and planning horizon; builds the load forecast (peak / energy, reference / high / low, EE / BTM-PV / EV / DR / departing-load adjustments, reconciliation to PUC-assigned LSE load); builds the existing-resource inventory (utility-owned, PPAs, capacity / RA contracts, transmission rights, retirements, expiring contracts); runs the need assessment (capacity, energy, RPS / clean-energy, GHG, RA capacity contribution / ELCC); models a scenario matrix (reference, high-load, low-load, high-cost, policy-stress, fuel-shock, accelerated-retirement) with explicit assumption deltas; selects a preferred portfolio with NPV revenue requirement and customer-bill impact; runs sensitivities; documents the resource-adequacy showing; builds an action plan anchored to PUC milestones; and produces a DRAFT IRP filing packet with regulatory cover letter, executive summary, chapters in the regulator's required order, an equity / disadvantaged-community overlay where required, a confidentiality-treatment table, and an appendices index for the filing utility's regulatory team to verify, sign, and serve. Never determines whether the IRP satisfies a particular PUC's statute or decision, never affirms model output without the filing utility's resource-planning team verifying the underlying run, never opines that a portfolio is "least-cost / best-fit", and never serves the filing.

by @archlab-space (devasher)·MIT-0