Brake horsepower is the number that decides how big a motor a pump needs and how much electricity it will draw. It is the actual power delivered to the pump shaft, which is always more than the useful power the pump puts into the fluid because no pump is perfectly efficient. This guide explains what brake horsepower is, how it relates to hydraulic horsepower through efficiency, and how it links flow and head to the electrical load a SCADA system can watch.
Brake Horsepower in one line: Brake horsepower is the power that must be supplied to a pump's shaft to do its job, calculated as the hydraulic horsepower delivered to the fluid divided by the pump's efficiency. Hydraulic horsepower depends on the flow rate, the head, and the fluid's specific gravity; dividing by efficiency accounts for the losses inside the pump. Brake horsepower is the figure used to size the driver motor or engine, so it directly sets the electrical or mechanical load.
Hydraulic horsepower is the useful power the pump actually imparts to the fluid, and it is set by three things: how much flow the pump moves, how much head it adds, and how dense the fluid is through its specific gravity. Move more flow, lift it higher, or pump a heavier fluid, and the hydraulic horsepower rises. This is the output side of the pump - the work that leaves in the moving, pressurized liquid.
Brake horsepower is the input side - the power that has to arrive at the shaft to produce that hydraulic output. Because friction, turbulence, leakage, and mechanical losses inside the pump consume some of the shaft power, brake horsepower is always larger than hydraulic horsepower. The ratio between the two is the pump's efficiency, so brake horsepower equals hydraulic horsepower divided by efficiency.
The efficiency in that relationship is not a fixed number - it varies with where the pump is running on its curve, peaking near the best efficiency point and falling off toward the extremes of flow. That means brake horsepower for a given hydraulic output changes as the pump moves along its curve, which is one reason running near the best efficiency point keeps energy use down.
A pump does not run itself - it is turned by a motor, engine, or turbine, and that driver has to supply the brake horsepower the pump demands at its worst-case operating condition. Sizing the driver on hydraulic horsepower alone would leave it underpowered, because it would ignore the losses inside the pump. Engineers therefore use brake horsepower, with a margin, to select a driver that will not overload.
The subtlety is that brake horsepower changes with the operating point. For many pumps the brake horsepower rises as flow increases, so the driver must be sized for the highest flow the pump might see, not just its design duty. A pump that runs far out on its curve, past its intended flow, can demand more brake horsepower than expected and overload a motor that looked adequately sized on paper.
Once the shaft power is known, converting between horsepower and kilowatts is a straightforward fixed conversion, and the electrical power the motor draws from the supply is the shaft brake horsepower adjusted for the motor's own efficiency. So the chain runs from flow and head, through hydraulic horsepower, through pump efficiency to brake horsepower, and finally through motor efficiency to the electrical load on the system.
The brake horsepower a pump demands shows up in the real world as motor current and power draw, and those are quantities a SCADA system can measure directly. Because brake horsepower ties flow, head, and efficiency together, watching the motor's electrical load gives an indirect but sensitive read on what the pump is doing hydraulically. A change in load with no obvious change in operation is worth investigating.
A cloud SCADA such as Merobix can trend motor current or power alongside flow and discharge pressure, so an operator sees the relationship between the work the pump is doing and the power it is drawing. If the electrical load climbs while flow and head stay flat, something is stealing power - a bearing dragging, an impeller rubbing, or the pump running off its intended point - and the load trend catches it.
The load view is also a useful cross-check on measurement. If a flow meter reads high but the motor draws only modest power, the two are inconsistent, because higher hydraulic output should demand more brake horsepower and more electrical load. Reconciling the electrical signature against the hydraulic measurements is a practical way to catch a drifting meter or a mechanical problem before it becomes a failure.
Brake horsepower equals the hydraulic horsepower delivered to the fluid divided by the pump's efficiency. Hydraulic horsepower itself depends on the flow rate, the head, and the fluid's specific gravity. Dividing by efficiency accounts for the friction, turbulence, and mechanical losses inside the pump, so brake horsepower is always larger than hydraulic horsepower.
Brake horsepower is the actual power the driver must deliver to the shaft, so sizing a motor on it, with margin, ensures the motor will not overload. Since brake horsepower often rises with flow, the driver must be sized for the highest flow the pump might see, not just its design point, or a pump running far out on its curve could overload it.
Hydraulic horsepower is the useful power the pump puts into the fluid, set by flow, head, and specific gravity. Brake horsepower is the larger power that must be supplied to the shaft to produce that output, because internal losses consume part of it. Their ratio is the pump's efficiency, so brake horsepower equals hydraulic horsepower divided by efficiency.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.