How to Add Transit Days Between Two Steps in EDGEBIC

To add transit days between two steps in EDGEBIC by User Solutions, set Transit Days on the upstream routing step and choose whether they count as calendar or working days. The control lives on the routing (Bill of Routing) step whose completion starts the wait. Once you save and reschedule, the downstream step cannot begin until that many days after the upstream step finishes. This models real gaps such as an outside heat-treat vendor's turnaround or a shipment between two plants, without you having to invent a placeholder operation to hold the time.

This recipe covers one specific task. For how transit sits alongside queue and flow time in the schedule, read EDGEBIC queue and transit times explained and the broader recipe how to set queue, flow, and transit times.

Before You Start

• The routing (Bill of Routing) open, with the upstream step identified. That is the step whose completion begins the transit gap, usually the outsourced or shipping operation.
• The number of days parts are away, and whether that number is business days or elapsed days.
• Confirmation that no transfer delay is already set on the same step for the same gap, since the two are additive.

Step by Step

1. Open the routing and select the upstream step (for example, the outsourced heat-treatment operation).
2. Set Transit Days to the number of days parts are away (for example, 3).
3. Set Is Calendar Days to off to count only working days, or on to count every calendar day.
4. Save the routing.
5. Run Generate Schedule.

What Changes When You Save

On the next run, EDGEBIC adds the transit days to the upstream step's end date before it lets the downstream step start. With working days, it counts only days the work center is open, skipping weekends and holidays, so three working days over a weekend can span five calendar days. With calendar days, it counts every day. The transit is applied after any lot-streaming overlap and before the downstream start is fixed, so the gap composes cleanly with the rest of the schedule. Downstream steps shift out by the transit, and the job's finish date reflects the real turnaround.

How to Check It Worked

Open the Job View and compare the upstream step's end date with the downstream step's start. The gap should equal the transit days you set, counted in the mode you chose. For a three-working-day transit with a Thursday completion, the downstream step should start the following Tuesday if Saturday and Sunday are non-working. If the gap is off, confirm the transit days sit on the upstream step and that the calendar-versus-working setting matches your intent.

Common Mistakes

• Transit days on the wrong step. They belong on the upstream step, whose completion starts the wait, not on the downstream step that is waiting. Placing them on the waiting step does not produce the gap.
• Wrong day mode. Working days skip weekends and holidays; calendar days do not. A vendor turnaround quoted in business days should be working days, or the schedule will let the next step start too early.
• Stacking transit days and transfer delay. The two are additive on the same gap. Transfer delay is a sub-hour handling lag for a lot-streaming batch; transit days is a multi-day shipping gap. Use one, not both, for a given delay.
• Confusing transit with queue time. Queue time is a shift-aware buffer that counts only during working hours, for something like a cool-down. Transit days count in whole calendar or working days. For a same-shop buffer, queue time is usually the better fit, as covered in the queue and transit overview.

Where to Go Next

Transit days are one of three inter-step buffers, alongside queue time and lot-streaming overlap. To see them work together on one step, read how to set queue, flow, and transit times, and for a multi-site scenario see multi-plant scheduling with transit times. The full platform is at EDGEBIC, with more recipes in the EDGEBIC How-To Library.