Requirements and Limitations

The following data requirements and limitations apply to utilities and customers using the Flat Rate Load Shifting Report emails. These requirements must be met for a utility and a customer to participate in the program.

Utility Requirements and Limitations

This list specifies the utility requirements and limitations:

  • Required Cloud Services: Oracle Utilities Opower Load Shifting, Rate Coach

Customer Requirements and Limitations

This list specifies the customer requirements and limitations:

  • Billing Frequency: Monthly or bi-monthly.
  • Data Delivery Frequency: Daily. Must be received within 48 hours from last data read.
  • Data Requirements: Interval data (hourly or more granular).
    • Hourly Disaggregation Data Requirements:There are additional AMI data requirements to show advanced insights such as appliance-level disaggregation. Contact your Delivery Team for more information.
  • Data History: Interval data for the last two weeks, billing data for the last 12 months, and AMI data to the beginning of the current billing cycle. Note that the Hourly Usage module has additional data history requirements.
  • Data Coverage: Oracle must receive read coverage for the period included in the email. The period duration can vary from 5 to 7 days (for weekly emails), as it depends on the utility's peak hour intervals. This product does not differentiate between estimated and non-estimated reads. Both types of reads are supported. At least 75% of possible reads for the current billing cycle (including estimated reads) is required to calculate the bill forecast.
  • Fuel Type: Electric-only or dual fuel. Note that these emails cover only the electric portion of the customer's bill and usage.
  • Meter Type: The customer must have a smart meter.
  • Customer Type: The customer must be residential.
  • Rate Plan: The customer must be on a flat rate plan.
  • Multiple Service Points: Not currently supported.
  • Zero Usage: In the case when a customer hasn't used any electricity during the week, several checks are completed to determine whether to hide modules.