Demand Response Language Clean-Up

Measure Description

The objective of this code change proposal is to clean up and clarify the existing demand response (DR) requirements so that all sections of the standards use consistent terminology and approach. The goal is to improve comprehension of and compliance with the existing requirements. The Statewide CASE Team also strives to make it easier for occupants of compliant buildings to realize the economic benefits of their buildings’ demand responsive controls by enrolling in DR programs. The Statewide Utility Team recommends improvements to the language in the Standards, Reference Appendices, Compliance Manuals, and compliance documents to:

1. Improve the clarity of the code language without changing the stringency of the standards;
2. Harmonize the demand responsive control requirements, including requirements related to the application of open or standards-based communications protocols;
3. Clarify and improve the compliance and enforcement process; and
4. Establish a foundation within the Title 24, Part 6 Standards, Appendices, Alternative Calculation Method Reference Manuals, and Compliance Manuals upon which additional measures that have load reshaping and ancillary service benefits can be added in future code cycles.

The modifications aim to align the terminology used in Title 24, Part 6 with terminology used by industry, model codes, utility programs, and other regulating bodies such as the Federal Energy Regulatory Commission and the California Independent System Operator (CAISO). Revisions also aim to provide sufficient detail on how to comply with the standards while maintaining the appropriate level of leeway to allow for continued market innovation and transformation.

Resources

The Statewide CASE Team 2019 Title 24, Part 6 Final CASE Report is available below. The Final CASE Report incorporates feedback received during utility-sponsored stakeholder meetings, Energy Commission Pre-Rulemaking workshops, and personal communication with stakeholders.

Presenations and Meetings

1. Presentation from Stakeholder Meeting on October 11, 2016 
2. Notes from Stakeholder Meeting on October 11, 2016
3. Presentation from Stakeholder Meeting on March 28, 2017
4. Notes from Stakeholder Meeting on March 28, 2017

Code Language

1. Draft Code Language, March 2017

Reports

1. CASE Study Results Report
2. Final CASE Report
3. Draft CASE Report