Writing an RFP for utility billing? How to specify private hydrant billing as its own service, with copy-ready requirement language.
For US Utilities serving 3,000-100,000 meters and for operations team, billing team and utility managers. For Heads of Billing who own collections accuracy and revenue leakage.
If you are writing a utility billing RFP, the private hydrant requirement is one vendors will answer vaguely unless you specify it precisely. Private hydrant billing means billing a customer-owned fire hydrant or private fire-protection service as its own distinct service, with its own rate, line item, and reporting, rather than folding it into a metered water account. The requirement to write is that the private hydrant behaves like every other service, with equivalent reporting and bill-print clarity, and that setting it up is configuration rather than custom development. This guide gives you the requirement language to paste into the RFP, what to verify in a demo, and the red-flag answers to score down. A capable utility billing platform meets all of it without a change request.
A private hydrant, or a private fire-protection service line, is not billed like metered consumption. It is a standby service: the utility guarantees water and pressure for fire protection whether or not any water flows, and charges for that availability. That is why it belongs on the bill as its own service rather than as a usage line on a water meter account. For water utilities specifically, this sits alongside the other rate lines covered in the water utility billing software overview.
What separates a private hydrant service from a standard metered account:
A California water district we work with bills base, service, capital, and private fire charges as separate lines on the same account. Private hydrant billing is that private-fire line handled as a first-class service.
Can the vendor report a private hydrant as its own service line, or is it stapled onto a water account?
The requirement is straightforward to state and surprisingly hard for older systems to meet: a private hydrant has to behave like every other service in the system, with equivalent reporting and bill-print clarity. This table breaks the requirement into what to write and what to verify in the demo.
Separate reporting is often the requirement that exposes an aging system, because private-fire revenue that cannot be isolated makes rate studies and regulatory reporting manual. The broader reporting discipline is covered in the water utility regulations and compliance software overview.
If you are drafting the RFP, paste these requirement statements directly. Each is written so a vendor has to demonstrate the capability rather than claim it, and each maps to a row you can score during evaluation.
Keep each statement as its own scored line in the RFP. A requirement bundled into a paragraph is one a vendor can answer with a single unverified "yes"; a requirement on its own line has to be demonstrated.
Private hydrants are one of several special services utilities bill outside the standard metered path, and they are easy to confuse with a temporary hydrant meter. Scoping the requirement correctly means naming which one you mean.
The row that matters most for scoping: a private hydrant is a permanent standby service, while a temporary hydrant meter is metered construction usage on a portable device. They are different requirements, and a system that handles one does not automatically handle the other.
Are you writing this into your requirements, or hoping the vendor already does it?
If you are drafting the RFP or an evaluation checklist, structure the private hydrant requirement in terms a vendor cannot answer with a vague yes. Write it in five steps:
Fold these into the wider evaluation using the utility billing software evaluation checklist, so private hydrants are scored alongside every other billing requirement rather than raised after selection.
How will you tell a real yes from a hopeful one?
When you score responses and demos, these answers mean the vendor cannot handle private hydrants as their own service, whatever the cover letter says:
Any one of these is the platform talking, not the requirement. The evaluation discipline that catches it before you sign is covered in the guide to choosing a utility billing system. The strongest evidence is a live demo: ask the vendor to add the service type, set its rate, and print a sample bill during the session.
SMART360 treats a private hydrant as a first-class service. You define the service type, its rate basis, and its bill presentation as configuration, so a private hydrant carries the same reporting and bill-print clarity as a metered water service.
That last row is the difference that shows up in the ten-year cost. On many legacy platforms, adding a service or changing a rate is a billable change request; on SMART360 a rate change is an admin task, not a procurement event. Island Water Authority went live in 10 weeks with a 92% reduction in billing errors because services and rates were configured in the platform rather than coded, and SMART360 is priced per connection for the 3,000 to 100,000 connection range.
Private hydrant billing is the practice of billing a customer-owned fire hydrant or private fire-protection service as its own distinct service on the utility bill, with its own rate, line item, and reporting. Because the service is billed on availability (a standby charge) rather than on metered consumption, it cannot ride the standard metered billing path and needs to be set up as a separate, non-metered service type.
Setting a private hydrant up as its own service keeps the standby charge transparent to the customer and keeps private-fire revenue reportable on its own for rate studies and audits. When the charge is stapled onto a metered water account, the revenue cannot be isolated, the customer cannot see it clearly, and rate changes become manual work. A separate service type gives the private hydrant its own rate schedule, reporting, and bill presentation.
State it in terms a vendor cannot answer vaguely: require the system to define a private hydrant as its own non-metered service type, with an independent rate schedule, a standby or connection-size charge basis, separate reporting for revenue and account counts, distinct bill-print presentation, and setup through admin configuration rather than custom development. Scoring these alongside every other billing requirement prevents surprises after selection.
A private hydrant is a permanent fire-protection service billed on a standby or connection-size charge with no meter read. A temporary hydrant meter is a portable meter placed on a public hydrant to measure construction water use, billed on consumption and usually against a deposit. They are different billing requirements, and a system that handles one does not automatically handle the other, so an RFP should name which it means.
Private hydrant billing is a small requirement that reveals a large truth about a billing platform: whether a new service is configuration or a vendor project. A utility should be able to define a private hydrant as its own service, give it its own rate and reporting, and present it clearly on the bill, without custom development each time the rate changes. That capability is part of a wider move off systems where every change is billable, covered in the utility billing software implementation guide. To see how SMART360 sets up private hydrants and other special services as configuration, book a demo.
Bynry Inc.
8 The Green STE.R,
Dover, Kent,
Delaware 19901
+1 732-630-0285
Bynry Inc.
Serene Tower, Pakharbaug
Pune, Maharashtra 411021
+91 93252-51217
