METHODS AND SYSTEMS FOR RESOLVING WELL COMPLETION PROBLEMS IN INJECTION NETWORKS

TECHNICAL FIELD

This description relates to methods and systems for solving well completion problems in injection networks.

BACKGROUND

Water injection networks are systems used in oil production to enhance hydrocarbon recovery. These networks include injection wells, water treatment facilities, injection manifolds, and control and monitoring systems. Water is injected into the reservoir through dedicated wells to maintain pressure, displace oil, and improve production rates. Water injection networks enable the efficient distribution and management of injected water, optimizing the process of pushing oil towards production wells and maximizing overall oil recovery from the reservoir. Water injection wells include well completion segments such as casing, tubing, casing string, perforated tubing, among other examples.

SUMMARY

Water injection systems are important for achieving higher oil production rates and eventually higher oil recovery factor. For example, failures in injection wells could result in producing lower oil rates. This disclosure describes systems and methods for using pressure profiles generated from simulation models to identify wellbore hotspots at which in-situ injection pressure is approaching or exceeding internal yield pressure limits of well completions.

One aspect of the subject matter described in this specification may be embodied in a method that involves generating respective water injection hydraulic simulation models for a plurality of injection wells in a water injection network, the water injection network including a plurality of well completion segments; generating, using the respective water injection hydraulic simulation models, respective simulated pressure profiles for the plurality of injection wells at one or more injection rates; determining respective internal yield pressure limits for the plurality of well completion segments; determining, based on the respective internal yield pressure limits and the respective simulated pressure profiles, a potential leak problem in the water injection network; and performing a corrective action to resolve the potential leak problem.

The previously described implementation is implementable using a computer-implemented method; a non-transitory, computer-readable medium storing computer-readable instructions to perform the computer-implemented method; and a computer system including a computer memory interoperably coupled with a hardware processor configured to perform the computer-implemented method or the instructions stored on the non-transitory, computer-readable medium. These and other embodiments may each optionally include one or more of the following features.

In some implementations, generating the water injection hydraulic simulation model for the plurality of injection wells involves generating the water injection hydraulic simulation model for the plurality of injection wells using a steady-state multiphase flow simulation software.

In some implementations, the method further involves maintaining up-to-date versions of the respective water injection hydraulic simulation models based on real-time injection data.

In some implementations, the one or more injection rates include a plant baseline injection rate.

In some implementations, determining respective internal yield pressure limits for the plurality of well completion segments involves: determining that a first well completion segment is damaged; and responsively using a de-rating method to calculate a de-rated internal yield pressure value for the first well completion segment, where the de-rated internal yield pressure value is the respective internal yield pressure limit for the first well completion segment.

In some implementations, the de-rating method is one of: a Default Designating Method (DDM), a Simple De-rating Method (SDM), or an Explicit De-rating Method (EDM).

In some implementations, the de-rating method is selected based on an extent of the damage to the first well completion segment.

The details of one or more embodiments of these systems and methods are set forth in the accompanying drawings and description below. Other features, objects, and advantages of these systems and methods will be apparent from the description, drawings, and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a workflow for detecting a well completion problem and performing a corrective action to resolve the detected problem, according to some implementations.

FIG. 2 illustrates an example Automated Model Advisory Launcher, according to some implementations.

FIG. 3 illustrates a graph depicting different pressure profiles for a horizontal injection well from surface to reservoir at five different sets of plant rates along with the minimum internal yield limit, according to some implementations.

FIG. 4 illustrates a flowchart of an example method, according to some implementations.

FIG. 5 is a block diagram of an example computer system, according to some implementations.

FIG. 6 illustrates hydrocarbon production operations that include both one or more field operations and one or more computational operations, which exchange information and control exploration for the production of hydrocarbons.

DETAILED DESCRIPTION

This disclosure describes systems and methods for using pressure profiles generated from simulation models to identify wellbore hotspots at which in-situ injection pressure is approaching or exceeding internal yield pressure limits of well completions.

FIG. 1 illustrates a workflow 100 for detecting a well completion problem and performing a corrective action to resolve the detected problem, according to some implementations. The workflow 100 can be performed for a water injection network that includes one or more water injection wells. The water injection network can include well completion segments (e.g., casing, tubing, downhole joint, etc.). In some examples, the workflow 100 is performed by a computer system that is configured to monitor and/or control the water injection network. The computer system can be located on-site in the field near the water injection network or can be located off-site (e.g., a cloud computer system). FIG. 5 illustrates an example computer system and is described in more detail below.

At step 102, the computer system develops a water injection hydraulic simulation model, perhaps using a steady-state multiphase flow simulation software. The water injection hydraulic simulation model is a model that is used to simulate the performance or behavior of wells, such as injection wells. The water injection hydraulic simulation model can include a mathematical representation of the injection well, e.g., mathematical equations that the define the operations and properties of the components of the injection well, such as pipelines, choke valves, manifolds, pumps, and other equipment. More specifically, the water injection hydraulic simulation model can simulate the flow of water in the injection well and/or the water injection network based on properties such as, fluid properties, fluid flow rates, pressures, and constraints on the water injection network.

In some examples, the computer system uses the same or similar model for each of the water injection wells. In other examples, the computer system generates a respective water injection hydraulic simulation model for each water injection well in the water injection network. In yet other examples, the computer system uses the same or similar models for subsets of the water injection wells and different models for other subsets of the water injection wells.

At step 104, the computer system maintains up-to-date models for the water injection wells based on real-time injection data (e.g., pressure and flow rate). In some examples, the computer system uses an Automated Model Advisory Launcher to generate and maintain the up-to-date models of the water injection wells based on the real-time injection data. An example Automated Model Advisory Launcher is described in FIG. 2.

FIG. 2 illustrates an example Automated Model Advisory Launcher (AMAL) 200, according to some implementations. The AMAL 200 can be implemented using a computer system, such as the computer system 500 of FIG. 5. The AMAL 200 generates a digital twin representation of a wellbore, e.g., a water injection well. To generate the digital twin representation of the wellbore, the AMAL 200 obtains real-time data from the wellbore and uses the data for generating the digital twin representation. The digital twin representation models the static and dynamic parts of the injection system, which allows users to simulate existing and hypothetical scenarios. As shown in FIG. 2, the AMAL 200 includes a Modeling Infrastructure Library and Modeling Software that is used to generate the digital twin representation. The AMAL 200 creates a link (e.g., .Net link) between a database (e.g., Oracle database) and a steady-state simulator. The Automated Model Advisory Launcher utilizes an automated service to pull and push data from the database.

Returning to FIG. 1, at step 106, the computer system, e.g., using the AMAL 200, generates simulated pressure profiles for the injection wells at one or more plant rates. The simulated pressure profile is a pressure profile versus depth. In particular, the computer system generates simulated in-situ pressure profiles from wellhead to injection zone at the one or more plant rates. In some examples, the computer system first generates a simulation pressure profile at a baseline plant rate, and then generates one or more additional simulation pressure profiles at different plant rates. The different plant rates can be pre-configured, e.g., based on a user input or based on historical data. Note that the different plant rates can be defined as a percentage of the baseline rate. For instance, the one or more plant rates can include a baseline plant rate (i.e., 100% of the baseline plant rate), 50% of the baseline plant rate, 75% of the baseline plant rate, 125% of the baseline plant rate, 150% of the baseline plant rate, etc. Note that the pressure profiles can be simulated at different operation conditions. Also, an example simulated pressure profile is shown in FIG. 3 and described in more detail below.

At step 108, the computer system identifies an internal yield pressure limit for each of the injection wells. In particular, the computer system can obtain a respective internal yield pressure for each well completion segment in an injection well. The yield pressure profiles can depend on the types and sizes of the installed casing and tubing strings. In some examples, if a well completion segment is damaged (e.g., due to corrosion or other damage), the computer system can calculate a de-rated internal yield pressure value for that well completion segment. The computer system can use a corrosion log to determine whether a well completion segment is damaged. The de-rated internal yield pressure figures can be obtained using one of several methods, including a Default Designating Method, a Simple De-rating Method, and an Explicit De-rating Method. In some examples, the computer system selects the de-rating method to use based on the extent of the damage to the well completion segment, which can be determined from the corrosion log.

The following is an example of using the Explicit De-rating Method, which is appropriate for suspected or known corrosion in tubulars (e.g., casing or tubing). In this method, the de-rating of the minimum internal yield pressure for the inner and outer strings can be quantified by an explicit reduction of the nominal casing thickness due to corrosion or other damage. More specifically, an adjusted minimum internal yield pressure (MIPY) can be calculated using Equation [1]:

