From setup to launch: Building a solution with Wialon Platform

Mixed fleet management: Bringing owned, leased, and rented vehicles into one solution

Cover

Consider a delivery company adding rented vans for a seasonal peak. The fleet manager needs to assign them to deliveries alongside the company’s owned and leased vehicles, follow their trips, and keep track of when each van is due to be returned. The extra vans should become part of the daily operation without creating a separate management process.

As a fleet management solution provider, you may find that vehicles in the same fleet need different connections. Some already have compatible GPS trackers. Others may provide data through an original equipment manufacturer (OEM) system. Access to a rented vehicle’s data may need to be arranged with the rental company.

Your job is to bring these vehicles into a solution that supports your client’s daily work. With Wialon, you can connect compatible hardware and supported OEM data, configure the functionality the fleet team needs, and integrate the solution with the client’s other systems.

A unified fleet management solution helps your client plan work around vehicle availability and performance, regardless of who owns each vehicle.

Why mixed ownership complicates fleet management

A mixed fleet can include different brands, vehicle types, and powertrains. Here, the distinction is ownership: vehicles the business owns, leases, or rents. The terms of these arrangements can affect permission to install equipment, access to data, and the length of time each vehicle remains in the solution.

A rented van may already have a GPS tracker, but the fleet operator may not have access to its data. A leased vehicle may supply location and mileage but lack the fuel measurements required for a particular task. These differences affect which functions you can configure and where another data source is needed.

Trucks Various Sizes Road 1
Ownership does not determine the technology: leased vehicles can use aftermarket trackers, and owned vehicles can supply OEM data. Check the equipment and access conditions for each group, then decide how to include those vehicles in the client’s fleet management system.

This allows you to retain compatible equipment instead of assuming every vehicle needs a new tracker. It also helps identify vehicles that cannot support the requested functions through their existing connections.

Define how the client will manage the whole fleet

Start with your client’s daily operation. For the seasonal delivery fleet, dispatchers may need current vehicle locations and trip status, while the fleet manager needs mileage and service information. Agree with the client which tasks the solution must support across the fleet.

That agreement should distinguish essential functions from additional requirements. Following vehicle movements requires location data, while detailed fuel monitoring may require additional readings or sensors. Give the fleet team consistent ways to work with its vehicles, and explain where coverage differs.

For the delivery company, the initial setup could cover adding the rented vans to the vehicle list, following their trips, and including their mileage in fleet reports. More specialized functions can follow once you have confirmed that the required data is available.

Match each vehicle to the right connection

With those tasks agreed, check which readings each connection must supply and how frequently. Installation permissions, data access, and connectivity will help determine which connection suits each vehicle.

Aftermarket telematics uses trackers and sensors installed after manufacture. It allows you to select equipment for the job, such as location tracking or fuel-level measurement. If the client’s existing trackers are compatible with Wialon, you can use them as part of the solution.

OEM telematics uses connectivity built into the vehicle by its manufacturer. Where the required data and authorized access are available, you may be able to connect a vehicle without another installation. Supported OEM data can also be brought into Wialon; the available readings depend on the brand, model, and selected data package.

__CTA_BANNER_OEMEN__

The connection must suit the task. Periodic odometer readings may support maintenance planning and monthly mileage analysis, but dispatchers assigning the nearest vehicle need recent location data. Explain these differences before presenting the vehicles together in one interface.

Without a live data feed, you cannot track a vehicle in real time. Dated manual readings or periodic imports may still support maintenance and cost analysis where appropriate. The solution should clearly distinguish those records from current vehicle data.

Connect daily fleet management with the wider business

Once the vehicles are connected, use consistent vehicle names, groups, and mileage sources so dispatchers and managers can work across the fleet without having to interpret each data source separately.

A tracker may identify a van by device ID, the workshop by registration number, and the rental company by contract reference. These identifiers need to stay linked to the same vehicle, even if its tracker is replaced.

Wialon gives your client a common environment for managing vehicle activity, monitoring fuel consumption, and planning maintenance. Flexible reports let fleet managers analyze how different groups of vehicles are used, investigate unusual activity, and review operating costs. For a mixed fleet, this helps bring owned, leased, and rented vehicles into the same management processes, according to the data available for each vehicle.

Integrations extend that work to information held in the client’s other systems. For example, you can connect mileage and vehicle activity from Wialon with lease payments and rental charges in an accounting or enterprise resource planning (ERP) system. You configure how those records are matched, while the client’s finance team agrees which expenses to include and how to allocate them. This connects fleet management with financial planning and helps the client assess the cost of the capacity they use.

