Voices: Other Voices

Modular Procedural Automation Improves Operations

Using a Standard Automation Methodology Also Prevents Incidents by Allowing Operators to Share Best Practices

By A.N. Vennavelli, A.Y. Ogundeji

Fractionation Research Inc. (FRI) has been studying distillation and distillation equipment for almost 60 years on behalf of its 70 members, each of whom pay an annual subscription fee for services. FRI's two industrial-size distillation columns (Figure 1) are located on the Oklahoma State University campus in Stillwater. Three binary separation tests are typically run within those two columns:

  1. p- and o-xylenes from 75 mm Hga to atmospheric pressure;
  2. Cyclohexane and n-heptane near atmospheric pressure; and
  3. Isobutane and n-butane from 100 psia to 500 psia.

During test runs, the trays and packings within the columns are subjected to a very wide range of liquid/vapor and mass transfer regimes. All of the runs are logged at steady-state conditions, but steady state is maintained only long enough to collect the relevant data. The process conditions are then modified for the next test. Tests conducted include start-up, transitions within and between various modes of operations, flooding, un-flooding, setpoint changes and shutdowns.

Unsteady-state procedures at the FRI distillation units are now implemented semi-automatically using a solution called modular procedural automation (MPA). MPA was first pioneered by Yokogawa, and it initially was based on ISA88 principles. It's now being deployed using the guidelines under consideration by the ISA106 working group. MPA is a methodology that can be implemented with virtually any modern automation system, and it's effective across a wide range of processes and industries.

As implemented by FRI using Yokogawa hardware and software, MPA provides specific, on-screen instructions and information for our control room operators and technicians in areas listed in the "On-Screen Operator Guidance."

By having our operators follow these instructions and use the supplied information, MPA has produced safer operations at our test facility. Based on our experience, we believe that an MPA or similar solution might have prevented some of the largest chemical plant accidents of the past decade.
MPA Software Runs in the DCS


During 2011, the FRI control room was augmented with a data historian and MPA supervisory software supplied by Yokogawa. These tools were loaded onto the existing Yokogawa DCS, which has been in place for several years. Figure 2 depicts our control system architecture.



The historian, which collects data every second and stores it in a database, has allowed FRI to analyze unsteady data and data from operating modes other than total reflux. FRI engineers, with assistance from Yokogawa, have used the MPA software to build and execute electronic, semi-automated procedures for start-ups, transitions and shutdowns.

Semi-automated procedures based on operational experience were initially implemented using MPA, but none of the procedure algorithms were completely satisfactory when first tested in the control room. Some of the algorithms required additional process checks, some a faster or slower rate of execution, and some others needed increased flexibility.

To improve these procedures, the MPA software was run in parallel with actual operations, but in an offline mode. The procedures were then adjusted to closely mimic operator's actions. This step allowed the system to pass validation tests and, at the same time, increased operator understanding and trust.

Also Read "Control Room: Shrink Your System Footprint"

FRI's best board operators were in the control room during these trial runs, and their experience was used to modify and improve the initial MPA instructions. Our aim was to use MPA to capture the knowledge of our best operators, so this knowledge could be used by other operators to reproduce our best practices, time after time.

Specifically, our best operating procedures were captured and disseminated to other operators via various software screens. For example, Figure 3 is a screen that the FRI board operators now see during start-ups. The left pane of the screen shows the macro start-up steps. The lower right portion shows the current micro step. The upper-right pane shows the steps that were already completed. The software allows the operator/engineer to override certain steps in the procedure if such a need should arise.



FRI's board operators are well-trained, but we find that different operators can start, change and shut down operations in various ways. All of our operators are encouraged to fully understand the units and their operation, and to think on their own. But with MPA, there is now a uniformity of starts, changes and stops. This yields improved operations, while still allowing operators to act independently if unforeseen conditions should arise.

Goal Is to Assist, Not Eliminate Operators

As implemented at FRI, manpower reduction is not one of the goals of the MPA methodology. In too many global control rooms, manpower reductions have already occurred, and many senior technicians have retired over the past 10 years. We believe that experienced operators are a valuable asset, so we use MPA to assist, not eliminate, our operators. This assistance is provided by using MPA to share best practices among our operators, allowing the present generation of technicians to learn from our best operators even after they've retired.

