Requirements and Limitations
The following data requirements and limitations apply to all utilities and customers using the EV Charging Coach V3 program. These requirements must be met for a utility and a customer to participate in the program.
Utility Data Requirements
Utilities must meet the following criteria:
- Rate Modeling or Rate Engine Plus: In order for the platform to support utility-specific rates, an intensive rates modeling and configuration process is necessary.
-
Required Cloud Services: Oracle Utilities Opower Load Shifting Cloud
Service, Electric Vehicle and one of the following:
- Oracle Utilities Opower Load Shifting Cloud Service, Rate Coach
- Oracle Utilities Opower Proactive Alerts Cloud Service
Customer Data Requirements
Customers must meet the following criteria:
- Billing Frequency: Monthly or bi-monthly.
- Electric Vehicle: Customers much charge an electric vehicle at their residence.
- Data Delivery Frequency: Daily. Must be received within 48 hours from last data read.
- Data Requirements: Interval data (hourly or more granular). There are additional AMI data requirements to show advanced insights such as appliance-level disaggregation. Contact your Delivery Team for more information.
- Data History: Advanced Metering Infrastructure (AMI) data going back to the beginning of the current billing cycle.
- Data Coverage: Estimated reads are not supported.
- Fuel Type: Electric-only or dual fuel. Note that these emails cover only the electric portion of the customer's bill and usage.
- Meter Type: The customer must have an AMI meter that measures whole-home usage, and not an EV-only meter.
-
Charger type:
- L2 chargers: All features are supported.
- L1 chargers: Features that include disaggregation data are not supported.
- Rate Plan: Customers must be on a time-of-use (TOU) electric rate plan.
- Email Address: Customers must have a valid email address established with the utility.
Limitations
The following are known limitations:
- Meters: EV-only meters are not supported.
- Solar: Solar customers are not supported.
-
Zero Usage: In the case when a customer hasn't used any electricity during
the week, several checks are completed to determine whether to hide modules, or to
fail the entire email communication. The checks are as follows:
- Introduction Email: If the Hourly Usage module has 0 usage, exclude that module but send the communication.
- Weekly Email: If the Hourly Usage module has 0 usage, exclude that module but send the communication.