Transport Topics panelists put fleet AI data quality ahead of model selection
At the Technology & Maintenance Council AI Summit, BeyondTrucks CEO Hans Galland and PrePass CTO Chas Wurster argued that fleets should define the business problem and clean the underlying data before buying another AI product. Galland cited a carrier survey in which about 75% of fleets lacked a formal AI position, even though more than half were already using AI in some form.
The panel separated fleet AI into automation, decision support, and generative systems. The examples were practical: document processing, anomaly and failure prediction, route optimization, driver-assistance systems, and extracting information from bills of lading, all of which depend on time-, location-, vehicle-, and driver-linked records that legacy systems often capture inconsistently.
The message is a planning constraint rather than a technology forecast. A fleet can be surrounded by vendor features and still fail to produce a trustworthy maintenance, dispatch, or safety decision if its records are manually entered, closed to other systems, or not available in real time.
For a fleet executive, the scarce asset is not another model; it is a usable operating record that can support a decision across maintenance, safety, and dispatch.
Choose one decision such as unplanned downtime or load assignment, inventory the data required to make it, and test whether the current systems expose those fields with stable identifiers.
Fleet technology leaders should require every AI proposal to name its decision owner, data dependencies, human review point, and measurable operating outcome before approving a pilot.
Large fleets can establish a governed data architecture across regions; medium fleets can reconcile one operating lane; small fleets can start with a clean vehicle, driver, and work-order register before adding AI.