Usage Fields

The billing data usage fields capture details such as the customer's total energy usage amount, bill cycle duration, and total billing charge.

Each table row represents a column in the data file. The header row of the data file must contain all table "Column Name" values, even if all values in those columns are blank. The columns must appear from left to right in the order in which they appear in the table and be separated by tab characters.

Note: If you are sending data in two files to Oracle Utilities, then this data should be included in its own, separate file. See Billing Data File Specifications for more information.

Usage data should be transmitted in a separate file.

Column Name	Description
service_point_id	Utility’s unique identifier for the service point. See Billing Data Entity Definitions for more information. Type: STRING Can Be Empty?: No. Default: Not applicable.
usage_value	Usage value amount based on meter read in units determined by meter's units. Commas cannot be used in this field. The value must be positive and the usage cannot exceed 999999999 kWhs. Values that are too large will be rejected. Negative usage values can be accepted, but this requires configuration. Contact your Delivery Team for more information. Type: NUMBER Can Be Empty?: No. Default: Not applicable.
date_to	End date of meter read period. Type: STRING (yyyymmdd) Can Be Empty?: No. Default: Not applicable.
duration	Number of days the usage value represents. For example, this could be 30 for a monthly billing cycle, 60 for a bimonthly billing cycle, and so on. Durations for monthly, bi-monthly, quarterly, and annual billing cycles are supported. Type: NUMBER Can Be Empty?: No. Default: Not applicable.
is_estimate	A flag to indicate whether a usage read was estimated or not. Allowed Values: A Actual read by utility. E Estimated read. U User-reported read. Note: A user-reported read is treated as an estimated read when it is imported into the Oracle Utilities Opower system. Type: STRING Can Be Empty?: No. Default: E
usage_charge	Amount billed to the customer for usage during this period. This should only include the variable charge for the actual energy usage, and should exclude taxes, account fees, rebates, or other bill adjustments. If the reported `usage_value` is the sum of usage from multiple meters at the same `service_point`, the `usage_charge` is required to provide an effective usage rate. Type: NUMBER Can Be Empty?: Yes. Default: Null.
demand_peak	Highest usage mark within a month based on meter read in units determined by the meter's units. Generally, this will be present only if the utility has a special high-water mark meter installed at a business site. Note: Only enter values in this column if your utility is part of the Oracle Utilities Opower Small and Medium Business Energy Efficiency pilot program. If your utility is not part of this program, do not enter any values in this column. Type: NUMBER Can Be Empty?: Yes. Default: Null.