Intermittently operated pumps start and stop with demand, keeping wells efficient by refilling storage and maintaining pressure. They’re less suited to continuous heating or constant sump removal. Understanding duty cycles helps you design smarter building water systems.

Multiple Choice

Which is a common application for intermittently operated pumps?

Intermittently operated pumps are designed to start and stop with demand rather than run nonstop. The best fit here is drawing water from wells because a well supply isn’t a constant flow—the pump only needs to run to refill a storage tank or to maintain system pressure, starting when pressure drops and stopping when the tank is full. This on-off cycling matches how a well system is used in everyday water supply, maximizing efficiency and reducing wear. Other tasks don’t align as cleanly with this on-demand behavior: heating water typically involves a continuous or controlled circulation to meet steady heating needs, and sump pumps are focused on removing water as it enters, often with different duty patterns rather than the on-demand, pressure-triggered cycling seen with well pumping.

Intermittently operated pumps are one of those quiet workhorses in modern building automation. They aren’t flashy or glamorous, but they’re the kind of device that quietly makes systems reliable, efficient, and easier to manage. When you’re designing or troubleshooting Level II automation, understanding how these pumps decide when to start and stop can save you headaches, wear, and wasted energy.

What “intermittent” really means in a pumping system

Think of an intermittent pump as a traffic controller for water. It doesn’t run all the time; it kicks into gear when there’s a need and steps back when the need dissipates. In many buildings, the signal that prompts a pump to start is a pressure drop or a tank level that falls below a set threshold. Once the target level is reached or pressure is restored, the pump takes a break. This on-off cycling is a natural fit for systems where demand fluctuates, or where water storage acts as a buffer.

This behavior contrasts with continuous-duty pumps, which run steadily to satisfy constant flow requirements. In the quiet rhythm of a well-fed building or facility, intermittent operation reduces wear and energy use because the motor isn’t spinning full tilt all day, and it gives the system a little breathing room between cycles.

A common scenario: water from wells getting a helpful boost

One of the most typical applications of intermittently operated pumps is drawing water from wells. Here’s why this pairing makes so much sense. A well supply often doesn’t deliver a constant gush of water. It fluctuates based on groundwater levels, usage patterns, and seasonal changes. You don’t need a pump running continuously to maintain a comfortable baseline pressure or fill a storage tank. You need it when the pressure dips or when the tank’s water level drops sufficiently, and you want it quiet and efficient in between those moments.

In practice, a well-fed system might have a storage tank or a distribution loop that serves the building. The level sensor or pressure sensor in the tank acts as a watchdog: when the level falls below a set point, the controller sends a signal to the pump to start. After the tank is topped up, or the pressure is restored to the desired value, the pump shuts off. The result is a clean, predictable duty cycle that matches actual demand, rather than a constant hum that doesn’t reflect reality.

Why this approach matters for energy and longevity

  • Energy savings: Pumps consume significant power, and starting currents can be high. By cycling on only as needed, you reduce both energy usage and thermal strain on the motor. Modern variable-frequency drives (VFDs) or soft-start controllers can further smooth transitions, lowering electrical stress and extending motor life.

  • Wear and tear: Startups are rough on mechanical parts. When a pump runs intermittently, you can design the control logic to minimize rapid cycling and pressure spikes, which helps prevent premature bearing wear, impeller damage, and valve chatter.

  • System balance: Storage tanks and pressure tanks act as buffers. They absorb short-term demand fluctuations, letting the pump turn on briefly and off again rather than fighting against sharp changes in flow demand. That buffering is a core principle in Level II automation—manage the variables, don’t chase them in real time with brute force.

Control strategies that make intermittent pumping robust

  • Pressure-based control: The simplest approach uses two setpoints—cut-in and cut-out. When pressure falls to the cut-in point, the pump starts; when it reaches the cut-out point, it stops. This method is intuitive and reliable for well-mourced water systems.

  • Tank-level control: If you have a storage tank, level sensors can govern the pump. The pump starts when the tank level dips below a lower threshold and stops when it’s buffered up. This can be especially effective in buildings with fluctuating water use, delaying the need to pump until it’s meaningful.

  • Time-based sequencing: In some installations, you’ll see a time-based element layered in, especially when there are multiple pumps or when supply and demand patterns follow predictable daily rhythms. The idea is to avoid simultaneous starts and spread the load, minimizing electrical peak demand.

  • Flow and demand forecasting: More advanced systems try to anticipate demand by analyzing past usage patterns. The controller can preemptively run a pump to prevent pressure drops during anticipated high-use periods. This is where Level II automation shines—combining sensor data, historical trends, and intelligent sequencing.

