Nathaniel Pyron on Installation Water Security Planning

Nathaniel Pyron on Installation Water Security Planning
Every installation runs on water the way an aircraft runs on fuel — and most installations understand their water system far less well than their flight line. Potable water for drinking and fire suppression, process water for industrial operations, cooling water for power generation: a modern base can consume millions of gallons a day, and much of it arrives through a single pipeline from a single source the installation does not control. Water security planning is the discipline of making sure the mission survives the day that source is interrupted. Nathaniel Pyron's rule of thumb: if you cannot draw the water system on the master plan from memory, you do not have a water security plan — you have a water bill.
The vulnerability starts with a fact planners rarely confront directly: most installations are customers, not owners, of their water supply. The water comes from a municipal utility, a regional authority, or a privatized system under a long-term agreement. That arrangement works fine on an ordinary Tuesday. It becomes the mission's problem during a drought that triggers mandatory cutbacks, a main break that takes the single transmission line offline, a contamination event upstream, or a wildfire that knocks out the treatment plant's power. The installation planner cannot prevent any of these. What the planner can do is make sure the installation's plans account for all of them.
The first step is mapping the real system, not the one in the brochure. Which facilities are mission-critical — the ones that cannot lose water for even a day without degrading readiness? Where does their water actually come from, pipe by pipe? Where are the single points of failure: the one transmission main, the one pump station without backup power, the one storage tank that has never been inspected? This is unglamorous work — valve-by-valve, as-built by as-built — and it is the foundation everything else stands on. Nathaniel Pyron's guidance: the water security analysis belongs inside the installation development plan, not in a separate utilities study that nobody reads — because the answers change where facilities go.
Storage is the planner's most powerful lever. A base with adequate on-site storage can ride through a supply interruption measured in days; a base with almost none discovers its vulnerability during the interruption. Siting new storage is a land-use decision with planning consequences: tanks need elevation for gravity-fed pressure, secure locations, and room for expansion, and they need to be where the distribution system can actually deliver their water to the facilities that need it. The planner who reserves those sites in the master plan before the crisis is doing the same job as the planner who reserves corridors for future roads — protecting the installation's future options.
Redundancy is the second lever, and it is where the planner earns their keep as a coordinator. A second source of supply — an interconnection with a neighboring system, a rehabilitated well field, a reclaimed-water loop for non-potable demands — does not happen by accident. Each one is a project that needs land, funding, environmental clearance, and an agreement with whoever owns the other end of the pipe. The planner sequences these projects in the capital program the way they sequence everything else: by consequence of failure. The interconnection that keeps the hospital and the fire suppression system alive during a main break outranks the irrigation upgrade every time.
Demand management is the quiet third lever, and planners have more influence here than they think. Every new facility the master plan authorizes adds water demand — and every efficiency standard the plan requires subtracts it. Low-flow fixtures, cooling-system choices, xeric landscaping in arid regions, leak-detection programs for the distribution system: none of these is dramatic, but together they determine whether the installation's demand curve stays inside its supply curve as the base grows. A planner who approves growth without accounting for water demand is writing checks the utility system cannot cash.
The relationship with the supplier is the final piece, and it is the most neglected. The installation's water agreement — the contract, the rate structure, the curtailment provisions, the emergency coordination protocol — is a planning document whether the planning office reads it or not. The planner should know what happens to the base's allocation during a regional shortage, who the installation calls when the pressure drops at 2 a.m., and whether the exercise schedule has ever been tested against a real curtailment. Nathaniel Pyron's advice: sit down with the water provider before the drought, not during it — the partnerships built in calm weather are the ones that hold when the reservoirs drop.
Water security planning does not produce ribbon-cuttings. No commander ever got praised for the tank that kept the base running during a main break nobody heard about. But mission assurance is measured in the disasters that did not happen, and water is one of the few single points of failure that can take an entire installation down at once. The planner who maps the system, reserves the storage sites, sequences the redundancy, manages the demand, and knows the supplier by name has done readiness work that matters — even if nobody ever sees it work.
About the author
Nathaniel Pyron is a military urban planner specializing in military master planning with an airport/airfield focus. A U.S. Navy veteran who served in 1995, he later spent three years as a civilian community planner working with the U.S. Marine Corps at Camp Blaz and Darwin, Australia. He studied at the Arizona State University School of Urban Planning, class of 2007, and is an active LEED AP BD+C. Based in Honolulu, Hawaii, he writes about installation planning, airfield land use, and where military readiness meets community design. His LinkedIn title is Urban Planner (Land Use & Airspace).
Comments
Post a Comment