Rates Data Integration Process

Your Delivery Team will use the following process to set up and configure utility-specific rates:

  1. Scoping: A product expert is assigned to review your rate plans and confirm the applicable rate components for those plans with the support of your rates subject matter expert. See Rates Modeling for more information.
  2. Calculation Logic Definition: Once the rate plans in the scope are solidified, the Delivery Team works with you to determine the calculation logic for each rate plan before implementation.
  3. Data Extract Build and Analysis: The Delivery Team defines the rate data files that are applicable for your utility based on the rate plans that will be supported and the calculation logic required. You work with the Delivery Team to build the data files required. The Delivery Team analyzes this data to confirm the quality standards are met for consumption by the Oracle Utilities Opower Rate Engine. This process generally consists of two phases:
    • Phase 1 - Full Historical File Integration: For historical cost data display and rate analysis, the utility should perform one-time data file transfer for all periodic and historical data files that are applicable. The length of the history will be dictated by each utility’s requirements, but it should coincide with the length of history for which customer and billed usage data is being provided from the utility production billing system. This is typically January 1st of the previous calendar year to the present. For example, if your Delivery Team planned to launch your program for the first time on December 1, 2016, the team would need data going back to January 1, 2015.
    • Phase 2 - Incremental File Integration: Ongoing data transfer frequency for each of the data elements is dependent on the frequency in which the data changes. Your Delivery Team will work with you to determine the data transfer frequency (weekly, daily) that is required based on the rate structures being used and the likelihood of change to prices or other configurable factors.
  4. Configuration and Quality Assurance: You provide the Delivery Team with a set of sample test data and calculation for validation of the implemented logic. The Delivery Team configures the rate plans as defined in the definition phase and tests the configurations using the test data sets provided.
  5. User Acceptance: The Delivery Team works with you to conduct user acceptance testing of the calculations being presented by the end product prior to rolling it out.