Meeting Summary - 05/20/2025 NDSWG Meeting

▶️1 - Antitrust Admonition - 9:30 a.m.

▶️2 - Oncor Comments on NPRR1265

• 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.

▶️3 - ERCOT Notification Logs

NDSWG_May20.pdf

• 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'.

▶️6 - CIM 16 Timeline Update

• ERCOT is changing the modeling application backend schema to CIM 16 format.
• This affects models for EMS, market systems, and online postings.
• Incremental files for TSPs and the layout in the MAGE application will also shift to CIM 16.
• ERCOT is collaborating with a vendor to convert from CIM 10 to CIM 16 database.
• A quarter three or four workshop will introduce the CIM 16 model and schema changes to the public.
• Workshop will be half-day and potentially part of a series.
• MOTE system will transition to CIM 16 by February, enabling participants to test CIM 16 modeling processes.
• CIM 16 training will be provided in the MOTE system within the same quarter.
• Database migration expected to occur in Q2 2027, with no double modeling in CIM 10 and 16.
• MOTE system is a market test environment including a MAGE test setup.
• Citrix likely to be used for MOTE access due to potential version complications.
• Schema sharing for DSPs is being considered, possibly via an OWL or UML diagram accompanying the workshop.

▶️7 - Manual Contingency Review

• Finish up on double circuit contingency and move to manual contingency review.
• Emails with specific database loads for every TSP will be sent out in June.
• Submit manual contingency corrections based on allocated production loads.
• Reminder for DPC CAMRs to submit after receiving the modeling completed email notification.
• Ensure actions are taken promptly to avoid delays.
• Discussion on NPRR1234 categories for loads over 25 megawatts; currently in draft.
• Encouragement to submit more standard submissions rather than interim updates.
• Request for interim updates breakdown between monitor and camera not currently available.
• Encouragement to adhere to the outside 90-day timeline for model changes submissions.
• Positive feedback on discussions regarding SCR831 and NPRR1265, with no objections to moving forward.

▶️8 - SCR831

• Discussions on previous concerns about the burden of SCR831 but no formal comments submitted.
• Plan to have a joint meeting with SPWG and SSWG on June 9 to discuss common concerns.
• Emphasis on internal discussions within each working group before the joint meeting to avoid delays.
• Focus on upgrading the software to handle sequence data, improving process efficiencies, especially for those handling multiple roles.
• Intent to improve case quality for the model between planning and protection.
• It's confirmed that adding short circuit information isn't a significant change.
• Remembered that sequence data already exists in models, and SCR will update software to include additional needed data.
• Importance of conversations within working groups to address any aspects not resolved.
• Plan to discuss templates and additional information needed after the joint meeting.
• Clarification that implementing SCR831 would take 1-2 years post-approval for software updates.
• Next discussion on this topic scheduled for the NDSWG meeting on June 17.

9 - Adjourn