- Home
- Blog
- Glossary (EDGEBIC)
- What Is a Shop Floor Kiosk? Definition and Example
A shop floor kiosk is a terminal on the production floor where operators record what is happening on their machine, starting a job, running it, pausing for a breakdown or missing material, and finishing, so that actuals flow back to the schedule. It is the shop-floor equivalent of a time clock, except it clocks the job and the machine rather than the worker's shift. Each action an operator takes is a punch, and the punches roll up into the actual dates and hours the plan needs to stay honest.
This entry is part of the EDGEBIC by User Solutions glossary series; for the broader vocabulary of production planning, see the manufacturing glossary.
How a Shop Floor Kiosk Works
A schedule is only as good as its feedback. Without a way to record what actually happened, the plan drifts from reality within a shift, and the planner is guessing. The kiosk is the feedback channel: it sits where the work is, and it turns operator actions into structured data the scheduler can consume.
The unit of capture is the punch. A punch is a single state on one job at one machine over a span of time. The states cover the real life of an operation: setup while the machine is being prepared and no good pieces are made, run while it is producing, idle while the operator waits for material or the next job, down for a breakdown, rework for correcting a defect, and teardown, which despite its name is the first setup phase on the kiosk's changeover ribbon, where the previous job's setup is stripped before the new one is built.
Run punches carry output. As the machine produces, the kiosk accumulates good pieces, scrap, and rework separately, so the record reflects yield rather than just quantity. The terminal does not vary from machine to machine: the elapsed clock runs during production and the counters are there to tap at every station. Which measure leads is settled when the day is logged, where the missing side can derive from a rate or both can be entered independently so performance variance can be computed.
At end of day, the punches for each operation roll up: the day's hours are recomputed from the punch spans, and the operation's actual start and end are set. Those are exactly the values a reschedule reads.
A Concrete Example
An operator arrives at CNC-3 for an 8-hour run. At the kiosk they:
- Punch setup while installing the fixture and loading tools.
- Punch run and begin producing; the kiosk counts good pieces and one scrap.
- Punch down mid-shift when a coolant line fails, selecting a machine reason code, then back to run when it is fixed.
- Tap complete operation to close the job. Teardown is not an end-of-job punch: it is the first phase of the next changeover.
The stamps land as they happen rather than in a nightly batch: the operation's actual start is written at the first start-run tap, and its actual end when the operator taps complete operation. Punches accumulate into a daily hour total that separates productive run time from downtime. Nothing auto-closes a punch left open, so a machine down overnight should simply be left paused, where the time is recorded as non-productive; a punch left running inflates its phase and needs a supervisor correction in the history drawer, which is recorded and attributed.
How EDGEBIC Uses It
EDGEBIC ships a dedicated shop floor kiosk application that shares the same database as the planning desktop, so punches become actuals on the planner's schedule directly.
- Operators punch state changes. Setup, run, idle, down, rework, and teardown are captured per job per machine, with good, scrap, and rework pieces on run punches.
- Hours or pieces lead. The terminal captures both at every machine: the elapsed run clock advances on its own and the good and scrap counters are tapped per piece. Which measure a shop records as the truth is decided when the day is logged, through the Auto Calc Hours control, rather than configured per station.
- The stamps land as they happen. The first start-run tap stamps the operation's actual start and completing the operation stamps its actual end, with punches accumulating into per-day hours; an end-of-day snap keeps a same-day close from producing an inverted date.
- Corrections are auditable. Auto-close handles forgotten punches, and supervisor punch adjustments record the old value, new value, reason, and adjuster.
The kiosk is what makes actuals preservation on reschedule possible: the reschedule can only preserve completed work because the kiosk recorded it. Pauses are captured with a reason code so the plant knows why a job stalled, and the shop floor guide walks through the operator's day at the terminal.
A shop floor kiosk is a terminal on the production floor where operators record what is happening on their machine: starting a job, running it, pausing for a breakdown or missing material, and finishing. Each action is a punch, and the punches roll up into the actual dates and hours the schedule needs. It is the shop-floor equivalent of a time clock, except it clocks the job and the machine rather than the person's shift.
A kiosk records punches, each a single state on one job at one machine over a span of time: setup, run, idle, machine down, rework, or teardown. Run punches accumulate good, scrap, and rework pieces. The kiosk captures both measures at every machine, and which one a shop records as the truth is settled when the day is logged: the missing side can derive from a rate, or both can be entered independently. The punches accumulate into per-day hours, while the operation's actual start is stamped at the first start-run tap and its actual end when the operator completes the operation.
The kiosk writes actuals back to the same schedule the planner works from. When an operator starts a job, the operation gets an actual start; when they finish, it gets an actual end and its punches roll up into the daily hours. On the next reschedule the engine reads those actuals, preserves completed work, and replans only what is left. The kiosk closes the loop between the plan on the planner's screen and the reality on the floor.
Expert Q&A: Deep Dive
Q: An operator ran a job Monday and Tuesday but forgot to clock out Monday night. Does that break the actuals?
A: It leaves the punch open, and nothing closes it automatically. Paused and idle time is recorded as non-productive and never enters the job's production hours, so a machine left paused overnight is harmless and is in fact the recommended way to leave a breakdown. A punch left *running* is the real problem, because it inflates that phase's elapsed record. The fix is a supervisor correction in the punch history drawer, where every punch and every edit is listed with who made it and when, each correction requires a reason, and the original is kept alongside it forever.
Q: Can an operator record scrap and rework at the kiosk, or only good pieces?
A: Both. During a run punch the kiosk accumulates good pieces, scrap, and rework separately, so the day's output reflects yield, not just quantity produced. A pause for a defect is recorded as a rework punch, and a machine breakdown as a down punch with a reason code, so the reason a job fell behind is captured alongside the hours. That detail is what makes shop-floor data useful for variance analysis rather than just a raw hour count.
Frequently Asked Questions
Ready to Transform Your Production Scheduling?
User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.

User Solutions Team
Manufacturing Software Experts
User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.
Share this article
Related Articles
The EDGEBIC Scheduling Glossary Index
A themed index to the EDGEBIC glossary: scheduling engine, capacity and calendars, materials and planning, shop floor, reporting, quoting, and data import terms, defined in plain language.
What Is the Critical Chain in Manufacturing Scheduling?
The critical chain is the longest dependent path through a plan once shared machine contention is counted, not just step precedence. Here is how it differs from the critical path.
What Does Finite Capacity Mean in EDGEBIC?
Finite capacity means the scheduler refuses to book more hours on a machine than that machine actually has. See exactly how EDGEBIC enforces it, day by day and shift by shift.
