Reference · built on requestOperator by FibricFacilities & comfort

Hot Water Temperature

Watches hot water storage and recirculation return temperatures and proposes setpoint or flushing work orders.

Request accessPricing ↗

About

Domestic hot water has two numbers that matter and one that is rarely watched. OSHA's Legionella guidance says to store hot water at a minimum of 60°C (140°F) and deliver it at a minimum of 50°C (122°F) to all outlets, because the bacteria multiply between 20°C and 50°C. The storage tank is usually on the building management platform. The recirculation return, the far end of the loop, often is not.

Hot Water Temperature reads the tank, the loop return, and the sensors you add at distant outlets, over BACnet/IP, Modbus TCP, or LoRaWAN, and proposes a water heater setpoint change, a recirculation pump check, or a flushing work order in your CMMS when a reading falls outside the limits in your water management program. The engineer approves each one. It never changes a setpoint on its own.

This is a reference listing. It documents what Fibric would read from Hot Water Temperature and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Storage tank and water heater outlet temperatures, and the heater setpoint, as analog objects over BACnet/IP or from Niagara, Metasys, or Desigo CC
  • Recirculation return temperature and recirculation pump run state, over BACnet/IP or as Modbus TCP registers on the pump or controller
  • Temperature uplinks from LoRaWAN sensors strapped to pipes at distant outlets and dead legs, with battery and last-seen per sensor
  • Mixing valve outlet temperature where the valve reports it, so a scald-limited delivery is not read as a cold loop
  • The control limits and monitoring points from your water management program, entered per building
  • Open work orders on the heater, pump, or loop in Fiix, UpKeep, or Limble, so a known fault is not filed twice

Proposed actions

  • Target capability: propose a water heater setpoint change when storage sits below the limit in your program, sized to the limit
  • Target capability: propose a recirculation pump work order when the return temperature falls while storage holds, or the pump reports stopped
  • Target capability: propose a flushing work order for outlets and dead legs whose sensors read in the growth range for the period you set
  • Target capability: propose a monitoring log entry in your CMMS at the interval your program sets, with the readings, for the program record
  • Target capability: propose a sensor check when a pipe sensor reads flat for days or disagrees with the loop it sits on

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Watch the far end of the loop

    A LoRaWAN pipe sensor on the top-floor return reads below 50°C every morning while the tank holds 60°C over BACnet/IP. The operator proposes an UpKeep work order on the recirculation pump with both series attached.

    With LoRaWAN Network, BACnet / IP, UpKeep

  • Keep the program log without the clipboard

    Your water management program asks for readings at named points at the interval it sets. The operator proposes a Limble log entry with each reading from Modbus TCP and BACnet/IP, for the engineer to sign, and flags any outside its limit.

    With Modbus TCP, BACnet / IP, Limble CMMS

  • Flush the dead legs that stay warm

    Pipe sensors on a vacant wing read in the growth range for days. The operator proposes a Fiix flushing work order listing those outlets and the readings, and a note to check the loop's balancing valve.

    With LoRaWAN Network, Fiix

Requirements

  • A building management platform connector over BACnet/IP, or Niagara, Metasys, or Desigo CC, with the heater and loop points on its list
  • A Modbus TCP connector for pumps or controllers not on the building platform, or a LoRaWAN Network connector for pipe-mounted sensors
  • A CMMS connector such as Fiix, UpKeep, or Limble, with the heaters, pumps, and loops listed as assets
  • The control limits from your water management program, as ASHRAE Standard 188 describes, entered per building
Authentication
Reads temperature and pump points through the read allow-list of your BACnet/IP, Modbus TCP, or building platform connector, reads pipe sensors through your LoRaWAN network server key, and files work orders through the account your CMMS connector holds.

Limits

  • It reads pipe surface and tank temperatures. It does not sample water, culture Legionella, or replace the testing your program requires.
  • Setpoint proposals stay within the band you set and are checked against scald risk only where a mixing valve reports its outlet.
  • It proposes work orders and setpoints. It never writes a setpoint, starts a pump, or opens a valve.
  • Outlets without a sensor are not watched. A loop with one return sensor is judged at that point, not at every fixture.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Hot Water Temperature ↗

Questions and answers

What does a person approve?
Each setpoint change, pump or flushing work order, log entry, and sensor check. The proposal shows the point, the reading, the limit in your program it was checked against, and the exact change or work order text. The engineer approves, edits, or dismisses it.
What record is left?
A receipt per proposal: the readings and the limit cited, the setpoint before and after or the work order id in your CMMS, who approved it, and how to restore the previous setpoint. Log entries carry the readings as the program record.
Does it change a heater setpoint on its own?
No. It reads temperatures and writes nothing without approval. An approved setpoint change goes once through your building platform connector, within the band you set. Pumps and valves are never commanded; those go to a technician as work orders.
Ask about Hot Water Temperature

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy