Field guide · assembly comparison

RPZ vs. DCVA vs. PVB: what the assembly types protect against

RPZ, DCVA, and PVB are not interchangeable labels. Their construction and protection limits differ, and a local water system or authority—not a generic comparison chart—decides what is permitted for a particular hazard and installation.

The short comparison

An RP or RPZ assembly uses two checks and a relief valve and is commonly used where both backsiphonage and backpressure protection are needed, including high-hazard situations under many programs. A DCVA uses two checks and is commonly limited to lower-hazard applications. A PVB uses an air inlet to break a vacuum and protects against backsiphonage, not backpressure. An SVB is in the pressure-vacuum-breaker family and has the same backsiphonage-only boundary.

Those are functional descriptions, not an installation recommendation. Local codes, water-system policy, product approval, elevation, drainage, service conditions, and hazard classification can change what is allowed.

Sources for this section: EPA: Cross-Connection Control Manual; Washington Administrative Code: cross-connection control; California State Water Resources Control Board: Cross-Connection Control Policy Handbook (April 2026).

Compare the assemblies by function, not by a product nickname

Function and limits at a glance
RP / RPZPressure conditions addressed:Backpressure and backsiphonage.Important boundary:Has a relief valve; drainage, access, approval, and local installation rules matter.
DC / DCVAPressure conditions addressed:Backpressure and backsiphonage in lower-hazard applications under EPA guidance.Important boundary:Do not infer low hazard from the device already installed; the receiving program classifies the service.
PVBPressure conditions addressed:Backsiphonage.Important boundary:Does not protect against backpressure and depends on its required elevation and installation conditions.
SVBPressure conditions addressed:Backsiphonage.Important boundary:A spill-resistant vacuum-breaker family still requires the locally accepted field procedure and installation context.

Sources for this section: EPA: Cross-Connection Control Manual; EPA: Protecting Water Quality through Cross-Connection Control and Backflow Prevention; USC Foundation: Field-test training tools; California State Water Resources Control Board: Cross-Connection Control Policy Handbook (April 2026).

Four facts to take to the authority before selecting or replacing one

  • The protected service and the actual or potential contaminant source—not just the building type.
  • Whether backpressure, backsiphonage, or both are credible at that point in the system.
  • Whether the installation offers the required elevation, drainage, clearance, orientation, and access for the proposed assembly.
  • The exact make, model, size, and approval listing the water system or authority accepts at the time of work.

Sources for this section: EPA: Cross-Connection Control Manual; USC Foundation: Approval Program; Washington Administrative Code: cross-connection control; California State Water Resources Control Board: Cross-Connection Control Policy Handbook (April 2026).

Different families produce different field records

The assembly type determines the field-test procedure and the readings that belong on a record. An RP record includes relief-valve information; a DCVA record records both check valves; a PVB record addresses its air inlet and check. A form that uses the wrong reading set is not made correct by changing the label at the top.

The baseline math used by a tool may be useful for organizing a record, but only the receiving authority's accepted procedure and form determine whether a result is accepted. That is why the pages below stay separate instead of treating every assembly as one generic test.

Sources for this section: USC Foundation: Field-test training tools; Washington State Department of Health: Backflow prevention assembly field test report; Texas Commission on Environmental Quality: Cross-connection control and backflow prevention.

Keep the comparison current

Product approval lists, local policies, and active code editions change. USC describes its own approval process and publishes information about approvals, but a USC listing is not a substitute for the model and policy accepted by the service's water system. Likewise, a state example can explain a rule structure but does not travel automatically to another state.

For a replacement, retain the decision source, permitted model information, installation approval, and the first test report in the same property record. That makes the next review less dependent on memory or a disconnected PDF.

Sources for this section: USC Foundation: Approval Program; Washington Administrative Code: cross-connection control; Texas Commission on Environmental Quality: Cross-connection control and backflow prevention.

Sources and review boundary

This guide was reviewed on August 22, 2026. It links to primary public sources where possible and labels state and local examples as examples. It is educational material, not engineering, legal, installation, certification, or water-system approval advice.

Continue with the right next question

Fill this out on the phone instead.

The generator asks for exactly these fields, grades every differential as you type, opens repair and retest fields when something fails, and hands you the finished one-page PDF. No account, no install, works with no signal.