Dispersion over the urban area
The vehicles end up where the last user leaves them. The status of each person is discovered by going there, and each check costs a trip.
Sector — Micromobility
Your vehicles are everywhere. That is exactly where they can disappear.
Scooters, e-bikes and scooters shared or rented move throughout the city and return only if someone comes to pick them up. The problem, however, comes first: almost no fleet tracker is installed on a vehicle that does not have the electrical system of a car. We install it.
The point
A fleet that doesn't stand still anywhere.
A micromobility fleet does not have a forecourt. It's spread across square kilometres of the city, changes location every hour, and the only way to know where a vehicle is is if someone sees it.
Recovery scheduled by heart
The collection round is built on where the vehicles were yesterday, not on where they are now: you pass where you don't need them and skip where you need them.
Exit from the service area
A vehicle that leaves the operational coverage only becomes a problem when someone searches for it and cannot find it.
The device that cannot be mounted
Fleet telematics requires a 12 or 24 volt system and a diagnostic socket. On a scooter there is neither one nor the other, and the installation stops before it begins.
The stationary vehicle that no one knows is stationary
A vehicle that stops being used does not report it: it remains on the list as available until a customer finds it and complains about it.
The technical difference
any vehicle, any voltage
It's the reason this page exists, and it's a fact about installation over software.
What does fleet telematics mean?
An automotive plant. Most devices are powered by 12 or 24 volts and connect to a diagnostic socket or the vehicle's on-board network. It's a premise so obvious that it almost never gets written down — until you're faced with a vehicle that doesn't accommodate it.
What changes on a micromobility vehicle
There is no diagnostic socket, there is no on-board network to interrogate, and the supply voltage is not what the device expects. The practical result is that the installation is not done, or is done with improvised solutions that do not last long.
What we do
Zenit supplies and installs satellite trackers on any type of vehicle and at any voltage. It is an installation capability, not a software function, and applies to everything that a standard automotive system does not have: micromobility vehicles, but also trailers, equipment and machinery.
- The installation is evaluated on the actual vehicle, not on the catalogue model
- The coverage of the available data changes with the vehicle: on a scooter it is position, route and use
- Installation coverage is verified before installation, not after
What do you see
The functions needed on a distributed fleet
Only what is available today. What depends on the vehicle is said as such instead of being promised.
Location in real time
Where each vehicle is when the device communicates, on a single map instead of one report at a time.
Route history
Where a vehicle was and when: it is the data with which a day is reconstructed instead of hypothesizing it.
Geofence and areas
Areas drawn on the map that generate an event when a vehicle enters or exits. You define them, on your operational coverage.
Stops and use
How long a vehicle has been standing where it is, to distinguish the one in use from the one to be recovered.
Operational alerts
Rules that report the exception instead of letting anyone who passes by discover it.
A single fleet
If you also manage vans or company cars, they are on the same platform as light vehicles.
What changes
From «let's go and see» to «we know where they are».
No number declared: we have no verifiable data on micromobility fleets to cite, and citing generic ones would be worse than remaining silent.
Before
- 1
Visual search
The position of a vehicle is discovered by going there, and each check costs a trip.
- 2
Tour built from memory
Recovery follows habit, not the actual distribution of today's means.
- 3
Unmanned coverage
A half outside the area is noticed when it misses, not when it goes out.
With Zenit
- 1
Position available for consultation
Where each vehicle is located when the device communicates, without going out.
- 2
Ride built on today's data
Recovery starts from where the vehicles are now and how long they have been stationary.
- 3
Exit from the marked area
The geofence generates the event as it happens.
coverage
What Zenit doesn't do, said here instead of in the demo
In this sector it is needed more than elsewhere: the misunderstanding comes first and wastes time for both.
We do not provide the vehicles
Your existing e-scooters and e-bikes remain unchanged. Zenit supplies and installs the tracking devices and the platform that reads them; it does not supply the vehicles themselves.
We do not manage rental to the end customer
Booking, vehicle unlocking, payment and invoicing to the end user are not part of the coverage. If you're looking for a sharing platform, you're looking for something else — and it's best to know that now.
We are not a sharing platform
There is no app for your customers. There is a platform for you, which tells you where the vehicles are and what operational status they are in.
We are not talking about compliance with municipal rules
The areas are configured, but the parking and circulation restrictions change from municipality to municipality and from resolution to resolution. We do not know them and we do not declare that the system complies with them: the tool is configurable, the evaluation remains yours.
The value
The cost of a fleet that cannot be seen is made up of travel.
No percentage declared. These are the levers and they are measured on your operations.
Fewer empty runs
A lap built on the real position avoids passages where there was no need to go.
Vehicles put back into service earlier
A stationary and localized vehicle is recovered; a still and unknown one remains still.
Guarded coverage
Exiting the operational area becomes an event instead of a discovery.
Before installation
Three decisions that define the configuration
Vehicle, necessary data and operating area determine how to install the device and which rules to configure.
Half
the vehicle
Brand, model and how the system is made: it is the check that says if and how it is installed, and it must be done on the actual vehicle rather than on the technical data sheet.
We respond with an inspection or photos of the housing, not with specifications.
Data
The data coverage
On a vehicle without an on-board network, the data available is position, route and use. Which of these you actually need changes what makes sense to install.
It is defined before installation, so no report is born empty.
Area
The operational area
Where vehicles can stay and where they can't is your decision, and determines how geofences are configured.
You draw it on the map together, starting from the coverage you already use.
Frequently asked questions
Frequently asked questions about micromobility
Bring us a vehicle, not a specification.
The quickest way to find out if it can be installed is to tell us what resources you have. The verification is done on the real vehicle, and it is the first thing to clarify before talking about functions.