About the Author: Efrain Rios is the founder of Fortress Oil & Gas, LLC, a full-stream asset integrity solutions provider for the oil & gas industry. For the last 20 years he has specialized in risk management, regulatory compliance, operational efficiency improvement and cost reduction strategies for mechanical integrity programs. This includes the direct management and accountability of the asset integrity technology systems and governing processes for upstream operations spread over 12 countries. Efrain is a member of NACE International and the API Sub-committee on Inspection and Mechanical Integrity (SCIMI). He is also the leading expert on software solutions utilizing asset integrity management (AIM) systems and mobile data collection technology.
In the industry today, there are numerous applications being used to manage asset integrity information, i.e. data and records associated with design, construction, corrosion, inspection, process chemistry, and degradation remediation. As the first article in a 5-part series, this is intended to provide readers with an overview of inspection data management systems (IDMSs), how they help support mechanical integrity assessments, and some common challenges that users face. The other four parts in this series are as follows:
- Part 2: Selecting the Right IDMS
- Part 3: Filling Functionality Gaps Through Development
- Part 4: The Importance of Standardization
- Part 5: The Implementation Hurdle
WHAT IS AN IDMS?
An IDMS is a software application used to manage inspection results and schedules for fixed equipment such as pipework, heat exchangers, pressure vessels, and storage tanks. They also provide access to certain asset integrity records that companies are required to maintain for the life of their equipment. Per inspection codes API 510 (pressure vessels), API 570 (piping), and API 653 (storage tanks), inspection results must be analyzed to assess the equipment’s integrity and determine whether (a) it’s suitable to remain in operation until the next scheduled inspection date without intervention or (b) its integrity has been compromised and requires some form of remediation, e.g. repair, alteration, re-rate, or replacement. The software assists in these assessments by calculating equipment corrosion rates, remaining lives, next inspection dates, and retirement dates based on stored thickness data from previous inspections. It is also common for an IDMS to store other pertinent information such as design temperatures and pressures, materials and codes of construction, installation dates, insulation types, and scaffolding or man lift requirements. While there are many IDMS applications on the market today, some of the most widely recognized names include Antea, Visions, PCMS, UltraPIPE/PS AIM, Meridium and many others.
WHAT ARE SOME COMMON CHALLENGES?
Although companies use an IDMS as a tool to help manage their inspection programs more effectively, it is very common for problems to arise over time. Typical issues faced by most inspection teams are listed below.
- Low confidence in KPI reports
- Inconsistent data processing techniques
- Untimely data entry
- Unreliable calculation outputs
- Duplicate entries with conflicting information
WHAT ARE THE TYPICAL CAUSES?
The issues listed above, as well as most other problems, primarily stem from four key areas:
The absence of well-defined and documented data management practices.
As you will see in part 4 of this series, “The Importance of Standardization,” defining and documenting standardized data entry processes and other key aspects of information management (work processes, roles and responsibilities, information storage locations and access procedures, permission levels, etc.) is the foundation of a high-functioning program. Creating a single reference document that addresses each of these areas helps team members to:
- Minimize safety and compliance risk
- Prevent future database “clean-up” projects
- Maintain confidence in the data
- Ensure that report queries can function properly
- Reduce time requirements for identification of mechanical integrity concerns
- Minimize potential for hidden integrity issues
- Decrease onboarding time and cost
- Increase data processing efficiency
- Streamline future data automation efforts
- Facilitate future continuous improvement such as paperless inspection and work management integration
An incorrectly installed or poorly configured IDMS application
Since inspection work processes often vary from company to company, IDMS developers have created software applications that are highly flexible. However, when users lack in-depth knowledge of the software’s functionality, this flexibility very often creates problems. Properly configuring the software to process inspection data is critical to accurately assessing equipment’s suitability for continued service and maintaining conformance with respective inspection codes.
For example, one very widely used IDMS allows users to determine an equipment item’s remaining life by averaging the remaining life values calculated at each of its condition monitoring locations (CMLs). This necessarily means that some CMLs on the equipment will have retirement dates earlier than the retirement date of the equipment they are on. This issue may also appear within the inspection due dates since they are calculated using remaining life values. This type of data conflict is one that can create a lot of confusion during annual inspection planning and throughout the year as inspections are completed. Also, some companies rely on these averaged remaining life values to drive their integrity management decisions. Teams may believe that they have enough time to plan a replacement only to find that the equipment has failed during the planning period. As one can see, a poorly configured database can create conflicting inspection dates, retirement dates, and remaining life values potentially leading to overdue inspections and poorly informed integrity management plans.
Uncontrolled levels of software access or improperly assigned permissions
Most people would agree that a user’s ability to access certain functionality within a software application should always align with their competency level. However, far too often users are permitted full access to an IDMS with little or no oversight. Without truly understanding the impact their actions, these users can unintentionally create highly undesirable consequences. For example, providing full access to an entry level user might lead to them accidentally changing the inspection schedule for an entire plant when they only intended to update the schedule for a single piece of equipment. With the right level of controls and proper oversight, these types of large scale issues can be avoided.
Outdated or no formal training
Quite often, companies will postpone IDMS training to help minimize inspection program expenses. In these cases, experienced personnel use on-the-job scenarios to share knowledge with junior team members. While this may be great for the short term, it is usually detrimental in the long run. Over time, the team’s collective knowledge decreases because less frequently-used skills are lost, and new team members are limited to informal peer-to-peer training which is often inaccurate.
As you can see an IDMS software is a critical component to an inspection data management program. However, it is not enough to simply install the software and hire people to use it. The overarching inspection data management program must be maintained. Otherwise, inspection programs risk losing confidence in their data and a reducing their ability to manage mechanical integrity issues, which later forces them to spend a great deal of time and money fixing problems that could have been prevented. Therefore, it is highly recommended that inspection data management programs are assessed annually (including a detailed review of the IDMS itself) to ensure a high level of data quality and mechanical integrity are maintained.
In part 2 of this series “Selecting the Right IDMS,” we will discuss the necessary considerations for selecting a new inspection data management system, including the selection process, scoring system, core functionality comparison, cybersecurity, remote access, and potential bolt-on tools.