Test dry-pipe/preaction system low air (or nitrogen) pressure supervisory alarms
domain: NFPA 25 ch. 13, dry/preaction air supply supervision · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm the system's required normal air/nitrogen pressure range and low-pressure alarm setpoint from the dry pipe valve's trip chart/manufacturer data
Check system air/nitrogen pressure against the required range on the gauge at the frequency appropriate to whether a functioning low-air supervisory alarm is present
Functionally test the low-air supervisory alarm by slowly bleeding air pressure down and confirming the signal transmits to the monitoring station before pressure drops low enough to risk a false trip
Restore system air/nitrogen pressure to the correct operating range using the compressor or nitrogen generator, confirming the air maintenance device (if present) cycles correctly
Document alarm activation pressure versus the required setpoint and the time taken to restore normal pressure after the test
Known gotchas
A dry system relies on maintaining a pressure differential above the trip point to stay set -- bleeding pressure too far or too fast during a supervisory-alarm test can accidentally trip the dry valve
Where a compliant, monitored low-air supervisory alarm exists, NFPA 25 allows less frequent manual gauge checks than an unsupervised system requires -- applying the same schedule to every dry system regardless of supervision either wastes effort or under-checks a system that needs weekly attention
Nitrogen-inerted systems, increasingly used as an MIC-prevention retrofit, have different normal operating pressures and generator maintenance items than compressed-air systems -- applying compressed-air baselines to a nitrogen system will misdiagnose a normal reading as a fault or vice versa
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?