WO2016053331A1 - Transfert basé sur des images de données d'emplacement de puits entre des dispositifs dans un champ de pétrole - Google Patents

Transfert basé sur des images de données d'emplacement de puits entre des dispositifs dans un champ de pétrole Download PDF

Info

Publication number
WO2016053331A1
WO2016053331A1 PCT/US2014/058642 US2014058642W WO2016053331A1 WO 2016053331 A1 WO2016053331 A1 WO 2016053331A1 US 2014058642 W US2014058642 W US 2014058642W WO 2016053331 A1 WO2016053331 A1 WO 2016053331A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
format
wellsite
computing device
image
Prior art date
Application number
PCT/US2014/058642
Other languages
English (en)
Inventor
Florin M. ANGHELESCU
David CRAWSHAY
Original Assignee
Landmark Graphics Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Landmark Graphics Corporation filed Critical Landmark Graphics Corporation
Priority to US15/505,581 priority Critical patent/US10380052B2/en
Priority to PCT/US2014/058642 priority patent/WO2016053331A1/fr
Priority to CA2959310A priority patent/CA2959310C/fr
Priority to GB1703114.7A priority patent/GB2545354B/en
Priority to ARP150102873A priority patent/AR101792A1/es
Priority to FR1559181A priority patent/FR3026871B1/fr
Publication of WO2016053331A1 publication Critical patent/WO2016053331A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38—Information transfer, e.g. on bus
    • G06F13/382—Information transfer, e.g. on bus using universal interface adapter
    • G06F13/387—Information transfer, e.g. on bus using universal interface adapter for adaptation of different data processing systems to different peripheral devices, e.g. protocol converters for incompatible systems, open system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K19/00—Record carriers for use with machines and with at least a part designed to carry digital markings
    • G06K19/06—Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code
    • G06K19/06009—Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code with optically detectable marking
    • G06K19/06037—Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code with optically detectable marking multi-dimensional coding
    • E—FIXED CONSTRUCTIONS
    • E21—EARTH OR ROCK DRILLING; MINING
    • E21B—EARTH OR ROCK DRILLING; OBTAINING OIL, GAS, WATER, SOLUBLE OR MELTABLE MATERIALS OR A SLURRY OF MINERALS FROM WELLS
    • E21B44/00—Automatic control systems specially adapted for drilling operations, i.e. self-operating systems which function to carry out or modify a drilling operation without intervention of a human operator, e.g. computer-controlled drilling systems; Systems specially adapted for monitoring a plurality of drilling variables or conditions
    • E—FIXED CONSTRUCTIONS
    • E21—EARTH OR ROCK DRILLING; MINING
    • E21B—EARTH OR ROCK DRILLING; OBTAINING OIL, GAS, WATER, SOLUBLE OR MELTABLE MATERIALS OR A SLURRY OF MINERALS FROM WELLS
    • E21B47/00—Survey of boreholes or wells
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/002—Specific input/output arrangements not covered by G06F3/01 - G06F3/16
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K7/00—Methods or arrangements for sensing record carriers, e.g. for reading patterns
    • G06K7/10—Methods or arrangements for sensing record carriers, e.g. for reading patterns by electromagnetic radiation, e.g. optical sensing; by corpuscular radiation
    • G06K7/10544—Methods or arrangements for sensing record carriers, e.g. for reading patterns by electromagnetic radiation, e.g. optical sensing; by corpuscular radiation by scanning of the records by radiation in the optical part of the electromagnetic spectrum
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K7/00—Methods or arrangements for sensing record carriers, e.g. for reading patterns
    • G06K7/10—Methods or arrangements for sensing record carriers, e.g. for reading patterns by electromagnetic radiation, e.g. optical sensing; by corpuscular radiation
    • G06K7/14—Methods or arrangements for sensing record carriers, e.g. for reading patterns by electromagnetic radiation, e.g. optical sensing; by corpuscular radiation using light without selection of wavelength, e.g. sensing reflected white light
    • G06K7/1404—Methods for optical code recognition
    • G06K7/1408—Methods for optical code recognition the method being specifically adapted for the type of code
    • G06K7/1417—2D bar codes
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16Z—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS, NOT OTHERWISE PROVIDED FOR
    • G16Z99/00—Subject matter not provided for in other main groups of this subclass

Definitions

  • the present disclosure relates generally to wellsite data collection and reporting and, more specifically, to the transfer of wellsite data between computing devices in a petroleum field.
  • a modern drilling operation for the exploration and production of oil and natural gas generally involves a number of different organizations that are responsible for various aspects of the operation at a wellsite.
  • a variety of service companies and contractors may be used to provide specialized services related to the equipment that may be associated with a drilling rig at the wellsite.
  • each of these service providers may need to share data related to its activities at the wellsite with one or more of the other service providers.
  • the exchange or transfer of electronic data between different organizations in the oil and gas industry has been difficult. This difficulty has been primarily due to the use of propriety data formats and strict data access control policies, which may vary from one service company or contractor to another.
  • each service provider may use proprietary computer systems and data formats to collect and store wellsite data produced by various sources, e.g., instrumentation devices on a rig.
  • each service provider typically have limited network capabilities or only have access to other devices on a private network associated with that particular service provider.
  • some devices used in the field and at the wellsite may be completely "locked down," for example, by disabling all network capabilities and other means for transferring electronic data to other devices (e.g., access to external storage devices, such as through a serial data connection).
  • the only option for a service provider to transfer wellsite data from the device to another service provider is to produce a hard copy or printout of the wellsite data.
  • the second service provider would then have to undertake the time-consuming process of manually entering the data into the appropriate computer system of the second provider.
  • WITMSL Wellsite Information Transfer Specification Markup Language
  • FIG. 1 illustrates an exemplary petroleum field environment in which wellsite data may be transferred between various computing devices using matrix barcodes.
  • FIG. 2 illustrates an exemplary process flow for transferring wellsite data between the petroleum field devices of FIG. 1 using matrix barcodes.
  • FIG. 3 illustrates an exemplary system for transferring wellsite data between petroleum field devices using matrix barcodes.
  • FIG. 4 is a process flowchart of an exemplary method for enabling wellsite data transfer between petroleum field devices using matrix barcodes.
  • FIG. 5 is a process flowchart of another exemplary method for enabling wellsite data transfer between petroleum field devices using matrix barcodes.
  • FIG. 6 is a block diagram of an exemplary computer system in which embodiments of the present disclosure may be implemented.
  • Embodiments of the present disclosure relate to transferring wellsite data between computing devices in a petroleum field using matrix or two-dimensional (2D) barcodes. While the present disclosure is described herein with reference to illustrative embodiments for particular applications, it should be understood that embodiments are not limited thereto. Other embodiments are possible, and modifications can be made to the embodiments within the spirit and scope of the teachings herein and additional fields in which the embodiments would be of significant utility. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the relevant art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • references to "one embodiment,” “an embodiment,” “an example embodiment,” etc. indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • wellsite data is used herein to refer to the different types of data that may be produced and collected from various sources at a wellsite in a petroleum field. Such data may relate to activities performed at any of the various stages of a well's life cycle including, for example, well planning, drilling, and completion. Examples of such activities include, but are not limited to, daily operations, casing, cementing, perforations, stimulations, pipe tally, and testing of wellbore equipment. As noted above, the wellsite data produced in the field may be from a number of different sources at the wellsite.
  • Such data sources may be associated with different service providers, e.g., service companies and/or specialized contractors, that may be involved in the various operations at the wellsite including, for example, drilling, surveying, wireline testing, completions, production, oilfield planning and analysis.
  • Examples of different sources of wellsite data include, but are not limited to, sensors or other instrumentation devices on a drilling rig in addition to various types of computing devices used by service providers in the field for collecting and reporting data related to inventory tracking (e.g., pipe tally reports) and other activities performed at the wellsite (e.g., daily operations reports).
  • Each service provider may use its own proprietary computer systems, networks, and electronic data formats for representing, storing, and managing wellsite data generally.
  • FIG. 1 illustrates an exemplary petroleum field environment 100 in which wellsite data may be transferred between various devices using one or more matrix barcodes.
  • a matrix barcode includes, but is not limited to, a quick response (QR) code.
  • QR quick response
  • embodiments of the present disclosure are not intended to be limited to matrix barcodes and that the disclosed embodiments may be implemented using any type of coded image format for encoding and representing coded data for purposes of transfer between disparate or incompatible computing devices via an optical display/reader interface.
  • environment 100 includes a plurality of computing devices 110, 120, 130, 140 and 150.
  • computing devices 110, 120, 130, 140, and 150 may be used by, for example, different service providers at a wellsite for collecting and/or reporting data related to different aspects of the drilling and production operations conducted at the wellsite.
  • computing devices 110, 120, and 130 may be represent different sources of the wellsite data that may be collected and reported to computing device 140.
  • the reporting function performed by each of computing devices 110, 120, 130 may include, for example, transferring the wellsite data to computing device 140 using matrix barcodes 115, 125, and 135, respectively, and without having to use a network connection or an external memory device to enable data transfer between the respective devices, in accordance with the embodiments disclosed herein.
  • Each of computing devices 110, 120, 130, 140, and 150 may be implemented using any type of computing device having at least one processor and a memory in the form of a computer-readable storage medium for storing data and instructions that can be read and executed by the processor.
  • a computing device may also include an input/output (I/O) interface for receiving user input or commands via a user input device (e.g., a mouse, QWERTY or T9 keyboard, touch-screen, or microphone).
  • the I/O interface may also be used by each computing device to output or present information to a user via an output device.
  • the output device may be, for example, a display coupled to or integrated with the computing device for displaying a digital representation of the information being presented to the user.
  • the output device may be a printer coupled to the device for printing a physical paper copy of the presented information.
  • the presented information output via the display or printer may include one or more matrix barcodes (e.g., one or more QR codes) generated based on wellsite data to be transferred to another device, as will be described in further detail below.
  • computing device 110 may be, for example, a desktop or workstation while computing devices 120, 130, and 140 may be different types of mobile devices (e.g., smartphones, tablet device, portable digital assistant (PDA) or similar type of mobile device).
  • Computing device 150 may be, for example, a laptop computer for receiving wellsite data from computing device 140. As shown in FIG.
  • computing device 150 may be communicatively coupled to a database 160.
  • Database 160 may be, for example, a local or remote data store used for storing wellsite data collected from one or more sources at the wellsite, e.g., as reported by computing devices 110, 120, and/or 130.
  • computing devices 140 and 150 may be associated with the same service provider, e.g., an oilfield services company responsible for supervising wellsite operations.
  • devices 140 and 150 may be different devices used by the service provider at different locations in the petroleum field.
  • Device 140 may be a mobile device used by company personnel located at the wellsite while device 150 may be a laptop computer used by personnel in an office building used by the company as a centralized management facility for operations in the petroleum field.
  • database 160 may be, for example, a centralized repository for different types of wellsite data maintained by the service company and made accessible to other computing devices on the service provider's private network.
  • computing devices 110, 120, and 130 may be associated with different third-party service providers that have disparate communication networks and systems, e.g., specialized contractors that provide services and support for particular pieces of equipment used at the wellsite. Further, each service provider may use, for example, a proprietary data format that may be specific to that provider's computer systems. In an embodiment, each of computing devices 110, 120, 130, and 140 may have limited network connectivity or restricted access to devices and networks that are external to the private network of the particular service provider associated with that device. Thus, computing devices 110, 120, 130, and 140 may not be able to use a network connection for transferring or exchanging electronic data with each other or with other devices on a different service provider's network.
  • the networking capabilities and access to peripheral devices e.g., memory cards or other external data storage devices
  • peripheral devices e.g., memory cards or other external data storage devices
  • the networking capabilities and access to peripheral devices may be completely disabled or "locked down” for security reasons, thereby preventing each locked down device from establishing any type of data connection with other devices, including other devices on the same provider's network.
  • computing device 110 may be part of a data collection and reporting system associated with a drilling rig 112.
  • Drilling rig 112 may be any type of onshore or off-shore drilling rig used to drill wells in subterranean formations, e.g., for purposes of hydrocarbon exploration, production, or stimulation operations in a petroleum field.
  • Drilling rig 112 may be equipped with various instrumentation devices, e.g., down- hole sensors, for capturing data related to different parameters of the particular drilling operation.
  • Computing device 110 in this example may be communicatively coupled to drilling rig 112 or one or more instrumentation devices thereof for purposes of collecting and reporting the captured data.
  • the wellsite data produced by an instrumentation device may be in, for example, a proprietary format associated with a particular oilfield service provider or contractor responsible for operating and maintaining the particular instrumentation device.
  • the wellsite data produced by the instrumentation devices of drilling rig 112 may be collected and/or reported by computing device 110 on a periodic or per-event basis, for example, based on commands input by a user of computing device 110. In some implementations, the collection and reporting may occur in real time, e.g., as part of a real-time monitoring function performed by computing device 110.
  • the instrumentation data collected by computing device 110 may be stored to a database 114 that is communicatively coupled to device 110.
  • database 114 may be, for example, a local or remote database used to store wellsite data. However, database 114 may be accessible only to computing device 110 and other devices on the private network of the third-party service provider associated with device 110.
  • computing device 110 and/or computing device 140 may have limited or restricted networking capabilities. As such, it may not be possible for computing device 110 to transfer wellsite data to computing device 140 via a traditional network.
  • computing device 110 may generate a matrix barcode 115 for transferring the wellsite data to computing device 140.
  • Matrix barcode 115 may be generated by device 110 as a single matrix barcode (e.g., a single QR code symbol) or a matrix barcode stream including a plurality of matrix barcodes (e.g., a QR code stream including a series of QR codes).
  • matrix barcode 115 may be presented for transfer to computing device 140 via a display of computing device 110.
  • device 110 may output matrix barcode 115 via a printer coupled to device 110.
  • Matrix barcode 115 may be printed as part of, for example, a paper report related to the instrumentation data collected for drilling rig 112.
  • Matrix barcode 115 presented by device 110 may be transferred to device 140 via an image capture device, e.g., a digital camera, or a matrix barcode scanner coupled to device 140.
  • computing device 120 may represent another source of wellsite data in addition to device 110.
  • computing device 120 may be part of, for example, a mobile inventory tracking system for different types of equipment that may be used at the wellsite, e.g., for wellsite operations conducted with drilling rig 112.
  • a mobile inventory tracking system may be, for example and without limitation, a mobile pipe tally system for tracking drill pipe, casing, and tubing information as the equipment arrives at drilling rig 112 or is run into the borehole.
  • Device 120 in this example may be used by, for example, a casing-hand or well engineer to record measurements of pipe joints being unloaded from a transport vehicle or vessel as well as those being run into the hole.
  • the measurements recorded by device 120 may be stored as pipe tally data 122 in, for example, an internal memory of device 120.
  • pipe tally data 122 may be stored in an external data store or removable storage device coupled to device 120.
  • Pipe tally data 122 may then be used by device 120 to generate various pipe tally reports.
  • pipe tally data 122 or a pipe tally report generated therefrom may be converted by device 120 into one or more matrix barcodes 125, which can be transferred to device 140.
  • Matrix barcode(s) 125 may be generated using, for example, the above-described technique used by device 110 to generate matrix barcode 115.
  • computing device 130 may represent yet another source of wellsite data.
  • a user 132 may use computing device 130 to track daily activities performed at the wellsite, e.g., workover and intervention operations conducted at drilling rig 112.
  • each daily 24-hour period of activity may be divided into two 12-hour shifts.
  • User 132 in this example may be a well engineer responsible for the first 12-hour day shift while user 142 may be responsible for the second 12-hour shift.
  • user 132 may need to report the activities performed during the first 12-hour shift to user 142, e.g., as part of a daily hand-off procedure between shifts.
  • device 130 may be used to generate a matrix barcode 135, which can be used to transfer the 12-hour shift data to device 140.
  • a matrix barcode 135 can be used to transfer the 12-hour shift data to device 140.
  • the activities for both 12- hour shifts may be uploaded into a data management system for tracking daily operations conducted at the wellsite. This may involve, for example, transferring the data from device 140 to device 150, e.g., by using another matrix barcode generated by device 140 for this purpose, which can be presented on a display of device 140 and captured by an image capture device or matrix barcode scanner of device 150.
  • FIG. 2 illustrates an exemplary process flow 200 for transferring wellsite data between the petroleum field devices of FIG. 1 using matrix barcodes (e.g., matrix barcodes 115, 125, or 135).
  • matrix barcodes e.g., matrix barcodes 115, 125, or 135.
  • the transfer of wellsite data is shown in FIG. 2 as originating from computing device 110 and continuing to computing devices 140 and 150.
  • process flow 200 is not intended to be limited thereto and that the wellsite data being transferred may originate from another computing device (e.g., computing device 120 or 130 of FIG. 1) corresponding to a different data source, as described above.
  • device 110 obtains wellsite data from a source at the wellsite.
  • the source may be, for example, an instrumentation device of a drilling rig, e.g., drilling rig 112 of FIG. 1, as described above.
  • the wellsite data is generated by the data source in a proprietary format.
  • device 110 converts the wellsite data from the proprietary format to a "portable" data format.
  • a portable data format may include, for example, any platform-independent data format that is not specific to any particular computing system.
  • such a portable format may be, for example, a text-based data format conforming to an industry standard format for electronic data exchange/transfer of wellsite information.
  • WITSML Wellsite Information Transfer Specification Markup Language
  • XML extensible markup language
  • a matrix barcode is generated from the converted wellsite data.
  • the generated matrix barcode is then presented in step 208 via an output device of computing device 110 for transfer to computing device 140.
  • the output device may be a display for presenting a digital representation of the matrix barcode or a printer for printing a physical copy of the matrix barcode, e.g., as part of a report generated by computing device 110.
  • computing device 140 captures the matrix barcode using an image capture device, such as a digital camera, or matrix barcode scanner device coupled to computing device 140.
  • an image capture device such as a digital camera, or matrix barcode scanner device coupled to computing device 140.
  • a matrix barcode reader application executable at computing device 140 also may be used for capturing the matrix barcode, e.g., as it is displayed on a monitor or display of computing device 110 or printed on a physical piece of paper.
  • computing device 140 may present the captured matrix barcode for further transfer to computing device 150.
  • computing device 150 acquires the matrix barcode from computing device 140.
  • device 150 may acquire the matrix barcode by capturing a digital representation or image of the matrix barcode using an image capture device or matrix barcode scanner coupled to device 150.
  • the image capture device or scanner may be utilized by a matrix barcode reader executable at device 150 for capturing the matrix barcode.
  • computing device 150 extracts the wellsite data from the matrix barcode captured in step 214. This may include, for example, converting the extracted wellsite data from the compressed binary format described above into a portable text-based (e.g., XML) format or a proprietary format used by the service company or provider associated with computing device 150, as described above.
  • the extracted wellsite data may then be uploaded in step 218 to a database (e.g., database 160 of FIG. 1) for storage and later use, e.g., as part of a wellsite data management system of the service company or provider in this example.
  • FIG. 3 illustrates an exemplary system 300 for transferring wellsite data between computing devices in a petroleum field using matrix barcodes.
  • a computing device 302 transfers wellsite data in the form of a matrix barcode 303 to a computing device 304.
  • device 302 may be used to implement, for example, computing device 110
  • device 304 may be used to implement, for example, computing device 140.
  • device 302 includes a matrix barcode generator 310 and an I/O interface 315.
  • Device 304 includes a matrix barcode reader 320 and an I/O interface 325.
  • devices 302 and 304 may be associated with disparate computing systems that lack interoperability, as described above.
  • Devices 302 and 304 may use I/O interfaces 315 and 325, respectively, for performing various data input and output functions.
  • device 302 may use I/O interface 315 to receive input from an input device 316 and also, to output information to an output device 318.
  • Input device 316 may be, for example, a user input device including, but not limited to, a mouse, QWERTY keyboard, touch-screen, microphone, or a T9 keyboard.
  • Output device 318 may be, for example, a display or printer.
  • input device 316 and output device 318 may be a single device, e.g., a touch-screen display, which can be used for both input and output.
  • each of devices 302 and 304 may include any number of additional components for implementing the matrix barcode based data transfer functionality disclosed herein.
  • matrix barcode generator 310 includes a data converter 312 and a matrix barcode renderer 314.
  • matrix barcode generator 310 obtains wellsite data from a data source at the wellsite.
  • the data source may be, for example, an instrumentation device of a drilling rig (e.g., drilling rig 112 of FIG. 1, as described above).
  • device 302 may communicate with the instrumentation device on a periodic basis or per-event basis, e.g., based on commands received from a user via I/O interface 315.
  • the wellsite data obtained from the instrumentation device in this example may be in a proprietary format.
  • the proprietary format may be associated with, for example, the particular service provider responsible for operating the instrumentation device.
  • data converter 312 converts the wellsite data from the proprietary format to a portable text-based format (e.g., WITSML), as described above.
  • the converted wellsite data may then be used by data converter 312 to generate at least one matrix barcode 303.
  • Matrix barcode 303 may be generated using any of various well- known encoding formats for creating matrix barcodes of various sizes and levels of error correction.
  • matrix barcode 303 is a matrix barcode stream including a plurality of matrix barcodes generated by data converter 312 based on the converted wellsite data.
  • Multiple matrix barcodes may need to be generated if, for example, the size of the converted wellsite data is greater than the maximum storage capacity of a single matrix barcode symbol, e.g., depending on the encoding format that is used, dimensions of the matrix barcode being generated, and selected error-correction level.
  • the conversion operation performed by data converter 312 may also include generating a binary version of the wellsite data that has been converted into the portable text-based format.
  • Data converter 312 may also use a binary data compression format to compress the binary wellsite data and generate a compressed binary representation of the converted wellsite data. The compressed data may then be embedded into one or more matrix barcodes generated by data converter 312. This would allow a larger amount of data to be embedded within each matrix barcode that is generated.
  • matrix barcode renderer 314 uses I/O interface 315 to present a representation of the generated matrix barcode 303 via output device 318 and thereby, enable the wellsite data embedded in matrix barcode 303 to be transferred to device 304.
  • output device 318 may be a display (e.g., a monitor or LED display) of device 302 and the representation of matrix barcode 303 is a digital image of matrix barcode 303 presented on the display.
  • output device 318 may be a printer and the representation of matrix barcode 303 is a printed image of matrix barcode 303 on a physical medium, such as paper.
  • matrix barcode reader 320 of device 304 uses I/O interface 325 to capture matrix barcode 303 as presented by device 302 via an input device 326.
  • Input device 326 may be, for example, an image capturing device, e.g., a digital camera, or matrix barcode scanner coupled to device 304.
  • matrix barcode reader 320 includes a data extractor 322 and a data manager 324.
  • data extractor 322 processes the captured matrix barcode 303 to extract the wellsite data embedded therein. The extracted wellsite data may then be converted by data extractor 322 from one format to another.
  • the wellsite data may be converted from a compressed binary format to a portable text-based format (e.g., WITSML).
  • the wellsite data may be converted into another proprietary format that is used by the service provider associated with device 304 and that is different from the proprietary format used by the service provider associated with device 302 and rig instrumentation device described above.
  • data manager 324 uploads the converted wellsite data to a database (e.g., database 160 of FIGS. 1 and 2, as described above) for storage and later use. While not shown in FIG.
  • device 304 may include a network communications interface capable of receiving and transmitting data over a local or wide-area electronic network, e.g., a private network of the associated service provider.
  • the network interface may be used by data manager 324 to transmit the wellsite data to the database.
  • device 304 may also be capable of displaying or otherwise presenting another representation of matrix barcode 303 via an output device 328 for purposes of transferring matrix barcode 303 and the corresponding wellsite data to another computing device.
  • the other device may be, for example, on the same private network as device 304.
  • the matrix barcode based data transfer functionality described herein may be useful when, for example, there may be limited or no network connectivity available to either device.
  • Matrix barcode generator 310 and matrix barcode reader 320 may each be implemented as, for example, components of a wellsite data collection and reporting application executable at device 302 and device 304, respectively. While matrix barcode generator 310 is shown in FIG. 3 only with respect to device 302, it should be noted that device 304 may include a matrix barcode generator in addition to matrix barcode reader 320 for implementing the matrix barcode generation functionality described above. Likewise, while matrix barcode reader 320 is shown in FIG. 3 only with respect to device 304, it should be noted that device 302 may include a matrix barcode reader in addition to matrix barcode generator 310 for implementing the matrix barcode reading/capture and data extraction functionality described above. Thus, referring back to FIGS. 1 and 2, each of computing devices 110, 120, 130, 140, and 150 may implemented using, for example, one or both of matrix barcode generator 310 and matrix barcode reader 320 of devices 302 and 304, respectively, as described above.
  • FIG. 4 is a process flowchart of an exemplary method 400 for enabling wellsite data transfer between petroleum field devices using matrix barcodes.
  • Method 400 includes steps 402, 404, 406, and 408.
  • steps 402, 404, 406, and 408 For discussion purposes, method 400 will be described using system 100 of FIG. 1, as described above, but is not intended to be limited thereto. Also, for discussion purposes, method 400 will be described using system 300 of FIG. 3, as described above. For example, the steps of method 400 may be performed by matrix barcode generator 310 of FIG. 3. However, method 400 is not intended to be limited thereto.
  • Method 400 begins in step 402, in which wellsite data is obtained in a first format.
  • the first format may be a data format associated with the particular source of the wellsite data.
  • a source format may be, for example, a proprietary data format used by a particular service provider associated with an instrumentation device or sensor of a drilling rig (e.g., drilling rig 112 of FIG. 1) at the wellsite, as described above.
  • the obtained wellsite data is converted from the first format into a second format to be used for matrix barcode generation.
  • the second format may be, for example, a portable text-based data format.
  • the portable text-based data format may be based on, for example, an extensible markup language (XML) standard for wellsite information transfer (e.g., WITSML), as described above.
  • XML extensible markup language
  • step 406 at least one matrix barcode is generated based on the converted wellsite data.
  • step 404 may include converting the wellsite data from the portable text-based data format into binary data and compressing the binary data using a binary data compression format to generate a compressed binary representation of the wellsite data. Further, step 406 may include, for example, embedding the compressed wellsite data into the matrix barcode being generated.
  • a representation of the generated matrix barcode is presented via an output device for transfer to one or more other computing devices.
  • the output device may be a display
  • the representation of the matrix barcode may be a digital image of the matrix barcode presented via the display for transfer to a second computing device via a digital image capture device of the second computing device.
  • the digital image capture device of the second computing device may be, for example, a digital camera utilized by a matrix barcode reader application (e.g., matrix barcode reader 320 of FIG. 3, as described above) executable at the second computing device.
  • the matrix barcode generated in step 406 may be a matrix barcode stream including a plurality of matrix barcodes
  • the digital image presented via the display is an animated bitmap representation of the matrix barcode stream, e.g., as an animated Graphics Interchange Format (GIF) image.
  • the digital image presented via the display may be a digital video including a plurality of image frames, where different image frames may represent one or more of the plurality of matrix barcodes in the matrix barcode stream. For example, each image frame may be used to display a different one of the plurality of matrix barcodes. Alternatively, consecutive image frames may be used to display the same matrix barcode for a suitable period of time to ensure that the image of the matrix barcode is properly read.
  • FIG. 5 is a process flowchart of another exemplary method 500 for enabling wellsite data transfer between petroleum field devices using matrix barcodes.
  • Method 500 includes steps 502, 504, 506, and 508.
  • steps 502, 504, 506, and 508 For discussion purposes, method 500 will be described using system 100 of FIG. 1, as described above, but is not intended to be limited thereto. Also, for discussion purposes, method 500 will be described using system 300 of FIG. 3, as described above. For example, the steps of method 500 may be performed by matrix barcode reader 320 of FIG. 3. However, method 500 is not intended to be limited thereto.
  • Method 500 begins in step 502, which includes capturing a matrix barcode presented on a display of a computing device.
  • the matrix barcode may be captured using, for example, an image capture device, e.g., a digital camera, or dedicated matrix barcode scanner.
  • the captured matrix barcode in this example may have been presented on a display of the computing device.
  • the matrix barcode may be printed on a sheet of paper or other physical medium, and the printed matrix barcode may be captured using the same image capture device or matrix barcode scanner.
  • wellsite data is extracted from the captured matrix barcode.
  • the extracted wellsite data may then be converted into a portable text-based format in step 506 and uploaded to a database system for data storage and management purposes.
  • FIG. 6 is a block diagram of an exemplary computer system 600 in which embodiments of the present disclosure may be implemented.
  • System 600 can be a computer, phone, PDA, or any other type of electronic device. Such an electronic device includes various types of computer readable media and interfaces for various other types of computer readable media.
  • system 600 includes a permanent storage device 602, a system memory 604, an output device interface 606, a system communications bus 608, a read-only memory (ROM) 610, processing unit(s) 612, an input device interface 614, and a network interface 616.
  • ROM read-only memory
  • Bus 608 collectively represents all system, peripheral, and chipset buses that communicatively connect the numerous internal devices of system 600. For instance, bus 608 communicatively connects processing unit(s) 612 with ROM 610, system memory 604, and permanent storage device 602. From these various memory units, processing unit(s) 612 retrieves instructions to execute and data to process in order to execute the processes of the subject disclosure.
  • the processing unit(s) can be a single processor or a multi-core processor in different implementations .
  • ROM 610 stores static data and instructions that are needed by processing unit(s) 612 and other modules of system 600.
  • Permanent storage device 602 is a read-and-write memory device. This device is a non-volatile memory unit that stores instructions and data even when system 600 is off.
  • Some implementations of the subject disclosure use a mass-storage device (such as a magnetic or optical disk and its corresponding disk drive) as permanent storage device 602.
  • system memory 604 is a read-and-write memory device. However, unlike storage device 602, system memory 604 is a volatile read-and-write memory, such as random access memory. System memory 604 stores some of the instructions and data that the processor needs at runtime.
  • the processes of the subject disclosure are stored in system memory 604, permanent storage device 602, and/or ROM 610.
  • the various memory units include instructions for automatically determining data items for a coincident event in accordance with some implementations. From these various memory units, processing unit(s) 612 retrieves instructions to execute and data to process in order to execute the processes of some implementations.
  • Bus 608 also connects to input and output device interfaces 614 and 606.
  • Input device interface 614 enables the user to communicate information and select commands to the system 600.
  • Input devices used with input device interface 614 include, for example, alphanumeric, QWERTY, or T9 keyboards, microphones, and pointing devices (also called “cursor control devices").
  • Output device interfaces 606 enables, for example, the display of images generated by the system 600.
  • Output devices used with output device interface 606 include, for example, printers and display devices, such as cathode ray tubes (CRT), liquid crystal displays (LCD), and light emitting diode (LED) displays. Some implementations include devices such as a touchscreen that functions as both input and output devices.
  • CTR cathode ray tubes
  • LCD liquid crystal displays
  • LED light emitting diode
  • embodiments of the present disclosure may be implemented using a computer including any of various types of input and output devices for enabling interaction with a user.
  • Such interaction may include feedback to or from the user in different forms of sensory feedback including, but not limited to, visual feedback, auditory feedback, or tactile feedback.
  • input from the user can be received in any form including, but not limited to, acoustic, speech, or tactile input.
  • interaction with the user may include transmitting and receiving different types of information, e.g., in the form of documents, to and from the user via the above-described interfaces.
  • bus 608 also couples system 600 to a public or private network (not shown) or combination of networks through a network interface 616.
  • a network may include, for example, a local area network (“LAN”), such as an Intranet, or a wide area network (“WAN”), such as the Internet.
  • LAN local area network
  • WAN wide area network
  • Some implementations mclude electronic components, such as microprocessors, storage and memory that store computer program instructions in a machine-readable or computer-readable medium (alternatively referred to as computer-readable storage media, machine-readable media, or machine-readable storage media).
  • Some examples of such computer-readable media include RAM, ROM, read-only compact discs (CD-ROM), recordable compact discs (CD-R), rewritable compact discs (CD-RW), read-only digital versatile discs (e.g., DVD-ROM, dual-layer DVD-ROM), a variety of recordable/rewritable DVDs (e.g., DVD-RAM, DVD-RW, DVD+RW, etc.), flash memory (e.g., SD cards, mini- SD cards, micro-SD cards, etc.), magnetic and/or solid state hard drives, read-only and recordable Blu-Ray® discs, ultra density optical discs, any other optical or magnetic media, and floppy disks.
  • CD-ROM compact discs
  • CD-R
  • the computer-readable media can store a computer program that is executable by at least one processing unit and includes sets of instructions for performing various operations.
  • Examples of computer programs or computer code include machine code, such as is produced by a compiler, and files including higher-level code that are executed by a computer, an electronic component, or a microprocessor using an interpreter. While the above discussion primarily refers to microprocessor or multi-core processors that execute software, some implementations are performed by one or more integrated circuits, such as application specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs). In some implementations, such integrated circuits execute instructions that are stored on the circuit itself. Accordingly, the steps of exemplary methods 400 and 500 of FIGS. 4 and 5, respectively, as described above, may be implemented using system 600 of FIG. 6, as described above, or any computer system including processing circuitry or a computer program product including instructions which, when executed by at least one processor, causes the processor to perform functions relating to these methods.
  • ASICs application specific integrated circuits
  • FPGAs
  • Embodiments of the subject matter described in this specification can be implemented in a computing system that includes a back end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this specification, or any combination of one or more such back end, middleware, or front end components.
  • the components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network.
  • Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), an inter-network (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks).
  • LAN local area network
  • WAN wide area network
  • inter-network e.g., the Internet
  • peer-to-peer networks e.g., ad hoc peer-to-peer networks.
  • the computing system can include clients and servers.
  • a client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
  • a server transmits data (e.g., a web page) to a client device (e.g., for purposes of displaying data to and receiving user input from a user interacting with the client device).
  • client device e.g., for purposes of displaying data to and receiving user input from a user interacting with the client device.
  • Data generated at the client device e.g., a result of the user interaction
  • any specific order or hierarchy of steps in the processes disclosed is an illustration of exemplary approaches. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged, or that all illustrated steps be performed. Some of the steps may be performed simultaneously. For example, in certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.
  • exemplary methodologies described herein may be implemented by a system including processing circuitry or a computer program product including instructions which, when executed by at least one processor, causes the processor to perform any of the methodology described herein.
  • a computer-implemented method for enabling wellsite data transfer between petroleum field devices using coded data images includes: obtaining wellsite data in a first format at a first computing device; converting the obtained wellsite data from the first format into a second format to be used for coded data image generation; generating at least one coded data image based on the converted wellsite data; and presenting via an output device of the first computing device a representation of the generated coded data image for transfer to a second computing device.
  • the first and second computing devices are associated with disparate computing systems that lack interoperability.
  • the first format is a proprietary data format supported by only the first computing device and the second format is a portable text-based data format supported by each of the first and second computing devices.
  • the portable text-based data format is based on an extensible markup language (XML) standard for wellsite information transfer.
  • the above-described method includes: converting the wellsite data from the proprietary data format into the portable text-based format; generating a binary version of the converted wellsite data in the portable text-based data format; and compressing the binary version of the wellsite data using a binary data compression format to generate a compressed binary representation of the wellsite data, wherein generating at least one coded data image includes embedding the compressed wellsite data into the coded data image being generated.
  • the output device is a display of the first computing device
  • the representation of the coded data image is a digital image of the coded data image presented via the display for transfer to the second computing device via a digital image capture device of the second computing device.
  • the second computing device is configured to capture the coded data image presented on the display of the first computing device via the digital image capture device, extract the wellsite data from the captured coded data image, convert the extracted wellsite data into a portable text-based format, and transmit the converted wellsite data to a database system for storage and later use.
  • the coded data image is a matrix barcode and the digital image capture device of the second computing device is a digital camera utilized by a matrix barcode reader application executable at the second computing device.
  • generating at least one matrix barcode comprises generating a matrix barcode stream including a plurality of matrix barcodes and the digital image presented via the display is an animated bitmap representation of the matrix barcode stream.
  • the digital image presented via the display is a digital video including a plurality of image frames representing one or more of the plurality of matrix barcodes in the matrix barcode stream.
  • a system for enabling wellsite data transfer between petroleum field devices using coded data images comprises at least one processor and a memory including instructions stored therein, which when executed by the processor, cause the processor to perform functions including functions to: obtain wellsite data in a first format at a first computing device; convert the obtained wellsite data from the first format into a second format to be used for coded data image generation; generate at least one coded data image based on the converted wellsite data; and present via an output device of the first computing device a representation of the generated coded data image for transfer to a second computing device.
  • a computer-readable storage medium having instructions stored therein, which when executed by a processor cause the processor to execute functions, including functions to: obtain wellsite data in a first format at a first computing device; convert the obtained wellsite data from the first format into a second format to be used for coded data image generation; generate at least one coded data image based on the converted wellsite data; and present via an output device of the first computing device a representation of the generated coded data image for transfer to a second computing device.

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Mining & Mineral Resources (AREA)
  • Geology (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • General Engineering & Computer Science (AREA)
  • General Life Sciences & Earth Sciences (AREA)
  • Geochemistry & Mineralogy (AREA)
  • Fluid Mechanics (AREA)
  • Environmental & Geological Engineering (AREA)
  • Electromagnetism (AREA)
  • Automation & Control Theory (AREA)
  • Toxicology (AREA)
  • Computer Vision & Pattern Recognition (AREA)
  • Artificial Intelligence (AREA)
  • General Health & Medical Sciences (AREA)
  • Health & Medical Sciences (AREA)
  • Human Computer Interaction (AREA)
  • Geophysics (AREA)
  • Information Transfer Between Computers (AREA)
  • Arrangements For Transmission Of Measured Signals (AREA)

Abstract

L'invention concerne des systèmes et des procédés pour permettre le transfert de données d'emplacement de puits entre des dispositifs de champ de pétrole à l'aide d'images de données codées, telles que des codes à barres matriciels. Des données d'emplacement de puits sont obtenues dans un premier format au niveau d'un premier dispositif informatique. Les données d'emplacement de puits sont converties du premier format en un second format à utiliser pour la production de codes à barres matriciels. Au moins un code à barres matriciel est produit sur la base des données d'emplacement de puits converties. Une représentation du code à barres matriciel produit est présentée par l'intermédiaire d'un dispositif de sortie du premier dispositif informatique pour le transfert à un second dispositif informatique.
PCT/US2014/058642 2014-10-01 2014-10-01 Transfert basé sur des images de données d'emplacement de puits entre des dispositifs dans un champ de pétrole WO2016053331A1 (fr)

Priority Applications (6)

Application Number Priority Date Filing Date Title
US15/505,581 US10380052B2 (en) 2014-10-01 2014-10-01 Image based transfer of wellsite data between devices in a petroleum field
PCT/US2014/058642 WO2016053331A1 (fr) 2014-10-01 2014-10-01 Transfert basé sur des images de données d'emplacement de puits entre des dispositifs dans un champ de pétrole
CA2959310A CA2959310C (fr) 2014-10-01 2014-10-01 Transfert base sur des images de donnees d'emplacement de puits entre des dispositifs dans un champ de petrole
GB1703114.7A GB2545354B (en) 2014-10-01 2014-10-01 Image based transfer of wellsite data between devices in a petroleum field
ARP150102873A AR101792A1 (es) 2014-10-01 2015-09-09 Transferencia basada en imágenes de datos del sitio del pozo entre dispositivos en un campo de petróleo
FR1559181A FR3026871B1 (fr) 2014-10-01 2015-09-29 Transfert a base d'images de donnees de site de puits entre des dispositifs dans un champ petrolifere

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2014/058642 WO2016053331A1 (fr) 2014-10-01 2014-10-01 Transfert basé sur des images de données d'emplacement de puits entre des dispositifs dans un champ de pétrole

Publications (1)

Publication Number Publication Date
WO2016053331A1 true WO2016053331A1 (fr) 2016-04-07

Family

ID=55538119

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2014/058642 WO2016053331A1 (fr) 2014-10-01 2014-10-01 Transfert basé sur des images de données d'emplacement de puits entre des dispositifs dans un champ de pétrole

Country Status (6)

Country Link
US (1) US10380052B2 (fr)
AR (1) AR101792A1 (fr)
CA (1) CA2959310C (fr)
FR (1) FR3026871B1 (fr)
GB (1) GB2545354B (fr)
WO (1) WO2016053331A1 (fr)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11378387B2 (en) 2014-11-12 2022-07-05 Helmerich & Payne Technologies, Llc System and method for locating, measuring, counting, and aiding in the handling of drill pipes
CA2967774C (fr) 2014-11-12 2023-03-28 Covar Applied Technologies, Inc. Systeme et procede pour la mesure de caracteristiques de deblai de forage et d'emplacement avant de fluide pendant des operations de forage avec vision par ordinateur
US12012809B2 (en) 2019-10-16 2024-06-18 Magnetic Variation Services LLC Drill pipe tally system
US12022281B2 (en) 2021-06-23 2024-06-25 Capital One Services, Llc User authentication

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070145137A1 (en) * 2005-12-27 2007-06-28 Mrowiec Zbigniew R Systems and methods for processing measurement data
US20100177212A1 (en) * 2006-05-26 2010-07-15 Lifetouch Inc. Identifying and Tracking Digital Images With Customized Metadata
US20120249870A1 (en) * 2011-03-28 2012-10-04 Pieter Senster Cross-Compiling SWF to HTML Using An Intermediate Format
US20120318578A1 (en) * 2011-06-14 2012-12-20 Forrest Paul Schumacher Method of and system for drilling information management and resource planning
US8543234B2 (en) * 2010-06-07 2013-09-24 Fei Gao Method and software system for treatment planning and surgical guide CAD/CAM

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8121971B2 (en) * 2007-10-30 2012-02-21 Bp Corporation North America Inc. Intelligent drilling advisor
EP2396509B1 (fr) * 2009-02-11 2018-05-30 M-I L.L.C. Appareil et procede pour la caracterisation de puits de forage
US8342406B2 (en) * 2010-09-20 2013-01-01 Research In Motion Limited System and method for data transfer through animated barcodes
US9191266B2 (en) * 2012-03-23 2015-11-17 Petrolink International System and method for storing and retrieving channel data
US9380060B2 (en) * 2013-12-27 2016-06-28 Verizon Patent And Licensing Inc. Machine-to-machine service based on common data format

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070145137A1 (en) * 2005-12-27 2007-06-28 Mrowiec Zbigniew R Systems and methods for processing measurement data
US20100177212A1 (en) * 2006-05-26 2010-07-15 Lifetouch Inc. Identifying and Tracking Digital Images With Customized Metadata
US8543234B2 (en) * 2010-06-07 2013-09-24 Fei Gao Method and software system for treatment planning and surgical guide CAD/CAM
US20120249870A1 (en) * 2011-03-28 2012-10-04 Pieter Senster Cross-Compiling SWF to HTML Using An Intermediate Format
US20120318578A1 (en) * 2011-06-14 2012-12-20 Forrest Paul Schumacher Method of and system for drilling information management and resource planning

Also Published As

Publication number Publication date
FR3026871A1 (fr) 2016-04-08
US10380052B2 (en) 2019-08-13
GB201703114D0 (en) 2017-04-12
US20170284184A1 (en) 2017-10-05
GB2545354B (en) 2021-06-23
AR101792A1 (es) 2017-01-11
CA2959310A1 (fr) 2016-04-07
CA2959310C (fr) 2020-04-21
FR3026871B1 (fr) 2018-10-05
GB2545354A (en) 2017-06-14

Similar Documents

Publication Publication Date Title
Carvajal et al. Intelligent digital oil and gas fields: concepts, collaboration, and right-time decisions
US10380052B2 (en) Image based transfer of wellsite data between devices in a petroleum field
US20210348490A1 (en) Oilfield system
US20090300725A1 (en) Enabling synchronous and asynchronous collaboration for software applications
US20180335907A1 (en) Extensible graphical editor for asset modeling
Flichy et al. The industrial IoT in oil & gas: Use cases
Sadlier et al. Automated decision support to enhance while-drilling decision making: Where does it fit within drilling automation?
JP6552160B2 (ja) 情報管理システム、情報管理方法及びプログラム
Svensson et al. Driving rig performance through real-time data analysis, benchmarking, dashboards and developed key performance indicators
Svensson et al. Improving data quality in witsml data
Eldred et al. A Small Operator's Implementation of a Digital Oil-Field Initiative
Sharma et al. Edge Computing: A Powerful and Agile Platform for Digital Transformation in Oilfield Management
Rosli et al. Closed-Loop Data Analytics for Wells Construction Management in Real Time Centre
Shields Standards Address the Challenges of Drilling Automation
Pickering et al. WITSML" Comes of Age" for the Global Drilling & Completions Industry
Salman et al. Digitalization of a Giant Field–The Rumaila Story
Gauder et al. Practical Staged Implementation of Digital Field with Short Term Benefits
Elrefai et al. Inhouse design and implementation of well integrity database management system
Ritter et al. Industry experience in deriving updated emission factors to characterize methane emissions for select emission sources in natural gas systems
Solvi et al. An Electronic Rig Action Plan-Information Carrier Equally Applicable to the Driller and the Automation Platform
Seale et al. Enterprise SCADA case study: pipeline, plants, production
Arnaout et al. Managing Challenges for Digital Transformation Initiative in a National Drilling Contractor-A Case Study from Algeria
Talabi et al. An Integrated Operations Framework for Enhanced Oil Recovery EOR Management
White et al. Standardized Reporting of Hydraulic Fracturing Treatments Supports Production Optimization and Meeting Regulatory Requirements
US10370939B2 (en) Efficient way of reporting issues associated with reservoir operations to support team

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14903250

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15505581

Country of ref document: US

ENP Entry into the national phase

Ref document number: 2959310

Country of ref document: CA

ENP Entry into the national phase

Ref document number: 201703114

Country of ref document: GB

Kind code of ref document: A

Free format text: PCT FILING DATE = 20141001

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14903250

Country of ref document: EP

Kind code of ref document: A1