Start Your VTS Business With Enterprise-Ready Technology

Project Overview

The project focused on digitizing and automating fleet operations for the Bangladesh Petroleum Corporation (BPC) to monitor tank lorry and oil tanker movements nationwide.

Previously, manual record-keeping made it difficult to track deliveries, leading to security risks, system loss, and frequent delays.

Kolpolok Limited developed a Fleet Management System with real-time GPS tracking, smart reporting, and centralized oversight, giving BPC complete visibility, enhanced security, and measurable cost efficiency across its fuel transport network.

Project Timeline

Project Kickoff : July 16, 2024
Design & Development : 2024 – 2025
Testing & Deployment :Mid 2025
Maintenance Phase : 2025 – Ongoing
Contract Duration : 3 Years (with continuous system maintenance & enhancements)

Problem Statement

Before implementation, BPC’s logistics network faced several long-standing issues:

• Manual fleet tracking with no unified dashboard.
• Inability to verify real-time tanker routes and delivery statuses.
• Frequent fuel theft, unauthorized detours, and delayed shipments.
• Limited data visibility and reporting inefficiency.
• High operational costs due to system loss and lack of automation.

Solutions

Kolpolok Limited developed a smart web and mobile-based Fleet Management System tailored to BPC’s structure.

Key highlights of the solution:

• Technology Stack: Laravel (Backend), React (Frontend), Flutter (Mobile), integrated with REST APIs and real-time telemetry.
• Core Modules: Fleet Tracking, Geo-Fencing, Analytics Dashboard, Trip Logs, Fuel Consumption Reports, and Automated Alerts.
• Integrations: Google Maps API for live tracking, SMS gateways for notifications, and IoT-based vehicle sensors for telemetry data.
• Automation: Automated route monitoring, fuel-level tracking, maintenance scheduling, and performance summaries.

Features

• Real-time GPS tracking of tank lorries and oil tankers.
• Intelligent dashboard for centralized management.
• Route optimization and scheduling tools.
• Automated reports for performance and deliveries.
• IoT telemetry for live sensor data.
• Secure role-based access for admin and users.
• Data-driven analytics for fuel consumption and delivery patterns.
• Offline/online sync support for field officers.
• Comprehensive mobile access for on-the-go updates.

Goals

The core mission of the project was to minimize fuel system loss, strengthen transportation security, and ensure data-backed reporting for all petroleum subsidiaries.

Key Objectives & KPIs:

• Reduce system loss
• Monitor 100% of fleet movements in real time.
• Generate automated performance and delivery reports daily.
• Improve security visibility across depots and routes.
• Enable proactive maintenance to prevent delays.

Final Product

At the handover stage, Kolpolok Limited delivered:

• A fully functional web and mobile application for live fleet monitoring.
• Training and user documentation for all BPC departments.
• Ongoing maintenance and SLA-based technical support.
• Integration with existing IT infrastructure for smoother data exchange.

Results / Outcomes

Since deployment, BPC’s fleet management operations have seen measurable impact:

• Significant reduction in unauthorized fuel movement and delays.
• Faster decision-making with real-time reporting dashboards.
• Enhanced transparency between transport divisions.
• Cost savings from reduced manual monitoring and losses.
• Improved data accountability across all petroleum subsidiaries.
• Thousands of fleet trips are now tracked monthly with digital accuracy.

Project Overview

Purpose: Build an own telematics platform that supports multi-protocol GPS/IoT devices, real-time tracking, sensor analytics, and enterprise reporting.

Business Processes Covered: VTS, VMS, telemetry ingestion, route/geo-zone control, alerts, reporting, billing hooks.

Build Type: New build (from scratch) to replace legacy listeners that couldn’t scale with new protocols.

Project Timeline

Duration: 6 months to MVP; ongoing hardening and UAT
Phases: Architecture → Development → QA → UAT → Deployment → Optimization

Problem Statement

Existing stacks could not ingest diverse device protocols or handle protocol/version drift, causing data loss, latency spikes, and unreliable tracking. Result: visibility gaps, delayed alerts, and higher support load.

Solutions

• Tech Stack: Laravel, React, Go, C++, Apache Kafka, MongoDB, PostgreSQL, Redis, RabbitMQ
• Core Systems: High-throughput Telematics Listener (Go/C++), scalable Web Platform (Laravel/React)
• Integrations: Map APIs, SMS gateway, Payment gateway
• Automation: Stream processing for event detection, auto alert routing, scheduled report jobs, health checks

Features

• Fleet GPS integration with multi-device protocol adapter
• Live tracking (status, route, speed), trip history, geo-fencing & geo-zones
• Sensor streams (fuel, temp, load) with threshold alerts
• Multi-level dashboards & reports (distance, fuel, halt, speed, occupancy, expense)
• Role-based access (admin, ops, viewer), org & group management
• Data pipeline with Kafka for scale; Redis for low-latency reads
• Offline-tolerant data capture (device-side) and safe replays
• Billing hooks (package/usage ready), export & APIs

Goals

• Zero-loss ingestion across diverse GPS/IoT devices
• Low-latency updates for live tracking and alerts
• Enterprise-grade stability for transport/logistics and public sector
• Admin efficiency via dashboards, scheduled reports, and RBAC

KPIs Targeted

Ingestion reliability, end-to-end event latency, dashboard load time, alert delivery time, device/protocol coverage, uptime/SLA.

Final Product

