Requirements and Limitations

The following data requirements and limitations apply to all utilities and business customers enrolled in Weekly Energy Updates, within the Business Customer Engagement Proactive Alerts Cloud Service.

On this page:

Requirements

Utility Requirements

Category

Description

Scale

The number of communications sent may be affected by attrition, opt-outs, customer eligibility, and data availability.

Language

Not all languages and locales are supported at this time. Contact your Oracle Utilities Sales Representative to confirm that alerts are available in your market.

Other Product Requirements

  • Web Portal Requirements: Some of the features listed in this documentation require access to a web portal. For example, to enable customers to set a personal threshold for the Bill Forecast, or to opt in or out of the program from a utility website, the utility must provide customers with access to a web portal. Oracle Utilities Opower provides the Business Customer Engagement Digital Self-Service Web Portal.

    Note: Purchasing the web portal is not required to send alerts. A web portal is required only if utilities want to utilize features that require customer access to a web portal. Utilities might also decide to create their own web portal and use APIs to enable customers to access and update their information. For additional information, see the Oracle Utilities REST API documentation.

  • Single Sign-On: The utility must use single sign-on (SSO) to be able to edit customer email addresses for non-recipients of the program, or they must edit these via Oracle Utilities Opower APIs.

Back to Top

Customer Requirements

Category

Description

Billing Frequency

Monthly or bi-monthly.

Data Delivery Frequency

Daily. The utility must be able to deliver customer data to Oracle Utilities within 72 hours (48 hours from the last data read of the day). Data must be sent to Oracle Utilities in the right schema and according to the Oracle Utilities Opower Interval Data Transfer Standards.

Data Requirements

Billing Data: Billed usage data from the utility is required.

AMI Data: The customer must have AMI data for the last two weeks. Hourly or more granular data is required. Weekly Energy Updates will not be sent without this level of data granularity.

Customer Contact Information: The utility must be able to provide contact information for the customer if auto-enrollment is being used.

Email Address: The customer must have a valid email address.

Data Coverage

By default, at least 50% coverage is required for the last two weeks, the highest day in the customer’s last week, and the last day of the week.

Supported Fuels

Electric-only, gas-only, and dual-fuel customers are supported.

Back to Top

Other Limitations

  • Customer Service Limitation: Customer Service Representatives may not be able to determine why a customer did not receive a Weekly Energy Update. In such cases, an issue should be logged in My Oracle Support.
  • Service Points Limitation: The customer must only have one service point for each meter type. For example, dual-fuel customers must have exactly one electricity and one gas service point, while single-fuel customers must only have one service point.

Back to Top