To build a weekly operator roster in EDGEBIC by User Solutions, select the operator, open the Roster sub-tab, add a global shift row, and tick the weekday columns the operator works that shift. Each tick saves immediately. The roster is a weekly pattern, the same shape as a shift's own weekly hours: you set the normal week once and record absences separately as time off. It is what turns a certified operator into available capacity the scheduler can staff.
This post is the rostering task. It sits between certifying people and applying the constraint to a routing step, all of which are walked through in how to set up operators, skills, and rosters.
Before You Start
| Prerequisite | Why |
|---|---|
| Global shifts exist, for example Day Shift and Night Shift | The roster is a shift-by-weekday grid, and it keys on the global shifts |
| The operator exists and is certified in at least one skill | An unrostered or uncertified operator cannot be staffed |
| Work centers using custom calendars derive them from a global shift | A person can only cover a work center shift that traces back to a global shift they are rostered on |
Step 1: Open the Operator's Roster Sub-Tab
Open the Daily Hours tab, select the Operators inner tab, select the operator in the list, and open the Roster sub-tab. The roster grid holds this one person's weekly pattern.
Step 2: Add a Shift Row
At the bottom of the grid, pick a shift in the Add shift selector, for example Day Shift, and click Add Row. A new row appears for that shift with unticked weekday columns. The shifts in the selector are the global shifts, which is why one roster row can cover every machine that mirrors that shift.
Step 3: Tick the Weekdays Worked
On the new row, tick the weekday columns the operator works that shift: Mo Tu We Th Fr Sa Su. Each tick saves immediately, so there is no separate save step. A standard weekday worker on days is Day Shift with Mo through Fr ticked and Sa, Su clear.
Step 4: Add Rows for a Rotation
If the person rotates between shifts, add another row for the second shift and tick its weekdays. Someone on days early in the week and nights later is two rows: Day Shift with Mo, Tu, We and Night Shift with Th, Fr. Use Remove to drop a shift row entirely. This captures the normal pattern once; a specific week off the pattern is time off, not a roster edit.
What Changes When You Roster
| Surface | Effect |
|---|---|
| The qualified pool | On each rostered shift and weekday, the person's hours join the pool for the skills they hold |
| Skill-gated steps | From the next scheduling run, they can be placed into windows this person now staffs |
| The operator calendar | The person's availability shows on the rostered shifts and days |
| Scheduling | Nothing moves until the next run: rostering is master data |
People are budgeted in hours per shift per day. Joe holds one budget of hours on Monday's Day Shift regardless of how many skills he carries, so booking him through one skill leaves fewer hours for another. That hour accounting is described in how EDGEBIC books operator hours.
How to Check It Worked
The roster grid shows the ticked weekdays for each shift row, and after a scheduling run the person appears in the qualified pool for their skills on those days, staffing steps that need them. If a machine still refuses to staff the person, check that the machine's shift derives from a global shift the person is rostered on.
Common Mistakes
- Rostering onto a work center's custom shift with no global parent. No roster row can match it, so skill-gated steps routed there never staff. Derive the shift from a global parent.
- Editing the roster for a one-week absence. The roster is the normal pattern. Record a specific absence as time off instead.
- Expecting the roster to set clock times. It sets presence by weekday. The hours come from the shift, and overlap within a shift is normal.
- Rostering someone who holds no certification. Presence without a skill staffs nothing. Certify first.
Next Steps
Record the exceptions to the pattern with how to record operator time off. To understand why an unstaffed shift becomes unusable capacity for a gated step, read operator and skill scheduling explained.
Every task in this library is indexed on the EDGEBIC how-to hub. To watch a roster turn certified people into a staffed schedule, book a walkthrough of EDGEBIC and bring one shift's crew.
Expert Q&A: Deep Dive
Q: Our people rotate between day and night shifts week to week. How do we roster that without editing every week?
A: Add more than one shift row for the operator. On the Roster sub-tab you can add a Day Shift row and a Night Shift row for the same person, each with its own ticked weekdays. So a rotation where someone works days Monday through Wednesday and nights Thursday and Friday is two rows: Day Shift with Mo, Tu, We ticked and Night Shift with Th, Fr ticked. That captures the normal pattern once. You only touch it again when the pattern itself changes, not week to week. A specific week off the pattern, like a vacation, is recorded as time off rather than by editing the roster, which keeps the roster meaning the usual week and the exceptions clearly separate.
Q: We rostered a welder but jobs on one particular machine still refuse to staff. What is wrong?
A: Almost always that machine uses a custom shift that is not derived from any global shift, so no roster row can ever match it. Roster rows attach to global shifts; a work center shift with no global parent has an identity the roster cannot reference, and a skill-gated step routed there finds an empty pool and fails to schedule. The fix is on the work center's calendar, not the roster: derive that machine's shift from the global shift the welder is rostered on, or roster people onto the global shift the machine mirrors. Once the machine's shift traces back to a global shift with a rostered, qualified person, the step staffs. This is intentional, because a silent pass here would recreate the double-booking problem the labor constraint exists to prevent.
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.