In one embodiment, the equipment used to drill a well to recover hydrocarbons from the Earth is called a drilling system. Drilling control systems and planning tools for drilling operations often display schematics of a drilling system and data describing the operation of the drilling system. It can be a challenge to navigate to the location of failures in such drilling system displays.
In one embodiment, a drilling system 100, illustrated in
In one embodiment, a computer 140 receives data from the downhole equipment and sends commands to the downhole equipment through the surface telemetry system 135. In one embodiment the computer 140 includes input/output devices, memory, storage, and network communication equipment, including equipment necessary to connect to the Internet.
In one embodiment, the drilling system 100 includes a drilling control system 145 which monitors and controls the drilling system 100. In one embodiment, the drilling control system 145 monitors sensors (not shown) that detect vibrations, weight on bit, and other parameters of the drilling system 100 that can be used, along with data collected from the downhole equipment through the surface telemetry system 135 (which, in one embodiment, it receives from the computer 140) to analyze drilling system 100 failure modes such as fatigue, yield stress, sinusoidal buckling, helical buckling, lockup, and torque failure. In one embodiment, the drilling control system 145 uses the collected data to estimate where in the drilling system such failures have occurred.
In one embodiment, the drilling control system 145 is part of the computer 140. In one embodiment, the drilling control system 145 is a process that runs in the computer 140. In one embodiment, the drilling control system 145 is a separate computer or processor from the computer 140.
In one embodiment, shown in
The memory 206 stores a plurality of data records 212a-n (data records 212b-n are represented by an ellipsis). Each of the data records 212a-n includes a depth zone field 214, a component description field 216, a failure flag field 218, and other fields represented by ellipsis 220.
In one embodiment, the depth zone field 214 contains data representing a depth zone, which describes a range of depths in a well. In one embodiment, the depths are measured depths. In one embodiment, the depth zone is defined by an upper depth and a lower depth and the range of depths is the depths between the upper depth and the lower depth. In one embodiment, the depth zone is defined by a single depth and the range of depths is the range of depths between the single depth and an offset. In one embodiment, the offset is the same for all data records. In one embodiment, the offset is the same for sets of data records. For example, if the single depth is 3500 feet and the offset is 50 feet, the range of depths is 3500-3550 feet.
In one embodiment, the component description field 216 contains data representing a description of a component in the drill string in the depth zone for the data record. In one embodiment, the component can be any of the components in a drill string including drill pipe, tools, bits, etc. For example, if the depth zone is 4500-4530 feet and the drill string component at that depth is drill pipe, the component description field for the data record 212a-n having that depth would contain a designation representing drill pipe, such as the words “Drill Pipe,” an abbreviation of drill pipe, such as “DP,” or a code that represents drill pipe.
In one embodiment, the failure flag field 218 is a flag that is set upon detection of a failure in the drill string 110 in the depth zone for the data record 212a. In one embodiment, the failure is one of the failure modes that can be detected by the drilling control system 145 (i.e., fatigue, yield stress, sinusoidal buckling, helical buckling, lockup, and torque failure). In one embodiment, the other fields represented by ellipsis 220 are failure flag fields for one or more of the other failure modes that can be detected by the drilling control system 145.
In one embodiment, the drilling control system 145 includes a mouse 222, a keyboard 224, and a graphical user interface 226 that communicate with the processor 204 through the input/output interface 208. In one embodiment, the mouse 222 is one or more of a standard computer mouse, a graphics tablet or a similar device. In one embodiment, the keyboard 224 is one or more of a standard QWERTY keyboard and a key pad. In one embodiment, the graphical user interface 226 is one or more of a monitor and a television.
In one embodiment, the drilling control system 145 includes other equipment 228 that communicate with the processor 204 through the input/output interface 208. In one embodiment, the other equipment 228 includes standard computer peripherals such as an optical drive, a printer, a modem, a network interface, a wireless network interface, and other similar equipment. In one embodiment, the other equipment 228 includes the sensors described above by which the drilling control system 145 can identify drilling system 100 failure modes. In one embodiment, the other equipment 228 includes the surface telemetry system 135. In one embodiment, the other equipment 228 includes the computer 140.
In one embodiment, the drilling control system 145 includes a data store 230, such as a hard drive or a similar device that is accessible to the processor 204 through the bus 210. In one embodiment, the data store 230 stores an operating system and programs to, among other things, accomplish the functions described in this patent application.
In one embodiment, the processor executes a program stored on the data store 230, gathers data from the other equipment 228, accepts further input from the keyboard 224 and mouse 222, analyzes the collected data, and displays the result on the graphical user interface 226. In one embodiment, the results are displayed in a well schematic display area 232, where a well schematic can be displayed, and a well data display area 234, which displays data collected by the drilling control system 145. It will be understood that other data beyond that shown in
In one embodiment, shown in
In one embodiment, shown in
In one embodiment, the one or more columns of the well data table 314 are divided into depth zone rows 322. In one embodiment, the content of each of the cells in the resulting matrix of cells, where each cell is the intersection of a row and a column, corresponds to the presence or absence of the drill system failure associated with the intersecting column at the measured depth zone associated with the intersecting row. In one embodiment, an empty or blank cell indicates that the drill system failure associated with the column that intersects at that cell is not present at the depth associated with the row that intersects at that cell and the presence of a value, such as an “x,” indicates that the corresponding fault has occurred at the corresponding depth. For example, in one embodiment, cell 324 represents the presence or absence of the drill system failure “torque failure” at measured depth 4740-4770 feet (in the example, each row corresponds to a range of 30 feet of measured depth). The fact that cell 324 is empty indicates that the drilling system 100 has not experienced torque failure at measured depth 4740-4770 feet. If cell 324 contained a value, such as an “x,” that would indicate that the drilling system 100 had experienced torque failure at measured depth 4740-4770 feet.
In one embodiment, each of the depth zone rows 322 corresponds to data contained in one data record 212a-n. In one embodiment, the measured depth column 316 contains a representation of the data contained in the depth zone field 214 of a corresponding data record 212a-n. In one embodiment, the component type column 318 contains a representation of the component description field 216. In one embodiment, the drill system failure fields 320 contain a representation of the data contained in the failure flag field 218 and the other failure flag fields contained in the other fields 220 of a corresponding data record 212a-n.
In one embodiment, if a fault (or faults) occurs in the drilling system 100, the processor 204 receives data from the other equipment 228 through the input/output interface 208 and interprets the data to identify the fault (or faults) and the location of the fault (or faults) in the drilling system 100. In one embodiment, the processor 204 will set the flags in the failure flag field 218 or the other fields 220 corresponding to the identified fault (or faults) in the data record or data records 212a-n that correspond to the location of the identified fault (or faults). For example, if the processor 204 determines that the drill string 110 is experiencing sinusoidal buckling at 4530 feet of measured depth, in one embodiment the processor 204 will set the failure flag field 218 or other field 220 associated with the sinusoidal buckling failure in the data record 212a-n which has a depth zone field 214 that includes 4530 feet.
In another embodiment, the data records 212a-n are populated by a planning tool 236 (see
In one embodiment, the processor then causes the portion of the graphical user interface's 226 well schematic display area 232 where the fault occurred (i.e., where the failure flag field 218 or the other failure fields 220 have been set) to be shaded as shown in
In one embodiment, illustrated in
In one embodiment, illustrated in
In use, in one embodiment, as shown in
In one embodiment, the drilling control system 145 uses the processor 204 with access to the memory 206 to generate and transmit for display on a graphical user interface 226 a schematic of a portion of the drill string 110 (block 704). In one embodiment, the schematic is displayed in a well schematic display area 232 of the graphical user interface 226.
In one embodiment, the drilling control system 145 uses the processor 204 to emphasize on the schematic of the portion of the drill string on the graphical user interface 226 a representation of an emphasized depth zone, wherein a failure flag in a data record 212a-n for the emphasized depth zone is set (block 706). In one embodiment, the failure flag is stored in a failure flag field 218 in a data record 212a-n.
In one embodiment, shown in
In one embodiment, the results of calculations that reside in memory 820 are made available through a network 825 to a remote real time operating center 830. In one embodiment, the remote real time operating center 830 makes the results of calculations available through a network 835 to help in the planning of oil wells 840 or in the drilling of oil wells 840.
The word “coupled” herein means a direct connection or an indirect connection.
The text above describes one or more specific embodiments of a broader invention. The invention also is carried out in a variety of alternate embodiments and thus is not limited to those described here. The foregoing description of an embodiment of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto.
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/US2012/050365 | 8/10/2012 | WO | 00 | 1/27/2015 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2014/025361 | 2/13/2014 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
4597662 | Hirata et al. | Jul 1986 | A |
5202680 | Savage | Apr 1993 | A |
5532715 | Bates et al. | Jul 1996 | A |
5973663 | Bates et al. | Oct 1999 | A |
6206108 | MacDonald | Mar 2001 | B1 |
6580823 | Englefield et al. | Jun 2003 | B1 |
6760665 | Francis | Jul 2004 | B1 |
7027925 | Terentyev et al. | Apr 2006 | B2 |
7139689 | Huang | Nov 2006 | B2 |
7357196 | Goldman et al. | Apr 2008 | B2 |
7359844 | Sung et al. | Apr 2008 | B2 |
7630914 | Veeningen et al. | Dec 2009 | B2 |
7730967 | Ballantyne et al. | Jun 2010 | B2 |
7747628 | Tanzy | Jun 2010 | B2 |
7802634 | Boone | Sep 2010 | B2 |
8237714 | Burke | Aug 2012 | B1 |
9141720 | Zak | Sep 2015 | B2 |
20020139527 | Song et al. | Oct 2002 | A1 |
20030015351 | Goldman et al. | Jan 2003 | A1 |
20030025734 | Boose | Feb 2003 | A1 |
20030234782 | Terentyev et al. | Dec 2003 | A1 |
20040138818 | Shray et al. | Jul 2004 | A1 |
20050063251 | Guidry et al. | Mar 2005 | A1 |
20050279532 | Ballantyne | Dec 2005 | A1 |
20060239118 | Guidry | Oct 2006 | A1 |
20070067798 | Wroblewski | Mar 2007 | A1 |
20070103324 | Kosuge | May 2007 | A1 |
20080126049 | Bailey et al. | May 2008 | A1 |
20100133008 | Gawski | Jun 2010 | A1 |
20100147510 | Kwok | Jun 2010 | A1 |
20110047503 | Allen et al. | Feb 2011 | A1 |
20110214090 | Yee | Sep 2011 | A1 |
20120124477 | Edgar | May 2012 | A1 |
20120216117 | Arriola | Aug 2012 | A1 |
20130091432 | Shet | Apr 2013 | A1 |
20130341093 | Jardine | Dec 2013 | A1 |
20140012506 | Adsit | Jan 2014 | A1 |
20140118334 | Guijt | May 2014 | A1 |
20140229877 | Adegbola | Aug 2014 | A1 |
20150193126 | Whalley | Jul 2015 | A1 |
20160162519 | Stowe | Jun 2016 | A1 |
Number | Date | Country |
---|---|---|
2316820 | Feb 2008 | RU |
2373390 | Nov 2009 | RU |
2439315 | Jan 2012 | RU |
Entry |
---|
Discovery House, Australian Government IP Australia, Patent Examination Report No. 1, Patent Application No. 2012387177, which is an AU counterpart to the instant application, Sep. 3, 2015. |
Intellectual Property Office of Singapore, Written Opinion, Application No. 11201408742Q, which is an SG counterpart to the instant application, Sep. 9, 2015. |
European Patent Office, Communication—extended European search report, Application No./Patent No. 12882705.2-1610 / 2861822 PCT/US2012050365, which is an EP counterpart to the instant application, dated Feb. 23, 2016. |
Intellectual Property Office of Singapore, Notification of Grant, Patent Application No. 11201408742Q, which is an SG counterpart to the instant application, dated Mar. 22, 2016. |
Australian Government IP Australia, Patent Examination Report No. 2, Patent Application No. 2012387177, which is an AU counterpart to the instant application, dated Aug. 10, 2016. |
Federal Service on Industrial Property, Official Action of substantive examination, Application No. 2015108061/03(012898), which is an RU counterpart of the instant application, dated May 4, 2016. |
Federal Service on Intellectual Property, Search Report, Application No. 2015108061/03(012898), which is an RU counterpart of the instant application, dated May 4, 2016. |
Translation of the Federal Service on Industrial Property, Official Action of substantive examination, Application No. 2015108061/03(012898), which is an RU counterpart of the instant application, dated May 4, 2016. |
Australia Government IP Australia, Patent Examination Report No. 3, Patent Application No. 201238777, which is an AU counterpart to the instant application, dated Aug. 31, 2016. |
English translation of Federal Service on Intellectual Property (Rospatent), Decision on Grant, Application No. 2015108061/03(012898), entire document, which is a RU counterpart to the instant application, Sep. 14, 2016. |
Federal Service on Intellectual Property (Rospatent), Decision on Grant, Application No. 2015108061/03(012898), which is a RU counterpart to the instant application, entire document, Sep. 14, 2016. |
International Bureau, International Preliminary Report on Patentability, International Application No. PCT/US2012/050365, which is the PCT parent of the instant application, Feb. 10, 2015. |
International Searching Authority, International Search Roport and Written Opinion of the International Searching Authority in PCT/US2012/050365, which is the PCT parent of the instant application, Nov. 2, 2012. |
Canadian Intellectual Property Office, Examiner's Requisition, Application No. 2,881,630, which is a CA counterpart of the instant application, Feb. 8, 2016. |
Number | Date | Country | |
---|---|---|---|
20150193126 A1 | Jul 2015 | US |