Of our seventy lorries, the twelve delivered this year are the first that receive software updates from their manufacturer over the mobile network. Software in a modern lorry manages the engine, the gearbox, the braking systems and the driver's displays. Until now it changed only when a lorry went into a workshop, where a technician connected a laptop and a fitter signed the job sheet.
A United Nations regulation on vehicle software updates, known as R156 and adopted for new vehicles across Europe, requires manufacturers to manage updates as a controlled process. It covers updates sent over the air, makes sure an update can be installed safely, and requires the driver to be told what it will change. That is reassuring about the manufacturer. It says nothing about us.
In September two of the new lorries installed an update overnight in our yard. The next morning the dashboard showed a new warning message, which the release notes described as a change to how tyre pressure readings are displayed. The release notes had been posted to the manufacturer's fleet portal, which nobody in our transport office signed in to. One driver rang in thinking his lorry was faulty and waited forty minutes for an answer. No harm was done. It was simply the first time a supplier had changed the behaviour of our equipment, on our premises, without anyone in the company knowing it was going to happen.
For twenty years my department has managed software on things that stay in buildings. Our fleet is becoming a set of computers on wheels, changed by someone else on a schedule they choose. So the transport manager and I have agreed how we will treat them before the rest of the fleet catches up. Each lorry's software version is now recorded in the asset register next to its servicing history. The fleet portal is checked every week, and its notices come to the transport office and to my service desk. Where the manufacturer lets us choose, updates install on Saturday nights, when most of the fleet is parked. Any update that changes what a driver sees or does is briefed to drivers before it installs, in the same way as a change to our handheld software.
When software reaches the things that move your goods, change management has to reach them as well, and someone has to decide whose job that is before the first update arrives.
– Serguey Shinder