With CloudConnect from Invers, an API aggregator is now available to give shared mobility operators access to telematics units from different vehicle manufacturers, vehicle models and form factors such as cars, scooters, kick scooters or e-bikes, via a single application programming interface (API) and connect them to their sharing software. This allows operators to strategically build up their vehicle offerings without being restricted by technical limitations. “It is becoming increasingly important for our customers to have the flexibility to integrate different vehicles into their fleet, whether they are factory-equipped with telematics by the manufacturer or have already been retrofitted with an after-market solution from a telematics provider,” explains Alexander Kirn, CEO of INVERS. “With CloudConnect, we offer a solution that allows operators to communicate with telematics units and APIs from different manufacturers via the unified OneAPI interface. We focused on ensuring developers can use our solution quickly and easily by providing very detailed documentation on our website.”
Telematics units that make vehicles sharing ready, i.e., ready for use in shared mobility services, use different command and response types, as well as data structures, to communicate and receive data from the vehicle directly or via the cloud. When operators want to add a new vehicle with a different telematics to their fleet, integration is often a complex process for developers that requires a lot of time and resources. For each telematics, there is a need to understand the interface and figure out how commands and information are structured. CloudConnect simplifies this process by acting as an API aggregator that can communicate with different telematics models and APIs, translating them into generic interface format and standardized data, making them usable by fleet management and mobility services from one central location. In this way, CloudConnect significantly reduces development effort because developers do not have to implement each individual interface via a separate connection. Similarly, the solution reduces time-to-market during implementation and complexity in ongoing operations because developers only need to work with one uniform interface.
SOURCE: INVERS
