Not every situation is one an automatic controller should be left to handle. During startup, an odd trip, or a diagnostic exercise, an operator often needs to take the loop off automatic and set the output directly. The auto/manual station, sometimes called a hand/auto station, is the element that lets them do exactly that. This guide explains what the station is, why manual control remains essential even in a fully automated plant, and why switching between automatic and manual must always be bumpless.
Auto/manual station in one line: An auto/manual station is the faceplate element that lets an operator switch a control loop between automatic mode, where the controller sets the output, and manual mode, where the operator sets the output directly. It exists so a loop can be driven by hand during startup, troubleshooting, or abnormal conditions, and its mode changes must be bumpless so the process is not disturbed when control is handed between operator and controller.
On a control loop faceplate, the auto/manual station is the control that decides who is holding the output. In automatic mode the PID controller owns the output: it reads the process variable, compares it with the setpoint, and drives the final element on its own. In manual mode the operator owns the output: the controller stops adjusting, and the value sent to the valve or actuator is whatever the operator enters, which they can raise or lower directly. The station is simply the switch and the associated field that make that handover possible from the operator's screen.
Historically the term comes from panel instruments, where a hand/auto station or manual loading station was a physical device with a switch and a knob that let an operator take over a loop's output at the board. In a modern DCS or SCADA system the same function lives in software on the loop faceplate, but the concept is unchanged: a clear indication of which mode the loop is in, and a means to switch modes and to set the output by hand while in manual. Many faceplates also expose intermediate modes, but automatic and manual are the two fundamental states the station selects between.
The station is loop-level and operator-facing, which distinguishes it from configuration tools. It is meant to be used during normal operation by the people running the plant, giving them a sanctioned way to intervene in a single loop without touching the underlying control strategy. That everyday accessibility is the point: the ability to drop a misbehaving loop into manual has to be immediately available to an operator, not something that requires an engineer.
The most common reason to use manual is startup. Before a process reaches the conditions its controllers are tuned for, automatic control may be inappropriate or unstable, so operators frequently bring equipment up by hand, positioning valves directly to establish flows, warm up equipment, and stabilise conditions. Once the process is near its normal operating point, the loop is switched to automatic and the controller takes over. Manual gives the operator the direct command authority that a careful, staged startup requires, before conditions are ready for closed-loop control.
Manual is equally valuable for troubleshooting. When a loop is hunting, cycling, or behaving in a way that does not make sense, one of the first diagnostic actions is to put it in manual and fix the output. This immediately separates the controller's behaviour from the process's behaviour: if the process settles once the output is held steady, the trouble lies in the controller or its tuning, whereas if the process keeps moving with a fixed output, the disturbance is coming from the process itself. Manual is thus both a stabilising action and a diagnostic tool, letting an engineer isolate cause from effect.
There are also abnormal and maintenance situations where an operator simply needs to command the output regardless of what a controller would do. A failed or suspect measurement can make automatic control dangerous, since the controller acts on a value it should not trust, and dropping to manual lets the operator run the loop on judgement until the instrument is fixed. During certain maintenance and testing activities, direct control of a valve is likewise required. In all these cases the auto/manual station is the sanctioned path to human control, which is why it remains indispensable even in highly automated plants.
The one rule the auto/manual station must obey is that switching modes should not disturb the process. If handing control from the operator to the controller, or back, caused the output to jump, then every intervention would create a new upset, and operators would rightly be reluctant to use manual at all. Bumpless transfer is the mechanism that prevents this: the controller keeps its internal state aligned with the actual output while in manual, so that on the switch to automatic it continues from the output the operator left rather than snapping to some freshly calculated value. Going the other way, manual simply starts from the output automatic was already producing. The result is that the mode changes but the output does not jump.
In a cloud SCADA system such as Merobix, the auto/manual station appears on the loop faceplate an operator opens, showing the current mode plainly and offering the switch and the manual output field. Because the platform is cloud-based, an authorised operator or engineer can see a loop's mode and, where policy permits, act on it from wherever they are, which matters for assets spread across many remote sites. The mode of every loop is also a recorded value, so it is possible to see across a whole operation which loops are in manual at any moment, an important situational-awareness signal since a loop left in manual is one the automatic system is no longer minding.
That recorded mode history is useful well beyond the moment of switching. Reviewing when loops went to manual and came back helps reconstruct what happened during a startup or an upset, since manual periods mark where operators intervened. It also surfaces loops that quietly stay in manual for long stretches, which often points to a tuning problem, a bad measurement, or a control strategy operators have lost confidence in. Making the auto/manual state visible and historised across a distributed operation turns a simple operator convenience into a source of insight about how well the automation is actually serving the plant.
In automatic mode the controller calculates the output itself from the setpoint and the process variable and drives the final element. In manual mode the controller stops adjusting and the operator enters the output directly. The auto/manual station is the faceplate control used to switch between the two and to set the output by hand while in manual.
Putting a loop in manual and holding the output steady separates the controller's behaviour from the process's behaviour. If the process settles with a fixed output, the trouble is in the controller or its tuning; if it keeps moving, the disturbance is coming from the process. It is one of the fastest ways to isolate whether a problem is control-related or process-related.
If a mode change caused the output to jump, every switch would create a new process upset, and operators would avoid using manual when they needed it. Bumpless transfer keeps the controller's internal state aligned with the actual output so the switch changes the mode without moving the output. This makes it safe to hand control between operator and controller at any time.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.