Go beyond condition monitoring

Despite condition monitoring, unplanned outages continue to be an issue, significantly impacting financial performance through lost production and extra repair costs.

By Neil Cooper, Invensys Process Systems

Share Print Related RSS
Page 1 of 2 « Prev 1 | 2 View on one page

In today’s environment, chemicals makers face ongoing pressure to operate safely and reliably at the lowest possible cost. Most companies have adopted condition monitoring technologies as a key approach to improve the availability and reliability of process equipment and to proactively avoid downtime.

While these condition monitoring solutions are providing solid value for most plants, unplanned outages continue to be an issue, significantly impacting financial performance through lost production and extra repair costs.

So, in this article, we’ll explore the underlying challenges and introduce the concept of condition management — an enhanced approach that helps companies reap the full benefit from their condition monitoring investments. We’ll also discuss how to get started in condition management, looking at both business and technical considerations.

Building upon a baseline

For years plants have tracked the health of key equipment. Sites generally have focused on a relatively limited deployment of specific monitoring technologies aimed at protecting critical assets — primarily large rotating equipment. This has become simpler with the widespread availability of highly capable fieldbus-enabled monitoring tools, e.g., for vibration, temperature, pressure, corrosion and fluid analysis.

Now, the advent of intelligent field devices and sensors as well as low-cost wireless units that can be deployed into areas where hard wiring would have been cost-prohibitive is extending these base capabilities and the data they provide.

Unfortunately, plants aren’t enjoying the full potential of the data for three reasons:

  1. The focus of condition monitoring deployments is too narrow. Sites need to instrument a wider range of assets, so management can look beyond specific equipment to entire process areas or complex asset sets such as heat exchangers, dryers and other plant units.
  2. The volume of data available now is huge and will continue to grow exponentially. This creates a significant knowledge management challenge around making sense of the data. Exacerbating the problem, the aging workforce means that plants are losing more and more people with critical operational experience, knowledge and interpretive skills.
  3. Many companies still have operational silos. Plant personnel aren’t collaborating to detect, manage and analyze emerging issues. The net result is continued outages, even when the underlying condition or trend had been correctly detected.

Condition management defined

Addressing this set of challenges requires an enhanced, more holistic approach — condition management. Under this approach, the vast array of condition data is the entry point to a five-step process where the data are:

  1. aggregated and rationalized;
  2. combined to create context and support proper analysis;
  3. clearly presented and communicated;
  4. systematically managed to ensure the timely, accurate, consistent and effective resolution of the underlying issues; and
  5. used as input to an ongoing continuous improvement process.

The first three elements are aimed at turning the data into information, changing the condition information from “noise” in the eyes of operations personnel into useful decision support intelligence for all personnel.

The aggregation and rationalization also need to address the varying types of data, the time element (real-time, near-time and offline) as well as the various access and communication methods utilized by vendors.

Once the data are turned into properly contextualized and actionable information, it’s critical to manage the use of the information. It comes back to the fundamental difference between condition monitoring and condition management. Condition management information helps unlock the usefulness of the condition data by:

  • driving the appropriate workflow/processes to resolve the issue(s), bringing together the key personnel across operational disciplines (engineering, maintenance, control, safety, etc.).
  • providing input to an ongoing knowledge management process where new situations and their appropriate resolution are systematically captured and documented.

Further, condition management supports Six Sigma or Lean Sigma initiatives by supplying input for an ongoing process where the knowledge base is regularly reviewed and refined.

A telling example

A leading specialty chemicals maker discovered the value of the approach but only after a serious incident. The process uses a significant amount of power, so the company operates a 300-MW captive power plant. The site had deployed condition monitoring tools on assets there — vibration, rpm, and amperage on the pumps in the cooling towers, the manufacturer’s monitoring tools on the turbine, and assorted flow and temperature meters throughout the cooling system.

When the primary pump in the cooling tower failed, the control system initiated a cutover to a back-up pump and then cleared the alarm. An operator entered the occurrence in the log, where the required follow-up was to have maintenance staff repair the primary pump.

Shortly after this initial incident, the operator started receiving alarms that the temperatures in the cooling system were drifting out of range, coupled with pressure warnings. Assuming that this was a “storm” created by the cutover to the back-up pump, the operator acknowledged and cleared the alarm set.

