EDGEBIC How-To

How to Deactivate an Operator in EDGEBIC

User Solutions TeamUser Solutions Team
|
6 min read

To deactivate an operator in EDGEBIC by User Solutions, open the Operators tab under Daily Hours, select the person, uncheck Active, and save. An inactive operator drops out of the scheduling engine's feed, so no new work is staffed to them on the next run, while their history, certifications, roster, and time off all stay intact. Deactivation is the reversible, history-preserving way to retire a person from scheduling.

Deactivating is not deleting. Deletion throws the record away and is guarded when a routing step is pinned to that person; deactivation keeps the audit trail and lets the operator come back. This page covers the clean retirement and the one cleanup step that prevents a scheduling problem afterward. To create an operator in the first place, see how to add an operator.

Before You Start

  • You know which steps are pinned to the operator. A step hard-assigned to one named person has no fallback, so it needs a plan before the person leaves the feed.
  • You have a reassignment plan for pinned steps. Another qualified operator, or removal of the pin, for any step that names this person specifically.
  • You want to keep the history. If so, deactivate rather than delete, so past jobs the person was planned into stay readable.

Step 1: Open the Operator

Open the Daily Hours tab and select the Operators inner tab. This is the operators manager, with the operator list on the left and detail sub-tabs for skills, roster, and time off on the right. Select the person you want to retire.

Step 2: Uncheck Active

Uncheck Active on the operator. This marks the person out of service for scheduling. Their skills, roster rows, and time off are not deleted; they simply stop counting as available capacity.

Step 3: Save

Save the operator. The person is now inactive: no longer part of the engine feed, so the next scheduling run staffs no new work to them, while every historical booking that named them stays intact and readable.

Step 4: Clear Any Pinned Steps

Deactivating removes the person from the feed but does not rewrite routings. A step pinned to one named operator never substitutes anyone else, so with that operator inactive the step's qualified pool is empty and it will slide or fail loudly. Find any steps pinned to the person, reassign them to another qualified operator or remove the pin, then rerun Drive Schedule. Steps that only required a skill rather than a specific person are covered by the remaining certified, rostered operators, though work can slide if losing one person tightens capacity.

What Changes When You Save

SurfaceEffect
The scheduling engineExcludes the operator from the qualified pool on the next run
New workNo steps are staffed to the person going forward
History and certificationsPreserved and readable; past bookings still name the person
A step pinned to the operatorHas an empty pool until reassigned, so it slides or fails loudly

Deactivating an operator moves no bars on its own. Work only re-staffs on the next scheduling run, which is when the person's absence from the pool takes effect.

Deactivate Versus Delete

ActionWhen to useEffect
Deactivate (uncheck Active)Someone who has left or is on indefinite leaveReversible; history preserved; out of the feed
DeleteA record created in error and never usedGuarded while any routing step is pinned to the person; throws away history

The delete guard is deliberate: it refuses to remove someone a pinned step still depends on, so you cannot orphan a routing by accident. For anyone who has done real work, deactivation is the correct path.

Reactivating an Operator

Deactivation is reversible, which is much of why it beats deletion. If the person returns, open them, recheck Active, and save. Because their certifications, roster, and time off were never thrown away, they rejoin the qualified pool immediately and are schedulable again at the next run, with their past and new bookings on one continuous record. That makes deactivation the right tool for a seasonal layoff, a long leave, or a contractor between assignments, where a delete would force you to rebuild the whole record and lose the trail.

Common Mistakes

  • Deactivating without clearing pinned steps. A step hard-assigned to the person has no fallback and will slide or fail. Reassign or unpin those steps, then rerun.
  • Deleting instead of deactivating. Deletion loses history and is guarded while the person is pinned to any step. For someone who ran real jobs, deactivate.
  • Confusing deactivation with time off. For a vacation or training week, use time off so the person returns automatically. Deactivation is for an open-ended exit.
  • Expecting bars to vanish on save. Deactivation stops new staffing; it does not move work already planned. Rerun to rebuild the schedule without the person.

Next Steps

To handle a temporary absence rather than a permanent exit, see how to record operator time off. For the parallel retirement of a machine, read how to deactivate a work center. Every task is indexed on the EDGEBIC how-to hub, and the platform overview is at EDGEBIC.

Expert Q&A: Deep Dive

Q: A machinist left mid-quarter but they are on jobs that already ran. Do we delete them?

A: Deactivate, do not delete. Unchecking Active takes the person out of the engine feed so no future work is staffed to them, while every historical record stays intact, so their name still appears on the jobs they were planned into. Deletion is guarded anyway if any routing step is pinned to that person, and even where it is allowed it throws away history you may want for an audit. The rule of thumb is simple: people who have left get deactivated, and a hard delete is reserved for a record created in error that never touched a real schedule.

Q: We deactivated an operator and now a skill step will not schedule at all. What did we miss?

A: That step was almost certainly pinned to the operator you just deactivated, and a pinned step never substitutes another person, so with them out of the feed the qualified pool for that step is empty and it slides or fails loudly. Before deactivating someone who is pinned to steps, reassign those steps to another qualified operator or remove the pin. If the step only required a skill rather than a specific person, other certified, rostered operators cover it, though the work can slide if losing one person tightens capacity.

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

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.

Let's Solve Your Challenges Together