Reserve Estimate Serialization for Accurate 3D Volume Calculation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional methods for calculating reserve estimates in reservoir models are inadequate, particularly for complex geometries like fault blocks and salt bodies, as they fail to provide accurate three-dimensional visual representations and geologic volume definitions.

Innovation Solution

Converting reserve estimates into a standard format by serializing them with a sealed triangulated mesh and thickness grid, compressing the data into a byte array, and storing it as a printable string in Processing History fields, linked to a 3D modeling engine with predefined identification properties.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If traditional volumetric calculations are used, then the calculation process is simple, but the accuracy of geologic volume definition is poor

Engineering Contradiction:
Improveaccuracy of geologic volume definitionVSAvoidcomplexity of calculation framework
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The reservoir model is divided into discrete grid blocks that are processed individually through serialization and compression algorithms, allowing complex geometries to be handled through systematic segmentation of the computational domain

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent transforms reserve estimates from traditional volumetric parameters into a standardized format using serialization and compression techniques, changing the data representation parameters to enable accurate storage and retrieval of complex geometric information

Inventive Principle:
Principle #35Parameter changes

2Measurement precision

If grid-based volumetric calculations are used, then the methodology is straightforward, but the three-dimensional visual representation is inaccurate

Engineering Contradiction:
Improveaccuracy of three-dimensional visual representationVSAvoidease of gaining accurate visual representation
Core Design Contradiction:
Measurement precisionVSEase of operation

Solution Approach 1:

The patent creates a standardized copy of reserve estimate data in a compressed byte array format that can be stored and retrieved, allowing accurate reproduction of three-dimensional geometric information without requiring complex real-time calculations

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent transitions from traditional two-dimensional grid-based volume calculations to three-dimensional visual representations by serializing data that includes spatial coordinates and geometric information across multiple dimensions

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Measurement precision

If geocellular-based volume calculations are used, then the approach is more detailed, but the volume definition remains inaccurate due to stair-stepped geometry

Engineering Contradiction:
Improveaccuracy of volume definitionVSAvoidcomplexity of geometry representation
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent changes the geometric representation parameters from stair-stepped approximations to precise three-dimensional coordinates stored in the standardized format, enabling accurate volume calculation for complex geometries like fault blocks and salt bodies

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10430998B2Converting reserve estimates in a reservoir model to a standard format for dynamic comparison
Publication Date: 2019.10.01 LANDMARK GRAPHICS CORP
  • US10430998B2 patent drawing
  • US10430998B2 patent drawing
  • US10430998B2 patent drawing

AI summary

Systems and methods for converting reserve estimates in a reservoir model to a standard format for dynamic comparison by storing them with a sealed triangulated mesh and a thickness grid as a printable string in one or more Processing History fields.