Industrial, IoT & Operational SystemsFleet telematics provider · 2019 MVP build

Electronic Logging Device Telematics Platform: Device Protocol, Mobile App and Web Portal Fleet telematics provider

A telematics company bringing an electronic logging device (ELD) product to market that needed the device protocol, driver app and fleet portal built as a coherent platform. The client is not named.

Duration: 2019 MVP build
Platform: Device protocol (G8), mobile application, web portal
Channels: IIoT telematics: device to dashboard

Scope, visualised

What the MVP platform includes

Platform layers: device, app, portal3
Protocol revision documented1.5.6
Development manual deliveredHandover
Capture
Monitor
Alert
Act
Report

Overview

Electronic logging devices sit in vehicles and report engine and driving data. Technovier built the platform around the G8 device: a versioned protocol document (revision 1.5.6) defining how the device communicates, a mobile application for drivers (account creation, login and daily use), a web portal for fleet operators, and a development manual so the platform could be extended. It was delivered as an MVP platform.

G8 ELD device protocol (rev 1.5.6), mobile application, web portal, developer handover manual

Problem, Constraints, Baseline, Approach, Results

Problem

Device data is only useful if it reaches drivers and fleet managers reliably; the hardware existed but the protocol, app and portal did not.

Constraints

The platform had to follow the G8 device's communication rules exactly and remain extensible by the client's own team afterwards.

Baseline

No application layer; device output could not be viewed or acted on outside the hardware itself.

Approach

A versioned protocol specification for device-to-platform communication, a driver mobile app designed screen by screen, a fleet web portal, and a development manual for handover.

Results

An MVP platform delivered with protocol, app, portal and documentation. Fleet-scale usage was not measured within the engagement, so no adoption or performance figures are claimed.

Handover

Development manual delivered

3

Platform layers: device, app, portal

1.5.6

Protocol revision documented

Handover

Development manual delivered

3

Platform layers: device, app, portal

Key metrics shown: 3 Platform layers: device, app, portal; 1.5.6 Protocol revision documented; Handover Development manual delivered.

Challenges

1. Protocol fidelity: Every message between the device and the platform had to match the hardware's rules; a versioned protocol document was the contract.
2. Two audiences, one data model: Drivers needed a simple daily app; fleet managers needed a portal over the same device data.

Responses

  • Versioned protocol document: Communication with the G8 device was specified and revised as a document (rev 1.5.6) so app, portal and firmware stayed aligned.
  • Driver app and fleet portal on one platform: Account creation, login and daily driver flows in the app; fleet views in the web portal; both reading the same device data.
  • Development manual for handover: The client's team received a manual to extend the platform after the MVP.

Why it matters for IIoT

Device → protocol → cloud → app and portal is the canonical IIoT shape. This project built every layer of it for vehicle telematics; the same structure carries sensor, meter and machine data in industrial monitoring.

Protocol as the contract: Treating the device protocol as a versioned document is what keeps hardware and software teams aligned, in fleets or on a plant floor.

Conclusion

A device-to-dashboard telematics platform delivered as an MVP: protocol, driver app, fleet portal and handover documentation. It is Technovier's reference point for IIoT and remote-monitoring builds.

Your operation is next

One view from the field to the executive's phone.

Tell us about the plant, fleet or network you run and we'll scope the supervisory layer on a discovery call, no pitch deck.

Questions about this system

Frequently Asked Questions

Hardware in the vehicle reports engine and driving data through a defined protocol; a mobile app serves drivers and a web portal serves fleet operators, all over the same data. This project built that platform around the G8 device.
It was delivered as an MVP platform with protocol, app, portal and a development manual. Fleet-scale usage was not measured within the engagement, so this case study reports scope only.