Skip to content

Update utility rate downloads to URDB v8 to fix #743#760

Merged
brtietz merged 8 commits into
developfrom
urdb-v8-update
Nov 15, 2021
Merged

Update utility rate downloads to URDB v8 to fix #743#760
brtietz merged 8 commits into
developfrom
urdb-v8-update

Conversation

@cpaulgilman

Copy link
Copy Markdown
Collaborator

To test this pull request, temporarily replace for urdb_rates, urdb_companies, and urdb_companies_by_zip in webapis.conf with a valid NREL developer API key. **DO NOT COMMIT THIS TO THE SAM REPOSITORY **. Or, build a version of SAM from SAM-private.

URDB v8 URL

https://openei.org/services/doc/rest/util_rates/?version=8

Differences between v8 and v7

Request parameters have not changed between v7 and v8.

v8 has three new response fields for billing demand, none of which SAM uses for bill calculations:

lookbackMonths
lookbackPercent
lookbackRange

One response field is in v7 but not v8:

demandratchetpercentage

The following rate has lookbackPercent and lookbackMonths for testing (both are unused by SAM):

Arizona Public Service

Large General Service TOU (E-32 L) Secondary

https://openei.org/apps/USURDB/rate/view/5a5e2d055457a3e16be429d1l

There are no rates in the URDB with lookbackRange

