Bring your own AVL, sensors, and hardware.
SnowOps is built around pluggable provider abstractions — one pipeline for every vehicle-position source, one pipeline for every sensor stream, and HID support for the physical controls operators actually want to use. All providers ship disabled by default; you enable what you have.
Five providers, one tracking pipeline
A single IVehiclePositionProvider abstraction funnels every source into one VehicleLocation table, one SignalR feed, and one public live map. A coordinator runs per-provider scheduling with failure isolation — one provider outage doesn't stop the others.
Traccar
REST / HTTP Basic auth — self-hostable open-source AVL.
Geotab
JSON-RPC via the official SDK.
Samsara
REST with Bearer token via the official SDK.
GTFS-Realtime
protobuf VehiclePositions — reuse a transit feed for fleet visibility.
OGC Moving Features
MF-JSON — the open standard for moving entities.
Sensible defaults
All providers ship disabled by default — credentials aren't required at startup. A generic device-to-vehicle mapping table and per-provider provenance tagging (LocationSource) keep everything traceable. Units auto-normalize (knots / km-h / m-s → mph, m → ft).
Failure isolation
Independent polling cadences (5s base tick) mean one flaky provider can't drag down the rest of the live map.
Dedicated sensor host
Sensors run in a separate SnowOps.Api.Sensors bounded context — a parallel pipeline (ISensorReadingProvider + SensorReadingSyncCoordinator) with Sensor + SensorReading entities on TimescaleDB. Stations auto-register on first sighting.
Live broadcast
Observations push to clients over a dedicated /sensorHub — same real-time philosophy as the AVL pipeline.
RWIS, pavement, friction — on open standards
SnowOps ingests stationary sensor observations through pluggable providers, with native RWIS support baked into the entity model.
OGC SensorThings API
Part 1: Sensing (OGC 18-088 v1.1) compliant ingestion.
RWIS-native fields
Pavement temperature, surface status, precipitation, and friction (mu).
ThingsBoard
REST + JWT provider for existing IoT deployments.
Tactile control, even in gloves
Touchscreens are hard to operate with winter gloves and harder still when bouncing down a salted road. SnowOps supports physical controls that work the way operators work.
Bluetooth GNSS receivers
External high-accuracy positioning for precise plowing and salting — beyond device-GPS accuracy.
USB / Bluetooth MacroPads
HID keypads and knobs — tactile, glove-friendly, no special drivers.
- ⌨️
Programmable controls
Plow up/down, salter on/off, spread-rate knob, task-status keys, emergency-alert button.
Cross-platform HID
The same HID MacroPad works across Android vehicle tablets, Windows convertibles, and iPads — a real UX advantage over touchscreen-only rivals.
Provider families
Plug in what you already have
Whether it's Geotab, a ThingsBoard IoT stack, or a custom MacroPad — SnowOps meets your hardware where it is.
Request a demo →