Meeting Summary - Requirements for REP and TDSP Data Submission to ERCOT in Conjunction with PUCT Rule 25.186- 04/01/2025 Workshop

▶️1 - Antitrust Admonition

• Participants are encouraged to review the NPRR document on their own and provide feedback.

▶️2 - Background

ERCOT-Workshop-to-Address-Requirements-for-REP-and-TDSP-Data-Submission-to-ERCOT-in-Conjunction-with-PUCT-Rule-25.186.pdf

• The discussion is about a legislative and substantive rule requirement involving ERCOT, TDUs, and REPs regarding smart responsive appliances or devices.
• Definition of a smart appliance/device: Allows electric usage to be adjusted remotely.
• Participants in these programs cannot participate in ERS or TDSP load management programs.
• REPs must submit data to ERCOT within 45 days after each calendar quarter end.
• Data submission includes ESI ID, participant data, event list, specific dates, start/stop times, and ESI IDs involved.
• ERCOT’s filings with the commission are public and aggregated, ensuring no individual REP activities are revealed.
• Data from REPs is treated as protected information.
• The rule provides for funding, with some TDSP programs announced for funding smart thermostats.
• Discussion and questions encouraged, with a focus on residential customers.
• Clarified that large loads, like crypto loads, are not included; only residential customers are addressed.

▶️3 - Data Submission

• Initial plan for data submission was introduced.
• The presentation included a next slide prompt indicating a continuation or an overview of the plan.

▶️3.1 - Initial Plan

• ERCOT will continue using its secure file sharing application introduced last year instead of Proofpoint.
• Entities submitting data must notify ERCOT to be added to the share list, as only ERCOT can add individuals.
• Suggestion made to use a generic email address for data submissions, similar to drsurvey@ercot.com.
• First data submission deadline for ERCOT is May 15, covering the first quarter of the year.
• Reps and TDSPs are required to submit data 45 days after each calendar quarter ends.
• Positive confirmation required from reps or TDSPs not engaged in demand response programs; no response does not equal no participation.
• Coordination required between ERCOT and TDSPs for load management program data submissions.
• Discussion on whether to align TDSPs data submission schedule with that of REPs or ERS team was highlighted.
• Preference expressed for data submission 45 days post-quarter end to maintain synchronization.

▶️3.2 - Long Term Plan

• Continuation of using secure file share option for data submission while introducing data exchange via the NAESB process.
• NAESB process requires bureaucratic approval and system changes; can't be implemented for initial submissions.
• Incorporation of the NPRR to initiate development work at ERCOT for NAESB data exchange.
• Seeking feedback to incorporate in NPRR before submission.
• Proposal to conduct residential smart devices survey quarterly, differing from the annual DR survey.
• No need to report ESI ID data for direct load control program if already reported under smart device participation.
• Additional information required in new survey format compared to previous data collection.
• Quarterly submission still required to notify ERCOT of non-participation in programs.
• Provision of sample files for detailed information required, available in PowerPoint and NPRR.
• Submission format: CSV file, not Excel; involves two-way file exchange.
• Clarification that reps do not need to submit ESI IDs already reported by TDSPs; flagged as errors otherwise.
• TDSPs are required to report specific ESI ID participation details including duration.
• Detailed reporting required for thermostat programs, with emphasis on ensuring no overlap in reporting by reps and TDSPs.
• Long-term plan includes NAESB addition for data exchange.

▶️4 - Draft NPRR

NPRR Changes to Address PUCT Rule 25.186 REP Data Reporting and Validation

• File naming conventions for submissions and response files are similar across all submissions.
• Distinguishing feature in file naming is the report name field.
• Three sets of file reports: RDP participant, events-specific file format, and TDSPs for load management.
• TDUs are responsible for thermostat programs where reps do not manage signals or rebates.
• Clarification on TDSP funding: smart devices funded by TDSPs can participate in the program intended to increase thermostat adoption.
• Reports are more about collecting and providing data rather than implementing a program.
• Reporting data is required for compliance with ERCOT and PUCT rules.
• Program aimed at increasing residential demand response; no penalties for not meeting goals.
• Aggregate data reporting is required; not individual rREP-level data.
• Reports required from all reps every quarter, similar to an annual DR survey but targets all reps.
• Both CR reps and TDSPs are required to report quarterly.
• ERCOT will cross-reference submissions from reps and TDSPs to ensure compliance.
• Reporting rule strictly applies to residential programs.
• Quarterly data submission is required 45 days after the end of each quarter.

▶️4.1 - REP Participation Data

• Data requirements for participation: ESI ID, start date, and stop date.
• Guidelines for stop date if customer is still participating at the end of the quarter.
• Clarification on handling non-continuous periods of participation by entering separate rows.
• Discussion on whether residential batteries should be included in reports along with other smart devices like thermostats.
• Potential inclusion of battery charging in reporting, pending further talks with PUCT staff.
• Clarification needed on ADER pilot reporting and its overlap with REP smart device program.
• Validation of start and stop dates specifically for each reporting quarter, with leniency on previous records.
• Response file format upon submission, including original report ID for NAESB submissions.
• Explanation of error messages including invalid ESI ID, not being REP of Record (ROR), invalid dates, overlapping dates, and duplicate rows.

▶️4.2 - REP Event Data

• Discussion about specific data requirements for the ESI ID, including event deployment details, device type, and opt-out information.
• Importance of refining data collection to address issues not covered by the annual DR survey.
• Emphasis on handling multiple deployments per day and multiple rows for customers with more than one device.
• Consideration of adding battery devices and other significant device types to the list.
• Clarification of different types of errors in the system, specifically NAESB ER3 type errors which are logic-based, versus formatting errors which are ER1 and ER2.
• Identification of issues such as invalid event dates, ESI IDs, and device type codes affecting data validation.

▶️4.3 - TDSP Participation Data

• If participation extends beyond the calendar quarter reported on, code the last day of the quarter.
• If participation varied throughout the quarter, use multiple rows to reflect changes.
• Clarification was provided on when TDSP should include ESI ID in their reports, particularly when performing remote calls.
• There is a requirement to report participation regardless of program deployment status.
• TDSPs should report the dates participants were on the program, including when they were tested and removed.
• The TDSP response file follows the same pattern as the rep response file.
• The discussion included potential errors in reporting and the format of error rows.

▶️5 - Stakeholder Feedback

• Suggestion to send a file of ESI IDs to representatives to reduce errors in the annual Doctor survey.
• Melissa Lauderdale from Gexa Energy showed interest in the ESI ID list.
• Discussion on the discomfort around providing a home battery and the relevance of a DG profile for identification.
• Questions raised about the inclusion of residential batteries in ERCOT reporting.
• Clarification on reporting requirements for TDSPs and co-ops.
• Discussion on data submission deadlines and forms specified by ERCOT.
• Concerns raised about the scope of reported data, focusing on direct load control programs rather than peak rebate programs.
• Introduction to new data collection requirements and feedback on the initial submission deadlines.
• Clarification provided by ERCOT legal team on the current and future data submission process.
• Stakeholders expressed a need for focusing initial reports on smart thermostats.
• Acknowledgment of a potential need for adjusting report content once more data is available.
• Confirmation that customer ESI ID lists will be used for report validation.
• Discussion on TDSP reporting requirements and their implications for ERCOT data collection.
• Emphasis on the collaborative aspect of the process and the alignment with other ongoing projects.

6 - Adjourn