Close on the heels of this second set of indications, the turbine monitoring system flagged a significant temperature variance and recommended an immediate shutdown. Again, on the assumption that this was a blip caused by the cutover, the operator cleared the alarm.

After two minutes, which was the defined “re-alarm” time, the turbine monitoring system reported dangerously high temperatures and again recommended a shutdown. This time, the operator (per the written procedures) contacted the plant manager, who gave approval to proceed with the shutdown.

This caused a production outage that impacted delivery of a critical intermediate to one of the company’s key customers. Further, the sequence of events and the elapsed time from initial warnings to shutdown resulted in extreme temperatures within the turbine. This led to significant damage, necessitating the replacement of its main bearings.

The root cause turned out to be that back-up pump had not come online as expected. In doing the situation analysis, the company discovered a number of specific issues:

  1. The back-up pump wasn’t instrumented in the same manner as the primary one, so there wasn’t any critical warning to the operator.
  2. Condition information for the primary pump and the back-up pump weren’t linked.
  3. The pump, temperature/pressure and turbine data weren’t connected. Each was handled discretely by the operator in separate areas of the human/machine interface (HMI); the combined elapsed time in dealing with the discrete events exceeded the safe shutdown point for the turbine.
  4. No automated communication alerted maintenance, engineering or plant management to the developing issue.
  5. The operator didn’t have any way of seeing the maintenance status of the primary assets including the pumps — this would have shown that the back-up pump had a pending inspection because of previously reported issues.

Looking at this real-life example in its entirety, no particular action or practice alone could be blamed. Instead, the situation arose because of the lack of context and ineffective use (i.e., management) of available information.

The foundation for success

As the example underlines, effective condition management must address all of the elements together. Specifically this means:

  • collecting the right data (condition, process area and system);
  • gathering the complete set of data necessary to provide the context needed to accurately assess an issue and its impact;
  • automating the response, including actions and escalations; and
  • enforcing the post-event analysis and continuous improvement process.

Moving to condition management is ultimately a knowledge management challenge. In many companies, such a move requires a change in both technical and business process practices. This challenge is manageable but firms need to be committed to the change in approach and need the discipline to effectively implement and sustain it.

The process has to include the use of supporting tools and technologies that allow the capture of the institutional knowledge currently existing in plant personnel across all the disciplines.

Figure 1. Success depends upon properly using wide variety of inputs from all plant levels.

Figure 1. Success depends upon properly using wide variety of inputs from all plant levels. (Click image to enlarge).

Condition management fundamentally is a closed-loop model with four main elements — collect, analyze, act and optimize. This model provides the framework for translating the business needs into a solution architecture for a plant. Figure 1 shows the relationships among these elements, starting at the process measurement level through decision support and feeding back to the process.

Getting started

As with any change process, it’s critical to understand the starting point. This demands taking a hard look at several areas and asking some tough questions:

Culture. Does the company understand that there are issues and that there’s inherent and significant value in resolving them? As a simple test, can people articulate the impact or cost of an unplanned outage? Is the company really willing and ready to change? Effective condition management will include changes to business processes and roles, so these points are fundamental.

Business processes. Are the firm’s processes documented? Have they recently been validated or benchmarked against others in the industry and best practices? In many cases, simple process enhancements or better communication can deliver significant performance improvements. Don’t apply technology without this process baseline. Note in particular that a formal approach based on root-cause analysis and including continuous improvement efforts is a fundamental requirement.

At a broader level check whether a formal lifecycle management program is in place. A recent survey conducted by the ARC Advisory Group found that companies that had adopted such a program had a significantly better return on assets than those that hadn’t. The research also indicated that the largest portion of the gains come from properly managing the “operate and maintain” stages of the lifecycle. It’s precisely here where condition management is a key enabler of improvements. The ARC lifecycle model, (Figure 2) shows the relationship between plant asset management (PAM) and an asset lifecycle management scheme.

Figure 2. In CALM, the operate/maintain stage offers the largest portion of return-on-asset improvement. Source:ARC.

Figure 2. In CALM, the operate/maintain stage offers the largest portion of return-on-asset improvement. Source: ARC

Page 1 of 2 « Prev 1 | 2 View on one page
Share Print Reprints Permissions

What are your comments?

You cannot post comments until you have logged in. Login Here.

Comments

No one has commented on this page yet.

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