15 Fleet, Movement & Maintenance
Service
Service create flow, service list, and service item setup.
Illustrations on this page are conceptual examples — not screenshots of the live system.
How you can use it
The same Fleet module supports different transport models — pick the scenarios that match your operation.
Service in daily operations
Service create flow, service list, and service item setup.
Vehicle & movement control
Service for fleet and workshop managers — typical in Bangladesh vehicle-heavy organisations.
Service plans per vehicle type
Teams use Service when they need service plans per vehicle type — without maintaining a separate spreadsheet or WhatsApp thread.
Due soon and overdue service…
Teams use Service when they need due soon and overdue service lists — without maintaining a separate spreadsheet or WhatsApp thread.
Benefits for your team
What improves when vehicle data lives in one place instead of spreadsheets and phone calls.
Service plans per vehicle type
Service helps because service plans per vehicle type — recorded inside the VMS audit trail instead of informal channels.
Due soon and overdue service…
Service helps because due soon and overdue service lists — recorded inside the VMS audit trail instead of informal channels.
Links to garage job cards
Service helps because links to garage job cards — recorded inside the VMS audit trail instead of informal channels.
Service history per asset
Service helps because service history per asset — recorded inside the VMS audit trail instead of informal channels.
Makes daily work easier
Less chasing, less re-entry, fewer surprises on the morning dispatch board.
- Service supports view, add, list, settings — so users do not jump between unrelated tools for the same task.
- Less manual follow-up: service plans per vehicle type
- Less manual follow-up: due soon and overdue service lists
- Less manual follow-up: links to garage job cards
- Branch-scoped access means local teams open Service without seeing other depots' records.
Multi-user & mobile-ready
Different roles see different slices — desktop for planning, mobile for field, dashboard for leadership.
- Operations lead (desktop)Plans and supervises Service with full register access, filters, and exports.
- Branch user (tablet / laptop)Works on branch-scoped Service records — no cross-branch data leakage.
- Field staff (mobile)Submits or confirms Service tasks from phone — limited permissions, faster updates.
- Manager / approverReviews exceptions, approvals, and summaries inside Service without re-keying data.
- Owner / executive (dashboard)Reads KPI widgets fed by Service — not day-to-day data entry screens.
Works with your other modules
Fleet is the vehicle master — other modules read from it so data stays consistent across the platform.
- Vehicle OwnersService and Vehicle Owners share the same platform data — no duplicate entry between modules.
- FleetVehicle master in Fleet feeds live status into Service.
- Vehicle AssetsService and Vehicle Assets share the same platform data — no duplicate entry between modules.
- GPS Location SharingLive movement from GPS sharing supports client updates tied to Service.
- PlaybackRoute replay evidence supports disputes managed in Service.
- ReportsReport hub aggregates Service metrics for branch and management packs.