WO2016187048A1 - Prospect assessment using structural frameworks - Google Patents

Abstract

Managing traps includes obtaining a structural framework of a subsurface domain. The structural framework represents geologic surfaces of the subsurface domain. Managing traps further includes identifying structural spill points and crestal points for the subsurface domain based at least in part on the structural framework, detecting, using the structural framework, trap envelopes based at least in part on the plurality of structural spill points and the crestal points, and performing a spatial assessment of the subterranean formation based on the trap envelopes. Managing traps further includes conducting a field operation based on the spatial assessment. For example, prospect assessment may be performed based on the spatial assessment and may be used to perform the field operation.

Description

PROSPECT ASSESSMENT USING STRUCTURAL

FRAMEWORKS

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority under 35 U.S.C. § 119(e) to US Provisional

Patent Application Serial Number 62/162,625, filed on May 15, 2015 and entitled, "PROSPECT ASSESSMENT USING STRUCTURAL FRAMEWORKS", which is incorporated herein by reference in its entirety.

BACKGROUND

[0002] Hydrocarbons (e.g., oil and gas) naturally migrate upward from a "source" rock through porous and permeable subterranean strata until the route of the hydrocarbons is eventually blocked by a layer of impermeable rock called a "seal" rock. Along the route of the hydrocarbons, if the hydrocarbons find a structure with a suitable geometrical configuration and bounded from above by such an impermeable layer with a competent sealing capacity, the hydrocarbons will accumulate beneath the sealing body and into the porous layer named "reservoir" rock. In another scenario, the upward migration may be blocked by a radical change in the permeability of the reservoir rock as a result of rapid changes in its lithology or by impermeable faults (lateral seal). The locations in which the migration is blocked are called "traps," further named structural and stratigraphic traps, respectively. Stratigraphic traps also include a bottom seal. The traps may therefore include oil or gas in commercial accumulations. When exploring for oil and gas, geoscientists aim to detect such subsurface locations where migrating hydrocarbons may potentially be trapped and preserved. Once a trap or is found based on the geometrical configuration of potential sealing surfaces, the trap is further analyzed, in particular in terms of reservoir, sealing and hydrocarbon fluid properties, in order to become a "prospect". If, based on the trap analysis hydrocarbons have been predicted to exist in economic quantity the trap location become a prospect. Prospects have one or more proposed drilling locations and are ranked by their chance of success and potentially recoverable oil and gas volumes.

SUMMARY

[0003] In general, in one aspect, one or more embodiments relate to a method for managing traps that includes obtaining a structural framework of a subsurface domain. The structural framework represents geologic surfaces of the subsurface domain. The method further includes identifying structural spill points and crestal points for the subsurface domain based at least in part on the structural framework, detecting, using the structural framework, trap envelopes based at least in part on the plurality of structural spill points and the crestal points, and performing a spatial assessment of the subterranean formation based on the trap envelopes. The method further includes conducting a field operation based on the spatial assessment.

[0004] Other aspects will be apparent from the following description and the appended claims.

BRIEF DESCRIPTION OF DRAWINGS

[0005] FIG. 1 is a schematic view, partially in cross-section, of a field in which one or more embodiments of prospect assessment using structural framework may be implemented.

[0006] FIG. 2 shows a schematic diagram of a system in accordance with one or more embodiments.

[0007] FIG. 3 shows a flowchart in accordance with one or more embodiments.

[0008] FIG. 4.1 provides a general flowchart for performing a prospect assessment using structural framework in accordance with one or more embodiments. [0009] FIGs. 4.2, 4.3, 4.4, and 4.5 are flowcharts representing the expanded workflow of each block of FIG 4.1 in accordance with one or more embodiments.

[0010] FIG. 5.1 shows a 3D structural framework model with faults, horizons and zones of seal and reservoir in accordance with one or more embodiments.

[0011] FIG. 5.2 depict an example of section view of a trap envelope in accordance with one or more embodiments.

[0012] FIG. 5.3 depict an example of section view of the trap envelope with prospect segments delineated in accordance with one or more embodiments.

[0013] FIGs. 5.4 and 5.5 depict an example of section view of the trap envelope with fluid contacts marked on the prospect segments in accordance with one or more embodiments.

[0014] FIGS. 5.6 and 5.7 show examples of 3D structural framework models with trap envelopes, spill points and crestal points and the potential connections among spill and crestal points in accordance with one or more embodiments.

[0015] FIG. 6 shows an example of a prospect evaluation scenario performed using structural framework in accordance with one or more embodiments.

[0016] FIG. 7.1 shows a computing system in accordance with one or more embodiments of the technology.

[0017] FIG. 7.2 shows a network system in accordance with one or more embodiments of the technology.

DETAILED DESCRIPTION

[0018] Specific embodiments will now be described in detail with reference to the accompanying figures. Like elements in the various figures are denoted by like reference numerals for consistency. However, it will be apparent to one of ordinary skill in the art that the invention may be practiced without these specific details. In other instances, well-known features have not been described in detail to avoid unnecessarily complicating the description.

[0020] In general, embodiments of the technology provide a method and system for performing a field operation by at least reducing the uncertainty and risk associated with drilling a well to find or further expand the knowledge of an oil and gas accumulation. In particular, the method may be employed to detect one or more traps (e.g., structural and/or stratigraphic), utilizing a structural framework, geometrical rules as well as assumptions about the sealing rocks and faults. The structural framework is represented by a set of geologic surfaces, which are delineated by subterranean formation boundaries and fault planes. The subterranean formation boundaries and fault planes may be identifiable through seismic data within a defined region in the subsurface. The geometric location of a point on the geologic surfaces is defined by the location's surface distance coordinates and either depth or seismic travel time in the vertical direction.

[0021] Once a trap is detected, a "trap" software object is created and may be elected to become a "prospect" object. The trap object is characterized by a crestal point and one or more spill points. The crestal point is the highest point of a trap. The crestal point is the location the hydrocarbon column is most likely to pierce through the top seal and migrate further upward if the subsurface conditions changes. A spill point is a location where hydrocarbons may escape the trap if the trap were indefinitely supplied and the seal strength is not overcome by the hydrocarbon column height. Further prospect analysis (deterministic or probabilistic) is carried out on the software object to estimate in-place and recoverable oil and gas volumes for the prospect. An evaluation of chance of success of finding oil and gas in the prospect, or prospect risking, may be attached to the prospect assessment. Prospects or subsets of the prospects, called prospect segments, may be summed into prospect groups or plays to enter the decision making process which is resource assessment. One or more embodiments determine a set of scenarios that that may further test the effect of the variability of various prospect attributes. Based on the analysis, drilling locations and trajectories may be determined to recover possible hydrocarbons from the prospects groups or plays.

[0022] FIG. 1 depicts a schematic view, partially in cross section, of a field (100) in which one or more embodiments may be implemented. In one or more embodiments, one or more of the modules and elements shown in FIG. 1 may be omitted, repeated, and/or substituted. Accordingly, embodiments should not be considered limited to the specific arrangements of modules shown in FIG. 1.

[0023] A geologic sedimentary basin contains subterranean formations (104).

