One asset tree
Your hierarchy, defined the way your business is actually organised, once. Every module reads it rather than keeping its own list of wells, sites or stations. That is why the second module you turn on needs no setup.
A platform, not a portal
Most field software is a product with a login. Field Warden is a backbone with modules on it: your asset tree, your permissions and your alarm rosters are built once and everything after that sits on them.
The backbone
One permission system
Access is granted on a branch of the tree, not per module. A foreman who can see one field can see that field in monitoring, in work orders and in costs, and nobody has to remember to grant it three times.
One alarm engine
Callout rosters, escalation and acknowledgement are platform features rather than a monitoring feature. When a module needs to tell somebody something at 3am, it uses the roster you already built.
Modules plug into it
Two are available today and the rest are on a list we have thought about. What makes this different from a roadmap slide is that a new module is a row rather than a redesign: it arrives reading the tree you already built, respecting the permissions you already granted, and calling the roster you already set up. There is no second implementation and no second login.
Atlas
Included with the platformYour asset hierarchy: the tree every other module reads, with typed attributes and subtree permissions
About AtlasPulse
Available nowRemote monitoring: live values, trends, alarms with callout rosters, setpoint control and cameras
About PulseDispatch
PlannedWork orders, assignment, scheduling, completion
Rounds
PlannedSite visits, route sheets, field checks, mobile and offline
Ledger
PlannedBudgets, AFEs, cost tracking against assets
Yield
PlannedProduction and volumetric accounting, reporting
Depot
PlannedEquipment and material management, transfers between locations
Dose
PlannedChemical management, injection rates, inventory, consumption
Revive
PlannedInactive well tracking and reactivation candidates
Tune
PlannedWell optimization, performance against expectation
Horizon
PlannedDrilling and capital forecasting
Why this matters past five people
A company of three shares everything and needs none of this. Past that, the questions start: who can change a setpoint, who gets called when a well goes down at 2am, who is allowed to see the whole company rather than their own area, and what happens when a contractor needs one field for one month.
Every one of those is answered on the tree. Roles carry named privileges rather than a tier, so “can acknowledge alarms but cannot write setpoints” is a role you can actually make. Access is scoped to a branch, so giving a contractor one field is one grant that expires rather than a new account with a shared password.
Each organisation’s data is isolated at the database itself rather than by a filter the application is trusted to remember. An integrator working across four customers signs in once and switches between them, and no query can reach across that line even if somebody writes one wrong.
See it on your own wells
The fastest way to judge this is a Sphynx on something you own, reading real values into your own tree.