Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Utility Rate Structures Fail to Consider Adjustments #55

Open
brtietz opened this issue Apr 1, 2024 · 2 comments
Open

Utility Rate Structures Fail to Consider Adjustments #55

brtietz opened this issue Apr 1, 2024 · 2 comments

Comments

@brtietz
Copy link

brtietz commented Apr 1, 2024

The data manager successfully connects to the URDB and downloads the rate data available in the rate field:

image

However, this is only one portion of the rate. Adjustments are also a critical feature https://apps.openei.org/USURDB/rate/view/62f12eaa7a464314265d3c76#3__Energy:

image

The actual values paid by the consumer are rate + adjustment: https://co.my.xcelenergy.com/s/billing-payment/residential-rates/time-of-use-pricing

@cancom84
Copy link
Collaborator

cancom84 commented Apr 4, 2024

Thanks for raising the issue, we were aware of it. From our experience working with rate structures, each customer's contract seem to be a little different from the listed rates therefore we will let the users decide what numbers to use as they can manually change the numbers within the selected rate.

@brtietz
Copy link
Author

brtietz commented Apr 4, 2024

Allowing users to enter rates make sense, there are a host of things that utilities change more frequently than the URDB gets updated, like fuel costs for natural gas. System Advisor Model takes the same approach.

For the naive or busy user who doesn't have time to look up the current rate, using rate + adjustment would have an error of 6.7% comparing the URDB value to the Xcel website, whereas only looking at rate would be off by 43%. Using rate alone is going to be biased lower than what the customer will actually pay.

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

No branches or pull requests

2 participants