UWI
Validated against the Canadian format, so a transposed digit is refused at entry rather than found six months later in a report
Your hierarchy, not ours
Atlas is the asset tree every other module reads. It is free, and the reason is worth saying out loud: you cannot use any of this without first defining where your things are, so charging for the tree would be charging admission twice.
It also means the work you do here is not work you do again. Every module we ship afterwards sits on the structure you build once, reading your node types, your attributes and your roll-ups.
Three companies, three shapes, one platform
Most software gives you Site and Asset and asks you to squeeze your business into them. Your node types are yours: you name them, you decide what nests inside what, and you decide how deep it goes. Switch between three real shapes below.
The most common shape in oil and gas: where a thing physically is. Roll-ups follow the same lines, so a field total is the sum of its batteries without anybody maintaining a second list.
- RegionPrairie North
- FieldKestrel
- BatteryKestrel 12-14 Battery
- Well100/12-14-038-01W4
- Well102/12-14-038-01W4
- Well100/13-14-038-01W4
- BatteryKestrel South Satellite
- Well100/04-22-037-01W4
- BatteryKestrel 12-14 Battery
- FieldStonecrop
- BatteryStonecrop 6-9 Battery
- Well191/06-09-029-22W3
- BatteryStonecrop 6-9 Battery
- FieldKestrel
Attributes with types, not a notes field
An attribute that accepts anything is a field somebody eventually puts a phone number in. Yours are typed and validated at entry, which is the only point where a bad value is cheap to fix.
Latitude and longitude
Range checked, and refused if the point lands outside the area you operate in
Locked dropdown
A closed list you define. Nobody can add a forty-first value to a list of forty by typing it, which is how a dropdown becomes useless
Number with units
The unit is part of the attribute, so nothing is stored as a bare figure
Date
One format, stored unambiguously, regardless of how it was typed
Text and long text
For the things that genuinely are notes
Getting your existing list in
Nobody types four hundred wells into a new system, and a platform that expects them to is a platform that never gets used. Bulk import takes the spreadsheet you already maintain, matches your columns to your attributes, and tells you what it could not accept and why before anything is written.
Validation runs on the import, which is the point: the same UWI check that refuses a bad entry in the interface refuses it in a file of four hundred rows, and you get a list of the ones to fix rather than four hundred rows of silently wrong data.
Permissions follow the tree
Access is granted on a branch, so giving a foreman their own area is one grant on one node rather than a list maintained well by well. It applies everywhere: the same grant governs what they see in monitoring, and it will govern what they see in work orders and costs without being granted again.
It is also how a contractor gets one field for one month without a shared login, and how an integrator works across four customers without any of them being able to see each other.
Roll-ups come free with the structure
Because the tree is real rather than a set of labels, a total at a battery is the sum of its wells and a total at a field is the sum of its batteries. Nobody maintains a second list of what belongs to what, which is where these numbers usually go wrong: not in the arithmetic, in the membership.
Build your tree
Atlas is free, so the tree is something you can build and judge before you decide about monitoring.