Skip to content

Embedded cost-of-service analysis for ri_hp_rates #72

@jpvelez

Description

@jpvelez

What

Perform an embedded cost-of-service analysis for HP vs. non-HP customers in Rhode Island, as aprt of the ri_hp_rates report. The methodology for how to do so are in @sherry's write up from R2-11, which is available here, namely in sections 2.3.3, 2.3.4, and 2.4.

Why

Even though marginal cost-of-service-based approaches to measuring the cross-subsidy that likely exists between HP and non-HP customers in RIE's territory make more sense, Rhode Island is an embedded cost-of-service state, so we'll need to show the what it means to do this comparison and cost-of-service terms, in order to explain why it is incomplete.

How

  • Read sections 2.3.3, 2.3.4, and 2.4 of the RI methodology write-up
  • Write a quick notebook that quantifies what percent of RI bldgs in 2024.2 upgrade 0 have heat pumps, if any
    • If none do, we'll likely need to construct a mixed upgrade scenario where 99% of customers are on upgrade 0, and 1% of customers are randomly selected to be on upgrade 2 (medium performance cold-climate ASHP)
  • Clarify and document the full methodology (assuming 2024.2 resstock data) in sufficient detail to 1. get validation from @sherry and 2. be unblocked for implementing the analysis via polars in a quarto notebook
  • Produce a polars quarto notebook that compares the embedded cost-of-service of HP and non-HP customers
    • The notebook should assume the reader knows a little python and polars, but otherwise holds the readers hand through the data prep and computations, perhaps using LaTeX formulas where it makes sense to tie to Sherry's write-up. (Later on, this will be that basis for the corresponding section of the report's Data & Methods section.)
    • The notebook should write-up the key results and any complementary analysis that is performed (Later on, this will be that basis for the section of the ri_hp_rates report on the emedded cost of service analysis, which will be written by @jpv .)

Deliverables

  • UPDATE ME

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions