INOMO Technologies · Oensingen, Switzerland
Telematics, customised to your vehicle.
We build the telematics control unit and the backend that decodes it. Read any signal, act on the vehicle, own the data model, and run it in our cloud or on your own cluster.
30 connectors · COVESA VSS · mTLS
What we deliver
We design the board and we write the backend it talks to.
- TCU NOVA AMThe hardware. A telematics control unit designed in Oensingen with the vehicle interfaces your conversion needs and a certificate-based identity for every unit.Product details
- INOMO Fleet ManagementThe backend. Every raw signal is mapped to COVESA VSS through a profile you control. Signals without a mapping are kept and listed for review.How it works
- One vehicle or a seriesRetrofit a single vehicle, convert a small series or roll out across large-series production, on the same hardware and the same stack.Find your fit
How customisation works
How a raw CAN value becomes a signal you can query.
Telemetry is only useful when it means the same thing across every vehicle. INOMO Fleet Management normalises what the TCU sends to the COVESA Vehicle Signal Specification, using a mapping profile per device type that you can read and change.
- 01
Raw signals
CAN, OBD-II or OEM API values arrive exactly as the vehicle sends them, in the vendor’s units and encoding.
- 02
TCU NOVA AM
The unit authenticates with its own X.509 certificate over mutual TLS and streams into your tenant only.
- 03
Mapping profile
A per-device-type profile scales, offsets and converts each signal to a VSS path. Unmapped signals are logged with samples and can be mapped later.
- 04
Your data
Dashboards, geofences, trips and workflows on one model. Export it, query it or host the whole stack yourself.
The same speed, three encodings
The same vehicle speed arrives in three encodings. The mapping profile turns all of them into one VSS signal your dashboards and integrations can rely on.
| Source | Raw | Mapped |
|---|---|---|
| TCU vendor A | km/h · integer | Vehicle.Speed · km/h · float64 |
| TCU vendor B | mph × 10 · integer | Vehicle.Speed · km/h · float64 |
| OEM cloud API | m/s · float | Vehicle.Speed · km/h · float64 |
Who it is for
One vehicle, a small conversion, or a production series.
Single vehicle
Plug in a TCU NOVA OBD or fit a NOVA AM. One mapping profile, one dashboard, and the data stays yours.
Small series conversion
Define the mapping profile for the device type once. Every converted vehicle inherits it, and a change to the profile reaches the whole series.
Large series
OEM signal sets, tenant isolation down to the database row, and a self-hosted deployment via Helm when the data must not leave your infrastructure.
Customised solutions
Six things customers asked us to build.
Some read the vehicle, some act on it. All of them run on the same unit with a different configuration.
Charge control from the vehicle
The vehicle steers its own charging so a depot stays inside its load limit.
Door control
Lock, unlock and door state for delivery vehicles, driven from a workflow or from the dispatcher screen.
High-frequency telemetry
Signal rates far above a standard tracking interval, where the analysis needs them.
Precise positioning
Metre-level and better, indoors and on the depot yard, where satellite navigation gives up.
Sensor integration
Temperature, humidity and presence read in alongside the vehicle bus.
Actuator control
Geofenced air suspension for depot use, or exterior lighting driven from the backend.
- 30 connectors
- TCU vendors, OEM cloud APIs and business systems
- COVESA VSS
- One canonical signal model across every vehicle
- mTLS per device
- An X.509 identity for every unit in the field
- SaaS or self-hosted
- Helm chart for your cluster, data residency in the EEA in ours
Tell us what your vehicles should report, and what they should do.
You will be talking to the engineers who design the board and run the backend.