oppiOS / Synapse
A slammed Saturday is not a quiet Tuesday.
OPPI reads which one you are in, and who should take the job.
The screens to steer it are still in build.
The Harbour Room, Fri 19:05, 6 on shift
Next-cycle preview. Suggest mode logs the winner and leaves the task unassigned.
Example venue. Illustrative data.
Modes
Synapse classifies the venue's revenue mode from thresholds: above the surge line, below the quiet line, or normal in between. Categories of work can be paused in a surge and boosted in a quiet, so prep does not get raised in the middle of the rush.
Scoring
For each task, clocked-on staff are scored: does their area match, how many minutes are already in their queue, how long is left on their shift. A buffer at the end of a shift keeps new work off someone about to leave; a minimum coverage per area keeps a station from being emptied.
In build
The routing engine, its settings model and its speed profiles exist and run server-side. What does not exist yet is the screen to set thresholds and modes, or to see assignments as they are made. Until it does, Synapse is not something a venue manager can open, and we will not pretend otherwise.
What it does
Surge, quiet or normal, from thresholds.
Area match, current queue, shift time remaining.
An assignment mode of suggest, or automatic.
Categories paused in a surge, boosted in a quiet.
Minimum coverage per area; a buffer before a shift ends.
How fast work moves, per profile, feeding the score.
Surge mode. Prep categories paused. The bar's queue counts against new work.
Quiet mode. Deep-clean categories boosted. The person with an hour left is not given the two-hour job.
Work that finds the right hands.
The routing engine is built. The screens are next.