- Home
- Blog
- EDGEBIC How-To
- How to Set an Operator Pin in EDGEBIC
To set an operator pin in EDGEBIC by User Solutions, set the routing step's Operator picker to a named person, or drag the operation onto that person's lane on the Schedule View Gantt. The picker is enabled only once the step has a Required Skill, and it lists only operators qualified for that skill. Once pinned, the step schedules only for that person: the rest of the qualified pool is never a fallback, so the pinned person's absence becomes visible schedule movement rather than a silent substitution.
An operator pin is a planner-side assignment, not a kiosk login. The shop floor kiosk has no login or PIN at all. This post covers the planner mechanism; the wider labor model behind it is operator and skill scheduling explained.
Before You Start
| Prerequisite | Why |
|---|---|
| The step has a Required Skill set | The Operator picker is enabled only once a skill is set |
| The person you want to pin is certified in that skill | The picker lists only qualified operators |
| You accept the trade-off | A pin trades schedule flexibility for certainty about who does the work |
Step 1: Confirm the Step Requires a Skill
Open the BOR tab and select the step, or use the BOR Designer's properties panel. Confirm Required Skill is set. A pin without a skill is meaningless, so the Operator picker stays disabled until a skill is chosen. If you have not set one yet, do that first, which is covered in how to require a skill on a routing step.
Step 2: Set the Operator Picker
Set the step's Operator field to the named person. The list shows only operators qualified for the step's skill, so you cannot accidentally pin an uncertified person. Leaving the field on Auto lets the scheduler staff the least-loaded qualified person, which is the right default for most work.
Step 3: Or Pin by Dragging on the Gantt
Alternatively, on the Schedule View with View by set to Operator, drag the operation's bar onto the target person's lane. The drop is accepted only if that person is qualified for the step's skill; an unqualified drop snaps back with the reason. Dropping on the Unassigned lane clears the pin. This is the same pin, set from the Gantt instead of the picker.
Step 4: Reschedule
The pin is stored when you set it, including with the job's preserved routing so it survives reschedules. Run Drive Schedule or a reschedule to see the effect. From then on, only that person's hours count for the step.
What Changes When You Pin
| Surface | Effect |
|---|---|
| The step's staffing | Only the pinned person's hours are considered; the rest of the pool is never a fallback |
| The person's absence | The step slides through their time off to their first day back, not to a colleague |
| A skill change on the step | Keeps the pin; if the person does not hold the new skill, the next run stops with a message naming the problem |
| Clearing the skill | Also clears the pin |
The pin is stored in two places, the global routing and the job's preserved snapshot, so a reschedule that reads the snapshot does not silently drop it. Why the schedule reacts to any labor change only on the next run is described in how EDGEBIC books operator hours.
How to Check It Worked
The step's Operator field shows the named person, and on the Gantt the bar sits in that operator's lane. After a reschedule, the crew line in the bar's tooltip names only the pinned person. If the pinned person is out, the step visibly slides to their return rather than moving to a qualified colleague, which is the pin doing its job.
Common Mistakes
- Confusing the pin with a kiosk login. The kiosk has no login. The pin is a planner-side assignment of a step to a person.
- Pinning everything. A pin removes flexibility. Reserve it for steps where the identity of the person is a real requirement, and leave the rest on Auto.
- Changing a pinned step's skill and expecting the pin to update. The pin survives the change. If the person is no longer qualified, the next run stops with a naming message.
- Expecting a pinned step to fall back during a vacation. It never does. Un-pin to Auto or drag to Unassigned if a substitute is acceptable.
Next Steps
To move a pin from one person to another visually, read how to reassign a job to a different operator. If a pinned step will not schedule at all, an operator cannot be assigned to a step covers the causes.
Every task in this library is indexed on the EDGEBIC how-to hub. To see a pin turn one person's PTO into visible schedule movement, book a walkthrough of EDGEBIC.
Expert Q&A: Deep Dive
Q: We want a specific inspector on a customer's job every time. Is a pin the right tool, and what does it cost us in flexibility?
A: A pin is exactly the right tool when the identity of the person is a requirement, such as a customer sign-off or the one operator you trust with a particular fixture. Set the step's Operator picker to that inspector, or drag the bar onto their lane on the Gantt, and the work schedules only for them. The cost is real and intended. A pinned step never falls back to the qualified pool, so when the inspector is out, the step slides to their first day back rather than going to a colleague. That trades schedule flexibility for certainty about who does the work. Use pins sparingly: for most steps, leaving the operator on Auto lets the scheduler load-balance across everyone qualified and keeps dates tighter.
Q: We changed a pinned step's skill and now the schedule stops with an error naming the person. What happened?
A: The pin survived the skill change, and the pinned person does not hold the new skill. Clearing the skill entirely clears the pin, but changing the skill to a different one keeps the pin deliberately, so a pin is not silently wiped during routine editing. The trade-off is that a skill change can leave a pin pointing at someone no longer qualified. The scheduler catches this immediately and fails fast with a message naming the problem, rather than quietly rescheduling around it. The fix is to either certify the pinned person in the new skill or re-pin the step to someone who holds it. Then reschedule. The stop is the system protecting you from a pin that no longer makes sense.
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
How to Create a Watched-File Integration in EDGEBIC
Create a watched-file integration in EDGEBIC: point it at the file your ERP drops, pick the target entity and import mask, set the debounce, and let a new file trigger the run.
How to Rehearse an Integration With the EDGEBIC Simulator
Use the built-in Simulator to provision demo data, watch real integration runs happen, and prove the mechanism before you point anything at a live ERP. Includes the tear-down rule.
How to Run an Integration Now and Pause All Schedules in EDGEBIC
Force one integration to run with Run Now, cancel a run in progress, disable a single definition, or tick Pause all schedules to stop every automatic sync for the session.
