- Home
- Blog
- EDGEBIC How-To
- How to Add a Saturday Shift for One Week in EDGEBI…
To add a Saturday shift for one week in EDGEBIC, put a per-day capacity override on the work centers that will run, not a shift edit. Open the per-day capacity dialog, select the shift, find the Saturday row, and type the approved hours in the Capacity (h) column with a reason. It switches on that one Saturday, for those work centers only, and reverses when you click Reset.
Weekend production is off by default. The temptation is to tick Saturday on the shift, but that turns Saturday on forever, for every machine using that shift. The override is the surgical alternative. For the dialog in full generality, read how to override capacity for one day from EDGEBIC by User Solutions.
Before You Start
- You know which work centers will actually work. Overtime is rarely the whole plant.
- You know the approved hours per work center, expressed as the day total across instances.
- You know the shift. Overrides are shift-specific.
- You can rerun the schedule. The Saturday hours do nothing until Drive Schedule runs.
Why an Override, Not a Shift Edit
| Shift edit | Per-day override | |
|---|---|---|
| Scope | Every week the shift runs | The one Saturday you choose |
| Work centers affected | Every one using the shift | Only the ones you override |
| Audit trail | None | Reason field plus an Overridden flag |
| Undo | Untick Saturday again, plantwide | Click Reset on the row |
The override wins on every axis for a one-off. A shift edit is correct only when Saturday becomes a permanent part of the pattern.
Step 1: Open the Per-Day Capacity Dialog
Open the Workcenter tab. On the first work center that will work overtime, click 📊 (tooltip Per-day capacity). The Per-Day Capacity dialog opens.
Alternate route: in Schedule → Resource Calendar, double-click the Saturday cell on the Total Capacity row for the work center.
Step 2: Select the Shift and Find the Saturday
Pick the shift in Shift:. Set the From: and To: range so the target Saturday appears in the grid.
On that Saturday's row, Shift default (h) reads 0, because the weekend is off. That zero is exactly what your override replaces.
Step 3: Type the Approved Hours
Type the approved hours in Capacity (h). Remember the rule: this is the total for the day across every instance, used verbatim.
| Situation | Enter |
|---|---|
| One machine, 8-hour Saturday | 8 |
| Two machines, both 8 hours | 16 |
| Two machines, one staffed for 8 hours | 8 |
| One machine, half day | 4 |
The change saves as you type. The Overridden column ticks.
Step 4: Add a Reason
Enter a Reason so the plan explains itself: Overtime approved, rush order, Saturday catch-up, week of the 12th. Six weeks from now, a Saturday of production with no reason attached is a mystery. With one, it is a record.
Step 5: Repeat for Each Work Center
Capacity belongs to a work center and shift pairing, not to the plant. If four work centers are working Saturday, that is four overrides. Move to each one's 📊 dialog and repeat. Use the same reason text so the audit reads cleanly.
Step 6: Close and Rerun
Click Close, then run Drive Schedule.
What Changes When You Save
| Surface | Effect |
|---|---|
| The override | Saves instantly, Overridden column ticks |
| Resource Calendar | Shows the Saturday hours on refresh |
| Existing schedules | Unchanged until Drive Schedule runs |
| Next scheduling run | Places work on the overridden Saturday, ahead of the shift formula |
| Every other week | Untouched. Only this Saturday gained hours |
How to Check It Worked
- Confirm the Overridden tick on each Saturday row, across every work center you meant to authorize.
- Confirm you entered the day total, not per-machine hours, on each.
- Open the Resource Calendar and read the Saturday capacity. It should match your numbers, and the following Saturdays should still read zero.
- Run Drive Schedule. The rush job's finish date should pull ahead, and Saturday bars should appear only on the work centers you overrode.
Step 7: Let It Expire
The override applies to one date. Next Saturday is untouched automatically, so there is nothing to undo for the following week. If plans change and the overtime is cancelled, reopen the dialog and click Reset on the row to return that Saturday to zero.
Common Mistakes
Editing the shift instead. Ticking Saturday on the shift turns on every Saturday of the year, for every work center on that shift. This is the exact mistake that sits in our shift and calendar mistakes list under "expecting weekend hours to produce weekend work" and its inverse.
Per-machine hours on a multi-instance work center. The override is the day total. Two machines at 8 hours is 16, not 8.
Overriding the wrong shift. If the work center runs days and nights, the Saturday hours land on whichever shift you selected. Pick the one the crew is actually working.
Skipping the rerun. The Saturday hours become available capacity instantly on the dashboards, but no job moves onto them until Drive Schedule runs.
Next
A per-day override is the honest way to authorize weekend overtime: targeted, dated, and self-documenting. The same dialog does the reverse, taking a machine out for maintenance: how to block a machine for a maintenance day. More single-task recipes are in the EDGEBIC how-to hub, and the platform overview is at /edgebic.
Expert Q&A: Deep Dive
Q: A rush order needs our whole finishing line working this Saturday only. That is four work centers. Do I really override each one?
A: Yes, one override per work center, because capacity is a property of the work center and shift pairing, not of the plant as a whole. Open the per-day capacity dialog on each of the four, select the shift, and enter the Saturday hours with the same reason so the audit reads consistently. It is more clicks than a single switch, but it is also the correct granularity: if only two of the four are actually the constraint on the rush job, you can authorize just those two and leave the others on their normal week, which keeps the overtime bill honest.
Q: Our press runs two instances. I want both working eight hours this Saturday. What number goes in the override?
A: Sixteen. The Capacity value is the total for the day across every instance, and the scheduler uses it verbatim without multiplying by the instance count. Two machines at eight hours each is sixteen, so entering eight would give you a half-loaded Saturday and quietly under-deliver on the rush order you are working the weekend for. If you wanted only one of the two presses staffed, sixteen would be wrong the other way: enter eight for a single machine. Read the instance count off the grid before you type.
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.
