US20130192823A1

US20130192823A1 - Systems, methods, and devices for monitoring wellbore conditions

Info

Publication number: US20130192823A1
Application number: US13/748,660
Authority: US
Inventors: Mark Francis Barrilleaux; Gary Hurst
Original assignee: BP Corp North America Inc
Current assignee: BP Corp North America Inc
Priority date: 2012-01-25
Filing date: 2013-01-24
Publication date: 2013-08-01
Also published as: EP2807336A2; WO2013112674A2; BR112014018074A2; WO2013112674A3; AU2013212140A1

Abstract

A method includes releasing a flow device into a wellbore to travel towards a target device that is positioned in the wellbore and that is actuated by the flow device, monitoring for communications transmitted by the flow device. The method further includes identifying a condition of the wellbore from the communications.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent Application No. 61/590,483 filed Jan. 25, 2012, the disclosure of which is incorporated by reference herein in its entirety.

TECHNICAL FIELD

Aspects of the disclosure are related to the exploration and production of natural resources, and in particular, to technology for monitoring the condition of wellbore environments.

BACKGROUND

In the field of oil and gas exploration and production, wellbore environments can be enhanced with specialized monitoring and communication technologies. Often referred to as smart wells, these environments are equipped with sensor networks and other monitoring equipment that provide above-ground operators with a detailed view of the well, which improves operating conditions and results.
In many examples, well conditions are reported to the surface by way of communication cabling installed along the drill string. Conditions are monitored using a variety of equipment located in the wellbore, such as near field communications components that detect the presence or absence of downhole tools. For instance, a near-field tag may be applied to a piece of equipment that, as the equipment is positioned in the well, interacts with near-field sensors to report the position of the equipment.
These and other examples present attempt to address the difficult operating conditions found within a wellbore. The sheer depth of a well and the characteristics of the geology surrounding the well can make communicating with downhole elements challenging. In addition, the expense of outfitting a smart well can be prohibitive relative to the associated benefits.

SUMMARY

Implementations are directed to systems, devices, methods, and software that enhance the monitoring of wellbore environments and their operation. According to implementations, a method can include releasing a flow device into a wellbore to travel towards a target device that is positioned in the wellbore and that is actuated by the flow device, monitoring for communications transmitted by the flow device, and identifying a condition of the wellbore from the communications.
Additionally, according to implementations, a flow device for deployment in a wellbore environment can include a spherical shell encasing components, such as a sensor, a processing system, and an interface system. The sensor can detect at least one characteristic of the wellbore environment. The processing system generates communications based on the characteristic, and the interface system transmits the communications.
Further, according to implementations, a system for monitoring a wellbore environment can include a device release assembly configured to release a flow device into a wellbore to travel towards a target device positioned in the wellbore and actuated by the flow device. The system can also include a wellbore communication system configured to monitor for communications transmitted by the flow device and identifying a condition of the wellbore from the communications.
In implementations, the condition can comprise a level of obstruction of the wellbore derived from a location of the flow device indicated by the communications. In implementations, the flow device senses characteristics of the wellbore and generates the communications based on the characteristics. Transmitting the communications can comprise transmitting the communications while traveling towards the target device. In implementations, subsequent communications can be transmitted by the flow device indicative of the flow device having arrived at the target device.
In implementations, the flow device can comprise a drop ball, the target device comprises a valve, including a landing and a valve seat. In implementations, the target device can comprise a down hole tool and seating the drop ball against the landing allows an application of hydraulic pressure to the down hole tool.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below. It should be understood that this Summary is not intended to limit the scope of the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

Various features of the implementations can be more fully appreciated, as the same become better understood with reference to the following detailed description of the implementations when considered in connection with the accompanying figures, in which:

FIG. 1 is a diagram that illustrates an example of wellbore environment, according to various implementations;

FIG. 2 is a flow diagram that illustrates examples of processes related to wellbore operations, according to various implementations;

FIG. 3A is a diagram that illustrates another example of a wellbore environment, according to various implementations;

