How to Set a Transfer Delay in EDGEBIC

To set a transfer delay in EDGEBIC by User Solutions, open the upstream routing step and enter a value in hours in the Transfer Delay field. It adds a flat material-handling lag after a transfer batch is ready, on top of the lot-streaming overlap, so the downstream step starts at the upstream start plus the flow time plus the delay. The control lives on the routing step, in the Bill of Routing.

Transfer Delay is the field that models the physical move: the forklift run, the crane lift, the walk to the next cell. It is deliberately separate from queue time and transit days, and mixing them up is the usual reason a plan overlaps too much or too little.

Before You Start

• The step already has a transfer batch set, or is a continuous-process step using a flow step. Transfer Delay adds a lag on top of an overlap, so there must be an overlap to add it to. See how to set a transfer batch size.
• You know the move time in hours. 30 minutes is 0.5, 45 minutes is 0.75.
• You can rerun the scheduler to see the effect.

Step 1: Open the Routing Step

Open the Bill of Routing for the product, in either the Grid View or the Designer. Select the upstream step: the one that produces the pieces that get moved.

Step 2: Confirm the Overlap Is There

Check that the step has a Transfer Batch Size greater than zero on a discrete work center, or a Flow Step on a continuous-process work center. This is the overlap the delay attaches to.

If neither is set, a handling gap between operations is better expressed as Queue Time, not Transfer Delay.

Step 3: Enter the Transfer Delay

Set Transfer Delay to the move time in hours. A 45-minute forklift move is 0.75. A two-hour crane-and-stage sequence is 2.

Leave Queue Time at zero on this step. When a lot-streaming model is active, the queue-adjusted end is replaced, so a queue time here would simply be discarded and the anomaly report would flag the combination.

Step 4: Save and Reschedule

Save the routing, then run Schedule / Re-Schedule so the change reaches the plan.

What Changes When You Save

The downstream step's earliest start moves later by the delay. Its new start is the upstream start plus the lot-streaming flow time plus the transfer delay, reconciled to a feasible capacity slot. Transit days, if any, still compose after that. Nothing about the upstream step's own duration changes; the delay lives in the gap between the two steps.

How to Check It Worked

1. On the Job View, confirm the downstream bar now starts later by roughly the delay you entered, relative to the overlap without it.
2. Open the step-by-step schedule and confirm the downstream operation's planned start reflects the added lag.
3. Run the anomaly report and confirm the step is not flagged for a queue-time-plus-lot-streaming conflict. If it is, clear the queue time on that step.

Common Mistakes

Putting queue time on a lot-streaming step. When lot streaming is active, the queue-adjusted end is replaced, so queue time is discarded and flagged. Use Transfer Delay for the lag instead.

Using transit days for a sub-hour move. Transit days are a calendar or working-day gap for parts that leave the facility. A forklift move across the shop is hours, not days. Use Transfer Delay.

Adding a delay with no overlap to attach to. Transfer Delay is a lag on top of a lot-streaming overlap. On a non-overlapping step, use queue time. Set the transfer batch first.

Next

Transfer Delay is the flat handling lag that sits on top of a transfer batch, and keeping it distinct from queue time and transit days is what makes a lot-streamed plan realistic. To set the overlap it attaches to, read how to set a transfer batch size and what a transfer batch is. For the calendar-based gap instead, read how to add transit days between two steps. More single-task recipes are in the EDGEBIC how-to hub, and the platform overview is at /edgebic.