No results from query (at bottom of https://openei.org/apps/IURDB/)

{"lookbackRange":"$exists","sector":"Residential","sector":"Commercial"}

https://openei.org/services/doc/rest/util_rates/?version=8

Adds three new variables (all unused by SAM):

lookbackMonths
lookbackPercent
lookbackRange

Removes one variable (also unused):

demandratchetpercentage

@sjanzou sjanzou left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good and works with a few rates I tested.

Comment thread deploy/runtime/ui/Utility Rate - Flat.txt
Comment thread deploy/runtime/ui/Utility Rate - Unused.txt
Comment thread deploy/runtime/webapis.conf

@brtietz brtietz left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The new items should be used to populate the billing demand inputs as per the issue description: #743

The URDB search query is based on version 7, so it's hard to find rates with these new values. Here's an example with lookbackRange: https://openei.org/apps/IURDB/rate/view/5f73585d5457a3dc0b692d6f#2__Demand

I'm fine with lookbackMonths going to unused items, but lookbackRange and and lookbackPercent should be populating ur_billing_demand_lookback_period and ur_billing_demand_lookback_percentages, respectively.

@cpaulgilman

cpaulgilman commented Nov 14, 2021

Copy link
Copy Markdown
Collaborator Author

Looking at this more, I'm not sure we can rely on lookbackRange and lookbackPercent values in URDB v8. Should we use those values to populate ur_billing_demand_lookback_period and ur_billing_demand_lookback_percentages anyway? One alternative would be to display a message if the URDB has lookback data suggesting that the user check the rate sheet to correctly populate the demand billing inputs manually.

Below is the result of my study of 3 rates in URDB v8.

urdbv8-json-files.zip

Village of Holbrook Nebraska Rate 9

https://assets.website-files.com/5a26c42ac0c9b0000147937c/6005a6480de8e00f07163a18_Large%20Industrial%20Service.pdf

https://openei.org/apps/USURDB/rate/view/53a19c105257a3d708077749#2__Demand

Notes

  • Not clear where URDB lookbackpercent comes from. Should the 60% apply to every month or only the summer season months?

  • URDB lookbackmonths matches billing periods in rate sheet.

  • This is a small utility and we don't have a copy of the rate sheet for this specific rate, so not sure we should use it as an example.

From URDB

"lookbackpercent":0.6
"lookbackrange":0
"lookbackmonths":[false,false,false,false,false,true,true,true,true,false,false,false]

From rate sheet

SECTION 5. BILLING DEMAND AND ENERGY:

A. Billing Demands

  1. Production Billing Demands

    a. The Production kW Billing Demand for the monthly Billing Periods of October through May (Winter Season) shall be determined as follows: The Customer’s measured demand coincident with NPPD’s maximum system demand occurring during On-Peak Demand Hours of the current Billing Period with adjustments, if any, to such measured demand for (i) kilowatt loss factor (Section 6) and (ii) power factor adjustment (Section 7). In the event that during all or a portion of the hour of the NPPD maximum system demand occurring during On-Peak Demand Hours of the current Billing Period there is no load at a Customer’s delivery point(s) due to an equipment outage, then for billing purposes NPPD shall estimate what the Customer’s load would have been at the delivery point(s) during this hour absent such equipment outage. The On-Peak Demand Hours for the Winter Season shall be 0801 to 2200 Central Time every Monday through Saturday, excluding New Year’s Day, Memorial Day, Thanksgiving Day, and Christmas Day.

    b. The Production kW Billing Demand for the monthly Billing Periods of June through September (Summer Season) shall be determined as follows: The average of the Customer’s highest measured demands during On-Peak Demand Hours on each of four (4) separate days during the current Billing Period or the three (3) Summer Season monthly Billing Periods immediately preceding the current Billing Period with adjustments, if any, to each such highest measured demand for (i) kilowatt loss factor (Section 6) and (ii) power factor adjustment (Section 7). The four (4) measured demands utilized for this calculation shall be selected from the same Billing Periods and in the same quantities as those utilized to charge the NPPD retail division for providing this service to the Customer. The On-Peak Demand Hours for the Summer Season shall be 0901 to 2300 Central Time every Monday through Sunday, excluding Labor Day.

SECTION 6. LOSS FACTORS:

For billing purposes, all power and energy sold and purchased under this Rate Schedule shall be based on Point of Measurement at Bus A. If the Point of Measurement is located at other than Bus A, the measured power and energy shall be adjusted for losses to Bus A by multipliers determined by NPPD.

Arizona Public Service E-32 L Secondary

http://www.aps.com/library/rates/E-32TOUL.pdf

https://www.aps.com/-/media/APS/APSCOM-PDFs/Utility/Regulatory-and-Legal/Regulatory-Plan-Details-Tariffs/Business/Business-NonResidential-Plans/e32_Large.ashx?la=en

https://openei.org/apps/USURDB/rate/view/5a5e2d055457a3e16be429d1#2__Demand

Notes

  • URDB lookbackpercent matches summer percentage in rate sheet.

  • URDB lookbackrange is zero, should be 12 (or 11?) months based on Item 2 in rate sheet.

  • URDB lookbackmonths don't quite match "May-October" description in rate sheet.

  • To import this correctly into SAM, the "Billing Demand Percentage" column of ur_billing_demand_lookback_percentages should be set to 80 for May-Oct and zero for Nov-Apr. That could be done by multiplying URDB loobackmonths by lookbackpercent (assuming lookbackmonths is correct).

From URDB

"lookbackpercent":0.8
"lookbackrange":0
"lookbackmonths":[false,false,false,false,true,true,true,true,true,false,false,false]

From rate sheet

For billing purposes, the kW used in this rate schedule will be the greater of the following:

  1. The average kW supplied during the 15-minute period (or other period as specified by an individual customer contract) of maximum use during the month, as determined from readings of the Company’s meter or in accordance with the Company’s Service Schedule 8.

  2. 80% of the highest kW measured during the six (6) summer billing months (May-October) of the twelve (12) months ending with the current month.

  3. The minimum kW specified in the agreement for service or individual contract.

Georgia Power Co PLL-11

https://www.georgiapower.com/content/dam/georgia-power/pdfs/business-pdfs/rates-schedules/5.00-pll.pdf

https://openei.org/apps/IURDB/rate/view/5f73585d5457a3dc0b692d6f#2__Demand

Notes

  • URDB lookbackrange is 12 compared with 11 in rate sheet.

  • URDB lookbackpercent matches rate sheet summer adjustment factor, but 60% winter adjustment is in demandcomments.

  • URDB lookbackmonths is empty. Assuming "true" is summer and "false" is winter, description in rate sheet could be could be interpreted as ' lookbackmonths = [0,0,0,0,0,1,1,1,1,0,0,0].

  • Based on rate sheet description SAM's "Consider Actual Peak Demand" column of ur_billing_demand_lookback_percentages would need to be be set to 1 for June through September.

From URDB

"demandattrs":[{"lookbackMinKW":"500"}]
"lookbackpercent":0.95
"lookbackrange":12
"demandcomments":"Lookback Percent is 60% in the not-summer months (Oct thru May)."

From rate sheet

DETERMINATION OF BILLING DEMAND:

The Billing Demand shall be based on the highest 30-minute kW measurement during the current month and the preceding Eleven (11) months.
For the billing months of June through September, the Billing Demand shall be the greatest of:

(1) The current actual demand, or
(2) Ninety-Five percent (95%) of the highest actual demand occurring in any previous applicable summer month (June through September), or
(3) Sixty percent (60%) of the highest actual demand occurring in any previous applicable winter month (October through May).

For the billing months of October through May, the Billing Demand shall be the greater of:

(1) Ninety-Five percent (95%) of the highest summer month (June through September), or
(2) Sixty percent (60%) of the highest winter month (October through May), including the current month.

Customers who change from a time of use type tariff will have their minimum Billing Demands calculated for the first Eleven (11) months on this tariff based on the greater of:

(1) 95% of the average of the four (4) Summer Months highest On-Peak kW, or

* Download URDB lookback percent and lookback range to Billing Demand inputs.

* Add URDB demand reactive power charge to Unused inputs.

* Automatically enable demand charges and billing demand when URDB rate includes them.

* When URDB contains lookback data, display UI message box advising user to check Billing Demand inputs.
@cpaulgilman

Copy link
Copy Markdown
Collaborator Author

@brtietz Let me know what you think of these latest commits.

@brtietz brtietz left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great! I think this is ready to merge at this point.

@brtietz brtietz merged commit 16e5dc2 into develop Nov 15, 2021
@brtietz brtietz added this to the SAM Fall 2021 Release milestone Dec 3, 2021
@cpaulgilman cpaulgilman deleted the urdb-v8-update branch December 7, 2021 23:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants