Requirements and Limitations

The following data requirements and limitations apply to all utilities and customers in the Oracle Utilities Opower Affordability Proactive Alerts Cloud Service.

Utility Requirements and Limitations

Category	Description
Scale	Scale restrictions may apply. The actual number of communications sent may be affected by attrition, opt-outs, customer eligibility, and data availability.
Localization	US English and Spanish are supported. Contact your Oracle Utilities sales representative or Delivery Team to confirm whether the alerts are available in your market.
Required Cloud Service	Affordability Proactive Alerts Cloud Service.
Data Integration	Data must be sent to Oracle Utilities in the correct schema and at the appropriate frequency. Your Delivery Team will work with you to set up the data integration and transfer process.

Customer Requirements and Limitations

Category	Description
Billing Frequency	The utility must bill their customers on a monthly, bi-monthly, or quarterly basis.
Data Delivery Frequency	Monthly, bi-monthly, and quarterly.
Data Requirements	Billing data is required. Program participation data is required to know what programs customers are enrolled in. See the Program Participation Data Transfer documentation for details.
Data History	The customer must have at least one bill of historical billing data in the form of monthly, bi-monthly, or quarterly read data. If the alert includes any insights that look back to customer energy use trends from the previous year, then billing data from the previous year is required.
Data Coverage	Data for a single bill period is the typical minimum data coverage requirement.
Supported Fuels	Gas, electricity, and dual fuel.

Back to Top