Sensors, safety, and reliability in the mix

  • Sensors you can trust: Pressure transmitters, level sensors, and clean, well-maintained control cabinets matter. If sensors drift or fail, the whole story changes—the pump could short-cycle, run dry, or miss a critical refill. Regular calibration and redundancy in critical points help keep the system honest.

  • Protection features: Overload protection, dry-run protection, and proper motor protections aren’t cosmetic add-ons. Without them, you’re looking at nuisance trips, shortened lifespans, and unexpected outages.

  • Startup/shutdown logic: A smart controller will consider the duration of a pump run and the time since the last start. Short, frequent starts aren’t ideal, so many intelligent controls implement a minimum on-time or a dead-band to prevent chattering.

Maintenance mindset: keep the cycle healthy

  • Inspect and calibrate: Check sensors and confirm setpoints are what you intend. Small drift can turn an efficient system into a headache generator.

  • Valve health: Check check valves and pressure-relief devices. If a valve leaks or sticks, the pump may work harder than it should, or it could fail to shut off cleanly.

  • Vibration and alignment: If you hear unusual noises or see vibrations, it’s a sign something’s off with mounting, alignment, or impeller wear. Address it before it leads to bigger problems.

  • Battery backups and power quality: Fluctuations in power can cause unnecessary starts or misreads of sensor data. A stable power supply and, where appropriate, a backup option help keep the cycle consistent.

From theory to practical layouts

When you’re designing a building automation plan, the intermittent-pump concept isn’t a single component; it’s part of a broader network of controls that make an entire system more predictable and manageable. Here are a few practical threads you’ll encounter:

  • Integration with building management systems (BMS): The pump controller talks to the BMS through standard communication protocols. This lets facility managers see pump status, history, and alarms from a single dashboard. It also allows coordinated actions—like coordinating pump starts with other water-using systems to avoid pressure fluctuations.

  • Redundancy and reliability: In critical facilities, you’ll see multiple pumps with a priority and back-up scheme. The lead pump handles normal demand, while one or more standby pumps take over if the lead fails or if demand spikes. The control logic maintains seamless operation during transitions.

  • Energy dashboards: Data on pump runtime, energy consumption, and cycle counts can feed into dashboards that highlight efficiency trends. This isn’t just nerdy data for data’s sake; it helps managers identify opportunities to trim waste, schedule maintenance, or adjust setpoints to better align with actual usage.

  • Water quality considerations: In well systems, water quality parameters can influence pump operation. For example, if iron content or particulates affect intake, you might add filtration or pre-treatment stages, with the pump cycling in harmony with system readiness rather than fighting against a dirty inlet.

A few soft truths about the real world

  • Every system is a little different. A rule that works beautifully in one building might need tweaking in another. The beauty of intermittent pumping is its adaptability; you don’t need to run a system like a railroad—just smartly timed pulses that match the needs.

  • It’s easy to over-engineer. Sometimes the simplest control—two pressure setpoints, a decent sensor, and a reliable pump—gets you most of the way there. Complexity has its place, but it’s worth pausing to ask whether it delivers tangible benefits.

  • The human factor matters. Operators who understand the logic behind on-off cycling tend to maintain what they’ve built more thoughtfully. Clear alarms, intuitive dashboards, and straightforward maintenance checklists make life easier for everyone involved.

A quick mental model you can carry into a project

  • Look for buffers first: Does the system have a storage tank or a pressure reservoir? If so, intermittent pumping is a natural fit.

  • Match the signal to the need: If the goal is to maintain steady pressure with variable demand, a pressure-based cut-in/cut-out is king. If the goal is to refill a tank, level-based control wins.

  • Protect the heart of the system: Ensure sensors, wiring, and motor protections are solid. A well-protected system is more reliable and easier to diagnose when something drifts off course.

  • Plan for the future: If you expect demand to grow, design with modularity in mind. It’s easier to add a spare pump, upgrade sensors, or bring in smarter logic later than to retrofit a stubborn setup.

In the end, intermittently operated pumps embody a practical philosophy: let the system respond to real needs, not pretend demands. When a well supplies a building, the power of automation reveals itself in the steady hum of a pump that starts when water is needed and rests when it isn’t. It’s a quiet dance—one that makes buildings safer, more efficient, and a little bit wiser about when to push and when to pause.

If you’re curious about how these principles scale to larger facilities or more complex networks, the same logic underpins many Level II strategies. You’ll see the same themes repeated: buffers that smooth demand, sensors that tell a reliable story, and controls that keep the whole system speaking in a common language. The result isn’t flashy, but it’s profoundly practical—a reminder that good automation isn’t about never stopping; it’s about stopping at the right moments. And in the world of building systems, those right moments often revolve around water, pressure, and the quiet stewardship of energy.