At the February RTF meeting, members addressed the remaining Residential HPWH measure applications that they hadn’t had time to discuss in January, those being the “Any Vintage/Any Install Location” applications. As part of a previous measure update, the RTF added a suite of measure applications representing the purchase of an efficient HPWH where the install specifics, including both the building vintage and the water heater location within the building are unknown, in hopes of supporting some emerging midstream HPWH programs where little was known about a water heater’s ultimate destination. Many of the important assumptions behind this ‘Any/Any’ measure were based purely on staff and member judgement. New data sources, since the previous update in 2018, have revealed significant differences between this ‘Any/Any’ measure and what this new data is showing with more HPWHs going into new construction and to meet energy codes than was assumed as well as significant potential for double counting between midstream and new construction programs.
Working with the Heat Pump Water Heater Subcommittee Prior to the meeting, RTF Contract Analysts came up with two paths for rethinking the applications. After much discussion, the RTF eventually voted for an approach that added UESs for above code HPWHs that are not claimed by another efficiency program and replaced the current ‘Any/Any’ measure applications with a suite of more specific UESs that will allow programs to use the RTF’s UESs like building blocks to tailor savings to their specific programs.
Recognizing that this update might impose challenges to existing HPWH programs, the RTF convened a meeting to facilitate a discussion to share ideas about how the region can effectively and efficiently implement this measure. The meeting provided an opportunity for implementers from across the region to validate each other’s challenges and share ideas for working through them, and we hope the discussion was valuable for those who participated. Those meeting materials and a summary of the discussion can be found here.