Object-Relational Mapping API for Oilfield Data

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current oilfield data management systems lack the ability to automatically generate an object-oriented application programming interface (API) that allows for seamless access to oilfield data stored in various formats, leading to inefficiencies in data retrieval and manipulation, particularly when dealing with large datasets and frequent queries.

Innovation Solution

A method and system that utilize a computer-implemented approach to form an application programming interface (API) by obtaining structural descriptions of data entities, domain models, and mapping specifications, enabling the creation of an object-oriented API that maps relational data to an object view, allowing for efficient access and manipulation of oilfield data across different data repositories.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional data repositories are used to store oilfield data, then data storage capacity is sufficient, but data retrieval efficiency deteriorates due to frequent queries and large datasets

Engineering Contradiction:

Improvedata retrieval efficiencyVSAvoidquery overhead time

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The patent introduces an object-relational mapping layer as an intermediary between the relational database and object-oriented applications. This mapping layer automatically translates object-oriented queries into efficient relational database queries, eliminating the need for manual query optimization and reducing query overhead time while maintaining fast data retrieval.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces manual query writing and optimization processes with an automated code generation system. The system automatically generates object-oriented API code from domain models and relational schema, substituting the mechanical process of manual query construction with automated translation, thereby improving productivity and reducing time loss.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

2Productivity

If manual code generation is used to create API interfaces, then flexibility is maintained, but development time increases and productivity decreases

Engineering Contradiction:

ImproveAPI development speedVSAvoidcode generation time

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The patent performs preliminary actions by defining domain models and relational schemas before actual API development. These models serve as templates that automatically generate the entire API layer, including all necessary code, reducing development time from weeks to minutes while maintaining full flexibility.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent substitutes manual code writing with an automated code generation system that takes domain models and relational schemas as input and produces complete object-oriented API code. This mechanical substitution eliminates repetitive manual coding tasks, dramatically increasing productivity and reducing development time.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

3Ease of operation

If relational databases are used to store data, then data structure is well-defined, but access to data becomes complex when needing object-oriented interfaces

Engineering Contradiction:

Improveobject-oriented data accessVSAvoiddata access layer complexity

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces an object-relational mapping layer as an intermediary that translates between relational database structures and object-oriented interfaces. This layer automatically handles the complexity of mapping relationships, allowing users to access data through simple object-oriented code while the underlying relational database maintains its structured integrity.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a universal mapping framework that can handle multiple data sources, relationships, and query patterns through a single object-relational mapping layer. This multi-functional approach simplifies data access by providing a unified interface that works for all types of queries and data retrieval operations, reducing overall system complexity.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS7895241B2Method and apparatus for oilfield data repository

Publication Date: 2011.02.22 SCHLUMBERGER TECH CORP

AI summary

The invention relates to a method for performing operations of an oilfield having at least one wellsite, a surface network, and a process facility, each wellsite having a wellbore penetrating a subterranean formation for extracting fluid from an underground reservoir therein. The method includes storing oilfield data associated with a plurality of oilfield entities in a first data repository, obtaining a first target metamodel comprising structural description of a first plurality of data entities of the first data repository, obtaining a domain metamodel interleaved with a first mapping specification, the domain metamodel comprising structural description of a domain model for representing the plurality of oilfield entities in an application programming interface, obtaining a mapping specification associating the first target metamodel with the domain metamodel and forming the application programming interface based on the domain metamodel, the first target metamodel, and the first mapping specification using a computer implemented method.