Channels and interval readings

Each meter can have multiple channels to import different types of interval data. 

Add a channel

When a meter has no channels configured or you need to add a new one, use the Actions menu and chose Add New Channel.

 

Channel properties

  • Interval: How often the interval data is recorded (15 minutes, hourly). If you are adding an interval not listed, pick the closest match.
  • Type: Data type associated with the channel. Most often used types areReading Use, Reading Demand, Use, or Demand.
  • Description: Add more information about the channel.
  • Channel Import ID: Unique ID used to identify the specific channel when importing readings. (Different from the meter import ID which is used for any channel on the meter.)
  • Multiplier: Each physical meter may have a specific multiplier determined by the manufacturer to convert raw readings into specific output units. The maximum length of characters is 12.
  • Rule:
    • Odometer readings continue to increase over time regardless of when the reading occurs (car odometer).
    • Trip readings reset to zero after each reading or the reading is an instantaneous value.
  • Units: Choose the units measured by the channel after the multiplier has been applied.
  • Maximum Reading: Used for odometer readings to determine when the meter has reached the rollover point.

Actions menu

Edit a channel with the Actions menu.

Edit Channel

Update or delete the current channel.

Add New Channel Settings

Add New Channel Settings lets you track changes over time.

For example, when you replace a submeter and your multiplier changes, you can set the effective date and update the multiplier. Interval data charts use the units of the most recent channel version. Data from prior versions is converted automatically to the units of the most recent version.

When you Add New Channel Settings, you enter the final reading for the old meter. If the new meter is odometer, you also enter the initial reading. These readings are visible on the interval data charts and are used by the chargebacks engine to calculate bills.

Explanation of final and initial channel readings

When you enter the final and initial readings during Add New Channel Settings UtilityManagement follows these rules.

Old rule New Rule Final meter reading Initial meter reading
Odometer Odometer Enter the final reading, the timestamp is midnight of the effective date. Enter initial reading, the timestamp is 00:00:01 of the version effective date.
Odometer Trip Enter the final reading, the timestamp is midnight of the effective date. N/A
Trip Trip Enter the final reading, the timestamp is midnight of the effective date. N/A
Trip Odometer Enter the final reading, the timestamp is midnight of the effective date. Enter initial reading, the timestamp is 00:00:01 of the version effective date.

If you don't have your final and initial meter readings when you create the new channel setting you can enter them at any time.

See Less than daily interval readings and chargebacks to correct any readings entered on the effective date before the meter swap out.

Channel setting rules

  • Readings with a timestamp of midnight (00:00:00 am) are for the prior period. This reading closes out the prior period.
  • Channel settings are designed to change daily (not hourly). Channel setting changes are always effective at midnight.
  • There are two rules depending on the interval:
    • Daily or greater (daily, weekly, monthly).
    • Less than daily (hourly, 30-minute, 15-minute).
 

Daily or greater interval readings and chargebacks

If changes are made to a channel and the interval is daily or greater (for example, daily, weekly, monthly):

  1. Add New Channel Settings.
  2. Enter a final reading for the old meter. A final reading is defined as any reading after 23:00:01 up to and including 00:00:00 (midnight) of the new channel settings effective date. This final reading closes out the prior channel settings period.
  3. If the new meter has odometer readings, enter an initial reading for the new meter. Trip meters do not need an initial reading.

    Example
    The Add New Channel Settings effective date is 12/17/2020. The final reading date should be between (inclusive) 12/16/2020 23:00:01 - 12/17/2020 00:00:00.

    If an initial reading is needed (odometer), the initial reading date should be after 12/17/2020 00:00:00.
 

Less than daily interval readings and chargebacks

If changes are made to a channel and the interval is less than daily (for example, hourly, 15-minute) additional steps are required. Failure to complete these steps can result in incorrect chargeback bills.

      1. Sum all the readings prior to the actual meter replacement time for that day.
      2. Delete the individual readings.
      3. Enter the sum from step 1 to the day prior to the meter replacement.

Example

Replace a trip meter with a trip meter and change the multiplier at 6:30 am on 01/02/2021.

Old meter: Trip, multiplier * 1 = KWH

New meter: Trip, multiplier * 1 = KWH