FIG. 3B is a diagram that illustrates an example of a wellbore communication system, according to various implementations;

FIG. 4 is a diagram that illustrates another example of a wellbore environment, according to various implementations; and

FIG. 5 is a diagram that illustrates another example of a wellbore environment, according to various implementations.

DETAILED DESCRIPTION

For simplicity and illustrative purposes, the principles of the present teachings are described by referring mainly to examples of various implementations thereof. However, one of ordinary skill in the art would readily recognize that the same principles are equally applicable to, and can be implemented in, all types of information and systems, and that any such variations do not depart from the true spirit and scope of the present teachings. Moreover, in the following detailed description, references are made to the accompanying figures, which illustrate specific examples of various implementations. Electrical, mechanical, logical and structural changes can be made to the examples of the various implementations without departing from the spirit and scope of the present teachings. The following detailed description is, therefore, not to be taken in a limiting sense and the scope of the present teachings is defined by the appended claims and their equivalents.
Various implementations described herein allow operators to release flow devices into wellbore environments. The flow devices can provide a dual purpose: both to actuate a downhole tool, but also to provide useful communications from which the condition of the wellbore can be determined The flow devices and processes associated with the flow devices can provide a cost effective way in which the operation and monitoring of wellbore environments can be improved.
In an example, a drop ball with integrated communication capability can released into a wellbore and flow towards a target device positioned in the well, such as a valve or a tool. The valve or tool can include a seat against which the drop ball can be positioned to actuate the valve or tool. Normally, an operator must wait an extended period of time before applying pressure to actuate the device to ensure that the drop ball has arrived at the target device so as to avoid shearing the seat due to the momentum of the pumping fluid. In this example, the operator can monitor the location of the drop ball and commence pumping upon its arrival at the target device with less delay than what was previously incurred. In addition to monitoring the location of the drop ball, other wellbore conditions can be monitored, such as the level of obstruction within drill pipe. Thus, not only will the operator save valuable time, but the productivity and safety of the wellbore environment will be improved with the increased visibility into wellbore conditions.
FIG. 1 illustrates an example of a wellbore environment 100, according to various implementations. While FIG. 1 illustrates various components contained in the wellbore environment 100, FIG. 1 illustrates one example of a wellbore environment and additional components can be added and existing components can be removed.
As illustrated, the wellbore environment 100 can include a drill pipe 101 extending through a wellbore 103 formed by rock and other surrounding geology 105. It should be understood that a single drill pipe, the drill pipe 101, is shown for purposes of simplicity and clarity even though additional piping is possible and indeed likely. It should also be understood that the drill pipe 101 can be replaced with other kinds of drill string equipment or tubing during drilling, completion, or production periods, or can be referred to by other names. Likewise, it should be understood that other layers and components can exist between the drill pipe 101 and the wellbore 103, such as cement and other elements that can make up the drill string, but are not shown for purposes of clarity. Regardless, implementations described herein are applicable to any kind of tubing that may be deployed in a wellbore environment during any stage of the life of a well.
A target device 107 can be placed within the drill pipe 101. The target device 107 can include a landing 109 or other such instrument that, when engaged by a flow device 111, actuates the target device 107. Examples of the target device 107 can include valves and downhole tools, such as stabilizer, shock, and sledgehammer tools. The flow device 111 can be released into the drill pipe 101 and the wellbore 103 by a device release assembly (D.R.A.) 102. In an example, the flow device 111 can be a drop ball. However, other types of flow devices are possible, such as a dart, cone, sphere, cylinder, or other shaped devices.
The wellbore environment 100 can also include a wellbore communication system 113. The wellbore communication system 113 can be capable of monitoring for communications transmitted by the flow device 111 as the flow device 111 moves towards the target device 107. These communications can provide indications of the progress made by the flow device 111 towards the target device 107 from which the location of the flow device 111 can be derived. Additionally, the communications from the flow device 111 can indicate in-depth information about the condition of the wellbore 103. For instance, the communications can contain data related to the temperature of fluid in the drill pipe 101, the viscosity of the fluid, or the movement of flow device 111, itself (such as acceleration). Any number of characteristics of the wellbore 103 can be monitored by the flow device 111 and communicated to the wellbore communication system 113.
The flow device 111 can communicate with the wellbore communication system 113 in a number of ways in order to transfer the characteristics of the wellbore 103 for processing and monitoring. For instance, the flow device 111 can communicate with the well communication system 113 by way of a communication network deployed along the drill string, for example, the drill pipe 101 and other components. Likewise, the flow device 111 can contain equipment sufficient enough to allow for direct communication between the flow device 111 and the wellbore communication system 113. It should be understood that many communication methods and modes are contemplated herein, as will be discussed in more detail below with respect to FIG. 3A, FIG. 4, and FIG. 5.
FIG. 2 illustrates an example of a process 200 of operation of the wellbore environment 100, according to various implementations. The illustrated stages of the process are examples and that any of the illustrated stages can be removed, additional stages can be added, and the order of the illustrated stages can be changed. Additionally, the following discussion references both the steps outlined by the process 200, but also the time sequence noted in FIG. 1. It should be understood that the process 200 can be implemented by a variety of equipment deployed in the wellbore environment 100 and operated in a distributed manner. Likewise, the process 200 can be implemented in a single, stand-alone piece of equipment capable of performing the stages of the process 200.
Referring to FIGS. 1 and 2, in 201, the D.R.A. 102 can release the flow device 111 into the wellbore 103 at time T₁. At time T₂after the flow device 111 has been released into wellbore 103, the flow device 111 proceeds to drop towards the target device 107 and transmits communications along the way. Communicating can occur continuously or periodically, or can occur at discrete intervals triggered by the proximity of the flow device 111 to another communication element. In addition, the flow device 111 can hold off with any communicating until it arrives at the target device 107. At that time, the flow device 111 can communicate its arrival, but withhold any other information or communications for later retrieval and processing at the surface.
In 203, at time T₃, the wellbore communication system 113 can monitor for the communications as the flow device 111 drops towards the target device 107. The flow device 111 can transmit the communications in a variety of forms, including wireless (e.g., radio frequency (RF) signals), sound, pressure waves, electromagnetic signaling, or the like. The communications can be generated and transmitted in an active manner, but can also be considered passive communications, such as the case with some near-field communication technologies.
In 205, upon receiving the communications, the wellbore communication system 113 can identify a condition of the wellbore 103 from the communications. For instance, the wellbore communication system 113 can interpret the speed with which the flow device 111 reached the target device 107 as indicative of the level of obstruction of the drill pipe 101, or the viscosity of any fluid contained within the drill pipe 101. At time T₄, the flow device 111 can eventually reach the target device 107 and actuates it by way of the landing 109. The arrival of the flow device 111 can cause actuation of the target device 107. Likewise, actuating the target device 107 can require steps other than the arrival of flow device 111. For instance, pumping can be required to seat the flow device 111 tightly against the landing 109. In some cases, this can actuate the target device 107 for its intended purpose, but in many cases the seating of the flow device 111 at landing 109 can trigger other elements, such as hydraulic pumps, that physically actuate the valves or tools represented by the target device 107.
FIGS. 3A and 3B illustrate another example of a wellbore environment 300, according to various implementations. While FIGS. 3A and 3B illustrate various components contained in the wellbore environment 300, FIGS. 3A and 3B illustrate one example of a wellbore environment and additional components can be added and existing components can be removed.
As illustrated in FIG. 3A, the wellbore environment 300 can include a drill pipe 301 positioned within a wellbore 303. The wellbore 303 can be formed by geology 305 through which the wellbore 303 is drilled. As mentioned above with reference to FIG. 1, the drill pipe 301 can include more than the single pipe depicted in FIG. 3A. Likewise, the implementations described herein can be applied to tubing other than just drill pipe, such as any piping used in drilling, completion, or production stages. A target device 307 can be positioned within the drill pipe 301. The target device 307 can include a landing 309 against which the flow device 311 can be seated in order to actuate the target device 307. The flow device 311 can transmit communications to a wellbore communication system (W.C.S.) 313 by way of nodes N₁, N₂, and N₃as it flows towards the target device 307.
FIG. 3A also illustrates one example of a sequence of events for the operation of the wellbore environment 300. As indicated, at time T₁, the flow device 311 has entered the drill pipe 301 and passed node N₁as it flows towards target device 307. The flow device 311 can transmit communications that are detected by node N₁as the flow device 311 passes by node N₁. Node N₁can then relay those or other communications derived from them to the W.C.S. 313 by way of a communication network.
Later at time T₂, the flow device 311 has reached node N₂. As with node N₁, node N₂can detect communications transmitted by the flow device 311 and can relay those or other communications derived from them to the W.C.S. 313. Finally, flow device 311 nears node N₃. Node N₃can detect and relay the communications, transmitted by flow device 311 as it flows towards target device 307, to the W.C.S. 313. The W.C.S. 313 can process the communications to determine the condition of the wellbore 303.
For instance, the communications can contain information related to the temperature, pressure, viscosity, or obstruction levels of fluid contained within the drill pipe 301. These characteristics can be detected or sensed by the flow device 311 as it progresses through the drill pipe 301 towards the target device 307. It should be understood that any number of characteristics could be detected and reported to the W.C.S. 313. It should also be understood that the information pertaining to the characteristics can be encoded in the communications such that the W.C.S. 313 can decode the communications to obtain the information. Any number of encoding protocols suitable for wireless communications within a wellbore can be utilized when generating the communications.
FIG. 3A further illustrates component elements of the flow device 311, the W.C.S. 313, and a communication node 341. The communication node 341 can be representative of nodes N₁, N₂, and/or N₃. As illustrated the flow device 311, the W.C.S. 313, and the communication node 341 can contain some similar components, including processing systems (323, 333, and 343), memories (325, 335, and 345), and communication interfaces (327, 337, and 347). In addition, the W.C.S. 313 can include a user interface 339. The flow device 311 can include one or more of a sensor 329.
In operation, the various processing systems 323, 333, and 343 can be operatively linked to the memories 325, 335, and 345 respectively, as well as the communication interfaces 327, 337, and 347 respectively. The processing systems 323, 333, and 343 can be capable of executing software stored in the corresponding memories 325, 335, and 345. When executing the software, the processing systems 323, 333, and 343 can drive associated ones of the flow device 311, the W.C.S. 313, and the communication node 341 to operate as described herein for each element.
The processing systems 323, 333, and 343 can each be implemented within a single processing device but can also be distributed across multiple processing devices or sub-systems that cooperate in executing program instructions. Examples of the processing systems 323, 333, and 343 can include general purpose central processing units, microprocessors, application specific processors, and logic devices, as well as any other type of processing device.
The communication interfaces 327, 337, and 347 can each include communication connections and devices that allow for communication between devices. For instance, the flow device 311 can communicate with the nodes N₁, N₂, and/or N₃, while nodes N₁, N₂, and/or N₃can communicate with the W.C.S. 313. Likewise, the nodes N₁, N₂, and/or N₃can communicate with each other. Additionally, the flow device 311 can communicate directly with the W.C.S. 313. Examples of connections and devices that together allow for inter-device communication can include network interface cards, antennas, power amplifiers, RF circuitry, transceivers, and other communication circuitry.
The memories 325, 335, and 345 can comprise any storage media readable by processing systems 323, 333, and 343 respectively, and capable of storing software. The memories 325, 335, and 345 can include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. The memories 325, 335, and 345 can each be implemented as a single storage device but can also be implemented across multiple storage devices or sub-systems. The memories 325, 335, and 345 can each include additional elements, such as a controller, capable of communicating with the processing systems 323, 333, and 343. Examples of storage media can include random access memory, read only memory, and flash memory, as well as any combination or variation thereof, or any other type of storage media. In some embodiments, the storage media can be a non-transitory storage media. In some embodiments, at least a portion of the storage media can be transitory. It should be understood that in no case is the storage media a propagated signal.
Software stored on or in the memories 325, 335, and 345 can include computer program instructions, firmware, or some other form of machine-readable processing instructions having processes that when executed by the processing systems 325, 335, and 345 direct associated ones of the flow device 311, the wireless communication system 313, and the communication node 341 to operated as described herein. For example, software can drive the flow device 311 to detect or measure characteristics of the flow device 311, or characteristics of elements external to the flow device 311, and then generate and transmit communications indicative of those characteristics to the W.C.S. 313 by way of the nodes N₁, N₂, and/or N₃. Likewise, the software can drive the communication node 341 to relay communications transmitted by the flow device 311 to the W.C.S. 313. The software can also drive the W.C.S. 313 to monitor for and receive those communications, and to process the communications to identify a condition of the wellbore 303.
The software can be implemented as a single application or as multiple applications or modules. In general, the software can, when loaded into the processing systems 325, 335, and 345 and executed, transform the processing systems 325, 335, and 345, and the flow device 311, the communication node 341, and the W.C.S. 313 from general-purpose devices into special-purpose devices customized to monitor the wellbore environment 300 as described herein.
The flow device 311 can include one or more of the sensor 329. The sensor 329 can detect characteristics of the wellbore environment 300 as the flow device 311 moves through fluids and other materials towards the target device 307. The sensor 329 can interact with those fluids and materials to measure characteristics of them. However, the sensor 329 can be contained within the flow device 311 and can measure characteristics of the flow device 311 itself, such as the acceleration and change in acceleration of the flow device 311 as it moves through the fluid. The sensor 329 can be operatively coupled with the processing system 323, either directly or through the memory 325. It should be understood that, while only one sensor 329 is shown for purposes of clarity, multiple sensors can be integrated within the flow device 311 and deployed to monitor multiple characteristics.
In an example where the flow device 311 is a drop ball or other similar device, the flow device 311 can be enclosed with a casing suitable for wellbore operations. The casing or shell can be sufficiently strong to withstand the temperatures, pressures, and other challenges of a wellbore environment, yet still allow for the transmission of wireless communications. While some metal or steel materials may suffice, other composite, plastic, or ceramic materials can also prove well suited to a wellbore environment.
As mentioned, the W.C.S. 313 can include one or more of a user interface 339. The user interface 339 can have input devices such as a keyboard, a mouse, a voice input device, or a touch input device, and comparable input devices. Output devices such as a display, speakers, printer, and other types of output devices can also be included with the user interface 339. The operation of the user interface 339 will be discussed in more detail with respect to FIG. 3B. The user interface 339 can also be considered to be an integration between the user devices mentioned herein with software elements, such as operating system and application software. For instance, a user can navigate an application view using a user device, such as a mouse. The interface functionality provided by the integration of user interface software with user interface devices can be understood to be part of the user interface 339.
FIG. 3B illustrates two views 351 and 361 that can be displayed to a user by way of the user interface 339. For example, the views 351 and 361 can be displayed on a display of the user interface 339. The views 351 and 361 illustrate various ways in which the condition of the wellbore environment 300 can be presented. In particular, the view 351 can include two graphical representations 353 and 355 of the performance of the wellbore environment 300. The view 361 can include graphical representation 363 corresponding to the wellbore environment 300. The graphical representation 353, 355, and 363 can be made possible by the interaction of the W.C.S. 313 with the flow device 311. In particular, the communications transmitted by the flow device 311 can be processed by the W.C.S. 313 to generate the graphical representations 353, 355, and 363.
In graphical representation 353, the location of a flow device, such as the flow device 311, can be demonstrated in a graphical manner. The wellbore 303 can be depicted as having several sections, including an upper section 302 and a middle section 304, as well as distance markings d2, d3, d4, and d5. Likewise, the flow device 311 can be depicted as located in the upper section 302 of the wellbore 303. The graphical representation 353 can provide the operator with a visualization of the wellbore environment 300, allowing the operator to see a graphical representation of the flow device 311 and its progress as it travels towards the target device 307. This visualization can be useful in that it can allow the operator to plan for and commence pumping close in time to the arrival of the flow device 311 at the target device 307 and/or the bottom of the wellbore 303. In addition, this visualization can alert the operator to any obstructions that may inhibit the flow device 311 from reaching the target device 307.
In the graphical representation 355, the expected distance traveled by the flow device 311 can be depicted by a plot 391 on a graph. Likewise, the actual distance traveled by the flow device 311 can be depicted by a plot 393 on the graph. These depictions can allow an operator to visualize the progress made by the flow device 311 as it travels towards the target device 307 against the expected experience of the flow device 311. Differences in the actual travel time compared against the expected travel time can alert the operator to problems in the wellbore 303.
The view 361 can include a graphical representation 363 pertaining to the content or composition of fluid and material in various sections of the wellbore 303. For instance, the upper section 302 can be shown with cross hatching at an angle relative to the diagonal cross hatching of the middle section 304, while a lower section 306 can shown with a dotted fill. These graphical distinctions can be intended to demonstrate that the composition or state of each section is different relative to composition or state of the other sections. For instance, temperature, pressure, or viscosity differentials between the different sections can be represented by the varying graphical distinctions. These differential states can provide the operator with an indication about the performance of the wellbore environment 300.
It should be noted that the graphical representation 363 depicts a multi-directional well that extends horizontally in some places. The graphical representation 363 can be useful with high angle or horizontal wells in that any geological shoulders or other obstructions created by the layout or path of a well can hinder the progress of a the flow device 311. By displaying the route of the well along with the position of the flow device 311, the operator will be better able to ascertain whether or not such shoulders may be impeding the flow of the flow device 311.
FIG. 4 illustrates another example of a wellbore environment 400 and its operation, according to various implementations. While FIG. 4 illustrates various components contained in the wellbore environment 400, FIG. 4 illustrates one example of a wellbore environment and additional components can be added and existing components can be removed.
As illustrated, the wellbore environment 400 can include a drill pipe 401 surrounded by a wellbore 403. The wellbore 403 can be formed by surrounding geology 405 during the drilling process. A target device 407 can be situated in the drill pipe 401. The target device 407 can include a landing 409. Contact between the landing 409 and a flow device 411 can initiate an actuation of the target device 401. Additionally, due to a conical shape of the landing 409, contact can also cause the flow device 411 to break apart into component parts that drift towards the surface of the wellbore 403 and ultimately transmit communications to a wireless communication system (W.C.S.) 413. It should be understood that shapes other than a conical shape can be utilized to break apart the flow device 411, such as a spiked or spired landing. The W.C.S. 413 can derive a condition of the wellbore 403 from the communications from the flow device 411.
Referring to the time sequence illustrated in FIG. 4, at time T₁, the flow device 411 can be released into the wellbore 403. As discussed above, a device release assembly can be utilized to release the flow device 411. As the flow device 411 travels down the wellbore 403 in the drill pipe 401 towards the target device 407, the flow device 411 can detect characteristics of the wellbore environment for later reporting to the W.C.S. 413. At time T₂, the flow device 411 can contact the landing 409 with sufficient force to break apart the flow device 411 into constituent components. At time T₃, the components can float and/or can be propelled to the surface whereby they can be retrieved and interrogated for information. The W.C.S. 413 can process the information to determine a condition of the wellbore 403. Other methods or mechanisms may also be implemented that bring the flow device 411 to the surface, rather than breaking apart the flow device 411 into its component parts. For instance, the flow device 411 can be pumped to the surface intact.
FIG. 5 illustrates another example of a wellbore environment 500 and its operation, according to various implementations. While FIG. 5 illustrates various components contained in the wellbore environment 500, FIG. 5 illustrates one example of a wellbore environment and additional components can be added and existing components can be removed.
As illustrated, the wellbore environment 500 can includes a drill pipe 501 and a wellbore 503. The wellbore 503 can be formed by geology 505 surrounding it, created during the drilling process. A target device 507 can be placed within the drill pipe 501. In this example, multiple flow devices 511A, 511B, and 511C can be utilized to determine the conditions within the wellbore 503. The flow devices 511A, 511B, and 511C can be utilized to measure different conditions within the wellbore 503. Likewise, the flow device 511A, 511B, and 511C can be utilized to measure the conditions of the wellbore 503 at different times. In operations, the flow devices 511A, 511B, and 511C can flow towards the target device 507. Any of the flow devices 511A, 511B, and 511C can actuate target device 507 upon engaging with a landing 509.
In operation, the flow devices 511A, 511B, and 511C can be released into the drill pipe 501 within the wellbore 503 and can flow towards the target device 507, as indicated by the solid arrows with a downward direction. In this example, the flow devices 511A, 511B, and 511C can be configured to relay communications to a wellbore communication system (W.C.S.) 513. The dotted arrows with an upward direction can represent communications transmitted by the flow device 511A and relayed by flow devices 511B and 511C the W.C.S. 513. The W.C.S. 513 can process the communications to identify a condition of the wellbore 503.
Certain implementations described above can be performed as a computer applications or programs. The computer program can exist in a variety of forms both active and inactive. For example, the computer program can exist as one or more software programs, software modules, or both that can be comprised of program instructions in source code, object code, executable code or other formats; firmware program(s); or hardware description language (HDL) files. Any of the above can be embodied on a computer readable medium, which include computer readable storage devices and media, and signals, in compressed or uncompressed form. Examples of computer readable storage devices and media include conventional computer system RAM (random access memory), ROM (read-only memory), EPROM (erasable, programmable ROM), EEPROM (electrically erasable, programmable ROM), and magnetic or optical disks or tapes. Examples of computer readable signals, whether modulated using a carrier or not, are signals that a computer system hosting or running the present teachings can be configured to access, including signals downloaded through the Internet or other networks. Concrete examples of the foregoing include distribution of executable software program(s) of the computer program on a CD-ROM or via Internet download. In a sense, the Internet itself, as an abstract entity, is a computer readable medium. The same is true of computer networks in general.
While the teachings have been described with reference to examples of the implementations thereof, those skilled in the art will be able to make various modifications to the described implementations without departing from the true spirit and scope. The terms and descriptions used herein are set forth by way of illustration only and are not meant as limitations. In particular, although the method has been described by examples, the steps of the method may be performed in a different order than illustrated or simultaneously. Furthermore, to the extent that the terms “including”, “includes”, “having”, “has”, “with”, or variants thereof are used in either the detailed description and the claims, such terms are intended to be inclusive in a manner similar to the term “comprising.” As used herein, the terms “one or more of” and “at least one of” with respect to a listing of items such as, for example, A and B, means A alone, B alone, or A and B. Further, unless specified otherwise, the term “set” should be interpreted as “one or more.”
Also, the term “couple” or “couples” is intended to mean either an indirect or direct connection. Thus, if a first device couples to a second device, that connection may be through a direct connection, or through an indirect connection via other devices, components, and connections. In addition, as used herein, the terms “axial” and “axially” generally mean along or parallel to a central axis (e.g., central axis of a body or a port), while the terms “radial” and “radially” generally mean perpendicular to the central axis. For instance, an axial distance refers to a distance measured along or parallel to the central axis, and a radial distance means a distance measured perpendicular to the central axis. Those skilled in the art will recognize that these and other variations are possible within the spirit and scope as defined in the following claims and their equivalents.

