Agents & MCP API and MCP Integrations Available

Din digitale arbeidsbenk for olje- og gassløsninger

Avanserte stangpumpedesign. Effektivt samarbeid via en suite med digitale verktøy. PetroBench leverer den komplette livssyklusløsningen med bransjeledende nøyaktighet og intelligens.

Be om demo Utforsk plattform

Integrerer med:

Design

Skybasert stangpumpedesign

RodSim

RodSim erstatter manuelle designarbeidsflyter for stangpumpe med automatiserte beregninger, bulkdataimport og direkte enterprise-dataintegrasjon. Ingeniører samarbeider i sanntid på tvers av regioner om delte brønndesign og analyser.

Utforsk RodSim

0:00 / 0:00

Ingeniørsamarbeid

Støtter samtidige ingeniører på tvers av flere regioner og grupper

Bulkdataintegrasjon

Importer og analyser brønndata med integrert databehandling

Brønnnøyaktighet

Kubisk spline-interpolasjon sikrer presis brønnrepresentasjon og nøyaktige resultater

Rask og skalerbar ytelse

Høyytelsessimuleringer bygget for enterprise-skala operasjoner

Komplett Livssyklusløsning

Design smart. Optimaliser kontinuerlig.

Design optimaliserte stangpumpesystemer med bransjeledende simuleringsnøyaktighet. Overvåk og optimaliser produksjonsytelse gjennom hele brønnens livssyklus.

PetroBench-plattformen

Skyplattformfundament og infrastruktur for ingeniører, IT-direktører, ledere og administratorer

Brønnstyring

Samlet brønndatabase og kontroll

Brukerstyring

Rollebasert tilgangskontroll

Selskapsstyring

Bedriftsinnstillinger og drift

Event Hub

Koble til enterprise-systemer

Datalager

Sentralisert datalagring

SSO-integrasjon

Single Sign-On integrasjon

Multi-Tenancy

Sikker isolasjon for forretningsenheter

Massehandlinger

Masseoppdatering/import/eksport

Sikkerhet og revisjon

Samsvar og overvåking

Arbeidsflytorkestrering

Automatisering av forretningsprosesser

Varslingssenter

Sanntidsvarsler og oppdateringer

Kommentarer og annotering

Kontekstuelle diskusjoner om brønner

Utforsk plattform

New Agents

Vector

Engineers Click. Agents Call

Agents call the same RodSim engine your engineers already run. Vector stays on the open well, sims and reads through the engine, writes behind guardrails with a full audit trail.

Request Demo Explore MCP

Capabilities

Run Simulation

Rod-pump dynamics, wellbore mechanics, and production scenarios on the same cubic-spline engine.

Same engine

Draft Changes

Propose SPM and string overrides behind write guardrails. Engineers approve before anything touches the well.

Queued for review

Inspect Results

Compare results against baseline envelopes in your workspace, engineer pull, not passive monitoring.

Workspace pull

Works with

Same engine from chat or click

Run a sim, draft a change, and keep the record on the well.

Ask Vector, or click Run in the workspace. Both hit the same RodSim engine on the well you have open.

Drafts sit behind write guardrails. Nothing hits the live well until an engineer signs off.

Inputs and outputs land on the well record. Open the run later and see what RodSim returned.

Well Assistant

Hi John.

Diagnose individual wells, run sims, interpret dyno cards.

Uses your org wells and sims.

Well Assistant

Hi John.

Diagnose individual wells, run sims, interpret dyno cards.

Uses your org wells and sims.

Well Assistant

Hi John.

Diagnose individual wells, run sims, interpret dyno cards.

Uses your org wells and sims.

Surfaces Vector, MCP, REST

Work the Same Wells Your Way

Chat in PetroBench, bring your AI tools, or connect company systems. Every path runs the same simulations.

Vector

Chat on the well already open in your workspace. Sims and designs stay with the team.

See Vector

MCP

Bring Claude, Cursor, or MCP clients to the same wells without leaving those tools.

See MCP

REST

Plug PetroBench into the systems your company already runs day to day.

See REST

Request Demo

Built for Your Organization

Three Roles. One Workspace

Engineers design. Operations review. IT connects the stack. Same wells and permissions for all three.

Production Engineers

Design and Simulate in the Browser

Import wells, run RodSim, and compare designs. Every simulation stays versioned.

Import wells and files
Run cloud simulations
Version history

See engineers

Operations Teams

Review the Same Well

Dyno cards and designs on one well record. Vector can inspect; writes need engineer approval.

Shared well record
Drift visible in workspace
Writes need signoff

See operations

IT and Security

Connect SSO. Keep Data Yours

SSO with SAML or OIDC. Connect Snowflake, Databricks, Azure, AWS, or WellView. Audit log on every action.

SSO and role-based access
Native data connectors
Full audit log

See IT path

Dataintegrasjon

Koble dine data lakes og eldre systemer

Koble dine data lakes og eldre systemer til PetroBench for sanntidsdata i hver simulering.

RSDX RodStar design

RSVX RodStar vertical

INP6E SRod input

XLSX Spreadsheet

Import av eldre data

Importer brønnfiler og historiske data fra eldre verktøy med enkelimport eller vår bulkimportmodul.

Snowflake

Databricks

Azure

AWS

WellView

REST API

Enterprise-dataintegrasjon

Native tilkoblinger til Snowflake, Databricks, Azure, AWS og WellView for sømløs datasynkronisering med din eksisterende infrastruktur.

Les mer om dataintegrasjon Utforsk plattform

FAQ Common Questions

Questions Operators Ask

Answers before you book a walkthrough.

When we click Run, do all engineers hit the same RodSim engine?

Yes. RodSim runs in the shared workspace, not on one laptop. The same well opens the same way for every engineer on the team.

Can we keep our desktop rod-lift tool running during a pilot?

Yes. Run the same wells in PetroBench next to your current desktop tool. Engineers compare numbers on wells they already know before the team moves the well of record into the workspace.

Can we import RodStar, SRod, and existing well files?

Yes. Bulk import brings in the common legacy formats so well files and rod strings come across without rebuilding.

Can Snowflake, Databricks, or WellView feed the workspace?

Yes. Native connectors pull wells, surveys, and production data into PetroBench. File import stays available when a connector is not the path.

Do designs live on one well record, or do we still pass files around?

Designs live on the well. Anyone with access opens that well and sees the same runs and the recommended design.

How do we pick a recommended design when we have run more than one case?

Compare up to five designs side by side on the well. Pick the base case from that view. That recommended design stays on the well for the team.

Who can open a well, the engineer's region, or the whole company?

Access follows your org tree and roles. An engineer opens the wells their region and permissions already allow. The workspace does not widen that view.

What does a successful pilot look like before we roll out further?

Most teams import a set of wells they already know, run those in the workspace, compare side by side with their current tool, then widen regions once the team is comfortable.

Do we all design against the same pumping units and rods?

Yes. Headquarters publishes equipment libraries and templates. Divisions and regions inherit those so every engineer designs against the same catalog.

Once we pick a recommended design, where does operations find it?

On the well. Operations opens that well and sees the base case. The next engineer on that well starts from that version.

Se hvordan det transformerer arbeidsflyten din

Se PetroBench-plattformen i aksjon for ditt selskap. Vi demonstrerer hvordan våre skybaserte verktøy optimaliserer dine ingeniørarbeidsflyter for stangpumpe.

Live simuleringsdemo

Dine brønndata

Ingeniørteam

Har du spørsmål eller trenger hjelp med noe annet? Ta kontakt