Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm PRV type (standpipe hose-valve PRV vs. sprinkler supply PRV) since inspection/test scope differs slightly by application
Perform the annual inspection confirming normal valve position, accessibility, and gauge function
Every 5 years, perform the full-flow test: flow the valve at its design flow rate and confirm outlet pressure stays within the valve's listed regulation range under real flowing conditions rather than only static, no-flow pressure
Compare full-flow results to the original acceptance test/design values to detect a valve that regulates properly at rest but fails or chatters under actual flow
Document any deviation for adjustment or replacement, since a malfunctioning PRV can either starve downstream demand or over-pressurize downstream piping/hose
Known gotchas
A PRV that reads correctly on a static gauge check can still fail badly once actual flow is introduced -- the 5-year full-flow test exists specifically because static checks alone give a false sense of compliance
Full-flow testing a standpipe PRV requires an actual water discharge (hose stream or test header) at significant flow, which is logistically and safety-intensive on a high-rise standpipe -- not a quick annual-style visit
An over-pressurizing (failed) PRV on a standpipe is a life-safety hazard to firefighters using the hose connection under fire conditions, not just a paperwork issue, and should be escalated with appropriate urgency
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?