$\begin{matrix} M I Y P_{Adj} = (M I Y P \times U F_{b}) - Δ P_{wcd} . & [1] \end{matrix}$

In Equation [1], MIYP is a minimum internal yield pressure in pound per square inch (PSI) or PSI Gauge (PSIG). UF_bis a (unitless) burst utilization factor with a maximum value of 1.0. The value of the burst utilization factor deteriorates based on the metal loss of the well completion segment. And Δ P_wcdis the pressure differential pressure from the interior to the exterior of the well completion segment at the worst tubular hotspots (e.g., the hotspots with the highest metal loss as determined from a corrosion log).

At step 110, the computer system identifies well completion segments that are approaching the limits of the determined internal yield pressures. That is, the computer system determines whether there is a problem with the water injection network. The computer system uses the simulated pressure profiles to identify wellbore hotspots at which the in-situ injection pressure is approaching or exceeding internal yield pressure limits of the well completion segments. Additionally, the computer system can compare the simulated (in-situ) pressure to the adjusted MIYP at the tubular hotspots.

FIG. 3 illustrates a graph 300 depicting different pressure profiles for a horizontal injection well from surface to reservoir at five different sets of plant rates along with the minimum internal yield limit, according to some implementations. As shown in FIG. 3, the simulated pressure profile is generated for plant rates that include a baseline plant rate (i.e., 100% of the baseline plant rate), 50% of the baseline plant rate, 75% of the baseline plant rate, 125% of the baseline plant rate, and 150% of the baseline plant rate.

Returning to FIG. 1, at step 112, the computer system takes corrective actions to ensure injection wells are operating within the internal yield pressure limits. In particular, the computer system causes a corrective action to be performed to avoid or mitigate the detected problem before a completion failure occurs. As an example, if the computer system determines that a well completion segment is approaching the limits of internal yield pressure, the computer system causes a corrective action to be performed that prevents the well completion segment from approaching the limits of internal yield pressure, thereby ensuring that the injection wells are operating within internal yield pressure limits. Additionally, the computer system can cause more robust internal corrosion logging for well completion segments exposed to in-situ pressure approaching internal yield limits. That is, the computer system can identify well candidates for robust internal corrosion logging by considering completion segments that are exposed to in-situ pressure approaching internal yield limits. Additionally, the computer system can provide outputs that suggest enhanced upgrades for injection system networks. Furthermore, the computer system can generate instructions that reduce the injection rate of the well by (i) restricting the choke valve and/or (ii) closing the well and isolating it from the injection system until the integrity of impacted downhole string is restored by a workover rig.

The workflow 100 maintains the integrity of downhole completions of injection wells by coupling hydraulic simulation features with the results of corrosion logs. Doing so enables a hydrocarbon system to identify well completion segments that are prone to reach/exceed internal yield pressure limits in water injection networks. Thus, the workflow 100 provides proactive identification of potential completion failures before they actually occur, which improves the reliability of water injection systems.

FIG. 4 illustrates a flowchart of an example method 400, according to some implementations. For clarity of presentation, the description that follows generally describes method 400 in the context of the other figures in this description. For example, method 400 can be performed by computer system 500 of FIG. 5. It will be understood that method 400 can be performed, for example, by any suitable system, environment, software, hardware, or a combination of systems, environments, software, and hardware, as appropriate. In some implementations, various steps of method 400 can be run in parallel, in combination, in loops, or in any order.

At step 402, method 400 involves generating respective water injection hydraulic simulation models for a plurality of injection wells in a water injection network, the water injection network including a plurality of well completion segments.

At step 404, method 400 involves generating, using the respective water injection hydraulic simulation models, respective simulated pressure profiles for the plurality of injection wells at one or more injection rates.

At step 406, method 400 involves determining respective internal yield pressure limits for the plurality of well completion segments.

At step 408, method 400 involves determining, based on the respective internal yield pressure limits and the respective simulated pressure profiles, a potential leak problem in the water injection network.

At step 410, method 400 involves performing a corrective action to resolve the potential leak problem.

In some implementations, the method further involves maintaining up-to-date versions of the respective water injection hydraulic simulation models based on real-time injection data.

In some implementations, the one or more injection rates include a plant baseline injection rate.

In some implementations, the de-rating method is one of: a Default Designating Method (DDM), a Simple De-rating Method (SDM), or an Explicit De-rating Method (EDM).

