What does a Proof of Concept deployement look like for an electric utility?
Sizing the system Cloud-Sliver needs the following information to size the system
- The number of utility customer billing accounts
- Approximate number of these accounts that have 15-minute interval meters vs daily read meters
- Write-up on billing rate structures – This is typically a book in Acrobat format that is published on the utility’s web site and has been filed with the relevant public utility commission. Generally, the book is around 100 pages in length. If the utility has published any rate summaries for its customers these should also be included. The rate summary is typically a page or two in length, formatted as tables, and published on in customer support portion of the utility’s web site.
Extracting data Cloud-Sliver needs the following data extracts from the utility’s system of record. In the North American market, the system of record is usually a system such as CIS or CC&B.
"Input" customer data Denormalized flat-file data table export that typically includes (at least) the following:
Additional fields often include things like:
- service point ID
- account ID
- customer ID
- meter ID
- customer name
- customer address (street address, city, state, zip code – usually as individual fields)
- latitude / longitude
- bill cycle number
- customer email & cell phone (for alerting purposes)
- meter multiplier(s) - if they haven’t already been applied to the meter data
"Input" meter data Data file(s) of at least 1-2 months of daily meter readings.
For data sources like L&G Command Center (CC) or UtiliNet (USC) these are ASCII human readable files that are in a comma separated (CSV) format or similar (the delimiters may be “|” instead of “,” for example). Typically it is only older MV-90 data format files that are in binary format.
Data file(s) of at least 1-2 months of interval (typically 15 minute) meter data.
"Output" bill data Denormalized flat-file export of billing data. This typically includes (at least) the following:
Note: this should include line item detail. The line items can either be individual fields in a single record or follow-on records that reference the same bill segment ID’sGiven a rate structure definition, and the information in this file, it should be possible to calculate a customer’s bill including all of the line item detail. If the customer has questions about what to include in this file – remind them that it should have all of the data elements required to do a complete calculation of a customer’s bill.
- service point ID
- account ID
- bill segment ID
- bill ID
- energy data (kWh, kW, pf, KVAR, etc. required for line-item calculation)
- rate class
- meter multiplier(s)
- bill cycle meter reading start date & time and end date & time
- billed amount
Parallel system With this information and these data files, Cloud-Sliver can configure a system with both an internal facing web site that can be used by key accounts team, customer support, etc. and an external facing web site that can be used for customer engagement & support.
The system can run in parallel with the billing system of record and can be used to check and reconcile the system of record and can also be used for rate scenario analysis, financial forecasting, etc.