1 / 16

Reporting Changes for On-Peak and Seasonal Peak Assets

This announcement outlines the changes for reporting MPV data in MW instead of MWh for On-Peak and Seasonal Peak Assets in CAMS. It also introduces new methods for validating MPV using EEM data and provides instructions for uploading CSV files in EEM.

jasonterry
Download Presentation

Reporting Changes for On-Peak and Seasonal Peak Assets

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. June 29, 2016 ISO-NE Holyoke Joseph Ballantine Principal Analyst Asset Registration and Auditing Effective for Initial Settlement of June 2016 Reporting Changes for On Peak and Seasonal Peak Assets

  2. CAMS MPV Data Reported in MW

  3. Beginning with the initial settlement of June 2016 MPV data must be reported in CAMS in MW and not MWh for all On Peak and Seasonal Peak Assets For the month of June 2016 and going forward it will not be necessary to multiply the monthly MW savings for an asset by the performance hours in a month. For the final settlement of April and May continue to report MPV in MWh Seasonal Peak Assets do not report zero performance in months with zero seasonal peak hours But, the DRV for Seasonal Peak Resources will continue to be calculated per MR1III.13.7.1.5.5 CAMS MPV Data Reported in MW

  4. CAMS MPV Data Reported in MW III.13.7.1.5.5. Calculation of Demand Reduction Values for Seasonal Peak Demand Resources. Monthly Demand Reduction Values shall be established for the months of June, July, August, December, and January and seasonal Demand Reduction Values for the remaining calendar months. The monthly Demand Reduction Value of Seasonal Peak Demand Resources shall be equal to its Average Hourly Load Reduction or Average Hourly Output over Demand Resource Seasonal Peak Hours in the month. If there are no Demand Resource Seasonal Peak Hours in the months of July, August, or January, the Demand Reduction Value for those months shall be equal to: (i) the Demand Reduction Value established for the previous month if the previous month’s Demand Reduction Value was calculated using Seasonal Peak Hours or (ii) the Seasonal DR Audit results if the Demand Reduction Value for the previous month was not calculated using Seasonal Peak Hours. If there are no Demand Resource Seasonal Peak Hours in the months of June or December, the Demand Reduction Value of that resource for those months shall be equal to (i) the first applicable seasonal audit, if conducted in that month, or (ii) where there was no audit conducted in the month, the applicable previous seasonal Demand Reduction Value.

  5. CAMS MPV Data Reported in MW

  6. EEM Measure Detail Data Report Used as a Supporting Document in CAMS

  7. EEM Data as a Supporting Document in CAMS Beginning with the initial settlement of June 2016 EEM data will be accepted as the supporting documents validating the monthly MPV for an On Peak or Seasonal Peak Asset in CAMS The preferred format will be a screen shot of the EEM report page for the current market month Supporting Documents generated from other sources will continue to be accepted but ISO will be comparing the reported MPV to the EEM data ISO may request an explanation for any asset where significant differences are found

  8. New csv Upload Capability for EEM

  9. CSV Upload Capability in EEM On or about 7/1/2016 ISO will add a csv upload function to EEM A csv of the ISO specified format must be created and then using the drag and drop interface the data will be uploaded into EEM The interface does a preliminary format check and data is accepted or rejected on an all or none basis Subsequently all data is subject to the same validations as those performed when adding or modifying data through web services or the UI and data is accepted until an error is found There are instructions imbedded in the program as well as specific error messages when data is not accepted The upload capacity has been tested with up to 100 measure details and performs well

  10. Except for the date format noted above all data fields use the format identified in the Energy Efficiency Measures (EEM) Web Services Data Exchange Specificationin Section 3.9.5 Additional Value Restrictions

More Related