In some implementations, the de-rating method is selected based on an extent of the damage to the first well completion segment.

FIG. 5 is a block diagram of an example computer system 500 that can be used to provide computational functionalities associated with described algorithms, methods, functions, processes, flows, and procedures, according to some implementations of the present disclosure.

The illustrated computer 502 is intended to encompass any computing device such as a server, a desktop computer, an embedded computer, a laptop/notebook computer, a wireless data port, a smart phone, a personal data assistant (PDA), a tablet computing device, or one or more processors within these devices, including physical instances, virtual instances, or both. The computer 502 can include input devices such as keypads, keyboards, and touch screens that can accept user information. Also, the computer 502 can include output devices that can convey information associated with the operation of the computer 502. The information can include digital data, visual data, audio information, or a combination of information. The information can be presented in a graphical user interface (UI) (or GUI). In some implementations, the inputs and outputs include display ports (such as DVI-I+2x display ports), USB 3.0, GbE ports, isolated DI/O, SATA-III (6.0 Gb/s) ports, mPCIe slots, a combination of these, or other ports. In instances of an edge gateway, the computer 502 can include a Smart Embedded Management Agent (SEMA), such as a built-in ADLINK SEMA 2.2, and a video sync technology, such as Quick Sync Video technology supported by ADLINK MSDK+. In some examples, the computer 502 can include the MXE-5400 Series processor-based fanless embedded computer by ADLINK, though the computer 502 can take other forms or include other components.

The computer 502 can serve in a role as a client, a network component, a server, a database, a persistency, or components of a computer system for performing the subject matter described in the present disclosure. The illustrated computer 502 is communicably coupled with a network 530. In some implementations, one or more components of the computer 502 can be configured to operate within different environments, including cloud-computing-based environments, local environments, global environments, and combinations of environments.

At a high level, the computer 502 is an electronic computing device operable to receive, transmit, process, store, and manage data and information associated with the described subject matter. According to some implementations, the computer 502 can also include, or be communicably coupled with, an application server, an email server, a web server, a caching server, a streaming data server, or a combination of servers.

The computer 502 can receive requests over network 530 from a client application (for example, executing on another computer 502). The computer 502 can respond to the received requests by processing the received requests using software applications. Requests can also be sent to the computer 502 from internal users (for example, from a command console), external (or third) parties, automated applications, entities, individuals, systems, and computers.

Each of the components of the computer 502 can communicate using a system bus 503. In some implementations, any or all of the components of the computer 502, including hardware or software components, can interface with each other or the interface 504 (or a combination of both), over the system bus. Interfaces can use an application programming interface (API) 512, a service layer 513, or a combination of the API 512 and service layer 513. The API 512 can include specifications for routines, data structures, and object classes. The API 512 can be either computer-language independent or dependent. The API 512 can refer to a complete interface, a single function, or a set of APIs 512.

The service layer 513 can provide software services to the computer 502 and other components (whether illustrated or not) that are communicably coupled to the computer 502. The functionality of the computer 502 can be accessible for all service consumers using this service layer 513. Software services, such as those provided by the service layer 513, can provide reusable, defined functionalities through a defined interface. For example, the interface can be software written in JAVA, C++, or a language providing data in extensible markup language (XML) format. While illustrated as an integrated component of the computer 502, in alternative implementations, the API 512 or the service layer 513 can be stand-alone components in relation to other components of the computer 502 and other components communicably coupled to the computer 502. Moreover, any or all parts of the API 512 or the service layer 513 can be implemented as child or sub-modules of another software module, enterprise application, or hardware module without departing from the scope of the present disclosure.

The computer 502 can include an interface 504. Although illustrated as a single interface 504 in FIG. 5, two or more interfaces 504 can be used according to particular needs, desires, or particular implementations of the computer 502 and the described functionality. The interface 504 can be used by the computer 502 for communicating with other systems that are connected to the network 530 (whether illustrated or not) in a distributed environment. Generally, the interface 504 can include, or be implemented using, logic encoded in software or hardware (or a combination of software and hardware) operable to communicate with the network 530. More specifically, the interface 504 can include software supporting one or more communication protocols associated with communications. As such, the network 530 or the interface's hardware can be operable to communicate physical signals within and outside of the illustrated computer 502.

