How to Turn Off Lot Streaming on a Step in EDGEBIC

To turn off lot streaming on a routing step in EDGEBIC by User Solutions, set both Transfer Batch and Flow Step (hrs) to zero on that step and save the routing. With every overlap field at zero, the next step waits for this one to finish completely. Two fields, one save, one scheduling run. The reason it is worth a dedicated procedure is that the two fields are independent, and clearing one while leaving the other set produces exactly the symptom you were trying to remove.

Overlap is usually a good thing. Letting the next operation start on the first pallet while the rest of the lot is still being made is the classic transfer batch idea, and it buys real days. It stops being a good thing the moment the shop cannot actually do it: a furnace that cannot release a partial load, a plating line that ships whole lots, a cell where the material handler runs twice a shift and no more.

Before You Start

• Know which step carries the setting. Streaming lives on the upstream step, the one whose partial output the successor is waiting for. That is the row to edit.
• Check whether the work center is marked Continuous-Process. On such a machine, transfer batches are ignored and only Flow Step streams. Zeroing the batch there changes nothing. See how to mark a work center as continuous process.
• Expect dates to move out. Removing overlap returns the time it was saving.

Step 1: Open the Routing and Find the Step

Open the BOR tab and select the routing. In the data grid, the relevant columns are Flow Step (hrs), Transfer Batch, Transfer Delay h, and Transit Days. Overlapping bars on the Gantt trace back to a non-zero value in one of the first two.

Step 2: Zero Both Streaming Fields

On the upstream step's row:

• Set Transfer Batch to 0. This is the piece-count model: it was letting the successor start once the first N pieces existed.
• Set Flow Step (hrs) to 0. This is the start-to-start lag model: it was letting the successor start a fixed number of hours after this step began, regardless of quantity.

Zero both even if you believe only one was set. They are separate mechanisms and they do not clean each other up.

Step 3: Decide What Happens to Transfer Delay

Transfer Delay h is a flat handling lag that rides on top of a streaming gate: forklift time, a cooldown before parts can be touched. With streaming off, ask what it was there for.

Queue time is the natural home for a post-operation buffer on a serial step. Flat elapsed hours can land past shift end, at which point the capacity search simply finds the next open slot, which is rarely what a planner means by a two-hour cooldown. How to add queue time before an operation covers that field.

Step 4: Save the Routing

Click Update Standard BOR to change the recipe for every future job, or update the job's own copy if you only want one order affected. Nothing on the Gantt moves at this point. Routing edits change the recipe, not the plan.

Step 5: Reschedule

Run Drive Schedule. The successor step now waits for the upstream step to complete, plus whatever queue time or transit days remain on it.

What Changes When You Save

That last row is the one people miss. While a streaming gate is active on a step, any Queue Time (hrs) configured on the same step is discarded, even if the queue would have ended later. Turning streaming off hands the step back to its queue time. If that value is stale, it is about to start mattering again. Look at it before you reschedule rather than after someone asks why welding now starts four hours later than expected.

How to Check It Worked

1. On the BOR grid, confirm both Transfer Batch and Flow Step (hrs) read 0 on the step.
2. Run Drive Schedule.
3. Open the Job View Gantt and look at the two bars. The downstream bar should now begin at or after the upstream bar's end, with a visible gap if queue time or transit days apply.
4. Open the Scheduler Anomalies report and confirm the F-checks for that step are quiet. A step with two streaming models set, or with queue time fighting a flow step, shows up there.

Common Mistakes

• Zeroing one field and not the other. Transfer Batch and Flow Step are independent. Clear both.
• Editing the wrong step. Streaming sits upstream, on the step producing the parts, not on the step waiting for them.
• Forgetting the continuous-process rule. On a work center flagged Continuous-Process, a transfer batch was never doing anything, so removing it cannot be the fix. Flow Step is the field in play there.
• Leaving a stale queue time to surprise you. It was inert; now it is not.
• Not rescheduling. The recipe changed. The plan did not, until you run it.
• Turning overlap off when the real problem is the size. If the shop can move partial lots but not in sublots of 5, raise the batch rather than removing streaming altogether. A practical starting point is the order quantity split into four or five sublots.

Where to Go Next

If you are switching models rather than removing overlap, how to set a transfer batch size covers the piece-count route and how to set a flow step overlap covers the hours-based one. For gaps that are travel rather than overlap, see how to add transit days between two steps. The full index is at the EDGEBIC How-To Library, and the platform is at EDGEBIC.