Requirement Analysis · Response to Demand Letter

Aman Group — TMS / FTS (ERP)
Transport Management Software: Requirement Analysis

Analysis of the Transport Department demand letter prepared by Engr. Joy Chandra Das (Sr. Manager, Head of Transport Maintenance, Operation, Logistics & Development)
ClientAman Group — Transport Department Analysed2026-07-11 SourceTMS/FTS (ERP) Demand Letter
Purpose of this document: The demand letter lists requirements as free-form notes across TMS, FTS, VTS, WMS, Store, and PDI. This analysis decodes those notes into a structured system, maps each requirement to a defined module, marks what is standard vs. Aman-specific, and highlights the gaps & clarifications needed before scope/costing.

1. Executive Summary

Aman Group runs a fleet of light and heavy vehicles across multiple concerns and wants a single ERP-grade platform to manage transport operation, maintenance, logistics and development. The letter is not a single "vehicle management" system — it is effectively six inter-connected sub-systems under one ERP:

TMSTransport Management

Freight/logistics operations: booking → loading manifest → dispatch → gate pass → unloading → receive → delivery → return trip → billing & account.

FTSFleet / Fuel Tracking

Spare-parts inventory, fuel tracking, log & repair history, maintenance scheduling, warranty/insurance, rental-vehicle trips.

VTSVehicle Tracking (GPS)

Live GPS/vehicle tracking with recurring notifications.

WMSWorkshop Management

Appointments, job cards, mechanic tracking via app, parts inventory, invoicing.

StoreSpare Parts / Store

SKU/QR cataloging, auto stock deduction on use, reorder alerts, procurement.

PDIPre-Delivery Inspection

New-vehicle inspection: paperwork/VIN, exterior, engine & fluids, interior/electronics, test drive.

Key characteristic: Nearly every module explicitly requires Daily / Weekly / Monthly / Yearly notifications & reports. This is a notification- and reporting-heavy system — the scheduling/alert engine and reporting engine are core, not add-ons.

2. Full Requirement Breakdown (extracted from the letter)

2.1 Vehicle Info Setup

Vehicle type & details · registration details · staff & driver profile · setup routes · route-based transport fare · scheduling routes with driver/staff · maintenance · workshop · store · unwanted goods · fuel consumption analysis · daily roster/operation vehicles · distribution · requisition · job-card · notification. Plus: store inventory / procurement / BRTA, repair & workshop maintenance, reports.

2.2 TMS Modules (each with daily/weekly/monthly/yearly notification)

VTS system · maintenance job card · booking · loading manifest · dispatch · unloading · receive · gate pass · delivery · return trip details · account · leader (loading crew) · fuel consumption · billing · vendor info · employee list · overtime schedule · vehicle field shift · requisition · driver's duty schedule · maintenance notification · store inventory · (other systems as needed).

2.3 FTS Modules

Spare parts inventory · fuel tracking · log & repair history · maintenance scheduling · warranty & insurance tracking (BRTA & new vehicle) · vehicle trip details (company inside & outside) · vehicle trip notification (rental vehicle purpose).

2.4 Workshop Management (WMS)

1. Appointments (digital calendar) · 2. Job cards (work orders) · 3. Mechanic tracking (technicians track time & progress via app) · 4. Parts inventory (auto-count & buy alert) · 5. Invoices & billing (job card → invoice).

2.5 Spare Parts / Store Management

1. Cataloging (SKU / QR code) · 2. Tracking (auto-subtract on use) · 3. Reordering (low-stock alert/order). Benefits cited: less downtime, cost control, efficiency. Reference tools named: Alldevice, Makula, Infraon.

2.6 PDI — Pre-Delivery Inspection (new vehicles)

1. Paperwork: VIN check, engine number, manufacturing date, odometer < 50 km · 2. Exterior: paint & body, glass, doors & trunk, tires · 3. Engine bay & fluids: oil & coolant, leaks, battery · 4. Interior & electronics: lights, AC/heating, infotainment, windows & mirrors, keys · 5. Test drive: steering & brakes, transmission.

2.7 TMS Reports (day/weekly/monthly/yearly)

1. Vehicle basic info (insurance, tax, fitness, route permit, number plate — auto renewal notification) · 2. Fuel/CNG consumption · 3. Maintenance requisition · 4. Maintenance report · 5. Billing · 6. Tax/fitness/insurance/route-permit notification · 7. Accidental case report · 8. Spare parts inventory · 9. Overtime schedule notification · 10. Return trip · 11. Central workshop · 12. Demand for additional vehicles · 13. More modules as per client desire.

3. Requirement → Module Mapping & Coverage

Covered already in our VMS scope Partial exists but needs Aman-specific extension New not in generic scope — build fresh

Aman RequirementMaps to ModuleStatusNotes
Vehicle type, registration, info setupVehicle ManagementCoveredDirect fit.
Staff & driver profile, duty schedule, roster, overtime, field shiftDriver + HR/RosterPartialDriver & roster covered; overtime, employee list, field-shift need HR-style extension.
VTS — live GPS trackingGPS Tracking & TelematicsCoveredCore tracking pipeline fits.
Setup routes + route-based transport fareRoute & TariffNewRoute master + fare/tariff per route not in generic scope.
Booking → loading manifest → dispatch → gate pass → unloading → receive → delivery → return tripTMS Freight OperationsNewBiggest addition. Full freight/logistics workflow — far beyond simple trip/dispatch.
Loader ("Leader") managementTMS Freight OperationsNewLoading crew tracking & assignment.
Maintenance, job card, maintenance scheduling & notificationMaintenanceCoveredPreventive schedules + work orders fit.
Workshop management (appointments, job card, mechanic app, invoicing)Workshop (WMS)PartialMaintenance covered; appointments calendar, mechanic time-tracking app, job-card→invoice need dedicated WMS.
Central workshop conceptWorkshop (WMS)NewMulti-workshop with one "central" hub & reporting.
Store / spare parts (SKU/QR, auto-deduct, reorder), procurementInventory / StorePartialInventory covered; QR issue-on-scan & procurement/PO flow to be extended.
Fuel / CNG consumption analysis & trackingFuel ManagementPartialFuel covered; add CNG as fuel type + analysis reports.
BRTA compliance: tax, fitness, route permit, number plate, insurance — auto renewalDocuments & CompliancePartialCompliance covered; needs BRTA-specific doc types & Bangladesh rules.
Warranty & insurance tracking (new vehicle / BRTA)Compliance + VehiclePartialWarranty field exists; tie to PDI & new-vehicle purchase.
PDI — pre-delivery inspection (new vehicles)PDINewEntire module new — 5-section digital checklist, pass/fail, photos, sign-off.
Rental vehicle trip details & notificationRental / TripNewSeparate handling & billing for rented vehicles.
Vehicle trip details — company inside & outsideTrip ManagementPartialTrip covered; add internal vs external classification.
Requisition (vehicle / maintenance / parts)Requisition WorkflowNewRequest → approval workflow across vehicle, maintenance, store.
Vendor infoVendor ManagementCoveredSupplier/vendor directory fits.
Account, billing, invoicingFinance / ERPPartialCost/expense covered; accounting & billing ledger = ERP integration.
Unwanted goodsScrap / DisposalNewTrack scrap/condemned goods & disposal.
DistributionTMS Freight OperationsNewGoods distribution to concerns/branches.
Demand for additional vehicles (report)ReportingNewCapacity/demand analysis report.
Accidental case reportIncident ManagementCoveredIncident/accident log fits.
All daily/weekly/monthly/yearly notifications & reportsNotification + Reporting EnginePartialEngine exists; must be scheduled & recurring on every module.
Coverage verdict: ~50% of Aman's ask maps directly to our existing VMS scope. The other ~50% is freight/logistics operations (TMS), PDI, route-fare, requisition workflow, WMS depth, and ERP/accounting — these move the project from a "fleet management app" to a full transport ERP. Scope & cost must reflect that.

