When systems are migrated to PowerDash, there are some important considerations that must be addressed to ensure that the system owner does not miss out on any eligibility production.
Is PowerDash designated as the approved reporter in the given registry/agency?
Regardless of the registry/agency, whether it is NEPOOL GIS, MassCEC Production Tracking System (PTS), PJM GATS, or any other agency, PowerDash must be listed as the reporter. The procedures for changing the reporter differ depending on the agency, and typically brokers will be very familiar with the procedure for the given agency.
For many incentive programs, PowerDash will show a status in our app when PowerDash is not yet listed as the reporter in the given agency. This is one way that PowerDash helps to identify issues that impact reporting readiness, instead of leaving issues in the realm of mystery.
Until this step is completed, PowerDash will not be able to report for the system.
Is PowerDash acquiring data from the same production meter used by the previous reporter, or a different meter?
In most cases, reporting continuity will be greatly helped if PowerDash is using the same production meter as the previous reporter. Even if there has been a lapse in data acquisition, in the common case the existing production meter will have continued measuring production during that lapse in data acquisition. When PowerDash begins acquiring data from that same meter, the "odometer-style" meter reading will be able to account for all the production during the data gap.
If PowerDash is using a different production meter than the one used by the previous reporter, there will be a need for additional coordination with PowerDash to account for the period of missing meter data.
Is the reporting basis for the given registry aggregated energy totals by month (or another time period), or cumulative lifetime energy readings?
With some registries, such as NEPOOL GIS, for most programs a reporter reports each system's energy total for a given month. In such cases, there could be a need for a PowerDash to report a true-up if the previous reporter missed reporting for any months before PowerDash began acquiring meter data. Here is what PowerDash would need to know:
- the last month for which the reporter reported to the agency
- the last cumulative lifetime meter reading that was used by the previous reporter as the basis for the last reported total in the agency
With other registries, such as the Massachusetts PTS, reporters like PowerDash are reporting the cumulative lifetime reading. That scenario can really help with continuity, bridging gaps of unreported months, In these cases, the first reading PowerDash reports will account for all missed production since the previous reported reading. However, if there have been missed months, the broker/aggregator may still need to request that the agency issue a true-up to carry forward the missed production into the earliest month that is still open for reporting/minting.
How can PowerDash support these reporting transitions?
PowerDash is ready to help support you. For individual reporting migrations, you can send an email to support@powerdash.com. When we are helping with the migration of systems in bulk, whether residential or commercial, we can tailor an efficient migration approach using tools like a shared Google spreadsheet.