Wireless wellsite service management system

Abstract

An apparatus comprising a scanner positioned at a wellsite for a wellbore operation and configured to emit a wireless signal and receive an output, wherein the scanner is configured to communicate the output to a data management system. The apparatus comprises a bi-directional tag positioned on a component utilized in the wellbore operation and configured to receive the wireless signal and return the output to the scanner, wherein the output provides information of the component.

Description

TECHNICAL FIELD

[0001] The disclosure generally relates to the field of operations performed at a wellsite for a wellbore operation and more particularly to management of wellsite components.BACKGROUND

[0002] In operations performed on a wellsite (such as for wellbore operations such as hydrocarbon recovery, geothermal, carbon capture, injection, mineral extraction, etc.), components to be utilized in wellbore operations (such as being deployed in the wellbore) may need to be tracked, documented, etc. such that the wellbore operations may be performed safely and according to plan. Effective management of components on a wellsite involves the organized coordination, maintenance, and monitoring of all components necessary for drilling, completion, and production operations. Key practices include inventory tracking, ensuring equipment functionality through regular inspections, adhering to safety standards, and optimizing workflows to prevent downtime. Proper planning and documentation are essential to streamline logistics, minimize costs, and ensure components are readily available, compliant, and operational.BRIEF DESCRIPTION OF THE DRAWINGS

[0003] Implementations of the disclosure may be better understood by referencing the accompanying drawings.

[0004] FIG. 1 is an illustration depicting an example well system, according to some implementations.

[0005] FIG. 2 is a schematic depicting an example wellsite service management system, according to some implementations.

[0006] FIG. 3 is a schematic depicting an example wellsite service management system, according to some implementations.

[0007] FIG. 4 is a flowchart depicting example operations for recording components with a wellsite service management system, according to some implementations.

[0008] FIG. 5 is a flowchart depicting example operations for interrogating a component, according to some implementations.

[0009] FIG. 6 is a block diagram depicting an example computer, according to some implementations.DESCRIPTION

[0010] The description that follows includes example systems, methods, techniques, and program flows that embody aspects of the disclosure. However, it is understood that this disclosure may be practiced without these specific details. For instance, this disclosure refers to scanners positioned at various places on a wellsite. Aspects of this disclosure can also be applied to any other scanner position on a wellsite to scan a bi-directional tag as desired, whether that be when the component with the bi-directional tag arrives at the wellsite location, is being deployed in the wellbore, etc. For clarity, some well-known instruction instances, protocols, structures, and operations have been omitted.

[0011] Example implementations relate to a wellsite service management system for managing components and corresponding records on a wellsite. In conventional operations, wellsite services may be challenged with record retention for tool and component identification, tracking, inspection, redress, repair, service life, etc. Many industry standards such as API 19PT and API 19AC have dedicated sections that provide specific requirements for service centers and users of tools and components regarding these activities. Currently, this burden may be primarily a manual exercise for personnel that is prone to mistakes and lost documentation. In some implementations, a wellsite service management system may provide an innovative method to automate the previously described processes. Additionally, the wellsite service management system may enable unique controls on the tools and components providing greater efficiency, safety, security, and quality control.

[0012] In some implementations a wellsite service management system may include an automatic identification system comprising one or more scanners and one or more bidirectional tags. The scanner may include a handheld scanner, a pass-through scanner, or a scanner integrated into equipment at the wellsite. For example, a pass-through scanner may be a pass-through scan that an assembly of tools and / or components transverses. As another example, a scanner may be integrated into a lubricator, wellhead, etc. such that the scanner may scan an assembly of tools / components as they are deployed into and / or removed from a wellbore. As another example, a scanner may be integrated into and / or positioned in a vehicle such that components may be scanned when the components arrive on the wellsite. A scanner on the wellsite may be configured to emit a wireless signal, such as radio frequency signals. The wireless technologies for the scanner may be based on Radio Frequency Identification (RFID), WiFi, Bluetooth, etc. In some implementations, one or more components on the wellsite may include a bi-directional tag configured to be interrogated by the signal emitted by the scanner. The bi-directional tag may be positioned on a component that may be utilized in wellbore operations on a wellsite, such as a perforating gun, explosive articles, tubular component, packer, liner hanger, pump, gas lift mandrel, drill bit, logging tool, etc. The bi-directional tag may not have to be visible. For example, the bi-directional tag may be positioned on an inner wall, chamber, etc. of a component, in a side pocket of a component, or any other suitable position. In some implementations, the bi-directional tag may be an RFID tag, such as passive RFID tag. The bi-directional tag may be configured to receive the signal generated by the scanner, and return an output to the scanner. The output may provide component information such as component type, component identification number, armed status, whether the component is a consumable or reusable item, intended well name, intended location, intended date / time of use, intended user, component specifications, cycle count, maintenance history and schedule, etc.

