Production control is waiting on a dedicated trailer from a tier-one supplier. On the TMS map it is moving north on the D1, GPS ping every few minutes, ETA 09:40. At 09:55 someone calls the gate. The truck is in your yard. The live map still shows it twenty kilometres south because the moment it turned off the motorway and entered your site, the cellular tracker lost clean sky view and the dot stopped updating.

‍

Dock two is empty. Dock four has a different carrier. The forklift team walks the yard. Radio traffic starts. The trailer was visible for three hundred kilometres and invisible for the last three hundred metres — exactly where labour, bay time, and line feed actually matter.

‍

That gap is normal. GPS and cellular trackers work in open sky. Roofs, walls, and metal siding kill or scatter the signal. Most plants solve the last mile with phone calls, gate logs, and ASN paperwork that never lands on the same map planners use inside the hall. twinzo closes the handoff: keep the outdoor leg on GPS coordinates, pick up the asset with indoor RTLS once it crosses your geofence, and show both on one facility model so the dock team sees the truck at bay four instead of on the motorway.

‍

Same pattern for returnable packaging. A steel rack leaves the supplier's stamping branch with finished panels, rides GPS tagged on the truck, unloads at your inbound buffer, and should loop back empty next week. Industry practice for OEM returnables treats each rack as balance-sheet inventory — plants run cycle counts on them because a missing rack blocks the next shipment and suppliers invoice for unreturned units.

‍

Outdoor GPS tells you the truck left Brno at 06:00. It does not tell you whether the rack sits in your quarantine aisle, staging by line three, or still on the trailer in the yard. Indoor tags on the rack — BLE, UWB, or a rugged GPS tracker that also beacons indoors — land it on the same twin as your forklifts and WIP buffers. Planners see the rack in hall B. Logistics sees the truck still attached at the gate. One object, two legs, one map.

‍

Typical moment: supplier portal shows 'delivered' because the truck GPS entered your geofence. Production still cannot find the rack because it never left the trailer. With indoor pickup at the gate or dock scan zone, the handoff timestamp matches physical reality, not just a fence crossing on the highway map.

‍

GPS needs line of sight to satellites. Indoor positioning uses anchors you control: BLE beacons, UWB anchors, Wi-Fi RSSI, or Quuppa-style locators in the ceiling grid. The asset carries a tag or telematics unit that switches modes — GNSS outdoors, UWB or BLE indoors — or you attach separate outdoor and indoor identifiers to the same logical device in twinzo.

‍

The operational boundary is not 'technology A vs technology B.' It is the gate, the yard line, the warehouse door, the tunnel between two halls. Draw that boundary as a geofence on the outdoor map. When the asset enters, twinzo maps the last GPS fix to the indoor coordinate system and continues the trail on the hall floor plan. When it leaves for the return leg, indoor tracking ends and GPS picks up again. No duplicate objects, no manual merge in a spreadsheet.

‍

Plants with multiple buildings on one campus hit the same wall twice: GPS is fine in the courtyard, useless in hall C. Each building gets an indoor layer. The asset walks hall A → yard → hall C and the path stays continuous because the platform normalises positions into one 3D scene per site, not three disconnected PDF layouts.

‍

Multi-site supply chains already run GPS on owned or leased trailers. Supplier branches often have a small yard and a staging hall — the same blind spot, just at the upstream end. If the supplier tags outbound racks or shares trailer telematics, twinzo can ingest those outdoor fixes alongside your indoor infrastructure.

‍

You do not need the supplier to deploy your full RTLS stack. Common patterns: they geofence their dispatch yard and you geofence your inbound gate; the asset ID stays constant; each leg appends to one history. For critical flows you place a portable tag on the rack at their dock and read it off at yours — outdoor GPS fills the gaps between sites, indoor anchors resolve the last metres at both ends.

‍

Dispatchers stop asking 'which plant is it heading to' on one system and 'which aisle did it land in' on another. The 3D twin shows the supplier branch model, the overland segment as a path, and your hall with the asset on the correct rack row. Same labels, same areas, same notification rules once it enters your no-go zones.

‍

Indoor tracking only helps if operators recognise the hall. twinzo combines scans, CAD, and Blender meshes per building so the rack or trailer sits in geometry people walk every day — not a grey box on a generic floor plan.

