Reference · built on requestOperator by FibricSafety, security & compliance

Legionella Flush

Finds low-use outlets and out-of-range water temperatures and proposes flush tasks and log entries for your water management plan.

Request accessPricing ↗

About

Legionella Flush is an operator job for the outlets in a building that nobody has run for days and the water temperatures that have drifted out of the range your plan sets. It reads hot and cold water temperatures from Tridium Niagara or Johnson Metasys points, or from Monnit, SensorPush, and Disruptive Technologies sensors on tanks and returns. It reads which rooms have been vacant from the property system: Oracle OPERA Cloud, Mews, or Cloudbeds. It reads the flush and temperature tasks already completed in your maintenance system.

It then proposes flush tasks per outlet, investigation tickets for readings out of range, and the log entries your water management plan needs. A person approves the tasks, does the work, and signs the log.

This is a reference listing. It documents what Fibric would read from Legionella Flush 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

  • Hot water flow and return temperatures and cold water temperatures from Tridium Niagara or Johnson Metasys points, with their timestamps
  • Temperatures from Monnit sensor messages, SensorPush samples, and Disruptive Technologies temperature events on tanks, calorifiers, and returns
  • Room occupancy: reservations and housekeeping room status from Oracle OPERA Cloud, resource states from Mews, and housekeeping status from Cloudbeds
  • Completed and overdue work orders in MaintainX, UpKeep, or Limble CMMS for flushing and temperature checks, by outlet or asset
  • The outlet register you keep: each outlet, its room, its riser, and the flushing interval your plan assigns
  • Days since each outlet was last used, derived from room occupancy and the last completed flush

Proposed actions

  • Target capability: propose a flush work order per outlet that has passed the interval your plan sets, in MaintainX, UpKeep, or Limble CMMS
  • Target capability: propose an investigation ticket when a hot or cold reading falls outside the range your plan sets, with the readings attached
  • Target capability: propose a log entry for the water management plan record once the task closes, for the responsible person to sign
  • Target capability: propose a weekly list of outlets and readings due or overdue, to the channel your facilities team watches

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

What you can build

  • Flush guest rooms empty for a week

    Rooms with no reservation in Oracle OPERA Cloud for longer than your plan's interval get one MaintainX flush work order each, listing the outlets, for housekeeping to run.

    With Oracle OPERA Cloud, MaintainX

  • Catch a calorifier drifting low

    A Monnit temperature sensor on the hot water storage reports below the range your plan sets. The operator proposes an UpKeep ticket with the readings and a Teams notice to the engineer.

    With Monnit iMonnit, UpKeep, Microsoft Teams

  • Keep the plan log from the BMS

    Return temperatures from Niagara points are read each day. The operator proposes the log rows your plan requires in Google Sheets, one per riser, for the responsible person to sign.

    With Tridium Niagara, Google Sheets

  • Work from Mews resource states

    Mews resources left Clean with no reservation become low-use outlets after your interval. Flush tasks go to Limble CMMS and a note lands in Slack.

    With Mews, Limble CMMS, Slack

Requirements

  • A temperature source: Tridium Niagara or Johnson Metasys points, or Monnit, SensorPush, or Disruptive Technologies sensors
  • An occupancy source for low-use detection: Oracle OPERA Cloud, Mews, or Cloudbeds, or a room usage sheet
  • One maintenance connector for flush tasks: MaintainX, UpKeep, or Limble CMMS
  • Your water management plan's outlet register, intervals, and temperature ranges, entered in the operator's configuration
Authentication
Reads points, sensors, and room status through the connectors you bind, and writes tasks and log rows through the maintenance and file connectors' credentials; it holds none of its own.

Limits

  • It does not sample or test water. Legionella testing, disinfection, and the plan itself remain with your responsible person
  • Low use is inferred from occupancy and task records. A room used without a reservation, or a flush done and not logged, reads as unused
  • Temperatures are read only where a sensor or point exists. Outlets with no sensor get flush tasks by interval, not by reading
  • It never changes a setpoint, opens a valve, or doses a chemical

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 Legionella Flush ↗

Questions and answers

What does the responsible person approve?
Each flush task, investigation ticket, and log row. You see the outlet, the days since use or the reading that triggered it, and the task text. You approve it, change it, or dismiss it. The log is signed by the person who did the work.
What does the plan log receive?
A receipt per outlet: the readings and occupancy read, the interval applied, the task proposed, who approved it, what was written to the maintenance system, and the log row filed. Dismissed proposals stay on file with the reason.
Does it replace a water management plan?
No. The plan names the outlets, intervals, temperature ranges, and responsible person. The operator applies those settings to the readings and records it can reach, and proposes work. Testing, disinfection, and sign-off stay with people.
Ask about Legionella Flush

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