Reference
Definitions for key terms in utility operations — meter-to-cash, Customer 360, AMI, MDM, tariff billing, revenue assurance, district energy, and more.
A two-way communication network connecting smart meters at customer premises to a utility's data systems. AMI enables remote meter reading, real-time consumption data, time-of-use billing, outage detection, and demand response programs — replacing the need for manual or drive-by reads.
One-way meter reading technology that transmits consumption data from meters to utility collection systems, typically via drive-by or walk-by handheld readers. Unlike AMI, AMR does not support two-way communication, real-time data, or remote disconnect — but remains widely deployed in water and gas utilities.
A structured billing cycle process that rates validated consumption data against applicable tariffs, calculates charges, generates exceptions for review, and produces invoices for a defined set of accounts and billing periods. Bill runs typically include pre-run validations, exception queues, approval stages, and invoice generation as discrete steps.
An account or read flagged during a bill run for review before invoicing — typically due to zero usage, unusually high or low consumption, estimated reads replacing actual reads, or missing data. Exception queues let billing staff review, correct, and approve flagged accounts before bills are sent, preventing customer disputes and revenue errors.
The core operational database for a utility company, storing customer accounts, premises, service agreements, meter-to-account relationships, billing history, payment history, and communication records. The Customer 360 is the system of record for all customer-facing utility operations and the foundation of the meter-to-cash lifecycle.
A web-based interface that gives utility customers or tenants online access to their bills, consumption history, payment processing, service request submission, and account management — without contacting customer service. Self-service portals reduce inbound call volume and improve customer satisfaction by making billing data transparent and accessible.
A billing component based on a customer's peak power draw (measured in kilowatts or kilovolt-amperes) during a billing period, separate from energy consumption charges. Peak demand is typically calculated from 15-minute or 30-minute interval data. Demand charges are common for commercial and industrial electric customers and can represent a significant share of total bills.
A centralized cooling service where chilled water is produced at a central plant and distributed via insulated underground pipes to connected buildings in a district, precinct, or campus. Buildings connect to the district cooling network via Energy Transfer Stations (ETS). District cooling is more efficient than individual building chillers and is widely deployed in the Middle East, Southeast Asia, and dense urban environments.
A centralized heating service that delivers hot water or steam from a central plant to connected buildings for space heating and domestic hot water supply. Common in Scandinavian cities, university campuses, airport precincts, and dense urban areas. District heating reduces carbon emissions compared to individual gas boilers and enables the use of waste heat from industrial processes.
The structured process of communicating with customers who have overdue balances — through progressive notices, payment arrangement offers, and escalation toward disconnection. Dunning workflows are governed by customer protection rules and regulatory requirements, including mandatory safety checks, dispute holds, and minimum notice periods before field disconnection.
The physical and metering interface between a district cooling or heating network and a building's internal systems. The ETS measures thermal energy consumption (supply and return temperature, flow rate), controls flow, and hydraulically separates the district network from the building's internal plumbing. Each ETS is a billing point in the district energy network.
Meter readings captured at regular intervals — typically every 15 or 60 minutes — rather than as cumulative monthly totals. Interval data is required for time-of-use billing, demand charge calculation, load profile analysis, and demand response programs. AMI meters produce interval data automatically; older AMR meters collect only cumulative totals.
Software that ingests, validates, stores, and manages consumption readings from smart meters (AMI), AMR devices, and manual reads. MDM systems apply VEE rules to ensure data quality, handle missing read estimation, maintain read history, and make validated consumption data available to billing systems. MDM is a prerequisite for accurate, automated billing at scale.
The complete utility revenue cycle from meter data collection through tariff rating, billing, invoice delivery, payment collection, collections, and revenue reconciliation. A connected meter-to-cash process — where all stages share a single operational record — eliminates manual handoffs, reduces revenue leakage, and accelerates the billing cycle from weeks to days.
A billing arrangement for customers with distributed generation — typically rooftop solar panels — that credits them for electricity exported to the grid, offsetting their consumption charges. Credits may carry forward across billing periods or be paid out annually at a true-up settlement. Net metering requires interval data to accurately track import and export separately.
A billing provision that sets a minimum demand charge based on the highest peak demand recorded in a recent period — typically the past 12 months — even if actual demand in the current billing period is lower. Ratchet clauses protect utility revenue by ensuring customers pay for the capacity reserved for their peak needs, regardless of whether they use it every month.
Processes and analytical tools that identify billing gaps before they become recurring revenue losses. Revenue assurance monitors unbilled accounts with valid reads, meters with data gaps, consumption anomalies, inactive accounts with usage, billing variances against historical patterns, and high-risk collections accounts. It converts reactive reconciliation into proactive gap closure.
A method of allocating a master meter utility bill across multiple tenants in a multifamily or commercial property based on a formula — typically unit square footage, number of occupants, or number of bedrooms — rather than individual submeter readings. RUBS is used where individual submetering is not installed and cost allocation is required.
A structured work assignment dispatched to field crews or service technicians for tasks such as meter installation, service turn-on or turn-off, meter exchange, read verification, leak investigation, or safety inspection. Service orders connect the Customer 360 (which creates the request) to field execution (which completes the task) and the billing system (which triggers account changes on completion).
The installation of individual meters at the unit or tenant level within a building or campus served by a single master meter connected to the utility. Submetering enables accurate per-tenant billing based on actual consumption, rather than allocated cost sharing. It is common in commercial real estate, multifamily residential, industrial parks, and campus environments.
The software component that applies rate structures to validated consumption data to calculate billable charges. A configurable tariff engine handles flat, tiered, time-of-use, demand, thermal, fixed, multi-part, ratchet, and tax-inclusive rates — with versioning, effective date control, and proration for partial billing periods — without requiring custom code for each rate change.
A rate structure that charges different prices for electricity depending on when it is consumed during the day or year. Peak periods — typically weekday afternoons when grid demand is highest — carry higher rates than off-peak or shoulder periods. TOU billing requires interval meter data and encourages customers to shift flexible loads to lower-cost periods.
The standard unit for measuring district cooling energy consumption. One ton of refrigeration is the cooling power equivalent to melting one ton of ice in 24 hours, approximately 3.517 kilowatts. TR-h measures cumulative cooling energy delivered to a building through its ETS. District cooling tariffs typically charge per TR-h consumed plus a monthly contracted capacity charge.
Meter reads that have been collected and validated but have not resulted in a bill — due to billing cycle gaps, account setup errors, Customer 360-to-MDM mismatches, or system failures. Tracking and resolving unbilled consumption is a core revenue assurance function. Left undetected, unbilled accounts represent direct, recurring revenue leakage.
The three-stage process applied to raw meter reads before they are used for billing. Validation checks reads against business rules — detecting missing reads, negative consumption, and out-of-range values. Estimation fills gaps using consumption patterns, historical averages, or neighbouring-day methods. Editing allows authorized staff to correct identified errors with a full audit trail.
UtilConnect connects Customer 360, meter data, tariff management, billing, and revenue assurance into one platform.
See how UtilConnect modernises Customer 360, meter data, billing, revenue assurance, and operational workflows — in one platform.