Instruction for How to Self Report Data

on November 18, 2014 M-RETS® News & Events, Training, Uncategorized and Tags: with 0 comments

The following procedures will instruct M-RETS Account Holders on:

  • Registering M-RETS Projects with a Self Reporting Reporting Entity
  • Data Reporting
  • Data Approval Timelines and REC Issuance

All questions about your M-RETS account can be directed to Bryan Gower 408-899-3340

 


Registering M-RETS Projects with a Self Reporting Reporting Entity

Who can self report data for an M-RETS Project?

A Reporting Entity is (1) the control area operator, interconnecting utility, scheduling coordinator, or an independent third-party meter reader and is not affiliated with the owner of the generator for which the entity is reporting; (2) the control area operator or interconnecting utility and that is affiliated with the generator owner, but having sufficient segregation of duties such that the person performing the Qualified Reporting Entity duties does not have access to transfer or retire Certificates created for that generator or (3) Self reported for projects that are under 150 kw

Small generators with a nameplate capacity less than or equal to 150 kW or generators using Distributed Generation Aggregation may opt to be treated as a Self-Reporting Generator. (OP 7.7)

 

How do I register my M-RETS Project as self reporting?

When registering an M-RETS Project, designate the Self Report option in the Reporting Entity drop down located in the  ‘Reporting Entity, State/Provincial/Voluntary Admin Access, and Sub-Account Assignment’ section on the first page of the Project Registration screen.

selfreport

 

Data Reporting

When can data be self reported?

A Self-Reporting Generator must enter actual cumulative meter readings measured in either kWh or MWh and the date of the meter reading via the Self-Reporting Interface. Actual cumulative meter readings must be entered no less frequently than annually. Self-Reporting Generators that do not enter meter readings via the Self-Reporting Interface as required will receive a reminder notice from the M-RETS Administrator. Any such generator not entering a cumulative meter reading within 30 days of receipt of such a notice may be deemed inactive by the M-RETS Administrator. If and when a Self-Reporting Generator’s Generation Activity Log is reactivated, the next meter read shall be the new baseline for accumulated generation data.A Self Reporting Generator must have its cumulative hourly meter readings verified by a Third Party Verifier or Qualified Reporting Entity, not less than annually(OP 7.8 and 7.6)

 

How will the data be reported?

Data will be reported to M-RETS using one of 2 methods:

      1. CSV file loaded into the Meter Data Loading Module
      2. Loaded directly into the Asset Management Module’s Review Data/Self-Report column

CSV file loaded into the Meter Data Loading Module

The account holder should locate the Meter Data Loading module to upload the CSV file. To locate the desired generation output file, the reporting entity selects the Meter Data Loading module’s “Browse” button to display a pop-up screen where the user can locate the desired file on computer or network drives. After selecting a file, the user selects the “Upload Now” button to upload the file.

Reporting Entity 3

A current period output file can be loaded as many times as needed within the 69 day window for that period’s certificate creation adhering to the four rules as listed below:

Data Reloading Rule Description
Rule 1, reloading data when the existing data is already “Account Holder Accepted” After an Account Holder has explicitly accepted the posted output data, if a file of the same, or different, data is reloaded, M-RETS will reject the data and notify the reporting entity that data for this unit has already been accepted. The status of the existing data will not change.  To override this rule, see rule 4 below.
Rule 2, reloading data when the existing data is “M-RETS Accepted” or “Account Holder Disputed” Reloading the data file will overwrite any data that was previously loaded for that unit and set the new data status to “M-RETS Accepted”.
Rule 3, reloading data when the existing data is “M-RETS Administrator Accepted”, “M-RETS Administrator Disputed”, or “M-RETS Admin Adjusted” If a file of the same, or different, data is reloaded, M-RETS will reject the data and notify the reporting entity that this unit’s data is either “M-RETS Admin Accepted”, “M-RETS Admin Disputed”, or “M-RETS Admin Adjusted” and therefore cannot be accepted. The status of the currently posted data will not change.  To override this rule, see rule 4 below.
Rule 4, data file reloaded by the M-RETS Administrator The reloaded data will overwrite all previously loaded data for this unit regardless of its current status

 

 

Data loaded directly into the Asset Management Module’s Review Data/Self-Report column

      1.   Locate the Asset Management module and select the Self Report or date (JAN 14) hyperlinkselfreport2
      2. Select the Add New Month to add a new month of generation or Add Adjustment to load adjustment dataselfreport3
      3. From the user interface, select the Vintage and complete the MWh and and Begin and End date (MM/DD/YYYY) fields selfreport4

 

How will the CSV file be created?

The CSV File can be created in Excel or Notepad. Programs (like Excel) that add formatting may reformat date fields which will result in errors when loading the file. Errors can be forwarded to the M-RETS Administrator with a screenshot and a copy of the file if assistance is needed in troubleshooting errors.  The data shall be in ASCII Text with data fields delimited by commas (Comma-Separated Value – CSV or TXT format).  The Generation file has the following general structure:

<column1Name>,<column2Name>,…

<column1Value>,<column2Value>,…

If the Column Name(s) and Value(s) do not conform with the above specification, the application will indicate a fatal error and the file will not be loaded.

The following example shows a conforming input file.

QRE CSV EX

 

How will the data be collected?

The data must be electronically collected by a meter data acquisition system, such as a MV-90 system, or pulse accumulator readings collected by the control area’s Energy Management System, and verified through a control area checkout/energy accounting or settlements process which occurs monthly. The preferred source for the data is a meter data acquisition system. If the control area does not have an electronic source for collecting revenue meter data, then manual meter reads will be accepted.