As shown in FIG. 1, the subterranean formation (104) may include several geological structures (106-1 through 106-4). As shown, the formation may include a shale layer (106-1), a limestone layer (106-2), a sandstone layer (106- 3), and another shale layer (106-4). A fault plane (107) may extend through the formation. In particular, the geologic sedimentary basin includes rock formations and at least one reservoir including fluids. In one or more embodiments, the rock formations include at least one seal rock as for example the shale layer (106-1), which may act as a top seal. In one or more embodiments, the rock formations may include at least one seal rock as for example the shale layer (106-4), which may act as a bottom seal. In one or more embodiments, various survey tools and/or data acquisition tools are adapted to measure the formation and detect the characteristics of the geological structures of the formation. Generally, survey operations and wellbore operations are referred to as field operations of the field (100). These field operations may be performed as directed by the surface unit (112).

[0024] Petroleum (i.e., oil and gas) may be formed within a basin by chemical reactions of sedimentary organic matter precursor material. After generation, petroleum migrates within the basin via permeable pathways until the netroleum accumulates within porous and permeable reservoir rock formations, or the petroleum is dissipated by chemical or biochemical reactions, or leakage to the adjacent formations or to the surface of the basin. Within any particular basin, one or more "plays" for possible production of hydrocarbons may exist. The United States Geological Survey defines a "play" as "a set of discovered or undiscovered oil and gas accumulations or prospects that exhibit nearly identical geological characteristics such as trapping style, type of reservoir and nature of the seal". A reservoir may include several different plays which differ from each other by the nature of the fluids within the pore spaces of the rock formations and/or the pressure thereof. A "reservoir" is a rock formation with substantially uniform rock mineral properties and spatial distribution of porosity and permeability such that the rock formation has the capability to store fluids, and has the capability for fluids to be produced in an economic way by application of industrial recovery methods. In one or more embodiments, the surface unit (112) is communicatively coupled to the E&P computer system (118). In one or more embodiments, the data received by the surface unit (1 12) may be sent to the E&P computer system (118) for further analysis. Generally, the E&P computer system (118) is configured to analyze, model, control, optimize, or perform management tasks of the aforementioned field operations based on the data provided from the surface unit (112). In one or more embodiments, the E&P computer system (1 18) is provided with functionality for manipulating and analyzing the data, such as performing simulation, planning, and optimization of production operations of the wellsite system A (114-1), wellsite system B (114-2), and/or wellsite system C (1 14-3). In one or more embodiments, the result generated by the E&P computer system (118) may be displayed for an analyst user to view the result in a two dimensional (2D) display, three dimensional (3D) display, or other suitable displays. Although the surface unit (112) is shown as separate from the E&P computer system (1 18) in FIG. 1.1, in other examples, the surface unit (112) and the E&P computer system (118) may also be combined. [0026] Although FIG. 1 shows a field (100) on the land, the field (100) may be an offshore field. In such a scenario, the subterranean formation may be in the sea floor. Further, field data may be gathered from the field (100) that is an offshore field using a variety of offshore techniques for gathering field data.

[0027] In one or more embodiments, the data received by the surface unit (112) represents characteristics of the subterranean formation (104) and may include seismic data and/or information related to location of the horizon and fault surfaces or characteristics of the formation rocks like porosity, saturation, permeability, natural fractures, stress magnitude and orientations, elastic properties, etc. during a drilling, fracturing, logging, or production operation of the wellbore (103) at the wellsite system (1 10).

[0028] FIG. 2 shows more details of the E&P computer system (118) in which one or more embodiments of prospect assessment using structural framework may be implemented. In one or more embodiments, one or more of the modules and elements shown in FIG. 2 may be omitted, repeated, and/or substituted. Accordingly, embodiments of prospect assessment using structural framework should not be considered limited to the specific arrangements of modules shown in FIG. 2.

[0029] As shown in FIG. 2, the E&P computer system (118) includes an analysis tool (210), a data repository (200) for storing input data, intermediate data, and resultant outputs of the analysis tool (210), and a field equipment module (220) for performing various tasks of the field operation. In one or more embodiments, the data repository (200) may include one or more disk drive storage devices, one or more semiconductor storage devices, other suitable computer data storage devices, or combinations thereof. In one or more embodiments, content stored in the data repository (220) may be stored as a data file, a linked list, a data sequence, a database, a graphical representation, any other suitable data structure, or combinations thereof. [0030] In one or more embodiments, the content stored in the data repository (220) includes the structural framework data (201), trap envelopes (202), parameter value sets (203), prospect segments sets (204), prospects (205) and plays (206).

[0031] In one or more embodiments, the structural framework data (201) is data characterizing a structural framework. In other words, the structural framework is a set of geologic surfaces that have particular geometry. The geologic surfaces delineate subterranean formation boundaries and faults. The subterranean formation boundaries and fault planes may be generated by analysis of seismic data obtained for a defined region in the subsurface. The structural framework may include a closed set of faults, horizons, and zones without having gridded properties assigned to any part of the structural framework. The structural framework may be stored as structural framework data (201), which is stored as software objects that fully describes each geologic surface along with the surface's location within the subsurface domain. In one or more embodiments, the subterranean formation (104) of the field (100) may include one or more geologic surfaces, which may be combined to define a structural framework.

[0032] In one or more embodiments the trap envelopes (202) are the geometric locations within the framework of the surfaces that bound zones where hydrocarbons can be trapped as explained above. By definition, the surfaces that bound a trap envelope are represented by sealing surfaces (top or base seal, faults) and the trap base. The trap base is determined by a horizontal plane that passes through the spill point or by an arbitrary plane that is determined based on a selected threshold value for the trap size. A trap envelop may include multiple faults, horizons and zones. A trap envelop is independent from the definition of reservoir and may include one or more reservoir layers. The trap envelope is characterized by the location information, location of crestal and spill points and by values of attributes such gross rock volume (GRV) or a distribution of the GRV within a set interval that can accommodate some level of uncertainty or by values of hydrocarbon fluid levels.

[0033] In one or more embodiments, each of the parameter value sets (203) includes a set of input values corresponding to parameters of the formations and elements within subterranean formation. In one or more embodiments, the input parameters include rock parameter (e.g., porosity, permeability, lithology, age of deposition, etc.), pore fluid data (e.g., fluid density, fluid viscosity, etc.), layer and fault geometry (e.g., layer thickness, etc.), and fault parameter (e.g., capillary pressure, shale gauge ratio, etc.) associated with the prospect. In one or more embodiments, the input values may be assigned to one or more input value set based on a user input and/or field measurements to generate multiple scenarios of the prospects and plays of the field. For example, at least a portion of the assigned values are based on measurements obtained from the data acquisition tools depicted in FIG. 1 above. In one or more embodiments, multiple sets of input values are used to generate multiple scenarios of the prospects and plays of the field. In one or more embodiments, at least a portion of the input parameters may be assigned different values among the multiple sets of input values to generate different scenarios of the prospects and plays.

[0034] In one or more embodiments, the prospect segments (204) represent a subset of the trap envelope volume that are occupied by a geologic formation having reservoir properties. The prospect segments may inherit properties from the parameter value sets (203), from the trap envelopes objects (202) or can have user selected parameter values.

[0035] In one or more embodiments, the prospects (205) represent a selected set of traps for which hydrocarbons have been predicted to exist in economic feasible quantity. The prospects with similar characteristics may be combined together for the scope of risk analysis and become plays (206). Prospect and plays may be characterized by attributes as chance of success (COS) that refer to finding commercial quantities of hydrocarbons, in place, recoverable, and risked volumes of oil or gas. The un-risked or potential in place of oil and gas volumes may be determined based on volumetric parameters of prospect segments like hydrocarbon pore volume (HPCV). The HPCV value may be further scaled based on fluid properties like oil and gas formation volume factors, oil and gas recovery factors, gas-oil-ratio (GOR) and condensate-gas- ratio (CGR) to calculate expressed in stock-tank oil initially in-place (STOIIP), gas initially in place (GUP), recoverable oil, solution gas, recoverable gas and condensate oil. The risked volumes of hydrocarbons are a measure of the probability (chance of success) to find the estimated in-place potential volumes and may be calculated by weighting the un-risked volumes by the COS value.

