Don't "set it and forget it" when it comes to your automation systems

Maintaining automation systems demands a strategic, collaborative approach.

By Christine LaFave Grace, managing editor

1 of 2 < 1 | 2 View on one page

Who’s monitoring the monitors at your plant? That is to say, with the push to implement new technologies that will help monitor equipment performance and run all of the data that they collect through software that aims to provide early notice of potential performance problems, how do you ensure that said technologies are operating optimally? Better-informed, faster, smarter decision-making depends on access to accurate data, and neglecting maintenance of the tools your plant depends on to deliver that data will undermine any digital initiative, however modest or ambitious it is.

Keeping that reality in mind, Plant Services spoke with a range of industry experts in system integration, utility operations, digital services, and more about best practices for maintaining automation systems. Here are their dos and don’ts for monitoring your monitors.

Do: Get off the ground on the right foot

Just because you have a specification for how a control system should be built or a software platform should be customized to address your teams’ priorities doesn’t necessarily mean that’s how it will get built. And in the critical commissioning and startup stage, it’s vital to identify and resolve any discrepancies as quickly as possible.

Running standardized site acceptance testing is a crucial first step to ensure that time and money aren’t wasted addressing connectivity or functionality issues once a new control system or software platform is up and running, says Nate Kay, P.E., project manager with Martin CSI, a member of the Control System Integrators Association. “Sometimes (a system) doesn’t get installed exactly the way it was designed maybe on the process side,” he says. “If there were any changes made on the fly or issues that occurred during the installation … we work with the contractors and the customer to determine where the problem is.”

In addition, it’s highly valuable to incorporate automation systems into your overall maintenance strategy, notes Richard Gaines, director of the Integrated Smart Operations Center (iSOC) at the New York Power Authority. iSOC, a central monitoring and diagnostics center in White Plains, NY, relies on predictive analytics software and smart technologies deployed across NYPA’s 16 power plants, more than 1,400 circuit miles of transmission lines, and substations statewide to detect operational anomalies and help prevent asset failures and power interruptions. A fully digitized, integrated approach to physical asset management means ensuring that the maintenance of data-collection tools isn’t an afterthought.

“When sensors are installed, we have to get them into the standard PM program that we use for all instrumentation,” says Gaines, a 36-year veteran of the NYPA. “Whether we’re doing gas analysis on a transformer or we’re looking at pressures, temperatures, and flows on a pump or turbine, our philosophy is that monitoring and diagnostic instrumentation shouldn’t be any different from the other instrumentation we use in process control. Even if it’s just (for) monitoring and diagnostics, it’s still just as important as (other) instrumentation for process control. So it gets rolled into our maintenance management system.” 

Do: Verify your data

Once the data starts streaming in from your new, automated condition-monitoring technologies, how can you know – with certainty, and over time – that the data really is valid? After all, for users of these connected technologies, condition and asset performance data underpin decisions about whether, how, and when to service equipment and adjust operating parameters to make processes run more efficiently. “Data quality is key,” says John Rosenberger, director of iWAREHOUSE GATEWAY and global telematics for The Raymond Corp., “because the collection systems could be sending data (to the cloud), but if they’re sending junk” – inaccurate or incomplete data – “now I’m throwing off a lot of those predictors that I have thresholds and controls set for.”

Periodic data validation, which can be performed by an independent third party (such as an outside laboratory) or by an OEM as part of a service agreement, is essential for ensuring data integrity. At iSOC, as part of a transformer monitoring system, oil gets sampled from transformers every six months and sent to a lab to ensure that values from the samples align with values taken from the transformers’ online sensors.

Once the third-party lab completes its analysis of an oil sample, the NYPA downloads it and runs it through an application that does a comparison between the lab sample and the instrument sample, Gaines says. “Our monitoring and diagnostics engineers will then determine whether there’s concurrence or a discrepancy between the two samples,” he says.

A focused effort on process instrumentation monitoring and maintenance, as well as having some redundancy in instrumentation, has proved useful in alerting the iSOC team when there might be a problem with one of its automation technologies, Gaines notes. “Often what we see is it’s not necessarily the machine itself that has a health issue; it might be the instrument on the machine,” he says. “When we’re profiling data for instance coming off a pressure transmitter, and we see that the trend line is flat, it’s not changing, we know that the instrument failed in place.”

The effort to validate data and quickly identify deviations from expected values is supported by improved communication and collaboration across traditionally siloed departments within an organization. One of the benefits of today’s network-connected automation technologies is that they’re narrowing the divides between IT and OT teams and between the office and the plant floor. “A lot of systems in the past have been stand-alone; they existed isolated on their own network so you relied on maintenance personnel to follow a regular preventive maintenance schedule for (them), but what we’re seeing more of is networking that ties into the whole industrial internet of things side, where instead of having this isolated system inside a box where only a few maintenance people interface with it, we’re starting to tie that in to the rest of the plant and also bridge the IT-OT (gap),” Martin CSI’s Kay says.

He offers an example: At one plant with which Martin CSI has worked, “the business side maintains the inventory, what they’ve ordered, where it goes; the maintenance side, they see the levels in real time on the screens,” Kay describes. “And we’ve started to work to merge those two together so that you have that data from the plant floor and the business side can compare it with their orders, their information, and you can detect problems that way. So, for example, if the inventory is way off and doesn’t coincide with what the plant floor sees…we might generate a preventive maintenance task so the maintenance department will look at it and see, is a level probe off, are the operators bypassing the safety procedure to get more out when they shouldn’t, that type of thing.”

1 of 2 < 1 | 2 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.


  • I'd add ... "DO set more alarms in your HMI/SCADA. Increase your reliability by writing alarms that monitor conditions before failure, to help drive you to use best practices like PM, PdM, TPM.


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