Import
Bring legacy RodStar and SRod files or lake data into the workspace. Rod string and well data load without re-entry.
Engineers For Engineers
Design on the Same Well
Import the survey, run RodSim, compare up to five designs, and pick the base case, one well record for the team.
Workflow Familiar Path, Cloud Workspace
Import, Simulate, Compare, Issue
The same steps your engineers run today, in a versioned workspace every teammate opens the same way.
RodSim Design Workspace
RodSim Well Data In, Designs Out
Import the survey, run RodSim in under 30 seconds, and pick the base case on the shared well
Cubic spline wellbore, step length to 10 ft
Compare up to five designs, set the base case
Bulk import from legacy files or the lake
RodSim How the Design Runs
Built for Wells You Already Design
Deviated surveys, side-by-side cases, and a run fast enough to iterate in the meeting
Survey step to 10 ft
Match step length to the survey so tight turns stay in the model
Cubic spline wellbore
Loads follow the survey you brought in, not a coarse polyline
Five designs side by side
Compare cases in one view and pick the base case
Platform One Workspace
Every Product Opens the Same Well
RodSim, Dynamics, and Automated Design share wells, company context, and equipment libraries
Collaborate Beyond the Desktop
Design Together, Not Alone
Desktop tools fit one engineer at a desk. PetroBench adds share, comment, and review on the same well.
Share with group or region
Recommended designs go to the team that owns the well
Comments on designs
Notes stay on the well record for the next engineer
Shared workspace
Same well, same designs, no conflicting file copies
Group / Region share Vector Optional Agent Help
Agent Help on the Open Well
Vector reads, simulates, and drafts on the same well record in RodSim. Live-well writes stay behind guardrails until you approve
Reads and sims on the well you have open
Same rod-lift engine as RodSim
Live-well writes queue for engineer review
Well Assistant
FAQ For Engineers
Questions Engineers Ask First
What production engineers ask before a pilot.
PetroBench keeps the workflow your engineers already know: import, simulate, compare, and pick the base case. Designs live on a shared well record with version history, the same well opens the same way for every engineer on the team.
During pilot, engineers run the same wells side by side in PetroBench and your desktop tool. Inputs and outputs stay on the well record so the team compares what they already know before they commit.
Yes. Bulk import handles the common legacy formats so existing well files and rod strings come in without rebuilding. Native connectors to Snowflake, Databricks, and WellView keep the rest of the data flowing.
Yes. Pilots run side by side with your current desktop workflow. Engineers compare the same wells in both tools before the team commits to PetroBench as the design workspace.
Each simulation and recommended design stays on the well record with its inputs and outputs. Engineers open prior versions, compare side by side, and see who changed what, without hunting email attachments.
RodSim compares up to five designs side by side on the same well. Pick the base case from that view. That recommended design stays on the well for the team.
Access follows your org tree, headquarters, division, region, and group. Role-based permissions scope which wells an engineer opens and which actions they can take.
Yes. Headquarters publishes equipment libraries, unit systems, and templates. Divisions and regions inherit those so every engineer designs against the same catalog.
No. Vector is optional agent help on the open well. Engineers design and simulate in RodSim without it. When Vector is enabled, live-well writes stay behind approval.
Yes. Set the base case and export the report from the well record. The recommended design stays in the workspace so operations and the next engineer open the same version.
See RodSim on One of Your Wells
Start with a well you already design. Import it, run RodSim, compare side by side, and pick the base case.