We find that our operators appreciate the assistance provided by our MPA software. It helps them corroborate their judgments and decisions regarding next steps. Our operators say that using MPA is "like having our best operator alongside them in the control room all of the time."

We feel that the MPA methodology might prevent future accidents at FRI and elsewhere. To verify this contention, we examined how MPA might have been used to prevent past accidents.

Could MPA Have Averted These Accidents?

The U.S. Chemical Safety Board was formed in 1998 to study major accidents, write reports and produce instructional videos. For several years, FRI has used those videos as focal points for our safety meetings.

At these meetings, one or two CSB videos are typically shown, and the attending engineers and technicians then determine relevance to the FRI operations. After discussion, a list of FRI-related action items is created, with documentation and follow-up to assure that lessons learned are correctly applied.

There were three CSB videos where we concluded that the MPA methodology might have prevented accidents: T2 Laboratories, BP Texas City and Sterigenics.

Also Read "How to Build the Control Room of the Future"

T2 Laboratories

T2 Laboratories was located in Jacksonville, Fla. T2 produced MCMT, a gasoline additive. The primary production step was an exothermic reaction in a 2,500-gallon reactor that included a water jacket. In 2007, the water supply failed and a runaway reaction resulted. At some point, the pressure build-up caused the relief valve to blow, but the relief system was too undersized, and the reactor exploded.

Details regarding the accident can be found in a CSB video (Reference 1) or the associated report (Reference 2). The video describes a lone board operator, who did not know what to do when the water jacket's water supply failed. He called off-site engineers for help, and they rushed to the plant, but reached it too late.

If the T2 control room had used an MPA solution, the following would have been possible:

  1. Prompts could have been provided to the board operator regarding the backup water supply;
  2. Corrective action steps for this type of condition could have been programmed as screen prompts or as automated flowrate and valve changes; and
  3. The software could have set off evacuation alarms.

The knowledge of the plant's most-experienced people could have been provided to the board operator via MPA, particularly as temperature excursions had occurred with the reactor before. The previous excursions could have been studied using a historian, and the lessons learned could have been implemented within MPA and made available to the operator.

BP Texas City Isomerization Unit

Details regarding this accident can be found in a CSB video (Reference 3) or the associated report (Reference 4). This accident was similar to the T2 Laboratories incident in that a very large burden seemed to fall upon a single operator. Regarding BP Texas City, the report stated, "Restructuring following the merger resulted in a significant loss of people, expertise and experience." In retrospect, some of that experience could have been captured using MPA and then made available to the operator.

The BP accident occurred in 2005 in an isomerization unit. When the lone operator came on shift, he had just a single line of input in the log book from the previous operator: "Starting up the Isom Unit."  Unfortunately, the supervisor of the newly arrived operator had been called out of the control room for an extended period to attend to a family emergency.

The newly arrived operator needed to continue to start the isomerization unit and control two other units, all with virtually no input and assistance. Due to a malfunctioning liquid-level alarm, he had no idea whether he was starting with six feet or 175 feet of liquid in the bottom of the raffinate splitter tower. The truth proved to be closer to the latter, and the tower overflowed into the blow-down drum, and the hot gasoline then overflowed and ignited.

If the BP control room had used MPA, the following would have been possible:

  1. The newly arrived operator would have had on-screen information regarding all of the steps that the previous shifts had taken, including the exact times of those steps;
  2. A safety warning could have been provided on-screen regarding the overflowing of the raffinate splitter tower, which had already happened a few times in the past;
  3. Out-of-date procedures would have been updated for the sake of the programming of the new software; and
  4. The MPA software could have shut the unit down in time to avoid the explosion.

If MPA had been correctly implemented, the lone operator of the three units would not have been alone.

Sterigenics Oxidizer Accident

This accident was described in a CSB video (Reference 5) and in the associated report (Reference 6). This accident did not occur because an operator was alone, but because a standardized procedure was not obeyed, and the operators did not understand the ramifications of diverting from that procedure.

