TELEMATICS TALKS - EPISODE 11 Guest: Kseniya, Marketing Team, Teltonika Telematics Host: Vlad, Vice President of Operations, Navixy Topic: E-Mobility, Mixed Fleets, GNSS Accuracy & Dead Reckoning ═══════════════════════════════════════════════════════════════════════════════ Vlad: Hello everyone, and welcome back to Telematics Talks. I'm Vlad, Operations VP at Navixy. Today's episode is special because we're diving into one of the hottest shifts in fleet tech right now: mobility. As many of you know, a lot of our customers are running mixed fleets — EVs alongside ICE vehicles — and they're balancing charging uptime and sustainability targets while still demanding rock-solid location data in dense cities, tunnels, and underground parking. That's where great hardware, clean data, insights, and platform integrations make or break the deployment. Joining me is Kseniya from the Teltonika marketing team — a brand many of you trust for rugged, easy-to-deploy devices across everything from delivery vans to e-bikes and industrial EVs. And by the way, at one of the conferences I saw you live in a band — totally unexpected! In this conversation, we'll dig into what "EV-ready" really means on both the device and CAN side, what's new for GNSS accuracy, multi-constellation L1/L5, and of course dead reckoning — which is especially interesting for urban canyons and tunnels. It's a pleasure to have you here. Thank you for joining us. My first question is: what drives you? What motivates you in what you do? ─────────────────────────────────────────────────────────────────────────────── Kseniya: Oh wow — we're starting very deep! I'd say I find telematics a really interesting niche. I work specifically with the telematics direction of the business, and it's exciting because there are so many use cases. Almost every project is unique, and for each client you need to find a special approach. I used to work in sales, now I'm in marketing, and the challenge I solve every day is: how do I communicate the message in a way that fits different markets we work in, and at the same time reaches the individuals who read our website, watch our videos, and so on. ─────────────────────────────────────────────────────────────────────────────── Vlad: Really interesting. Thank you for sharing that. Our partners are running mixed fleets. Usually they have traditional ICE vehicles that run on liquid fuel, and now they're switching a bit — or adding new units — that are EV-related. Ultimately, they need to manage both. So what helps you make that shift between light e-vehicles and heavy trucks or industrial vehicles? ─────────────────────────────────────────────────────────────────────────────── Kseniya: I'd say you need to be ready for different implementations of your devices. When designing a product, we look not only at the engine type, but at the use case. That's why, for example, we have OBD-reading devices that can read data from EVs and internal combustion engine vehicles as well. Or we have CAN-reading devices applicable for boats too. And if it's strictly about e-mobility — we also have devices designed specifically for that. So the secret is to consider not only the type of engine, but the overall use case. ─────────────────────────────────────────────────────────────────────────────── Vlad: That's probably a good tip for other manufacturers. So what's more essential in this case: the use case first, right? Or the model? ─────────────────────────────────────────────────────────────────────────────── Kseniya: I'd say the use case comes first, because it impacts everything: what size the device should be, what data needs to be read, what inputs and outputs to support, whether special standards are required, what certifications are needed in specific regions, and in EV cases — whether you need high-voltage support. ─────────────────────────────────────────────────────────────────────────────── Vlad: Let's put it another way: imagine someone who hasn't adopted the technology yet. Local partners are curious and eager to find new opportunities, but it's new and it feels scary. What would you recommend as a starting point? ─────────────────────────────────────────────────────────────────────────────── Kseniya: I totally understand. We go through the same feeling when we design any new product — it's exciting, but you always have concerns. First, you need to analyze the local context of the country you're working in. What industries are booming in your region? What businesses can you serve? And especially — what is the local regulation? When it comes to EVs, some countries mandate emission levels or have sustainability goals. That becomes a major driver for the market. So I'd recommend looking at what's going on locally, and considering emerging businesses that use electric vehicles — like car sharing, last-mile delivery, and personal micromobility. For example, I live in Vilnius, Lithuania. Scooters are part of daily life here. As soon as spring starts, you see scooters everywhere because they let you bypass traffic jams. So I'd suggest starting with local reality and local demand. ─────────────────────────────────────────────────────────────────────────────── Vlad: Thank you. If you had to identify a quick-win use case — a success story that helps the audience understand how to start — what would it be? ─────────────────────────────────────────────────────────────────────────────── Kseniya: One of my favorites is e-bike and e-scooter sharing services. We see more and more of them, and they're actively looking for e-mobility solutions because they want to be electric and sustainable. My suggestion is to approach the business and understand the pain points. Are you operating in a city like Dubai with skyscrapers — where you don't reliably see satellites? Then you need a solution for that. Do you know the habits of your users? Do you know where parking spots should be for rental bikes? Telematics can solve that. It's also important to understand what kind of vehicles they use: kick scooters, e-bikes, a mixed fleet, maybe even other vehicle types. That's how you put the puzzle together. ─────────────────────────────────────────────────────────────────────────────── Vlad: Designing hardware for EV isn't just about changing the power profile. CAN data speaks different languages and varies by model, and firmware needs to keep up — especially as more light EVs join mixed fleets and integration/testing demands grow. So what was the main challenge for you in making these integrations work? Power range? CAN data differences across models? Firmware changes? ─────────────────────────────────────────────────────────────────────────────── Kseniya: We've learned to work with high voltages for quite some time, so that part was fun. For data integration, we chose an interesting approach for our e-mobility device: we give partners — solution providers and companies integrating devices in the field — the possibility to specify, based on the vehicle's data communication protocol, what parameters should be collected. This gives them freedom to work with specific EV models, register those parameters in device configuration, and even avoid sharing the protocol with us — which is important when protocols can't be shared for confidentiality reasons. So the partner holds full information about the integration, and we provide the tools. At the same time, for the most common vehicles and basic parameters, we already have supported integrations — where we do the integration and provide a clear list of supported models and parameters. ─────────────────────────────────────────────────────────────────────────────── Vlad: So you provide supported models — and for others, partners can configure it themselves? ─────────────────────────────────────────────────────────────────────────────── Kseniya: Exactly. And we started doing this in the previous generation already, so we've been working this way for some time. ─────────────────────────────────────────────────────────────────────────────── Vlad: What about firmware updates? What happens if you're halfway through deployment and the OEM updates the firmware? ─────────────────────────────────────────────────────────────────────────────── Kseniya: It happens. The only way to handle it is to be able to update the devices over-the-air. Without that, it would be extremely hard to maintain hundreds of thousands of devices in the field. That's why we provide partners a platform to update device firmware and change configuration remotely. For our latest e-mobility devices, configuration is key — and we give partners tools to update online and implement changes. ─────────────────────────────────────────────────────────────────────────────── Vlad: Makes sense — otherwise you'd be running into the field every time, which is impossible, especially with scooters. And when you work directly with OEMs, do they provide protocols and updates, so you're prepared? ─────────────────────────────────────────────────────────────────────────────── Kseniya: It depends. Sometimes there is tight cooperation for specific use cases, and sometimes special solutions are created to fit a partner's needs. But OTA updates are always available. If we choose between a standard protocol that fits most cases versus something very specific that requires extra libraries — that choice depends on the use case. We always try to dig deeper: what kind of vehicles, light commercial, two-wheelers, special machinery, construction, and so on. Based on that, we provide the right solution. And for our CAN-reading devices, we have libraries with lists of supported vehicles and parameters — partners can choose what they want. ─────────────────────────────────────────────────────────────────────────────── Vlad: I totally agree — there's no universal solution in telematics. Businesses differ, even in the same industry: regulations differ, company size differs, the daily problems differ. You always need to adapt to the specific business, not just ship a box. Now, sustainability targets aren't just dashboard talk — they show up in daily routing, charging behavior, asset mix, and maintenance. Stakeholders want measurable CO₂ savings and operational KPIs, not anecdotes. So what are the main KPIs your customers put in front of their managers? What problems are they bracing for, and what do they need to show? ─────────────────────────────────────────────────────────────────────────────── Kseniya: It depends a lot on the country and region. For example, in the European Union there are CO₂ emission targets that businesses need to respect. In other regions, targets may be different — but sustainability goals are still spreading. Even in Saudi Arabia, in Vision 2030, there is a push toward electrification of fleets. Telematics provides visibility and allows businesses to compare costs of fuel vehicles versus electric vehicles — and decide what is more beneficial in their country, under their regulation, and even under their temperature conditions. Transitioning to EVs can be challenging in cold regions, for example. Businesses want to see: "I'm investing X money into fleet electrification — what mileage do I get, how often do I need to charge, and what does it look like compared to fuel cost?" We enable those calculations and comparisons. But ultimately, the question is: what goals does the business have? ─────────────────────────────────────────────────────────────────────────────── Vlad: Exactly. And in a mixed fleet, there's always a comparison — ICE versus EV — and stakeholders want real numbers. That means both fleets need advanced telematics. ─────────────────────────────────────────────────────────────────────────────── Kseniya: Absolutely. If you're a solution provider serving a mixed fleet — ICE and EV — you want to provide a solution that fits both. You don't want to rethink your device choice every time a new vehicle type appears. That's what we're aiming for with convergent devices. ─────────────────────────────────────────────────────────────────────────────── Vlad: Could you give an example of what dashboards should include — something easy to set up in the first week of testing? ─────────────────────────────────────────────────────────────────────────────── Kseniya: Dashboards are your space — I'll be happy to see what you build. But from my side, it's very important to monitor state of charge and state of health of batteries, plus charging habits of users. If batteries aren't charged properly, it impacts performance and battery lifespan — and battery replacement costs money. So state of health is crucial. Also, for EVs, uptime is different: if the battery dies, the vehicle stops — and the device may stop reporting too. Another useful platform feature is showing the nearest charging stations. Fuel stations are easy — charging stations are not always available, especially outside urban areas. Planning routes and expected mileage often depends on knowing where the next charging station is. ─────────────────────────────────────────────────────────────────────────────── Vlad: Since you mentioned scooters as a strong use case: would you recommend an external backup battery for the device? If the scooter battery dies, the device stops reporting and maintenance can't find it. ─────────────────────────────────────────────────────────────────────────────── Kseniya: Yes, 100%. I'd recommend an external battery because you want to track a scooter not only during trips, but also when it's parked — especially for sharing and rental businesses. Imagine the scooter is parked and it gets stolen. If there's no power, you lose visibility. So even though it makes the solution more expensive, it's worth it. It's an investment in visibility, security, and business stability — because you want scooters and e-bikes available for users. ─────────────────────────────────────────────────────────────────────────────── Vlad: Looking ahead to 2026: where should Teltonika focus? More CAN data, more platform reach, charging stations, connectivity — what's your strategy? ─────────────────────────────────────────────────────────────────────────────── Kseniya: Definitely richer CAN data. We've been working on it for a long time in our CAN-reading devices and our e-mobility series. We want to expand the list of integrations with different brands, give partners not only the ability to set up integrations themselves, but also provide a list of supported vehicles to choose from. That's a key direction for our e-mobility team for 2026. ─────────────────────────────────────────────────────────────────────────────── Vlad: And if you had to place a bet on growth areas — not brands, but industries or niches — what would grow most? Forklifts in warehouses? Two-wheelers? Something else? ─────────────────────────────────────────────────────────────────────────────── Kseniya: We'll definitely see growth not only in two-wheelers, but also in forklifts, and other four-wheelers like golf carts and recreational vehicles — many of them are electric now. We see a niche there for us and for our partners. We also see countries investing in converting two-wheelers from combustion to electric — for example, in Southeast Asia, including Indonesia, which is a manufacturing hub for two-wheelers. We see strong potential there too. ─────────────────────────────────────────────────────────────────────────────── Vlad: What do you think is the main driver for that — compliance-based decisions? ─────────────────────────────────────────────────────────────────────────────── Kseniya: Compliance is the easiest path for solution providers — if clients are obligated to use it, that's a clear win. But it's not only compliance. It's also consumer consciousness. People increasingly care whether suppliers are sustainable, what their carbon footprint is, what their impact on global warming is. That pushes businesses to go electric even when regulation isn't strong. ─────────────────────────────────────────────────────────────────────────────── Vlad: Do these projects usually come from end users, or from proactive solution providers? ─────────────────────────────────────────────────────────────────────────────── Kseniya: We'd definitely like to see proactivity from solution providers. They have expertise and can show fleet owners what can be achieved, because our field can be complicated and businesses don't always have a clear picture of what telematics can deliver. If we want industry growth, the ball is on the side of solution providers. ─────────────────────────────────────────────────────────────────────────────── Vlad: Location accuracy is another big challenge — especially in buildings, tunnels, and underground parking. "Good enough" location causes headaches when geofencing, billing, or delivery windows depend on precision. So what's new under the hood for improved accuracy — and what reduces drift? ─────────────────────────────────────────────────────────────────────────────── Kseniya: To know everything "under the hood," you should talk to our engineers — they'll be happy to explain. But when we worked on the platform, we understood customers expect higher accuracy for exactly those use cases. We focused on two things. First: increasing the number of satellites visible. The latest generation can track more than 40 satellites at the same time. Second: dead reckoning — technology that tracks the vehicle even without satellite coordinates, using a gyro and accelerometer to estimate where the vehicle or two-wheeler is moving. ─────────────────────────────────────────────────────────────────────────────── Vlad: That's really interesting — especially because GPS jamming devices exist and can block satellite signals completely. In that case satellites can drop to zero, but the device can still show movement because of dead reckoning. ─────────────────────────────────────────────────────────────────────────────── Kseniya: Yes, but it won't be 100% accurate — it's still estimation based on gyro and accelerometer. However, for use cases like stolen vehicle recovery, a few meters difference often doesn't matter. If you can map the track at some level of precision, you can recover the stolen vehicle. And it's not only about theft. It's also for city telematics in places like Dubai, where skyscrapers make satellite visibility difficult. Dead reckoning helps with last-mile delivery, locating rented vehicles, and more. ─────────────────────────────────────────────────────────────────────────────── Vlad: Partners also ask what's behind the dead reckoning technology. ─────────────────────────────────────────────────────────────────────────────── Kseniya: It's essentially the device's "brain" using the accelerometer and three axes to estimate movement direction. The computation happens inside the device — without sending data to the cloud — and then estimated coordinates are sent to the fleet management platform the same way as real satellite coordinates. ─────────────────────────────────────────────────────────────────────────────── Vlad: So even when satellites are at zero, the platform still shows the track — that's an amazing workaround. Now, do you have any success stories already using dead reckoning? ─────────────────────────────────────────────────────────────────────────────── Kseniya: Dead reckoning is a brand-new feature for us. It's not available to the general public yet — we're showing it only to a limited group of partners. So there are no success stories yet. But when it comes to precision and the increased number of satellites, we do have a strong use case: a sharing service in the Middle East. Precision mattered a lot because of area density, and it helped them increase efficiency drastically. They could see exactly where scooters and e-bikes were parked, analyze user behavior, understand where demand was highest, and place parking spots accordingly. The last time we asked, they told us they grew by 27% thanks to this solution. ─────────────────────────────────────────────────────────────────────────────── Vlad: Thank you — that really highlights how precision matters for both the operator and the end user. Imagine using an app to find your rented vehicle and seeing "somewhere around here" — that's not a great experience. Kseniya, thank you for sharing your perspective. We covered a lot today — from making EV fleets practical with battery insights and charging operations, to staying online through dense cities and patchy coverage, and how multi-constellation GNSS plus dead reckoning can provide clean location data. Before we wrap, what would be your advice to a software provider — what should they focus on when working with hardware and telematics data? ─────────────────────────────────────────────────────────────────────────────── Kseniya: If I could ask for one thing, it would be staying in touch with us. Dialogue between hardware and software partners is crucial, because we need to work together to provide a full solution for the end customer. If you have a project and you don't have the right hardware partner — come to us, we'll help figure it out. If you struggle with our devices — come to us, and we'll solve it. Dialogue is the key thing I'd ask from software partners. Luckily, we already have that with many of you, and with Navixy as well — and we'd like to continue in the same direction. ─────────────────────────────────────────────────────────────────────────────── Vlad: Thank you very much. And thanks again to Kseniya for sharing how Teltonika is approaching e-mobility and delivering rock-solid GNSS accuracy and security. This has been Telematics Talks. Until next time — stay efficient, stay accurate, and keep moving. ═══════════════════════════════════════════════════════════════════════════════ Learn more: - Navixy: https://www.navixy.com - Teltonika Telematics: https://teltonika-gps.com - Watch this episode: https://www.youtube.com/watch?v=oDeopNcxm5o