In the "old days," it was common for an operating position to have both "inside" and "outside" responsibilities. As such, one could often find control rooms empty, with no one watching the board. All of the operators might be out on the unit performing other tasks. It is common with todayís distributed control systems to hear operators and/or supervisors argue that the board canít be out of the board operatorís sight. Given past operating practices, this begs the questions, if not required by the process (i.e., an alarm or an information request from plant personnel), how long would an operator take before inspecting their board? What is the minimum inspection frequency for an operator to sample the process under their control?
A rare opportunity presented itself recently when Beville was observing an operator who (1) had a very stable process (therefore, no alarms forcing an inspection of the DCS), (2) little activity in the plant (therefore, few information exchanges with the field), and (3) an operating style that made it easy to determine when the board was being examined (he otherwise worked with his back to the console). The operator was observed over a four-hour period. DCS inspections due to alarms and communications were removed. The result is a series of times the board went unmonitored. A histogram of those inspections is shown below.
As would be expected, the operator typically checked the board every five minutes, never going longer than 20 minutes between inspections. It is interesting to note that the time since the last inspection exhibits an exponential decay. This indicates that the 20 minute limit in time away from the monitor is not a random occurrence, but part of the operatorís internal model for the need to check on the process.
So what does this mean? The first and most obvious conclusion is that the operator observed had an uneventful (boring) sample period. Second, DCS monitoring of a process can require very low levels of workload; monitoring a process is not inherently a high workload task. Third, it is possible to quantify aspects of operator behavior, which could then be compared to other jobs that require sustained monitoring (e.g., air traffic controllers). Fourth and finally, a stable process need not have the operator "glued" to the screen to maintain control of the process.
Copyright © 2000 Beville Engineering, Inc. , All Rights Reserved
RELATED EXTERNAL MEDIA
|Consortium Reports New Findings on Alarm Rates||Automation World|
|How Many Alarms Can An Operator Handle||Chemical Processing|
|Impact of Alarm Rates and Interface Design on Operator Performance||Automation World|
|Operator Interfaces: Moving from Comfortable to Most Effective||Automation World|
|Operator Performance as a Function of Alarm Rate and Interface Design||Mesa.org|
This year's Fall meeting for the Center for Operator Performance will be October 24-26 in Corpus Christi. For more information, please contact Lisa Via. Guests are always welcome!
Our summer newsletter is now available. Click here!
Take our short survey on operator span of control. Click here (new window)
David Strobhar's book, "Human Factors in Process Plant Operation," is now available in both hardcover and Kindle e-book.
Copyright © 1996-2017 Beville Engineering, Inc. All rights reserved. (937)434-1093. Beville@Beville.com