Every state has its own unique cultural, environmental, and regulatory factors that impact utilities, including when it comes to cross-connection control. And Florida is no different. State requirements, community quirks, and varied local resources all play a role in how Florida utilities address the risks of backflow.
At a high level, Florida Administrative Code (Rule 62-555.360) requires:
- Annual testing of all backflow assemblies
- Annual submission of a cross-connection report to the Florida Department of Environmental Protection (FDEP) for systems serving a population of 10,000+
- A comprehensive cross-connection control program for areas served by reclaimed water systems (62.610.419)
Most utilities in Florida focus their efforts on the annual testing of backflow assemblies. Not only does it apply to every public water system, but backflow testing is familiar, tangible, and well-defined. But what happens when knowledge gaps keep your utility from being able to effectively test, track, and report on the backflow assemblies within your system?
Cross-Connection Control Programs:
The Essentials Guide
You Can’t Test What You Don’t Know
Since on-site surveys aren’t always required, many Florida water systems face significant holes in their data that make effective backflow prevention a challenge. It’s a tale as old as time: You have to test assemblies, but you don’t have a complete and accurate picture of your system. These utilities often don’t know how many assemblies exist within their system or where they’re located. And that makes testing impossible.
A lot of public water systems in Florida also face inadequate knowledge on the residential side of things. With limited authority or insufficient permitting processes, utilities may be unaware of changes that increase the threat of backflow contamination. Residents install irrigation systems—a high-hazard connection—without alerting their utility. That results in two potential problems: Either they don’t install a backflow prevention assembly, creating a serious hazard to the distribution system, or they install an assembly unbeknownst to the utility, leaving it out of the testing cycle.
The communities at the highest risk are those experiencing significant growth and development, which is increasingly common in the state. So, what’s the solution?
Bridging the Gap to Compliance
If you don’t know where and what backflow prevention assemblies exist in your public water system, you need to find them. The best (and, really, only) way to do that: on-site surveys where trained, certified surveyors put eyes on service connections and inventory backflow prevention.
Proactive public water systems who have identified this issue will often develop a comprehensive cross-connection control program, regardless of whether the state requires that for them. No matter the regulatory requirements for your specific utility (i.e., even if your utility does not include a reclaimed water system), a good cross-connection control program underpins all backflow prevention activities and keeps you compliant elsewhere.
An effective program includes:
- A written plan, backed by a local ordinance that establishes enforcement authority
- On-site surveys that proactively identify and document cross-connections and backflow preventers
- Backflow assembly test tracking based on identified inventory
- Ongoing enforcement to ensure compliance with state regulations and the local ordinance
A plan, process, and overall program that allows you to find and track backflow assemblies helps you stay compliant with FDEP requirements. Plus, taking proactive steps to identify hazards in your distribution system helps you prevent backflow—which is cheaper and easier than responding to a contamination event.
Don’t wait until you’re labeled non-compliant by the state; make sure you have the information you need to trust that the backflow prevention in place effectively protects your system and your community.
Ready to learn more about how HydroCorp can support utilities in Florida with cross-connection control, backflow testing, and FDEP compliance?
