Requirements and Limitations

The Business Customer Engagement Digital Self Service - Energy Management cloud service comes with a set of data requirements and limitations. The requirements must be met for a utility and a business customer to participate in the program.

Utility Requirements

Category

Description

Cloud Service Requirements

The Business Customer Engagement Digital Self Service - Energy Management cloud service must be purchased. Features based on billing and AMI data are included in the service.

In order for rates insights to appear in the product, the Rates Engagement cloud service must be purchased, and rates modeling is required during initial program setup at an additional fee. Assessment will be needed to determine if your business rate structure can be supported. Contact your Delivery Team for more information.

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.

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 Authentication and the Oracle Utilities Opower SSO Configuration Guide. For standalone implementations of the product, Oracle Utilities supports SAML-based SSO. For embedded implementations, Oracle Utilities supports OpenID Connect-based SSO. Your Delivery Team will work with you to set up the proper method of SSO for your program.

Customer Requirements

Category	Description
Billing Frequency	Monthly, bi-monthly, and quarterly.
Data Delivery Frequency	Monthly, bi-monthly, and quarterly.
Data Requirements	Billing and AMI Data: Most features require billing or daily AMI data (or a combination of the two) to provide the best customer experience. Additional data requirements vary by feature. See the feature descriptions under Customer Experience for more information. Customer Classification: The customer must be classified as a non-residential customer. For information on customer classification, see the Account Fields section in the Oracle Utilities Opower Account Data Transfer specification.
Data History	For most features to have meaningful insights, a business must have more than one bill of historical billing data. Additional data requirements vary by feature. See the feature descriptions under Customer Experience for more information.
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 businesses are generally supported. However, supported fuels vary by feature. See the feature descriptions under Customer Experience for details.
Other	Active Account: Business customers must be associated with a premise that has an active account with the utility. An active account means that the business has signed up with the utility for at least one service point for one fuel type at an address. 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. Screen Resolution: A minimum width of 320 pixels is required for devices to display the features and widgets of the product.