The computer 502 includes a processor 505. Although illustrated as a single processor 505 in FIG. 5, two or more processors 505 can be used according to particular needs, desires, or particular implementations of the computer 502 and the described functionality. Generally, the processor 505 can execute instructions and manipulate data to perform the operations of the computer 502, including operations using algorithms, methods, functions, processes, flows, and procedures as described in the present disclosure.

The computer 502 can also include a database 506 that can hold data for the computer 502 and other components connected to the network 530 (whether illustrated or not). For example, database 506 can be an in-memory, conventional, or a database storing data consistent with the present disclosure. In some implementations, the database 506 can be a combination of two or more different database types (for example, hybrid in-memory and conventional databases) according to particular needs, desires, or particular implementations of the computer 502 and the described functionality. Although illustrated as a single database 506 in FIG. 5, two or more databases (of the same, different, or combination of types) can be used according to particular needs, desires, or particular implementations of the computer 502 and the described functionality. While database 506 is illustrated as an internal component of the computer 502, in alternative implementations, database 506 can be external to the computer 502.

The computer 502 also includes a memory 507 that can hold data for the computer 502 or a combination of components connected to the network 530 (whether illustrated or not). Memory 507 can store any data consistent with the present disclosure. In some implementations, memory 507 can be a combination of two or more different types of memory (for example, a combination of semiconductor and magnetic storage) according to particular needs, desires, or particular implementations of the computer 502 and the described functionality. Although illustrated as a single memory 507 in FIG. 5, two or more memories 507 (of the same, different, or combination of types) can be used according to particular needs, desires, or particular implementations of the computer 502 and the described functionality. While memory 507 is illustrated as an internal component of the computer 502, in alternative implementations, memory 507 can be external to the computer 502.

An application 508 can be an algorithmic software engine providing functionality according to particular needs, desires, or particular implementations of the computer 502 and the described functionality. For example, an application 508 can serve as one or more components, modules, or applications 508. Multiple applications 508 can be implemented on the computer 502. Each application 508 can be internal or external to the computer 502.

The computer 502 can also include a power supply 514. The power supply 514 can include a rechargeable or non-rechargeable battery that can be configured to be either user- or non-user-replaceable. In some implementations, the power supply 514 can include power-conversion and management circuits, including recharging, standby, and power management functionalities. In some implementations, the power-supply 514 can include a power plug to allow the computer 502 to be plugged into a wall socket or a power source to, for example, power the computer 502 or recharge a rechargeable battery.

There can be any number of computers 502 associated with, or external to, a computer system including computer 502, with each computer 502 communicating over network 530. Further, the terms “client,” “user,” and other appropriate terminology can be used interchangeably without departing from the scope of the present disclosure. Moreover, the present disclosure contemplates that many users can use one computer 502 and one user can use multiple computers 502.

Implementations of the subject matter and the functional operations described in this specification can be implemented in digital electronic circuitry, in tangibly embodied computer software or firmware; in computer hardware, including the structures disclosed in this specification and their structural equivalents; or in combinations of one or more of them. Software implementations of the described subject matter can be implemented as one or more computer programs. Each computer program can include one or more modules of computer program instructions encoded on a tangible, non-transitory, computer-readable computer-storage medium for execution by, or to control the operation of, data processing apparatus. Alternatively, or additionally, the program instructions can be encoded in/on an artificially generated propagated signal. For example, the signal can be a machine-generated electrical, optical, or electromagnetic signal that is generated to encode information for transmission to a suitable receiver apparatus for execution by a data processing apparatus. The computer-storage medium can be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or a combination of computer-storage mediums.

The terms “data processing apparatus,” “computer,” and “electronic computer device” (or equivalent as understood by one of ordinary skill in the art) refer to data processing hardware. For example, a data processing apparatus can encompass all kinds of apparatuses, devices, and machines for processing data, including by way of example, a programmable processor, a computer, or multiple processors or computers. The apparatus can also include special purpose logic circuitry including, for example, a central processing unit (CPU), a field programmable gate array (FPGA), or an application specific integrated circuit (ASIC). In some implementations, the data processing apparatus or special purpose logic circuitry (or a combination of the data processing apparatus and special purpose logic circuitry) can be hardware- or software-based (or a combination of both hardware- and software-based). The apparatus can optionally include code that creates an execution environment for computer programs, for example, code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of execution environments. The present disclosure contemplates the use of data processing apparatuses with or without conventional operating systems, for example, Linux, Unix, Windows, Mac OS, Android, or iOS.

