The problem: 40-minute SLA, paper-based dispatch
Wheel assembly job work for a major OEM runs on a tight clock. Each JIT call — a demand signal from the assembly line — must be fulfilled within 40 minutes. Miss the window and the assembly line stalls. At scale, that is a cost measured in lakhs per hour.
Before the migration, dispatch coordinators tracked JIT calls on shared spreadsheets and WhatsApp groups. Inward receipts were logged manually. Delivery challans were typed and printed. The reconciliation gap between OEM records and in-house logs ran at 12-15% per month — a constant source of billing disputes and audit findings.
The solution: unified JIT dispatch platform
The team deployed a JIT Dispatch module built natively on their existing ERP platform — sharing one database with inventory, accounts, and HR. No middleware, no separate system to log in to. JIT calls arrive as structured records with timestamps. Each call enters a pipeline view with a live countdown timer.
- Real-time queue view — dispatchers see all open calls sorted by time remaining
- One-tap challan generation — delivery challan auto-populated from JIT call data
- OEM challan matching — inward receipts auto-reconciled against OEM records nightly
- SLA breach alerts — coordinators notified at 30 minutes if call is not yet dispatched
- Audit trail — every status change timestamped and attributed to a user
Results after one quarter
Within the first quarter, SLA compliance climbed from an estimated 81% to 99.2%. The reconciliation gap fell from 12-15% to under 1%. Billing disputes with the OEM dropped by 94%. The finance team now closes the monthly JIT reconciliation in two hours instead of three days.
The countdown timer alone changed coordinator behaviour. When everyone can see the clock, nobody lets a call sit.
Why native integration mattered
Because the JIT module runs on the same database as inventory and accounts, every dispatched challan automatically updates stock levels and creates the corresponding payable entry. There is no nightly sync, no API call that might fail. The plant went live in four days — two days of data migration and two days of coordinator training.