Requirements and Limitations

2 Requirements and Limitations

The following data requirements and limitations apply to all utilities using the Opower Integration Hub.

Category	Description
Cloud Service Requirements	The Integration Hub Cloud Service must be purchased. The Opower platform must be set up in order to use the APIs described in Opower Integration Hub Features. Setting up the platform requires the Oracle Utilities Opower Customer Billing Integration and Platform Cloud Service Setup Fee. The Oracle Utilities Opower AMI Integration and Platform Cloud Service Setup Fee must be purchased in order to obtain AMI data and insights through the APIs. The following cloud services must be purchased in order to obtain AMI cost data at daily and subdaily resolutions through the APIs: Rates Engagement Cloud Service Rates Integration and Initial Rates Modeling Setup Fee Your Oracle Utilities Delivery Team will work with you to determine which cloud services and fees are applicable to your situation.
Implementation Requirements	You must complete data integration to use Oracle Utilities Opower data and insights with Opower Integration Hub. Data must be sent to Oracle Utilities in the right schema and according to the established data specifications. Your Delivery Team will work with you to identify which data specifications are applicable to your situation. AMI Insights: AMI insights are available if AMI data is provided to Oracle Utilities in the required format. For more information, see the Oracle Utilities Opower Interval Data Transfer documentation. Rates: Utility rates must be modeled by Oracle Utilities for rates data and insights to be available. For more information, see the Rates Engagement documentation. Single Sign-On: A utility must configure their instance of Oracle Identity and Access Management to allow for authentication and single sign-on (SSO) integration. This includes enabling the use of OpenID Connect Authorization Code Flow. Information on implementing Authorization Code Flow with Oracle Identity and Access Management and request examples can be found in the Identity and Access Management documentation.

Category

Description

Cloud Service Requirements

The Integration Hub Cloud Service must be purchased. The Opower platform must be set up in order to use the APIs described in Opower Integration Hub Features. Setting up the platform requires the Oracle Utilities Opower Customer Billing Integration and Platform Cloud Service Setup Fee.

The Oracle Utilities Opower AMI Integration and Platform Cloud Service Setup Fee must be purchased in order to obtain AMI data and insights through the APIs.

The following cloud services must be purchased in order to obtain AMI cost data at daily and subdaily resolutions through the APIs:

Rates Engagement Cloud Service
Rates Integration and Initial Rates Modeling Setup Fee

Your Oracle Utilities Delivery Team will work with you to determine which cloud services and fees are applicable to your situation.

Implementation Requirements

You must complete data integration to use Oracle Utilities Opower data and insights with Opower Integration Hub. Data must be sent to Oracle Utilities in the right schema and according to the established data specifications. Your Delivery Team will work with you to identify which data specifications are applicable to your situation.

AMI Insights: AMI insights are available if AMI data is provided to Oracle Utilities in the required format. For more information, see the Oracle Utilities Opower Interval Data Transfer documentation.
Rates: Utility rates must be modeled by Oracle Utilities for rates data and insights to be available. For more information, see the Rates Engagement documentation.
Single Sign-On: A utility must configure their instance of Oracle Identity and Access Management to allow for authentication and single sign-on (SSO) integration. This includes enabling the use of OpenID Connect Authorization Code Flow. Information on implementing Authorization Code Flow with Oracle Identity and Access Management and request examples can be found in the Identity and Access Management documentation.