- Home
- Blog
- EDGEBIC How-To
- How to Set Up an Overnight Shift in EDGEBIC (Cross…
How to Set Up an Overnight Shift in EDGEBIC (Crossing Midnight)
To set up an overnight shift in EDGEBIC, enter the times exactly as the crew works them on the Shift Configuration dialog, with the evening start and the morning end. An end time at or before the start (22:00 to 06:00, or 16:00 to 00:00) is read as crossing midnight, and the wrap-around arithmetic is handled for you. There is no special overnight checkbox.
The one thing worth internalizing is day attribution: overnight hours count on the day the shift starts, not the day it ends. Get that and everything else follows. This page is the single task. For the whole calendar model these hours live in, read shifts and calendars explained from EDGEBIC by User Solutions.
Before You Start
- You know the real start and end times, including how far into the morning the shift runs.
- You know the days it starts, which is not always the days you think (a Friday-start night shift runs into Saturday).
- You know which work centers run it, and whether any are on a custom calendar.
- You can rerun the schedule.
Step 1: Open the Shift Configuration Dialog
Open the Daily Hours tab, select the inner Shift tab, and click Add Shift. The Shift Configuration dialog opens with the heading Add Shift.
To edit an existing shift into an overnight pattern instead, click the pencil icon in the Actions column of its row.
Step 2: Name It
Enter the name in Shift Name: Night Shift, Graveyard, Third Shift. Name it for when it runs, since this label appears on every allocation record and capacity screen.
Step 3: Enter the Wrap-Around Times
In the Daily Working Hours section, tick the days the shift starts, then set Start: to the evening time and End: to the morning time.
Two common patterns:
| Pattern | Start | End | Duration |
|---|---|---|---|
| Evening into midnight | 16:00 | 00:00 | 8h |
| Late night into morning | 22:00 | 06:00 | 8h |
| Twelve-hour nights | 19:00 | 07:00 | 12h |
Enter them literally. The dialog detects that the end is at or before the start and treats the shift as running past midnight, adding a day to the end internally. The row's computed duration (⏱) confirms the math: 22:00 to 06:00 shows 8h, not a negative number.
Step 4: Mind the Days You Tick
Tick the evenings the crew actually clocks in, not the mornings they clock out.
A night shift running Sunday through Thursday nights means you tick Sunday, Monday, Tuesday, Wednesday, Thursday. The Sunday-night crew's hours run into Monday morning but count as Sunday. Friday and Saturday stay unticked, because a Friday-start shift would run into Saturday morning, and a Saturday-start into Sunday.
This is where day attribution bites, so decide the start days on purpose.
Step 5: Save
Click Save Shift (💾). The shift appears in the grid with its weekly Total Hours.
Step 6: Attach It to the Right Work Centers
A shift produces capacity only on the work centers attached to it. Open the Workcenter tab and check the Shift Calendar column:
- Global (green): the work center inherits the new shift automatically.
- Custom (amber): add the shift to the machine's own Associated Shifts list first (how to give one work center its own calendar).
For around-the-clock coverage, attach both the day and night shifts to the machine. One shift alone leaves it dark for the other half of the day.
How the Hours Are Attributed
The scheduler credits overnight hours to the calendar day the shift starts on. A 22:00 to 06:00 shift beginning Monday puts all 8 hours against Monday, even though 6 of them fall in Tuesday's early hours by the clock. Read every night allocation against its start day and the plan lines up. This is documented behavior, not a rounding quirk, and it is why night bars can appear "a day early" on the Gantt.
What Changes When You Save
| Surface | Effect |
|---|---|
| Shift Management grid | Shows the new shift and its Total Hours |
| Work centers on Global | Gain the overnight hours at the next run |
| Work centers on Custom | Unaffected until you add the shift to their list |
| Existing schedules | Unchanged until Drive Schedule runs |
How to Check It Worked
- Confirm the shift's Total Hours on the grid (40 for five 8-hour nights).
- Open the Resource Calendar and read a work center's capacity. With both a day and a night 8-hour shift attached, a one-instance machine should read 16 hours.
- Run Drive Schedule and open the Gantt. Night bars should sit in the evening-into-morning block, attributed to their start day.
- Confirm a long job flows across the day-to-night handover without a gap, if both shifts are on the machine.
Common Mistakes
Ticking the wrong days. Ticking the mornings the shift ends instead of the evenings it starts shifts every night by a day and can put production into an unintended weekend. Tick start days.
Attaching only one shift. Around-the-clock capacity needs both shifts on the machine. A day-only mill produces nothing at night regardless of how the night shift is defined.
Reading the allocation against the wrong day. Overnight hours count on the start day. A Monday-evening shift's early-Tuesday work is Monday's, and treating it as Tuesday's is the most common misread, listed under our shift and calendar mistakes.
Forgetting the rerun. Adding the shift raises available capacity, but no job moves onto the nights until Drive Schedule runs.
Next
An overnight shift is just a shift with wrap-around times and one rule to remember: hours count on the start day. Pair it with the day shift on the same machines for round-the-clock capacity. To add that day shift or a second crew, see how to add a second shift. More single-task recipes are in the EDGEBIC how-to hub, and the platform overview is at /edgebic.
Expert Q&A: Deep Dive
Q: Our night crew runs 20:00 to 04:00 Sunday through Thursday. The Sunday-night bars are showing on Sunday but the work is really Monday morning. Is that a bug?
A: No, that is the day-attribution rule working as designed. Overnight hours are credited to the calendar day the shift starts on, so a 20:00 to 04:00 shift that begins Sunday evening has its full eight hours attributed to Sunday even though four of them fall in Monday's small hours. Read the allocation against the start day and it is correct. The practical consequence is at the week boundary: a shift starting Friday evening runs into Saturday, so if you do not want Saturday-morning production, do not tick Friday on the night shift. Tick the evenings you actually start work, not the mornings you finish it.
Q: We want one mill running around the clock. How do the day and night shifts fit together on it?
A: Assign both shifts to that work center, not just one. A machine attached only to the day shift is dark all night no matter how the night shift is defined, which is the most common reason around-the-clock capacity does not materialize. With an 08:00 to 16:00 day shift and a 16:00 to 00:00 night shift both attached, a one-instance mill offers 16 hours a day and a long job flows straight through the 16:00 handover without stopping. Confirm the pairing on the work center's Associated Shifts tab, or trust the global calendar if the machine carries the green Global badge and both shifts are global.
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.