[0036] In one or more embodiments, the analysis tool (210) includes the user interface (211), the data loader (212), the trap detector (213), the prospect segment analyzer (214) and the scenario tester (215). Each of these components of the analysis tool (210) is described below.

[0037] In one or more embodiments, the user interface (211) corresponds to a graphical user interface that includes functionality to receive input from a user and present or display graphical data to the user. The user interface (211) includes a three dimensional (3D) structural framework viewer, a two dimensional (2D) section of structural framework profile viewer, and parameters value input fields in accordance with one or more embodiments.

[0038] In one or more embodiments, the 3D structural framework viewer shows a rendered image of the structural framework. In such embodiments, a portion of the structural framework is shown on the display. For example, the portion may include a left portion, right portion, top portion, bottom portion, and/or another such portion. In one or more embodiments, the rendering is defined by an observation point angle. The observation point defines the perspective from which the structural framework is viewed. For example, the observation point is a position of a virtual camera or theoretical user from which the structural framework is viewed. In particular, as an example, a top portion may be shown where the view is from above the surface of the earth looking downward at the subterranean formations.

[0039] In one or more embodiments, the 2D section of structural framework profile viewer shows a vertical slice of the structural framework. In particular, as an example, a portion may be shown where the view is a vertical slice of the subterranean formation through the middle of the structural framework, similar to the view in FIG. 5.1.

[0040] Continuing with the user interface (211), the input fields include functionality to receive input parameters from a user. For example, the input parameters may include a formation age of deposition, an observation point angle defining a rendering of the 3D structural framework, a location to display a 2D section of structural framework, a color palette to map different lithology of the subterranean formations, fluid contact location, porosity value for a reservoir section or any other parameter for detecting the trap envelope. In one or more embodiments, a minimum trap size parameter and a maximum trap size parameter are requested by the analysis tool (210). In one or more embodiments, the input fields may include selection boxes, text fields, dropdown menus, or any other type of field for a user to input data.

[0041] Although the user interface (211) is described with respect to the structural framework (201), the user interface (211) may include additional user interface components for oilfield analysis. For example, the user interface (21 1) may include components for simulation and modeling operations, components for interacting with the oilfield, including sending commands to the oilfield, and other components that are not shown or expressly described above.

[0042] In one or more embodiments, the data loader (212) is configured to obtain the structural framework data (201), the parameters values (203) and prospect (205) and play (206) attributes for analysis by the trap detector (213), the prospect segment analyzer (214) and the scenario tester (215). In one or more embodiments, the data loader (212) obtains at least a portion of the parameter values (203), prospect (205) and play (206) attributes from a user. In other words, the portion of the input value sets is specified by the user. In one or more embodiments, the data loader (221) obtains the structural framework data (201), the parameters values (203) and prospect (205) and play (206) attributes for analysis, at least in part, from the surface unit (112) depicted in FIG. 1 above.

[0043] In one or more embodiments, the trap detector (212) is configured to screen through the structural framework model in order to detect trap envelops (202). A trap envelope is a software object which is part of the structural framework object and may be displayed in the 3D in the user interface (211). In one or more embodiments, one or more trap envelopes may be selected and displayed in the 3D or 2D structural framework viewer. The viewer may be further configured to activate a display filter. More particularly, a view may be generated where faults, horizons and zones may be constraint to be displayed in the selected trap envelope(s).

[0044] In one or more embodiments, the trap detector (212) is configured to detect a set of crestal points on the surfaces within the structural framework. The crestal point is the highest point of a trap. For each crestal point, a spill point is detected which defines the trap base. In entirely sealed volumes (e.g., fault blocks), where no spill point exists, the entire volume will be considered as a trap.

[0045] Further, the trap detector (212) is configured to constrain the trap envelope based on a set of minimum and maximum trap size parameters. The minimum trap size parameter may specify a minimum trap volume, a minimum trap area, a minimum possible hydrocarbon column height, a minimum screening wavelength, and/or a smoothening parameter. The maximum trap size parameter may specify a maximum trap volume, a maximum trap area, or a maximum possible hydrocarbon column height. Both minimum and maximum trap size parameters may be dynamically changed, triggering an "on-the-fly" update of the resulting trap envelops.

[0046] In addition, the trap detector (212) may be configured to grid the structural framework model inside a given trap envelope.

[0047] In one or more embodiments, the trap detector (212) is configured to perform complex 3D mapping of potential leak and spill paths. Trap envelops might be connected to each other by potential leak connections and spill connections. The various trap envelopes may be displayed in the 3D or 2D structural framework viewer. Complex potential leak and spill paths like in FIG. 5.7 may be dynamically followed, e.g. from deeper traps into shallower traps. If the structural framework model is updated (e.g., different fault geometry; different velocity model), the trap envelops may be automatically updated, and leak and spill paths might change.

[0048] In one or more embodiments, the prospect segment analyzer (214) is configured to calculate in-place and recoverable oil and/or gas volumes and perform prospect risking. Prospect risking is estimating associated geological chance of success of the prospect. In one or more embodiments present the method of assessing the prospect may employ a 3D spatial analysis of the prospect segment software object. Both the prospect volumetric calculation as well as the prospect risking may benefit from the link to the prospect software object and the prospect software object's representation in the 3D environment. The linking may be particularly beneficial in the case of complex geology, which has multiple dependencies between prospect segments and prospects.

[0049] In one or more embodiments, the prospect segment analyzer (214) may operate on the trap envelopes software object and based on a plurality of input parameters (203). The prospect segment analyzer may partition the trap envelope into one or more prospect segments. In one or more embodiments, the partition, or split, may be based on a vertical separation of the reservoir layers according to properties, such as the age of deposition (or stratigraphic age), porosity, and permeability. The split may result in one or more parallel stripes of reservoir intervals of equivalent stratigraphic age. Further, the prospect segment analyzer (214) includes functionality to split the reservoir intervals in one or more lateral segments based on lithologic properties, such as sedimentation type of deposition, porosity or permeability. The split may result in one or more prospect segments of reservoir zones of equivalent lithologic properties. In one or more embodiments, the split may be determined as a result of a user input, or may be automatically derived from results of sedimentary basin modeling.

[0050] Further, the prospect segment analyzer (214) may be configured to calculate for each segment a segment gross rock volume (GRV) and, by specifying reservoir parameters such as net-to-gross ratio (NTG) and porosity, segment net rock volume (NRV) and net pore volume (NPV). In one or more embodiments, the GRV, NTG, NRV, and NPV, and also the resulting volumes, may be specified in a probabilistic manner by allowing a distribution of values instead of single value.

