Getting onto the floor
An operator signs in on the login screen with whichever methods the company has enabled: “Sign in with Google”, “Sign in with Outlook”, “Sign in with Passkey”, or an email address with “Continue” (a magic link, which lands on a “Check your email” confirmation). The available buttons follow the company’sAUTH_PROVIDERS, so a floor that only allows passkeys sees only that one.
Once in, the operator sets their context. If the company has more than one location, a “Location” submenu appears in the sidebar to pick which floor they’re standing on. With a single location the choice is skipped entirely. This selection scopes the board, the assigned lists, and everything they report.
Console (shared-station) mode
Console mode turns a station into a shared kiosk. It requires the Business plan and theconsoleEnabled company setting. Enabling console mode requires settings_update permission on the signed-in account; any operator can disable it.
In console mode an operator identifies themselves with a 4-digit PIN, not a full login. PINs are generated by Alforse and handed out by an admin — shown once when an operator is created or a PIN is reset, and stored only as a hash (see shop-floor PIN accounts). The station prompts to enter a PIN for the named operator, checks it, and attributes the work to that person. Three things stop it: “Incorrect PIN”, “Too many incorrect PINs. Please wait a few minutes and try again.” after repeated wrong guesses, or “No PIN set. Ask an admin to set a console PIN for you.” if the person has none yet.
The operations board
Released work appears on the Schedule board, with one column per . Each column lists queued by dispatch priority; the first card is the next scheduled operation. The board is display and filter only. A Display popover lets each station tune its own view, toggling “Empty work centers” on or off and showing or hiding “Customer”, “Description”, “Due Date”, “Duration”, “Progress”, “Status”, “Sales Order”, and “Thumbnail” on each card. Filters narrow the queue by “Work Center”, “Process”, “Tag”, or “Assignee”.Focused lists
Alongside the board, three sidebar lists cut the queue down to what one operator cares about right now: Each card carries a status badge, its progress, and a deadline chip (“ASAP”, “No Deadline”, or a date that turns red when overdue). The badge tracks the operation’s own status, not the job’s.Open Jobs
The “Open Jobs” list is the job-level view: columns for Job, Item, Quantity, Tracking, Assignee, Due Date, Deadline, and Status. One relabel to know here, because it trips people up: Opening a job shows its operations as a directed graph (the routing DAG), so an operator sees what feeds what. The toolbar lays it out “Left to Right” or “Top to Bottom” and offers “Fit”; nodes flag a “Rework” loop and a scrapped-quantity count when they apply.Running an operation
Open an operation and the station panel is where the shift actually happens. A big control starts and stops the clock: “Start” opens a production event, “Pause” closes it. A toggle picks which kind of time is being logged, matching the three : “Setup”, “Labor”, or “Machine”. The panel is tabbed into details, model (the 3D part view), procedure (work instructions, with attributes and parameters sub-views), and chat (a per-operation note thread).The guided assembly view
An operation whose type is Assembly opens a guided 3D view instead of a plain part model: the assembly plays back one step at a time, and each step lights up the components it installs. The player toolbar provides three visibility modes for exposing the current step: The view only changes what the operator sees. It never changes the step order, the components a step installs, or anything reported back. The author can also hide parts that get in the way on a particular step, and group steps into a sub-assembly that is built on its own before it goes in as one piece. Both play here exactly as authored; see assembly instructions. The same control appears in the ERP assembly editor, where an author checks that a step reads clearly before publishing. An author and an operator ask the model the same question, so the buttons mean the same thing on both screens.Reporting quantities
Good, bad, and reworked units are reported separately, so yield stays honest: Reworking in place is different from sending a unit back upstream. “Create Rework” does the latter: pick an operation under “Go back to operation”, give a “Reason for rework”, and Alforse re-runs every operation from that point forward to the current one. Closing the operation is a distinct action. “Mark as Done” ends any open events and flips the operation toDone. If quantities or steps aren’t satisfied Alforse warns (“Insufficient quantity”, “Steps are missing”) and the button reads “Mark as Done Anyways”. A guard also fires when tracked material was never issued; the operator must acknowledge “I understand and want to complete without issuing” to proceed.
Issuing material
Material is consumed against an operation from the same panel. The “Issue” action has an Adjustment Type: “Add to Inventory” (aPositive Adjmt.) or “Pull from Inventory” (a Negative Adjmt.). For serial- or batch- material, tabs let the operator “Scan” a barcode, “Select” from stock, or “Unconsume” to return material already issued.
One edge case surfaces right in the flow rather than failing silently. Issuing expired stock is governed by a policy (Warn, Block, or BlockWithOverride); an overridable block asks for a “Reason for issuing expired stock”.
Clocking in and out
When thetimeCardEnabled company setting is on, the sidebar carries a time card: “Clock In” and “Clock Out”, a “My Hours” view (a table of Date, Clock In, Clock Out, Duration), and a “Clocked in since” badge with the start time while a shift is open. Leave a shift open too long and Alforse nudges: after twelve hours it asks “Forgot to Clock Out?” with “I’m Still Working” or “Set Clock Out”. Time cards are labor time for payroll and presence; they are separate from the per-operation production events that drive job costing.
Picking, quality, inspections, and maintenance
The floor does more than run operations. Four adjacent surfaces live in the same app.On-floor picking
The “Picking” view lists the picking lists assigned to the operator. “Start” moves a list toIn Progress; “Finish” takes it to Completed. Each line is worked with “Pick”, “Unpick”, “Short”, or “Scan” (for tracked material), and a “No stock” badge flags an empty source. A short pick asks “How many were actually picked?” and records the shortfall with “Mark Short”.
Quality issues and inspections
An operator who spots a problem raises it without leaving the station. “Create Quality Issue” captures an “Issue Type”, a “Priority” (Low, Medium, High, or Critical), and a “Description”, and files a non-conformance for quality to triage. See quality for how that record is worked. Inspections and work instructions run as typed steps inside the procedure tab. A step is one of nine kinds:Maintenance dispatch
When a machine goes down, an operator raises a maintenance dispatch from the floor. Every dispatch created here isReactive by source (scheduled and non-conformance dispatches originate elsewhere). It carries a severity, a priority, and an OEE impact; choosing an OEE impact of “Down” ends the work center’s active production events, because the center can’t produce while it’s under repair. The maintenance worker executes it from a detail view with Play, Pause, and Complete controls, a “Time Worked” total, and a “Spare Parts” section (“Add & Issue”), landing on “Maintenance Completed” when done.