[0013] In some implementations, the scanner may communicate the output to a data management system for processing. The information obtained and processed by the data management system may cross-reference the information with the design of service, inventory databases, maintenance records, authorized-user verification, wellbore operation data, etc. to update one or more records, provide confirmation and alerts for the operation, etc. For example, the data management system may process the information to confirm all items meet the design of the service requirement, record the information in a database to update the wellbore operation history, etc. If a component is a consumable item, the corresponding information may integrate with inventory and chain-of-custody records for components such as explosives that may be required to be tracked. If a component is a reusable item, the corresponding information may provide current count cycles, maintenance schedule and history, etc. The information obtained and processed may be critical for post job analysis and improving design of service. For example, the sequence of components in an assembly, a components cycle count, maintenance history, etc. may all be utilized in analyzing wellbore operation performance and adjusting future wellbore operations, updating maintenance programs, etc.

[0014] In some implementations, when a bi-directional tag is interrogated by the signal from a scanner, the bi-directional tag may be configured to generate a responding signal that may provide an enabling or disabling actuation to an electronic device such as a switch, shunt, etc. that is incorporated into a component, such as an explosive device or an energetic device. For example, the electronic device may be incorporated into a perforating gun. The bi-directional tag may provide a signal to arm or disarm the perforating gun as the bi-directional tag is interrogated by the scanner signal. This may allow for regulatory-controlled components (such as explosives) to only be used at the intended location and time, and by an authorized user. In some implementations, if the output from the bi-directional tag does not provide the electronic device with the correct location and / or time (such as location coordinates, wellsite name, company name, wellbore operation date, authorized user, etc.), then the electronic device may be configured to disable the component due to the component being utilized incorrectly.

[0015] The wellsite service management system described herein may provide users with an automated process for component tracking at a wellsite, tracking maintenance and run history, updating wellbore operation records, verification of chain-of-custody for regulated components (such as explosives and radioactive material), etc. that may increase efficiencies by eliminating manual operations and record keeping. The wellsite service management system may provide value to customers with digital records and / or data, and allow remote access to data. Safety and security at the wellsite, and even beyond the wellsite, may be improved with the ability to arm / disarm explosive components by authorized location, date, time, defined user(s), etc., with lock-out of a component if not verified.Example System

[0016] FIG. 1 is an illustration depicting an example well system, according to some implementations. In particular, FIG. 1 is a schematic of a well system 100 that includes a wellbore 102 in a subsurface formation 101. The wellbore 102 includes casing and a number of perforations 190A-190H being made in the casing 106 at different depths to allow reservoir fluids (i.e., oil, water, and gas) from the subsurface formation 101 to flow into the wellbore 102. During hydraulic fracturing operations of the wellbores 102, fracturing fluid, with or without sand, may be pumped into the subsurface formation 101, via the perforations 190A-190H, to generate fractures 150A-150H in the subsurface formation such that reservoir fluid may flow into the wellbore 102.

[0017] The perforations 190A-190H may be formed via a perforating gun 180. Shaped charges in the perforating gun 180 may be detonated to create the perforations 190A-190H. The perorating gun 180 may be deployed into the wellbore 102 on a wireline 119 via a wireline truck 115. In some implementations, the perforating gun 180 may be deployed via other methods such as coiled tubing, jointed tubing, etc.

[0018] In some implementations, the wellbore 102 may be hydraulically fractured in stages. For example, a first stage may include hydraulically fracturing the perforations 190G, 190H to generate fractures 150G, 150H, respectively. After the hydraulic fracturing operations for the first stage are complete, a frac plug 130 may be positioned in the casing 106 above the first stage (i.e., at a lesser depth in the wellbore than perforations 190G, 190H). The frac plug 130 may be positioned in the wellbore 102 via any suitable setting method such as wireline 119. Similar operations may be repeated for each subsequent stage (i.e., setting frac plug 132 and frac plug 134 and hydraulically fracturing the next subsequent stage) until hydraulic fracturing operations for the wellbore 102 are complete.

[0019] In some implementations, bi-directional tags may be positioned on components utilized in the wellbore operations such as the perforating gun 180, frac plugs 130-134, etc. A scanner 120 may be configured to emit a signal to interrogate the bi-directional tags, which may in turn receive the signal and return an output to provide information about the respective component. The scanner 120 is shown integrated into a lubricator 114 to scan components as they are deployed into and / or removed from the wellbore 102, such as the perforating gun 180. In some implementations, the perforating gun 180 may be disarmed when on the surface 111, and may be armed when scanned by the scanner 120 prior to being deployed into the wellbore 102. For example, the bi-directional tag may provide a responding signal to an electronic device on the perforating gun 180 when the bi-directional tag receives the signal from the scanner 120. If the perforating gun 180 is the correct tool (i.e., the perforating gun information such as intended well, intended location coordinates, intended time / date, user, etc. matches the corresponding wellbore operation information), then the electronic device may arm the perforating gun 180 such that it may be operational when deployed in the wellbore 102 to create perforations. If the perforating gun 180 is the incorrect tool (aforementioned perforating gun information does not match corresponding wellbore operation information), then the electronic device may keep the perforating gun 180 disarmed and generate an alert for the user.

[0020] In some implementations, the scanner 120 may be positioned and / or integrated into any other suitable position on the surface such as in the wireline truck 115, as a standalone pass-through scanner, a handheld scanner, etc. Handheld devices may be lower power (i.e., up to 5 Watts) such that they may be utilized at a close distance to a bi-directional tag (i.e., up to 12 inches). Larger scanners, such as the scanner 120 or a scanner integrated into the wireline truck 115 may be higher powered to scan bi-directional tags at a further distance, such as greater than 1 foot, 50 feet, 300 feet, etc. For example, a scanner 120 may have power sufficient to scan bi-directional tags as the component arrives on the wellsite location. In this instance, the scanner power and frequency attributes may be designed such that they may transmit signals which are compatible with radio-frequency safety thresholds for the various explosive articles.

[0021] The wireline truck 115 can include a computer 170. In some implementations, the computer 170 can be local or remote to the wellsite. A processor of the computer 170 may include a data management system to perform operations, such as receiving output from the scanner, processing the output, and generate alarms, reports, etc. based on the processed output. For example, the data management system may cross-reference an assembly of components with the designed assembly. If the sequence of the assembly, one or more components within the assembly, etc. does not match the designed assembly, then the data management system may generate an alarm. An example of the computer 170 is depicted in FIG. 6, which is further described below.Example Wellsite Service Management Systems

[0022] Example configurations of a wellsite service management system are now described. The perforating systems are described in reference to the scanner 120 and computer 170 of FIG. 1.

[0023] FIG. 2 is a schematic depicting an example wellsite service management system, according to some implementations. FIG. 2 includes a wellsite service management system 200 comprising a scanner 222 and a plurality of bi-directional tags 210-216 positioned on a plurality of components 202-208, respectively. In the example schematic shown in FIG. 2, a scanning device comprising a scanner 222 is integrated into tubular 220 (such as a lubricator, wellhead, or any other suitable piece of equipment on a wellsite in which components may pass through). The scanner 222 may emit a wireless signal (such as a radio-frequency signal). The wireless signal may be at any suitable frequency. For instance, if the scanner was a handheld signal with a power of 5 Watts, the handheld scanner may emit a signal at approximately 900 megahertz (MHz), 2.4 gigahertz (GHz), 5 GHz, etc.

[0024] The plurality of components 202-208 may be assembled and passed through the tubular 220. For example, the components 202-208 may be a tool string comprising components that make up a bottom hole assembly during drilling and / or drill out operations, a perforating gun assembly, an electric submersible pump (ESP) assembly, a logging assembly, etc. As each component 202-208 passes through the tubular 220, each respective bi-directional tag may be interrogated by the signal emitted by the scanner 222. Each bi-directional tag (i.e., bi-directional antennas) may receive the signal and in return, generate an output that may be received by the scanner 222. The bi-directional tags and scanner may be an RFID system, where each bi-directional tag 210-216 does not have their own power source (e.g., battery) and the scanner 222 may be configured with an RFID reader. The scanner 222 may emit radio frequency signals that may provide energy to power the bi-directional tags 210-216 and enable communication between the bi-directional tags 210-216 and the RFID reader of the scanner 222. Any suitable RFID tag and reader may be utilized to scan and obtain data from each component 202-208. The bi-directional tag may be configured to generate output comprising information about the respective component, as described above. The scanner 222 may communicate the output to a data management system for processing. The data management system may be located within the scanner or remote to the scanner, such as in the computer 170 of FIG. 1.