[0051] Further, the prospect segment analyzer (214) may be configured to define fluid contact(s) within the trap envelope and subsequently within the prospect segments in order to establish possible oil and gas zones across reservoir layers in each trap envelope. In one or more embodiments, these contacts may accommodate a transition interval between them. Based on hydrocarbon saturation in the pore space a hydrocarbon pore volume (HCPV) is calculated. Contacts may be of different type, speculative or proven. Dependent on the possible fluid fill, a prospect segment may be an oil prospect segment (oil column), a gas prospect segment (gas column), or an oil and gas prospect segment (oil column below gas column). Further, the prospect segment analyzer (214) may select the prospect segment fluid contact depth and nature by either one of the following methods. A direct method may specify the contact(s), from, but not limited to, wells within prospect segment or by direct user input of oil and/or gas column heights known from, but not limited to, nearby analogue wells. An indirect method may specify the contact(s) from parameters, such as top/fault/base seal capillary entry pressure for oil, for gas, type/density of charge fluid (oil, gas), charge amount per prospect segment, per trap envelop, or at a given location(s) within the structural framework model. The contact(s) may be a result of the fluid volume migration within the available HCPV, and respecting the seal capacity versus hydrocarbon column height (fluid buoyancy) balance. In one or more embodiments, the parameters of the direct and indirect methods, and also the resulting fluid contacts level, may be specified in a probabilistic manner. The prospect segment may be further (deterministically or probabilistically) specified in terms of fluid properties like oil and gas formation volume factors, oil and gas recovery factors, gas- oil-ratio (GOR) and condensate-gas-ratio (CGR) to calculate the un-risked potential in-place and recoverable oil and gas resources.

[0052] Further, the prospect segment analyzer (214) may be configured to calculate risked volumes of hydrocarbons that are a measure of the probability (chance of success) to find the estimated volumes (un-risked volumes weighted by chance of success). This chance of success may be broken down into different elements, such as charge, reservoir, seal and trap.

[0053] In one or more embodiments, the prospect segment analyzer (214) may be configured to summarize the prospect segments in prospects or prospect collections, which in turn may be summed into plays or entire basins, to build up an exploration portfolio.

[0054] In one or more embodiments, the scenario tester (215) may be configured to perform calculations across the trap envelopes in order evaluate the chance of success for each prospect or for the entire play. Further, based on the calculated prospect or play in-place volumes calculated by the prospect segment analyzer (214) and the trap mapping provided by the trap detector

(213), a set of risked volumes may be calculated taking into account inter- segment and inter- trap dependencies. Inter-segment and inter-trap dependencies may include potential spill and leakage paths as well as consistent correlations both for volumetric and risk parameters. Whereas having a 3D view on the prospect segment when assigning chance of success may be better, some of the risk estimations may directly benefit from the prospect segments embedded into the trap envelopes, which in turn are embedded into the structural framework model. One or more embodiments may address the risk dependencies between prospect segments (e.g., via the prospect segments' common prospect envelop, or via the prospect segments' common reservoir or seal facies) and between trap envelops (e.g., charge within the structural framework model, following fill-and-spill or leakage paths).

[0055] In one or more embodiments, the result generated by the E&P computer system (118) may be displayed to a user using a two dimensional (2D) display, three dimensional (3D) display, or other suitable displays. For example, the trap envelopes result may be used by the user to predict hydrocarbon content throughout portions of the field (100) and to facilitate drilling, fracturing, or other exploratory and/or production operations of the field (100).

[0056] In one or more embodiments, the E&P computer system (118) includes the field equipment module (220) that is configured to generate a field operation control signal based at least on a result generated by the E&P computer system (1 18), such as based on the risked volumes found after scenario testing. As noted above, the field operation equipment depicted in FIG. 1 above may be controlled by the field operation control signal. For example, the field operation control signal may be used to control drilling equipment, an actuator, a fluid valve, or other electrical and/or mechanical devices disposed about the field (100) depicted in FIG. 1 above.

[0057] FIG. 3 depicts an example method in accordance with one or more embodiments. For example, the method depicted in FIG. 3 may be practiced using the E&P computer system (118) described in reference to FIGS. 1 and 2 above. In one or more embodiments, one or more of the elements shown in FIG. 3 may be omitted, repeated, and/or performed in a different order. Accordingly, embodiments of prospect assessment using structural framework should not be considered limited to the specific arrangements of elements shown in FIG. 3.

[0058] In Block 301, a structural framework of a subsurface is obtained in accordance with one or more embodiments. The structural framework may be obtained from a data repository and/or generated. For example, in one or more embodiments, one of more reservoir layers are identified based on the formation porosity and permeability. In one or more embodiments, the reservoir layer is a subsurface layer between two structural framework surfaces. In one or more embodiments the reservoir is identified as having the formation porosity and permeability values above a certain threshold that would allow fluid hydrocarbons to migrate and accumulate in commercial quantities within the layer pore space.

[0059] In Block 302, structural spill points and crestal points for the traps are identified based on the structural framework in accordance with one or more embodiments. For example, the base of the seal surface that is part of the structural framework may be scanned. The scan process is spatially analyzing the derivative of the depth value in order to select low and high points on the surface structure. Further, a set of crestal points on the base of the seal surface are associated with the high structural points and one or more corresponding spill points are associated with adjacent low points. In one or more embodiments the spill point is selected as the highest point on the intersection curve between two surfaces such as a base of a seal surface and a fault surface.

[0060] In Block 303, one or more trap envelopes are defined based on crestal points and spill points and based on the surfaces from the structural framework.

The crestal point is the highest point of a trap. In one or more embodiments the upper boundary of the trap envelope is defined by the sealing surface of the structural framework that include the crestal point. In one or more embodiments the surface that include the crestal point may be the top of the reservoir surface. The spill point is the lowest point of the trap. In one or more embodiments the lower boundary of the trap envelope is selected as the horizontal plane that include the spill point.

[0061] In Block 304, a spatial assessment of the reservoir within the trap envelops may be performed. The spatial assessment may be performed across the trap envelopes and determine the risk factors for the prospect segments within the structural framework. In one or more embodiments, the spatial analysis considers the trap mapping in calculating the COS of one or more of the prospects. In one or more embodiments the risk factors and risked hydrocarbon volumes are calculated taking into account inter-segment and inter-trap dependencies such as potential spill and leakage paths as well as consistent correlations both for volumetric and risk parameters. In one or more embodiments the risked volumes may be substantially reduced compared with the total in place recoverable.

[0062] In Block 305, a field operation is initiated on the prospect well based on the risked volumes calculated. In one or more embodiments the well operation may be a well logging or a formation testing that aim to collect more data regarding the prospect reservoir. In one or more embodiments a well abandonment may be initiated as a result of unacceptable level of chance of failure (COF), where COF is defined as 1- COS. In one or more embodiments, the field operation may be to extract hydrocarbons from the spatial assessment of the traps.

[0063] FIGs. 4.1, 4.2, 4.3, 4.4, and 4.5 show flowcharts in accordance with one or more embodiments. While the various blocks in these flowcharts are presented and described sequentially, one of ordinary skill will appreciate that at least some of the blocks may be executed in different orders, may be combined or omitted, and at least some of the blocks may be executed in oarallel. Furthermore, the actions in the blocks may be performed actively or passively. For example, some actions may be performed using polling or be interrupt driven in accordance with one or more embodiments. By way of an example, determination blocks may not require a processor to process an instruction unless an interrupt is received to signify that condition exists in accordance with one or more embodiments. As another example, determination blocks may be performed by performing a test, such as checking a data value to test whether the value is consistent with the tested condition in accordance with one or more embodiments.

[0064] FIG 4.1 shows a general flowchart to perform a prospect assessment using structural framework in accordance with one or more embodiments. In Block 411, one or more trap envelope is detected based on the structural framework. In Block 412, one or more prospect segments are assessed for volume of hydrocarbons and for the prospect level chance of success factor. In Block 413 the prospect segments are combined to generate prospects, prospect collection, or play level analysis. In Block 414 one or more scenarios are tested for risk factors using the trap envelopes spatial relationships. The Blocks 41 1, 412, 413, and 414 are described in more details in FIGs 4.2, 4.3, 4.4, and 4.5, respectively. In one or more embodiments, the example shown in these figures may be practiced using the E&P computer system shown in FIGS. 1 and 2 and the method described in reference to FIG. 3 above.

