Proportional band and proportional gain describe the same thing two different ways, and mixing them up is one of the fastest ways to badly detune a loop. Proportional band is the percentage of input span the process variable must move to drive the controller output across its full range. It is the inverse of gain, so a wide band is a gentle controller and a narrow band is an aggressive one - which is backwards from how gain reads. This page untangles the two conventions so a value copied from a DCS into a PLC does not end up meaning the opposite of what you intended.
Proportional Band in one line: Proportional band (PB) is the change in process variable, expressed as a percent of measurement span, needed to move the controller output from 0 to 100 percent. It is the reciprocal of proportional gain: PB percent equals 100 divided by gain, so a small band means high sensitivity and a large band means low sensitivity.
Proportional action produces an output change in proportion to error, and how strong that action is can be written as either a gain or a band. Gain is a plain multiplier: a gain of 4 means the output moves four times as far as the error. Proportional band asks the opposite question - how much does the input have to change to swing the output across its whole span - and answers it as a percentage. The conversion is simple: proportional band percent equals 100 divided by gain, and gain equals 100 divided by proportional band percent.
Because the two are reciprocals, they move in opposite directions, and this is exactly where field mistakes happen. A gain of 5 corresponds to a 20 percent band. A gain of 0.5 corresponds to a 200 percent band. When you make a controller more aggressive you raise the gain but lower the band, and when you make it gentler you lower the gain but raise the band. An engineer who thinks in gain and then types a number into a controller that expects band can end up with a loop hundreds of times too fast or too slow.
A worked example makes it concrete. Suppose a temperature loop has a span of 0 to 200 degrees and a proportional band of 50 percent. Fifty percent of the 200-degree span is 100 degrees, so the process variable must swing 100 degrees to move the output from fully closed to fully open. Halve the band to 25 percent and now only a 50-degree swing does the same thing - the controller has become twice as sensitive, equivalent to doubling the gain.
The convention you meet depends largely on the platform in front of you. Traditional distributed control systems and older single-loop controllers, many of them descended from pneumatic and analog designs, overwhelmingly express proportional action as proportional band in percent. Programmable logic controllers and most modern software PID blocks express it as gain, sometimes called proportional gain or Kp. Neither is wrong, but a plant that runs both will have tuning documented in two incompatible units.
The trap is copying a value across the boundary without converting it. A DCS loop tuned to a 40 percent band is equivalent to a gain of 2.5. If that 40 is entered directly into a PLC block that reads it as gain, the loop is suddenly running a gain of 40, roughly sixteen times too aggressive, and it will very likely go unstable the moment it is put in automatic. The reverse mistake - entering a gain of 2.5 into a field where the controller expects band - leaves the loop almost inert.
Standardizing on one convention in your tuning records, and noting which convention each controller expects, removes most of this risk. When you do migrate values, do the reciprocal-of-100 conversion explicitly and sanity-check the result against the loop you started from. A band of 100 percent and a gain of 1 are the same setting; if your conversion did not land near a value you recognize, you converted in the wrong direction.
You cannot see proportional band directly on a trend, but its effects are unmistakable, and a SCADA historian gives you the data to spot them. A band that is too narrow, meaning gain too high, shows up as an oscillating process variable that swings around setpoint with a fairly constant period. A band that is too wide leaves a large, persistent offset between PV and setpoint because pure proportional action alone cannot fully erase steady-state error - that is what the integral term is for.
When a cloud SCADA platform such as Merobix historizes PV, setpoint, and output together across remote sites, an engineer can compare loop behavior without visiting each controller. That matters because the same physical process controlled by a DCS at one site and a PLC at another may have tuning entered in different units, and the trends are the common language that reveals whether the two loops are actually tuned alike.
Documenting each loop's proportional setting alongside its historized behavior also protects the plant over time. When a loop that once behaved well starts oscillating, having the original band or gain on record - and knowing which convention it was in - lets you tell whether someone retuned it or whether the process itself changed. Without that record, every investigation starts by guessing which units the last person used.
Divide 100 by the proportional band percentage to get the gain, and divide 100 by the gain to get the band percentage. For example, a 25 percent band equals a gain of 4, and a gain of 2 equals a 50 percent band. Because they are reciprocals, a narrow band always means a high gain and a wide band always means a low gain.
A smaller proportional band makes the controller more aggressive. Less process-variable movement is needed to swing the output across its full range, which is the same as a higher gain. This is the opposite of the intuition many people have, so it is a common source of tuning errors when switching between band and gain conventions.
Proportional band is a legacy of pneumatic and analog controllers, where expressing sensitivity as a percentage of span was natural, and many distributed control systems kept the convention. Modern PLCs and software PID blocks generally use gain instead. Both describe identical proportional action; the difference is only in how the number is presented.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.