• Production-ready web platform + telematics listener services
• UAT completion, deployment scripts, environment playbooks
• Technical documentation (APIs, protocol mapping, ops runbooks)
• SLA-based maintenance & support options

Results / Outcomes

• Stable real-time tracking with protocol-agnostic ingestion
• Faster alerting & reports, fewer manual reconciliations
• Easier onboarding of new devices and vendors
• Lower ops overhead through automation and clear observability

Project Overview

Purpose: Build an own telematics platform that supports multi-protocol GPS/IoT devices, real-time tracking, sensor analytics, and enterprise reporting.

Business Processes Covered: VTS, VMS, telemetry ingestion, route/geo-zone control, alerts, reporting, billing hooks.

Build Type: New build (from scratch) to replace legacy listeners that couldn’t scale with new protocols.

Project Timeline

Duration: 6 months to MVP; ongoing hardening and UAT
Phases: Architecture → Development → QA → UAT → Deployment → Optimization

Problem Statement

Existing stacks could not ingest diverse device protocols or handle protocol/version drift, causing data loss, latency spikes, and unreliable tracking. Result: visibility gaps, delayed alerts, and higher support load.

Solutions

• Tech Stack: Laravel, React, Go, C++, Apache Kafka, MongoDB, PostgreSQL, Redis, RabbitMQ
• Core Systems: High-throughput Telematics Listener (Go/C++), scalable Web Platform (Laravel/React)
• Integrations: Map APIs, SMS gateway, Payment gateway
• Automation: Stream processing for event detection, auto alert routing, scheduled report jobs, health checks

Features

• Fleet GPS integration with multi-device protocol adapter
• Live tracking (status, route, speed), trip history, geo-fencing & geo-zones
• Sensor streams (fuel, temp, load) with threshold alerts
• Multi-level dashboards & reports (distance, fuel, halt, speed, occupancy, expense)
• Role-based access (admin, ops, viewer), org & group management
• Data pipeline with Kafka for scale; Redis for low-latency reads
• Offline-tolerant data capture (device-side) and safe replays
• Billing hooks (package/usage ready), export & APIs

Goals

• Zero-loss ingestion across diverse GPS/IoT devices
• Low-latency updates for live tracking and alerts
• Enterprise-grade stability for transport/logistics and public sector
• Admin efficiency via dashboards, scheduled reports, and RBAC

KPIs Targeted

Ingestion reliability, end-to-end event latency, dashboard load time, alert delivery time, device/protocol coverage, uptime/SLA.

Final Product

• Production-ready web platform + telematics listener services
• UAT completion, deployment scripts, environment playbooks
• Technical documentation (APIs, protocol mapping, ops runbooks)
• SLA-based maintenance & support options

Results / Outcomes

• Stable real-time tracking with protocol-agnostic ingestion
• Faster alerting & reports, fewer manual reconciliations
• Easier onboarding of new devices and vendors
• Lower ops overhead through automation and clear observability

Project Overview

Purpose: Build an own telematics platform that supports multi-protocol GPS/IoT devices, real-time tracking, sensor analytics, and enterprise reporting.

Business Processes Covered: VTS, VMS, telemetry ingestion, route/geo-zone control, alerts, reporting, billing hooks.

Build Type: New build (from scratch) to replace legacy listeners that couldn’t scale with new protocols.

Project Timeline

Duration: 6 months to MVP; ongoing hardening and UAT
Phases: Architecture → Development → QA → UAT → Deployment → Optimization

Problem Statement

Existing stacks could not ingest diverse device protocols or handle protocol/version drift, causing data loss, latency spikes, and unreliable tracking. Result: visibility gaps, delayed alerts, and higher support load.

Solutions

• Tech Stack: Laravel, React, Go, C++, Apache Kafka, MongoDB, PostgreSQL, Redis, RabbitMQ
• Core Systems: High-throughput Telematics Listener (Go/C++), scalable Web Platform (Laravel/React)
• Integrations: Map APIs, SMS gateway, Payment gateway
• Automation: Stream processing for event detection, auto alert routing, scheduled report jobs, health checks

Features

• Fleet GPS integration with multi-device protocol adapter
• Live tracking (status, route, speed), trip history, geo-fencing & geo-zones
• Sensor streams (fuel, temp, load) with threshold alerts
• Multi-level dashboards & reports (distance, fuel, halt, speed, occupancy, expense)
• Role-based access (admin, ops, viewer), org & group management
• Data pipeline with Kafka for scale; Redis for low-latency reads
• Offline-tolerant data capture (device-side) and safe replays
• Billing hooks (package/usage ready), export & APIs

Goals

• Zero-loss ingestion across diverse GPS/IoT devices
• Low-latency updates for live tracking and alerts
• Enterprise-grade stability for transport/logistics and public sector
• Admin efficiency via dashboards, scheduled reports, and RBAC

KPIs Targeted

Ingestion reliability, end-to-end event latency, dashboard load time, alert delivery time, device/protocol coverage, uptime/SLA.

Final Product

• Production-ready web platform + telematics listener services
• UAT completion, deployment scripts, environment playbooks
• Technical documentation (APIs, protocol mapping, ops runbooks)
• SLA-based maintenance & support options

Results / Outcomes

• Stable real-time tracking with protocol-agnostic ingestion
• Faster alerting & reports, fewer manual reconciliations
• Easier onboarding of new devices and vendors
• Lower ops overhead through automation and clear observability