Part of the Mapping series on the Mobtag platform.
In short: Arguments about P&IDs and plot plans are not what stop handovers. What hurts is the gap between the map everyone believed, the permit to work, the inspection record, and where the kit was last week. Google Maps (or your map layer) in Mobtag ties pins to asset profiles and your tag and site model so a shift lead, a project manager, and a commercial lead look at the same live picture—not three exports with different “as at” times.
Mapping is not a prettier chart. It is a shared coordinate system for things, place, and who owns the answer. When the pin, the stock site, and the tags on the asset are fed by the same scans and movements, “where is it?” becomes a filter you trust—not a room full of people reconciling three lists.
When the map and the job site disagree
- The master drawing and the “live” list were never the same file. Operations move kit; the plot plan in the board pack and the list in the yard are updated on different days—sometimes never.
- A permit names a work front; a pin can look like a post code—if a site or zone in the data model does not match how you actually issue and return equipment, the gap reappears at every handover.
- Tags live in a spreadsheet; pins live in a slidedeck and geography never joins the row you need when the phone rings.
| Layer | How it helps when it is the same data |
|---|---|
| Pins and groups | “Show me everything in scope for next month in zone C” without spinning up a new GIS project. |
| Stock sites and location | The move you care about—not a monthly guess in a pivot. |
| Tags | A family of equipment on a filter, not a brand-by-brand export every night. |
Who needs the map—and what “enough” means
- Shift lead—last relevant movement at a named place or pin on the same screen, not a thirty-column national dump.
- Project office—zones or contracts that line up at least to the WBS or the permit register in the right postcode and site id.
- Commercial and finance—one story for hires and moves that stands up in the P&L or in a claim, not a debate about which of three sheets is official this week.
How a scan shows up on the map
Tie the line of work to one asset and one place in the model you teach on day one. Then the search and the map are cousins, not rival answers. A sensible grain: asset at a stock site with a pin, tags from the agreed hierarchy, and every movement refreshing that row.
The wallpaper trap: governance on a static image
Maps as wallpaper—if the layer only changes when someone loads a CSV of lat/long on a Friday, the map is a governance risk: attractive in a pack, wrong on a Wednesday night job.
Prefer events—a move, a count, a handover—so the pin or site in the system of record updates because work happened. The view should be a consequence of operations, not a side art project.
| Symptom | Healthier habit |
|---|---|
| “We’ll refresh the map in Q2” | Every operational list is sourced from—or checked against—the same row the map reads. |
| Three “current” exports | One named, in-scope view for a date and place the CFO and the safety lead both sign off in the same review. |
| Pins without sites | A simple rule: no new pin without a valid site or zone the field actually names in a real handover. |
Summary: Pins, stock, and tags in one operational system give you a map that stays workable for handovers, audits, and “we thought we had two in that city”—without a separate mini-GIS on every new contract.