4. Aman-Specific Additions (not in generic VMS)

  1. TMS Freight Operations chain — Booking, Loading Manifest, Dispatch, Gate Pass, Unloading, Receive, Delivery, Return Trip. A complete goods-movement workflow with documents at each step.
  2. Route master + route-based fare/tariff — define routes and the transport charge per route; feeds billing.
  3. PDI module — digital pre-delivery inspection for newly purchased vehicles (5 sections, pass/fail, photo evidence, sign-off, link to warranty).
  4. BRTA compliance pack — Bangladesh-specific: tax token, fitness, route permit, number plate, insurance with auto-renewal alerts.
  5. Rental vehicle management — separate trip & billing handling for hired/rented vehicles.
  6. Requisition & approval workflow — for vehicles, maintenance, and spare parts.
  7. ERP / Accounting integration — account, billing, invoicing, procurement ledger.
  8. HR-linked scheduling — employee list, driver duty schedule, overtime schedule, vehicle field shift.
  9. Central Workshop — multi-workshop model with a central hub & consolidated reporting.
  10. Unwanted goods / scrap and Distribution tracking.
  11. Mechanic App — technicians view assigned jobs, track time, update job-card progress (implies a 3rd mobile app beyond Driver & Staff).

5. Recommended System Architecture for Aman

LayerModules
Core / MasterVehicles, Drivers/Staff, Routes & Fare, Vendors, Employees, Company/Concern hierarchy, Roles & Access
TMS — OperationsBooking, Loading Manifest, Dispatch, Gate Pass, Unloading, Receive, Delivery, Return Trip, Distribution, Roster, Requisition
FTS — FleetVTS/GPS, Fuel/CNG, Maintenance Scheduling, Log & Repair History, Warranty/Insurance, Rental Trips, Tyre
WMS — WorkshopAppointments, Job Cards, Mechanic App, Parts Consumption, Invoicing, Central Workshop
StoreSpare-parts Catalog (SKU/QR), Stock In/Out, Reorder, Procurement/PO, Unwanted Goods
PDINew-vehicle inspection checklist, photo evidence, sign-off
Compliance (BRTA)Tax, Fitness, Route Permit, Insurance, Number Plate — auto-renewal alerts
Finance / ERPBilling, Account, Invoicing, Cost/TCO
Cross-cuttingNotification Engine (D/W/M/Y), Reporting Engine, Audit, Dashboards
AppsDriver App · Staff App · Mechanic App (new)

6. Gaps & Clarifications Needed from Aman

QuestionWhy it matters
Does "FTS" mean Fleet Tracking or Fuel Tracking system?Defines module boundary between VTS and FTS.
Is GPS hardware already installed on vehicles, or app-based tracking only?Changes tracking architecture & cost significantly.
How many vehicles, concerns, workshops, and users?Drives scaling, licensing, and pricing.
Should the system integrate with existing ERP/accounts, or is billing/account built in-house?Integration vs. build — major scope difference.
Is a separate Mechanic App required (implied by "mechanic tracking via app")?Adds a third mobile app to scope.
Is freight billing to external customers needed, or internal cost allocation only?Determines TMS billing complexity.
Is weighbridge / weight capture part of loading/unloading?Affects manifest & hardware integration.
Language preference — English, Bengali, or both?Localization scope for UI & reports.
Are the named tools (Alldevice, Makula, Infraon) references for style or must-integrate?Reference vs. integration requirement.

7. Recommended Phasing (for Aman)

PhaseScopePriority
P1 — Foundation & MastersVehicles, drivers/staff, routes & fare, vendors, roles, BRTA compliance, notification engineMust-have
P2 — Maintenance, Workshop & StoreJob cards, WMS, mechanic app, spare-parts store (SKU/QR), procurement, fuel/CNGMust-have
P3 — TMS OperationsBooking → manifest → dispatch → gate pass → unloading → receive → delivery → return trip, distribution, requisitionMust-have
P4 — VTS & Driver/Staff AppsGPS tracking, geofence, Driver App, Staff App, roster, overtime, field shiftHigh
P5 — PDI, Rental & FinancePDI module, rental-vehicle trips, warranty/insurance, billing/account, ERP linkHigh
P6 — Reporting & AnalyticsAll D/W/M/Y reports, dashboards, demand-for-additional-vehicles, central-workshop reportsHigh
Next step: Once the Section 6 clarifications are answered, this analysis converts directly into a final Scope of Work + module list + cost/timeline for Aman Group's approval.
Requirement Analysis — Aman Group TMS/FTS (ERP) · Prepared 2026-07-11 · Based on Transport Department demand letter by Engr. Joy Chandra Das
Mahfuz Akandমূল সাইটে ফিরুন