1 / 8

RTU Communications Status and Monthly Model Update

RTU Communications Status and Monthly Model Update. Nate Butler, Supervisor EMS Applications Paul Cooper, DRI RTU Communications Testing Coordinator DRITWG March 19, 2010. RTU Communications Testing Status. March Test Results. Model updates and validation testing went very well.

simeon
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 March 19, 2010

  2. RTU Communications Testing Status

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

  4. Upcoming Testing • Model Update Test • Looking for input on scheduling. • Continued Testing of Dispatches • Simulated Dispatches • Simulated Audit Dispatches • Test Message? • End-to-End Testing • Configuration/Model Update • Dispatch/Audit Test • Simulated Asset Telemetry • DRMUI in Sandbox Environment • Participation is Required • Servers used in testing will be converted to production configuration after test.

  5. Updated Communications Spec 1.2 • DR Communications Specifications version 1.2 issued • In the communication tables: • Replaced MIDD with NCSO. • Replaced MIDC with DTMC. • Fixed inconsistency in dispatch/test flag. • Message ID’s were considered redundant since the dispatch time (DTIM) is already unique. • Participants should feedback DTIM in DTMC after receiving a new dispatch. • Modified the “Dispatch Instruction Feedback Performance Requirements” to show how these changes will affect dispatch processing.

  6. Production/Dispatch Test Information • In the dispatch tests, not all resources were dispatched at the same time. • Attempt to provide a more realistic test. • Timeline used in recent dispatch tests: • All load resources were dispatched to full capability. • All emergency generation resources were dispatched to full capability. • All emergency generation resources were dispatched to 0. • All load resources were dispatched to 0. • Distributed spreadsheets showing which resources in the test database were load resources and which were emergency generation resources.

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

  8. Questions

More Related