- Home
- Blog
- EDGEBIC How-To
- How to Add a Second Shift in EDGEBIC and Double Yo…
How to Add a Second Shift in EDGEBIC and Double Your Capacity
To add a second shift in EDGEBIC, open the Daily Hours tab, select the inner Shift tab, and click Add Shift. Name it, tick the weekdays it runs, set the start and end times, and save. Then confirm it reached the work centers you meant it to reach, because that second step is where most of the capacity gets lost.
Adding hours is the single largest lever on a promise date. A one-instance work center on one 8-hour shift offers 8 hours a day. Attach a second 8-hour shift and it offers 16. This page covers that one task from end to end. For the whole calendar model (shifts, holidays, downtime, overrides and how they stack), read how to set up shifts and holidays in EDGEBIC by User Solutions.
Before You Start
- You know the real hours the second crew works, including the days it does not run.
- You know which work centers the shift applies to. Not every machine gets staffed on nights.
- You know which of those work centers are on a custom calendar. Those need the shift added individually.
- You can rerun the schedule afterward. The new hours do nothing until Drive Schedule runs.
Step 1: Open the Shift Management Page
Open the Daily Hours tab from the main navigation, then select the inner Shift tab. The Shift Management page lists your existing shifts with columns S.#, Shift Name, Daily Working Hours, Total Hours, and Actions.
Read the Total Hours column on the shift you already have. That is the weekly number you are about to add to.
Step 2: Click Add Shift
Click Add Shift. The Shift Configuration dialog opens with the heading Add Shift.
Step 3: Name It for When It Runs
Enter the name in Shift Name. Name shifts by when they run, not by who works them: Night Shift, Second Shift, Weekend Shift. This name appears on every capacity screen and on every allocation record, so it has to be self-explanatory to someone reading a report six months from now.
Step 4: Set the Days and the Hours
In the Daily Working Hours section, tick the checkbox on each day the shift runs, then set Start: and End: for that day. Each row shows the computed duration (⏱) as you type, which is your first check that the entry is right.
A standard second shift: Monday to Friday ticked, Start: 16:00, End: 00:00, each row showing 8h. Saturday and Sunday left unticked, contributing zero.
Days do not have to match. A shift can run 10 hours Monday to Thursday and 6 on Friday. Reset All Days clears every day back to 00:00 if you want to start over.
Step 5: Save the Shift
Click Save Shift (💾). The dialog closes and the new shift appears in the grid with its weekly Total Hours.
Step 6: Confirm It Reached the Right Work Centers
This is the step people skip. Open the Workcenter tab and read the Shift Calendar column:
| Badge | What happens to your new shift |
|---|---|
| 🌐 Global (green) | The work center inherits the new shift automatically. Nothing more to do |
| 📅 Custom (amber) | The work center follows only its own shift list. Your new shift does not apply until you add it there |
For a Custom work center that should work the new shift, click ✏️ Edit, go to the Associated Shifts tab, use Add Existing Shift, tick the new shift, click Add Selected, and Save. The mechanics are in giving one work center its own calendar.
What Changes When You Save
| Surface | Effect |
|---|---|
| Shift Management grid | Updates immediately with the new Total Hours |
| Work centers on Global | Gain the hours as available capacity at the next scheduling run |
| Work centers on Custom | Unaffected until you add the shift to their own list |
| Resource Calendar and dashboards | Show the higher capacity when refreshed |
| Existing schedules | Unchanged until you run Drive Schedule |
How to Check It Worked
- Confirm the new row on the Shift Management grid, with the Total Hours you expected (40 for five 8-hour days).
- Open the Resource Calendar and read a work center's total capacity for a normal day. A one-instance machine on two 8-hour shifts should read 16 hours where it read 8.
- Run Drive Schedule and compare finish dates. A 20-hour operation that took three days on one shift should now finish inside two.
- Open the Gantt and confirm bars appear inside the new window. If capacity rose but nothing moved, the schedule was never rerun.
Common Mistakes
Assuming a work center works every shift. Capacity comes from the pairing of a work center and a shift, not from the shift alone. A machine attached to only one shift is dark during the other, no matter how many shifts the plant has defined.
Adding the shift and never rerunning. Saving a shift never moves a schedule. The dashboards will show more capacity while the Gantt shows the old plan, which reads like a bug and is not one.
Editing the existing shift instead of adding a new one. If you widen Day Shift from 08:00 to 00:00 rather than creating a second shift, you lose the ability to see which crew is loaded and you change the calendar for every work center using it. Two named shifts keep the allocations readable.
Overlapping the two shifts by accident. Ending the first at 16:30 and starting the second at 16:00 double-counts half an hour of clock on every working day. Read the durations on both cards before saving.
Next
A shift is only real for the work centers attached to it, and only in the plan after Drive Schedule runs. If your second shift crosses midnight, read how to set up an overnight shift next for the day-attribution rule. More single-task recipes live in the EDGEBIC how-to hub, and the platform overview is at /edgebic.
Expert Q&A: Deep Dive
Q: We added a night shift last week and the plan barely changed. Total capacity on the dashboard went up. Why did jobs not spread into the evening?
A: Two candidates. First, check whether you reran Drive Schedule after saving the shift. The dashboards read the calendar directly and show the new capacity immediately, while the Gantt shows the plan as last computed, so a rise in available hours with no movement in the bars usually means the schedule was never rebuilt. Second, check which work centers actually gained the shift. If the constraint machine is on a custom calendar with the amber badge, it did not pick up the new global shift, so the plant has more capacity everywhere except the one place that governs the finish date.
Q: Our second shift starts when the first ends, 16:00 straight after 08:00 to 16:00. Will a job run across the handover without stopping?
A: Yes. A job that needs more hours than one shift offers continues into the next available shift on the same work center, and the allocation records show which shift and which instance each slice ran on. A 20-hour operation on a one-instance mill working both an 08:00 to 16:00 and a 16:00 to 00:00 shift finishes at 20:00 on the second day rather than midday on the third. The only thing to check is that both shifts are attached to that specific work center, since capacity comes from the pairing, not from the shift alone.
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.
