Integrity Compliance – Create and Process Analysis
This an overview of the Integrity Compliance module as a part of our Cognitive Integrity Management user guide video series. This module allows the user to:
Integrity Compliance Module:
- Analyze in-line inspection data that was just ingested the vendor report
- Run What-If scenarios using a library of attributes and conditions to identify existing threats
- Create an action plan for any identified threats
Once you login to Cognitive Integrity Management you will select Integrity Compliance under the processes tab on the main header menu.
The layout of this screen is very similar to the assessment planning module. However rather than creating an assessment, you will be creating a series of analysis’.
You start the process by creating a new analysis by clicking the new+ button on the top right corner of the analysis table.
When creating an analysis you start off by selecting the system you would like to analyze. You then assign a name and choose the type of vendor report you will analyze by selecting from either preliminary report or final report. Then, you will choose the assessment you would like to look at. Finally, you will see a list of vendor reports assigned to the assessment, here you are able to select a single report or multiple.
Typically, you would want to assess the single vendor report you just uploaded.
Now we will cover each of the tabs under the vendor report table:
PODS> General > Pipe Properties > Interacting Threats > Conditions > Attributes> Validation
Just as assessment planning, all related PODS data to each system selected is loaded into the dashboard. This allows the engineer to double-check and ensure there are no updates required from the GIS team.
Now let’s click on the General Tab
We can start to configure the analysis under this tab. There are several types of analysis you can perform in the software with many ways to configure them. However, we have provided analysis templates that are out of the box. We have a default template for gas and one for liquid-based on regulatory conditions. For the purpose of the video, we will choose Liquid. As you can see, when the Liquid default analysis is selected, the rest of the fields on the general tab are auto-populated with the previously determined values for a Liquid analysis. We can set up any number of custom default analysis templates with settings of your choice to save you time when creating analysis in the future.
Let’s review the different options you have here. We first define whether we want tool tolerance applied. Users can select ‘None’ to have no tolerance applied at all to the analysis, or ‘Provided in ILI file’ if the tolerance values are provided in the vendor file that we are analyzing the data for. Next, we select whether the tolerance is applied to HCA and Non-HCA conditions or both. Next, we select which operating pressure we would like to use for analysis. Finally, we apply the corrosion growth rate we would like to use for the analysis from the following options: Half-life, pit-to-pit average, pit-to-pit maximum, pit-to-pit minimum. For the pit-to-pit options, when a single anomaly has more than one historical match, these selections specify whether you prefer to calculate the minimum, average, or maximum rate of growth. Half-Life will be used by default for any records where there is no previous anomalies to align to, or where the pit-to-pit growth rate is negative.
Now moving into pipe properties:
To measure the integrity compliance conditions, we need to input information about the pipe medium. This information can be imported from either PODS (if it has been connected to CIM) or by the ILI report if the information is provided by the vendor. This can be specified in the ‘Pipe Properties Source’ dropdown. A user can input default pipe properties that CIM will use in the instance where it does not find pipe properties in the source that was specified above. The inputs required include wall thickness, yield strength, diameter, nominal diameter, seam type, installation date and MOP.
Interacting Threats tab:
Under this tab, the user can select which previous vendor reports they would like to compare against when analyzing interactions. Through this functionality, the user can determine which logs they would like to consider for interactions.
Under this tab there are approximately 200 conditions or criteria that CIM can identify – these conditions cover standard PHMSA regulatory requirements such as immediate, 180 days etc,. It also includes best practices from all of our customers as well as some we have created using our own criteria based on research our data science team has done. If you had previously selected a Default Analysis type (in this case we selected liquid), then the conditions would be auto-populated already. The user has the option to just use the defaults selected, or remove and add conditions as they please.
On the left-hand side is a list of the condition categories that have been configured. Checking a category off, opens up the conditions in that category to be selected for the analysis.
On the right-hand side, we can toggle criteria that we would like to look at within a regulatory required window. Clicking each category will show which conditions are below it. Checking or unchecking a condition adds or removes it from your analysis.
A user can also change re-assessment intervals or adjust them on the company RIA conditions, to ensure they get ahead of conditions in future.
Also, we can flag growth conditions with top side, bottom side, dent
The Attributes Tab:
This tab is where the user can tweak how the conditions are going to be evaluated, such as changing the ACN value for cracks, dents in close proximity, setting assessment interval periods etc. Again, these will be auto-populated with the pre-set values if you use a default analysis type as we did here. To edit any of these attributes, just click the edit icon, adjust the value, and save.
Finally, the validation tab
This tab functions the same as the assessment planning module where the system will alert users if there is key missing data.
If the validation area is clear, the user can process the analysis. Remember, you can continue to edit and save your analysis until you are comfortable with it and feel that it is ready to process. Once you are ready, click the Process Analysis button. This will kick off the analysis in the background. This analysis should be complete in a couple of minutes, however, if a more in-depth analysis is running such as threat detection it can take up to 15 mins. The notification center will notify the user once the analysis is completed
We have now covered a basic overview of the Integrity Compliance module within Cognitive Integrity Management. Please feel free to send any questions related to this module to firstname.lastname@example.org
Please continue to the next video in the series