A computer program, which can also be referred to or described as a program, software, a software application, a module, a software module, a script, or code can be written in any form of programming language. Programming languages can include, for example, compiled languages, interpreted languages, declarative languages, or procedural languages. Programs can be deployed in any form, including as stand-alone programs, modules, components, subroutines, or units for use in a computing environment. A computer program can, but need not, correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data, for example, one or more scripts stored in a markup language document; in a single file dedicated to the program in question; or in multiple coordinated files storing one or more modules, sub programs, or portions of code. A computer program can be deployed for execution on one computer or on multiple computers that are located, for example, at one site or distributed across multiple sites that are interconnected by a communication network. While portions of the programs illustrated in the various figures may be shown as individual modules that implement the various features and functionality through various objects, methods, or processes; the programs can instead include a number of sub-modules, third-party services, components, and libraries. Conversely, the features and functionality of various components can be combined into single components as appropriate. Thresholds used to make computational determinations can be statically, dynamically, or both statically and dynamically determined.

The methods, processes, or logic flows described in this specification can be performed by one or more programmable computers executing one or more computer programs to perform functions by operating on input data and generating output. The methods, processes, or logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, for example, a CPU, an FPGA, or an ASIC.

Computers suitable for the execution of a computer program can be based on one or more of general and special purpose microprocessors and other kinds of CPUs. The elements of a computer are a CPU for performing or executing instructions and one or more memory devices for storing instructions and data. Generally, a CPU can receive instructions and data from (and write data to) a memory. A computer can also include, or be operatively coupled to, one or more mass storage devices for storing data. In some implementations, a computer can receive data from, and transfer data to, the mass storage devices including, for example, magnetic, magneto optical disks, or optical disks. Moreover, a computer can be embedded in another device, for example, a mobile telephone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a global positioning system (GPS) receiver, or a portable storage device such as a universal serial bus (USB) flash drive.

Computer readable media (transitory or non-transitory, as appropriate) suitable for storing computer program instructions and data can include all forms of permanent/non-permanent and volatile/non-volatile memory, media, and memory devices. Computer readable media can include, for example, semiconductor memory devices such as random access memory (RAM), read only memory (ROM), phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), and flash memory devices. Computer readable media can also include, for example, magnetic devices such as tape, cartridges, cassettes, and internal/removable disks. Computer readable media can also include magneto optical disks, optical memory devices, and technologies including, for example, digital video disc (DVD), CD ROM, DVD+/−R, DVD-RAM, DVD-ROM, HD-DVD, and BLURAY. The memory can store various objects or data, including caches, classes, frameworks, applications, modules, backup data, jobs, web pages, web page templates, data structures, database tables, repositories, and dynamic information. Types of objects and data stored in memory can include parameters, variables, algorithms, instructions, rules, constraints, and references. Additionally, the memory can include logs, policies, security or access data, and reporting files. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

Implementations of the subject matter described in the present disclosure can be implemented on a computer having a display device for providing interaction with a user, including displaying information to (and receiving input from) the user. Types of display devices can include, for example, a cathode ray tube (CRT), a liquid crystal display (LCD), a light-emitting diode (LED), or a plasma monitor. Display devices can include a keyboard and pointing devices including, for example, a mouse, a trackball, or a trackpad. User input can also be provided to the computer using a touchscreen, such as a tablet computer surface with pressure sensitivity or a multi-touch screen using capacitive or electric sensing. Other kinds of devices can be used to provide for interaction with a user, including to receive user feedback, for example, sensory feedback including visual feedback, auditory feedback, or tactile feedback. Input from the user can be received in the form of acoustic, speech, or tactile input. In addition, a computer can interact with a user by sending documents to, and receiving documents from, a device that is used by the user. For example, the computer can send web pages to a web browser on a user's client device in response to requests received from the web browser.

The term “graphical user interface,” or “GUI,” can be used in the singular or the plural to describe one or more graphical user interfaces and each of the displays of a particular graphical user interface. Therefore, a GUI can represent any graphical user interface, including, but not limited to, a web browser, a touch screen, or a command line interface (CLI) that processes information and efficiently presents the information results to the user. In general, a GUI can include a plurality of user interface (UI) elements, some or all associated with a web browser, such as interactive fields, pull-down lists, and buttons. These and other UI elements can be related to or represent the functions of the web browser.

