Model Name | Architecture | Provider | Purpose | Input | Output | Usage Context |
---|---|---|---|---|---|---|
RouteAccept-LGBM | LightGBM (Gradient Boosting Decision Trees) | Azure ML | Predicts whether a route will be accepted, the reason for correction, and potential SLA risk | Structured delivery route features (~60 per route) | Classification label + score + ETA deviation estimate | Core dispatch logic, live route filtering |
RouteScore-RNN | GRU-based recurrent neural network | Custom | Evaluates sequential logic and terrain consistency across the delivery path | Ordered stop list with metadata (20–30 steps) | Scoring value + flag for anomalies or fatigue risk | Supplementary scoring layer for complex routes |
FeedbackParse-BERT | Transformer (BERT-style) | Azure ML / Hugging Face | Extracts structured issues from unstructured text comments | Text comments (~512 tokens) from clients, couriers, or dispatchers | Classified labels (e.g. “access problem”, “equipment missing”) | Post-delivery feedback analysis, route quality loop |
ExplainRoute-GPT | GPT-4 (Generative Transformer) | Azure OpenAI | Generates a natural-language explanation of how and why a route was constructed | Route metadata, constraints, vehicle & item context | Full sentence-level summary of routing logic | Dispatch UI assistant, AI transparency layer |
Model Name | Avg Inference Time | Retraining Frequency | Context Volume | Explainability | Real-Time Compatible |
---|---|---|---|---|---|
RouteAccept-LGBM | ~300 ms | Weekly | Fixed vector (~60 features) | Feature importance | Yes |
RouteScore-RNN | ~400 ms | Monthly | Up to 30 delivery steps | Internal only | Yes |
FeedbackParse-BERT | ~800 ms | Monthly | ~512 tokens | Label classification | Partially (batch preferred) |
ExplainRoute-GPT | ~1–1.2 sec | No retraining (prompt-based) | ~2,000 tokens | Full natural-language output | UI use only (not for routing logic) |