Skip to content

R2I Protocol · Robot-to-Infrastructure

Deployment

We need nothing from your suppliers to get started.

Way in — retrofit
The node is mounted on the infrastructure that already exists. Software on the equipment if it can be updated; a gateway beside it if it is analogue. It is deployed by the integrator or maintainer the customer already has. We do not make the door smart: we put a smart doorkeeper in front of it.
The management systems
They connect through adapters, over the interfaces they already expose. No supplier has to modify their product.
The issuers
The customer issues credentials the way it issues accreditations today. Autonomous fleet operators integrate the issuer SDK out of self-interest — without verifiable identity, their asset does not get in.
Way forward — OEM
Once the protocol is rolling, manufacturers integrate it at the factory. The lever is not convincing the manufacturer: it is the customer demanding it in tenders and renewals (the precedent is OCPP in chargers). Customer traction activates manufacturers, never the other way round.

The pilot can start next month with what is already installed.