A production engineer we work with used to drive to the office to check a rod string configuration before a field visit. Not because the engineering required it. The file was on a workstation. That is an access problem, not an engineering problem, and it is one of a dozen small frictions that add up across a day. Here are four moments where the day changes when simulation runs in the browser, taken from how engineers actually use PetroBench.
Reviewing a design before the field
With legacy desktop tools the design lives in a file on one machine, behind a VPN and a licensed install. Checking a configuration at 6 a.m. means being at that machine.
On the platform the design lives on the well. Open the well from any browser, and the current configuration, the latest simulation and the version history are on the record. The check takes the time it takes to read it.
Comparing three taper designs
On the desktop, three candidates are three files. Each run takes minutes, and the metrics end up side by side only if someone copies them into a spreadsheet.
RodSim runs a design in about ten seconds, so the loop is duplicate, change the taper, run. The comparison view puts up to five designs next to each other with every metric in one view, and the comparison is shared with the team by link instead of attached to an email.
Getting a report out
The desktop version of reporting is screenshots pasted into a template, and the template drifts from what actually ran. Three months later the PDF and the simulation disagree, and nobody can say which one moved.
PetroBench generates the PDF report from the simulation itself: rod string summary, torque profiles, wellbore visualization, operating conditions. The report reflects exactly what ran, every time, because it is derived from the run rather than assembled next to it.
Finding work from three weeks ago
On a workstation, old work is a filename and a memory. Whether the file on the shared drive is the version that went to the field is a question with no reliable answer.
On the platform the work is attached to the well. Search the well, open its simulations, and version history shows who changed what and when. The design that went to the field is the one on the record, not the one someone remembers.
What does not change
The physics does not care where it runs. The same predictive wave equation the industry has used for decades produces the same loads and stresses. What changes is how much of the day goes to logistics and how much goes to analysis: no drive to a workstation, no file archaeology, no spreadsheet assembly around the actual engineering.
Import your existing files by drag and drop and run one of your own wells both ways for a week. The comparison makes the argument better than this page can.
Related: How to Use the Comparison View. How to Use Version History and Restore Previous Designs.