PEAK’s RMTNET Tool Sarma (NDR) Nuthalapati, Principal NetApps Engineer Hongming Zhang, Manager Network Applications Matt Veghte, Lead, Real-Time Operations Engineer Malvika Patil, Real-Time Operations Engineer Jesse Parker, Real-time Operations Engineer PEAK Reliability RC User Group Meeting 3rd May 2018

Introduction RMTNET (Real-time Multi Timepoint Network Analysis) Basecase and Contingency analysis Several hour ahead studies based on Equipment Outages/Innages Load Forecast Unit Commitment Net Interchange Multi-point study/STNET in auto pilot mode Runs every 15 minutes

Introduction RMTNET (Real-time Multi Timepoint Network Analysis) Basecase and Contingency analysis Several hour ahead studies based on Equipment Outages/Innages Load Forecast Unit Commitment Net Interchange Multi-point study/STNET in auto pilot mode Runs every 15 minutes Equipment Outages/Innages Coordinated Outage System (COS) Balancing Authorities (BAs) are expected to require Generator Owners (GOs) and Generator Operators (GOPs) to communicate outages to BAs Transmission Operators (TOPs) are expected to require Transmission Owners (TOs) and BAs to communicate outages to TOPs

Introduction RMTNET (Real-time Multi Timepoint Network Analysis) Basecase and Contingency analysis Several hour ahead studies based on Equipment Outages/Innages Load Forecast Unit Commitment Net Interchange Multi-point study/STNET in auto pilot mode Runs every 15 minutes Load Forecast Real-time Loads are archived into PI system for every State Estimation Run Forecast the load data for next few hours based on the historic load data (which is saved PI) Forecast every 15 minutes

RMTNET Main Display-Intro 1-Periodicity, Time of Study, etc. 2-RMTNET Sequence and Status 3-RMTNET Process Status

RMTNET Main Display-Set up Study Setup-1 Study Setup-2 Study Setup-3

RMTNET Main Display-Input Data Review Study Setup

RMTNET Main Display-Input File Setting Input File Options

RMTNET – External Data Files Display has Equipment External Name showing the COS ID for the outage.

RMTNET Alarms-Categories BASECASE Alarm At least one Timepoint results in INVALID Solution Violation Alarm Contingency Analysis for a Timepoint has some violations Only shown in the display (not logged) Auto-acknowledged and auto-deleted Will be configured as logs

RMTNET Alarms-Categories BASECASE Alarm At least one Timepoint results in INVALID Solution Violation Alarm Contingency Analysis for a Timepoint has some violations Only shown in the display (not logged) Auto-acknowledged and auto-deleted Will be configured as logs

Monitoring RMTNET Status on Network Online Sequence Display Coming soon !

RMTNET – Results

RMTNET – Results Start time, Completed time Timestamps for current and future hours Violations in the basecase Violations for contingency The numbers in each TAB: Indicates the total number of respective outages. Clicking on each tab (with numbers) will provide the details of the outages.

RMTNET – Results Start time, Completed time Timestamps for current and future hours Violations in the basecase Violations for contingency The numbers in each TAB: Indicates the total number of respective outages. Clicking on each tab (with numbers) will provide the details of the outages.

RMTNET – Results Start time, Completed time Timestamps for current and future hours Violations in the basecase Violations for contingency The numbers in each TAB: Indicates the total number of respective outages. Clicking on each tab (with numbers) will provide the details of the outages.

RMTNET – Results

RMTNET Results in iGrid Display RMTNET results in iGRid is set up to only display results for timestamp T+1 and T+2. The results for timestamp T will be more or less the same as RTCA so any issues there will be taken care of in real-time by the RCSOs.

RMTNET Usecases – Impact of a future outage (2nd Jan 2018) The RMTNET results indicated blank results. The ROE recognized this condition (without alarms) and proactively investigated the situation and found it was caused by a future outage. This resulted in updating a COS entry that had the wrong breakers and identifying a missing 69kV transmission line in model. Later when outage was actually taken, the RTCA basecase became unsolved due to this condition and was immediately resolved (since the problem was known hours in advance).

RMTNET Usecases – Impact of a future outage It was observed that no results were generated for timepoint 3 starting with the 08:18 run (for 0830, 0930, 1030); no results were generated for timepoints 2 and 3 starting with the 09:19 run (for 0930, 1030, 1130); and no results were generated for any of the three timepoints on the 10:18 run (for 1030, 1130, 1230). On checking Analyst displays RMTNET Message log, there were messages indicating that the basecase was unsolved for timepoints 2 and 3. From this information it seemed to make sense that there was an outage starting at or around 10:30 that was causing the basecase to go unsolved. Sure enough, the os_EMS file had one outage at COPCO2 (COS ID: 1-00531191) which started at 10:30AM and this was the root of the issue. From this information it seemed to make sense that there was an outage starting at or around 10:30 that was causing the basecase to go unsolved. Sure enough, the os_EMS file had one outage at COPCO2 (COS ID: 1-00531191) which started at 10:30AM and this was the root of the issue.

Work in Progress RMTNET-ECC File Generator RFG Project Load Forecast Unit Commitment data PI Trends for Path flows forecasted in RMTENT Use of Forced Outage Detection (FOD) results to fine tune RMTNET

Summary Real-time Look ahead Studies (Real-time Multi Timepoint Network Analysis) Equipment Outages/Innages Load Forecast Unit Commitment Net Interchange Proactive in identifying potential issues due to forthcoming outages, etc., Helps to forecast path flows Sarma (NDR) Nuthalapati snuthalapati@peakrc.com