Buildings

The HVAC Maker's Guide to Remote Machine Monitoring

A heat pump's efficiency is measured once, on commissioning day, then never again. Watched continuously, that same number becomes a service trigger, a contract clause, and heat billed by the kilowatt-hour.

TagoIO Team ·
The HVAC Maker's Guide to Remote Machine Monitoring

Remote monitoring lets a maker of heat pumps, boilers, chillers, rooftop units or refrigeration equipment watch every unit’s efficiency continuously, catch refrigerant leaks and fouling as drift long before comfort or stock is lost, and bill the heating or cooling delivered by the kilowatt-hour. In the example on the Heating & Cooling solutions page, a school’s heat pump delivers 21,960 kWh of heat, gets a slow leak repaired after a 10% COP drift, and closes the month with a $2,305.80 invoice at $0.105 per kWh.

Key points

  • COP, the ratio of heat delivered to electricity consumed, is the one number that carries the category: it detects faults, prices contracts, and proves guarantees.
  • The whole catalog connects over what each site already has: air handlers over Modbus, chillers over LoRaWAN retrofit sensors, heat pumps over cellular, reefers over satellite.
  • Heat as a service only works when every billing line is backed by a measurement; the heat meter, the COP trend, and the invoice come from one data stream.
  • In an efficiency contract the incentive flips: an inefficient machine burns the maker’s margin, not the customer’s budget, which is exactly why buyers trust the model.

How does heating and cooling equipment connect?

Each machine reports over the network its site already has, and the platform receives all four paths the same way:

How heating and cooling equipment connects: air handlers over Modbus, chillers over LoRaWAN, heat pumps over cellular, transport refrigeration over satellite, converging on TagoIO and out to the service desk, portal and invoice

In the field this usually means a site gateway bridging Modbus, M-Bus heat meters and BACnet into the cloud; the industrial gateways from our partner InHand Networks are a common choice for HVAC retrofits. Battery-powered LoRaWAN sensors cover cold rooms and display cases, cellular covers rooftop and residential units, and satellite covers reefers and remote cold chain, a pattern close to the cargo monitoring we described in From Location to Intelligence. Installed units retrofit with add-on sensors for temperature, pressure, current or energy, with no change to the controller, and a payload parser absorbs any proprietary format on arrival.

Which measurements matter?

The solutions page lists the working set: COP, flow and return temperature, superheat, discharge pressure, compressor current, filter pressure drop, cold room temperature, and heat delivered. Three of them do most of the commercial work: the heat meter (flow and delta-T) measures the product, COP prices and polices it, and filter pressure drop and superheat explain the drift when it comes.

The walkthrough: a leak caught as a trend

The page’s simulated case shows the mechanism. Heat pump 12 heats a school’s main block. At 2 degrees outside it runs a COP of 3.22, sitting on its clean curve. One week, in the same weather, COP reads 10% under the curve and crosses the leak-check line: the signature of a slow refrigerant leak, invisible to the building and expensive to ignore. A leak check is booked for 9 AM the next morning, the leak is repaired, the unit recharged, and COP returns to its curve. The month closes with 21,960 kWh of heat delivered, the guarantee kept, and the $2,305.80 invoice issued.

The fleet view scales the story: 6,840 kWh billed at $0.105 per kWh so far in the month ($718.20, up 15% on October), one heat pump of four needing attention, and $2,680.65 ready to bill across all four buildings, each line itemized in kWh. The smaller cards show the same pattern on filters (212 Pa across a bank, the new set already on order) and cold rooms (a defrost watched at -16.4 degrees).

The money lane and the data lane

Heat as a service is two parallel lanes, and every item in one is backed by an item in the other:

Heat as a service: the data lane from heat meter to live COP to drift detection, tied to the money lane of metered thermal billing, service before failure, and an efficiency guarantee
Model What the customer pays for Basis
Monitoring and service plan Leaks and fouling fixed before losses $ per unit, monthly
Heat or cooling delivered Metered thermal output $ per kWh
Efficiency guarantee A COP floor in writing Premium on the kWh rate
Cold chain compliance Temperature records and alerts $ per room or vehicle, monthly

Note the incentive flip in the second and third rows: once you bill by the kWh with a COP floor, a degraded machine consumes your margin. That is why the drift detection is not a feature but the foundation; it protects the contract you signed. The progression between these rows follows the ladder from Climbing the Fusion Ladder, compressed here because the meters HVAC needs are standard parts.

Where does TagoAI fit?

TagoAI builds the screens so your engineers stay on the thermodynamics. Describe the view in the TagoAI panel, for example “a heat pump board per building, quiet while each unit tracks its clean curve, flagging any COP that falls under it”, and TagoAI creates the widget and its code against live devices; in the page’s sample it flags the unit running 2.8 against a clean 3.2. Verify what it builds against device data before a building owner sees it.

What does the building owner see?

Their buildings, their comfort, their bill, and nothing else. Each customer signs in to a TagoRUN portal showing their units, the heat delivered, the efficiency record behind the guarantee, and the invoices, isolated by Access Management policies and branded with the Custom Domain & Whitelabel add-on, with your own app on the stores through the Custom Mobile App add-on. For a maker selling heat by the kWh, that screen is the product the customer touches daily, and it carries your name, not a platform’s. Behind it, your service organization sees the fleet by model and climate: which refrigerant circuits leak early, which installers’ sites drift first, what a healthy seasonal COP curve looks like per product line, the record that, as we argued in What Makes a Moat in IoT, no rival can reproduce without your installed base.

Frequently asked questions

Can units already installed be connected? Yes. Add-on sensors for temperature, pressure, current or energy retrofit over LoRaWAN, cellular, satellite or other supported networks. New units send from the controller over MQTT or HTTP.

Our controller uses its own data format. Does it matter? No. A payload parser converts it into named variables as messages arrive.

Can each building owner see only their own units? Yes. Access Management policies isolate every customer in a TagoRUN portal, under your domain with the Custom Domain & Whitelabel add-on and in your own mobile app with the Custom Mobile App add-on.

How is heat billing computed? An Analysis totals heat delivered, cooling delivered or run hours per customer per month and posts the figures to your billing system over HTTP.

What keeps the thresholds honest across seasons? Trained models in TagoIO Analytics learn each unit’s seasonal baseline, so a COP that is normal in January does not false-alarm in May.

Is the platform reliable enough for a billing contract? TagoIO runs on AWS in the US or the EU with a 99.9% uptime SLA for eligible accounts, ISO 27001 certified and GDPR compliant. Details at tago.io/trust.

The commissioning report that never ends

Pick one product line and make one promise: the efficiency this machine shipped with is the efficiency it will keep, proven monthly. The Heating & Cooling solutions page walks the whole build, from the first connected heat pump to the kWh invoice under your brand. One number, watched forever, carries the service plan, the guarantee, and the new business model.