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

Consider improvements to Electricity Purchases input page #179

Open
cpaulgilman opened this issue Dec 5, 2024 · 0 comments
Open

Consider improvements to Electricity Purchases input page #179

cpaulgilman opened this issue Dec 5, 2024 · 0 comments

Comments

@cpaulgilman
Copy link
Collaborator

SAM's Electricity Rates page was originally designed for behind-the-meter (BTM) financial models to calculate bill savings = bill without system - bill with system.

As of SAM 2017.9.5, we added electricity rates to the front-of-meter (FOM) financial battery configurations to better account for the cost of charging batteries. This proved to be useful for accounting for PV inverter night-time consumption, and for CSP parasitic losses as well. Now, electricity rates were being used to calculate an operating cost instead of bill savings.

For SAM 2020.11.29 r2, we changed the label for FOM configurations from "Electricity Rates" to "Electricity Purchases" to make it clearer that the retail electricity prices are to calculate the cost of purchasing electricity.

For SAM 2024.12.12, we added Single Owner and Commercial financial model options to the industrical process heat (IPH) configurations that generate heat and consume some electricity.

This issue is to review the implementation of the "Electricty Purchases" input page in the user interface to see if it can be streamlined to make it easier to add to future configurations for both BTM And FOM applications, taking into consideration the need to remain consistent with the Utility Rate Database (URDB) API.

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

1 participant