[0065] FIG 4.2 shows a flowchart to perform one or more trap envelopes detection in accordance with one or more embodiments.

[0066] In Block 421, a structural framework is loaded in accordance with one or more embodiments. In one or more embodiments, the structural framework may be selected from multiple seismic interpretation results. In one or more embodiments, the structural framework may be loaded and viewed in the graphic interface.

[0067] In Block 422, the reservoirs, fault, and top and bottom seal surfaces within the structural framework are defined in accordance with one or more embodiments. For example, the zones between surfaces of the structural framework that correspond to geologic layers are classified. In one or more embodiments the classification of the layers may be performed according to the layer functionality within the elements of a petroleum system. The petroleum system is represented by an assemblage of subsurface geologic formation that possess one or more organic rich source formation and one or more genetically related hydrocarbon accumulation. The elements of a petroleum systems are the source rock, the reservoir rock, the seal rock and the overburden (neutral) rock.

[0068] In Block 423, one or more crestal and spill points on the fault and seal surfaces are detected. The crestal and spill points may be detected from scanning the base surface of the seal layers. The crestal point are associated with the local high point on the base surface of the seal layers. For each crestal point, one or more spill points are detected by looking for the nearest local low value on the base of the seal surface. The detection is performed by incrementally identifying closed depth or two-way travel time (TWTT) contours until the contour reaches the spill point (no closed depth/TWTT contour). In one or more embodiments, if the closed contours are crossed by a fault surface, a spill point is selected at the location where the fault surface reach the first contour.

[0069] In Block 424, the trap envelopes are defined based on the framework surfaces and crestal and spill points. The trap envelope is the geometric location of the space bounded by multiple surfaces. For each trap envelope, one surface is selected as the top seal that includes a crestal point. Lateral and base seal surfaces may be included. Another surface boundary is selected as the horizontal plane that includes the nearest spill point. If a fault intersection is encountered, the fault surface is selected to bound the trap as well. If no spill point is encountered toward the next seal surface, the entire volume may be considered as a trap. In one or more embodiments, the trap envelope may be constrained based on a set of minimum and maximum trap size parameters. If a minimum trap size parameter is specified based on a minimum trap volume, a minimum trap area, a minimum possible hydrocarbon column height, a minimum screening wavelength, or a smoothening parameter, the trap envelope may not be lower than that value. In one or more embodiments, a combination of multiple may either mitigate micro-traps considered too small to be of interest (big number of spiky artefacts and flat traps; economic threshold), or may merge the traps into bigger traps if possible. Similarly, if a maximum trap size parameter is specified based on a maximum trap volume, a maximum trap area, or a maximum possible hydrocarbon column height the trap envelope cannot exceed that value. The maximum trap size parameters may prevent unrealistic mega-traps by setting an artificial base to the trap, even though the structural spill point is not reached (or if no structural spill point exists).

[0070] In Block 425, the trap envelope parameters are calculated. The gross rock volume (GRV) of the trap envelope may be calculated from trap envelope geometry, and the trap envelopes are ranked according to GRV (lead ranking workflows). In one or more embodiments, a GRV distribution may be calculated for each trap envelop in order to integrate the structural uncertainty of the structural framework model and the trap envelops that the structural framework model hosts. In one or more embodiments, different sets of crestal and spill points may be detected as the structural framework is altered.

[0071] In Block 426, the trap envelope connections are mapped. Trap envelops might be connected to each other. A leak or a spill from one trap envelope may discharge hydrocarbons into an adjacent trap envelope following a path of least hydrodynamic resistance. The potential leak and spill paths are dynamically followed, e.g. from deeper traps into shallower ones and the connections among the plurality of trap envelopes are mapped. In one or more embodiments, the structural framework model is updated (e.g., different fault geometry; different velocity model), and the trap envelops is therefore updated. As a result, the map is changed as the leak and spill paths is changed. [0072] FIG 4.3 shows a flowchart to perform one or more prospect segment assessments. In Block 431, reservoir layers across the trap envelopes are specified in accordance with one or more embodiments. For example, one or more reservoir layers may be selected within each trap envelope. The selection process aims to delineate the reservoir layers within a trap envelope based on stratigraphic or characteristics or parameters value range of formations inside the trap envelope. The stratigraphic characteristics may include age of deposition interval, facies characteristics from sedimentary models, environment of deposition maps or seismic attributes. In one or more embodiments the partition is based on a vertical separation of the reservoir layers according to properties as porosity or permeability derived from measurements in nearby wells.

[0073] In Block 432, reservoir parameters values are assigned to each prospect segment. The reservoir layer selected described in Block 431 are assigned the corresponding parameters values according to the reservoir formation properties like porosity, permeability and net-to-gross ratio (NTG). In one or more embodiments, environmental properties, like temperature and pressure, may be specified. In one or more embodiments, the values may vary across each reservoir layer. In one or more embodiments, the parameters can be assigned as value intervals in a probabilistic manner.

[0074] In Block 433, the reservoir layers are split or partitioned into prospect segments. The reservoir layers described in Block 431 are separated in one or more lateral segments based on lateral within a layer variation of reservoir properties assigned at the previous block, such as, porosity or permeability. In one or more embodiments, the separation is based on sedimentary environment of deposition maps or seismic facies maps. For each prospect segment, a segment gross rock volume (GRV) is calculated. Further, based as net-to-gross ratio (NTG) and porosity a segment net rock volume (NRV) and net pore volume (NPV) are calculated. In one or more embodiments, the GRV, NTG, and porosity, are assigned in a probabilistic manner as interval value distribution. The resulting volumes may be displayed as well as a distribution of values instead of single value.

[0075] In Block 434, the fluid contacts are defined for each prospect segments across the trap envelope. The fluid contact(s) within the trap envelope and within the prospect segments may be defined in order to establish possible oil and gas zones within each prospect segment. Further, based on oil and gas saturation within each zone, the hydrocarbon pore volume (HCPV) is calculated. In one or more embodiments, the contacts may accommodate a transition interval between the contacts. The specification of oil and gas saturation trend may be integrated to calculate the contact's HCPV. The prospect segment fluid contact depth and nature may be selected by specifying the contact(s), from, but not limited to, wells within prospect segment or by direct user input of oil and/or gas column heights known from, but not limited to, nearby analogue wells. In one or more embodiments the fluid contact(s) are derived from parameters, such as top/fault/base seal capillary entry pressure for oil, for gas, type/density of charge fluid (oil, gas), charge amount per prospect segment, per trap envelop, or at a given location(s) within the structural framework model. In one or more embodiments, the fluid contacts level is specified in a probabilistic manner based on a probabilistic model of input parameters.

[0076] In Block 435, the fluid properties are specified in accordance with one or more embodiments. The fluid properties of prospect segment may be further specified (deterministically or probabilistically) in terms of oil and gas formation volume factors, oil and gas recovery factors, gas-oil-ratio (GOR) and condensate-gas-ratio (CGR). The fluid properties may then be used to calculate the un-risked potential in-place and recoverable oil and gas resources. The resources are normally expressed in stock-tank oil initially in- place (STOIIP), gas initially in place (GUP), recoverable oil, solution gas, recoverable gas and condensate oil per prospect segment. [0077] In Block 436, prospects risk is calculated in accordance with one or more embodiments. In one or more embodiments, a risk assessment is performed at prospect segment level. The chance of success for the prospect segment to actually hold the calculated un-risked volumes determined at previous block is estimated in order to calculate risked resources that are un- risked resources weighted by chance of success. This chance of success is broken down into different elements, such as charge, reservoir, seal and trap. This chance of success is broken down into its components such as charge, reservoir, seal and trap. The components are evaluated independently and a composite value may be provided.