Claims

What is claimed is:

1. A method of operating a wellbore environment, the method comprising:

releasing a flow device into a wellbore to travel towards a target device that is positioned in the wellbore and that is actuated by the flow device;

monitoring for communications transmitted by the flow device; and

identifying at least one condition of the wellbore from the communications.

2. The method of claim 1, wherein the at least one condition comprises a level of obstruction of the wellbore derived from a location of the flow device indicated by the communications.

3. The method of claim 1, wherein the communications comprise characteristics of the wellbore sensed by the flow device while traveling towards the target device.

4. The method of claim 1, the method further comprising:

monitoring for subsequent communications transmitted by the flow device indicative of the flow device having arrived at the target device; and

upon detecting the subsequent communications, actuating the target device with the flow device by seating the flow device against a landing coupled to the target device.

5. The method of claim 4, wherein the flow device comprises a drop ball, wherein the target device comprises a valve, and wherein the landing comprises a valve seat.

6. The method of claim 4, wherein the flow device comprises a drop ball, wherein the target device comprises a downhole tool, and wherein seating the drop ball against the landing allows an application of hydraulic pressure to the downhole tool.

7. The method of claim 1, the method further comprising:

prior to releasing the flow device into the wellbore, releasing at least one other flow device into the wellbore; and

monitoring for communications transmitted by the at least one other flow device while traveling towards the target device.

8. The method of claim 1, the method further comprising:

prior to releasing the flow device into the wellbore, releasing at least one other flow device into the wellbore, wherein the communications from the flow device comprise communications from the at least one other flow device that are relayed by the flow device.

9. The method of claim 1, wherein monitoring for the communications transmitted by the flow device comprises monitoring for communications transmitted by each of a plurality of components of the flow device separated from each other upon the flow device reaching the target device.

10. A flow device for deployment in a wellbore environment, the flow device comprising:

a shell encasing a plurality of components; and

the plurality of components comprising:

a sensor configured to detect at least one characteristic of the wellbore environment;

a processing system configured to generate communications based on the characteristic; and

an interface system configured to transmit the communications.

11. The flow device of claim 10, wherein the interface system is configured to relay communications received from at least one other flow device.

12. A system for monitoring a wellbore environment, the system comprising:

a device release assembly configured to release a flow device into a wellbore to travel towards a target device that is positioned in the wellbore and that is actuatable by the flow device; and

a wellbore communication system configured to monitor for communications transmitted by the flow device and identify at least one condition of the wellbore from the communications.

13. The system of claim 12, wherein the at least one condition of the wellbore comprises a level of obstruction of the wellbore.

14. The system of claim 12, the system further comprising:

the flow device, wherein the flow device is configured to sense characteristics of the wellbore, generate the communications based on the characteristics, and transmit the communications while traveling towards the target device.

