Does it work out how much a failed trap is costing?

No, and there is no field that could. A saving figure produced from a tag count and a generic assumption is a number nobody should be quoting. What a trap is worth replacing is between you and whoever surveyed it.

How does it decide a trap has failed?

It does not. The finding is whatever your survey said, in the surveyor's words. CompliMaint defines no failure criteria and grades nothing.

How often should traps be surveyed?

This product states no interval. It depends on the system and on what your last survey found.

Can I keep the trap population separately from the survey?

That is exactly the shape: the trap is the row and persists, and each survey's finding is recorded against it with a date.

Is anything transmitted?

No. Traps and findings stay in this browser.

Steam trap survey register

The traps you have, what your survey said about each — and what was done about it.

The tag is the row, and it persists

A trap survives many surveys. Keeping the population as the register, with each survey's finding recorded against the trap, is what makes “this one has been reported blowing through three years running” visible at all.

The finding is the surveyor's word

Blowing through, cold, cycling, holding — whatever your survey actually said. CompliMaint defines no failure criteria and grades nothing, because how a trap's condition is determined depends on the survey method and the person doing it.

No saving is calculated

There is no steam loss, energy cost or payback figure in this tool, and no field for one. A saving produced from a tag count and a generic assumption is a number that ends up in a business case with nobody behind it. What replacing a trap is worth is between you and whoever surveyed it.

Kept alongside: Boiler log · Thermal imaging survey log · Corrective action register

A register of steam traps and survey findings, kept per building on your device. The finding is the surveyor's own description. CompliMaint defines no failure criteria, sets no survey interval, and calculates no steam loss, energy cost or payback — there is no field for one. Everything runs on your device.

Questions people ask

Does it work out how much a failed trap is costing?: No, and there is no field that could. A saving figure produced from a tag count and a generic assumption is a number nobody should be quoting. What a trap is worth replacing is between you and whoever surveyed it.
How does it decide a trap has failed?: It does not. The finding is whatever your survey said, in the surveyor's words. CompliMaint defines no failure criteria and grades nothing.
How often should traps be surveyed?: This product states no interval. It depends on the system and on what your last survey found.
Can I keep the trap population separately from the survey?: That is exactly the shape: the trap is the row and persists, and each survey's finding is recorded against it with a date.
Is anything transmitted?: No. Traps and findings stay in this browser.