Requirements and Limitations

There are multiple Oracle Utilities Opower Digital Self Service cloud services. Each cloud service comes with a set of data requirements and limitations. The requirements must be met for a utility and a customer to participate in the program.

On this page:

General Requirements

  • Cloud Service Requirements: The Digital Self Service - Energy Management cloud service is a prerequisite for all other cloud services listed on this page. For an overview of all cloud services available from Oracle Utilities, see the Oracle Energy and Water Cloud Service Descriptions online at Oracle Contracts - Cloud Services Service Descriptions.
  • Active Account: Customers must be associated with a premise that has an active account with the utility. An active account means that the customer has signed up with the utility for at least one service point for one fuel type at an address.
  • Screen Resolution: A minimum width of 320 pixels is required for devices to display widgets.
  • Supported Browsers: The customer must use a supported web or mobile browser. Oracle Utilities Web products adhere to the Oracle Software Web Browser Support Policy.
  • Configuration: Configurations are limited to the utility logo, primary and secondary colors, and up to 10 configurable text changes.

Back to Top

Digital Self Service - Energy Management Cloud Service

Utility Requirements

  • Cloud Service Requirement: Utilities must purchase the Digital Self Service - Energy Management cloud service.
  • Data Integration: Data must be sent to Oracle Utilities in the right schema and according to the established data specifications. Your Oracle Utilities Delivery Team will work with you to identify which data specifications are applicable to your situation.
  • Single Sign-On: Oracle Utilities recommends that utilities use single sign-on (SSO), as outlined in the Oracle Utilities Opower SSO Configuration Guide. If the utility uses SAML-based SSO, third-party cookies must be enabled on the customer's web or mobile browser to view Oracle Utilities Opower embedded web features. Third-party cookies authenticate the customer's account using a session identifier, which allows embedded widgets to display the correct data for the customer. Third-party cookies are not required for OpenID Connect-based SSO.

Customer Requirements

  • Data History: For most features to have meaningful insights, a customer must have more than one bill of historical billing data in the form of monthly, bi-monthly, or quarterly read data. Additional data requirements vary by feature.

Back to Top

Digital Self Service - Energy Management AMI Cloud Service

Utility Requirements

  • Cloud Service Requirement: In order to purchase the Digital Self Service - Energy Management AMI cloud service, utilities must also purchase the Digital Self Service - Energy Management cloud service.

Customer Requirements

  • Data History: For most features to have meaningful insights, a customer must have more than one bill of historical billing data in the form of subdaily, daily, monthly, bi-monthly, or quarterly read data. Additional data requirements vary by feature.

Back to Top

Rates Engagement

Utility Requirements

  • Cloud Service Requirement: In order to purchase the Rates Engagement cloud service, utilities must also purchase the following cloud services:
    • Digital Self Service - Energy Management
    • Digital Self Service - Energy Management AMI
  • Rates Data Transfer: The utility must send rates data to Oracle Utilities in the correct schema and at the appropriate frequency. See Oracle Utilities Opower Rates Data Transfer for details.
  • Rates Modeling: Rates modeling is required during initial program setup, and is not included in the cost of the cloud service. See Rate Modeling for more information.

Customer Requirements

  • Billing Frequency: Customers must be billed on a monthly, bimonthly, or quarterly basis.
  • AMI Data: Customers must have daily or sub-daily AMI reads.

Back to Top

Rate Engine Plus

Utility Requirements

  • Cloud Service Requirement: In order to purchase the Rate Engine Plus cloud service, utilities must also purchase the following cloud services:
    • Digital Self Service - Energy Management
    • Digital Self Service - Energy Management AMI
    • Rates Engagement
  • Rates Data Transfer: Rates data must be sent to Oracle Utilities in the correct schema and at the appropriate frequency. See the Oracle Utilities Opower Rates Data Transfer Standards for details.
  • Rate Validation: The utility must purchase a one-time fee to cover rate validation and related set up tasks. This process ensures that the Rate Engine Plus has correctly modeled rates for utility customers. To perform this process, Oracle Utilities compares energy cost information calculated by the Rate Engine Plus to customer utility bill amounts.

Customer Requirements

  • Billing Frequency: Customers must be billed on a monthly, bimonthly, or quarterly basis.
  • AMI Data: Customers must have daily or sub-daily AMI reads.

Back to Top