NatLabRockies / NatLabRockies/SAM

Allow compensation rate within TOU tiers

Open
#2,117 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
486
Forks
219
Avg merge
10h 10m
Merged PRs (30d)
2

Description

Is your feature request related to a problem? Please describe.

SAM currently only allows a flat compensation rate that applies for net metering. From the documentation:

For the purpose of annual net excess compensation, monthly excess generation is calculated from the monthly total generation and load, regardless of time-of-use (TOU) periods.

PECO has net metering, but on their TOU rate plan, the annual cash out is done at the "price to compare" within each TOU tier. See https://www.peco.com/cdn/assets/v3/assets/blt1b5616c79bacadb4/blte7bf67602d7799ef/64cb648f5b39c52180713adf/S1-Solar_Net_Metering_Time_of_Use_10212021.pdf?branch=prod_alias.

Describe the solution you'd like

It would be helpful to be able to specify the compensation rate within the same tiers that are used for electricity charges from the grid. SAM seems to already bank everything separately, so I hope this would be a straightforward improvement.

Describe alternatives you've considered

Using one of the other compensation types (e.g. net billing or net metering with $ credits), but I don't see a way to accomplish it (at least certainly not simply).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are identified. Start by locating the net-metering compensation and TOU-tier handling, then compare how annual cash-out rates are selected. Done means compensation can be specified per existing TOU tier without changing other compensation modes.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.