Innovation, best practices and optimization

Matrikon’s Alarm Mik Marvan concluded the session on alarm management at the Matrikon Summit 2007 showing how Matrikon’s Alarm Management System can help companies implement best practices.

2 of 3 1 | 2 | 3 View on one page

Allowing for the additional characteristics of batch operations, such as multiple process steps, multiple phases, process loads, set points that are a function of time, and few, if any steady-state operations, these are his recommendations for building such a system.

  1. Adhere to the basic definition of alarms—“abnormal situations requiring a response.” Just doing this will knock out about 75% of alarms, says Alford.
  2. Tag alarm records with sufficient information needed to use the information for displays, sorts, queries and report generation. Include lot numbers, category, priority, process step/phase, etc.
  3. Generate more “intelligent” alarms that make use of all available relevant information, such as those that include if-then rules incorporating redundant sensors, trend slopes, and other correlated variables.
  4. Eliminate nuisance alarms. Do not include “notifications” on alarm displays. Make every effort to separate information messages from alarms.
  5. When color-coding displays, use each color only one time. If red indicates a high-priority alarm, don’t use that color for anything else.
  6. Minimize multiple alarms for each event.
  7. Ensure that alarms alert, inform and guide. They should tell the operator everything he needs to know about the alarm. “Most commercial systems do a great job of alerting, a mediocre job of informing and a bad job of guiding,” says Alford.
  8. Set up a system that allows sufficient mining of alarm data. Make records easy to access and understand. Include sufficient alarm tag information. Include “relative time” information. The fact that the alarm occurred at 3:00 a.m. is less important than that it occurred 2 hours into, say, a sterilization process. Include utilities that allow the creation of pareto charts and other trending information and those that include the ability to combine discrete and continuous trends. This is all about providing the necessary context.

Mik Marvan concluded the session with showing how Matrikon’s Alarm Management System can help companies implement these best practices. See for detailed information about this system.

Operational Excellence: Tai-Ji Steps Out at Hovensa Refinery
Step testing usually requires a lot of steps. As a result, traditional step tests and model identifications are very time consuming. Users must step a variable, wait for steady state, step it again, wait again, step, wait, step, wait, etc. This process also is costly and intrusive to process operations, and can require six to eight weeks or more of plant engineers’ time for new or maintenance projects. And, these days, there often aren’t enough experienced staffers to do these jobs anyway.

So, wouldn’t it be nice to find a way to automatically dance through step tests and modeling procedures? You bet.

That’s just what Bob Tkatch, process engineer at Hovensa LLC’s application engineering department, and his colleagues thought when they evaluated and adopted Tai-Ji on-line, multi-variable identification software and Matrikon’s Control Performance Monitor control performance monitor at the St. Croix, U.S. Virgin Islands-based refinery’s Crude Unit 6 MPC application with 34 multi-variable (MV) controllers and 90 CVs covering two furnaces, an atmospheric tower, and a naphtha stabilizer.

During the plant test, an existing MPC controller is online and active in stabilizing the operation, while the test program moves all MVs simultaneously. It took only eight days to conduct the closed-loop plant test, and perform model identification and review. The new plant test was found to be non-intrusive to the plant’s normal operations allowing the operators to concentrate on their normal duties. The refinery’s latest multi-variable predictive controller (MPC) retesting was completed automatically by stepping multiple independent variables simultaneously, while the MPC controller was in service. 

Hovensa is a joint venture between a subsidiary of Amerada Hess and a subsidiary of Petroleos de Venezuela, S.A. (PDVSA). The refinery can process approximately 500,000 barrels per day (BPD) of crude oil, which makes it one of the largest such facilities in the world. Hovensa includes four crude units, three vacuum units, eight DDs, three platformers, four sulphur recovery units, four amine units, 198 large tanks, and other facilities.

Tkatch reported that automated testing was especially welcome at Hovensa because they only have two APC engineers, or four during maximum staffing. Also, he says automated testing was needed because many MV controllers begin to perform poorly over time due to model degradation or inaccuracies, and so their models no longer reflect operating conditions. This degradation can be caused by long unit run-time, fouling exchangers and valves, changing operational objectives, and/or unit damage.

“A well-tuned, well-maintained MV controller pushes multi-variable constraints more effectively, providing opportunities for more efficient and profitable operations,” says Tkatch. “With Tai-Ji, MPC plant test projects and modeling projects can be done with limited staff, budget, time, and intrusion into the daily life of operations. We use Tai-Ji because it saves time and it works. Using Tai-Ji takes away the misery of doing traditional step testing.”

To accomplish these goals, Tai-Ji automates closed-loop and open-loop testing by first stepping variables automatically within defined limits. All defined variables then are stepped simultaneously, which enables Tai-Ji to provide far more steps per variable in its step test than a traditional step test could ever accomplish in the same time period. “Stepping all variables simultaneously provide far more steps per variable in about 25-30% of the time required to do a traditional test because you’re not stepping and waiting, stepping and waiting,” says Tkatch. “We can start the automated test, go do our other work, and just check on the test once in a while.”

2 of 3 1 | 2 | 3 View on one page
Show Comments
Hide Comments

Join the discussion

We welcome your thoughtful comments.
All comments will display your user name.

Want to participate in the discussion?

Register for free

Log in for complete access.


No one has commented on this page yet.

RSS feed for comments on this page | RSS feed for all comments