A Booking Falls Outside Its Shift Hours

A booking that falls outside its shift's working hours has a mismatch between the shift the operation used and the hours now in effect: usually a work-center shift override with a different window than the global shift, or a shift whose daily hours were changed after the plan was made. The scheduler places work inside the defined hours, so a booking outside them almost always means those hours changed or an override you did not expect is in play. Aligning the hours and re-running scheduling clears it.

EDGEBIC by User Solutions defines a shift as a set of per-weekday working windows, and it schedules operations inside those windows. When a booking's clock times fall outside the hours defined for its day of week, the anomaly report flags it. This post, part of the EDGEBIC troubleshooting guide, covers the two causes and their fixes.

Shifts Define Hours by Weekday

A shift is not a single block; it carries separate start and end times for each day of the week, so Monday can run eight to four while Saturday runs a half day or none at all. The scheduler places every operation inside the window for the relevant weekday. The shift-bounds check flags any booking whose clock window falls outside the start and end defined for that day, comparing the operation's actual times against the shift's daily hours.

Overnight shifts, where the end time is earlier in the clock than the start, are excluded from the check to avoid false positives, since those legitimately cross midnight.

Cause 1: A Work-Center Shift Override

A work center can carry its own shift definition that takes precedence over the global shift for bookings on that machine. If the override window differs from the global one, an operation on that machine can run to hours the rest of the plant does not, and it looks like it is running outside shift when it is actually following the override.

How to tell: the symptom appears on one machine while the rest of the plant stops on time, and that machine has a work-center-specific shift with different hours.

Fix: open the machine's shift assignment and compare its window to the global shift. If the difference is intended (that machine genuinely runs later), the booking is correct. If not, correct the override so its hours match what you expect, then re-run scheduling for the machine's jobs. See how to add a second shift and how to set up shifts, holidays, and downtime for where shift windows live.

Cause 2: The Shift Hours Changed After Scheduling

If a shift's daily hours were edited after a plan was made, bookings placed under the old hours can now fall outside the new ones. Shortening an afternoon shift, for example, leaves any work already scheduled into the removed hours sitting outside the shorter day. Editing shift hours does not retroactively move work already booked into the window you changed.

How to tell: the shift was edited recently, and the flagged bookings predate the edit, running past the new start or end.

Fix: re-run scheduling for the affected jobs. The engine replans them inside the current hours. Any time you change a shift's hours, reschedule the jobs already booked in the affected window.

Confirming the Fix

After aligning the shift hours or correcting the override and re-running scheduling, re-open the anomaly report and confirm the shift-bounds chip returns zero rows for the job. On the Gantt, each operation's clock window should sit inside the shift's working hours for its weekday.

Prevention

• Reschedule after any shift edit. Whenever you change a shift's start or end times, run one scheduling pass over the jobs booked in the changed window, so no plan is left running past the hours it should respect.
• Know which machines carry overrides. A work-center-specific shift is easy to forget. When a booking on one machine looks wrong, check its override before assuming a bug, since the override is the scheduler doing exactly what it was told.
• Keep weekday hours complete. A shift with hours defined only for some weekdays can push work into a day it should not run; fill in every weekday the machine actually works.
• Distinguish this from a missing second shift. If work is not filling an evening shift at all, that is a different symptom covered under the schedule not using your second shift; this post is about work running outside the hours that are defined. A warning that a day's bookings exceed the shift-design cap is different again, and a work center booked past its shift design covers how to tell planned overtime from a stale shift setting.