Modern vehicles already have the connectivity needed to produce valuable fleet data. The challenge has increasingly been how to get that data out of individual manufacturer ecosystems and into the platforms fleet operators actually use.
That just became easier.
Wialon has integrated OEM vehicle data through High Mobility and flespi, enabling its partners and customers to bring data directly from supported connected vehicles into the Wialon ecosystem without installing additional telematics hardware.
For fleets, this creates another route to connectivity. Instead of fitting a separate device to every supported vehicle, existing factory-fitted connectivity can be used to access data such as location, mileage, fuel or energy consumption, and vehicle status, depending on the manufacturer, model and selected data package.
From the vehicle to Wialon, without additional hardware
The principle behind the integration is straightforward.
Connected vehicles already transmit data to their manufacturers' cloud environments. High Mobility provides the layer that connects to these official OEM data sources and standardizes data from many automotive brands into a common format. flespi then provides the middleware that brings this data into Wialon, where it can be used alongside information from other vehicles and telematics devices.
The result is a much shorter path from factory-fitted vehicle connectivity to an operational fleet management platform.
For Wialon partners, this is particularly important. Supporting another vehicle brand no longer necessarily means developing and maintaining another individual OEM integration. High Mobility handles the OEM connectivity and standardization layer, while the resulting data can flow into an environment that Wialon users already know.
Hardware-free becomes easier to deploy across mixed fleets
Hardware-free telematics is not new. What is changing is how accessible it is becoming.
One of the biggest challenges for fleets has been fragmentation. A mixed fleet may contain Mercedes-Benz, Renault, Volvo, BMW, Volkswagen and other vehicles, each with different data interfaces, commercial arrangements and technical requirements.
High Mobility was built to remove much of this complexity. Rather than requiring businesses to establish and maintain separate integrations with every manufacturer, we provide one technical and commercial layer for accessing supported OEM vehicle data.
The Wialon integration takes this one step further. Fleet operators and telematics service providers already working in Wialon can now incorporate supported OEM data into their existing workflows rather than building a separate application around it.
This means OEM connectivity becomes another tool available to the fleet, alongside conventional telematics hardware.
Less installation, faster access to connected vehicles
The practical advantage is simple: if a compatible vehicle already contains the required connectivity, there may be no need to install another tracker purely to retrieve supported vehicle data.
That can remove physical installation work, reduce vehicle downtime during onboarding and make it easier to connect geographically distributed fleets. It can also be particularly useful when vehicles enter and leave a fleet frequently, because connectivity can increasingly become a software provisioning process rather than a hardware installation project.
There are still cases where dedicated telematics hardware is the right solution. Aftermarket devices can provide capabilities, update frequencies or additional sensor data that may not be available through a particular manufacturer's connected vehicle platform.
The important change is that fleets no longer have to treat hardware as the default for every vehicle.
Depending on the fleet, the best architecture may be OEM data, aftermarket hardware or a combination of both. Wialon's integration with High Mobility makes that hybrid approach considerably easier to manage within one ecosystem.
The EU Data Act is accelerating the change
This development also comes at an important point for vehicle data access in Europe.
The EU Data Act has applied since 12 September 2025 and establishes rights for users of connected products, including vehicles, to access data generated through their use and to make that data available to third parties of their choice. From 12 September 2026, an additional Article 3(1) requirement applies to connected products and related services placed on the market after that date, requiring product data and related service data to be accessible to users by default where relevant.
For the fleet industry, the direction is clear: access to vehicle-generated data is becoming less tied to closed manufacturer ecosystems.
But regulation alone does not solve the technical problem. Fleets still need a practical way to connect different manufacturers, normalize their data and make it usable inside the systems that run their operations.
That is where integrations such as High Mobility, flespi and Wialon become important.
Making OEM data part of everyday fleet management
At High Mobility, our focus has always been on making direct vehicle data usable beyond the OEM environment.
We connect to official manufacturer data sources, standardize different OEM formats into a consistent data model and provide the infrastructure needed to work with multi-brand connected fleets.
By bringing that infrastructure into Wialon through flespi, OEM data becomes accessible to another large ecosystem of fleet management providers and operators without requiring them to build the entire OEM connectivity layer themselves.
The vehicle already has the hardware. High Mobility provides access to the data. And with Wialon, that data can now become part of the fleet management environment businesses already use.
Interested in connecting your fleet or fleet management solution directly to OEM vehicle data? Get in touch with the High Mobility team to explore the available brands, data packages and integration options.
