RTU Communications Status and Monthly Model Update

RTU Communications Status and Monthly Model Update

Nate Butler, Supervisor EMS ApplicationsPaul Cooper, DRI RTU Communications Testing CoordinatorDRITWGApril 14, 2010

RTU Communications Testing Status

2

DDEFrame Relay

Installed

Router Installed

RTU Installed

Passed Test Mode

Passed Live Mode

Passed Dispatch

Passed Telemetry

1 Yes Yes Yes Yes Yes Yes Yes




5 Yes Yes Yes Yes Yes Yes No



8 Yes Yes Yes Yes No No Yes

9 Yes Yes Yes Yes No No No

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.

3

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.

4

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

5

Final Model Update and Dispatch Test

6

Test Date Day Event Description

04/26/2010 10:00 D-7 Update Released for Test

04/26 thru 05/03 D-7 thru D RTU Verification Period

05/03/2010 10:00 D Update of Production CFE/RTUs

05/04/2010 10:00 D+1 Dispatch Simulation

Final 05/04/2010 13:00 D+1 EMS Failure Test

05/04/2010 14:00 D+1 CFE Failure Test




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)

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

9

DR MUI – Asset Telemetry Function

Peter Friedland – Operations Solution ManagerDRITWGApril 14, 2010

Agenda

1. DR MUI Asset Telemetry Use Cases2. Preferred DR Asset Telemetry Correction Method3. DR MUI Asset Telemetry Limitations4. Questions

11

Use Case One – Normal Telemetry Corrections1. Billing Quality DR Asset Telemetry is continually

collected by the DDE’s RTU and scanned by ISO-NE2. DDE has 2.5 days following an operating day to post

corrections to DR Telemetry via the DR MUI3. ISO-NE respectfully asks that the DDE not simply

perform a bulk upload of all DR Asset telemetry for all five minute periods

4. DDE should be combing through the DR Asset data downloaded from the DR MUI and sending only the needed corrections and/or omissions

5. Extra care with review Asset telemetry at the source will dramatically reduce the possibility of billing errors and/or re-settlements

12

Use Case Two – Abnormal Telemetry Corrections1. Planned or unplanned prolonged system failure(s)

necessitate the bulk upload of missing blocks of DR Asset Telemetry data

2. DDE will review and upload missing DR Asset Telemetry with ISO-NE coordinating the overall effort for recovery

13

DR MUI Asset Telemetry Upload Limit

1. Only 500 records (five minute readings) can be uploaded in a single Web Service or XML file upload transaction

2. Multiple transactions consisting of 500 records can be submitted in succession

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

4. The DR MUI is expected to be capable of serving the DDE’s with good performance and high reliability

14

Questions

15

RTU Communications Status and Monthly Model Update

Documents

Transcript of RTU Communications Status and Monthly Model Update