During commissioning and maintenance there are times when an engineer needs the system to ignore what a field device is actually saying and use a chosen value instead. That deliberate override is called a force, and a tag under it is a forced tag: the live signal is still there, but the system reports the forced number in its place. Forcing is a legitimate and sometimes necessary tool, but a force that outlives its purpose becomes a hidden lie in the data. This guide explains what forcing is, why every force should carry a distinct flag, how force lists and audits keep them under control, and how forcing differs from entering a hand value.
Forced Tag in one line: A forced tag is a live signal that an engineer has manually overridden so the system reports a chosen value instead of the real field reading, typically during commissioning, testing, or maintenance. The underlying signal still exists but is bypassed by the force. Because a forgotten force silently substitutes a fake value for real data, forced points should carry a distinct quality or flag, be listed on an active-force list, and be recorded in an audit so they are visible and eventually removed.
Forcing is the deliberate act of overriding a value so that the system uses a number an engineer supplies rather than the one coming from the field. The live signal keeps arriving in the background, but the force intercepts it, so displays, logic, and calculations all see the forced value instead. It can be applied to an input, holding a reading at a fixed number regardless of the sensor, or to an output, driving a device to a commanded state regardless of the control logic. In both cases the point stops reflecting reality and starts reflecting the engineer's instruction.
The reason forcing exists is that there are legitimate situations where the real signal is unavailable, untrustworthy, or in the way of a task. During commissioning a technician may force an input to a known value to test that downstream logic and displays respond correctly before the actual instrument is connected or calibrated. During maintenance an engineer may force a signal to keep a process stable while a faulty transmitter is replaced, or force an output to exercise a valve or a pump for a checkout. In each case forcing is a controlled, intentional intervention with a clear short-term purpose.
The trouble is that forcing is powerful precisely because it is invisible to the normal operation of the system. The whole point is that the logic and the displays behave as if the forced value were real, which means nothing about the ordinary running of the system reminds anyone that a force is in place. A force that was applied for a ten-minute test and then forgotten will keep quietly substituting its value for months, and the process will run on a fiction without anyone noticing until the discrepancy causes a problem. This is why the governance around forcing matters as much as the mechanism itself.
The single greatest danger of forcing is the forgotten force. Because a forced value behaves like a real one, a force left in place after its purpose has passed becomes a silent corruption of the data: an operator trusts a reading that is not coming from the field, a calculation uses a value that no longer reflects reality, and a safety-relevant point may be pinned to a state that is no longer safe. Incidents in industry have been traced to overrides and forces that were applied for a legitimate reason and never removed, so treating forcing as something to be tracked and cleared, not just applied, is essential.
The primary control is that a forced value should never look identical to a live one. A forced point should carry a distinct flag or quality indicator so that anyone looking at it, on a display, in a report, or in an alarm, can see that the number is overridden rather than real. Making forces visually and programmatically distinct turns an invisible substitution into an obvious one, so an operator taking over a shift can immediately see which points are not to be trusted as field data, and downstream consumers can decide whether to treat a forced value differently.
Above the individual flag sits the force list, an active list of every force currently in effect, which is the standard way to keep the whole set under control. Reviewing the force list is a routine part of good operating discipline, especially at shift handover and at the end of any commissioning or maintenance activity, so that forces applied for a task are deliberately cleared when the task is done. Beyond the live list, an audit record of forces, who forced what, when, to what value, and when it was removed, provides the accountability that makes forcing a governed activity rather than an ad-hoc one. Reporting active forces to operators and supervisors closes the loop, ensuring no force lives on unseen.
Forcing is often confused with entering a manual or hand value, but the distinction is important. A hand value is typically used where there is no live signal to begin with, an unmetered stream, a manual reading taken by an operator, a value keyed in because no instrument exists, so the entered number is filling a genuine gap rather than displacing anything. A force, by contrast, overrides a signal that is present and working: the live value is right there, and the force deliberately pushes it aside. The practical difference is that a hand value substitutes for absence while a force substitutes for a real, available reading, which makes a lingering force more dangerous because it is actively hiding truth rather than merely standing in for missing data.
Both should be flagged distinctly, but the risk profile differs. A stale hand value is out of date; a stale force is a fiction laid over live data. That is why the governance around forcing tends to be stricter, with explicit force lists and audits, while hand values are more often governed by staleness rules and periodic re-entry. Understanding which mechanism is in play on a given point tells an engineer what kind of failure to guard against and what record should exist to explain the value.
In a cloud SCADA platform such as Merobix, where a central team may supervise many remote sites without visiting them, keeping forces visible is both harder and more valuable. Harder, because the person who applied a force during a site visit may be far from the person now watching the data, so a force that is not clearly flagged can easily be forgotten across that distance. More valuable, because a centrally maintained active-force list lets a supervisor see every override across the whole fleet at once, review them at handover, and confirm that commissioning and maintenance forces were cleared before a site was declared normal. Carrying a distinct quality on forced points through to the hosted history and reports means that even a much later analysis of the data can tell which figures were real field measurements and which were engineer-supplied overrides.
Forcing overrides a signal that is present and working, deliberately pushing the real field reading aside so the system uses a chosen number. A hand value fills a gap where there is no live signal, such as a manual reading or an unmetered stream. The practical difference is that a force actively hides a real available reading, which makes a forgotten force more dangerous than a stale hand value that merely stands in for missing data.
Because a forced value behaves exactly like a real one, so nothing in normal operation reminds anyone it is there. A force applied for a short test and never removed keeps silently substituting its value, so operators trust a reading that is not from the field and calculations run on a fiction. Industry incidents have been traced to overrides that were applied for a legitimate reason and never cleared.
A force list is the active list of every force currently in effect on the system, the standard way to keep overrides under control. Reviewing it at shift handover and at the end of any commissioning or maintenance work ensures forces applied for a task are deliberately cleared when the task is done. Paired with a distinct flag on each forced point and an audit record of who forced what and when, it turns forcing into a governed activity.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.