The first-order-plus-dead-time model, universally shortened to FOPDT, is the workhorse abstraction of process control. It boils a loop's behavior down to just three numbers, and nearly every tuning rule and control loop performance monitoring tool fits this model to a step test in order to characterize how a process responds. It is not a perfect description of reality, and it does not try to be; its whole value is that three parameters are simple enough to work with while still capturing what matters for tuning. This guide explains the three parameters, how they come straight off a step-response trend, and how they feed the tuning that follows.
FOPDT Process Model in one line: A first-order-plus-dead-time (FOPDT) model describes a process using three parameters: process gain, how far the measurement ultimately moves per unit of output change; time constant, how quickly it gets there once it starts moving; and dead time, the pure delay before it starts moving at all. These three numbers are read off the reaction curve from a step test, and they are the inputs that tuning methods like lambda and IMC use to calculate controller settings.
The FOPDT model reduces the tangled dynamics of a real process to three intuitive quantities. The process gain answers how much: for a given change in controller output, how far does the measurement eventually move? A high gain means a small output change produces a large swing; a low gain means the process is sluggish in magnitude. The time constant answers how fast: once the process starts responding, how quickly does it approach its new value? A short time constant means a snappy response; a long one means the process eases toward its destination slowly. The dead time answers how late: after the output changes, how long before the measurement shows any response at all? This is the pure delay, and it is the hardest of the three for a controller to cope with.
Together these three tell a controller almost everything it needs to know to be tuned. Gain sets how strongly the controller should push, because it says how much bang each output move delivers. The time constant sets the natural pace of the loop, which the controller should respect rather than fight. And dead time sets the fundamental speed limit, because it is the interval during which the controller is acting blind and cannot see the effect of its moves. The relationship between dead time and time constant, in particular, tells you how controllable the loop is: a loop dominated by dead time is inherently harder to control tightly than one dominated by its time constant.
The model is called first-order because it approximates the process response as a simple exponential approach to a new value, the same curve a single tank or a single lag element would produce. Real processes are often more complicated, with several lags stacked up, but a first-order-plus-dead-time approximation captures the essential shape well enough for tuning purposes by lumping the extra complexity into the dead-time term. This deliberate simplicity is exactly why it is the model everyone reaches for.
The parameters are not guessed; they are measured from a step test, also called a bump test. Put the loop in manual, make a clean step change in the controller output, and record the resulting measurement trend, the reaction curve. Every one of the three numbers is visible in that curve. The process gain is the total change in the measurement divided by the size of the output step, once the process has settled. The dead time is the flat interval at the start, before the measurement begins to move. And the time constant is read from how long the response takes to cover most of its journey to the new value after it starts moving.
There are established graphical and computational techniques for extracting these numbers cleanly, and modern tools automate the fit, but the concept is the same whether done by eye or by software: find the three parameters that make the FOPDT curve match the observed response as closely as possible. A good fit demands a good test, which is why practitioners care about a clean, sufficiently large step, a quiet period free of disturbances, and enough time for the process to settle. Garbage data yields a garbage model, and a wrong model yields wrong tuning.
Once fitted, the model feeds directly into tuning. Lambda tuning and internal model control, or IMC, are model-based methods that take the gain, time constant, and dead time and compute controller settings from them, letting the engineer dial in a desired closed-loop response speed. This is what closes the loop between the process-gain and dead-time concepts and actual controller settings: those individual parameters are precisely the ingredients of the FOPDT model, and the model is the thing the tuning rules consume. Understanding gain and dead time in isolation is useful, but it is the model that assembles them into something a tuning method can act on.
Fitting an FOPDT model requires exactly one thing: a good record of how the measurement responded to a change in output, which is trend data a SCADA historian keeps as a matter of course. That means the raw material for characterizing a loop is already sitting in the historian, and a monitoring tool can fit models from step tests captured in normal operation, or from deliberate bumps, without any special instrumentation. The three parameters become properties of the loop that the system can store, track, and use.
In a cloud SCADA platform such as Merobix, this lets loop models be built and refreshed centrally across many sites. A control engineer can pull the reaction curve from a recent step test on a remote asset, fit the gain, time constant, and dead time, and compute updated tuning, all from the historized trend rather than a field visit. Because the model parameters are stored, the system can also flag when a loop's behavior has drifted away from its known model, a hint that the process has changed through fouling, wear, or a shift in operating conditions, and that a fresh characterization is due.
This model-centric view serves any process the platform monitors. Oil and gas separators and heaters, water treatment dosing loops, power plant thermal loops, and manufacturing lines all benefit from being described by a simple, portable three-parameter model that travels with the loop and underpins its tuning. Keeping that model current from SCADA data, rather than rediscovering it by hand each time, is what makes systematic, fleet-wide tuning practical instead of a per-loop expedition.
They are process gain, time constant, and dead time. Gain is how far the measurement ultimately moves per unit of output change, the time constant is how quickly it approaches that new value once it starts moving, and dead time is the pure delay before it starts moving at all. Together these three numbers describe enough of a loop's response for tuning purposes.
You run a step test with the loop in manual, make a clean change in the controller output, and read the parameters off the resulting reaction curve. Gain is the settled measurement change divided by the output step, dead time is the flat interval before the measurement moves, and the time constant is read from how long the response takes to cover most of its journey. A clean, disturbance-free test is essential for a good fit.
It is the input to model-based tuning. Methods like lambda tuning and internal model control take the fitted gain, time constant, and dead time and calculate controller settings from them, letting the engineer target a desired closed-loop response. The model is also used to assess controllability, since the ratio of dead time to time constant indicates how tightly a loop can be controlled.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.