[0078] FIG 4.4 shows a flowchart to perform prospect segment combination in accordance with one or more embodiments. In Block 441, prospect resources are assessed. The volumes of hydrocarbons calculated at prospect segment level of the prospect segments that are part of each trap envelop of the structural framework are added together. The results are expressed as prospects or prospect collections summary.

[0079] In Block 442, play resource are assessed. The volumes of hydrocarbons calculated at prospect level of the prospects that have similar characteristics, such as, for example, a common source layer for hydrocarbons, are added together. The results may be expressed as play or basin summary.

[0080] FIG 4.5 shows a flowchart to perform scenario testing and integrated structural framework risk estimates in accordance with one or more embodiments. In Block 451, leak and spill dependencies are determined based on the trap envelop connection map. Based on the trap envelope connections mapped across the structural framework and provided above, one or more inter-segment and inter-trap dependencies are established. The dependencies link the potential spill and leakage paths and the leakages are considered when estimating the prospect segments, the prospects, play or basin. [0081] In Block 452, a geologic scenario is run. In one or more embodiments a geologic scenario is assessing the risked volumes integrated over the prospect by selecting various combination of geologic parameter sets of the structural framework. In one or more embodiments, the risked volumes of hydrocarbon can be calculated based on various reservoir layer thickness, porosity or permeability for example.

[0082] In Block 453, a prospect scenario is run. In one or more embodiments, a prospect scenario is assessing the risked volumes integrated over the prospect by selecting various fluid levels in one or more prospects of the structural framework. In one or more embodiments, the calculations across the trap envelopes are performed in order evaluate the chance of success for each prospect or for the entire play. Further, based on the calculated prospect or play in-place volumes and the trap connection map, a set of risked volumes is calculated by taking into account inter-segment and inter-trap dependencies, such as potential spill and leakage paths as well as consistent correlations both for volumetric and risk parameters.

[0083] In Block 454, a well scenario is run. In one or more embodiments, a well scenario is assessing the risked volumes integrated over the prospect by selecting various fluid levels in one or more prospect segments as determined at various potential well locations within the structural framework. By selecting alternative well locations and assessing the COS of the prospects across the structural framework, a lowest risk or highest reward scenario may be determined for a particular potential well location. The low risk location is selected for development in a field operation.

[0084] Although the above describes running geological scenarios, prospect scenarios, and well scenarios, similar techniques may be used to run other types of scenarios. For example, one or more embodiments may be used to run exploration scenarios. [0085] FIGs. 5.1-5.6 show examples in accordance with one or more embodiments. The following examples are for explanatory purposes and not intended to limit the scope.

[0086] FIG. 5.1 shows an example of a structural framework as a 2D intersection of 3D structural framework. The section shows the structural framework elements including horizon surfaces (511), fault surfaces (512), seal zones (513), reservoir layers (514) and seal surfaces (515).

[0087] FIG. 5.2 shows a trap envelop (520) determined by the crestal point (521) and bounded by the seal surface (522), the fault surface (523) and the base plane (524) selected as the horizontal plane crossing the spill point (525). At the intersection of the fault plane with the seal plane a second spill point is selected (526).

[0088] FIG. 5.3 shows a trap envelop with four prospect segments (531, 532, 533 and 534). In one or more embodiments, the prospect segments may be defined based on a variation of properties of reservoir layers such as the age of deposition, environment of deposition, porosity or permeability.

[0089] FIG. 5.4 shows a set of trap envelops and an example user interface (540). The example user interface includes a displayed hierarchical tree (541) and 3D window (542).

[0090] FIG. 5.5 shows a trap envelop profile with prospect segments and two possible hydrocarbon fluid zones. The reservoir pore space of the zone on top of the envelope (551) is saturated with gas. The gas-to-oil boundary (552) separates the gas zone (551) from the zone below (553) saturated with liquid hydrocarbons (oil). The oil-to-water boundary (554) separates the oil saturated zone (553) from the water saturated zone (555).

[0091] FIG. 5.6 shows a trap envelop profile with prospect segments and two certain hydrocarbon fluid zones. The trap is tested by three exploration wells (560.1, 560.2 and 560.3). The exploration well (560.1) penetrates a saturated gas interval (561) while exploration well (560.2) penetrates a saturated oil interval. The well (560.3) intercepts a water saturated interval. The three tested interval do not overlap at any point. Due to limited extent of the proven intervals, two more zones of uncertainty are identified within the trap envelope. The reservoir pore space of the zone on top of the envelope (561) is considered saturated with gas. Below the saturated gas zone (561), respectively below the proven gas boundary (562), a zone of possible gas or oil is identified (568). The zone below the potential gas-to-oil boundary (566) is considered saturated with oil (563) proven by the exploration well (560.2). Below the proven oil zone (563), and separated by the potential oil-to-water boundary (567), a zone of possible oil or water is identified (569). The proven water boundary (564) separates then the possible oil or water saturated zone (569) from the water saturated zone (565) that was tested by the well (560.3).

[0092] FIG. 5.7 shows a structural framework with crestal points (571), spill points (572) and resulting trap envelopes (573). The spill and leak connections between trap envelops are also illustrated.

[0093] FIG. 6 shows an embodiment of prospect-based scenario testing (600).

In this embodiment, prospect 4 (604) is successful and considered to be filled to spill. Further, as prospect 4 (604) is filled to spill, the likelihood of prospect 3 (603) to be charged is higher (+10% chance of success), therefore increasing its risked mean recoverable oil resources by 18 MMbbl. However, if prospect 4 (604) is filled to spilled, the likelihood of prospect 2 (602) to be charged is lower (-10% chance of success), therefore decreasing its risked mean recoverable oil resources by 6 MMbbl. So if prospect 4 (604) turns out to be filled to spill, the expected value would be around 200 MMbbl, but this also increase the overall value of the undrilled prospects by 12 (18-6) Mmbbl.

[0094] FIG. 7.1 shows a E&P computer system in accordance with one or more embodiments. The E&P computer system (700) may include one or more computer processor(s) (702), associated memory (704) (e.g., random access memory (RAM), cache memory, flash memory, etc.), one or more storage device(s) (706) (e.g., a hard disk, an optical drive such as a compact disk (CD) drive or digital versatile disk (DVD) drive, a flash memory stick, etc.), and numerous other elements and functionalities. The computer processor(s) (702) may be an integrated circuit for processing instructions. For example, the computer processor(s) may be one or more cores, or micro-cores of a processor. The computing system (700) may also include one or more input device(s) (710), such as a touchscreen, keyboard, mouse, microphone, touchpad, electronic pen, or any other type of input device. Further, the computing system (900) may include one or more output device(s) (908), such as a screen {e.g., a liquid crystal display (LCD), a plasma display, touchscreen, cathode ray tube (CRT) monitor, projector, or other display device), a printer, external storage, or any other output device. One or more of the output device(s) may be the same or different from the input device(s). The computing system (700) may be connected to a network (712) (e.g., a local area network (LAN), a wide area network (WAN) such as the Internet, mobile network, or any other type of network) via a network interface connection (not shown). The input and output device(s) may be locally or remotely (e.g., via the network (712)) connected to the computer processor(s) (702), memory (704), and storage device(s) (706). Many different types of computing systems exist, and the aforementioned input and output device(s) may take other forms.

