S10-Mo. In-House Logistics Delivery SLA + Order Optimization (Momo-Specific)
Published 2026-05-14Updated 2026-06-302 min read
Momo differentiation point ⭐ — Analyzes in-house logistics (momo Fast) 24-hour delivery promise breach rate combined with region, time slot, and outdoor weather.
1. URL · Persona
/delivery-sla· P5 (Logistics · MD)
2. User Story
P5 — Northern fulfillment-center 24-hour promise breach rate + heavy-rain impact + next-day ordering guidance on a single screen.
3. Data Mix
| Data | Source |
|---|---|
| DeliverySLA logs | TimeStream (~250K) |
| Fulfillment centers | Neptune (Channel nodes) |
| Region (North · Central · South) | DeliverySLA attribute |
| External weather | WeatherSignal (Central Weather Administration) |
| Order surge (Double 11, etc.) | Campaign + OrderTransaction |
4. Processing Pipeline
1. Compute daily (region, fulfillment_center) 24h SLA breach rate
2. Join with WeatherSignal (heavy rain · typhoon)
3. Annotate Double 11 and other campaigns
4. Simulate next-day ordering (current stock · expected orders · SLA recovery cost)
5. Recommendation: ordering guidance combining fulfillment load + outdoor weather
5. Output UI
- Left: Per-region SLA breach-rate time series
- Center: Fulfillment-center load heatmap (time slot × region)
- Right: Outdoor weather vs SLA breach scatter plot
- Bottom: Next-day ordering simulation (stock · forecast · recommendation)
6. Guardrails
- Block external exposure of business information (stock · logistics unit cost)
- Cite external weather source
7. Demo Scenarios
- Northern 24-hour breach rate 32% → impacted by -50mm heavy rain (1-day lag)
- Day after Double 11 → breaches +25% vs normal, recommend ordering +30%
- Next 7-day simulation → per-region SLA recovery cost