Mission Report · MapMyIndia [Gtropy] · Mappls Insight, for Tata PowerProject case study
Contract Management Dashboard
Vehicle contracts are billed on kilometres. A dashboard that compares month-to-date kilometres with a full month's limit calls every vehicle under-used for most of the month.
- Status
- Active
- Owned
- Product design · UX · Working prototype
- Pages
- 2
- Status bands
- 90% · 110%
- Case study
- Read it on Behance
- Stack
- HTML prototype
- JavaScript
- Charts
- Mappls Insight
ResultsBeing measured
- Client sign-off on the pro-rating and variable-cost logic
- Whether the 90% and 110% bands match how the business judges a vehicle
- Cards and charts the client keeps or drops
I decided
- Two pages, with billing as a separate deliverable
- Utilization charts in place of pricing charts
- Compare kilometres to date with the limit to date
- Status colours kept apart from the brand orange
I built
- The working prototype, one HTML file that opens offline
- Each round of client changes and the walkthrough
How it works
What it does, feature by feature
Contract overview
Cost, kilometres, utilization and vehicle counts as cards, with KM driven against the allowance and the status split.
Contract managementVehicle details
Every vehicle's limit, extra kilometres, variable rate and cost; a click opens the full calculation and its month-end projection.
Contract managementVendor summary
Vendors compared by utilization, with a status that comes from the vendor's combined kilometres.
VendorsTimelines
Daily, weekly (last 7 days or Mon–Sun), monthly and custom ranges, with fixed cost and limits pro-rated to the days chosen.
PeriodTo-date handling
Running periods are marked to date, compared with the same days last period, and projected to month end.
PeriodFilters
Region, vertical, business, project, vendor and utilization band, applied to every card and chart.
All viewsEditable bands
The under and over thresholds (90% and 110% by default) change every status on every page.
Rules
Actual cost
Kilometres driven in the period →
The contract model: a fixed charge covers the contractual kilometres, and every kilometre beyond them is billed at the vehicle's variable rate. Illustrative units, not a client's rates.
Utilization, % of the limit to date
- Under utilised: below 90%
- Optimal: 90–110%
- Over utilised: above 110%
Utilization is kilometres driven ÷ the limit for the same days. Comparing to date with to date is the fix: against the full month's limit, a vehicle on track reads as under-used until the last day.
Inputs
- Daily kilometresper vehicle
- Contractfixed charge + KM limit
- Variable rate
- Period chosen
Calculation
- Pro-rate limit and fixed costto the days covered
- Extra KM × ratevariable cost
- Utilization to dateagainst 90% / 110%
- Month-end projectionat the current pace
Views
- Overview cards and charts
- Vehicle table + cost drawer
- Vendor summary
What the dashboard computes for any period the user picks. A model of the logic, not live data.
Brief
A contract management dashboard for Tata Power's vehicle contracts on Mappls Insight: what each vehicle and vendor costs, and whether it is under-used, on track or over-used.
Context
Each vehicle is hired on a contract: a fixed charge that covers a set number of kilometres, and a variable rate for every kilometre beyond it. The client manages vehicles across regions, verticals (Solar and Wind) and businesses (O&M and EPC), from many vendors.
Users
Contract and fleet managers who approve vendor bills and need to see, on any day of the month, which vehicles and vendors are drifting from their contracts.
Discovery
The live dashboard compared kilometres driven so far with the whole month's limit, so a vehicle on pace looked under-used for most of every month, and so did the fleet average.
Problem
Make cost and utilization correct on any day, for any period, without the user having to know which figures are still running.
Strategy
Pro-rate everything to the days the user is looking at, compare running periods with the same days of the previous one, and say plainly when a figure is to date.
Prioritization
Two pages: Contract management (overview and vehicle details) and Vendor summary. Billing became a separate deliverable rather than a third tab that would have crowded the two jobs the client actually asked for.
UX
Data stops at the last full day, future dates can't be picked, and Weekly defaults to the last seven days instead of a half-finished calendar week. A running period carries a to-date tag and a month-end projection.
Design
Uniform KPI cards with a small visual each, utilization charts instead of pricing charts (by business, by vertical, by region, a histogram and a KM-against-limit scatter), and status colours (under, optimal, over) kept apart from the brand orange.
Build
A working prototype in a single HTML file that opens offline, with sample data, the client's filters and the new cost columns, revised round by round with the client.
Outcome
In client review. Nothing measured yet, so nothing is claimed.
Learnings
A wrong denominator is a UX bug. Every chart was correct arithmetic on the wrong comparison until the period was made explicit.