Hassi Radar
Rig and well wayfinding for oil & gas
Every rig and well on the map, and a way to reach it. Hassi Radar puts every drilling rig and well on one searchable map and gets crews to them. Search a name, see the exact position, and follow turn-by-turn or compass guidance to the pad — with no mobile signal required, because most of a field has none.
The problem
Finding a specific pad still depends on memory and a sign at a junction.
Miss the sign, or find it moved, damaged or buried since your last trip, and you are navigating from memory across a landscape with very few landmarks.
Navigation by roadsign
Wells and rigs are identified by physical signposts at track junctions. Signs are small, unlit and far apart across terrain with few landmarks — and they get moved, damaged, buried in sand, or replaced when a rig goes down for move. A driver unfamiliar with a field has no way to confirm a turn was right until several kilometres later.
A wrong turn is charged to the operator
When a service crew arrives hours late for a specific operation, the rig waits. Rig time is the most expensive resource on a drilling programme, and the delay propagates through every operation behind it. The cost is spread across many small incidents rather than one visible event, so it is rarely measured.
Consumer navigation apps cannot help
A routing engine can only route over roads in its map data. The paved approaches to a field are usually mapped; the graded tracks leading to individual pads are largely not. Asking a consumer maps app for a well pad returns a refusal, or a route to a highway point kilometres from the destination.
The solution
The whole field on the phone every crew already carries.
Each well and rig is a point on a map with a name, a status and exact coordinates. A driver searches for the destination, sees where it is, and navigates to it.
Every rig, by status
Rigs plotted on street or satellite basemaps and shown as active or DTM — the same distinction the physical signs carry. A rig deployed onto a well appears as one combined marker, matching operational reality rather than two unrelated points.
Every well, clustered sensibly
Wells group automatically when zoomed out and are labelled by field prefix, so a group named MD01 to MD04 collapses to a single MD0 marker with a count and the national view stays legible.
Navigation to the pad
Turn-by-turn handoff to the phone's maps application for the paved approach, then an offline GPS compass giving live bearing and distance for the final tracks that no routing service knows about.
Search that finds it
Instant search across rigs and wells by name or location, with results listed while the map stays in view. Panning is bounded to the area of operation, so the map never strays off it.
This is a wayfinding tool, not a monitoring tool.
The primary user is a driver who is lost right now. The map, search and navigation are available without an account and without a connection. Controlling who may change data is a separate layer on top — it is never in the way of someone who just needs to find a pad.
Read access requires no account
A driver who is lost needs the map immediately. Anyone can open Hassi Radar and use the map, search and navigation without signing in. Accounts exist to control who may change data, not who may see it.
Offline is the normal case, not the error case
Most of the field has no usable coverage. The application is built on that assumption: it never presents a network error as a failure, never blocks on a request, and never loses work because a connection dropped.
Nothing is asked of the crew
No check-in, no reporting, no form to complete. The application asks nothing of the driver and gives them the location. Adoption depends on this.
Built for the field
Designed for no signal, because most of the field has none.
This is the capability that separates Hassi Radar from a general-purpose mapping application, and it was the hardest part of the build.
Remote locations, no coverage
Map tiles are cached automatically as crews work, so areas already visited stay fully available with no signal at all.
Work continues while disconnected
Records can be created, edited, deleted and deployed offline. Each change is queued locally and badged visibly, so a crew always knows what has synchronised and what has not.
Reconciliation that cannot corrupt
On a weak connection, four sequential updates are four chances to fail — and a drop midway leaves the server holding a value neither side can identify as intermediate. Collapsing the queue before transmission removes both problems.
Capabilities
What the application does.
Everything below is in the current build and running today.
Two basemaps, one tap apart
Vector street mapping and high-resolution satellite imagery, with an accurate geodesic scale bar that stays correct at any latitude and zoom.
Interactive operational map
Rigs, wells and their deployment relationships plotted geographically, with proximity clustering so the national view never becomes unreadable.
Two navigation modes
Turn-by-turn handoff covers the mapped drive. Compass mode computes great-circle bearing and live distance from GPS — no tiles, no routing service, no network of any kind.
Complete offline operation
Tiles cache automatically as crews work, with street and satellite stored separately so one never evicts the other. Records can be created, edited and deployed entirely offline.
Synchronization that survives a bad line
Queued changes reconcile automatically in an order that preserves rig-to-well relationships. Repeated edits collapse before transmission — four renames become one update, and a record created then deleted offline is never sent.
Three roles, enforced server-side
Viewer needs no account and is read-only. Operator creates rigs, which are assigned to them, and edits only their own. Administrator has full control including the in-app user management console.
Storage you can see and clear
Exactly how much map data sits on the device, cleared selectively per basemap. Unsynchronised work is never removed by any clearing operation.
Deployment
A private system, on your infrastructure.
Hassi Radar is stood up for one organisation at a time. There is no public installation and no shared database between clients.
Private to one organisation
There is no public installation and no shared database between clients. The system is stood up for a single organisation.
Your infrastructure
Deployed on a hosted virtual server or on-premise within your own network, with scheduled database dumps and configurable retention.
Your data stays yours
All rig and well data resides in your database instance. The only external services contacted are the two commercial map tile providers, which serve base cartography only — no rig or well information leaves your server.
Distributed to your teams
The Android application is distributed directly or through managed enterprise distribution restricted to your organisation. Accounts are created by your own administrators in the app.
Full technical and security documentation — architecture, data handling and the security measures in the current build — is available to prospective clients on request.
Request documentationSee Hassi Radar against your operation.
The most useful first conversation is about your fields, your rigs and how crews find them today — not a generic demo. Tell us how your operation runs and we will show you what the application would look like for it.