success-icon
The redesigned DominionEnergy.com is here!: A fresh look, easier navigation, and enhanced search features make it easier than ever to find the information you need.

Instructions for Using Weather Sensitive Profiles

Weather sensitive profiles are used to model energy using piece-wise linear regression of weather variables: temperature only (spring and fall), or temperature and relative humidity (summer only), or temperature and wind speed (winter only). Each weather sensitive profile is a Least Square Error regression based on historical hourly load data for a particular customer class, season and day type (e.g., RESVA, fall, Saturday, etc.) Each customer class will have a unique set of hourly weather sensitive profiles. A set of hourly profiles created for a four season, three day type customer class would consist of 288 sets of profiles (4*3*24).

Equation Development

A weather sensitive profile is calculated for each hour (1-24) from data in hour-ending format and is composed of one to three line segments, based on optimal temperature break points. The temperature breakpoints were determined to optimize the goodness of fit of the resulting regression equations. The temperature breakpoints (T-min, T-max) define the beginning and end of each line segment.

Each hour within a weather sensitive profile will be comprised of 1 to 3 sets of equations, depending on the season and day type.

The basic equation for a line is: Y = mX + b

Where

Y is the dependent or response variable, m is the slope of the line X is the independent or predictor variable, and b is the intercept or constant.

The full equation for estimating customer load from multiple weather variables is

LOAD(c)(h)(t) = (m1)(X1) + (m2)(X2) + b

Where

(c) = Customer class

(h) = Hour specified (1-24)

(t) = Temperature range m1 = temperature variable from the weather sensitive profile

X1 = temperature in degrees Fahrenheit from a weather station source

m2 = the auxiliary weather variable from the weather sensitive profile, either relative humidity (summer only) or wind speed (winter only). In the spring and fall this variable will be zero.

X2 = the auxiliary weather variable from the weather station, either percent relative humidity (summer only) or wind speed in miles per hour (winter only)

b = a constant

Note that the weather data for X1 and X2 will be from a weather forecast when the supplier is scheduling load and will be based on actual weather for settlement. (Also, please be aware that the constant coefficient should not be confused with base, or constant load. It is simply a coefficient in the regression equation and will vary widely within a class set of equations.)

Detailed Examples

For purposes of this example, we will use a hypothetical profile for a hypothetical customer class that we will designate as “Good Customers” or the GC class, as designated in column A. Secondly, we must determine the appropriate season and day type shown in column B. These tables are very wide and will appear below broken into three sections, one for each line segment.

Good Customer (GC) Profile
Spring Season Three Day Type (Weekday, Saturday, Sunday)
Weather sensitive profile

Spring Weekday

Applying these coefficients to the temperature data produces an average kW load per customer. Since the season is Spring, there are no coefficients for relative humidity (RH) or for wind.

LOAD (hour8)= -2.0649 + (0.049)(69) + (0.14)(0) + (5)(0)

LOAD (hour8)= -2.0649 + 3.381

LOAD (hour8)= 1.3161 kW

The regression software has also provided a range of acceptable values for the resulting answer (as shown in cols. V-W) to prevent unusually extreme temperatures from producing extreme results. The lower range for an acceptable answer is 0.6175 kW in this case, and the upper range is 2.8064 kW. Since 1.3161 is well within [P_Min<LOAD<P_Max] it is an acceptable answer.

Programming should include this test:

If Load<p_min then LOAD=P_min
Else
If Load>p_max then LOAD=P_max

Expand this average kW per customer number to your total customer class population by applying a scalar developed to reflect your number of customers in that class on that date, their usage factors, and the class loss factors.