Requirements and Limitations

The following data requirements and limitations apply to all utilities and customers of Oracle Utilities Opower Digital Self Service - Transactions. This documentation reflects the most recent release of Digital Self Service - Transactions, which is listed as part of the Release Readiness documentation.

Utility Data Requirements and Limitations

The following list describes the utility requirements for Digital Self Service - Transactions:

Customer Integrated System: Integration is required with an Oracle Utilities Customer Care and Billing system or an Oracle Utilities Customer to Meter system. This includes a real-time connection between Digital Self Service - Transactions and the Customer Care and Billing or Customer to Meter system. Your Oracle Utilities Delivery Team will work with you to configure your Customer Care and Billing or Customer to Meter system, which has a direct impact on the functionality available to customers. See the Oracle Utilities Customer Care and Billing or Customer to Meter Documentation, as well as the Oracle Utilities Opower Digital Self Service - Transactions Configuration Guide for applicable configuration tasks.
Oracle Version Requirements: The list below includes Oracle products that can be integrated with Oracle Utilities Digital Self Service - Transactions Cloud Service, including the supported versions:
- Oracle Utilities Customer Cloud Service 22C
- Oracle Utilities Customer Cloud Service 23A
- Oracle Utilities Customer Cloud Service 23B
- Oracle Utilities Customer Care and Billing 2.6 SP1
- Oracle Utilities Customer Care and Billing 2.7 SP3
- Oracle Utilities Customer Care and Billing 2.9
- Oracle Utilities Customer to Meter 2.6 SP1
- Oracle Utilities Customer to Meter 2.7 SP3
- Oracle Utilities Customer to Meter 2.9
Oracle Cloud Services: Your Oracle Utilities Cloud Services may include the following applications. Refer to your license agreement to confirm your applicable Cloud Services:
- Oracle Utilities Digital Self Service - Transactions
- Oracle Utilities Digital Self Service - Energy Management features are an optional add-on, available through the Oracle UtilitiesOpower Digital Self Service - Energy Management Cloud Service. Exceptions include the Data Browser and Green Button, which are included directly with the Digital Self Service - Transactions Cloud Service. For information on how these features are presented as part of Digital Self Service - Transactions, see Your Utility Use. For additional information on the Digital Self Service - Energy Management feature functionality and requirements see the Oracle Utilities Opower Digital Self Service - Energy Management Cloud Service Product Overview .
- Oracle Cloud Infrastructure Identity and Access Management
- Oracle Utilities Customer Cloud Service
- The Savings Hub feature is an optional add-on, available through the Oracle Utilities Opower Affordability Cloud Service. For information on how these features are presented as part of Digital Self Service - Transactions, see Savings Hub. For additional information on the Affordability Cloud Service feature functionality and requirements, see the Oracle Utilities Opower Affordability Savings Hub Cloud Service Overview.
Customer Account Authentication: The utility must configure and integrate an identity management system in implementation, test, and prod environments to handle customer account creation and authentication. This includes defining account requirements, such as password rules, using the third-party identity management system. See the Oracle Utilities Opower Digital Self Service - Transactions Authentication Configuration Guide for supported authentication protocols.
Deployment: Digital Self Service - Transactions can be included as part of a utility's existing website and must be hosted within a utility's third-party content management system.
Credit Card Payments: Credit card payments require a third-party processor. The utility must configure and integrate with a payment processor to support the Digital Self Service - Transactions credit card payments feature. The preferred payment processing vendor for Oracle Utilities is Paymentus. The integration with Paymentus utilizes a Paymentus capability (CP Flow) where accounts and actions are passed to Paymentus as part of an API call. Out-of-the-box APIs for real-time transactions are available between Paymentus and Customer Care and Billing version 2.6 Service Pack 1 and later. Digital Self Service - Transactions can redirect users using single sign-on to a Paymentus portal that can be customized for credit card processing. The Paymentus portal can leverage the existing APIs to Customer Care and Billing to validate the account and display the amount due, without requiring users to log in again. Users with multiple accounts can view up to 100 accounts available for payments when being redirected to Paymentus. Refer to Paymentus' third-party documentation for information on the supported flow.
Outbound Notifications: The utility must configure and integrate an external system with their customer integrated system to deliver outbound notifications for the defined Billing and Payment Alerts. Oracle recommends integrating with Oracle Responsys and Oracle Integration Cloud to support outbound notification delivery. For additional information on configuring outbound notifications, see the Oracle Utilities Opower Digital Self Service - Transactions Configuration Guide.
Rates Engagement: Rate Comparison web features are an optional add-on of Digital Self Service - Energy Management, which require the Oracle Utilities Opower Rates Engagement Cloud Service. For information on how Rate Comparison features are presented as part of Digital Self Service - Transactions, see Your Utility Use. For additional information on the Rates Engagement Cloud Service feature functionality and requirements see the Oracle Utilities Opower Digital Self Service - Energy Management Cloud Service Product Overview .
Advanced Metering Infrastructure (AMI): AMI features are an optional add-on, available through the Oracle Utilities Opower Digital Self Service - Energy Management AMI Cloud Service. Exceptions include the Data Browser and Green Button, which are included directly with the Digital Self Service - Transactions Cloud Service. See the Oracle Utilities Opower Digital Self Service - Energy Management Cloud Service Product Overview for more information.
Bill Provision Service: The bill provision framework chosen by the utility must be configured to specify the Oracle Utilities Opower bill download API. For more information, see the Oracle Utilities Opower Digital Self Service - Transactions Bill Download Integration Guide.
Implementation Support Services: For information on implementation support services for Digital Self Service - Transactions, refer to Oracle Contracts - Cloud Services Service Descriptions.
Analytics: Digital Self Service - Transactions supports integration with Google Analytics to analyze web traffic. You must provide Oracle Utilities with your Google Analytics tracking ID to support this integration.
Chat Support: Digital Self Service - Transactions can be integrated with chat services to allow customers and utilities to communicate in real time in a chat channel. Genesys chat service is a third-party service that requires a separate service agreement and contracting with the third-party Genesys chat vendor prior to integration with Digital Self Service - Transactions.
Outage Management System: The utility must configure and integrate an outage management system with their customer integrated system to push issue information reported by the customer to an Outage Management System, and to provide issue information to the Outage Map. Oracle Utilities recommends integrating with Oracle Utilities Network Management System to support the customer outage experience. For additional information on configuring outage features, see the Oracle Utilities Opower Digital Self Service - Transactions Configuration Guide.

Customer Data Requirements and Limitations

Service Type: Customers can have electric, gas, dual fuel, water, or wastewater service. Supported functionality varies by service. All features that are not applicable to a customer's service types are hidden from view. Refer to the feature descriptions below for feature-specific requirements.
Browser Support: The customer must use a supported web or mobile browser. Oracle Utilities Web products adhere to the Oracle Software Web Browser Support Policy.