Dashboards
Drag-and-drop layouts with map, chart, table, number and status widgets, per role and shareable.
Backend
INOMO Fleet Management ingests what any TCU or OEM API sends, normalises it to COVESA VSS through mapping profiles you control, and gives your team dashboards, geofences, trips and workflows on one data model.
id: geotab category: fleet_mgmt vendor: Geotab auth_template: host_allowlist: [my.geotab.com] capabilities: streams: - name: logrecord signals: - Vehicle.Speed - Vehicle.CurrentLocation.Latitude - Vehicle.CurrentLocation.Longitude
Customisation
Most platforms decide what a signal means. INOMO Fleet Management lets you decide: per device type, in a profile you can read, version and change, with the raw values kept for when you change your mind.
30 connectors today: TCU vendors, OEM cloud APIs and business systems. New connectors follow a documented specification.
Scale, offset and unit conversion per raw signal, mapped to a COVESA VSS path. A change to the profile reaches every vehicle of that type.
Signals without a mapping are logged with sample values and listed for review. Raw telemetry is retained alongside the mapped model.
What it does
Every function reads the same normalised signals, so a figure in a report matches the dashboard it came from.
Drag-and-drop layouts with map, chart, table, number and status widgets, per role and shareable.
Polygon, circle and corridor zones with real-time enter and exit events, targeted at vehicle groups.
Automatic segmentation from movement: a trip opens above 3 km/h and closes after five minutes idle. Map replay and CSV export down to addresses, coordinates and idle time.
Python scripts with one entrypoint, edited in the built-in IDE and run in a sandbox. Triggered manually, on a schedule, by webhook, or by one of nine domain events.
Emissions per trip and per vehicle, calculated to ISO 14083 and the GLEC Framework, next to fuel and charging cost.
Ask in plain language. Answers come from your own vehicles, drivers, trips, orders and schedules.
Also included
Licences, qualifications, shifts and availability.
Reusable vehicle groups that policies and dashboards target.
Current position and status across the fleet.
Charge points, sessions and energy tariffs.
Service state per asset, driven by real signals.
Jobs and shift plans alongside the vehicles that serve them.
Pick vehicles, signals and a range; chart and export.
A mobile app for the people actually in the vehicle.
Connectors
Each connector is a manifest: identity, auth, the fields an operator fills in, and the VSS signals it produces. Adding a source does not require a code change.
Deployment
Hosted in the EU with data residency in the EEA. Per-organisation single sign-on with Microsoft and Google. Start with one vehicle and scale without an infrastructure project.
The same platform as a Helm chart for your Kubernetes cluster. Your data never leaves your network. Chart updates are published like any other release.
Engineered with the GDPR and the EU Cyber Resilience Act in mind; requirements are tracked end-to-end in a V-model requirements suite.
You will be talking to the engineers who design the board and run the backend.