What Is a Cross-Shift Operation in Scheduling?

A cross-shift operation is a single routing step whose hours do not fit inside one shift, so the scheduler places part of them in one shift and the remainder in the next available ones, continuing across days or a closed weekend as needed. It is still one operation with one start, one end, and one hours figure; only its placement is fragmented. The consequence worth internalizing is that its elapsed span and its worked hours are two different numbers, and confusing them is the most common misreading of a production Gantt. EDGEBIC by User Solutions splits operations this way by default.

How it works

The scheduler places an operation by walking forward from the moment it becomes eligible, examining each shift on each day in turn. In each candidate slot it books whatever will fit and subtracts that from what remains. If hours remain, it continues to the next slot. The loop ends when the remaining hours reach zero.

Three things follow from that loop.

The first slot is often partial. An operation eligible from 13:00 on an eight hour day shift can only use the three hours left, not eight. So the first booking is frequently smaller than a full shift, which is normal rather than a sign of contention.

Gaps cost nothing. Nights between shifts, weekends, and closures are skipped without consuming any of the operation's hours. The engine simply finds no capacity there and moves on. The gap is real calendar time and zero machine time.

Setup is counted once. The split is a scheduling artifact, not a physical interruption of the changeover, so the machine keeps its setup between shifts and the routing's setup hours are counted for the operation rather than per fragment. This is closely related to why an operation stays on the same machine for every shift it occupies within a run: moving it to a different machine mid-operation would mean a genuine second setup.

The result is one operation record whose window spans from the first fragment's start to the last fragment's end, with the hours distributed across the days the work actually happened on. Reading the plan correctly means reading both: the window to know when the next step can start, and the hours to know what the operation cost.

A concrete example

An assembly work center runs one machine on a day shift, Monday to Friday, 08:00 to 16:00. No weekend shift. An operation needs twenty hours and becomes eligible on Friday at 12:00.

The operation starts Friday at 12:00 and finishes Tuesday at 16:00. Its elapsed span is four and a half calendar days. Its worked content is twenty hours, exactly as the routing said.

Both numbers are load-bearing and they answer different questions. If you are asked what this operation costs, or how much of the machine's week it consumed, the answer is twenty hours. If you are asked when the next step can begin, the answer is Tuesday at 16:00, and the four and a half days are the honest span. A planner who reads the bar's width as effort concludes the routing is wrong; a planner who reads only the hours misses that the successor cannot start until Tuesday evening.

Cross-shift splitting also happens without a weekend. The same operation on a work center running both a day and a night shift, with two machines, would consume twelve hours across Monday's day shift from a 10:00 start and sixteen on Monday night, finishing at midnight the same calendar day. Same twenty-eight hour class of problem, a span measured in hours rather than days, because the calendar offered more shifts.

How EDGEBIC uses it

Splitting is the default and is what makes long operations schedulable at all: an eighteen hour operation cannot fit an eight hour shift under any arrangement. The slot the engine books into is described in what is a shift resource allocation in scheduling, and what a slot reports as free, including the partial-first-slot case, is covered in what is available capacity in scheduling.

Where the hours actually landed, day by day, is recorded in the structure described in what is a daily hour breakdown. That is the surface to use when the span and the hours disagree and you want to see the distribution rather than infer it from a bar.

Which slots exist at all comes from the calendar. The association between a machine and a shift is defined in what is a work center shift, and closures that remove slots entirely are covered in what is a plant holiday in scheduling. The general distinction between calendar time and working time, which is exactly what a cross-shift span exposes, is laid out in working day vs calendar day in scheduling.

The takeaway

A cross-shift operation is one piece of work wearing several calendar windows. The rule that keeps a plan readable is to hold two numbers in mind rather than one: hours for capacity and cost, elapsed span for when the successor can start. Almost every complaint that a Gantt bar looks impossibly long resolves the moment those two are separated, because the extra width is nights, weekends, and closures contributing calendar time and no machine time at all. For the underlying mechanics see what is available capacity in scheduling and what is a daily hour breakdown, then explore EDGEBIC or, if you are coming from the legacy product, RMDB to EDGEBIC.