__CTA_BANNER_API00EN__

For the seasonal fleet, this gives the fleet manager a way to compare the rented vans’ use and costs with the permanent fleet. Alongside expected demand, that comparison helps inform whether to keep the vans for another month. A complete total cost of ownership calculation would require all relevant expenses.

Test in daily use and plan for fleet changes

Include vehicles from the different ownership groups and data sources. Dispatchers and fleet managers can test the agreed functions in their normal work, including what happens when readings arrive late or a vehicle stops transmitting.

The review should cover both daily use and analysis. Can dispatchers follow the vehicles needed for the day’s work? Are missing readings obvious? Can the fleet manager review trips and mileage for the agreed period? You can address those gaps before extending the solution to more vehicles.

The service also needs to accommodate vehicles leaving or joining the fleet. When a rental is returned or a tracker moves to another van, historical readings must remain associated with the correct vehicle. Agree with your client who reports these changes, checks connections, and investigates interrupted data.

Your service includes maintaining connections and configurations as well as reports. Defining these responsibilities up front also helps you plan and price ongoing support.

Build the solution with Wialon

Wialon supports over 4,100 GPS device models, allowing you to retain compatible trackers and choose supported equipment where additional readings are needed. Supported OEM data can also reach Wialon, with available readings depending on the vehicle and selected data package.

Wialon lets you monitor vehicle activity and configure reports on fuel consumption, maintenance, and related costs. Integrations can connect this operational information with your client’s business software.

For example, Wialon partner UMT connected Wialon with Zammler Kazakhstan’s ERP system. Dispatchers previously copied arrival times and checkpoint visits into the ERP manually. UMT automated the transfer, so dispatchers could follow trip progress in the ERP without entering the information again.

__CTA_BANNER_ZAMMLERCASEEN__

For the delivery company, this means dispatchers can follow rented vans alongside the permanent fleet. Integrations can reduce repeated data entry and switching between systems. The fleet manager can compare how different groups of vehicles are used and assess their costs when deciding whether to extend a rental or add more capacity.

For you, this is an opportunity to build a service that grows with the client. Start with the functions the fleet relies on, retain compatible equipment, and add capabilities as requirements change.

Build fleet management solutions for the full range of vehicles your clients operate. Request a demo to explore how Wialon’s device compatibility, supported OEM data, and integrations can help expand your fleet digitalization offering.

Oem Cover (1)

Wialon adds support for OEM vehicle data through High Mobility

Read the article
0 1 1280x720

How APIs power fully integrated fleet management solutions

Read the article
Tmpzddnhh7g

Automation of trip management via ERP for a logistics company in Kazakhstan

Explore the full story

Frequently asked questions

What is a mixed fleet?

A mixed fleet combines different ownership arrangements, brands, vehicle types, or powertrains. In ownership terms, it includes owned, leased, and rented vehicles. Their operators need to manage those vehicles together despite differences in contracts, data access, and available equipment.

Why is it hard to manage a mixed fleet in one system?

Vehicles may use trackers or OEM connections that differ in their available readings, update intervals, and access conditions. The provider needs to connect supported sources and configure them around the fleet’s daily tasks. Integrations can then connect vehicle activity with maintenance, financial, or other business records.

What is the difference between owned, leased, and rented fleet data?

Ownership alone does not determine the data available. Equipment, connectivity, and permissions determine which readings the fleet can receive. Ownership arrangements affect the associated costs and may limit hardware installation or data access, particularly when a lease or rental agreement ends.

What is aftermarket versus OEM telematics data?

Aftermarket data comes from trackers or sensors installed after manufacture. OEM data comes through connectivity built into the vehicle by its manufacturer. Available readings and update intervals vary, so providers should check whether each source supports the client’s intended reports and daily tasks.

How does mixed fleet data affect total cost of ownership?

Scattered records make it harder to match expenses to the correct vehicle and period. Missing mileage or double-counted services can distort comparisons. Connecting operational and financial records helps, but a total cost of ownership calculation still needs to include all relevant expenses.

Can one system track owned, leased, and rented vehicles together?

Yes. Wialon can combine supported trackers and authorized OEM data feeds for fleet management. Available functions depend on the readings and update intervals each source provides. Vehicles without a live feed cannot be tracked live, but dated periodic readings may still support retrospective analysis.

6414342930e61

Alena Kalionava

Alena is the Content Marketing Team Lead at Wialon. She leads a talented team that produces a wide range of content — from blog posts and case studies to dynamic presentations — that empower and inform Wialon partners and fleet managers alike.

Related articles