[0025] FIG. 3 is a schematic depicting an example wellsite service management system, according to some implementations. FIG. 3 includes a wellsite service management system 300 comprising a scanner 302 and a detonator 306 with a bi-directional tag 308 positioned on the detonator. Although FIG. 3 depicts the scanner 302 as a handheld scanner, the scanner 302 may be any other suitable scanner as described above. The detonator 306 may be positioned on a perforating gun and ballistically coupled to one or more shape charges on the perforating gun such that the detonator 306 may initiate the activation of the shape charges. The scanner 302 may emit a radio frequency signal 304 to interrogate the bi-directional tag 308 positioned on the detonator 306. The bi-directional tag 308 may be an RFID tag, such that when the RFID tag receives the radio frequency signal 304, the RFID tag may generate an output. The scanner 302 may include an RFID reader to receive the output from the RFID tag. The output may then be communicated to a data management system for processing.

[0026] In some implementations, the output from the RFID tag (the bi-directional tag 308) may enable and / or disable the detonator 306 via an electronic device such as a switch or a shunt. For example, the detonator 306, positioned within a perforating gun comprising one or more shape charges, may be initially disabled when the perforating gun arrives on a wellsite. When scanned by the scanner 302, the bi-directional tag 308 may generate an output as mentioned above. If the information provided by the bi-directional tag 308 does not match wellbore operation records, then the detonator 306 may remain disabled. Alternatively, the detonator 306 may be enabled, via the switch, and the perforating gun may be ready for activation when initiated. For example, if the component name, serial number, assigned well name, company name, authorized user, date, time, component design, etc. provided in the information within the output from the bi-directional tag 308 does not correspond to wellbore operation information (such as the perforating gun is at the incorrect wellsite, has the incorrect perforation pattern design, etc.), then the detonator may be disabled. In some implementations, if the component information does not correspond to the wellbore operation information, then the data management system may generate an alert indicating the issue. Alternatively, the data management system may generate an alert that the component information does correspond to the wellbore operation information, and the detonator 306 (and perforating gun) is the correct component, the perforating gun is enabled, etc.Example Operations

[0027] Examples operations are now described.

[0028] FIG. 4 is a flowchart depicting example operations for recording components with a wellsite service management system, according to some implementations. FIG. 4 depicts a flowchart 400 of operations to scan a bi-directional tag positioned on a component on a wellsite and process the output via a data management system. The operations of flowchart 400 are described in reference to the wellsite service management system described in FIGS. 2-3. Additionally, the operations of the flowchart 400 are described in reference to the processor of the computer 170 described in FIG. 1.

[0029] At block 402, the scanner positioned at a wellsite for a wellbore operation, may emit a wireless signal. In some implementations, the processor of the computer 170 may provide instructions to the scanner to generate the wireless signal. As previously described, the signal may be at any suitable radio frequency or range of radio frequencies. The frequency range may be suitable such that a bi-directional tag may be interrogated, but the frequency does not effect, activate, etc. any other components on the wellsite, such as the detonator of a perforating gun. The scanner may be appropriately powered to scan components at a desired distance. For example, the power and distance may be suitable such that a bi-directional tag may be interrogated, but the power and distance does not effect, activate, etc. any other components on the wellsite, such as the detonator of a perforating gun. As previously described, the scanner may be positioned at any suitable location on the wellsite, provided the power, distance, and frequency attributes are consistent with safe wellsite operations.

[0030] At block 404, a bi-directional tag positioned on a component utilized in a wellbore operation may receive the wireless signal from the scanner. The bi-directional tag may be positioned at any suitable location on a component, and may or may not be visible. For example, the bi-directional tag may be positioned internally within the component, in an enclosed chamber on the interior or exterior of the component, on the external face of the component, etc. In some implementations, the bi-directional tag may be a bi-directional antenna (i.e., does not have its own power source such as a battery). Accordingly, when the bi-directional antenna receives the signal, the antenna may convert the signal to electromagnetic energy. This energy may power the bi-directional tag's internal chip, which then generates an output with the tag's programmed information (i.e., the component information). In some implementations, the bi-directional tag may be an optical bar code. For example, when the bi-directional tag may need to be visible (for instance, due to location limitations on the component), an optical bar code may be utilized.

[0031] At block 406, the scanner may receive the output generated by the bi-directional tag comprising component information. The component information may include any suitable information for the corresponding component for records such as wellbore operation history, assembly design, inventory, maintenance, enablement / disablement commands, etc. In some implementations, the scanner may be configured with an output reader, such as an RFID reader. The scanner may communicate the information to a data management system.

