Requirements and Limitations

3 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.

General Requirements

Category	Description
Customer Eligibility	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.
Customer Access Requirements	Customers must use a supported web or mobile browser. Devices must have a minimum width of 320 pixels to display widgets. Oracle Utilities Web products adhere to the Oracle Software Web Browser Support Policy.

Digital Self Service - Energy Management Cloud Service

Utility Requirements

Category	Description
Required Cloud Services	Utilities must purchase the Digital Self Service - Energy Management cloud service. AMI insights can be enabled in various widgets and features if utilities purchase the Digital Self Service - Energy Management AMI cloud service. For more information about what AMI insights can be provided, see Getting Started.
Implementation Requirements	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. See Authentication for more information. 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.
Scale	No applicable scale requirements.

Category

Description

Required Cloud Services

Utilities must purchase the Digital Self Service - Energy Management cloud service.

AMI insights can be enabled in various widgets and features if utilities purchase the Digital Self Service - Energy Management AMI cloud service. For more information about what AMI insights can be provided, see Getting Started.

Implementation Requirements

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. See Authentication for more information. 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.

Scale

No applicable scale requirements.

Customer Requirements

Category	Description
Billing Frequency	Monthly, bi-monthly, and quarterly.
Data Delivery Frequency	Monthly, bi-monthly, and quarterly.
Data Requirements	Billing Data: Most features require billing data to provide the best customer experience. Additional data requirements vary by feature. See the feature descriptions under Digital Self Service - Energy Management Web Portal for more information. Rates: Utility rates must be modeled by Oracle Utilities for cost information to appear. If rates are not modeled, energy use information is displayed by default. If the utility chooses to display cost information, rate modeling is required during initial program setup for an additional fee. See Rates Engagement and Rates Modeling for more information.
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.
Data Coverage	Data for a single bill period is the typical minimum data coverage requirement. Additional data coverage requirements vary by feature.
Supported Fuels	Electricity, gas, and dual fuel customers are generally supported. However, supported fuels vary by feature.

Digital Self Service - Energy Management AMI Cloud Service

Utility Requirements

Category	Description
Required Cloud Services	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.
Scale	No applicable scale requirements.

Customer Requirements

Category	Description
Billing Frequency	Monthly, bi-monthly, and quarterly.
Data Delivery Frequency	Monthly, bi-monthly, and quarterly.
Data Requirements	AMI Data: Most features require AMI data to provide the best customer experience. Additional data resolution requirements vary by feature. See the feature descriptions under Digital Self Service - Energy Management Web Portal for more information.
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.
Data Coverage	Data for a single day, week, or bill period is the typical minimum data coverage requirement. Additional data coverage requirements vary by feature.
Supported Fuels	Electricity, gas, and dual fuel customers are generally supported. However, supported fuels vary by feature.