[0095] Software instructions in the form of computer readable program code to perform embodiments may be stored, in whole or in part, temporarily or permanently, on a non-transitory computer readable medium such as a CD, DVD, storage device, a diskette, a tape, flash memory, physical memory, or any other computer readable storage medium. Specifically, the software instructions may correspond to computer readable program code that when executed by a processor(s), is configured to perform embodiments.

[0096] The computing system (700) in FIG. 7.1 may be connected to or be a part of a network. For example, as shown in FIG. 7.2, the network (720) may include multiple nodes (e.g., node X (722), node Y (724)). Each node may correspond to a computing system, such as the computing system shown in FIG. 7.1, or a group of nodes combined may correspond to the computing system shown in FIG. 7.1. By way of an example, embodiments may be implemented on a node of a distributed system that is connected to other nodes. By way of another example, embodiments may be implemented on a distributed computing system having multiple nodes, where each portion may be located on a different node within the distributed computing system. Further, one or more elements of the aforementioned computing system (700) may be located at a remote location and connected to the other elements over a network.

[0097] Although not shown in FIG. 7.2, the node may correspond to a blade in a server chassis that is connected to other nodes via a backplane. By way of another example, the node may correspond to a server in a data center. By way of another example, the node may correspond to a computer processor or micro-core of a computer processor with shared memory and/or resources.

[0098] The nodes (e.g., node X (722), node Y (724)) in the network (720) may be configured to provide services for a client device (726). For example, the nodes may be part of a cloud computing system. The nodes may include functionality to receive requests from the client device (726) and transmit responses to the client device (726). The client device (726) may be a computing system, such as the computing system shown in FIG. 7.1. Further, the client device (726) may include and/or perform at least a portion of one or more embodiments.

[0099] The computing system or group of computing systems described in FIG.

7.1 and 7.2 may include functionality to perform a variety of operations disclosed herein. For example, the computing system(s) may perform communication between processes on the same or different system. A variety of mechanisms, employing some form of active or passive communication, may facilitate the exchange of data between processes on the same device.

Examples representative of these inter-process communications include, but are not limited to, the implementation of a file, a signal, a socket, a message queue, a pipeline, a semaphore, shared memory, message passing, and a memory- mapped file. Further details pertaining to a couple of these non-limiting examples are provided below. ] Based on the client-server networking model, sockets may serve as interfaces or communication channel end-points enabling bidirectional data transfer between processes on the same device. Foremost, following the client- server networking model, a server process (e.g., a process that provides data) may create a first socket object. Next, the server process binds the first socket object, thereby associating the first socket object with a unique name and/or address. After creating and binding the first socket object, the server process then waits and listens for incoming connection requests from one or more client processes (e.g., processes that seek data). At this point, when a client process wishes to obtain data from a server process, the client process starts by creating a second socket object. The client process then proceeds to generate a connection request that includes at least the second socket object and the unique name and/or address associated with the first socket object. The client process then transmits the connection request to the server process. Depending on availability, the server process may accept the connection request, establishing a communication channel with the client process, or the server process, busy in handling other operations, may queue the connection request in a buffer until server process is ready. An established connection informs the client process that communications may commence. In response, the client process may generate a data request specifying the data that the client process wishes to obtain. The data request is subsequently transmitted to the server process. Upon receiving the data request, the server process analyzes the request and gathers the requested data. Finally, the server process then generates a reply including at least the requested data and transmits the reply to the client process. The data may be transferred as datagrams or a stream of characters (e.g., bytes). [00101] Shared memory refers to the allocation of virtual memory space in order to substantiate a mechanism for which data may be communicated and/or accessed by multiple processes. In implementing shared memory, an initializing process first creates a shareable segment in persistent or non- persistent storage. Post creation, the initializing process then mounts the shareable segment, subsequently mapping the shareable segment into the address space associated with the initializing process. Following the mounting, the initializing process proceeds to identify and grant access permission to one or more authorized processes that may also write and read data to and from the shareable segment. Changes made to the data in the shareable segment by one process may immediately affect other processes, which are also linked to the shareable segment. Further, when one of the authorized processes accesses the shareable segment, the shareable segment maps to the address space of that authorized process. Often, one authorized process may mount the shareable segment, other than the initializing process, at any given time.

[00102] Other techniques may be used to share data, such as the various data described in the present application, between processes without departing from the scope. The processes may be part of the same or different application and may execute on the same or different computing system.

[00103] Rather than or in addition to sharing data between processes, the computing system performing one or more embodiments may include functionality to receive data from a user. For example, in one or more embodiments, a user may submit data via a graphical user interface (GUI) on the user device. Data may be submitted via the graphical user interface by a user selecting one or more graphical user interface widgets or inserting text and other data into graphical user interface widgets using a touchpad, a keyboard, a mouse, or any other input device. In response to selecting a particular item, information regarding the particular item may be obtained from persistent or non-persistent storage by the computer processor. Upon selection of the item by the user, the contents of the obtained data regarding the particular item may be displayed on the user device in response to the user's selection.

[00104] By way of another example, a request to obtain data regarding the particular item may be sent to a server operatively connected to the user device through a network. For example, the user may select a uniform resource locator (URL) link within a web client of the user device, thereby initiating a Hypertext Transfer Protocol (HTTP) or other protocol request being sent to the network host associated with the URL. In response to the request, the server may extract the data regarding the particular selected item and send the data to the device that initiated the request. Once the user device has received the data regarding the particular item, the contents of the received data regarding the particular item may be displayed on the user device in response to the user's selection. Further to the above example, the data received from the server after selecting the URL link may provide a web page in Hyper Text Markup Language (HTML) that may be rendered by the web client and displayed on the user device.

[00105] Once data is obtained, such as by using techniques described above or from storage, the computing system, in performing one or more embodiments, may extract one or more data items from the obtained data. For example, the extraction may be performed as follows by the computing system in FIG. 7.1. First, the organizing pattern (e.g., grammar, schema, layout) of the data is determined, which may be based on one or more of the following: position (e.g., bit or column position, Nth token in a data stream, etc.), attribute (where the attribute is associated with one or more values), or a hierarchical/tree structure (consisting of layers of nodes at different levels of detail— such as in nested packet headers or nested document sections). Then, the raw, unprocessed stream of data symbols is parsed, in the context of the organizing pattern, into a stream (or layered structure) of tokens (where each token may have an associated token "type"). [00106] Next, extraction criteria are used to extract one or more data items from the token stream or structure, where the extraction criteria are processed according to the organizing pattern to extract one or more tokens (or nodes from a layered structure). For position-based data, the token(s) at the position(s) identified by the extraction criteria are extracted. For attribute/value-based data, the token(s) and/or node(s) associated with the attribute(s) satisfying the extraction criteria are extracted. For hierarchical/layered data, the token(s) associated with the node(s) matching the extraction criteria are extracted. The extraction criteria may be as simple as an identifier string or may be a query presented to a structured data repository (where the data repository may be organized according to a database schema or data format, such as XML).

