exida worked with Ashland to Implement a More Useful Alarm Management Program | exida

News & Events.

exida worked with Ashland to Implement a More Useful Alarm Management Program


  January 18, 2016

Ashland-exida

Ashland ISP Lima, located next to a large Husky Refinery in Lima, OH, was experiencing alarm management issues such as alarm floods and nuisance alarms. The BDO plant, which had been in operation since 2000, utilizes a DeltaV distributed control system. Rather than following a “DIY” approach, Ashland brought in exida to help them design and implement an effective alarm management program which included the following:

Ashland Table

Challenges

Improve alarm system performance to better support operations. After a plant upset, operators were often ooded with alarms (2000+ in 60 mins), such that the DCS (alarm system) did little to help guide the operator’s response to the situation. Like many plants, older operators had trouble getting helpful insights and guidance from the complex DCS Alarm System, and wished they had an old PANALARM® (annunciator panel) instead. Alarm priority was not tied to urgency or consequence severity, making it hard for operators to know which alarm was most important to respond to first.

The operations team consisted of senior operators that had been running the plant since it was first brought on line (15+ years experience) and new operators with two – six years experience. More and more new operators were being added as the experienced operators transitioned out of the work force (brain drain). According to the plant manager an important goal was “knowledge transfer” within the operations staff.

Solution

exida conducted an alarm management best practices training class to help Ashland’s multifunctional team gain a common understanding and to shape their vision for the future. This was followed by a two day alarm philosophy development workshop which de ned Ashland’s alarm management guidelines (e.g., alarm prioritization, criteria for having an alarm, alarm classes, alarm setpoint methodology, and treatment of non-alarm notifications).

Prior to beginning alarm rationalization, the DeltaV alarm con guration was exported and loaded into SILAlarm. The CVE tool was used to analyze three years of operational data (stored in OSI PI) in order to establish actual operating envelopes and recommended alarm setpoints. This information was imported into the SILAlarm master alarm database.

SILAlarm was then used to facilitate the alarm rationalization process and document the results. exida “kicked off” the rationalization process and trained the Ashland team so they could effectively lead the process themselves. Key alarm rationale such as cause, consequence, corrective action, and operator time to respond were recorded so that they could be displayed in DeltaV Alarm Help. Rationalized alarm settings were exported from SILAlarm and imported into DeltaV. This updated parameters such as limit, priority, class, hysteresis, on/off delay, and suppression time, while also automatically con guring the DeltaV Alarm Help faceplate for each alarm (thus saving engineering time).

Results

The Ashland team completed rationalization of some 7000+ alarms over the course of several months. Operators from all crews took part in the rationalization, which helped with buy-in and training. For example, operators saw rst-hand how alarm priority would now re ect the urgency of response and the severity of the consequences. Taking part in the rationalization process with the senior operators was educational for the novice and intermediate operators yielding significant knowledge transfer.

Key Findings

  • A large number of High-High and Low-Low alarms were eliminated since their operator response was not different from the associated High and Low alarms.
  • There was a large number of alarms in the “LOPA-listed” class, which meant that numerous alarms were being used to provide risk reduction.
  • Some existing alarms were found to NOT meet the criteria for being an alarm, but were still needed by operations. These notifications were recon gured as Alerts or Prompts so that they could be annunciated and displayed to the operator separately from alarms.
  • Displaying the results of rationalization in DeltaV Alarm Help aids novice and intermediate operators to understand the meaning and consequence of configured alarms.