Professional Documents
Culture Documents
2
Chapter 1
Industry Challenges
Process industries face numerous challenges keeping health, safety, and
environment (HSE) at the forefront, an aging workforce, improving equipment
availability, maintaining quality, and increases in operator workloads. Distracted
operators make mistakes, especially during transitions, and operational error is the
single biggest reason for unscheduled shutdowns. In this chapter we will take a
closer look at some of these challenges and how procedures play an important
role. First lets clarify what a procedure actually is.
It seems that procedures may not be the first thing that comes to mind when thinking about process
automation. Still, they play an important role at any industrial plant or factory, and though we like to refer to
the process industries as being largely continuous, most continuous processes actually have multiple
operating states. Process manufacturing is constantly in flux, and because of this, procedures exist. In
fact, the entire world of process operations is governed by procedures.
What is a Procedure?
Procedures are best described as pre-set
tasks that are consistently completed in a
specific order so as to achieve the desired
result. The automation of these
procedures bridges the gap between the
process control systems and plant
operators by augmenting operator actions
with electronic Standard Operating
Procedures (SOPs) that are integrated
with a Distributed Control System (DCS).
Today, operational procedures can be lumped into three primary categories: manual procedures,
prompted procedures and automated procedures. These operational procedures are typically
implemented as manual procedures in written form, either electronically or on paper. More often than
not, there is no way to verify that the procedures actually executed were, in fact, consistent with the
prescribed standard operating procedures (SOPs) for the process. We trust the operators to be
consistent. But is that always the case?
Many industries have been using prompted or automated procedures for some time, especially
the batch industries, such as life sciences, and food and beverage production. In the continuous
process industries, however, prompted and automated procedures are not the established way of
operating. Operations such as starting up and shutting down a refinery unit for instance, are often
considered to be a craft or an art form that relies heavily on experience and knowledge of the facilitys
operational and maintenance staff and its historical method of operation.
This is not to say that automated procedures are unknown in the continuous process industries.
Many companies have implemented sequence logic that allows procedures to be automated. However,
these have been done largely in an ad hoc framework using custom programming methodologies that
can become cumbersome when the time comes to upgrade the automation infrastructure. This ad hoc
approach also carries a high cost of ownership, since the custom logic has to be maintained by the end
user. Changes made to the code over time can create a tangled mass of 'spaghetti code' that can be
impossible to translate and maintain.
To make it even more complex, many end user companies in the process industries today are
the result of mergers and acquisitions. Along with that comes the multiple system platforms and
inconsistent code implementations that have accumulated over the years. Clearly, this is not a
sustainable way to operate and is likely to affect your operations in at least three ways, related to:
Plants are especially vulnerable during abnormal operation states. Thus, many safety incidents
occur during infrequent, transitional, or abnormal situations. A potentially dangerous (and abnormal)
situation might occur when an infrequent operation has to take place, but key individuals are not
available, leaving inexperienced operators to follow inadequate or incorrect instructions. Something can
get out of control and quickly lead to undesirable outcomes such as equipment damage, environmental
release, injuries and/or fatalities. (Source: ISA-106 and Concepts of Procedural Automation).
There are three broad operational procedures involving transitions: start-up, shut-down and unit
state change. The unit state change includes transitions like grade changes, production rate changes,
process equipment switches, feed changes, etc.
Safety statistics show the majority of incidents not related to outright mechanical failures happen
during abnormal situations, primarily unit startups and shutdowns. Prime examples are the Kern Oil
Refinery that occurred during a crude unit startup and the BP Texas City disaster that took place
during a raffinate splitter tower startup. Unfortunately, such incidents did not stop after 2005 and many
more examples continue to occur much too frequently even today.
Operators today can be under huge Operational error is the single biggest
amounts of stress that will have an impact on their reason for unscheduled shutdowns. Procedure
responses to abnormal situations. Under normal based recovery from abnormal situations is faster
operating conditions, the operator can apply their and more reliable than recovery based on random
training and basic knowledge successfully. At the operator knowledge even from expert operators.
first sign of a fault, the operator is capable of Effective operational consistency can be
acknowledging the event and responding seen day-in and day-out within high-risk industries
accordingly. As the situation begins to deteriorate, like nuclear power or aviation, where the
the ability of the operator to effectively respond consequences of an accident can be so
deteriorates rapidly. catastrophic that the importance of consistent
A widespread issue in manufacturing plants reliability raises itself to a very high level. These
is alarm flooding. As formerly independent high-reliability organizations nearly always achieve
systems are integrated for more effective operation error-free operations due to their strong
by fewer operators, each operator now has an operational consistency.
ever increasing scope of responsibility a wider
area to monitor and consequently more alarms to
deal with. Without rigorous alarm rationalization
efforts, alarm flooding becomes a serious problem
and increases the risk of safety and environmental
incidents.
Operational Consistency
Years ago (industrial) automation involved hand valves and a few field mounted pneumatic
loops, but this grew to a few hundred single loop controls and indicators on large boards, then to
several hundred loops and indicators on single or small clusters of single-monitor Operator Consoles
to todays large centralized control rooms. These control rooms have groups of Workstations, each
with multiple monitors. This evolution also affected the role of an operator. In the past, a single
operator was responsible for managing an environment of perhaps less than 50 items, now a single
operator may have hundreds of loops and thousands of indicators to cope with. The proficiency and
effectiveness of operators remains a serious concern for Operations Management, as technology has
changed the visualization of the process facility and driven up the scope of responsibility of an operator
to include 100s to 1000s of loops. As mentioned earlier, the large number of devices requires a
considerable attention span under normal conditions, but become a greater concern under the stress of
a disturbance or abnormal situation. To maintain situational awareness and consistent operation within
such an environment, is a challenge, especially when abnormal situations occur.
11
MPA Introduction
To deal with some of the challenges described in the pervious chapter, consider
Modular Procedural Automation (MPA). It is a solution that captures operators
knowledge and best practices and ensures procedures are consistently employed
throughout the manufacturing process. Using the capabilities of MPA, plant
operations, engineering, HSE and management can be more confident that the
correct procedures are being followed. MPA is a clear path to operational
excellence in the process industries.
Modular Procedural Automation (MPA) is not new, nor is it some theoretical concept. It has
existed for many years, mostly in batch and semi-batch processes, but also in continuous processes by
some early adopters. It is all about automating specific tasks in a process that typically require a lot of
manual intervention from operators, to avoid the problems that can originate in manual intervention.
There are real benefits in its
application to batch and continuous
processes, and even a casual
examination shows multiple
opportunities. Procedural automation is
beneficial not only in chemical and
petroleum processing, but in any
process with sequential operations.
Procedure automation has therefore
been applied to a wide range of
processes from offshore platform
operation to cracking furnaces to
processing nuclear materials.
Procedures exist in all processes. Sometimes they are written down on paper, sometimes kept in
digital form in a document control system, and sometimes they just are in somebodys head. Well-
written procedures enable safe, consistent operations. In fact, for some industries, written procedures
are a legal requirement. However, having procedures and actually following them are often different
things. To maximize the benefit of any procedure, it must be faithfully followed day in and day out.
Thus, the basis for the main benefit of procedure automation: it enforces adherence to the procedure.
Modular Procedural Automation can also help in the development of the safety lifecycle. It is a method or
procedure that provides the means to specify, design, implement, and maintain safety systems in order to achieve
overall safety in a documented and verified manner. Modular Procedural Automation can help implement the
procedures required to developed safety lifecycle management in the same way it can help execute transition
changes and other functions in the plant.
The BP accident occurred in 2005 in an The operator would have had on-
isomerization unit. When the lone operator screen information regarding all of
came on shift, he had just a single line of the steps that the previous shifts
input in the log book from the previous had taken
operator: "Starting up the Isom Unit. A safety warning could have been
A very large burden seemed to fall provided on-screen regarding the
BP Texas City upon a single operator overflowing of the raffinate splitter
(2005) Restructuring following the merger tower
resulted in a significant loss of people, Out-of-date procedures would have
expertise and experience been updated
The MPA software could have shut
the unit down in time to avoid the
explosion
In 2007, four people were killed and 13 Prompts could have been provided
others were transported to the hospital when to the board operator regarding the
an explosion occurred at T2 Laboratories backup water supply;
Inc. during the production of a gasoline Corrective action steps for this type
additive called methyl cyclopentadienyl of condition could have been semi-
manganese tricarbonyl. automated with prompts; or fully
T2 Laboratories, The CSB report describes a lone board automated as automated flowrate
and valve changes; and
Chem. Explosion operator, who did not know what to do
when the water jacket's water supply The software could have set off
(2007) evacuation alarms.
failed. He called off-site engineers for
help, and they rushed to the plant, but The knowledge of the plant's most-
reached it too late. experienced people could have
been provided via MPA
Automation of High-density
Polyethylene Grade Change
Automation of Crude
Switch Operation
23
Implementing MPA
In the previous chapter we explained what to look for identifying MPA
opportunities. Next step is implementing MPA. An important lesson that MPA
vendors have learned is that if MPA is not made as easy as possible for operators,
then a project isnt likely to be successful. As a result, operator friendly software is
important. In this chapter we will highlight a methodology for implementing MPA.
You might think implementing MPA is easy. After all, standard operating (SOP) procedures may
already exist at your plant. As it turns out, most SOPs are based on stable operations. The reality is, that
for abnormal situations operations often rely on the experience of your senior operators. Part of
implementation is capturing that knowledge. Vendors like Yokogawa provide expertise on knowledge
engineering required to capture knowledge and transfer it into automated procedures.
As already mentioned, MPA methodology begins with an examination of the procedures chosen for
automation. At Fractionation Research Institute (FRI), a Yokogawa customer in the United States, during
the first step of the MPA methodology, the procedure evaluation process, uncovered that many of the
procedures were not actually written down in logical order, or correct with regard to values. The common
practice was to use the procedure as more of a guideline than an actual procedure. This allowed for
variations in actual startup and shutdown efficiency. As a solution MPA captured the best practices
(know-how) of the senior operators for use by all the operators. The figure below represents the difference
between the two in a flow diagram.
Procedural flow diagrams for the startup and shutdown procedures were created in order to
capture the evaluation resultscompleteness, logical order, correctness, steps to be automated, and sub-
procedures to be modularized. The procedural flow diagrams were converted into automated procedures.
The FRI subject matter expert and the Yokogawa consultant reviewed the automated procedures to
validate logic and completeness.
Testing on the procedures was
performed in Offline Mode
(disconnected from the process
control system), in Trial Mode
(read only from the process
control system), and Normal
Mode (read from and write to the
process control system). The
testing allowed for final
adjustments of the procedures
before they were placed into
operation.
2. Use MPA to help make your plant more productive through consistent, safer operations.