Reservoir software and data services

Reservoir software supports interpretation, modelling and evaluation of subsurface data. Related data services organize or analyze inputs and produce agreed study outputs. Licensing a software product differs from commissioning a specialist interpretation service.

Typical applications

Exploration, development planning and reservoir management use these tools and services. Available datasets and the technical question determine the required workflow.

Licensing and deployment options

Specify the software product, version and license requirement, or a separate service scope and deliverables. Data ownership and interoperability should be explicit.

Keep the data baseline separate from the interpretation

Start with a controlled input register so the reviewer can identify which records underlie each model or report. Mark missing coverage, uncertain units and revisions that have not been reconciled. Ask for changes made during preparation to be recorded rather than silently replacing the original inputs. This gives the owner a practical way to compare a returned dataset with the material supplied and to decide whether unresolved gaps need additional work.

Set review stages for the study's assumptions and outputs. An interpretable model can still depend on limited data or choices that need project approval. Ask the proposal to explain how those limitations will be presented and who accepts them. Avoid treating the purchase of a recognised application, or a visually persuasive model, as confirmation of reservoir performance or a reserve estimate. Those conclusions belong to the defined technical study and its responsible reviewers.

Test the required model exchange rather than a format name

An exchange standard such as RESQML addresses earth and reservoir modelling data between applications. The enquiry should still name the required version, objects and receiving workflow. Ask which parts of the project model can be transferred and what is omitted or converted. Version-specific documentation and a representative sample are more useful than a general statement that an application supports an industry standard.

Agree the checks for the exchanged result before work starts. Examples may include the expected geometry, property units, object identifiers and links to the supporting data relevant to the assignment. The buyer's technical team should determine which checks are appropriate; successful import alone does not demonstrate complete preservation of the intended model. Record warnings and unsupported content, and keep any approved simplifications visible in the delivered exchange report.

Make the final study usable beyond the initial demonstration

Specify the delivery folder structure, file formats, version register and explanatory notes needed for the owner's next workflow. Distinguish editable project files from read-only reports and exports. Identify continuing access or support dependencies and the terms governing reuse of developed material. Training or later model updates should be separately described when they are outside the initial assignment. Send the defined scope to Oillinko for manual review and coordination, with confidential datasets shared only through the agreed project channel.

Technical objective

Identify the subsurface question and the decision the work should support. Distinguish interpretation, geological modelling, simulation input preparation and a software purchase, because each has different inputs and acceptance records. Describe the asset or study area through the approved project brief and state which assumptions the technical team has already established. Ask the response to separate data preparation, specialist interpretation and application configuration. A software license supplies defined usage rights; it does not automatically include a reservoir study or validate its conclusions. Where the objective remains exploratory, request a bounded assessment phase with identified outputs before commissioning a larger modelling scope.

Available datasets

Provide a dataset inventory that identifies source, coverage, revision, format and the rights available for the proposed use. Include the relevant well, log, seismic, geological and production inputs only where they apply to the study. State units, coordinate references and known quality limitations. A file being available does not establish that its content is complete or suitable for the intended modelling task. Use representative anonymized samples for an initial compatibility review when authorized. Keep confidential field data within the agreed access arrangements, and ask the proposal to distinguish cleaning or conversion work from interpretation of the underlying measurements.

Software environment

List the applications and versions that create, process and receive the study data. State the required import and export formats and any exchange-standard version specified by the project. Support for a format family does not prove that every object or version needed by the workflow is handled. Ask for a compatibility statement against the actual source and destination applications and a representative exchange check. Identify computing, storage and deployment assumptions separately from software rights. Account credentials, activation files and unrestricted project databases are not required in a general enquiry; approved access is arranged through the owner's controlled project process.

Deliverables and license scope

Describe the outputs the owner must receive: source or edited datasets, model files, interpretation reports, assumptions, quality findings and any reproducibility records appropriate to the assignment. State which editable files are required and who will review the study. For software, identify edition, modules, user quantities, term, deployment and support coverage. For a service, define review stages, included revisions and the handover format independently of the license quotation. Ask how developed material and third-party data may be used after completion under the proposed agreement. Technical conclusions, usage rights and a successful file exchange are separate matters that require their own evidence.

How related requirements differ

Seismic and geophysical equipment: Seismic and geophysical equipment records measurements used to investigate subsurface conditions. Sensors, acquisition units and positioning equipment form systems selected for the survey method and required resolution. Sensor type, channel count, timing, positioning and data compatibility distinguish configurations. Equipment supply should be separated from acquisition crews and interpretation services.

Formation evaluation and logging tools: Formation-evaluation and logging tools measure selected rock, fluid or well properties. The measurement principle and conveyance arrangement determine what information can be collected under the specified borehole conditions. Open-hole and cased-hole tools address different conditions. Specify measurements, conveyance, hole geometry, pressure, temperature and compatibility with the acquisition system.

Core and fluid sampling equipment: Core and fluid sampling equipment collects and preserves material for analysis. The sampling method and container design influence whether the sample retains the properties relevant to the intended test. Core-handling accessories, pressure-preserving fluid samplers and ordinary containers serve different purposes. State sample type, conditions, materials and the required handling chain.

Compare licensing and support terms

For reservoir software and data services, compare the product edition, number of users, permitted deployment and support period. A license quotation may not include configuration, data migration, training or implementation services. Identify existing entitlements and the required renewal terms without sharing activation keys or account credentials. Software usage rights and support arrangements should be confirmed in the proposed license terms. Oillinko reviews the requirement and coordinates the enquiry; inclusion in the catalogue does not imply a software partnership or reseller appointment.

Questions before requesting a quotation

What information should be available first? Start with the intended application and the current technical specification for reservoir software and data services. In this category, the initial review includes technical objective, available datasets, software environment, deliverables and license scope. Attach the relevant drawings or scope documents and identify any information still awaiting confirmation. This makes it possible to distinguish a preliminary enquiry from a fully defined purchasing or service requirement.

Can a similar software name be treated as the same product? No. Edition, version, licensing model and permitted deployment can change the functionality or usage rights. An alternative should be evaluated against the required workflow and interfaces, with its commercial terms made explicit. Support and implementation responsibilities should be agreed separately where they are not included in the license proposal.