[0032] At block 408, the processor of the computer 170 may process, via a data management system, the information of the component. Processing the information may include cross-referencing the component information with wellbore operation information, external databases, etc. Moreover, the data management system may update records such as inventory, chain-of custody-controls, etc. For example, the component information may indicate if the component is consumable or reusable. If consumable, the data management system may cross-reference and / or update / modify records such as inventory records and chain-of-custody control records for materials such as explosives and radioactive materials that may be tracked to ensure legal possession and use. If reusable, the data management system may provide a user with current cycle counts, maintenance history and schedule, update cycle counts, etc. In some implementations, the data management system may update wellbore operation records, such as daily reports, assemblies ran in the wellbore, etc. and other records such as cycle counts, inventory databases, etc.

[0033] In some implementations, the data management system may generate alerts based on the component information. For example, if a plurality of components are coupled together to form an assembly, the data management system may cross-reference the assembled component sequence with the designed component sequence. If the assembled component sequence is incorrect with respect to the designed component sequence, the data management system may generate an alarm indicating an incorrect assembly sequence. As another example, if a chain-of-custody for a sensitive component (such as an explosive or radioactive material) is incorrect, the data management system may generate an alarm indicating incorrect custody. Additionally, in some implementations, the data management system may communicate commands to electronics on the component to disable, lock out, etc. the component for safety or security precautions.

[0034] FIG. 5 is a flowchart depicting example operations for interrogating a component, according to some implementations. FIG. 5 depicts a flowchart 500 of operations to scan a bi-directional tag positioned on an explosive device / article on a wellsite and actions to enable or disable the explosive device. The operations of flowchart 500 are described in reference to the wellsite service management system described in FIGS. 2-3 and the operations described in the flowchart 400 of FIG. 4. Additionally, the operations of the flowchart 500 are described in reference to the processor of the computer 170 described in FIG. 1. The operations described in the flowchart 500 may be independently or dependently applied. The steps and conditions described may be applied as enabling or as disabling, arming or disarming processes based on the bi-directional tag scanned.

[0035] At block 502, a component configured with a bi-directional tag may be scanned to obtain component information. The operations of scanning and obtaining component information may be similar to the operations described in flowchart 400FIG. 4. For example, a scanner may emit a wireless signal to interrogate a bi-directional tag on a component. The bi-directional tag may generate an output comprising the component information in response to the interrogation. In some implementations, the processor of the computer 170 may process the output to obtain the component information.

[0036] In some implementations, the component may be an explosive device / article such as a perforating gun. Accordingly, the component information may include information corresponding to the authorized use of the component such as location, date, time, defined user(s), etc. For example, the aforementioned information may prevent the explosive device / article from being used at the incorrect location, prematurely detonating, etc.

[0037] At block 504, the processor of the computer 170 may compare the component information to a Design of Service (DOS). The DOS may be the information planned / intended for a job site, well, etc. For example, the designed date, time, location, authorized user, component type and identification number, etc. may be within the DOS. The component information described in block 502 may be compared with the DOS to determine if the component information meets the requirements of the DOS.

[0038] At block 506, the processor of the computer 170 may determine if the component information meets the requirements of the Design of Service. The DOS may include tools / components to be used, component types and serial numbers, location of the well and / or job, specific stage / run in a particular well, etc. The requirements may include an exact match (e.g., well name, well identifier number, component identification number, date, authorized user, etc. within the component information must exactly match aforementioned information with the DOS), or an approximate match (e.g., difference in letter capitalization, slight variation in well name, only first 10 numbers of a well American Petroleum Institute (API) number match, first name and last name of authorized user are switched, etc.), etc. In some implementations, to meet the requirements at least a portion or all of the component information may match the DOS. Any suitable requirements for the comparison of text, numbers, dates, etc. or any combination thereof may be utilized to determine if the component information meets the requirements of the DOS. If the requirements are met, then operations proceed to block 510. Otherwise, operations proceed to block 508.

[0039] At block 508, the processor of the computer 170 may disable the component and generate an alarm. In some implementations, the component may be disabled by locking the safety of the component. For example, a switch in the component may be disabled (such as the safety of the detonator may be locked) to prevent the component from being used. The processor of the computer 170 may communicate a signal to the component to disable the component.

[0040] If a component is disabled due to the component information failing to meet the requirements of the DOS, an alarm may be generated indicating the failure and disablement of the component. The alarm may provide details such as which component information did not match with the DOS and / or if the explosive user-in-charge is not confirmed in the DOS. In some implementations, the alarm may be communicated to a user for review. The alarm may be required to be reviewed for approval (i.e., management of change (MOC)) before proceeding with the component. For example, the alarm may be disabled and the safety unlocked once the alarm is reviewed via the MOC, and operations with the component may proceed.

[0041] At block 510, the processor of the computer 170 may enable the component. The component may be enabled when the component information meets the requirements of the DOS and the explosive user-in-charge is confirmed. Accordingly, component may be enabled via the switch in the component changing to ready (e.g., unlock the safety), the signal communicated to an initiation device within the component (such as a firing head) may allow the component to arm, etc.Example Computer

