Every filter stage in your fleet on one timeline, dated from the water actually running through it. Due stages grouped into site visits. The work order raised with its parts list — before the espresso machine, the ice maker or the RO skid pays for it.
21 of the last 22 work orders opened themselves · No hardware needed to start
Built for the equipment water touches
Filters changed too early are money in the bin. Filters changed too late are a boiler, a membrane, or a customer. The timeline replaces the sticker date with three real dates — and turns the fleet's due stages into planned trips.
Every stage carries three clocks — the plan, the rating walked through real gallons, and the chemistry load. The earliest honest one governs. Nothing is averaged away.
The fleet view groups every due stage into site visits. Three stages due in the same fortnight at Camelback become one drive, one parts pull, one invoice line.
A 6-hourly sweep raises deduplicated replacement orders with the readings, the clock that governed and the cartridge to bring. Completing the task resets the clock.
A carbon block rated for 9,000 gallons at 150 ppm is not a 9,000-gallon block at 486 ppm. The timeline walks every rating through this site's real throughput and chemistry — and shows where the plan and the physics part ways.
RULE+S governs Stage 2. Rated to 12 Nov, metered to 24 Oct, chemistry-forecast to 24 Sep.
Per location, the Operations view turns the raw telemetry into the four things a manager actually asks — how good is the water, how long until the next replacement, is the membrane still rejecting, and is anything sneaking past the filtration.
Every filtration system opens to two panels: what is inside it — the stage sequence, media and micron ratings — and what it feeds: every device downstream, with the site each one actually sits in. That second list is the one a technician is after, and it is the one a spreadsheet cannot draw.
A LiquosLabs device reports TDS, hardness, throughput and leak events every 20 minutes — matched to the site by name, address and geography.
Rules with a memory: membrane rejection below 90% for 7 consecutive days. One bad bucket never wakes anyone.
Calendar plan, factory rating through real gallons, and chemistry exposure — side by side, with the governing one named.
Readings, the rule it broke, the clock that governed and the parts to bring — in the body. Completing the task resets the clock.
Seven KPI suites as one wheel: a segment per suite, its fire count, and the reason beside it. Click a segment and you're in that board, at that site — composed in 0.47 seconds from the same cached services, so the wheel can never disagree with the boards it links to.
— all in the same panel, one click apart.
A fixed interval is wrong in both directions: on soft water you throw away cartridges with life left; on hard, high-TDS water you run them past exhaustion and pay for the equipment behind them. Three clocks per stage put the replacement where the consumption actually is, and grouping due stages into site visits means one trip instead of three.
No. Start with the catalogue, your asset list and the municipal water data already held for each site — that alone corrects most intervals. Add LiquosLabs metering where the equipment is expensive enough to justify watching live.
Every user holds memberships scoped to a level of the hierarchy, each carrying a role. A branch manager sees their branch; a national account admin sees the whole account; a contractor sees only their assigned work. Modules a user has no capability on never appear in their panel at all.
Contacts, parts, assets, work orders and water tests import from CSV or Excel through a wizard that audits every row — imported, held for review, or failed with the reason. Nothing silently becomes a guess.