Why Operations Intelligence
On a busy IPD evening we could see how many picklists were open, but not whether picking or packing was the bottleneck, or which two operators carried half the dispatch load. Spreadsheets and gut feel do not scale when you run multiple warehouses and a hospital QR feed.
Operations Intelligence pairs two views:
- Operational KPIs — load by stage and warehouse (shift planning).
- Operator Productivity — the same stages credited to named staff (fairness, coaching, staffing proof).
Because Ailaaj operates pharmacies, we built attribution from how work is actually recorded: pick lines store picked_by, pack notes store a “Packed N by …” stamp with the packer’s name, dispatch stores dispatched_by, and delivery credits the assigned rider — with backfill so last month is reviewable, not only today forward.
How this differs from generic ERP reports
| Typical ERP | Ailaaj Operations Intelligence |
|---|---|
| Order status counts only | Discrete events per IPD stage (pick line, pack note, rider handoff) |
| One warehouse rollup | Per store + warehouse series on every chart |
| No link between volume and people | Same stage keys in KPI and productivity reports |
| SLA module mixed with volume | KPIs for load; SLA Monitoring for threshold breaches (separate screen) |
When it does not apply
- Compounding, IV prep, ward liaison, QC sign-off — shown as Not tracked until HMS/activity hooks ship.
- SLA compliance — use SLA Monitoring under Operations Intelligence when that phase ships; do not read KPI charts as breach timers.