Drill String Depth Range Manager for Multi-Scenario Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing drilling operation modeling and analysis software typically operates on a single analysis basis, discarding previous results and requiring users to reenter parameters to compare changes in operational parameters, limiting the ability to manage and view multiple instances of modeling and analysis simultaneously.

Innovation Solution

A computer-implemented method and system that allows users to run and retain multiple models and analyses within a given session, using a flexible database structure to store operational parameters for different drilling depth or time ranges, enabling easy comparison and retention of results through a graphical interface.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If existing drilling operation modeling software operates on a single analysis basis, then the software structure remains simple, but the user cannot retain or compare multiple analysis results simultaneously

Engineering Contradiction:
Improveability to manage multiple analysesVSAvoidsoftware structure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The software divides the analysis management function into separate modular components: a database module for storing multiple analyses, a display module for presenting results, and a control module for managing operations. This segmentation allows the system to handle multiple analyses without creating a monolithic complex structure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A database is introduced as an intermediary component between the user interface and the analysis calculations. The database stores multiple analysis results and operational parameters, enabling the software to retain and compare previous analyses without complicating the core calculation logic.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If the software discards previous analysis results, then the software remains simple to operate, but the user cannot easily review or compare past analyses

Engineering Contradiction:
Improveretention of analysis resultsVSAvoiduser operation simplicity
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The software automatically stores previous analysis results in the database during each analysis run, before the user needs to review them. This preliminary action of saving results eliminates the need for users to manually retrieve or reconstruct past analyses, maintaining ease of operation while preventing information loss.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The software provides feedback to users by displaying stored analysis results and allowing navigation between different analyses. Users can review previous results without restarting the analysis process, and the system responds to user actions by retrieving appropriate historical data from the database.

Inventive Principle:
Principle #23Feedback

3Productivity

If the user must reenter operational parameters to rerun analyses, then the software structure remains simple, but the user cannot easily compare the impact of parameter changes

Engineering Contradiction:
Improveanalysis comparison efficiencyVSAvoidparameter management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The software creates copies of operational parameters and analysis results in the database for each analysis run. Users can access these copies to compare how parameter changes affected results without needing to reenter original parameters, significantly improving comparison efficiency while managing complexity through structured data storage.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The database structure is designed to store multiple types of operational parameters and analysis results in a unified manner. This universal storage approach allows the software to handle various parameter types and analysis scenarios using the same underlying structure, improving productivity without proportionally increasing complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Adaptability or versatility

If the software allows multiple analyses to be retained, then the user can compare different drilling scenarios, but the database structure becomes more complex

Engineering Contradiction:
Improvemulti-scenario analysis capabilityVSAvoiddatabase structure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The database is segmented into distinct tables or sections for storing different types of information: operational parameters, analysis results, and metadata. This segmentation organizes the complexity by separating data types, making the database structure more manageable while enabling robust multi-scenario analysis capabilities.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10240450B2Depth range manager for drill string analysis
Publication Date: 2019.03.26 LANDMARK GRAPHICS CORP
  • US10240450B2 patent drawing
  • US10240450B2 patent drawing
  • US10240450B2 patent drawing

AI summary

A depth range manager provide users with a way to run and retain multiple depth range analyzes for a drill string operation, including the operational parameters for each analysis. This allows users easily to view and compare the analyzes at the different drilling depth ranges. In some embodiments, instead of drilling depth ranges, users may also urn and retain multiple different models and analyzes using multiple different drilling times. The operational parameters for the multiple different models and analyzes may be defined and stored using a flexible one-to-many database structure that accommodates the different sets of operational parameters as well as any existing single-analysis parameters associated with legacy analyzes. A graphical interface allows users easily to define and store the operational parameters in the flexible one-to-many database structure.