Control tower viewing consolidated trip positions from GPS mirror accounts

Definition

OCL Cargo’s GPS tracking agent (Agent 02, «Track the trip») reads carrier GPS mirror accounts, consolidates location in the OCL portal as the single source of truth for tower and customer service, and alerts only on a deviation — in under five minutes.

Learning about a deviation when the customer complains is already lost OTIF. Landing Agent 02 stops asking «where is it?» and moves to diagnosed exceptions.

What the GPS tracking agent means in practice

Landing cycle: reads the mirror,lands in OCL portal y single source a alert only on exception. Manual: call the driver, one tab per GPS, learn late.

The access concept is the GPS mirror account; this agent is who operates it at scale with computer use or integration.

Why it matters (shipper / 3PL / carrier)

1.Shipper / CS

Customer answers with real position, not «we already asked».

2.3PL / tower

Multi-carrier without headcount linear to every portal.

3.Carrier

Shares visibility without giving away GPS admin.

How it works / when it applies

It fits multi-carrier Mexico–US networks without a single API. Landing operating goal: alert in under five minutes on deviation; internal playbooks often target under 10 minutes to first useful alert.

Needs active mirrors, appointment/plant geofences, and an exception owner. See track & trace and geofencing.

SignalAgent actionOutput
Position on mirrorRead and normalizePoint in OCL portal
Vs plan / geofenceDetect deviationAlert to tower
No exceptionUseful silenceDoes not spam the team
Value is in the exception, not the pretty map.

Mirror checklist

1.Read-only

No edit rights; credential rotation.

2.Trip scope

Units for the shipment, not the whole foreign fleet.

3.Geofence

Origin, destination, border if applicable.

4.Alert SLA

Minutes and channel (tower).

Zen flow

  1. Mirror

    Read GPS

  2. Portal

    Single source

  3. Match

    Vs plan

  4. Alert

    Exception only

Detail lives in geofence and SLA; the diagram marks Agent 02’s cycle.

Common mistakes

1.Mirror without alerts

Decorative telemetry.

2.Asking to edit foreign GPS

Breaks carrier trust.

3.Not hanging off trip ID

Audit loses the GPS leg.

OCL and the shipment file (light)

Agent position and timestamps feed OTIF, detention, and pre-pay matching. Map: freight agents.

Sources and further reading

  1. Blog: GPS mirror accounts.
  2. Glossary: mirror account.
  3. Playbook: GPS 10-min alert.
  4. Hub: freight agents.
Key takeaways5 points
  1. Landing: reads mirrors, OCL portal y alert only on exception (<5 min).
  2. Does not replace the carrier GPS; uses a read-only mirror account.
  3. One tab per GPS platform is the anti-pattern; the agent consolidates.
  4. Without geofence and an owner, the map is decorative telemetry.
  5. Hub: freight agents.

Is tracking still a phone call to the driver?

30-minute diagnostic on one corridor: what the agent closes alone vs what escalates to your team. 6–8 week pilot.
Book a diagnostic

Frequently asked questions