100 likes | 113 Views
This presentation provides a detailed review of telemetry and state estimator (SE) issues, including a timeline to resolve them. It also discusses the root cause of the issues and outlines a plan to address them.
E N D
State Estimator and Telemetry Status John Dumas / Richard Howard / Daryl Cote TPTF
Agenda • Detailed Review of Telemetry and SE issues • Timeline to Resolve • Dashboard Overview Internal
SE reporting background • To date the EDS team has communicated Convergence Percentage and MW/MVar Tolerance This metric does not illustrate the root cause of the issue..,the remainder of this presentation describes the root cause and plan to resolve the root causes Internal
SE Comparison Between Zonal and Nodal Zonal Nodal The top illustrates Zonal and the bottom represents Nodal, the selected execution for comparison is 8:36 am on Feb 28 Internal
Generation Impacts Zonal Only block loads and dc line Nodal Due to the status issues of circuit breakers and Disconnects (mostly uninitialized ones), units and loads that in reality are on-line are modeled by SE as offline. If QSEs and TSPs provide accurate status then this issue will be resolved. Internal
Measurement Availability Zonal Nodal SE uses only available data...Too many measurement are still unavailable Internal
Observable Zonal Nodal Requests have been sent on this topic.. With proper response this gap will close Internal
Measurement Quality Zonal SCADA checks the difference between measurement of one end of the line and the other. With poor telemetry SE is ignoring this data. Nodal Internal
Telemetry Data Resolution Timeline 3/5: DB Load 3/3 3/10 3/17 3/24 3/13: Service Requests due to make next DB load 3/19: DB Load Internal
Dashboard • Dashboard will be published in the EDS 2 status report for week ending 3/7 Internal