Plug it in at 9am. Live on the map by 9:30.
Self-install OBD-II hardware, zero-touch activation, and a pipeline that turns raw GNSS records into road-snapped trips with speed-limit compliance on every completed journey, without an analyst, a spreadsheet or a support ticket.
Snapped · raw read 66.8 km
21 min stationary, ignition on
Moderate · 41 s duration
3-axis accelerometer thresholds
Proven devices, no installer required
Both supported devices plug straight into the vehicle's OBD-II port and draw power from it. There is no separate dongle, no wiring loom and no auto-electrician booking.
| Specification | Standard unit | Wide-coverage unit |
|---|---|---|
| Form factor | Plug-and-play OBD-II | Plug-and-play OBD-II |
| Cellular | 4G LTE (+2G fallback) | Low-power LTE (+2G fallback) |
| GNSS | GPS, GLONASS, Galileo, BeiDou | GPS, GLONASS, Galileo, BeiDou |
| Accelerometer | 3-axis | 3-axis |
| Bluetooth | 4.0 LE for external sensors and beacons | 4.0 LE for external sensors and beacons |
| Backup battery | Yes, for unplug detection | Yes, for unplug detection |
| Best suited to | Urban fleets with frequent data needs | Wide-area coverage, deep-indoor and power-sensitive use |
Devices bought through Vectis are pre-registered to your organisation before dispatch. The first time one checks in, it binds itself to your tenant and appears on the map. Nothing to configure, no serials to email anyone.
The internal battery reports removal, so a device pulled from the port is flagged instead of quietly going dark for a fortnight.
Where a plug-in unit is not suitable, enterprise fleets can use hardwired units fitted by a certified installer, on the same map and the same pipeline.
What happens between the OBD port and your screen
Each stage runs independently of the others. A slow enrichment never blocks ingest, and road enrichment can be re-run for a single trip or backfilled across a fleet.
- 01Session and decode
The device opens an encrypted session and streams its records. Each reading (ignition, movement, external voltage, signal strength, accelerometer) is decoded to a typed value against the vehicle.
- 02Trip detection
Ignition-off plus a debounce window closes the trip. The debounce is what stops one journey being recorded as four when the modem drops into a power-saving state at the lights.
- 03Road snapping
The finished trip is published for enrichment and map-matched to real road geometry, correcting GPS drift and producing a distance you can defend to a driver.
- 04Speed and compliance
Each snapped segment is matched to its posted limit, and overspeed episodes are graded by severity rather than taken from a single instantaneous reading.
Two enrichment tiers
Standard. Runs on our own infrastructure, so full-trip matching and speed limits cost nothing per trip.
Premium. A Google-powered pass that refines the first and last two minutes of a journey, where cold-start GNSS error is worst: the difference between “left the depot” and “left the neighbour's driveway”.
Where a segment has no posted limit in the map data, Vectis falls back through road classification and organisation defaults, and records which source it used. An event is never presented as evidence without saying where its limit came from.
Fences that mean something, not just shapes on a map
Draw a polygon or a circle and give it a job. A fence is a depot, a client site, a restricted area, or a business, private or home zone, and its category decides what its entry and exit events do, from an alert to a journey classification.
- Entry and exit, per fence
Alert when a vehicle arrives at or leaves a fence, chosen fence by fence, with overspeed inside the fence recorded as its own event.
- Fences that classify journeys
Business, private and home zones feed the logbook, so a journey from a driver's home zone to a business zone is proposed as home-to-work before anyone opens it.
- Idle, speed and harsh driving
Idling, overspeed and harsh braking, acceleration and cornering are detected from the device's own data against configured thresholds, and each event is attributed to the driver on record.
Try one device on one vehicle
A single OBD-II unit and a week of driving is enough to see what the pipeline produces from your own roads.