Everything about a vehicle in one place: master data, technical data, registration, plate history, equipment, tyre sets, vignettes, inspection dates, contracts, costs, receipts, damages, insurance, maintenance, documents and the full history.
The complete vehicle file — instead of 18 folders on a shelf
The vehicle file is the hub of MobilityManager: every other module writes back into it. A refuelling, a service, a traffic fine or a damage case shows up in the right tab automatically — nothing is maintained twice. The vehicle lifecycle is modelled explicitly: planned, in service and retired are distinct states with distinct rules.
What it does
What the module actually does
20+ tabs per vehicle
Master data, technical data, registration, plates, equipment, tyres, vignettes, due dates, contracts, purchase & tax, costs, receipts, damages, insurance, maintenance, fuel, truck/trailer, documents, e-mails, data sheet and usage history.
Counters beyond the odometer
Kilometres, operating hours, a second hour counter and starts — each with its reading, warning threshold and serial number. Replacing an odometer is a recorded event, so lifetime mileage stays correct across the swap.
Site on the vehicle
Depot, agency or branch as its own master datum. It is also the axis the row-level site visibility boundary uses to decide who sees the vehicle at all.
Lifecycle instead of an active flag
Planned (ordered, not yet delivered), in service and retired. Planned vehicles can be excluded from booking while already appearing in planning — commissioning and retirement are documented events.
Odometer readings with provenance
Single entry, bulk entry across the fleet, or a driver submission from the self-service portal — every reading with timestamp, source and plausibility check.
Plate and registration history
Re-plating, de-registration and re-registration stay traceable. Old plates remain searchable so historic fines and receipts can still be matched.
Leasing and acquisition data
Purchase, lease or rental including terms, instalments and residual values — the basis for cost accounting in the Fleet Cost Cockpit.
Vehicle file as PDF
Export the complete file with one click — for audits, handovers, resale or a public procurement file.
Workflow
Lifecycle
01Planned
02In service
03Retired
Frequently asked questions
Yes. The 'planned' lifecycle phase exists for exactly this: an ordered vehicle is created with everything already known, appears in planning and budgets, but is neither bookable nor cost-relevant. Commissioning moves it to 'in service'.
Retired vehicles are not deleted, they move to the 'retired' phase. History, costs, damages and documents stay complete and reportable — a prerequisite for tax audits and retention obligations.
Three ways: manually on the vehicle, via bulk entry for many vehicles at once, or as a driver submission from the self-service portal that fleet management simply confirms. Refuellings, services and the fuel card import also carry odometer readings — each one with its source.
Then activate the hour counter on the vehicle. Besides the odometer there are two operating-hour counters and a starts counter, and a maintenance interval can run on any of them. The odometer stays active on purpose, because cost per kilometre, lease projections and fuel analytics all build on it.