On the hottest afternoons of the year, everyone runs their air conditioner at once, and the grid strains. Load control is the utility's way of easing that peak: a small switch — a load-control receiver — is installed on equipment like a water heater or air conditioner, and during peak hours the utility cycles it off for a short stretch. The customer barely notices, and in exchange they get a bill credit or a rebate for enrolling.
The switch itself is simple. Keeping track of thousands of them is the hard part.
The problem: thousands of switches, one spreadsheet too many
A load control program lives or dies on its records. Which accounts have a device? Which loads does each device control? How many kilowatts can you actually shed, and where? Is that switch still connected, or was it returned two years ago? If you can't answer those questions, you can't run the program — or prove it's working.
That's what Incentit's load control feature is for: one record per device, tied to the account it serves.
One record per device
Every device in Incentit carries the facts a program manager needs: the account and location it's installed at, its serial number, device type, and status. It also carries the substation it belongs to (pulled from the account), the input voltage, and the antenna details — whether one is installed, where it sits, and when it went in — plus the signal threshold and the fail-safe time, so the team knows what the device does if it stops hearing from the utility.
Relays: what the device actually controls
A device is only half the story. The other half is its relays — the individual circuits it switches. Each relay in Incentit records which load it controls, how many kilowatts that circuit draws, which control group it belongs to, and when it was connected (and disconnected, if it was removed). It also records how the relay behaves: its function, its function time, whether it's inverted, and what it should do on power-up, power-down, or if the signal fails.
One device can control several loads at a property, so the relay list is where the real program lives.
Rules that keep the records honest
A device list is only useful if the data in it can be trusted, so Incentit enforces a few rules as records are saved:
- A device marked Installed has to have at least one relay with a connect date.
- A device marked Returned or Junk has to have a disconnect date wherever a connect date exists.
- A relay with a connect date has to have a circuit kW and a load type — otherwise the "how much can we shed" math has nothing to work with.
Getting a whole fleet in at once
Nobody types in a thousand devices by hand. Incentit takes a CSV upload: map the columns once (account, serial, device type, status, and the relay fields), and the system validates every row before anything is saved. Rows with problems are listed with the error; the valid ones can be committed as-is.
The number that matters
At the end of the day, a program manager needs one answer: how much load can we shed? The relay summary report gives it — net connected devices and net kilowatts, grouped by account and load type, exportable to CSV. That's the number that goes into the peak-day plan.
Tied to the incentive
A load control device usually arrives with an enrollment — a customer signed up and got a credit for it. In Incentit, the devices for an account show up right on that account's incentive record, so the enrollment and the hardware live in the same place. No cross-referencing a second system to find out whether the customer who got the credit still has the switch.
Where it fits
Load control is one of the oldest demand-response tools a utility has, and it still works — because it runs on records as much as on radios. Incentit keeps those records: the device, the relays, the kilowatts, and the enrollment, all tied to the account.
If your load control program still lives in a spreadsheet, book a demo and we'll show you what it looks like inside Incentit.