15. The system of claim 12, the system further comprising:

the target device comprising a landing, wherein the target device is actuated with the flow device by seating the flow device against the landing on the target device.

16. The system of claim 15, wherein the flow device comprises a drop ball, wherein the target device comprises a valve, and wherein the landing comprises a valve seat.

17. The system of claim 15, wherein the flow device comprises a drop ball, wherein the target device comprises a downhole tool, and wherein seating the drop ball against the landing allows an application of hydraulic pressure to the downhole tool.

18. The system of claim 12, wherein the wellbore communication system is configured to monitor for subsequent communications transmitted by the flow device indicative of the flow device having arrived at the target device.

19. The system of claim 12, wherein:

the device release assembly is further configured to, prior to release of the flow device into the wellbore, release at least one other flow device into the wellbore; and

the wellbore communication system is further configured to monitor for communications transmitted by the at least one other flow device while traveling towards the target device.

20. A computer readable storage medium comprising instructions that cause a processing system to perform a method comprising:

monitoring for communications transmitted by a flow device released into a wellbore to travel towards a target device that is positioned in the wellbore and that is actuated by the flow device; and

processing the communications to identify at least one condition of the wellbore.

21. The computer readable storage medium of claim 20, wherein the at least one condition of the wellbore comprises a level of obstruction in the wellbore.