[0042] FIG. 6 is a block diagram depicting an example computer, according to some implementations. FIG. 6 depicts a computer 600 for scanning components and processing component information provided by a bi-directional tag positioned on the respective component. The computer 600 includes a processor 601 (possibly including multiple processors, multiple cores, multiple nodes, and / or implementing multi-threading, etc.). The computer 600 includes memory 607. The memory 607 may be system memory or any one or more of the above already described possible realizations of machine-readable media. The computer 600 also includes a bus 603 and a network interface 605. The computer 600 can communicate via transmissions to and / or from remote devices via the network interface 605 in accordance with a network protocol corresponding to the type of network interface, whether wired or wireless and depending upon the carrying medium. In addition, a communication or transmission can involve other layers of a communication protocol and or communication protocol suites (e.g., transmission control protocol, Internet Protocol, user datagram protocol, virtual private network protocols, etc.).

[0043] The computer 600 also includes a processor 611 and a controller 615 which may perform the operations described herein. For example, the processor 611 may store and process component information obtained from one or more sensors positioned in a perforating system. The controller 615 may execute one or more action, such as updating one or more records, generating one or more reports, generating one or more alarms, enabling / disabling one or more components, etc. The processor 611 and the controller 615 can be in communication. Any one of the previously described functionalities may be partially (or entirely) implemented in hardware and / or on the processor 601. For example, the functionality may be implemented with an application specific integrated circuit, in logic implemented in the processor 601, in a co-processor on a peripheral device or card, etc. Further, realizations may include fewer or additional components not illustrated in FIG. 6 (e.g., video cards, audio cards, additional network interfaces, peripheral devices, etc.). The processor 601 and the network interface 605 are coupled to the bus 603. Although illustrated as being coupled to the bus 603, the memory 607 may be coupled to the processor 601.

[0044] While the aspects of the disclosure are described with reference to various implementations and exploitations, it will be understood that these aspects are illustrative and that the scope of the claims is not limited to them. In general, techniques for interrogating a bi-directional tag with a scanner to obtain component information and performing one or more actions based on the component information described herein may be implemented with facilities consistent with any hardware system or hardware systems. Many variations, modifications, additions, and improvements are possible.

[0045] Plural instances may be provided for components, operations or structures described herein as a single instance. Finally, boundaries between various components, operations and data stores are somewhat arbitrary, and particular operations are illustrated in the context of specific illustrative configurations. Other allocations of functionality are envisioned and may fall within the scope of the disclosure. In general, structures and functionality presented as separate components in the example configurations may be implemented as a combined structure or component. Similarly, structures and functionality presented as a single component may be implemented as separate components. These and other variations, modifications, additions, and improvements may fall within the scope of the disclosure.

[0046] Various modifications to the implementations described in this disclosure may be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other implementations without departing from the spirit or scope of this disclosure. Thus, the claims are not intended to be limited to the implementations shown herein but are to be accorded the widest scope consistent with this disclosure, the principles and the novel features disclosed herein.

[0047] Certain features that are described in this specification in the context of separate implementations also may be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation also may be implemented in multiple implementations separately or in any suitable subcombination. Moreover, although features may be described as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination may in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

[0048] Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Further, the drawings may schematically depict one more example process in the form of a flow diagram. However, some operations may be omitted and / or other operations that are not depicted may be incorporated in the example processes that are schematically illustrated. For example, one or more additional operations may be performed before, after, simultaneously, or between any of the illustrated operations. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the implementations described should not be understood as requiring such separation in all implementations, and the described program components and systems may generally be integrated together in a single software product or packaged into multiple software products. Additionally, other implementations are within the scope of the following claims. In some cases, the actions recited in the claims may be performed in a different order and still achieve desirable results.

[0049] Unless otherwise specified, use of the terms “up,”“upper,”“upward,”“uphole,”“upstream,” or other like terms shall be construed as generally away from the bottom, terminal end of a well; likewise, use of the terms “down,”“lower,”“downward,”“downhole,” or other like terms shall be construed as generally toward the bottom, terminal end of the well, regardless of the wellbore orientation. Use of any one or more of the foregoing terms shall not be construed as denoting positions along a perfectly vertical axis. In some instances, a part near the end of the well can be horizontal or even slightly directed upwards. Unless otherwise specified, use of the term “subsurface formation” shall be construed as encompassing both areas below exposed earth and areas below earth covered by water such as ocean or fresh water.Example Implementations

