Smart Table Service Intelligence

Hospitality · 2024-2025

PublicRepresentative · synthetic data
  1. 1

    Run a scene on the Floor

    The Floor is the product surface - a grid of synthetic tables across three sections, each showing its status, latest top-down snapshot and dining phase. Pick a scene (empty glasses, finished plates, a reorder opportunity, an anomaly, or a steady table) and Step the clock to advance the simulated camera one frame at a time.

    Open a table to see the live frame with its detection overlay - the perceived items, their fill states and per-item confidence - alongside the confirmation status. Watch a situation build: the confirmation counter (e.g. 2/3) has to fill before anything fires. A single odd frame never raises an alert, which is the whole point.

  2. 2

    Handle alerts

    Confirmed situations arrive in the alert feed in priority order, routed to the table's server: "Table 12 · drink refills · high" with a snapshot. Acknowledge it, mark it resolved, dismiss it, or flag it as a wrong alert. Later frames can confirm a resolution; an unhandled alert auto-escalates to a manager on timeout. A wrong-alert flag is feedback that tunes the rules - it never retrains a model.

    Roles matter here: a viewer is read-only, an owner commits actions (audited), and a guest can drive the loop ephemerally. Use the View-as switch to see each lens.

  3. 3

    Look behind the scenes

    Open "Behind the scenes" to see the full nine-stage trace for the last handled frame on the uniform trace-row contract - stage, provenance, model, tokens, cost and confidence. Switch Cloud/OSS inference and watch the cost meter, which only moves on the single metered vision stage and fails closed to $0 OSS at the budget cap. The inspector also shows recorded Cloud-vs-OSS divergences on real frames, including one honest "not captured" case. Everything is labelled: simulated camera, synthetic data, Cloud live or OSS recorded.

  4. 4

    Operate the Console

    The Console is one unified, role-gated operator surface. OPERATE (viewer-readable) holds the Overview metrics, Alert operations and the Wrong-alert review. The owner-only CONFIGURE section tunes the engine live - the sampling interval, the detection states and confidence floor, the confirmation window and governance timers, the action rules and the staff roster - with every change audited and reversible via Reset to baseline. The project-page walkthrough video narrates the full tour.