Implementations of the subject matter described in this specification can be implemented in a computing system that includes a back end component, for example, as a data server, or that includes a middleware component, for example, an application server. Moreover, the computing system can include a front-end component, for example, a client computer having one or both of a graphical user interface or a Web browser through which a user can interact with the computer. The components of the system can be interconnected by any form or medium of wireline or wireless digital data communication (or a combination of data communication) in a communication network. Examples of communication networks include a local area network (LAN), a radio access network (RAN), a metropolitan area network (MAN), a wide area network (WAN), Worldwide Interoperability for Microwave Access (WIMAX), a wireless local area network (WLAN) (for example, using 802.11 a/b/g/n or 802.20 or a combination of protocols), all or a portion of the Internet, or any other communication system or systems at one or more locations (or a combination of communication networks). The network can communicate with, for example, Internet Protocol (IP) packets, frame relay frames, asynchronous transfer mode (ATM) cells, voice, video, data, or a combination of communication types between network addresses.

The computing system can include clients and servers. A client and server can generally be remote from each other and can typically interact through a communication network. The relationship of client and server can arise by virtue of computer programs running on the respective computers and having a client-server relationship.

Cluster file systems can be any file system type accessible from multiple servers for read and update. Locking or consistency tracking may not be necessary since the locking of exchange file system can be done at application layer. Furthermore, Unicode data files can be different from non-Unicode data files.

FIG. 6 illustrates hydrocarbon production operations 600 that include both one or more field operations 610 and one or more computational operations 612, which exchange information and control exploration for the production of hydrocarbons. In some implementations, outputs of techniques of the present disclosure can be performed before, during, or in combination with the hydrocarbon production operations 600, specifically, for example, either as field operations 610 or computational operations 612, or both.

Examples of field operations 610 include forming/drilling a wellbore, hydraulic fracturing, producing through the wellbore, injecting fluids (such as water) through the wellbore, to name a few. In some implementations, methods of the present disclosure can trigger or control the field operations 610. For example, the methods of the present disclosure can generate data from hardware/software including sensors and physical data gathering equipment (e.g., seismic sensors, well logging tools, flow meters, and temperature and pressure sensors). The methods of the present disclosure can include transmitting the data from the hardware/software to the field operations 610 and responsively triggering the field operations 610 including, for example, generating plans and signals that provide feedback to and control physical components of the field operations 610. Alternatively or in addition, the field operations 610 can trigger the methods of the present disclosure. For example, implementing physical components (including, for example, hardware, such as sensors) deployed in the field operations 610 can generate plans and signals that can be provided as input or feedback (or both) to the methods of the present disclosure.

Examples of computational operations 612 include one or more computer systems 620 that include one or more processors and computer-readable media (e.g., non-transitory computer-readable media) operatively coupled to the one or more processors to execute computer operations to perform the methods of the present disclosure. The computational operations 612 can be implemented using one or more databases 618, which store data received from the field operations 610 and/or generated internally within the computational operations 612 (e.g., by implementing the methods of the present disclosure) or both. For example, the one or more computer systems 620 process inputs from the field operations 610 to assess conditions in the physical world, the outputs of which are stored in the databases 618. For example, seismic sensors of the field operations 610 can be used to perform a seismic survey to map subterranean features, such as facies and faults. In performing a seismic survey, seismic sources (e.g., seismic vibrators or explosions) generate seismic waves that propagate in the earth and seismic receivers (e.g., geophones) measure reflections generated as the seismic waves interact with boundaries between layers of a subsurface formation. The source and received signals are provided to the computational operations 612 where they are stored in the databases 618 and analyzed by the one or more computer systems 620.

In some implementations, one or more outputs 622 generated by the one or more computer systems 620 can be provided as feedback/input to the field operations 610 (either as direct input or stored in the databases 618). The field operations 610 can use the feedback/input to control physical components used to perform the field operations 610 in the real world.

For example, the computational operations 612 can process the seismic data to generate three-dimensional (3D) maps of the subsurface formation. The computational operations 612 can use these 3D maps to provide plans for locating and drilling exploratory wells. In some operations, the exploratory wells are drilled using logging-while-drilling (LWD) techniques which incorporate logging tools into the drill string. LWD techniques can enable the computational operations 612 to process new information about the formation and control the drilling to adjust to the observed conditions in real-time.

