The data layer of the hall
Scans, gate events, indoor location, vehicle positions and a camera sensor in trial describe operations in the moment they happen. Pollux Loading is the first application built on it.
The master data stays in the system of record. Tours, shipments and addresses come from the TMS, and that is where they are maintained.
The data layer records what happens to them afterwards in the hall: staged, scanned, through the gate, on the vehicle, or not. Every scan, every gate event, every indoor location and every vehicle position is an event with a time and a place.
The applications sit on top of that layer. Pollux Loading is the first of them.
Data layer
Package scans
Every package scanned when staged and again when loaded. A tour's status is the sum of those scans.
HandheldGate events
Every passage of a package through a gate, as an event with time and place.
GateIndoor location
Where an object is right now, reported by Bluetooth beacons instead of a search on foot.
BeaconVehicle positions
Where a vehicle is and when it is at the gate, from telematics.
TelematicsGeminEYE
A camera sensor that recognises packages without anyone scanning. In trial.
Camera · in trial
Application: Pollux Loading
Pollux Loading is the first application on the data layer: the cockpit for loading in a groupage terminal. Dispatch, the hall supervisor and the driver all work from the same loading list. Master data stays in the TMS.
Digital loading list
Which tour first: every tour with shipments, packages and progress, current with every scan.
Driver app
What comes next: the driver sees exactly one tour and the next task in it, and reports deviations where they occur.
Fill-level view
Does it still fit: how much loading space a tour already takes, while there is still time to change it.
Package search
Where is it: enter the SSCC and see when the package was last scanned and which tour it is on.