Roots in reliability

Reliability tools shouldn’t be an afterthought. Here’s how to build them into your project from the get-go.

By Arturo Medina, Emerson

1 of 2 < 1 | 2 View on one page

Manufacturing organizations often view tools and technologies for ensuring field process instrumentation reliability only as a vehicle for delivering operational benefits – in other words, something the operations team can be responsible for after a project is completed. As a result, the focus with project implementation has long been on delivering short-term results for capital project execution while leaving reliability teams to figure out how and where they can implement reliability features long after the project execution team has moved on.

New developments in project execution, though, are revolutionizing this old model. Instead of waiting until after project execution is complete to implement reliability strategies, many project teams are working with reliability champions to develop new programs that include reliability technologies in the project scope. These new developments in project design are enabling teams to execute projects faster and more successfully while simultaneously building a foundation for a reliability program that is online from the moment the plant begins operation.

Selling the project execution benefits of reliability

When operations teams – specifically reliability and maintenance personnel – help project teams understand the ways in which reliability technology can improve project execution, everyone wins. Project teams win by delivering faster, less-expensive, and more-successful implementations, while operations and reliability teams reap the benefits of having their own systems online and ready to go as soon as a new project is completed. Operations and reliability leaders who communicate and implement solutions beneficial to project implementation success and to long-term reliability can become project influencers, driving future decisions that incorporate operational certainty into project certainty.
At the heart of this new project delivery model are three key strategies that move the focus on reliability from project completion to project scope, paying significant dividends in fewer project delays and lower overall project costs.

Strategy 1: Using reliability to speed commissioning

With only a handful of technicians responsible for hundreds or thousands of devices in the field, reliability teams have needed to develop strategies to increase efficiency. Key reliability technologies have allowed the maintenance team to centralize monitoring and configuration of devices to perform their tasks with more speed and accuracy.

Because the commissioning process for capital projects often is plagued by inefficiency, commissioning is an ideal area for collaboration between reliability and project teams. Configuration of devices during commissioning is slow and cumbersome, with multiple technicians traveling back and forth between devices to check accuracy and functionality. Moreover, configuration typically is performed only after devices have been delivered and installed. Any errors here can have a significant negative impact on start-up, resulting in thousands or millions of dollars of lost revenue. 

Project teams can use reliability technologies to significantly speed commissioning. By replacing manual configuration with bulk configuration of field devices via templates, teams can save at least one hour of work per device. This can mean thousands of hours saved in the field (see Figure 1).

Moreover, incorporating reliability technology into project scope takes configuration off the critical path, diluting it across the early months of the project, as configuration will no longer require devices to be on site and installed. Configuration specialists can be contacted months in advance to create templates in preparation for device installation. Saved work hours can be used on other critical commissioning and start-up tasks.
Incorporating reliability tools to realize commissioning benefits will enable project teams to regain control over timelines, ensuring that configuration needs don’t delay start-up. In return, reliability teams gain the advantage of having their tools in place, accompanied by an accurate asset database, from the first day of operation.

Strategy 2: Using reliability tools to use labor more efficiently

Reliability teams cannot afford redundant work in the field. Time spent traveling back and forth to devices and repeating the same tasks is time wasted. To prevent technicians from revisiting the same devices over and over, reliability technologies allow maintenance personnel to perform multiple tests with multiple steps using automated processes from a centralized location.

Rework is all too common during large capital projects. After visiting each device to ensure mechanical completion, technicians need to perform device testing, which often requires that technicians revisit equipment to ensure loop and interlock functionality.

Forward-thinking project teams are incorporating reliability tools into project scope to reduce or eliminate this redundant work during project implementation. For example, reliability teams frequently use automated loop checking and interlock testing to replace the old method of testing: connecting a handheld device to each unit in the field. Using reliability technologies lets technicians perform testing from the convenience of the control room or the maintenance shop with test steps managed and checked for accuracy by the asset management system. Redundant trips to the field are eliminated.

Another area where reliability time-savers can translate directly to project execution savings is in generating documentation. The reliability team understands that the last thing a technician needs to be doing is trying to balance a laptop along with a handheld and a clipboard, attempting to document 200–300 device configuration parameters. When those 200–300 parameters are multiplied by thousands of devices, as they are in most capital projects, the cost and hassle of manual documentation of device and activity data can quickly spiral out of control.

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.

Comments

No one has commented on this page yet.

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