Frequently Asked Questions
Do public restrooms benefit from touchless faucets compared to manual fixtures?
In high-traffic washrooms, touchless use reduces touchpoints and supports consistent shutoff behavior; performance depends on correct installation, power stability, and commissioning.
See details
Which environments should prioritize touchless fixtures first?
Prioritize airports, schools, healthcare, stadiums, and transit facilities where frequent users and rapid turnover amplify hygiene and maintenance advantages.
Read more
Which commissioning checks should be required for public restroom turnover?
Validate activation reliability, false-trigger resistance, shutoff response, run-time behavior, and flow at design pressure under final lighting and finished surfaces; document results for closeout.
See commissioning criteria
Which issues most often cause touchless faucets to stop working suddenly?
Sudden failure is commonly low power, sensor obstruction, loose connectors, or supply closure—verify power first, then sensor path, then solenoid/valve actuation.
See diagnostics
Which symptoms indicate a pressure/flow-path problem rather than a sensor problem?
Weak flow, unstable stream, or intermittent output often points to pressure instability, clogged aerators, or blocked screens—service the hydraulic path before replacing electronics.
See issue guide
Which power selection best matches continuous public-restroom duty cycles?
Choose power based on voltage stability under solenoid load and maintenance access; higher-duty applications often benefit from AC/hybrid planning to reduce voltage-sag risk.
See power options
Which preventive maintenance schedule keeps public restrooms reliable?
Use usage-based PM: frequent sensor window cleaning, scheduled aerator/strainer service, periodic voltage checks, and verification of shutoff/latency to prevent drift and downtime.
Maintenance guide
Which specification mistakes most often create user complaints in public restrooms?
Common pitfalls include skipping commissioning requirements, mismatching power strategy to usage, ignoring basin/counter geometry for activation-zone alignment, and omitting service access.
Specifier notes