[0050] Implementation #1: An apparatus comprising: a scanner positioned at a wellsite for a wellbore operation and configured to emit a wireless signal and receive an output, wherein the scanner is configured to communicate the output to a data management system; and a bi-directional tag positioned on a component utilized in the wellbore operation and configured to receive the wireless signal and return the output to the scanner, wherein the output provides information of the component.

[0051] Implementation #2: The apparatus of Implementation #1, wherein the wireless signal includes a radio-frequency identification signal, a Wi-Fi signal, or a Bluetooth signal.

[0052] Implementation #3: The apparatus of Implementation #1 or #2, wherein the scanner is a handheld scanner, a pass-through scanner, or integrated into equipment at the wellsite including a lubricator, a wellhead, or a data van.

[0053] Implementation #4: The apparatus of any one or more of Implementation #13, wherein the information includes component type, component identification number, enabled status, disabled status, consumable or reusable designation, or any combination thereof.

[0054] Implementation #5: The apparatus of any one or more of Implementation #1-4, wherein the data management system is configured to update at least one of the wellbore operation data, the one or more inventory databases, and cycle count with the information of the component.

[0055] Implementation #6: The apparatus of Implementation #5, wherein the data management system is configured to update the wellbore operation data, cycle count, with the information of the component.

[0056] Implementation #7: The apparatus of any one or more of Implementation #16, wherein the output is configured to provide an enabling or disabling actuation of an electronic device that is communicatively coupled with the component.

[0057] Implementation #8: The apparatus of Implementation #7, wherein the component is an explosive device, and wherein the output is configured to enable or disable the explosive device via the electronic device.

[0058] Implementation #9: The apparatus of Implementation #8, wherein the information to enable or disable the explosive device includes identification requirements of authorized location, date, time, one or more defined users, or any combination thereof.

[0059] Implementation #10: A system comprising: a scanner positioned at a wellsite for a wellbore operation and configured to emit a wireless signal and receive an output; a bi-directional tag positioned on a component utilized in the wellbore operation and configured to receive the wireless signal and return the output to the scanner; a processor; and a computer-readable medium having instructions stored thereon that are executable by the processor, the instructions comprising, instructions to obtain, via a data management system, the output from the scanner, wherein the output provides information of the component; and instructions to perform, via the data management system, one or more actions based on the information of the component.

[0060] Implementation #11: The system of Implementation #10, wherein the one or more actions includes updating one or more records, generating one or more alarms, enabling the component, disabling the component, or any combination thereof.

[0061] Implementation #12: The system of Implementation #10 or #11, wherein the scanner is a handheld scanner, a pass-through scanner, or integrated into equipment at the wellsite including a lubricator, a wellhead, or a data van.

[0062] Implementation #13: The system of any one or more of Implementation #10-12, wherein the information includes component type, component identification number, armed status, consumable or reusable designation, or any combination thereof.

[0063] Implementation #14: The system of any one or more of Implementation #10-13, wherein the output is configured to provide an enabling or disabling actuation of an electronic device that is communicatively coupled with the component.

[0064] Implementation #15: The system of any one or more of Implementation #10-14, wherein the component includes at least one of a perforating gun, an explosive article, an explosive device, a tubular component, a packer, a liner hanger, a pump, a gas lift mandrel, a drill bit, and a logging tool.

[0065] Implementation #16: A method comprising: emitting, via a scanner positioned at a wellsite for a wellbore operation, a wireless signal; receiving, via a bi-directional tag positioned on a component utilized in the wellbore operation, the wireless signal, wherein the bi-directional tag returns an output based on the wireless signal; receiving, via the scanner, the output, wherein the output provides information of the component; and communicating the output to a data management system.

[0066] Implementation #17: The method of Implementation #16 further comprising; generating, via the data management system, one or more alarms based on the output of the component.

[0067] Implementation #18: The method of Implementation #16 or #17 further comprising; cross-referencing, via the data management system, the output of the component with at least one of a design of service, an inventory database, and a maintenance record.

[0068] Implementation #19: The method of Implementation #18 further comprising:

[0069] cross-referencing a sequence of a plurality of components with the design of the service;

[0070] and confirming the design of the service based on the output of the respective components of the plurality of components.

[0071] Implementation #20: The method of any one or more of Implementation #16-19 further comprising; actuating an electronic device that is communicatively coupled with the component based on the output, wherein the electronic device includes a switch or a shunt.

[0072] Use of the phrase “at least one of” preceding a list with the conjunction “and” should not be treated as an exclusive list and should not be construed as a list of categories with one item from each category, unless specifically stated otherwise. A clause that recites “at least one of A, B, and C” can be infringed with only one of the listed items, multiple of the listed items, and one or more of the items in the list and another item not listed.

