Oncor filed comments to NPRR1265, sponsored by ERCOT, to update protocols regarding unregistered Distributed Generators (DGs).
Oncor supports the protocol change and suggests modifications for clarity and efficiency.
Suggested changes include removing 'directly connected' in the DG definition, using 'distributed' instead of 'distribution', and changing capacity units from megawatts to kilowatts.
Oncor expressed concerns about the reporting workload regarding unregistered DG connected to under frequency and voltage load shed feeders.
Proposed removing certain provisions and discussing them further in working groups.
Suggested aligning submittal date of information to ERCOT with the annual DG report to the PUC on March 30.
ERCOT's response accepted 99% of Oncor's comments, adding a sentence requested by LCRA for DSPs failing to provide data.
Discussion on ERCOT following up directly with DSPs for enforcement if data obligations are incomplete.
Agreement to align reporting dates with Oncor's suggestion of March 30.
Debated retaining 'indirectly' in DG definition, settled on ERCOT's version without it.
Both Oncor and ERCOT acknowledge good collaboration leading to refined NPRR changes.
Matthew Perez from the model maintenance team discussed notification logs.
Notification logs are generated when a CR with changes on an instance attribute is submitted after another CR with a future effective date but similar changes.
The logs provide information on whether changes are being overwritten or persisting due to a future change request.
Viewing the logs: Can be seen at submission in the CR's validation and import log section. They are not accessible once the CR window is closed.
A notification log example shows device type, instance path, message, and attributes being changed.
Notification logs indicate what changes persist or are overwritten.
Handling notification logs: Update the data after the tag CR or modify the existing CR while staying within modeling deadlines and communicating with ERCOT.
Correction NOGRR or NOMCR should include descriptive language pointing to the notification log, and the log itself should be attached.
For notification logs touching certain unmodifiable attributes, submit an 'offer help' email with details and the log attached.
Withdrawal notification logs differ as the submitter cannot see them due to CR closing upon withdrawal. They attach to the tagged CR.
ERCOT monitors notification logs via a mirror server a day behind and will reach out when necessary.
ERCOT is working with Siemens to improve notification log visibility.
Action Items
Download and save the notification log upon submission.
Include notification log in correction requests.
Submit 'offer help' requests for assistance with unmodifiable attributes.
Attend follow-up discussions with ERCOT regarding process improvements.
Questions
The presentation and additional materials will be posted after the meeting.
Clarifications were made on handling the notification logs.
▶️4 - NOMCR Timeline and Inclusion on Outage Coordination Studies
Discussion on how to include model changes into outage coordination studies initiated by TSP.
Presentation of the pre-cut timeline and how modeling interacts with coordination studies presented to NDSWG.
Explanation of protocols section 3.10.1 regarding timeline for model changes.
Detail on model changes submission timeline and the new column for new generators with a 120-day requirement versus 90 days for general model changes.
Standard model change submission process highlighted, emphasizing a 90-day submission period for outage studies.
Discussion of the timeline for model validation that includes a 15-day review, followed by market model validation and maintenance.
Clarification of 'interim period two', which is the last day for model change submissions for inclusion in future scheduled models.
Explanation of establishing production model loads from submitted models and how outage coordination cases for 60 and 90 days out are derived.
Discussion surrounding the benefits of submitting into the 90-day outage coordination study.
Explanation that submitting 120 days ahead allows topology changes to be included in future model studies.
Highlight of the processing timeline from submission to inclusion in the outage schedule, emphasizing benefits of early submission.
Clarification questions were addressed regarding the interplay of model changes, outage scheduling, and timelines.
The importance of submitting changes 120 days ahead of the desired outage coordination study date to ensure inclusion and avoid rejection was reinforced.
▶️5 - NOMCR Business Change on Additional Action Required Status
Implementation of a new business rule starting from June 1, 2025, aimed at addressing last-minute submissions, benefiting both ERCOT and TSPs.
TSPs have a three-day window to respond to an 'additional action required' status on a NOMCR, subject to rejection if not addressed.
Possible extension for a further three days if additional dialogue is necessary.
Challenges highlighted in coordinating contingency and modeling group responses from TSPs.
Advocated for linking model and contingency changes to ensure smoother processes.
Emphasis on communication to avoid NOMCR rejections and maintain manageable timelines.
Discussion about filters in email servers potentially hiding important status emails from NIMS.
Clarification provided on specific language in NOMCR status emails to indicate required actions.
Mention of different status indicators like 'additional action required' and 'modeling complete'.
