Hitachi Construction Machinery and Pronto Sign an Open-Automation MoU: What It Commits, and What It Doesn't

By OpenAutonomy.com Editorial Team

On July 16, 2026, Hitachi Construction Machinery (HCM) and Pronto announced a memorandum of understanding to work together on what they describe as open automation for mining. The stated intent is to give operators more automation options built around the equipment they already run rather than a single closed system. It is a short document with a long implied to-do list, and, like most partnership news in this industry, it is easier to misread than it appears.

This piece does two things: it lays out what the MoU actually says, and it offers a way to read this announcement (and the next one, and the one after that) without getting ahead of the facts.

What was announced

HCM, the mining-equipment maker that has said it will move to the LANDCROS brand from April 2027, and Pronto, the autonomous-haulage company now part of Atoms, signed an MoU for a strategic partnership on open mine automation. HCM's president and executive officer is Masafumi Senzaki; Pronto is led by co-founder and CEO Anthony Levandowski. The companies frame the work around a familiar set of pressures: operators want automation that improves productivity and safety, works with mixed brownfield fleets, and doesn't lock them into one vendor. No products, deployment sites, timelines, or financial terms were announced.

What an MoU does, and doesn't, commit

An MoU is a statement of intent, not a contract. It records that two organizations plan to explore working together and sets a frame for that exploration. On its own it creates no binding obligations, names no deliverables, commits no spending, and does not guarantee that a further, binding agreement will follow. That isn't a criticism. An MoU is how large, cautious organizations open a door before deciding how far to walk through it. But it means the correct reading of this news is "direction," not "done." An MoU can precede a decade of joint product or quietly lapse, and nothing in the document itself tells you which.

What each side brings

HCM brings mining equipment sold worldwide, long operational experience, and an existing customer base — the machines, service network, and site relationships any rollout has to plug into. Pronto brings a retrofit autonomous-haulage system designed to run on haul trucks from different manufacturers, offered in a tiered range aimed at operations from quarries to deep-pit mines. Pronto reports commercial mixed-fleet deployments across three continents. Its lineup widened in 2025 when it acquired SafeAI, adding a multi-sensor, ISO 26262 ASIL D-certified safety layer to its camera-based system; Pronto itself became part of the physical-AI company Atoms in 2026.

Why this is happening now

Two forces sit behind announcements like this. The first is operational: most mines are brownfield, running mixed fleets of different makes and ages, so an automation approach that only works on one brand of new truck is a hard sell. The second is structural: the autonomy market is consolidating, with acquisitions and ownership changes reshaping who owns which stack. Pronto's own recent history is one instance of this. The standard underneath much of this is ISO 23725:2024, published in August 2024, which defines common protocols for data exchange between fleet-management systems and autonomous-haulage systems from different manufacturers.

One distinction is worth holding steady here: consolidation is not the same as closing off. A vendor can grow by acquisition and still support open, standard interfaces, since growth and openness are separate choices. Reading every merger as a step toward a walled garden is as much a mistake as assuming every "open" label is earned.

The question worth carrying into every "open" deal

This is where a reader adds the most to their own understanding. "Open" and "OEM-agnostic," in this announcement and most like it, mean one specific thing: the automation can be retrofitted onto trucks from more than one manufacturer. That is brand-agnostic compatibility at the vehicle level, and it is genuinely useful. It is also not the same property as interoperability in the ISO 23725 sense.

ISO 23725 interoperability is about the seam between components: a documented, standardized interface where a fleet-management system from one provider and an autonomous-haulage system from another can meet, exchange dispatch and telemetry, and be checked against a common protocol. Brand-agnostic retrofit is about the truck. A system can fit any truck brand and still be a single-vendor stack behind the FMS-to-AHS seam: open at the wheels, closed at the interface.

Neither is wrong. An integrated stack can be a sound engineering choice, and a brand-portable one beats a brand-locked one. But they answer different questions, and an MoU answers neither. So, the question OpenAutonomy.com carries into this deal is the one it carries into every deal that uses the word "open": when the joint work produces something real, will it expose a documented interface a third party could build against and audit, interoperable in the ISO 23725 sense, or will it be a stack that happens to fit many trucks while staying closed at the seam?

A few concrete things to watch as this moves from intent to deployment:

• Does anything shipped conform to, or map against, ISO 23725 at the FMS-to-AHS interface? Or claim "open" only at the vehicle level?

• Could a third-party FMS, drill-guidance, or positioning provider connect without a bespoke, private integration?

• Is the interface documented and available, or described only in marketing terms?

• Separately, does the safety case sit behind a defined, shared boundary, or inside a box only one vendor can see into?

None of these can be answered today, because there is nothing shipped to answer them about. That is the point of a beat like this: mark the announcement, note what it does and doesn't commit, and keep the question open until there is a product to test it against.