Reading Reading Value Note
01/02/2021 07:00:00 am 6 Meter replacement. First reading on the new meter.
01/02/2021 06:00:00 am 3000 (delete reading after including in sum)
01/02/2021 05:00:00 am 4000 (delete reading after including in sum)
01/02/2021 04:00:00 am 5000 (delete reading after including in sum)
01/02/2021 03:00:00 am 4000 (delete reading after including in sum)
01/02/2021 02:00:00 am 3000 (delete reading after including in sum)
01/02/2021 01:00:00 am 5000 (delete reading after including in sum)
01/02/2021 00:00:00 am 5000 29000 Readings from 00:00:00 am on 1/2/2021 through 06:00:00 am.

The sum of the readings (29KWH) that occurred AFTER the version effective date of 1/2/2021 00:00:00 through the meter replacement's first new reading of 01/02/2021 07:00:00 am must be entered with the same settings that were in effect on the day prior to the new settings.

The timestamp of the summed reading needs to be entered between the day prior to the effective date at 23:00:01 pm through (midnight) 00:00:00 of the effective start date.

How to enter meter readings

Several options are available to enter interval readings.

  • Manually key the reading on each channel. This is quick and easy when you have one or two readings to enter, but probably not something you want to do for many meters.
  • Import readings with an interval data file in the Interval Data module. This option is preferred and you can upload multiple meter readings at one time. The interval data import format requires either a meter import ID or a channel import ID.
    • A comma-delimited file cannot have commas in the reading numbers. (Yes -> 432100.98, NO -> 432,100.98)
  • Use an Update Readings spreadsheet to add readings to a channel. This spreadsheet is helpful to correct multiple readings on a channel or add new readings.

upload interval data

Edit Meter Import ID and Route

Use the Meter's Actions menu to update the meter import ID and route. If you use routes assign the meter to a route. A meter can exist on only one route.

Channel import ID versus meter import ID

Two methods for importing interval data 

  • The meter import ID is assigned to a meter and is used by many different channels to import meter readings.
  • The channel import ID is assigned to the channel and is a unique ID that identifies the specific channel to import meter readings.

Channel import ID

Some metering systems identify channel data with a channel import ID. In UtilityManagement the channel import ID is a unique value in the database.

Example of meter import ID vs channel import ID, note each channel import ID is unique.

meter import vs channel import

Meter import ID

A meter import ID is assigned to the meter and is used by many different channels to import meter readings for a meter.

When importing interval data, the application first searches for a matching channel import ID, if one is not found, it searches for a matching meter import ID.

How is data imported when there is one meter import ID and multiple channels?

  1. Check the meter import ID and associated meter. If that meter has one channel and matches all other provided channel properties, the data is imported.
  2. If there is more than one channel, check the observation type. If only one channel matches the type, the data is imported.
  3. If there is more than one channel with a matching observation type, check the unit code. If only one channel matches the observation type and unit code, the data is imported.
  4. If there is more than one channel with a matching observation type and unit code, check the time interval. Only one channel should match the observation type, unit code, and time interval combination. If a match is found the data is imported.
  5. Kickout. If no matching channel is found, the import fails.

Special note on odometer rollover

To determine if an odometer channel has rolled over, UtilityManagement looks for a current value lower than the previous value and that the difference between them is greater than 10% of the max value of the channel. 

A configurable database setting for the allowable channel rollback percent defaults to 10% and is used to determine if a channel has rolled over. In certain situations, this database setting may need to be updated.

For example, a meter with a max value of 999,999,  UtilityManagement would treat values where the current reading is less than the previous reading by about 99,999 or more as a rollover.

Here's an example with some smaller numbers where the rollover is 99.

  1. Delta (-95) = current reading (2) - previous reading (97).
  2. Because the delta is negative, determine if it's a rollback (net metering or onsite generation) or a rollover.
  3. Percent difference = 95/99*100=95.96%.
  4. The reading is greater than 10% and is treated as a rollover.

An example with larger numbers and a rollover of 999,999.

  1. Delta (-2,760) = current reading (90,283) - previous reading (93,043).
  2. Because the delta is negative, determine if it's a rollback (net metering or onsite generation) or a rollover.
  3. Percent difference = 2,760/999,999*100=0.27%.
  4. The reading is less than 10% and is treated as a rollback.