851 S.W. Sixth Avenue, Suite 1100
Portland, Oregon 97204-1348
503-222-5161 fax 820-2370 www.nwcouncil.org/rtf
Date: April; 4, 2004
MEMORANDUM
TO: RTF Members
FROM: Tom Eckman, NWPPC; Ken Keating, Bruce Cody and Nelly Leap (BPA); Jeff Harris, NW
Alliance and Tom Wilson, David Bell and Paul Dionne (PCS UtiliData)
SUBJECT: Revised Automated CVR Protocol
At the February 10, 2004 RTF meeting the RTF tentatively approved the proposed “Automated CVR
Protocol No. 1.” There were two remaining items regarding the protocol that the RTF needed clarification on and they directed the RTF Subcommittee that had worked on the protocol to convene prior to the April 13, 2004 RTF meeting to clarify the items and to make recommendations. The two items were the re-verification triggers and protocols and the use of a 2 zone heating and cooling temperature compensation model.
A subcommittee meeting was scheduled by Tom Eckman with all interested parties invited and welcome. RTF Subcommittee met on March 16, 2003 at the NWPPC offices at 1:00 PM. The following persons attended the meeting: Tom Eckman, NWPPC; Ken Keating, Bruce Cody and
Nelly Leap, BPA; Jeff Harris, NEEA and Tom Wilson, David Bell and Paul Dionne (via phone) of
PCS UtiliData.
During the approximately 3 hour meeting the subcommittee developed the following recommended improvements/changes to the proposed “Automated CVR Protocol No. 1.”
Issue 1 – Two Zone Temperature Compensation
In the original proposed temperature compensation model a two zone model was proposed with a heating correction factor for temperatures below 65 degrees F and a cooling correction factor for temperatures above 65 degrees F.
The following two graphs which were included in the initial presentation to the RTF demonstrate the model. The first graph shows the heating only data and cooling only data on which separate Robust regressions are performed. Two slopes (or coefficients) are obtained. The second graph shows the combined heating and cooling data graphed against “heating or cooling degree hours, or a comfort temperature.” A fixed ratio of 2.5 was applied to the cooling data to take into account the assumed different between the efficiencies of heating and cooling equipment.

A three zone model was developed by PCS UtiliData in response to the request of further review by the RTF. The three zone model has a heating correction factor for temperatures below 65 degrees F, a cooling correction factor for temperatures above 70 degrees F and is no temperature correction for temperatures between 65 degrees F and 70 degrees F.
The following two graphs demonstrate impact of using the three zone model. The first graph shows the heating only data, cooling only data and neutral data. Separate robust regressions are performed on the heating only data and the cooling only data. Two slopes (or coefficients) are obtained. The robust median is computed for the data in the neutral zone. The second graph shows the combined heating, cooling and neutral zone data graphed against heating or cooling degree hours, or a
“comfort temperature.” The ratio computed by dividing cooling slope by the heating slope is applied to the cooling data to take into account the difference between the efficiencies of heating and cooling equipment on the particular feeder under study. No correction is made to data for temperatures between 65 degrees F and 70 degrees F.

Using the three zone model improves the accuracy somewhat. The table below shows the comparisons
Using 2002 Data to Forecast 2003 Results
Forecasted
Daily Savings
Actual* Daily
Savings
Feeder 1
343 kWh
0.87%
340 kWh
2 Zone Model
Feeder 3
660 kWh
2.8%
679 kWh
Feeder 1
347 kWh
0.87%
344 kWh
3 Zone Model
Feeder 3
631 kWh
1.4%
642 kWh
* Actual Daily savings computed using Robust Statistical Methods.
After discussion the Subcommittee agreed to recommend the use of the three zone model because;
 it seems to fit the physical world better and
 it seems to yield slightly more accurate results
Issue 2.
The re verification trigger wording as originally proposed was as follows:
Re-verification periods may need to be implemented after activities which significantly change the profile of a feeder’s load. These testing periods should be six weeks in length, with the system alternating between full CVR and at the controlled nominal midpoint above full CVR. Activities which trigger these testing periods may include, but are not limited to: changing load from residential to industrial, permanent reconfiguring of the

distribution system or a 10% growth in load. In addition, these test periods should happen every three years after the initial verification period, and upon request by invested parties.
After discussion the new recommended re-verification trigger wording is:
Re-verification will be required when there is a +/- 10% shift in temperature adjusted total annual load, a +/-10% shift in temperature adjusted total load during heating regime hours, a +/-10% shift in temperature adjusted total load during cooling regime hours, or a permanent reconfiguring of the distribution system (not including reconductoring, transformer replacement, capacitor banks, or other distribution system efficiency project).
If re-verification is triggered by a shift in the loads during heating or cooling regimes, the re-verification protocol will consist of one sixty day period during either the heating or cooling period. If re-verification is triggered by a shift in total annual load or a permanent re-configuration the re-verification protocol will consist of two sixty day periods, one in the heating period and one in the cooling period. During the reverification periods the system will alternate daily, operating one day at full voltage reduction and the next day at the controlled nominal midpoint.
The new CVRfs determined by these re-verifications will be used in lieu of the original
CVRfs.
At the conclusion of the meeting there was a concensus that these changes should be recommended to the full RTF and that with these changes the proposed “Automated CVR No.1” should be approved by the RTF.
________________________________________ j:\tom\rtf\2004_0413\cvrrevprotocolsummary.doc