[0073] As used herein, the term “or” is inclusive unless otherwise explicitly noted. Thus, the phrase “at least one of A, B, or C” is satisfied by any element from the set {A, B, C} or any combination thereof, including multiples of any element.

Claims

1. A system comprising:a scanner positioned at a wellsite for a wellbore operation and configured to emit a wireless signal and receive an output, wherein the scanner is configured to communicate the output to a data management system; anda bi-directional tag positioned on a component utilized in the wellbore operation and configured to receive the wireless signal and return the output to the scanner in each of a plurality of operational states of the component including a deployed state in the wellbore and a non-deployed state at the wellsite, wherein the output provides information of the component, wherein the output is used by the data management system to provide an enabling or disabling actuation of an electronic device that is communicatively coupled with the component, the enabling or disabling actuation being initiated by the data management system external to the component.

2. The system of claim 1, wherein the wireless signal includes a radio-frequency identification signal, a Wi-Fi signal, or a Bluetooth signal.

3. The system of claim 1, wherein the scanner is a handheld scanner, a pass-through scanner, or integrated into equipment at the wellsite including a lubricator, a wellhead, or a data van.

4. The system of claim 1, wherein the information includes component type, component identification number, enabled status, disabled status, consumable or reusable designation, or any combination thereof.

5. The system of claim 1, wherein the data management system is configured to cross-reference the information with at least one of a design of service, one or more inventory databases, maintenance records, and wellbore operation data.

6. The system of claim 5, wherein the data management system is configured to update at least one of the wellbore operation data, the one or more inventory databases, and cycle count with the information of the component.

7. (canceled)8. The system of claim 1, wherein the component is an explosive device, and wherein the output is used to enable or disable the explosive device via the electronic device.

9. The system of claim 8, wherein the output to enable or disable the explosive device includes identification requirements of authorized location, date, time, one or more defined users, or any combination thereof.

10. A system comprising:a scanner positioned at a wellsite for a wellbore operation and configured to emit a wireless signal and receive an output;a bi-directional tag positioned on a component utilized in the wellbore operation and configured to receive the wireless signal and return the output to the scanner, wherein the component is configured to receive the wireless signal and return the output in each of a plurality of operational states of the component including a deployed state in the wellbore and a non-deployed state at the wellsite;a processor; anda computer-readable medium having instructions stored thereon that are executable by the processor, the instructions comprising,instructions to obtain, via a data management system that is external to the component, the output from the scanner, wherein the output provides information of the component; andinstructions to perform, via the data management system, one or more actions based on the information of the component, the actions including providing an enabling or disabling actuation of an electronic device that is communicatively coupled with the component.

11. The system of claim 10, wherein the one or more actions includes updating one or more records, generating one or more alarms, enabling the component, disabling the component, or any combination thereof.

12. The system of claim 10, wherein the scanner is a handheld scanner, a pass-through scanner, or integrated into equipment at the wellsite including a lubricator, a wellhead, or a data van.

13. The system of claim 10, wherein the information includes component type, component identification number, armed status, consumable or reusable designation, or any combination thereof.

14. (canceled)15. The system of claim 10, wherein the component includes at least one of a perforating gun, an explosive article, an explosive device, a tubular component, a packer, a liner hanger, a pump, a gas lift mandrel, a drill bit, and a logging tool.

16. A method comprising:emitting, via a scanner positioned at a wellsite for a wellbore operation, a wireless signal;receiving, via a bi-directional tag positioned on a component utilized in the wellbore operation, the wireless signal, wherein the bi-directional tag returns an output based on the wireless signal, and wherein the bi-directional tag returns an output based on the wireless signal when the component is in each of a plurality of operational states including a deployed state in the wellbore and a non-deployed state at the wellsite;receiving, via the scanner, the output, wherein the output provides information of the component;communicating the output to a data management system that is external to the component; andinitiating, via the data management system, an enabling or disabling actuation of an electronic device communicatively coupled with the component based on the information of the component.

17. The method of claim 16 further comprising;generating, via the data management system, one or more alarms based on the output of the bi-directional tag.

18. The method of claim 16 further comprising;cross-referencing, via the data management system, the output of the bi-directional tag with at least one of a design of service, an inventory database, and a maintenance record.

19. The method of claim 18 further comprising:cross-referencing a sequence of a plurality of components with the design of the service; andconfirming the design of the service based on an output of the respective bi-directional tag of the plurality of components.

20. The method of claim 16, wherein the electronic device includes a switch or a shunt.

Images