117 lines
7.0 KiB
Markdown
117 lines
7.0 KiB
Markdown
# MVP decision — what exactly are we building?
|
||
|
||
Status: **Q1 settled on 2026-11-13.** Build the staffing copilot. Everything else is downstream.
|
||
|
||
## Decision (2026-11-13)
|
||
|
||
- **Hero:** staffing copilot for a Lidl/Kaufland store manager near Stadtgalerie / Kaiserstraße.
|
||
- **Output:** a usable next-week shift plan, generated in a few seconds, with visible assumptions.
|
||
- **Reusable core:** forecast + scenario engine.
|
||
- **Live layer:** SSE for scenario changes; frontend polling for data/model updates.
|
||
- **Paper:** hackathon deliverable about the core.
|
||
|
||
## The trap
|
||
|
||
"Pulse of the City" sounds like a dashboard. A dashboard is exactly the generic solution the preselection criteria penalize: it shows data, but it does not change a decision. The MVP must be a **decision**, with the map and charts as supporting evidence.
|
||
|
||
The technical stack is not the differentiator. Nuxt SSR, Go, FastAPI, SSE and SKE are delivery mechanisms. The judges will remember one thing: **what decision does this change?**
|
||
|
||
## Options
|
||
|
||
| Option | Data fit | User value | Demo strength | Originality | 24h effort | Reusable / paper |
|
||
|---|---|---|---|---|---|---|
|
||
| **Staffing copilot** | High | High | High | High | Medium-high | High |
|
||
| Ad placement planner | Medium | Medium | High | Medium | Medium | High |
|
||
| Store-location recommender | Low | Low | Medium | Low | Medium | Low |
|
||
| City pulse dashboard | Medium | Low | Medium | Low | Low | Medium |
|
||
| Dynamic waste routing | Low | Medium | Medium | Medium | High | Medium |
|
||
|
||
**Scores explained:**
|
||
|
||
- **Staffing:** the data's strongest signal is time-of-day and weekday. The decision is a shift plan: concrete, recurring, and measurable. The challenge explicitly names staffing. The demo changes a plan, not just a map.
|
||
- **Advertising:** the data has only eight fixed locations. Ranking eight points is a coarse spatial decision, and the demo collapses into a map — the generic dashboard trap. No ad inventory, cost or reach data.
|
||
- **Store location:** needs city-wide spatial granularity. Eight sensors in 580 m cannot rank commercial zones across Heilbronn. This would be dishonest.
|
||
- **City pulse dashboard:** useful context, no decision. It is a supporting view, not the product.
|
||
- **Dynamic waste routing:** requires waste-container and route data, plus optimization. Out of scope for this challenge and this dataset.
|
||
|
||
## Recommendation: PulseCast
|
||
|
||
**One sentence:** *PulseCast turns 15-minute footfall data into a 7-day staffing plan for an inner-city store, with a live what-if simulator.*
|
||
|
||
**Primary user:** a store manager at a Heilbronn inner-city retailer — Lidl, Kaufland, or an independent store near Stadtgalerie / Kaiserstraße.
|
||
|
||
**Job to be done:** *"Tell me how many people will walk past next week, and how many staff I need, hour by hour."*
|
||
|
||
**Decision:** the weekly shift plan. Not "explore the data." Not "look at a heatmap." A plan the manager can accept, edit or reject.
|
||
|
||
**Why this wins the challenge:**
|
||
|
||
- It uses the data where it is strongest: time-of-day, weekday, weather and location.
|
||
- It maps directly to "Dynamic Staffing," one of the three named use cases.
|
||
- It produces a concrete artifact — a shift plan — that a judge can imagine using on Monday.
|
||
- It is original relative to the dashboards other teams will build.
|
||
- The forecasting engine is reusable for advertising and city operations later; the staffing app is the first consumer.
|
||
|
||
## The MVP in five screens
|
||
|
||
1. **Now** — pulse map of the 8 sensors, current/replay reading, weather, last update. This is the "Pulse of the City" context.
|
||
2. **Forecast** — 48-hour and 7-day forecast per location, with uncertainty band, weather context and baseline comparison.
|
||
3. **Plan** — the hero screen: recommended staff per hour, shift blocks, coverage score, over/understaffed hours, estimated labor cost, comparison to a flat schedule.
|
||
4. **Simulate** — presenter changes weather / event / service standard; forecast and plan update; all phones stay in sync via SSE.
|
||
5. **About** — data coverage, model metrics, assumptions, privacy, limitations.
|
||
|
||
The hero screen is **Plan**. Everything else supports it.
|
||
|
||
**Plan generation requirement:** one click on "Generate next week" returns a shift plan in **under 2 seconds**. The plan is a table of 2–4 hour shift blocks per day, staff counts per hour, coverage score, cost, and a comparison to a flat schedule. The manager can edit the assumptions and regenerate. Export as CSV/print view. Not a drag-and-drop optimizer; a usable plan, fast.
|
||
|
||
## The decision logic — transparent, not magic
|
||
|
||
The ML predicts **footfall**. A separate, explainable heuristic turns footfall into staff:
|
||
|
||
```text
|
||
forecast footfall per hour
|
||
→ visitors per staff per hour (service standard)
|
||
→ required staff = ceil(footfall / standard × safety factor)
|
||
→ minimum staff, shift length, opening hours
|
||
→ shift blocks + coverage score + cost
|
||
```
|
||
|
||
The assumptions are visible and adjustable:
|
||
|
||
- visitors per staff per hour
|
||
- labor cost per hour
|
||
- minimum staff
|
||
- shift length
|
||
- safety factor
|
||
|
||
We do **not** have POS, sales, queue or labor-cost data. The app must say that. It predicts footfall; the staffing plan is decision support with explicit assumptions. That is honest and still useful. Do not claim a precise ROI.
|
||
|
||
## What is explicitly out of the MVP
|
||
|
||
- Ad-placement UI and store-location scoring. The forecast API can support them later.
|
||
- City-wide heatmap claims. The map shows measured points and a clearly labeled interpolation, not a city-wide surface.
|
||
- Real-time sensor ingestion. The dataset is a CSV; there is no live feed.
|
||
- Auth/SSO, multi-tenant roles, HA, Kafka, Postgres, deep learning, LLM chat.
|
||
|
||
## Decision record for Q1
|
||
|
||
### Q1.1 — Primary user
|
||
|
||
**Answered:** Lidl/Kaufland store manager near Stadtgalerie / Kaiserstraße.
|
||
|
||
### Q1.2 — Decision output and assumptions
|
||
|
||
**Answered:** a usable next-week shift plan, generated in a few seconds, with visible assumptions. Not a "busiest hours" dashboard, not an ad ranking. No fake ROI.
|
||
|
||
### Q1.3 — Reusable core vs app
|
||
|
||
**Answered:** forecast + scenario engine is the reusable core and the paper subject; the staffing app is the first consumer.
|
||
|
||
## Consequences of the other answers
|
||
|
||
- **SSR:** Nuxt SSR needs a Node deployment; Go API is a second deployment; FastAPI is a third. That is fine, but plan three pods, a Cloudflare Tunnel, and a load test. Onyx SSR was tested and works.
|
||
- **FastAPI + four horizons:** 15 min and 1 h are nowcasts; 48 h and 7 d are planning. The 15 min/1 h horizons need a live clock — the CSV has no live feed. Use a replay clock (P1) or keep them as model metrics. Base forecasts must be cached in Go so a FastAPI failure does not blank the app.
|
||
- **120 users:** Go SSE handles 120 easily; Nuxt SSR must handle 120 page loads; FastAPI is called once per scenario, not once per user. Test 120 concurrent SSE clients with k6.
|
||
- **Auth:** public read-only app; basic auth on `/control` only. The audience view stays frictionless.
|
||
- **Paper:** the paper is a hackathon deliverable. Target a 4–5 page technical report about the core; AI drafts, human verifies every number and citation. The demo takes priority over LaTeX polish.
|