How to Pause a Job With a Reason Code in EDGEBIC

To pause a job with a reason code in EDGEBIC by User Solutions, tap PAUSE on the shop floor terminal, pick one of the four reason categories, then pick the specific reason. The run punch closes and a paused punch opens carrying that reason. The point of the extra two taps is that paused time never becomes production hours on the operation, so downtime is recorded without polluting anyone's efficiency numbers.

The rest of the operator terminal workflow is in the shop floor execution guide. This is the pause.

Before You Start

Step 1: Tap PAUSE

Tap PAUSE on the running screen. The run punch closes at that moment, timestamped from the shared clock. Nobody types a time.

Step 2: Pick the Category

The WHY ARE YOU PAUSING? picker opens with four category tiles:

This is the same four-way taxonomy the scrap reason picker uses, which is why one glance at a work center's history tells you whether it is an equipment problem or a supply problem.

Step 3: Pick the Specific Reason

Choose the reason underneath the category. The paused punch carries it. The screen now shows the paused state and confirms the reason was recorded.

Step 4: Tap RESUME When Work Restarts

Tap RESUME. The paused punch closes, a fresh run punch opens, and the elapsed clock restarts. From the operation's point of view nothing was lost: production hours resume accumulating, and the gap between them is on the record with its reason attached.

If the operation is actually finished rather than paused, COMPLETE is available directly from the paused screen. Completing from a pause runs the same checks as completing from a run, described in how to complete an operation.

What Changes When You Pause

How to Check It Worked

The running screen shows the paused state rather than a counting clock, and the piece counters have stopped accepting taps (they only increment during a run, which is often how an operator notices they never resumed). Open the Handoff summary: the shift's hours split into setup, run, and down buckets, and your pause shows up under recent pauses with the reason you picked. On the planner side, the operation's daily actual hours reflect run time only.

Common Mistakes

• Forgetting to resume. A punch left paused stops accumulating production hours, so the day's numbers come out short and nobody notices until the operation looks stalled. If the counters will not increment, check whether you are still paused.
• Forgetting to pause. The opposite failure and the more expensive one: an open run punch through a four-hour breakdown books four hours of production time that never happened. Pause first, diagnose second.
• Using WAITING as a catch-all. It is the least actionable category. A broken spindle tapped as waiting sends maintenance nowhere and shows up in the Pareto as a supply-chain problem.
• Correcting a closed punch on the floor. Operators cannot edit closed punches by design. Corrections are a supervisor action in the history drawer, and every one requires a reason and is kept alongside the original.
• Expecting the pause to re-plan the job. It does not. Log through the shift, then reschedule.

Next Steps

Pause is one of four operator actions. The others are starting a job on the kiosk, recording a piece count, and completing an operation. When a pause turns into a real breakdown, the machine breakdown reschedule walkthrough shows what the plan does next.

Every task in this library is indexed on the EDGEBIC how-to hub. Bring your current downtime reason list to a demo of EDGEBIC and we will map it onto the four categories together.