How an Operator's Hours Are Attributed to a Job in EDGEBIC

In EDGEBIC by User Solutions, an operator's hours are attributed by the name they enter at the kiosk, which rides on every punch they make, and their productive hours are summed from run and rework punches only. The machine is one record of what happened; the person is a second, carried on the very same punches. That is how a job can tell you not just how many hours it took but who was standing at the machine for each of them. This is the human layer of shop floor data collection: the run is a fact, and so is who ran it.

There is a matching idea on the planning side, the attend fraction, which books operator-hours a job will need before it runs. This article is about the other end, the actuals: how the time a person actually worked gets recorded and attributed after the fact.

The Name Rides on the Punch

A kiosk session is bound to one work center, one physical machine lane, and one operator. The operator types their name into the Operator box when they start, and that name is stamped on every punch made during the session. Setup, run, down, rework, each carries the same operator name, so the punch history for a schedule is also a record of who was present for each state.

Because attribution lives on the punch and not on a separate roster entry, it survives everything the punch survives. Reschedules do not touch it. Corrections do not erase it. If a value is fixed later, the change is a separate append-only adjustment, and the original operator's punch stays intact underneath.

What Counts as Productive Hours

The kiosk offers an operator day summary: a person's productive hours for the day at a work center. It is filtered the same way the daily rollup is filtered, to run and rework punches only:

Setup, idle, down, and teardown time is still captured under the operator's name for downtime and setup analysis, but it does not inflate their productive-hours figure. Nobody's productive number is dragged down by a coolant alarm or a long changeover. That mirrors the rule that only run and rework hours roll up into a job's good, scrap, and rework counts and productive hours.

How Hours Add Up Across a Job

A single job rarely fits one session. It may pause overnight, cross a shift change, or move between operators. Each punch keeps the name of the session that made it, so the attributions accumulate naturally:

• Operator A opens the job in the morning, logging several run punches under their name.
• The shift changes. Operator B resumes the job in the afternoon, and their run punches carry their name.
• The schedule's daily rolled-up hours are the sum of every run and rework punch, regardless of name.

So the job answers two questions cleanly. How many productive hours did it take? The sum on the daily rollup. Who worked it? The names on the punches, split by session in the history drawer and reflected in each operator's day summary.

Pinning a Person to a Job

Attribution records who worked a job. If you need to reserve a specific certified person for a job before it runs, the operator PIN is the tool: it ties a named operator to the schedule so a reschedule keeps that assignment rather than reshuffling it. The PIN is the intent, the punch name is the outcome, and the two together give you both "who should run this" and "who actually did."

Keeping the Attribution Honest

Two habits keep the who reliable. First, operators enter their name at the start of a session, so the punches are tagged from the first tap rather than reconstructed later. Second, when a name is wrong or missing, a supervisor fixes it through the history drawer as an append-only adjustment that records the correct value and a reason, never an in-place overwrite. See how a supervisor corrects a kiosk punch for that path.

Because the job's total hours sum regardless of name, a blank or wrong operator never corrupts the schedule's numbers: it only leaves a gap in attribution that the correction closes. The plan reads the same hours either way, and it only reshapes remaining work on the next reschedule.

Where It Fits

Operator attribution is one thread in the actuals fabric. The punches that carry it also feed the daily rollup, OEE, and the reschedule. For the planning-side view of operator time as a constraint, read the operator attend fraction explained. For the concepts underneath the whole loop, what is production scheduling sets the frame, and the EDGEBIC shop floor guide or the EDGEBIC product overview tie it back to the platform.