How a manufacturer, an autonomy supplier and a mine operator share one verifiable answer about each machine.
A mine runs a fleet of autonomous haul trucks. The trucks come from a manufacturer, the autonomy kit from a supplier, and the mine operates them around the clock with a remote control room. From January 2027 the EU Machinery Regulation asks the manufacturer to protect safety functions against corruption.
The autonomy supplier pushes an update at night. A technician swaps a sensor computer after a fault. A truck comes back from the workshop. In each case the mine's fleet system shows the version that was meant to be installed. Nobody holds evidence of what is installed.
Each computer on the truck has a hardware identity and measures what it boots. The fleet system verifies those measurements before it assigns a route, and again after every update and repair. A truck that cannot prove its state may drive to the workshop and nothing else. Truck and control room verify each other before remote operation starts. All three companies read the same result.
The manufacturer has evidence for its conformity file. The supplier can show its update arrived intact. The operator knows, after any published vulnerability, which trucks are affected before the next shift.
An illustrative case built from public documentation and common architectures. It describes no particular company.
Working on attested autonomous vehicles and machines? A first call takes 30 minutes and commits you to nothing. Bring your product and the one question that worries you.
Next fixed date: EU Digital Identity Wallets are due in every member state on 24 December 2026, 42 days from now.