‍

Your main plant might be a LiDAR scan of the assembly hall. The supplier branch is CAD from their layout team. The connecting yard is a simplified mesh with gate posts and dock bays marked. Mixed sources, one scene per site. When the asset moves from yard mesh to hall scan, the icon does not jump to a different product — it crosses a door you drew on the twin.

‍

Between two of your own buildings on one campus, the same applies: hall one scan, hall two CAD, outdoor GPS or a short yard BLE grid in the middle. Maintenance tool cages, AGV totes, and borrowed forklifts that never leave the site still benefit — GPS is irrelevant indoors, but the cross-building path is the job that breaks without a continuous trail.

‍

Analytics on the combined path answer questions neither GPS nor indoor RTLS answers alone. How long did the trailer sit in the yard after the geofence ping said 'arrived'? Did the rack enter quarantine or go straight to line-side staging? Which supplier trucks consistently miss the dock appointment window but still consume gate labour?

‍

Area occurrence runs on the full trail: highway segment (speed, dwell at rest stops if you care), supplier dispatch yard, your gate, yard, dock, inbound aisle, buffer. Compare dwell at the supplier's staging hall vs your inbound — that is where balance-sheet returnables actually get lost, not on the motorway.

‍

Same stack as live forklift tracking. You are not exporting GPS CSVs and merging with a separate indoor report. One asset history, one set of areas, congestion and dwell computed whether the fix came from GNSS or a ceiling anchor.

‍

Notifications follow the same rules as tagged shop-floor devices. Geofence the supplier's outbound lane: alert your planner when the trailer starts the run. Geofence your gate: alert the dock when GPS enters, switch to indoor rules once the tag reads at the door.

‍

Inside, draw no-go zones — pedestrian aisles, clean rooms, fire lanes. A trailer tagged only with GPS never triggered those rules because it never appeared indoors. After handoff, a rack parked across a fire route or a forklift pulling a supplier cage through a pedestrian corridor raises the same alert as your own fleet would.

‍

For trials, simulate the path: gate → yard → dock → aisle. If area occurrence shows time in a no-go before you tag the fleet, fix the route with the supplier instead of discovering it on the first live delivery.

‍

You can rehearse the flow without waiting for hardware at every supplier branch. Place the trailer or rack on the supplier yard model, simulate movement along the road leg, hand off at your gate, continue to the dock and buffer on the indoor layout. Area occurrence and no-go checks run on that simulated path the same way they run on live data.

‍

Use it to decide where indoor anchors pay off. If simulation shows ninety percent of dwell is in your yard, not the hall, invest in yard coverage first. If the supplier handoff is always a two-hour gap between GPS 'departed' and your gate scan, fix the process before adding more outdoor pings.

‍

When tags go live, the simulated route becomes the baseline. Compare actual supplier runs to the plan. Deviations show up as extra dwell in an area, not as a missing dot on two different portals.

‍

Same GPS-plus-indoor pattern shows up wherever an asset leaves open sky and enters a roof:

‍

• Engineering tooling between plants — GPS on the shuttle van, UWB tag on the fixture crate, one trail from plant A's tool room to plant B's line.

• Spare parts cage on a scheduled milk run — outdoor telematics on the route, BLE in each hall so the cage is findable when the line stops.

• Customer-owned containers — GPS while on public roads, indoor pin when unloaded so finance and ops agree on custody.

• Trial forklift borrowed from a partner site — geofence their gate and yours; indoor tracking only for the week it lives in your hall.

• AGV load handoff at the plant boundary — outdoor AGV yard segment plus indoor drop at the assembly buffer, continuous path for throughput analysis.

‍

Pick one flow that already has GPS on the road leg and nothing inside: a dedicated supplier trailer, a returnable rack pool, or a cross-site tooling shuttle. Map the gate handoff, add indoor coverage where dwell actually happens, and put the asset on the same 3D twin your floor teams already use.

‍

Outdoor and indoor are not two projects. They are two segments of one job — get the rack from the supplier branch to the line without losing it in the yard.

‍

Get in touch if you want to walk through GPS-to-indoor handoff on your own site and supplier layout.

‍