One Org. Clear Control
HQ sets the standard. Divisions and regions inherit it. One view of the wells, roles and logs keep it aligned.
US - Permian Basin
- Bakken
- Eagle Ford
US Platform - Cloud Tenant Isolation
- Multi-Language
- Unit Support
- SSO / SCIM
- Local Integrations
- Security & Compliance
Canada - Alberta
- Saskatchewan
- Manitoba
Canada Platform - Cloud Tenant Isolation
- Multi-Language
- Unit Support
- SSO / SCIM
- Local Integrations
- Security & Compliance
-
Argentina -
Colombia -
Ecuador
- Cloud Tenant Isolation
- Multi-Language
- Unit Support
- SSO / SCIM
- Local Integrations
- Security & Compliance
-
Oman -
Kuwait -
Saudi Arabia
- Cloud Tenant Isolation
- Multi-Language
- Unit Support
- SSO / SCIM
- Local Integrations
- Security & Compliance
-
China -
Malaysia -
Australia
- Cloud Tenant Isolation
- Multi-Language
- Unit Support
- SSO / SCIM
- Local Integrations
- Security & Compliance
Mirror How Your Company Runs
PetroBench follows Headquarters, Division, Region, and Group, not a flat user list. Wells, people, and permissions land where they belong.
- Headquarters sets the standard
- Divisions match basins and business units
- Regions own local wells and teams
- Groups keep engineers scoped to the right assets
Set the Standard Once. Inherit Everywhere
HQ publishes equipment, units, languages, templates, and rules. Divisions operate inside that catalog, no parallel equipment lists, no conflicting unit systems.
- Equipment libraries published once for every division
- Unit systems, imperial, metric, and international
- Organization language defaults with personal preference within policy
- Design templates and standard operating rules
Control Who Can View, Edit, and Approve
Define exactly who can act on each product, scoped to the org tree. Leadership sees role changes and access events without standing up a second identity system.
- Per-product roles for RodSim, Dynamics, Automated Design, and Vector
- View, edit, simulate, and approve, scoped to HQ, division, region, or group
- Every role change and denied access lands in the security log
One View Across the Org
Leadership sees structure, users, wells, and recent activity in one place. Regions stay scoped. HQ stays informed without chasing decks.
- One analytic view across HQ, divisions, regions, and groups
- Users and wells scoped to the org tree they belong to
- Recent activity across business units without spreadsheet chase
- See which regions need review before the next ops meeting
Questions Leadership Asks First
What ops leads ask before a multi-division rollout.
PetroBench mirrors your operating structure: Headquarters, Divisions, Regions, and Groups. HQ sets equipment libraries, unit systems, languages, templates, and governance rules. Lower levels inherit those standards and scope wells to their teams.
Divisions operate within HQ-published libraries and templates. They configure basin-specific defaults and manage regions and groups under their division, without creating isolated accounts or duplicate equipment catalogs.
Each product | RodSim, RodSim Dynamics, Automated Design, and Vector, has its own permission model. Roles scope access to the org tree. Permission changes and denied access land in the security log.
Yes. HQ admins get an organization-wide dashboard, wells, users, regions, and recent activity across divisions in one cloud tenant. Region and division admins see only their scoped data.
No. One account can switch across divisions and regions according to role. Local teams stay scoped; leadership keeps organizational reach.
HQ publishes the unit system once for the organization. Divisions and regions inherit that standard so reports and designs stay comparable across business units.
Yes. Start with one division or region under the same HQ tenant. Standards, equipment libraries, and roles stay ready for the next business unit when you expand.
Vector is optional. Leadership can roll out RodSim and the org tree first. When Vector is enabled, it runs on the same wells and permissions, live-well writes stay behind engineer approval.
Yes. IT federates identity through your IdP and SCIM. Leadership defines the org tree, product roles, and who can view, edit, simulate, or approve inside that structure.
Pick one division or region, import a set of wells, and run designs side by side with your current desktop tool. Leadership reviews org scoping, roles, and recommended designs before expanding.
See Your Org on PetroBench
Walk HQ, divisions, and regions on a pilot well set your engineers already know.