An autonomous truck incident at Fortescue Metals Group (FMG) Christmas Creek operation this week has shone a light on the safety vulnerabilities of wireless mesh networks for the management of data associated with autonomous vehicles supplying a wide variety of sensory inputs.
Fortescue Metals Group confirmed today that one of its Auto Haulage System (AHS) trucks reversed into another parked AHS truck at slow speed on Monday night.
According to reports in The West Australian, the back corner of the reversing truck smashed into the cab of the stationary truck. It is believed the incident may have occurred after a dropout in Wi-Fi coverage which facilitates the transfer of data from the truck to the communications centre.
Fortescue Metals said in a statement that no one was hurt or at risk of being injured in Monday’s incident.
“This was not the result of any failure of the autonomous system,” Fortescue Chief Executive Elizabeth Gaines said in the statement.
The media release confirmed that “No manned vehicles or people were involved and its AHS trucks have safely travelled more than 24.7 million kilometres since 2012.”
FMG also confirmed that it is conducting a full investigation into the incident and will make details of the failure known to industry stakeholders and regulators.
Mesh network issues being investigated
Like all engineered systems, vulnerabilities and risks with systems are ever present and theoretically should be engineered out to remove those risks, however, many mesh network engineers have identified that failures can still occur in mesh networks for a variety of complex reasons. FMG says it’s investigating why the mesh network breakdown occurred.
For now, Fortescue will move on
FMG’s investigation will be one to watch by the industry. AMSJ suspects that as autonomous systems evolve at a rapid rate, incidents of this ilk will also continue to evolve in complexity.
When a driver traditionally reversed into another vehicle in the past, the investigation was typically quite concise with causative factors quite clear. There wasn’t a need to check the amount of data being transferred through an ever-evolving and ageing mesh network that may have an increasing nodal failure rate. There wasn’t a need to check the efficacy of a sensor network, the speed of the packets of data or the actions of a controller in a control room. The times are a changing!
Meanwhile, the Department of Mines, Industry Regulation and Safety confirmed the incident had been reported and that it would review the company’s internal investigation report to determine what further actions might be required.
The Department’s Director of Mines Safety, Andrew Chaplyn, said he understood that information relating to the incident had been shared with Fortescue staff at pre-start meetings this week.
“Fortescue is co-operating with the department’s inquiries,” he said.
Image: Fortescue Metals Group Autonomous Truck Solomon
Read more Mining Safety News
Im a big fan of technology, but there are risks involved in any use of semi conductor based electronic systems.
Too often do we see UPS held up as being the saviour, although the reality is UPS offer no protection against lightning, in fact they are just as susceptible to lightning as the critical loads they support,
Solve this lightning issue and there is at least a fighting chance.
CAT system was promoted as being highly network resielent. This failure indicates not only the opposite, but a deep technical design weakness behind CAT AHS systems.
It would appear you are unfamiliar with how the CMD for hauling system works. the truck that was moving must have had network connectivity. the CAT system will stop an AMT after X seconds of no network connectivity .
So the truck reversing in to another vehicle has nothing to do with a network outage and more to do with vehicle perception system and or a failure in process
Thank you. I could not understand how motion continued with out connection.
The CAT CMD for hauling system stops any truck that does not have communications after x time.
If the vehicle is in motion then it had network connectivity. I would suggest that this is likely a perception issue or procedural issue