Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Shop Floor

The Shop Floor is the operator’s home in Beelocity — a touch-friendly view designed for the device sitting next to your machine, your workbench, or your assembly cell. It shows the operations queued for the work center you’re operating, the operations a planner has already assigned to you specifically, and gives you four buttons to drive the work: Start, Pause, Resume, Complete.

Operators log in at the start of their shift like any other Beelocity user and log out at the end. While they’re logged in, every Start / Pause / Resume / Complete tap is stamped against their account, so the work order’s labor hours and the audit trail know who actually ran each step.

A typical shift

  1. Walk up to the device at your station, log in.

  2. Pick your station on the Shop Floor screen. Beelocity shows every active work center as a tappable card — name, code, and an Active indicator. Tapping a card swaps the same page into the station’s queue without navigating away, and the URL updates so reloading drops you straight back at your station. Use the ← Stations breadcrumb at the top to move to another machine.

  3. The queue view shows two territories side-by-side:

    • Assigned to you — operations a planner has hand-picked for you (across any work center).
    • Station queue — operations queued at this work center that any operator can claim.

  4. Tap Start on the operation you want to work on. The runner page opens with a live timer at the top, the instructions for this operation in the left column, and the current instruction’s detail (plus its action buttons) in the center.

  5. Walk through the instructions one by one. Each instruction is one of three types and the action bar at the bottom changes accordingly:

    • Step — a plain checklist item. Tap Mark done.
    • Quality check — confirm a condition. Tap Pass if it’s good, Reject (with a reason) if it isn’t.
    • Measurement — type a numeric value. Beelocity checks it against the target range; in-range values record as Pass, out-of-range values prompt you for a reason and record as a Reject.

    You can move between instructions in any order using Previous / Next, or by tapping any row in the list on the left. After you Pass / Reject / Mark done, the runner auto-advances to the next instruction so you can keep moving.

  6. If you have to step away — break, machine issue, waiting on parts — tap Pause (the icon in the top bar) and pick a reason. The timer stops and the time you’re paused does not count against your reported labor hours, only the time you’re actively working does.

  7. When you come back, tap Resume. (You don’t have to be the same operator who paused — shift handover lives in the resume button.)

  8. When you’re ready to record what you produced, tap Complete and enter:

    • Good quantity — units that passed quality this session.
    • Scrap quantity — units that failed quality.
    • Notes — optional explanation, especially if there’s scrap.

    The dialog tells you whether your numbers will close the operation:

    • If your good qty + already-produced reaches the operation’s target, the operation flips to Completed and disappears from the queue.
    • If you’re reporting less than the target (a session report), the operation flips to Paused and stays in the queue. Anyone can Resume it later to make the rest. The components for the qty you just reported are backflushed pro-rata, and (on the final operation) the good units land in the destination warehouse straight away — your warehouse can ship what you’ve already made without waiting for the rest.

    Before Complete succeeds, Beelocity checks that no blocking quality check or measurement is still in Reject. If one is, you’ll see a toast telling you how many are unresolved — re-do the work and re-Pass the step before completing.

  9. Pick the next operation from the queue, or log out if your shift is over.

Card states

Each card in the queue has a primary action button. The label tells you what tapping it will do:

  • Start — the operation is ready (PENDING_START). Tapping starts a fresh time segment under your name.
  • Resume — the operation is paused. Tapping closes the open pause and opens a fresh run segment under your name.
  • Open — you’re already running this operation. Tapping just navigates to the runner page so you can pause or complete.
  • Locked — another operator is currently running this operation. You can see it but cannot act on it until they pause or complete. (One operator at a time per operation.)

The queue auto-refreshes every five seconds, so a teammate’s actions show up without you needing to reload.

Pause reasons

Five categories cover almost everything:

  • Break — lunch, rest, scheduled break.
  • Waiting on materials — components are missing or being delivered.
  • Machine down — the equipment isn’t running. Tooling change-overs that take more than a minute or two count too.
  • Quality hold — a quality issue needs supervisor / inspection sign-off before continuing.
  • Other — anything that doesn’t fit. Use the notes field to explain.

Notes are optional but encouraged on Machine down and Quality hold so the supervisor can see what happened without flagging you down.

What gets recorded

Every Start / Pause / Resume / Complete tap writes a stamped row to the operator’s time-segment log:

  • Who tapped it.
  • When it started, when it ended.
  • Whether it was a working segment or a pause.
  • The pause reason and notes, if any.

When you Complete, Beelocity sums all your run-time segments on the operation, sets the operation’s reported labor hours from that, and rolls the operation up into the work order’s actual labor cost. So:

  • The labor hours on the work order match what you actually worked, not the routing’s estimate.
  • Pauses don’t count against labor.
  • A planner can drill into the operation later and see the full timeline of who ran it, when, and for how long.

Instruction types

Each step on an operation can be one of three kinds. The supervisor sets the kind when authoring the routing; you just see the action buttons that fit:

  • Step — a plain checklist item. Tap Mark done when you’ve done it. No pass/fail; it’s just an acknowledgement that you did it.
  • Quality check — a yes/no condition. Tap Pass if it passed; tap Reject if it failed and write a short reason (“Cracked solder joint on pin 12”). If the supervisor marked this step as blocking, a Reject prevents you from completing the operation until you re-Pass it after rework.
  • Measurement — a numeric reading with a target range (e.g. 4.0..7.0 mils). Type your measured value. Beelocity decides Pass / Reject for you by comparing it to the range; out-of-range values prompt for a reason and record as a Reject.

The list on the left of the runner page shows every step with its current state (pending, done, passed, rejected). You can tap any row to jump there; Previous / Next at the bottom step through them in order. Auto-advance after each action keeps you moving without lifting your hand from the screen.

Things to know

  • You can’t pause someone else’s work. If a teammate is in the middle of an operation, your card will show “Locked — in progress by …”. Wait until they pause or complete.
  • You can resume someone else’s pause. Shift handover is supported: if Salima paused for lunch and you’re back from break, tap Resume and the next run segment is yours.
  • You can complete a paused operation. You don’t have to resume first. Tap Complete from a paused state and Beelocity closes the pause for you.
  • You can’t restart a completed operation. Once you tap Complete, the operation is final. If you reported the wrong quantity, ask a supervisor — the operations grid in Work Orders has the override path.
  • Logging out is the end of your shift. The audit trail keys off your token. If two operators share a device, log out and log in cleanly between sessions — don’t leave one logged in for the other.