Inverter data, PVWatts estimates or calculations are not accepted sources of data

 

What validations will M-RETS perform when a file is loaded?

Before generation output data is posted to any M-RETS databases, the system performs the following validations:

Validation Type Description Failure Result
Reporting Entity validation Is the reporting entity designated to report output data for the generating unit, as classified by the Account Holder in the generating unit’s registration information? System rejects data, sends reporting entity an error message that they are not designated to report on this generating unit, and creates an Exception Report for M-RETS Administrator review.
Engineering Feasibility Assessment As described on the next page, feasibility is determined using a formula that includes the amount of generation reported (MWh), the duration (begin/end), the nameplate capacity, and the capacity factor. Soft-warning to the reporting entity that the MWh have failed the Engineering Feasibility for the generating unit. The reporting entity is allowed to continue posting the data, but it will remain in a pending state. Both the M-RETS Administrator and the Account Holder will be notified of the failed feasibility estimate.  Before the data can become eligible for Certificate Issuance, the M-RETS Administrator will require the Account Holder or QRE to submit the hourly metering readings or settlement system reports as available.
Begin/End Duration overlap/gap check For the duration of generation (Begin MM/DD/YYYY and End MM/DD/YYYY), are there gaps or overlaps from the data reported for the previous reporting period? System rejects the data and sends an error message to the reporting entity that the duration reported for this unit has either gaps or overlaps from data reported for a previous reporting period.  Either error message will be specific to the problem – one message for a gap, and another for an overlap.
Multiple Units aggregated to this meter flag – Y/N Does the unit being reported on share its meter with multiple units? If No, proceed with other validations. If Yes, see description to the right. M-RETS will write the data to the database for the Primary Generating Unit.  At Certificate Creation, and assuming the data is not disputed, M-RETS will divide the amount of reported generation by the number of units sharing the meter (or allocated by percentage specified by the Account Holder) and then process the data individually for each unit.
Current Status of any previously loaded data If data was previously loaded for the units in the file, what is that data’s current status? See Rules 1-4 on the previous page

Data validation is performed for both current period reporting and prior-period adjustment reporting, regardless of whether the data is loaded as a file or entered manually in the unit’s Self-Reporting screen. To determine the feasibility of the submitted data, M-RETS will use the following equation:

 (nameplate capacity) * (capacity factor) * (number of hours in the duration) * (1.02)

The number of hours in the duration is based on the duration of the generating period each time the information is reported on the generating unit.  To determine the duration value, M-RETS will calculate the number of hours in the generating period (for example, the number of hours in the generating period with a Begin Date of January 1, 2006 and an End Date of January 31, 2006 would be 744).  The 1.02 will allow for a margin of error.

If the validation is successful, the data is loaded into the database, and becomes available to the Account Holder to review and then accept, or dispute. If the data is accepted, it will be included in the certificate issuance cycle for the relevant reporting period. For prior-period adjustments, the data will contribute to the next certificate issuance after it was accepted (either by the Account Holder, or auto-accepted by M-RETS).

If the loaded data fails the Engineering Feasibility validation, the reporting entity will be prompted with a ‘soft’ warning as to the failed validation.  The reporting entity has the ability to continue posting the data by selecting the “continue” button on this pop-up screen, and if so wishes to continue posting data, M-RETS will send an automated email to both the M-RETS Administrator and the Account Holder that the data loaded for their generating unit has failed the Engineering Feasibility validation, but that the Reporting Entity has decided to have the data posted to the database anyway.  The notification will also state that the data has a status of “M-RETS Pending” until either corrected, or approved by the M-RETS Administrator. Data with this status will not contribute to Certificate Creation.  The reporting entity can also decide to not have the data posted to the database as a result of the failed validation by selecting the “cancel” button on this same pop-up screen.  Selecting cancel will discontinue the data loading process for the unit in question and no notifications will be sent.

 

Data Approval Timelines and REC Issuance

When will certificates be issued?

The M-RETS Administrator will issue one electronic Certificate for each MWh of energy that is generated by those generation units that are registered with M-RETS. Certificates will be issued based on the number of whole MWhs on the Generation Activity Log on the day of Certificate creation. (M-RETS Operating Procedure 10.1)

As soon as the generation data is received by the M-RETS Administrator and a data validity check is performed, the data will be posted on the generator’s “Generation Activity Log”.  The generation posting will be marked “M-RETS Accepted” on the Generation Activity Log. Once the generation is accepted by the Account Holder, the generation posting will be marked “Account Holder Accepted.”  Certificates will be issued on T2 + 7 days, where T2 is the day the generation posted is accepted by the Account Holder.  No changes will be allowed to the generation MWh data for seven calendar days prior to the M-RETS Certificate creation. (M-RETS Operating Procedure 10.3)

 

What happens when the data fails the Engineering Feasibility Calculation?

If data entered exceeds an estimate of technically feasible generation, M-RETS Administrator will be notified and the generation will be posted to the Generation Activity Log with a status “M-RETS Pending” until resolution is reached. If the data is in an ‘M-RETS Pending’ status at the time of issuance, the data will be zeroed out from the generation activity log.

Projects that have data that fails the M-RETS Engineering Feasibility Calculation will be reviewed by the M-RETS Administrator to confirm the Capacity Factor, Maximum Annual Energy and Nameplate Capacity is registered correctly. The M-RETS Administrator will recommend adjustments to the project registration if needed. The M-RETS Account Holder should forward the meter readings to the M-RETS Administrator to verify the reported generation.