GPS monitoring of official vehicles for government bodies and state-owned companies

When we start a conversation with the administration of a state-owned company or an agency, the list of questions is almost always the same:

• Whether official vehicles are used outside working hours and at weekends.
• Whether the mileage on the waybills matches the actual mileage.
• How much fuel is really used and what the difference is written off against.
• How many of the vehicles in the fleet are genuinely needed and how many stand unused for weeks.
• Where the emergency or duty vehicle is right now, if someone has to go out urgently.

That last question matters for services that work out in the field: municipal, emergency, technical. The dispatcher needs to see who is closest to the call rather than ring round the drivers.

In practice the changes are most noticeable in the first months, when staff learn that journeys are visible on the map and management starts looking at the reports regularly. If nobody opens the reports, the effect soon fades. After that monitoring becomes an ordinary accounting tool, like a bookkeeping program.

A government fleet is rarely uniform. One register may hold departmental saloons, minibuses for running about, refuse lorries, graders and water carts. We pick the right equipment for each type, but in the system everything is visible in one window.

• Official cars - a basic tracker recording mileage, journeys and work outside working hours. Fuel sensors are usually not needed: on newer vehicles the CAN bus data is enough.
• Older machines and lorries - a tracker and a fuel level sensor in the tank. Only this way can fuel written off be backed by fact rather than by a norm.
• Municipal plant and heavy equipment - sensors on the attachments: the brush, the blade, the pump. You see not only that the vehicle drove along the street but that it was sweeping or watering while it did.
• Field staff - personal trackers with a panic button for those who work alone on site.

To be honest about the limits: monitoring shows where and how a vehicle worked. It does not replace internal controls and it does not decide for itself which journey was official. The rules for using vehicles are set by the organisation, and the system helps check them.

A government organisation usually cannot just try something out. Before any vehicles are connected, three groups of questions have to be answered, and it is better to prepare the answers in advance.

The supplier qualification pack. What is usually asked for: a description of the solution and its functions, a list of the equipment with the manufacturers' documents, a description of the platform and of who operates it, the fitting and warranty service arrangements, the terms of technical support, a confidentiality agreement. The contents of the pack are determined by the customer and its procurement rules; we prepare our part to match your list.

The data hosting architecture. It is worth drawing the diagram before the pilot together with the IT department: tracker - communication channel - platform server - user workstations - and, where required, forwarding data into the agency's own system. The diagram marks where the data is held and for how long, who has access to it and how that access is granted and withdrawn. Hosting requirements are set by the organisation; we show which options are technically possible.

Acceptance criteria. Better written into the terms of reference than discussed after the fitting is done. For example:

• every vehicle in the register is connected and transmitting, with deviations on individual units explained;
• reports on mileage, fuel and work outside working hours are produced in the agreed format;
• access rights match the departmental structure and have been checked with test users;
• the responsible staff have been trained, and there is a support contact and a procedure for raising requests.