Vehicles & drivers
Registration, type, fuel, tank, odometer, ownership and speed limit. Drivers with licence details, linked to HR if you like.
GPS trackers or the driver's phone send positions to Hayat Fleet. Hayat draws the live map, cuts the drive into journeys and raises alerts. Dispatchers plan trips with proof of delivery, and fuel, repairs, tolls, fines and tyres are booked through your normal accounts, so cost per km is real money from your books.
One module for the live map, the trips and every cost of each vehicle.
Registration, type, fuel, tank, odometer, ownership and speed limit. Drivers with licence details, linked to HR if you like.
Registration, insurance, fitness, route permit, token tax and licences, with expiry reminders 30 days ahead by default.
Every vehicle moving on the map with its heading, driver, speed and ignition. New alerts pop up in the corner.
Replay a vehicle's route for up to 7 days. Journeys show distance, top speed, over-speeds and idle minutes.
Over-speed, idling, after-hours use, geofence entry and exit, offline trackers, fuel theft and odometer drops, acknowledged with a note.
Circle or polygon areas for depots, customers and restricted zones. Every entry and exit is recorded.
A dispatch board with free vehicles and drivers. Trips from planned to completed, with cargo, passengers, charge, and a proof-of-delivery photo and signature.
km per litre and cost per km between full tanks. Fills larger than the tank, odometer drops and low efficiency are flagged.
Service schedules by km or days, service records, and tyres from stock to fitting, removal and scrap, with the km each has run.
Trackers and gateways: a tracker device posts for one vehicle; a gateway, such as your tracking server, posts for every vehicle and each point is matched by IMEI. Points come as generic JSON or decoded Teltonika codec 8 / 8E, up to 1,000 per request. Most hardware trackers talk a binary protocol, so a decoder or forwarding service sits between them and Hayat.
Phone tracking: a driver's phone can report positions with a driver token, about every 15 seconds. Hayat Fleet does not come with its own driver app yet; the token and driver API are for the phone app your developer or tracking provider sets up.
Private details: drivers' phone, national ID and licence numbers, and trip customers' phones, are stored encrypted. Documents and proof-of-delivery images open only for signed-in staff.
Step-by-step guides are at help.hayaterp.com.
Hayat Fleet is the fleet management and GPS tracking module of Hayat ERP. It covers vehicles and drivers with documents, GPS trackers and phone tracking, the live map, journeys, geofences and alerts, dispatch with proof of delivery, fuel with theft flags, running costs, service and tyres.
Any tracker or service that can post positions as generic JSON or decoded Teltonika codec 8 / 8E over HTTPS. Binary trackers need a decoder or forwarding service in between, registered as a gateway.
A fuel fill larger than the tank plus a tolerance raises a critical fuel theft alert, and km per litre far below the vehicle's expected figure raises a warning. Odometer drops are flagged too.
Not yet. A driver's phone can report positions with a driver token through the driver API, for a phone app your developer or tracking provider sets up. Without one, dispatchers update trip status and proof of delivery on the trip page.
Every cost is a vehicle expense, posted when it is saved: as a Purchasing bill when on credit to a supplier, or to the payment method's account when paid directly. Fuel fills, service records and the first fitting of a tyre create their expense by themselves.
Yes. If your business also runs the Fuel station module, fleet slips whose vehicle number matches one of your vehicles are added to the fuel log, once only.
We'll show you the screens your business needs and send a quote within one business day.