1 / 15

RTU Communications Status and Monthly Model Update

This update provides the testing status and results for the RTU communications, including model updates and validation testing. It also outlines upcoming testing activities and discusses asset telemetry processing. Questions about the DR MUI asset telemetry function are addressed.

washingtone
Download Presentation

RTU Communications Status and Monthly Model Update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. RTU Communications Status and Monthly Model Update Nate Butler, Supervisor EMS Applications Paul Cooper, DRI RTU Communications Testing Coordinator DRITWG April 14, 2010

  2. RTU Communications Testing Status

  3. April Test Results • Model updates and validation testing went very well. • 8 RTUs participated. • FTP site was used to distribute the XML files. • 8 RTUs were able to successfully pass validation. • Dispatch testing • 6 RTUs participated. • 4 RTUs successfully pass dispatch test. • Audit testing • 6 RTUs participated. • 4 RTUs successfully pass audit test.

  4. Upcoming Testing • Continued Testing of Dispatches • Simulated Dispatches • Simulated Audit Dispatches • Final End-to-End Testing • April 26 thru May 7 • Final Test of Configuration/Model Update • Dispatch/Audit Test • Simulated Asset Telemetry • Failure Mode Testing • DRMUI in Sandbox Environment • Participation is Required • Servers used in testing will be converted to production configuration after test.

  5. Failure Mode Testing • Will simulate an audit dispatch then test each failure mode • Modes: • EMS Failure - May 4 @ 1pm • No output changes • Gap in asset telemetry data • Fill in missing data using DRMUI during test period • CFE Failure - May 4 @ 2pm • Loss of connection and stalled heartbeat signal • Gap in asset telemetry data • Fill in missing data using DRMUI during test period • RTU Failure - Schedule with Paul Cooper • Backend Failure - Schedule with Paul Cooper

  6. Final Model Update and Dispatch Test

  7. Dispatch MW Processing • Dispatch MW (DPMW) is the amount to reduce total consumption. • Generally: • Loads reduce consumption. • Emergency generation increases output to offset consumption. • Total MWh for all of the assets associated with that resource is expected to decrease by DPMW. • NetMW (NTMW) = sum of asset loads (LDMW) – sum of emergency generation (EGMW)

  8. Asset Telemetry Processing • Asset telemetry values should be KWh values. • KWh = (KW used over 5 minute period) x 12 • The ISONE CFE scales the values to MWh (= KWh / 1000). • Asset Telemetry Data will be processed using the timestamp of when the value was changed in the RTU. • As long as that timestamp falls within the 5 minutes following the time period being measured, it will be associated with the previous 5 minute period. (Ex: 09:00:00 for 09:05:00 < Timestamp <=09:10:00) • The 5 minute periods will be designated in the MUI using the start time of the interval.

  9. Questions

  10. DR MUI – Asset Telemetry Function Peter Friedland – Operations Solution Manager DRITWG April 14, 2010

  11. Agenda • DR MUI Asset Telemetry Use Cases • Preferred DR Asset Telemetry Correction Method • DR MUI Asset Telemetry Limitations • Questions

  12. Use Case One – Normal Telemetry Corrections • Billing Quality DR Asset Telemetry is continually collected by the DDE’s RTU and scanned by ISO-NE • DDE has 2.5 days following an operating day to post corrections to DR Telemetry via the DR MUI • ISO-NE respectfully asks that the DDE not simply perform a bulk upload of all DR Asset telemetry for all five minute periods • DDE should be combing through the DR Asset data downloaded from the DR MUI and sending only the needed corrections and/or omissions • Extra care with review Asset telemetry at the source will dramatically reduce the possibility of billing errors and/or re-settlements

  13. Use Case Two – Abnormal Telemetry Corrections • Planned or unplanned prolonged system failure(s) necessitate the bulk upload of missing blocks of DR Asset Telemetry data • DDE will review and upload missing DR Asset Telemetry with ISO-NE coordinating the overall effort for recovery

  14. DR MUI Asset Telemetry Upload Limit • Only 500 records (five minute readings) can be uploaded in a single Web Service or XML file upload transaction • Multiple transactions consisting of 500 records can be submitted in succession • ISO-NE IT Department has been spending considerable time stress testing (simultaneous users, 1000’s of Asset updates, etc) the DR MUI with respect to the Asset Telemetry upload function • The DR MUI is expected to be capable of serving the DDE’s with good performance and high reliability

  15. Questions

More Related