[00107] The extracted data may be used for further processing by the computing system. For example, the computing system of FIG. 7.1, while performing one or more embodiments, may perform data comparison. Data comparison may be used to compare two or more data values (e.g., A, B). For example, one or more embodiments may determine whether A > B, A = B, A != B, A < B, etc. The comparison may be performed by submitting A, B, and an opcode specifying an operation related to the comparison into an arithmetic logic unit (ALU) (i.e., circuitry that performs arithmetic and/or bitwise logical operations on the two data values). The ALU outputs the numerical result of the operation and/or one or more status flags related to the numerical result. For example, the status flags may indicate whether the numerical result is a positive number, a negative number, zero, etc. By selecting the proper opcode and then reading the numerical results and/or status flags, the comparison may be executed. For example, in order to determine if A > B, B may be subtracted from A (i.e., A - B), and the status flags may be read to determine if the result is positive (i.e., if A > B, then A - B > 0). In one or more embodiments, B may be considered a threshold, and A is deemed to satisfy the threshold if A = B or if A > B, as determined using the ALU. In one or more embodiments, A and B may be vectors, and comparing A with B is comparing the first element of vector A with the first element of vector B, the second element of vector A with the second element of vector B, etc. In one or more embodiments, if A and B are strings, the binary values of the strings may be compared.

[00108] The computing system in FIG. 7.1 may implement and/or be connected to a data repository. For example, one type of data repository is a database. A database is a collection of information configured for ease of data retrieval, modification, re-organization, and deletion. Database Management System (DBMS) is a software application that provides an interface for users to define, create, query, update, or administer databases.

[00109] The user, or software application, may submit a statement or query into the DBMS. Then the DBMS interprets the statement. The statement may be a select statement to request information, update statement, create statement, delete statement, etc. Moreover, the statement may include parameters that specify data, or data container (database, table, record, column, view, etc.), identifier(s), conditions (comparison operators), functions (e.g. join, full join, count, average, etc.), sort (e.g. ascending, descending), or others. The DBMS may execute the statement. For example, the DBMS may access a memory buffer, a reference or index a file for read, write, deletion, or any combination thereof, for responding to the statement. The DBMS may load the data from persistent or non-persistent storage and perform computations to respond to the query. The DBMS may return the result(s) to the user or software application.

[00110] The computing system of FIG. 7.1 may include functionality to present raw and/or processed data, such as results of comparisons and other processing.

For example, presenting data may be accomplished through various presenting methods. Specifically, data may be presented through a user interface provided by a computing device. The user interface may include a GUI that displays information on a display device, such as a computer monitor or a touchscreen on a handheld computer device. The GUI may include various GUI widgets that organize what data is shown as well as how data is presented to a user. Furthermore, the GUI may present data directly to the user, e.g., data presented as actual data values through text, or rendered by the computing device into a visual representation of the data, such as through visualizing a data model.

[00111] For example, a GUI may first obtain a notification from a software application requesting that a particular data object be presented within the GUI. Next, the GUI may determine a data object type associated with the particular data object, e.g., by obtaining data from a data attribute within the data object that identifies the data object type. Then, the GUI may determine any rules designated for displaying that data object type, e.g., rales specified by a software framework for a data object class or according to any local parameters defined by the GUI for presenting that data object type. Finally, the GUI may obtain data values from the particular data object and render a visual representation of the data values within a display device according to the designated rules for that data object type.

[00112] Data may also be presented through various audio methods. In particular, data may be rendered into an audio format and presented as sound through one or more speakers operably connected to a computing device.

[00113] Data may also be presented to a user through haptic methods. For example, haptic methods may include vibrations or other physical signals generated by the computing system. For example, data may be presented to a user using a vibration generated by a handheld computer device with a predefined duration and intensity of the vibration to communicate the data.

[00114] The above description of functions present a few examples of functions perfomed by the computing system of FIG. 7.1 and the nodes and/ or client device in FIG. 7.2. Other functions may be performed using one or more embodiments.

[00115] Although the preceding description has been described herein with reference to particular means, materials, and embodiments, it is not intended to be limited to the particular disclosed herein. By way of further example, embodiments may be utilized in conjunction with a handheld system (i.e., a phone, wrist or forearm mounted computer, tablet, or other handheld device), portable system (i.e., a laptop or portable computing system), a fixed computing system (i.e., a desktop, server, cluster, or high performance computing system), or across a network (i.e., a cloud-based system). As such, embodiments extend to all functionally equivalent structures, methods, uses, program products, and compositions as are within the scope of the appended claims. While a limited number of embodiments have been described, those skilled in the art, having benefit of this disclosure, will appreciate that other embodiments can be devised which do not depart from the scope as disclosed herein. Accordingly, the scope should be limited by the attached claims.

Claims

CLAIMS What is claimed is:

1. A method for managing traps comprising:

obtaining a structural framework of a subsurface domain, the structural framework representing a plurality of geologic surfaces of the subsurface domain;

identifying a plurality of structural spill points and a plurality of crestal points for the subsurface domain based at least in part on the structural framework;

detecting, using the structural framework, a plurality of trap envelopes based at least in part on at least a portion of the plurality of structural spill points and the plurality of crestal points;

performing a spatial assessment of the subterranean formation based on the plurality of trap envelopes; and

conducting a field operation based on the spatial assessment.

2. The method of claim 1, further comprising:

performing a split of the trap envelopes into a plurality of prospect segments; and

assigning a plurality of reservoir properties to each prospect segment in the subsurface domain.

3. The method of claim 2, wherein the spatial assessment comprises:

identifying a dependency between at least two prospect segments of the plurality of prospect segments; and

performing a volume calculation based on the dependency.

4. The method of claim 2, wherein the split is performed based on at least one selected from a group consisting of a vertical stratigraphic variation and a lateral facies variation of the plurality of reservoir properties.

5. The method of claim 2, further comprising:

defining a fluid contact within each prospect segment of the plurality of prospect segments.

6. The method of claim 5, wherein the fluid contact is determined based on an indirect method using geometry of the prospect segment and an amount of fluid available.

7. The method of claim 5, further comprising:

specifying a fluid property for a fluid within a prospect segment of the plurality of prospect segments.

8. The method of claim 1, wherein the spatial assessment comprises:

identifying a dependency between at least two trap envelopes of the plurality of trap envelopes; and

performing a volume calculation based on the dependency.

9. The method of claim 1, wherein performing a field operation comprises generating a drilling plan based on the spatial analysis.

10. A system for managing traps comprising:

a computer processor; and

memory storing instructions, which, when executed on the computer processor, cause the computer processor to:

obtain a structural framework of a subsurface domain, the structural framework representing a plurality of geologic surfaces of the subsurface domain;

identify a plurality of structural spill points and a plurality of crestal points for the subsurface domain based at least in part on the structural framework; detect, using the structural framework, a plurality of trap envelopes based at least in part on at least a portion of the plurality of structural spill points and the plurality of crestal points;

perform a spatial assessment of the subterranean formation based on the plurality of trap envelopes; and

conduct a field operation based on the spatial assessment.

11. The system of claim 10, wherein the instructions further cause the computer processor to:

perform a split of the trap envelopes into a plurality of prospect segments; and assign a plurality of reservoir properties to each prospect segment in the subsurface domain.

12. The system of claim 11, wherein the spatial assessment comprises:

identifying a dependency between at least two prospect segments of the plurality of prospect segments; and

performing a volume calculation based on the dependency.

13. The system of claim 11, wherein the split is performed based on at least one selected from a group consisting of a vertical stratigraphic variation and a lateral facies variation of the plurality of reservoir properties.

14. The system of claim 1, wherein the spatial assessment comprises:

identifying a dependency between at least two trap envelopes of the plurality of trap envelopes; and

performing a volume calculation based on the dependency.

15. A computer program product comprising computer program code to carry out the method according to any of claims 1-9.