The Daily Rhythm of a Kiosk-Run Shop with EDGEBIC

A kiosk-run shop keeps its schedule honest by following a simple daily rhythm: operators punch their real work at the machine, the planner logs and confirms actuals, and a reschedule re-plans the remaining work forward, once per shift or once per day. That cadence, captured in the phrase "log first, reschedule second," is what separates a plan that reflects reality from a plan that drifts into fiction. EDGEBIC by User Solutions is built around this rhythm, and this article walks through a full day of it.

Shops that reschedule daily against fresh actuals keep their promise dates believable. Shops that avoid rescheduling end up planning against a plan that no longer matches the floor. The rhythm is not extra work; it is the discipline that makes finite capacity scheduling pay off. This is the same practice that took User Solutions customers like GE Railcar from 30% to 90% on-time delivery: steady, small corrections against reality.

The Two Roles in the Rhythm

The rhythm has exactly two players, and their jobs never overlap.

The operator works at the shop floor kiosk, an execution terminal bound to one work center. Every tap opens or closes a punch: a single uninterrupted stretch of setup, run, pause, or down time. The operator starts jobs, counts good and scrap pieces, records why a machine stopped, and completes operations. The operator cannot reschedule, re-sequence, or browse the whole plant. The terminal is deliberately small.

The planner owns the schedule. The planner confirms the actuals the kiosk captured, handles anything logged manually, and runs the reschedule. The planner decides the cadence and reads the audit trail afterward.

This clean split, discussed in why the EDGEBIC kiosk has no login, is what keeps the floor fast and the plan under a single owner.

A Full Day of the Rhythm

Here is how the cadence plays out on a typical two-shift day.

Shift start: the plan lands on the floor

Before the crew arrives, the planner runs the morning reschedule and prints the day's work. Because the engine plans forward from the last logged position, the dispatch list reflects overnight reality, not yesterday's guess. Supervisors hand out each person's day, grouped and ordered, from the dispatch view. For how that reaches the floor, see how supervisors use the EDGEBIC dispatch view.

Through the shift: operators punch reality

An operator taps the terminal's Start Setup button on the next queued job. They step through the setup phases, then tap Start Run. If no one has recorded it yet, the operation's actual start is stamped at that moment. Through the run they tap the Good counter once per finished piece and the Scrap counter for a bad one, choosing a reason each time. When a machine stops, they tap Pause and pick the honest category. When the operation is done, they tap Complete Operation and the actual end is stamped.

Every one of those taps is a fact from the floor, timestamped from the shared clock. The operator never types times during normal use.

Shift change: the handoff

At the change, the outgoing operator opens the shift handoff summary: setup, run, and down hours, the good and scrap totals, and the most recent pauses with their reasons. It is everything the oncoming shift inherits, on one screen. Reading a handoff well is a skill of its own, covered in reading a shift handoff summary.

Next morning: log, confirm, reschedule

The planner confirms the actuals, fixes anything that was entered manually or needs a supervisor correction, and presses reschedule. Completed operations stay frozen. In-progress operations keep their logged hours and machine; only the remainder moves. Not-started operations re-plan against current capacity and calendars. The forward plan is honest again, and the rhythm repeats.

Why the Rhythm Beats Reacting

It is tempting to reschedule after every disruption. A better habit is a steady cadence with occasional targeted runs. Here is why.

Steady corrections stay believable. A daily reschedule makes small adjustments the customer barely notices. A monthly reschedule makes one enormous adjustment that breaks every promise at once. Frequent small corrections keep dates trustworthy.

Targeted runs are the polite option. When a single hot job jumps the queue or one machine goes down, a targeted reschedule touches only the jobs you changed and leaves every other job's plan and capacity exactly where it was. You do not disturb work you never touched. Save the full plant reschedule for calendar or capacity changes that affect everyone.

The floor stays out of it. Because operators only execute, the plan has one author. There is no tug of war between a supervisor dragging bars and the engine re-flowing them. The engine honors saved overrides and re-plans around them.

A Worked Example

Tuesday, a machine shop running one job through a saw, a mill, and assembly.

• 07:45. The planner logged the night shift's actuals, ran the morning reschedule, and printed dispatch. The saw job's real overnight finish moved the mill start forward two hours, and the printed sheet already reflects it.
• 08:00. The mill operator types their name in the Operator box, taps Start Setup on the queued job, steps through the setup phases, and taps Start Run at 08:50. Actual start stamped 08:50.
• 11:30. A coolant alarm. The operator taps Pause, picks Machine, then the coolant reason. Forty minutes later they tap Resume. The pause is recorded as non-productive and stays out of the job's production hours, but it lands on the handoff and the downtime report. This is the value described in what a pause with reason record is worth.
• 15:40. Twenty good pieces logged over the day. The operator taps Complete Operation; actual end stamped 15:40; the day's run hours roll up automatically.
• 15:45. Shift change. The handoff shows setup 0.9 hours, run 5.9 hours, down 0.7 hours, and the coolant pause on the recent list.
• Next 07:45. The planner confirms, reschedules, and prints again. Assembly now plans forward from the mill's real 15:40 finish, not the plan's guess.

That loop, run every day, is the whole discipline. Nothing about it is heroic. It is just consistent.

Making the Rhythm Stick

Three habits carry the rhythm.

• Punch in real time. Live punches carry phase-level detail that end-of-shift memory cannot reconstruct. Manual entry is a fallback, not the plan.
• Pick honest pause reasons. The four-category downtime split is what makes your Pareto analysis and machine downtime tracking meaningful.
• Log before you reschedule. The one habit that makes every run trustworthy.

When those three are second nature, the plan on the wall and the reality on the floor stay within an arm's length of each other all day. Getting a crew there takes about twenty minutes of teaching one loop rather than one screen, which is the approach in training your floor on the kiosk in one shift. That is the point of a kiosk-run shop, and the reason the rhythm exists.

See how the punch-to-plan cycle fits together in how actuals flow into the EDGEBIC schedule and the full shop floor execution guide. Explore the platform at EDGEBIC.