? Theory: Planned KMs vs Actual KMs

1️⃣ Planned KMs

Definition:
Planned KMs refer to the total distance estimated before the trip begins, based on route planning logic.

How it is calculated:

• Pickup and drop locations

• Route optimization engine (maps API)

• Defined route path

• Expected detours (if any)

• Standard routing rules (shortest / fastest route)

Source of Data:

• Map provider (e.g., routing engine)

• Trip creation module

• Pre-trip route configuration

Purpose:

• Fare estimation

• Billing forecast

• Driver payout estimation

• SLA compliance tracking

• Fuel cost planning

2️⃣ Actual KMs

Definition:
Actual KMs refer to the real distance traveled by the vehicle during the trip.

How it is calculated:

• GPS pings from device

• Odometer readings (if integrated)

• Telemetry tracking

• Path actually taken

Source of Data:

• In-cab device / BYOD GPS

• Backend telemetry aggregation

• Trip completion logs

Purpose:

• Final billing

• Reimbursement

• Driver performance analysis

• Route deviation tracking

• Fraud detection

? Planned vs Actual – Why Difference Occurs?

Differences may happen due to:

• Route deviations

• Traffic diversions

• Road closures

• Multiple stops added

• GPS drift

• Driver taking longer alternate route

• Dynamic rerouting

? Impact Analysis

⚙️ Engineering Perspective

From a system standpoint:

• Planned KMs = Static value stored at trip creation

• Actual KMs = Dynamic accumulation during trip lifecycle

• Variance = Actual_KM - Planned_KM

Recommended tracking metric:

Variance % = ((Actual - Planned) / Planned) * 100

Threshold-based alerting can be configured (e.g., trigger alert if variance > 8%).

? Business Importance

• Accurate billing

• Fuel optimization

• SLA compliance

• Preventing route manipulation

• Cost control