The one or more computer systems 620 can update the 3D maps of the subsurface formation as information from one exploration well is received and the computational operations 612 can adjust the location of the next exploration well based on the updated 3D maps. Similarly, the data received from production operations can be used by the computational operations 612 to control components of the production operations. For example, production well and pipeline data can be analyzed to predict slugging in pipelines leading to a refinery and the computational operations 612 can control machine operated valves upstream of the refinery to reduce the likelihood of plant disruptions that run the risk of taking the plant offline.

In some implementations of the computational operations 612, customized user interfaces can present intermediate or final results of the above-described processes to a user. Information can be presented in one or more textual, tabular, or graphical formats, such as through a dashboard. The information can be presented at one or more on-site locations (such as at an oil well or other facility), on the Internet (such as on a webpage), on a mobile application (or app), or at a central processing facility.

The presented information can include feedback, such as changes in parameters or processing inputs, that the user can select to improve a production environment, such as in the exploration, production, and/or testing of petrochemical processes or facilities. For example, the feedback can include parameters that, when selected by the user, can cause a change to, or an improvement in, drilling parameters (including drill bit speed and direction) or overall production of a gas or oil well. The feedback, when implemented by the user, can improve the speed and accuracy of calculations, streamline processes, improve models, and solve problems related to efficiency, performance, safety, reliability, costs, downtime, and the need for human interaction.

In some implementations, the feedback can be implemented in real-time, such as to provide an immediate or near-immediate change in operations or in a model. The term real-time (or similar terms as understood by one of ordinary skill in the art) means that an action and a response are temporally proximate such that an individual perceives the action and the response occurring substantially simultaneously. For example, the time difference for a response to display (or for an initiation of a display) of data following the individual's action to access the data can be less than 1 millisecond (ms), less than 1 second(s), or less than 5 s. While the requested data need not be displayed (or initiated for display) instantaneously, it is displayed (or initiated for display) without any intentional delay, taking into account processing limitations of a described computing system and time required to, for example, gather, accurately measure, analyze, process, store, or transmit the data.

Events can include readings or measurements captured by downhole equipment such as sensors, pumps, bottom hole assemblies, or other equipment. The readings or measurements can be analyzed at the surface, such as by using applications that can include modeling applications and machine learning. The analysis can be used to generate changes to settings of downhole equipment, such as drilling equipment. In some implementations, values of parameters or other variables that are determined can be used automatically (such as through using rules) to implement changes in oil or gas well exploration, production/drilling, or testing. For example, outputs of the present disclosure can be used as inputs to other equipment and/or systems at a facility. This can be especially useful for systems or various pieces of equipment that are located several meters or several miles apart, or are located in different countries or other jurisdictions.

While this specification contains many specific implementation details, these should not be construed as limitations on the scope of what may be claimed, but rather as descriptions of features that may be specific to particular implementations. Certain features that are described in this specification in the context of separate implementations can also be implemented, in combination, or in a single implementation. Conversely, various features that are described in the context of a single implementation can also be implemented in multiple implementations, separately, or in any suitable sub-combination. Moreover, although previously described features may be described as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can, in some cases, be excised from the combination, and the claimed combination may be directed to a sub-combination or variation of a sub-combination.

Particular implementations of the subject matter have been described. Other implementations, alterations, and permutations of the described implementations are within the scope of the following claims as will be apparent to those skilled in the art. While operations are depicted in the drawings or claims in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed (some operations may be considered optional), to achieve desirable results. In certain circumstances, multitasking or parallel processing (or a combination of multitasking and parallel processing) may be advantageous and performed as deemed appropriate.

Moreover, the separation or integration of various system modules and components in the previously described implementations should not be understood as requiring such separation or integration in all implementations; and the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

Accordingly, the previously described example implementations do not define or constrain the present disclosure. Other changes, substitutions, and alterations are also possible without departing from the spirit and scope of the present disclosure.

Furthermore, any claimed implementation is considered to be applicable to at least a computer-implemented method; a non-transitory, computer-readable medium storing computer-readable instructions to perform the computer-implemented method; and a computer system comprising a computer memory interoperably coupled with a hardware processor configured to perform the computer-implemented method or the instructions stored on the non-transitory, computer-readable medium.

METHODS AND SYSTEMS FOR RESOLVING WELL COMPLETION PROBLEMS IN INJECTION NETWORKS

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims