Topic:"Energy Efficiency Budgets" in M12768

Year PHP Load (GWh) ADC Load Shifting Differential ($M) Benefit to Other Customers ($M) 2020 875 6.6 7.3 2021 966 (16.7) 3.9 2022 957 (48.9) 3.8 2023 670 (33.6) 2.7 2024 766 (0.8) 3.1 2025 691 1.5 4.4 In response to Recommendation XIV-1 in...

AI summary The table presents annual data on PHP Load (GWh), ADC Load Shifting Differential ($M), and Benefit to Other Customers ($M) from 2020 to 2025. The data shows fluctuating values, with a notable negative differential in 2021 and 2022. The text references a recommendation from the 2020-2021 FAM Audit Report (M10416) and indicates additional context will be provided.

For the Year Ended December 31, 2025 YTD Dec $ YTD Dec MWh ELIADC in Annual FAM Report (reported on A3) $ 64,738,555 690,763 2025 ADC Adjustment (1) $ 11,022 2024 ADC Adjustment (2) $ (1,221,077) 2024 VOM Adjustment (2) $ 52,067 Power Fact...

AI summary The document provides a summary of financial and operational data for the year ended December 31, 2025, including ELIADC in the Annual FAM Report, ADC and VOM adjustments, and CBL Energy Charge details. It includes a table with data for January 2025, covering fuel and purchased power charges, operating and maintenance charges, and various adjustments and benefits.

Cause Code 2 - NDN - NSP Energy System Operator initiated ramp Down Total Billed $ 100.85 Cause Code 3 - PFL - PHP Failure to Load due to equipment or process constraints ADC $ (2.20) Cause Code 4 - PNA - PHP and NSP Agreement to new dispa...

AI summary This text details various cause codes related to energy system adjustments and billing, including ramp down events, failure to load due to equipment constraints, and adjustments related to the Active Demand Control (ADC) program. It also provides information on the total cost to serve PHP in 2025.

Extra Large Industrial Active Demand Control (ELIADC) Tariff 2025 Annual Report (NSEB M12768) NSPI Responses to BW Information Requests Request IR-3: 11 (c) As it relates to the availability of data for ELIADC Tariff administration or repo...

AI summary This document discusses a cyber incident that affected data and systems used for ELIADC Tariff administration, including impacts on PI and PortOps software, Excel files, and the temporary use of PHP meter data for billing. NS Power ER&M had to recreate trackers after the incident.

NON-CONFIDENTIAL 1 Request IR-5: 2 3 Please refer to PDF page 3, "Load Variations." Did PHP's lower-than-forecasted demand 4 increase system costs, such as through retention of higher capacity, higher reserves, greater 5 unit commitment, o...

AI summary The response to Request IR-5 explains that PHP's lower-than-forecasted demand did not affect NS Power's long-term procurement decisions, such as gas and power RFPs, as PHP load is not currently included in these decisions. The modeling in PortOps ensures PHP pays for all generation serving its demand.

Extra Large Industrial Active Demand Control (ELIADC) Tariff 2025 Annual Report (NSEB M12768) NSPI Responses to IG Information Requests 1 Request IR-1: 27 differential, when compared to previous years, was that actual fuel and purchased 1...

AI summary The document discusses NSPI's responses to information requests regarding the ELIADC Tariff 2025 Annual Report. It outlines factors that influenced the positive ADC in 2025, including fuel and power costs, load profile changes, system conditions, and tariff administration impacts.

CONFIDENTIAL (Attachment Only) 1 Request IR-5: 2 3 Reference: 2025 Annual Report, Exhibit N-1, p. 3/9, Load Variations 4 5 PHP's initial 2025 forecast totalled 811 GWh. There were revisions to PHP's 6 7 load forecast through the year, with...

AI summary The document requests clarification on PHP's 2025 load forecast, including discrepancies between initial forecasts and actual demand, the timeline for revisions, and the process for handling forecast changes. It also asks about the impact of forecast divergence on dispatch optimization and the calculation of the CBL energy charge.

2024 Annual and Regulated Financial Statements (NSEB M12227) NSPI Responses to NSEB Information Requests 1 Request IR-3: 2 3 With regards to Attachment 1, Regulated Operating Revenues, page 3 of 6: 4 5 Please provide a detailed breakdown o...

AI summary The document details a request (IR-3) from the Nova Scotia Energy Board (NSEB) for a breakdown of actual and forecasted revenues and energy sales by customer class from 2020 through 2024, including factors affecting changes in revenue or sales volumes. NSPI responded by referring to Attachment 1. The document also mentions the filing of Attachment 2 for 2025 ELIADC IG IR-15.

1 Request IR-1: 4 Response IR-1: 5 6 (a) The Energy Marketing team is staffed with seasoned employees with decades of 7 experience. Following the cyber incident, the Energy Marketing team, PHP, and the Nova 8 Scotia Power System Operator a...

AI summary The document discusses the Energy Marketing team's response to challenges faced after a cyber incident, including the use of the PLEXOS model as a temporary solution. It also mentions the lack of challenges in 2026 and the methodology used for the CBL forecast, referencing the 2025 AAR application (M11989).

Request IR-15: - (a) Please file NSPI's response to NSEB IR-3 in M12227 (2024 Annual and Regulated Financial Statements) for the purposes of this proceeding. - (b) Please produce a table for each year, 2020-2025, comparing ELIADC and Large...

AI summary Request IR-15 asks NSPI to file a response to NSEB IR-3 in M12227 and to produce tables comparing ELIADC and Large Industrial Revenues from 2020 to 2025, including energy sales and revenue metrics.

Request IR-3: Refer to the 2025 Report, section ELIADC Tariff Directives and Commitments from 2025 Proceedings, 1. 2022-2023 FAM Audit Report Recommendation XV-1, on page 7: a) Please provide an example of the overlapping, incomparable dis...

AI summary Request IR-3 seeks clarification on overlapping and incomparable dispatch results in the ELIADC Tariff Directives and Commitments from 2025 Proceedings. It includes questions about the scope of conflicting positions, model precision tolerance, load increments, modeling capabilities, and software limitations.