Petroleum site software an inspector can read
TankAware is our deepest build in this sector. Hundreds of sites, five permission tiers, and sensor data that has to mean something at two in the morning.
Petroleum operations do not fail from a shortage of data. They fail when the data sits in a binder in a truck. TankAware exists because Sutherland Excavating had thirty years of process and no way to prove any of it on demand.
What this work involved
4 things that decide this
- 01TankAware is a genuine oil and gas build for Sutherland Excavating Ltd. in Canada, not an adjacent capability claim.
- 02Sutherland reported 40% fewer manual errors and 30% less operational overhead after launch.
- 03The build carries five permission tiers, from Super Admin down to Contractor, each in an isolated tenant under its own subdomain.
- 04Predictive alerts flag an anomaly before a failure. That only works if your alert threshold survives a cold morning without crying wolf.
Site operations we have shipped
TankAware
AI + IoT petroleum site management for Sutherland Excavating Ltd.
Read the case study →
WAIQ
Business operations and execution platform for multi-site organizations.
Read the case study →
WorkMateAI
Dispute resolution, payments, and compliance for Australia's on-demand trades.
Read the case study →
One petroleum build, two adjacent ones
TankAware is the sector build. WAIQ and WorkmateAI are here because they solve problems a fuel operator also has.
| Build | What it does | Why it belongs here | Sector |
|---|---|---|---|
| TankAware | Inspections, IoT telemetry and predictive alerts. | Direct petroleum site management experience. | Oil and gas, Canada |
| WAIQ | SOPs, workflows and training across every site. | Standard process holding across scattered locations. | Multi-site operations |
| WorkmateAI | Contractor verification, held payments, disputes. | Vendor and contractor governance at volume. | Trades marketplace, Australia |
- ScheduleNobody has to remember.
- InspectDynamic checklist on site.
- FlagA deficiency becomes a record.
- AssignVendor gets the work order.
- CloseSigned off, with an audit trail.
Paper does the first two steps. It loses the last three, which is where the compliance risk sits.
An alarm that cries wolf is worse than no alarm
Tank level readings move on their own. Temperature changes, a delivery arrives, a sensor drifts. Set your threshold too tight and your team learns to ignore the phone within a fortnight.
Tuning that threshold is not a launch task. You do it for months afterwards, against real readings from real sites. That is why we stayed on the models after TankAware went live.
- Model the normal daily swing per site before you set any alert.
- Separate a sensor fault from a real anomaly. They need different people.
- Track how often an alert was acted on. An ignored alert is a design defect.
Downstream site management, end to end
Site management is where a fuel operator's compliance risk actually lives. Tank monitoring, inspection automation, deficiency-to-work-order flows, contractor payments, and the audit trail your regulator asks for.
TankAware carries all of it in one platform, with each client organisation in its own isolated tenant under a dedicated subdomain. Your existing sensors and gauge consoles are integrated rather than replaced.
- 01IoT tank telemetry with predictive alerts tuned against each site's normal daily swing.
- 02Inspection automation from scheduling through dynamic checklists to deficiency escalation.
- 03Vendor portals with integrated payments and a full deficiency-to-work-order lifecycle.
- 04Multi-tenant isolation, five permission tiers, and per-site document version control.
The stack behind TankAware
Platform
Data and AI
Controls
“TankAware has revolutionized how we manage petroleum sites. The real-time data and automation have exceeded expectations.”
Blake Sutherland · President, Sutherland Excavating Ltd.
What fuel operators ask us
01Can we replace paper inspection logs with an app?
Yes, and TankAware is that build. Your gain is not the digital form. It is that a flagged deficiency turns into an assigned work order with an audit trail. That is the half your paper process always loses.
02Will it connect to the gauge consoles we already have?
Usually. Tank-level sensors are integrated rather than replaced, so the question is what your console exposes and how often. Older kit sometimes needs a small gateway, and that goes in the scope before anyone quotes a price.
03How do you stop false alarms from training staff to ignore alerts?
Model the normal daily swing at each site first, then set thresholds against that rather than a single global number. Track whether anyone acted on each alert. An alert nobody responds to is a bug to fix, not a stat to report.
04Can the system produce what our assessor asks for?
That is what the audit trail exists for. TankAware carries per-site document version control, full audit logs and exportable compliance reports, so an assessor gets the record rather than a reconstruction. Build to what the standard requires and the evidence is a by-product of daily use.
05How long do these records need to be kept?
Retention depends on your jurisdiction and the tank class, so it is a question for your compliance lead rather than for us. The build decision is to make retention a configurable policy per tenant. Hardcoding a period into the schema is how a system becomes non-compliant after one rule change.
