Things you can do with JewelSuite Subsurface Modeling

You can import a wide variety of reservoir data, including many commonly used formats for which streamlined importing processes have been developed. When importing seismic data and/or seismic interpretation data in the time domain, time/depth conversion can be performed using the available domain conversion tools. You can access databases, to connect to or to import multiple well data files from applications commonly used in the industry. You can also export data in many formats to reuse in other applications. For details on exactly what files you can import and export, see File formats for importing and exporting data.

Data interpretations are organized in event types, where events describe a boundary. This can be a stratigraphic, a structural or a fluid boundary. An event can contain one or more graphical representations, e.g. markers and tri-meshes. Before you use your data as input for any model, you must organize your data in a ‘data container’. Such a data container can either be a seismic interpretation, or a surface set. Working with data containers ensures data consistency throughout the modeling workflow. You can assign events from alternative sources. The work from people working in multiple disciplines comes together in the stratigraphic model, where all disciplines should be aligned on how their data will be incorporated into the geological model.

The stratigraphic model links the stratigraphy of the units defined in the model area to the available data describing the bounding surfaces between those units. The stratigraphic model uses hierarchy in the form of stratigraphic levels. Hierarchical levels in the stratigraphic model support the lithostratigraphic concept commonly known as the Group-Formation-Member relationship. The hierarchical concept has great advantages during various modeling stages:

• Stratigraphy is hierarchical, which can be reflected in the stratigraphic model. Higher order units constrain the lower order units during construction of the internal zonation of the 3D geological model.
• Well correlation is more robust; lower order units are typically identified during (local) well correlation and can be placed in the context of higher order seismic (regional).
• Interpretations; structural modeling can be performed in stages: higher order stratigraphic units (seismic resolution scale) can be created first, allowing early QC steps and giving control over data resolution, before adding more detail in the form of flow simulation models.

You can quickly and easily correlate wells based on well log data. Correlated wells can be used to map surfaces throughout the reservoir to create a fine-scaled and accurate representation of geological features. Surface intersections can be calculated between wells and surfaces to compare the intersections with the available log data. You can easily correct mismatches with the well matching functionality to ensure full consistency between wells, surfaces and log data.

You can build a 3D structural model based on a fault model in combination with the well markers and the vertical zonation defined in the stratigraphic model. Structural modeling can be performed in stages, with higher order units modeled first, allowing QC steps to be performed at an early stage. Advanced automated and manual editing tools help you quickly clean-up the structural surfaces to produce a structural model. Different stratigraphic and fault models can be combined to create multiple structural model scenarios, which can serve as the input for building geological reservoir models.

The application uses the advanced JewelGrid system to create a geological model that honors the complete structural framework you have created, including complex geological features such as y-faults, x-faults, stacked faults, intrusions, and unconformities. This geocellular JewelGrid offers a simpler alternative to the pillar grid and UVT Grid approaches. The JewelGrid is a structured rectangular grid with vertical cell stacks. The grid is locally unstructured where faults pass through these vertical cell stacks and cells are split exactly where intersected by interpreted faults. Thus, there are virtually no restrictions with respect to geometry and topology.

You can build a geomechanical model which you can map to a 3D mesh which you can also generate in the application. This 3D mesh can serve as input to geomechanical simulation with, for instance, Abaqus. Another workflow allows you to create geomechanical properties on a 3D grid. A 3D grid with geomechanical properties can be used, for example as input to fault stability calculations, for which another workflow is provided.

Various ways of populating the reservoir model, surfaces, and wells with properties, such as porosity, permeability, and saturation, are available. You can create properties using Property Modeling methods in which petrophysical well log data is used as interpolation or simulation input. You can also use the built-in Property Calculator or the Function Tool to create or modify properties.

The JewelScript Editor enables you to create automated scripts, referred to as JewelScripts, that can be used for workflow automation. With the editor you can create reusable JewelScripts that combine the modeling workflows along with the available tools.

You can calculate fault transmissibility multipliers based on fault properties (such as clay content, fault displacement and fault permeability) or create a fault transmissibility multiplier matrix in which you can directly enter fault transmissibility multipliers on a zone-to-zone and/or fault basis. Both types of 'transmissibility multiplier models' can be selected as input during reservoir simulation.

You can perform volumetric uncertainty calculations, incorporating parametric uncertainties in the form of probability density functions that you assign to various modeling parameters in the domain models. Alternative domain models can subsequently be defined in so-called 'volumetric scenarios' that form the input to the volumetric uncertainty calculations. Via multiple volumetric concepts within one scenario, you can incorporate conceptual uncertainties in your calculations.

For all simulators, a full set of pre- and post-processing tools is available to set up your reservoir simulation cases interactively. You can define and run multiple reservoir simulation cases simultaneously on a distributed grid of servers using .NET-based Microsoft Windows™ Services. Results are immediately available for analysis during and after the completion of simulation runs. You can animate time-dependent grid properties in 2D or 3D views. You can compare well production results from multiple cases using the advanced charting capability. All data from the complete workflow is available for comparison at any time. You can also set up and connect to simulation clusters using Microsoft's HPC cluster support.

You can plan well trajectories, both vertical and deviated, through your reservoir models. Using the graphical tools or workflows, you can create single well plans or well pad plans. Based on pre-defined parameters such as well spacing, horizontal length, azimuth, etc, well pad plans can be automatically and accurately placed and updated. Smart target zone design for both single or multiple zones allows for easy placing of the well trajectories in the desired locations. Using these planned wells in the reservoir simulation you can determine the most optimal or suitable locations to drill new wells. You can copy reports to the clipboard and use the information to further analyze and customize the data.

With DMS, all data and projects are centralized in one auditable environment, providing a single source of truth. As opposed to working in a single solution, DMS enables worldwide collaboration between teams from different assets and disciplines and allows for sharing data at all stages of the project, i.e. input data, intermediate results and final modeling results. Multiple users can track and download the updates on specific domain models. With the DMS user-level security settings, the access level of each user to the data, and the actions each user can perform, is secured.