Patent Application
20240117944
Aspects of one or more non-limiting embodiments of the disclosure generally relate to analyzing the integrity of oil and gas transmission pipes and to methods, apparatuses, and systems for providing an interface for comprehensively collecting a wide variety of pipeline integrity related data sets, and inspection and survey reports, to process the integrity status and to determine the remaining lifetime of each point of a pipeline on a sophisticated mapping platform. In particular, aspects of one or more non-limiting embodiments of the disclosure generally relate to pipeline in-line inspection data conversion to integrate different pipeline inspection (In-Line Inspection (ILI)) reports into one standard platform.
Corrosion of metal is a long-standing historical and global problem in a wide range of industries, and the oil and gas industry is not an exception. Pipeline operators are faced with many questions about the presence, location, and severity of corrosion in their oil and natural gas pipeline systems. In particular, pipeline operators need easy and centralized access to comprehensive pipeline integrity information, from many different sources, to accurately assess the integrity of each point of a pipeline and deploy the results of such assessment efficiently and effectively.
However, there are several ILI vendors who each provide different pipeline inspection ILI reports. There is a need to standardize all of these different reports to be able to process them to populate the Inspection ILI results and upload them in one standard platform.
Illustrative, non-limiting embodiments of the present disclosure address the above disadvantages and other disadvantages not described above. Also, a non-limiting embodiment is not required to overcome the disadvantages described above, and an illustrative, non-limiting embodiment may not overcome any of the problems described above.
Aspects of one or more example embodiments allow a user to access databases to access information needed to comprehensive pipeline integrity analysis in an In-Line Inspection (ILI) platform. In particular, aspects of one or more example embodiments integrate various databases to allow easy access and centralized storage of all needed information for pipeline integrity assessment, regardless of ILI service provider, to deploy the results, for example, in an ILI module of a pipeline integrity application, or in an augmented reality platform.
Aspects of one or more example embodiments may include a conversion tool and a standard to standardize any In-Line Inspection (ILI) report to be uploaded in a Pipeline integrity platform to further steps to determine the internal and external corrosion rate in the oil and gas pipeline.
Aspects of one or more example embodiments may integrate different pipeline inspection ILI reports of different formats into one standard platform to facilitate comprehensive ILI analysis in one standard platform.
Aspects of one or more example embodiments may include data conversion, transferring, standardization and making data ready to be uploaded in a standard ILI data process platform.
Aspects of one or more example embodiments may standardize the domain range of pipeline ILI inspection entities including but not limited to Pipe joint manufacturing type, Orientation of anomalies in standard units, features domain range, anomalies domain range, etc. all in one platform.
Aspects of one or more example embodiments may provide a method including collecting, by a processor, In-Line Inspection (ILI) pipeline inspection reports having different formats; converting, by the processor, the different In-Line Inspection (ILI) pipeline inspection reports into one standard platform; and generating, by the processor, an integrated pipeline data user interface using the one standard platform.
Additional embodiments will be set forth in the description that follows and, in part, will be apparent from the description, and/or may be learned by practice of the presented embodiments of the disclosure.
Features, advantages, and significance of non-limiting embodiments of the disclosure will be described below with reference to the accompanying drawings, in which like signs denote like elements, and wherein:
The following detailed description of example non-limiting embodiments refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements.
The matters defined in the description, such as detailed processes and elements, are provided to assist in a comprehensive understanding of the example embodiments. However, it is apparent that the example non-limiting embodiments can be practiced without those specifically defined matters. Also, well-known functions or constructions are not described in detail since they would obscure the description with unnecessary detail.
Further, one or more features or components of one embodiment may be incorporated into or combined with another embodiment (or one or more features of another embodiment). Additionally, in the flowcharts and descriptions of operations provided below, it is understood that one or more operations may be included or omitted, one or more operations may be added, one or more operations may be performed simultaneously (at least in part), and the order of one or more operations may be switched to convert any ILI data set to a standard ILI template to be used in any Pipeline integrity application(s).
Even though particular combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of possible implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of possible implementations includes each dependent claim in combination with every other claim in the claim set.
No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items, and may be used interchangeably with “one or more.” Where only one item is intended, the term “one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” “include,” “including,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Furthermore, expressions such as “at least one of [A] and [B]” or “at least one of [A] or [B]” are to be understood as including only A, only B, or both A and B.
Also, in the present specification, it will be understood that when elements are “connected” or “coupled” to each other, the elements may be directly connected or coupled to each other, but may alternatively be connected or coupled to each other with an intervening element therebetween, unless specified otherwise.
A non-limiting embodiment consistent with
A non-limiting embodiment may a part of a whole integrated process, which includes aspects of U.S. patent application Ser. No. 17/942,712, PCT/IB2021/053901, and U.S. Provisional Application No. 62/989,065. A non-limiting embodiment may improve the functioning of a computer, or improve another technology or field, by standardizing input data from different Pipeline integrity application(s). A non-limiting embodiment, as explained in detail with references to Tables 5-20 below, may provide a database model and solution for this challenge of standardizing input data from different Pipeline integrity application(s) and, thus, improve computer capabilities.
By way of illustration, there are several ILI vendors who provide Pipeline inspection ILI reports. All of these reports need to be standardized to be able to process them to populate the Inspection ILI results and upload them in one standard platform.
For instance, the below data sets may be available for further assessment:
In general, a quality ILI report is referenced to inspection results of a specific pipeline. Therefore, the transfer of the quality data on the standard platform is a necessary action prior to any further ILI analysis.
When transferring the quality data of an ILI run with reference to a standard platform or system, the data can be automatically uploaded to an inspection lot for a pipeline.
Alternatively, a user can use the functions to transfer data to any other desired inspection software or augmented reality platforms. Using the latter function, a user can transfer the quality data prior to any ILI assessment to a standard inspection.
According to a non-limiting embodiment, an ILI conversion sub-module may be implemented. If the ILI result is not acceptable (above steps for tool performance validation and results verification), the ILI dataset cannot be used, and it needs to be repeated.
Unless specified otherwise, the formulation for acceptable data loss for magnetic tools may be: the maximum acceptable sensor loss (primary sensors) and/or data loss is 3% and continuous loss of data from more than three adjacent sensors or 25 mm circumference (whichever is smallest) is not acceptable.
Unless specified otherwise, the formulation for acceptable data loss for Ultrasonic (UT) Test based ILI tools may be: the maximum acceptable sensor and/or data loss is 3% and the maximum allowable signal loss due to other reasons (e.g., echo loss) is 5%, whereby continuous loss of data from more than two adjacent transducers or 25 mm circumference (whichever is smallest) is not acceptable.
For all technologies, an alternative methodology can be to define data loss based on the required probability of detection (POD) of a specific defect like: the POD of an anomaly with minimum dimensions for a minimum percentage of the pipeline surface and pipeline length. E.g., an anomaly with length (L)≥20 mm, width (W)≥20 mm, depth (d)≥20% (or d≥1 mm for UT) in the pipeline may be detected with a POD≥90% for ≥97% of the pipeline surface and ≥97% of the pipeline length.
The tool operational data statement may indicate whether the tool has functioned according to specifications and may detail all locations of data loss and where the measurement specifications are not met. When the specifications are not met (e.g., due to speed excursions, sensor/data loss, etc.), the number and total length of the sections may be reported with possible changes of accuracies and certainties of the reported results.
A non-limiting embodiment may check the below items:
The measurement capabilities of non-destructive examination techniques depend on the geometry of the metal loss anomalies. These metal loss anomaly classes have been defined as shown in Table 1 below to allow a proper specification of the measurement capabilities of the intelligent pig. Each anomaly class permits a large range of shapes. Within that shape a reference point is defined at which the POD is specified.
An even distribution of length, width and depth may be assumed for each anomaly dimension class to derive a statistical measurement performance on sizing accuracy.
The reference point/size in Table 1 is the point/size at which the POD is specified.
Resolution of Measurement Parameters
The following units and resolution may be used for the measurement parameters:
Input Data Set
According to a non-limiting embodiment, as shown in
At operation 102, a Standard ILI template is called. Operation 102 includes downloading a reference and standard ILI data format. Regardless of the ILI report and the ILI service vendor, this operation is to standardize the data set. This template has been prepared based on a Pipeline Operator Forum (POF) standard and each header refers to a particular category of information.
According to a non-limiting embodiment, the pipe tally report may be a listing of all pipeline component features and anomaly features and may be reported in accordance (including terminology) with the report structure as shown by the Standard ILI template after conversion in Table 2, shown below:
Fully assessed feature sheets may contain the following information to the full sizing specification:
According to a non-limiting embodiment, the pipe tally report may contain the following fields in the given sequence:
Log distance,
A non-limiting embodiment may serve as a high-level in-line-inspection specification and thereby will cover all pipeline and Pipeline ILI reports.
A non-limiting embodiment specifies the unique methodology to convert ILI reports (geometric measurement, pipeline mapping, metal loss, crack or other anomaly detection during their passage through steel pipelines). The tools may pass through the pipeline driven by the flow of a medium or may be towed by a vehicle or a cable. The tools may be automatic and self-contained or may be operated from outside the pipeline via a data and power link.
To upload ILI data into a standard platform it is necessary to have a proper system/platform to transfer and to translate the data and units and convert them to one standard platform for any further actions.
This process specifies the advised reporting requirement to a pipeline integrity team to be used for geometric measurement, pipeline mapping, metal loss, crack or other anomaly detection during the ILI process and reporting. In existing industry systems, an end user cannot import different types of ILI reports. It is a challenge to translate different columns in different reports. Moreover, in many cases the data fields need to be translated into a standard platform. For example, for defects orientation, some ILI service providers are reporting based on degree, others with o'clock orientation. Some companies report start and end point of defects and the deepest metal loss point, but others just report deepest location in general metal loss. Plus, clustering rules and defects interaction criteria are different in ILI companies, and it could be a challenge to understand and use them in other ILI modules like in analytical reports, Fitness-for-Service (FFS), Defect assessment, etc.
A non-limiting embodiment may serve as a generic and standard platform to translate and convert all types of ILI reports into a single standard platform for ILI.
For this challenge, industry needs an interim spreadsheet, to translate different ILI vendors to be able to import into a standard suite and to conduct further assessments.
According to a non-limiting, as shown in
According to a non-limiting, this standard data entry form may be compatible with Pipeline Open Data Standard (PODS 7.0) data model.
A non-limiting embodiment may upload ILI data in a standard platform. It needs a proper system to transfer and translate the data and units and to convert them into one standard platform.
Operation 103 includes converting log distance to “log distance” in a standard platform. Operation 103 standardizes log distance in a required unit. This log distance may be references for all anomalies in further operations.
Operation 104 includes a process to convert any geo mapping coordinates to WGS1984 format. The World Geodetic System (WGS) is a standard for use in cartography, geodesy, and satellite navigation including GPS. This standard includes the definition of the coordinate system's fundamental and derived constants, the normal gravity Earth Gravitational Model (EGM), a description of the associated World Magnetic Model (WMM), and a current list of local datum transformations.
The latest revision is WGS 84 (also known as WGS 1984 ensemble):
It is established and maintained by the United States National Geospatial-Intelligence Agency since 1984, and last revised in January 2021 (G2139frame realization). WGS 84 ensemble is static, while frame realizations have an epoch. Earlier schemes included WGS 72, WGS 66, and WGS 60. WGS 84 is the reference coordinate system used by the Global Positioning System.
As a CRS standard, and expressing by URN, urn:ogc:def:crs:EPSG::4326, it is composed of:
After operation 104, the next step of the process is identified by arrow A in
Operation 106 includes converting and translating all existing features identification to standard features and terminologies such as corrosion.
Operation 107 includes categorizing feature identification in a standard manner.
Operation 108 includes a sub-process to add other pipeline facilities and ancillaries like launcher, receiver, etc.
As shown in
Operations 109 and 110 include standardizing joint numbers and their reference location in the entire process. In particular, operation 109 includes converting joint numbers into a STD platform. Operation 110 includes assigning joint numbers to all features enclosed in that joint into a STD platform.
After operation 110, the next step of the process is identified by arrow D in
Operation 120 includes converting pipe length for each joint into a STD platform. In the API 5L standard specification, the steel line pipe shall be delivered in accordance with the random length and approximate length in the order contract. In the API 5L specification 9.11.3.3 the tolerance for the pipe length is specified as below:
The common random length of the API 5L steel line pipe is designated at 6 m, 8 m, 9 m, 10 m and 12 m. The length also can be customized according to specific requirements.
Operation 120 includes standardizing the joint length based on standard unit (meter). Operation 121 is continuation of operation 120 and includes assigning the joint length to all features.
Operation 122 includes recalling required data from a segmentation process. “Pipeline Segment” means a section of a Carrier's pipeline, the limits of which are defined by two geographically identifiable points, that, because of the way that section of the Carrier's pipeline is designed and operated, must be treated as a unit for purposes of determining capacity. Segmentation is the process of defining pipe sectors with similar characteristics (external or internal) that can be used as units for integrity evaluation. Segmentation can be static—i.e., initially predefined —, or dynamic—i.e., adaptable to mechanical or external conditions.
Static segmentations use fixed distances defined arbitrarily (e.g., one mile) or it is defined by specific mechanical elements of particular interest such as valves. In static segmentation, there is considerable variability in the results of risk assessment and this may increase intervention costs due to unnecessary evaluations. Furthermore, critical zones can be hidden if risks are weighted throughout long segments.
In the dynamic segmentation, the length is not relevant as long the feature on which the segmentation is evaluated remains constant throughout the entire segment.
Operation 123 includes standardizing joint manufacturing type based on API 5L standard and domain range. If this data is not available in an ILI data set, the system will read this from a Pipeline segmentation table.
Operation 124 is a continuation of Operation 123 to include an acceptable domain range for joint manufacturing type.
Operation 125 includes standardizing seam weld orientation for each joint in the pipeline. The output will be utilized in a tool tolerances adds-on.
After operation 125, the next step of the process is identified by arrow E in
Operation 130 is similar to operation 125 but for pipeline ancillaries.
Operation 131 includes an alternative wall thickness, reading from a pipeline segmentation data set.
Operation 132 includes assigning a wall thickness for every joint along the pipeline.
Operation 133 includes another alternative to operation 131 if wall thickness is available in ILI data (most likely in Ultrasonic ILI data).
Operation 134 includes calculating the distance of each anomaly to an upstream girth weld.
Operation 135 includes standardizing orientation of a top left corner of each anomaly box in a flow direction.
Operation 136 includes determining a surface location of each metal loss anomaly. For example, it can be either Internal, External, Mid wall, Unknown.
After operation 136, the next step of the process is identified by arrow F in
Operation 140 includes determining the anomaly box size (length, width, depth).
Operation 141 includes calculating the location of upstream girth weld.
Operation 142 includes adding an extra comment from the ILI data set.
Operation 143 includes uploading a standard data set to the platform for further analysis.
Further Steps and Modules:
Sub-Module ILI Tool Operation Validation
The objective of In-Line Inspection (ILI) is to obtain data on the pipeline condition as part of the baseline and/or revalidation process. A key part of the process is verification of the ILI tool performance and an analysis process through the use of field verification.
The quality and consistency of data obtained from the field is important for statistical verification of the performance of the ILI processes. In many cases the Operator is only focused on confirmation of a reported feature rather than the performance of the overall inspection process. This process is to validate the process and performance of ILI tool.
This process specifies the requirements and a detailed method statement for ILI operational reports in the ILI suite. It covers the basic requirements for ILI reports such as Sensor loss plots, Magnetization level assessment, etc., as a supplementary assessment for a standard ILI platform.
This process specifies the advised operational and reporting requirements for tools to be used for geometric measurement, pipeline mapping, metal loss, crack or other anomaly detection during their passage through steel pipelines. The tools may pass through the pipeline driven by the flow of a medium or may be towed by a vehicle or cable. The tools may be automatic and self-contained or may be operated from outside the pipeline via a data and power link. But regardless of technique and brand of ILI tool, this process covers minimum acceptance criteria for ILI operation before any data evaluation.
This algorithm may be provided based on a Pipeline Operator Forum (POF) standard and a PODS database.
This process may serve as a generic in-line-inspection specification and thereby cannot cover all pipeline or pipeline operator specific issues. To support the pipeline operator in specifying/detailing some optional items in this process, the Information Technology (IT) team should be flexible for any change during runs for different pipeline cases.
From the previous process, we have an interim spreadsheet as standard platform to be translated from different ILI reports and vendor templates and also, we have captured most of analytical reports and assessments.
The tool specifications may be given. In addition, the following operational data may be provided, whereby each type of tool that has been used may be described separately:
Sub-Module ILI Field Verification
An ILI project is not complete until the reported features have been verified in the field. The process which is followed in the field to achieve this is important as inappropriate inspection techniques in the field can invalidate an otherwise valid report.
Field verification of reported features has two important aspects as this helps confirm:
It is necessary to determine the performance of the inspection, in order to conduct the required preventative maintenance plans with the certainty of risk required by the Operator. Factors of Safety (FOS) can only be used effectively if the tolerances being used to calculate the FOS actually match those provided in the inspection report or are more conservative in nature. It is not acceptable to use sizing tolerances that are not conservative, which means the actual measured dimensions are greater than those predicted even with the tool vendors tolerance added.
Most ILI suppliers will provide support for field verification activities. The ILI suppliers are not just interested in when the ILI tool has not performed to specification. They also need good quality field data to help verify the tool performance specifications for a range of feature types.
To achieve consistency with data collection it is necessary to set standards and protocols that must be followed.
This requires trained field personnel to gather the data with the required accuracy and competency so that the results can be relied upon. The techniques and equipment used must be tested and certified in calibration. The calibration and device tolerances must be taken into account when evaluating the results.
This process is to verify the results of ILI run and to accept the step to proceed further steps in the entire process.
Sub-Module ILI Correlation
Thus sub-module outputs a correlated ILI report based on field verification results. This output of this sub-module will be the final report to be assessed in this process.
Sub-Module Corrosion Morphology Change
This sub-module determines the dimension class and morphology of metal loss corrosions (pin-hole, pitting, General corrosion, axial slotting, axial grooving, circumferential slotting, circumferential grooving).
Sub-Module Tolerance Allocation Considering (Pipe Body and Hazardous Area)
This sub-module considers ILI tool tolerances which are different for pipe body and hazardous (HAZ) area.
ILI service provider reports the tolerances for Caliper and MFL tools as outlined in ILI tables. Typically, these tool tolerances are added to the measured dimensions of an anomaly when assessing its static strength. Fitness-for-Performance (FFP) assessments are performed in this process, once with, and once without, consideration of ILI tool tolerances.
An ILI company may classify features in accordance with the Pipeline Operators Forum (POF) specification based on their aspect ratio (width×length), prior to applying the appropriate tolerance.
Sub-Module Clustering
Following inline inspection of a pipeline, the interaction criterion used in subsequent defect assessment is agreed upon between the inspection vendor and the pipeline operator. The first process, referred to as “boxing”, is where a box is drawn around each feature. The second process, referred to as “clustering”, is a process to determine whether boxes located in close proximity to one another should be considered as a single corrosion feature. Finally, a decision has to be made on whether adjacent defect clusters will interact or not. Remaining strength predictions of the corroded pipeline will be very sensitive to the interaction criterion used and the method.
To date, most of the Pipeline Integrity and ILI software, work on corrosion assessment on studying isolated defects, primarily of similar depths. The failure pressure of an interacting defect will be lower than that for an isolated defect because it will interact with neighbouring defects. Both American Society of Mechanical Engineers (ASME) B31G and RSTRENG do not provide guidance for grouping and assessing metal loss defects that may interact. Some guidance is given in BS 7910 and DNVGL RP-F101 and, indeed, some pipeline operators have developed their own criterion for grouping defects. In general, existing guidance is based on limited empirical or semi-empirical derived methods that still require on judgment from the analyst.
This process has recognized that a robust method for grouping and assessing metal loss defects that may interact is required by a pipeline integrity engineer. According to a non-limiting embodiment, there is a sub-module in the software which enables a user to select interaction criteria (clustering rules) utilizing different dimension rules and also even material property to apply clustering in 2 different levels and to apply immediate and future integrity assessment based on new grouped sizes (New length, width and depth).
There is a unique option in this sub-module that enables a pipeline integrity engineer to increase sensitivity of clustering (select more conservative rule and level) in High Consequence Areas (HCA) and also in Unusual Sensitive Areas (USA).
Not only the clustering rule to be selected by the pipeline software user is an option for pipeline integrity engineer, but also selection of with and without applying Tolerances and also different standards (Original ASME B31G, Modified B31G, Shell92, DNVGL RP F101, Part B and DNVGL RP F101 Part A with Axial loading) are available options to be selected. Next to all, a user can filter specific location of pipeline or specific orientation for detail studies.
Sub-Module ILI Analytical Study
This step specifies the requirements and a detailed method statement for analytical reports in the ILI suite. It covers the basic analytical reports for ILI reports such as distribution plots, high level analysis, distribution of orientation for different category of defects, etc. all based on a standard ILI platform.
An ILI suite for pipelines may be very comprehensive, interactive client software that provides access to the Inspection Data, database information and complete details of the inspection.
This step may provide thorough functionality to manage and maintain the pipeline facility and to generate any required reports, charts or graphs regardless of ILI service provider and any brand.
An ILI suite for pipelines may feature:
From a previous step there is an interim spreadsheet as standard platform to be translated from different ILI reports and vendor templates. After this translation (conversion), a system engine is able to start further analytical assessments for a selected data set as per this method statement.
All of these analyses will be based on standard spreadsheet (standard excel format) in CSV as a base for all types of ILI reports.
It is important to have consistent and reliable standards. The anomalies must be accurately measured in length, width and depth in ILI reports.
When evaluating anomalies, it is very important to understand the extent of the anomaly and how its interaction with adjacent anomalies is accounted for in the report. A best practice is to measure the distance from the upstream girth weld and to paint a box equivalent to the reported dimensions, including the tolerances and taking into account the interaction (of the boxes in a cluster).
The accuracy of the inspection can then be easily recognized and documented by photography. The different types of anomalies are evaluated against the appropriate standard or code for that specific type of anomaly include (but are not limited to):
ASME B31.G—Manual for Determining the Remaining Strength of Corroded Pipelines: A Supplement to ASME B 31 Code for Pressure Piping; published by ASME International,
The interaction rules to be used need to be completed in previous steps.
User device 210 includes one or more devices capable of receiving, generating, storing, processing, and/or providing information associated with platform 220. For example, user device 210 may include a computing device (e.g., a desktop computer, a laptop computer, a tablet computer, a handheld computer, a smart speaker, a server, etc.), a mobile phone (e.g., a smart phone, a radiotelephone, etc.), a wearable device (e.g., a pair of smart glasses or a smart watch), or a similar device. In some implementations, user device 210 may receive information from and/or transmit information to platform 220.
Platform 220 includes one or more devices capable of receiving, generating, storing, processing, and/or providing information. In some implementations, platform 220 may include a cloud server or a group of cloud servers. In some implementations, platform 220 may be designed to be modular such that certain software components may be swapped in or out depending on a particular need. As such, platform 220 may be easily and/or quickly reconfigured for different uses.
In some implementations, as shown, platform 220 may be hosted in cloud computing environment 222. Notably, while implementations described herein describe platform 220 as being hosted in cloud computing environment 222, in some implementations, platform 220 may not be cloud-based (i.e., may be implemented outside of a cloud computing environment) or may be partially cloud-based.
Cloud computing environment 222 includes an environment that hosts platform 220. Cloud computing environment 222 may provide computation, software, data access, storage, etc. services that do not require end-user (e.g., user device 210) knowledge of a physical location and configuration of system(s) and/or device(s) that hosts platform 220. As shown, cloud computing environment 222 may include a group of computing resources 224 (referred to collectively as “computing resources 224” and individually as “computing resource 224”).
Computing resource 224 includes one or more personal computers, a cluster of computing devices, workstation computers, server devices, or other types of computation and/or communication devices. In some implementations, computing resource 224 may host platform 220. The cloud resources may include compute instances executing in computing resource 224, storage devices provided in computing resource 224, data transfer devices provided by computing resource 224, etc. In some implementations, computing resource 224 may communicate with other computing resources 224 via wired connections, wireless connections, or a combination of wired and wireless connections.
As further shown in
Application 224-1 includes one or more software applications that may be provided to or accessed by user device 210. Application 224-1 may eliminate a need to install and execute the software applications on user device 210. For example, application 224-1 may include software associated with platform 220 and/or any other software capable of being provided via cloud computing environment 222. In some implementations, one application 224-1 may send/receive information to/from one or more other applications 224-1, via virtual machine 224-2.
Virtual machine 224-2 includes a software implementation of a machine (e.g., a computer) that executes programs like a physical machine. Virtual machine 224-2 may be either a system virtual machine or a process virtual machine, depending upon use and degree of correspondence to any real machine by virtual machine 224-2. A system virtual machine may provide a complete system platform that supports execution of a complete operating system (“OS”). A process virtual machine may execute a single program, and may support a single process. In some implementations, virtual machine 224-2 may execute on behalf of a user (e.g., user device 210), and may manage infrastructure of cloud computing environment 222, such as data management, synchronization, or long-duration data transfers.
Virtualized storage 224-3 includes one or more storage systems and/or one or more devices that use virtualization techniques within the storage systems or devices of computing resource 224. In some implementations, within the context of a storage system, types of virtualizations may include block virtualization and file virtualization. Block virtualization may refer to abstraction (or separation) of logical storage from physical storage so that the storage system may be accessed without regard to physical storage or heterogeneous structure. The separation may permit administrators of the storage system flexibility in how the administrators manage storage for end users. File virtualization may eliminate dependencies between data accessed at a file level and a location where files are physically stored. This may enable optimization of storage use, server consolidation, and/or performance of non-disruptive file migrations.
Hypervisor 224-4 may provide hardware virtualization techniques that allow multiple operating systems (e.g., “guest operating systems”) to execute concurrently on a host computer, such as computing resource 224. Hypervisor 224-4 may present a virtual operating platform to the guest operating systems, and may manage the execution of the guest operating systems. Multiple instances of a variety of operating systems may share virtualized hardware resources.
Network 230 includes one or more wired and/or wireless networks. For example, network 230 may include a cellular network (e.g., a fifth generation (5G) network, a long-term evolution (LTE) network, a third generation (3G) network, a code division multiple access (CDMA) network, etc.), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., the Public Switched Telephone Network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber optic-based network, or the like, and/or a combination of these or other types of networks.
The number and arrangement of devices and networks shown in
Bus 310 includes a component that permits communication among the components of device 300. Processor 320 may be implemented in hardware, firmware, or a combination of hardware and software. Processor 320 may be a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), or another type of processing component. In some implementations, processor 320 includes one or more processors capable of being programmed to perform a function. Memory 330 includes a random access memory (RAM), a read only memory (ROM), and/or another type of dynamic or static storage device (e.g., a flash memory, a magnetic memory, and/or an optical memory) that stores information and/or instructions for use by processor 320.
Storage component 340 stores information and/or software related to the operation and use of device 300. For example, storage component 340 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, and/or a solid state disk), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and/or another type of non-transitory computer-readable medium, along with a corresponding drive. Input component 350 includes a component that permits device 300 to receive information, such as via user input (e.g., a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, and/or a microphone). Additionally, or alternatively, input component 350 may include a sensor for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, and/or an actuator). Output component 360 includes a component that provides output information from device 300 (e.g., a display, a speaker, and/or one or more light-emitting diodes (LEDs)).
Communication interface 370 includes a transceiver-like component (e.g., a transceiver and/or a separate receiver and transmitter) that enables device 300 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. Communication interface 370 may permit device 300 to receive information from another device and/or provide information to another device. For example, communication interface 370 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi interface, a cellular network interface, or the like.
Device 300 may perform one or more processes described herein. Device 300 may perform these processes in response to processor 320 executing software instructions stored by a non-transitory computer-readable medium, such as memory 330 and/or storage component 340. A computer-readable medium is defined herein as a non-transitory memory device. A memory device includes memory space within a single physical storage device or memory space spread across multiple physical storage devices.
Software instructions may be read into memory 330 and/or storage component 340 from another computer-readable medium or from another device via communication interface 370. When executed, software instructions stored in memory 330 and/or storage component 340 may cause processor 320 to perform one or more processes described herein.
Additionally, or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein. Thus, implementations described herein are not limited to any specific combination of hardware circuitry and software.
The number and arrangement of components shown in
In non-limiting embodiments, any one of the operations or processes described herein may be implemented by or using any one of the elements illustrated in
The location of an anomaly is given with S-Log distance and S-Position as described in
The length of a metal loss anomaly is given by its projected length on the longitudinally axis of the pipe, the width of a metal loss anomaly is given by its projected length on the circumference of the pipe. The depth of a metal loss anomaly is determined by maximum wall loss (dP).
The ‘Magnetic Flux Leakage (MFL) Method’ accesses the relative depth d/t which is calculated on the basis of the tool calibration.
Both values d/t and t (calc) are independent and specified separately with concern to their accuracy.
Important consequence: For field comparison measurements it must be ensured that the reference wall thickness surrounding the anomaly is used to calculate the relative depth of the anomaly in order to apply the specified MFL depth accuracy. If this comparison will be based on the MFL calculated wall thickness the specified accuracy interval is enlarged following the law of error, i.e., the relative errors specified for the wall thickness and the relative anomaly depth must be summarized.
Sub-Module ILI Re-Run
If the ILI result is not acceptable (above steps for tool performance validation and results verification), the ILI dataset cannot be used, and it needs to be repeated.
Unless specified otherwise, the formulation for acceptable data loss for magnetic tools may be: The maximum acceptable sensor loss (primary sensors) and/or data loss is 3% and continuous loss of data from more than three adjacent sensors or 25 mm circumference (whichever is smallest) is not acceptable.
Unless specified otherwise, the formulation for acceptable data loss for UT tools may be: The maximum acceptable sensor and/or data loss is 3% and the maximum allowable signal loss due to other reasons (e.g., echo loss) is 5%, whereby continuous loss of data from more than two adjacent transducers or 25 mm circumference (whichever is smallest) is not acceptable.
ILI Data Set Validation
For all technologies, an alternative methodology can be to define data loss based on the required POD of a specific defect like:
The POD of an anomaly with minimum dimensions for a minimum percentage of the pipeline surface and pipeline length. E.g., an anomaly with L≥20 mm, W≥20 mm, d≥20% (or d≥1 mm for UT) in the pipeline may be detected with a POD≥90% for ≥97% of the pipeline surface and ≥97% of the pipeline length.
The tool operational data statement may indicate whether the tool has functioned according to specifications and may detail all locations of data loss and where the measurement specifications are not met. When the specifications are not met (e.g., due to speed excursions, sensor/data loss, etc.), the number and total length of the sections may be reported with possible changes of accuracies and certainties of the reported results. A non-limiting embodiment may assess the below ILI tool operation reports:
ILI Distribution Charts
According to a non-limiting embodiment, software may have the ability to show the columns in short text (abbreviations). According to a non-limiting embodiment, the output includes 23 very practical charts for the distribution of internal and external metal loss corrosion and other anomalies along the pipeline route and in different segments. One non-limiting embodiment showing such 23 charts is shown below in Table 3.
ILI Conversion Data Model
A standard data model for conversion according to a non-limiting embodiment is described below.
Description of Tables/Features
According to a non-limiting embodiment, each feature or table of a data model has certain required information such as the below items:
Name
According to a non-limiting embodiment, all required data in a data model has a special name. In relevant rows, each name has special required information including data type, primary condition, foreign key, and mandatory condition.
Data Types
According to a non-limiting embodiment, the Abstract Data Types package contains a number of “abstract” data types, which each contain one or more properties that relate to their named function. The abstract data types are included by reference in several of the data model classes. When physical models are generated these references are replaced by their properties. These data types are intended to make easier to extend by individual companies/implementers. Different types of data are described in Table 4 below.
Primary Key
In database design, a primary key is important because it serves as a unique identifier for a row of data in a database table. A primary key makes it convenient for a user to add, sort, modify or delete data in a database. One of the critical steps in database programming is the inclusion of a primary key to a database table. This ensures that each record in the table is distinct from other records, which eliminates the possibility of duplicate data. A primary key is composed of one or several column fields. Once a primary key is added to a table, it should remain constant and should not deviate from its purpose, which is to identify a database record.
Foreign Key
Foreign keys are structured into a database as a common component linking together two tables. A foreign key must always reference a primary key elsewhere.
The original table is called the parent table or referenced table, and the referencing table with a foreign key is called a child table. Foreign key references are stored within a child table and links up to a primary key in a separate table. The column acting as a foreign key must have a corresponding value in its linked table. This creates referential integrity.
Mandatory
Mandatory: Controls whether referential integrity is enforced. If this option is enabled, referential integrity is enforced (that is, a matching value in the table for the referenced primary key is mandatory); and if a matching value does not exist, a record cannot be created in the current table.
The relationship between an 1) instance of the order entity and 2) an instance of the customer entity is a mandatory relationship. Identifying weak entities and their associated mandatory relationships can be very important for maintaining the consistency and integrity of the database.
Comment Column
In the second tables of each feature, the column named “comment” describes each name in the previous table and provides high-level relevant information.
In Line Inspection
Table ILI Cluster
As shown below in Table 5 and Table 6, according to a non-limiting embodiment, an ILI Cluster represents a grouping of individual anomalies as identified by a particular cluster rule. Each cluster represents a location on the pipeline with a specified length and width—the ‘call box’. All anomalies contained within the ‘call box’ are summarized in the cluster record.
Table ILI Data
According to a non-limiting embodiment, as shown below in Table 7 and Table 8, the ILI Data table is used to record the data associated with an ILI inspection. Table columns include data taken during the inspection, data updated post inspection, and data calculated post inspection. Data taken during the inspection may be reclassified after additional review or simply updated with more specific information.
Table ILI Inspection
As shown below in Table 9 and Table 10, according to a non-limiting embodiment, each record represents one completed in-line inspection run and pertinent data related to the tool run. Because of the temporary or permanent configuration of the pipeline itself versus the storage of the Line/Route hierarchy, there may be one or more ILI_Inspection_Range records related to the single ILI inspection run.
One ILI Inspection record is related to one or more ILI_Inspection_Range records. Ideally, each ILI_Inspectiontool run is contained exactly within one Route. Because of temporary pipe reconfiguration or because of the method used to organize Line and child Routes within the data model, the ILI tool run may span one or more routes.
Without this relationship, the Routes would need to be modified to match the ILI run length, or the one ILI run would need to be broken into multiple ILI Inspection records, one for each route.
Table ILI Inspection Range
As shown below in Table 11 and Table 12, according to a non-limiting embodiment, each record represents one or more segments of the entire ILI tool inspection run. The ILI Run may span one or more routes but the Range does not.
Table ILI Pipe Length
As shown in Table 13 and Table 14, according to a non-limiting embodiment, a table contains information regarding the inline inspection of a pipe joint—weld to weld. This is linear event data that describes ILI inspection on a joint per joint basis.
Table ILI Range
According to a non-limiting embodiment, Table 15 and Table 16 show table records if the inspection range can be pigged by a regular or smart pig and the date of the last inspection.
Table Inspection Contact
According to a non-limiting embodiment, as shown in Table 17 and Table 18 Each record represents that name of a primary contact person from the ILI or other Inspection Company, contractor, pipeline operator, or other party involved in the pipeline inspection.
Table Inspection Interval
A non-limiting embodiment may comprise a Table Inspection Interval, as shown in Table 19 and Table 20.
The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations.
Some embodiments may relate to a system, a method, and/or a computer readable medium at any possible technical detail level of integration. Further, one or more of the above components described above may be implemented as instructions stored on a computer readable medium and executable by at least one processor (and/or may include at least one processor). The computer readable medium may include a computer-readable non-transitory storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out operations.
The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
Computer readable program code/instructions for carrying out operations may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects or operations.
These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer readable media according to various embodiments. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). The method, computer system, and computer readable medium may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the Figures. In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed concurrently or substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.
It will be apparent that systems and/or methods, described herein, may be implemented in different forms of hardware, firmware, or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and/or methods is not limiting of the implementations. Thus, the operation and behavior of the systems and/or methods were described herein without reference to specific software code—it being understood that software and hardware may be designed to implement the systems and/or methods based on the description herein.
Embodiments of the disclosure have been shown and described above, however, the embodiments of the disclosure are not limited to the aforementioned specific embodiments. It may be understood that various modifications, substitutions, and improvements can be made by those having ordinary skill in the art in the technical field to which the disclosure belongs, without departing from the spirit of the disclosure as claimed by the appended claims. It should be understood that such modifications, substitutions, and improvements shall fall within the protection scope of the disclosure, and should not to be construed independently from the technical idea or prospect of the disclosure.
This application is a continuation-in-part of U.S. patent application Ser. No. 17/942,712 filed Sep. 12, 2022, which claims priority from, PCT/IB2021/053901, filed on May 7, 2021, which claims priority from U.S. Provisional Application No. 62/989,065 filed on Mar. 13, 2020 in the U.S. Patent & Trademark Office, the disclosures of which are incorporated herein by reference in their entirety.
| Number | Date | Country | |
|---|---|---|---|
| 62989065 | Mar 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17942712 | Sep 2022 | US |
| Child | 18107817 | US |
