Your field crews spend the day in vehicles, and the vehicles are where the time and the fuel go. ISPCQ follows every tracked van live, plays back any day of its route and keeps its keys, papers and permanent driver on one record. Because it sits inside the ERP, a van is never just a dot: it carries the crew holding its keys, the jobs they were booked on and the outage they are driving to.
The tracking vendor gives you a login, a map and a replay that is really a file of coordinates. It knows that a vehicle stood for fifty minutes at an address. It does not know that the address was a booked installation, which crew had the keys that morning, or that the van was meant to be at the depot by five.
So the monitoring team works with two windows open, copying times from one into the other, and the questions that matter (was that trip for a job, why did the van leave home at nine at night, when is its licence due) are answered by whoever remembers.
ISPCQ reads the positions and supplies the context. The driver is whoever holds the keys on the Stores sign-out. The jobs are the ones that crew was booked on while it held them. Teams are the operator’s own org units, so each person sees their own teams’ vans. Working hours come from the HR shift calendar, and alerts land as ordinary tasks in a team’s queue.
The positions stay on your own tracker server. ISPCQ talks to Traccar, the open-source GPS server, and asks it for positions when someone looks, rather than keeping a second copy of everyone’s route. Monitoring never needs a login to it. The ERP only reads; it cannot send a command to a tracker.
The live map and history sit on the Dashboard. Trackers and trips sit in Notes & Tasks, and van keys in Inventory. The same vans appear on GeoMap. One set of permissions decides who sees which van, everywhere.
Every van with a tracker, on a map beside a list, in the same cockpit look as the network tabs. New positions are pushed to the page within seconds of a tracker reporting; nobody reloads. Each vehicle is drawn as its type (car, bakkie, van, truck, machine, heavy machinery or bike) with an arrow for its heading, green when moving, grey when parked, red when its tracker has gone quiet.
Open any van for where it drove. Pick a preset or your own From and To with times, step back and forth by the same span, and read the kilometres for exactly that window, not for whole days. The route is drawn clean: a van standing still is one spot, not a scribble of GPS drift.
Press play and a marker drives the route on the map, coloured by its speed, with the time and km/h beside it. The route itself is coloured from green through yellow and orange up to the speed limit you set, and red above it, with direction arrows along the line and Start and End flags. Parked time is skipped, so a day plays in minutes.
Save your offices and depots once as Places, and give a permanent van its driver’s home. From then on a stop reads Depot · 3 h 10 min instead of a street address, the live list says At Depot, and the history totals the time spent at each place over the period.
For a single day, route, stops and trips download as Excel files in local time and km/h. For any period up to 31 days, a CSV of exactly the trips and stops on screen: one row each with times, minutes, km, top speed, addresses and the place of every stop, a total row and time at each place. It doubles as an arrive-and-leave log for the depot.
One row per van: its tracker, SIM number, type, fuel type, how it reports, teams and the status read from the tracker server (online, offline, registered but silent, or missing there). Putting a tracker in a van also names it after the van on the tracker server, so the two never disagree; nobody logs in there to do it.
A vehicle reaches the cockpit in one of two ways, and the register says which. Your own devices: a tracker with its own SIM card and mobile data, connected straight to your Traccar server, reports about every thirty seconds and nobody else is involved. The GPS BG service: for vehicles tracked by GPS BG, an optional plugin for their service reads GPS BG’s own interface every four minutes and hands each vehicle’s last position to the same Traccar, so the map, history, replay and register work unchanged. It stays off unless the operator has a GPS BG account.
Van Keys is a screen inside Inventory with one large tile per van: green in the yard, orange when out, a colour of its own for a permanent van and red when an expired licence disc blocks it, with the driver and since when. Tap a van, tap the driver, done. Taking the keys back offers an optional check of condition, tools, fuel and odometer. The same van can never be given out twice, and a sign-out can never be hidden as private, so Stores can always take a van back.
Every five minutes the platform checks the fleet by itself. When a permanent van leaves its driver’s home outside that driver’s working hours, a high-priority Van moved out of hours task lands in the monitoring team’s queue with the time and the hours it broke. The working days come from the HR shift calendar, not a fixed Monday to Friday: a rostered day off alerts all day, and leaving up to 45 minutes before a shift is the drive to work, never an alert.
Monitoring sees each field team’s day: the crews, the van each held and when, and the jobs they did while holding it. A job is listed when its crew held a van’s keys at the job’s booked start, computed from the sign-outs rather than typed in. Log a trip on a job pre-fills the link to it; the trip card takes its times from the route history and closes with a verdict.
During an outage the question is who is nearest. Switch on the Vehicles layer in GeoMap and the live vans appear over the fibre plant, the fault and the affected customers, refreshing every thirty seconds. Click a van for its plate, state, place, last contact and driver, and a link to its route history.
Who sees which van. Vans belong to one or more of the operator’s org units. A person sees the vans of their own units and the units below them; seeing every van is a separate permission. The rule holds on the map, the history, the downloads, the tracker register and GeoMap alike, and a van you may not see behaves as if it does not exist.
The situation. At four in the afternoon a trunk cable is cut and a few hundred customers drop. Three splicing crews are somewhere across the region. At nine that evening one of the permanent vans leaves its driver’s home, on a day the roster says he is off. A week later finance asks how many kilometres the splicing team’s vans drove that month, and how long they spent at the depot.
What ISPCQ does. The NOC opens GeoMap on the fault, switches on Vehicles and sees which crew is closest, with the driver’s name from the morning’s key sign-out. The job goes to that crew. At 21:05 the out-of-hours check files a task in the monitoring queue, naming the van, the time it left home and the fact that its driver is not working today. The monitor opens the link, watches the van live, and replays the rest of the evening the next morning at 16×. For finance, the monitor filters the list to the splicing team, opens each van on Last month and downloads the CSV: every trip and stop, the km for exactly that month, and the time at the depot.
The result. Nobody opened the tracking vendor’s portal. The crew that fixed the cut, the trip that went with the job and the evening that needed an explanation are all on records the rest of the ERP already uses, with a verdict against each trip and a task against each question.