4 CCR 723-3-3606 - Electric Energy and Demand Forecasts
(a)
Forecast requirements. The utility shall prepare the following energy and
demand forecasts for each year within the planning period.
(I) Annual sales of energy and coincident
summer and winter peak demand in total and disaggregated among Commission
jurisdictional sales, FERC jurisdictional sales, and sales subject to the
jurisdiction of other states.
(II)
Annual sales of energy and coincident summer and winter peak demand on a system
wide basis for each major customer class.
(III) Annual energy and capacity sales to
other utilities; and capacity sales to other utilities at the time of
coincident summer and winter peak demand.
(IV) Annual intra-utility energy and capacity
use at the time of coincident summer and winter peak demand.
(V) Annual system losses and the allocation
of such losses to the transmission and distribution components of the system.
Coincident summer and winter peak system losses and the allocation of such
losses to the transmission and distribution components of the
systems.
(VI) Typical day load
patterns on a system-wide basis for each major customer class. This information
shall be provided for peak-day, average-day, and representative off-peak days
for each calendar month.
(b) Range of forecasts. The utility shall
develop and justify a range of forecasts of coincident summer and winter peak
demand and energy sales that its system may reasonably be required to serve
during the planning period. The range shall include base case, high, and low
forecast scenarios of coincident summer and winter peak demand and energy
sales, based on alternative assumptions about the determinants of coincident
summer and winter peak demand and energy sales during the planning
period.
(c) Required detail.
(I) In preparing forecasts, the utility shall
develop forecasts of energy sales and coincident summer and winter peak demand
for each major customer class. The utility shall use end-use, econometric or
other supportable methodology as the basis for these forecasts. If the utility
determines not to use end-use analysis, it shall explain the reason for its
determination as well as the rationale for its chosen alternative
methodology.
(II) The utility shall
maintain, as confidential, information reflecting historical and forecasted
demand and energy use for individual customers in those cases when an
individual customer is responsible for the majority of the demand and energy
used by a particular rate class. However, when necessary in the resource plan
proceedings, such information may be disclosed to parties who intervene in
accordance with the terms of non-disclosure agreements approved by the
Commission and executed by the parties seeking disclosure.
(d) Historical data. The utility shall
compare the annual forecast of coincident summer and winter peak demand and
energy sales made by the utility to the actual coincident peak demand and
energy sales experienced by the utility for the five years preceding the year
in which the plan under consideration is filed. In addition, the utility shall
compare the annual forecasts in its most recently filed resource plan to the
annual forecasts in the current resource plan.
(e) Description and justification. The
utility shall fully explain, justify, and document the data, assumptions,
methodologies, models, determinants, and any other inputs upon which it relied
to develop its coincident peak demand and energy sales forecasts pursuant to
this rule, as well as the forecasts themselves.
(f) Format and graphical presentation of
data. The utility shall include graphical presentation of the data to make the
data more understandable to the public, and shall make the data available to
requesting parties in such electronic formats as the Commission shall
reasonably require.
Notes
State regulations are updated quarterly; we currently have two versions available. Below is a comparison between our most recent version and the prior quarterly release. More comparison features will be added as we have more versions to compare.
No prior version found.