Smart Table Service Intelligence
Hospitality · 2024-2025
The problem
On a busy restaurant floor the gap between good service and bad service is usually measured in seconds. A glass that empties and sits, a plate finished but not cleared, a table that has paid and is ready to turn - each is a small moment that, missed, adds up to slow service, lower covers per night and a worse guest experience. Staff are attentive but finite, spread across sections, and at peak the floor simply has more happening than any one person can keep in view.
The production system closes that gap with overhead cameras that watch the tableware - not the guests - and prompt the right server at the right moment. The hard part is doing this without drowning staff in false alarms: a camera that fires on every flicker is worse than no camera at all. So the real work is not detection, it is restraint - only raising an alert when a situation is genuinely real and genuinely actionable.
The solution (downscaled)
This is a faithful, downscaled reimplementation on synthetic, top-down, tableware-only frames - no people, privacy by framing. A single vision stage reads each frame; every other stage (tracking, aggregation, confirmation, the action rules, governance and dispatch) is deterministic. The product surface is the staff Floor workspace, with the full alert lifecycle: acknowledge, escalate, resolve and flag-wrong.
The honest cost story is built into the design, not bolted on. Only the perception stage is metered; a change-gate skips frames that haven't moved; and a confirmation window requires a situation to repeat across several frames before any alert reaches a human. Those two deterministic levers are exactly how a real deployment keeps an always-on camera affordable - sample, don't stream.
What it is not
No real cameras, no live video, no real staff notifications, no real POS or venue. Every frame is synthetic and labelled; the cameras, detector, tracker, notification push and reorder integration are all simulated. The client is not named, and figures are representative ranges. What the real system uses instead of these shortcuts is spelled out in Architecture → Out of scope.