How a Material Step Schedules as an Instant Gate

A material step schedules as an instant gate: it consumes no work-center capacity and takes no shift hours, but its completion time becomes the earliest start for the operations that depend on it. EDGEBIC by User Solutions assigns a material step immediately rather than searching for machine capacity, then feeds its completion into the timing of the next operation. The result is a routing element that never competes for a machine yet still controls the sequence, which is precisely what a component or raw-material line should do.

Not every line in a routing is a machine operation. Some represent the components, sub-parts, or raw materials that flow into the work. Those lines have no setup, no run time, and no place on any shift, but they are far from irrelevant. They are the reason a downstream operation cannot start until its inputs exist.

Two kinds of routing line

A work-center step is a machine operation. It carries setup and run hours, it competes for finite capacity, and the multi-shift allocator has to find real slots for it across shifts and instances. A material step is different in kind. It stands for an input to the process, so it has no machine time of its own and nothing to place on a shift.

EDGEBIC recognizes the difference and handles each accordingly. When a step is a machine operation, the engine runs the capacity search. When a step is a material line, the engine skips the search entirely and assigns it instantly at the point its predecessors allow. There is no bucket to consume, so there is nothing to look for.

Instant assignment, but not zero influence

"Instant" describes the material step's own duration, not its effect on the plan. Scheduling is driven by the dependency graph: an operation's earliest start is the latest completion among all the steps it depends on. A material step sits in that graph like any other node. In the ordinary case it completes the moment it is reached, so it contributes no delay and the operation that needs it starts exactly when it otherwise would.

The value of keeping it in the routing is that the gate is now explicit. The downstream operation is defined as starting after the material, so the sequence is protected. If the material's availability is ever later than the operation's other predecessors, that availability becomes the binding constraint and the operation waits for it. This is how a plan absorbs a late material delivery without pretending the component was on hand. Whether a job without covering supply is planned on an assumed lead time at all, or reported as a shortage instead, is a per-product setting described in plan on lead time vs require on hand.

The engine composes it the same way it composes any predecessor timing. An operation's start is the maximum of its predecessors' end times, and a material step is simply one of those predecessors that happens to resolve instantly in the good case.

A worked example: a component gating a machine operation

Take a two-line routing. Line 10 is a material step, a purchased casting. Line 20 is a machining operation on Mill-2 with 6 hours of work, linked to start after Line 10. The job can start Monday 08:00, and Mill-2 has an 08:00 to 16:00 day shift.

Casting on hand. Line 10 resolves instantly at 08:00. Line 20 sees its only predecessor complete at 08:00, so it starts at 08:00 and, with 6 hours of work, finishes at 14:00. The material step cost nothing on the timeline. It simply confirmed the input was available.

Casting available Wednesday. Now Line 10 carries a readiness of Wednesday 08:00. Line 20's earliest start is the later of Monday 08:00 and Wednesday 08:00, so it starts Wednesday 08:00 and finishes Wednesday 14:00. Mill-2 was free on Monday and Tuesday, but the operation correctly waited on its input. Crucially, Mill-2 never showed two days of phantom load while it waited, because the material step booked no capacity.

That last point is what makes the instant gate valuable. The machine's utilization stays honest. The wait is real, the sequence is respected, and no work center is falsely marked busy during the delay.

Why model it this way

The instant-gate design keeps two things separate that are easy to conflate: what consumes capacity and what controls timing. A machine operation does both. A material line does only the second. By assigning material steps instantly and using them purely as start constraints, EDGEBIC avoids two opposite errors. It never invents machine load for a component that needs no machine, which would inflate utilization and distort the capacity picture. And it never lets an operation start before its inputs exist, which would produce a plan the floor cannot execute.

This is the same discipline that makes finite capacity scheduling trustworthy. Every constraint that should shape the plan is represented, and nothing that should not consume capacity does. A material step is the clean expression of a constraint that is about availability, not about machine time.

For where material fits in the wider flow, how a scheduler nets demand against inventory covers the planning side, and the complete scheduling engine guide shows how dependency ordering, capacity, and timing gates combine into one pipeline. To see how your own routings gate on their inputs, explore the EDGEBIC engine or bring your data to a demo.