The Sterigenics plant was located in Ontario, Calif. This facility sterilized medical equipment in large chambers using ethylene oxide gas. Subsequent to sterilization, according to procedure, the ethylene oxide gas was purged from the chambers using a three-step process. On the day of the accident, one of those steps was purposely skipped. As a result, a concentrated ethylene oxide gas stream was sent to the oxidizer, and the chamber exploded.

If the Sterigenics control room had used MPA, the software could have provided a message to the operators along these lines: "If Step 2 is skipped, a concentrated ethylene oxide gas stream will flow to the oxidizer, and an explosion might result." Upon seeing this message, the operators may very well have taken corrective action.

With MPA, Operators Are Never Alone

Regardless of the reasons, the control rooms of the western world do not seem to be as well-manned as those of 20 or 40 years ago. To address this situation, MPA can be used to transfer the knowledge and experience of the best remaining operators, engineers and technicians to new operators. This makes new operators more effective and efficient. When MPA is correctly implemented, no operator needs to start, run or stop an operating unit alone.

More from this voice

Title

An Embarrassment of Riches

Checking Out ControlGlobal.com Can Be Rather Like Harvesting a Tomato Patch. There's So Much Good Stuff There--and More Is Added Every Day

10/03/2011

Are Industry Analysts Relevant Anymore?

Does It Make Sense to Subscribe to Industry Research? For Most, the Answer Is the Classic Analyst Response: It Depends

08/01/2013

Automation Processes Are Easy to Listen To

We Have More Than 200 Podcasts on Subjects Ranging From the RS-485 Standard to How to Upgrade Your DCS. Listen and Learn

07/31/2012

Best Practices in High-Performance HMI Design

Having a Solid Foundation to Build On Is Extremely Important, and Having an Enforced Policy That Ensures Compliance Is Just As Important

10/03/2012

Bringing the Lincoln Paper Mill Back from the Dead

Lincoln Paper Wasn't Even a Zombie Company. It Was Dead. Closed. Kaput. Then New Owners Brought in Multivariable Testing to Help Resurrect It Through a Top-to-Bottom Revamp of Procedures, Processes and Plant Culture

05/13/2013

Championship Season for Industrial Instrumentation

How Potash Upgraded Its Systems, Training and Instrumentation Workforce All at the Same Time

11/18/2013

Choose and Manage Your Automation Suppliers Carefully

How Can We Manage Our Supplier Performance to Achieve Optimum Long-Term Results

10/11/2013

Collaboration Isn't Just for People

Today's Collaborative Infrastructure Can Bring Together Devices and Applications, Too.

10/31/2013

Comprehensive Training Prepares Kuwaitis to Take Over Refinery

Workforce Effectiveness Begins With an Assessment of the Customer's Unique Needs

10/28/2013

Could Cyber Terrorists Attack Our Company?

Less Than 25% of the Incidents Recorded in the RISI Database Represent Intentional Attacks on Control Systems

06/02/2010

Demanding Software Security Assurance

Users Wonder, "How Dependable, Trustworthy and Resilient Is My Supplier's Software?"

02/10/2011

Developing Control System Security Standards

Are There Several Standards in the Area of Control Systems Security?

06/01/2012

Do You Really Need to Train Them On...Everything?

Many Times Training Classes Are Ineffective because They Lack a True Training Objective

11/02/2009

Domino Theory

Can ISA88 and ISA95 Knock Down the Barriers Between Batch and Continuous Processing?

09/09/2008

Farewell to Standardization: Wireless and FDI

Will There Be One Standard for Wireless and One Standard for Field Device Integration?

02/06/2012

FDT Expands Its Industrial Network Footprint

FDT Is Like a 'Swiss Army Knife,' Enabling the Viewing of In-Depth Device Information From Multiple Protocols in a Single Environment

11/18/2013

Feeding the Asset Management Beast

Will the Work Underway at IEC on the Digital Factory and Similar Initiatives Help Integrate All the Disparate Standards Into a Unified Whole?

03/07/2014

Fieldbus Is Easy With Portable, Wireless Tools

Why Use Portable Tools? Find Out Its Benefits

04/02/2013

Finding Faults in Enterprise Asset Management Systems

Giant Swedish Mine Counts on an Integrated EAM System to Make Fault Reporting and Predictive Maintenance Easier

11/06/2012

Getting into Discrete

Process Meets Packaging

09/09/2008