- Home
- Blog
- EDGEBIC How-To
- How to Set a Flow Step Overlap in EDGEBIC
To set a flow step overlap in EDGEBIC by User Solutions, turn on the work center's continuous-process flag and set the routing step's Flow Step to the number of hours after the operation starts that the next step may begin. The control lives on the routing (Bill of Routing) step for a continuous-process operation. Once saved and rescheduled, the flow step acts as a start-to-start lag: a coating run from 8am to 4pm with a flow step of two lets the next step begin at 10am, overlapping the tail of the coating. Since the 2026 semantics update, the flow step is a plain hours-after-start lag, independent of quantity, per-piece time, and setup.
This is a single configuration task. For how the two overlap models fit together, read EDGEBIC lot streaming explained and the broader recipe how to overlap operations.
Before You Start
- The work center for the continuous-process operation, so you can turn on its continuous-process flag. This model is for equipment that processes material continuously, such as a coater, oven, or paint booth.
- The routing (Bill of Routing) open, with the continuous-process step identified.
- The overlap you want, in hours after the operation starts. This is how long the downstream step must wait before enough material has accumulated to begin.
Step by Step
- Open the Work Centers screen, select the continuous-process machine, and set Is Continuous Process to on.
- Open the routing and select the step for that operation.
- Set Flow Step to the number of hours after the upstream start that the next step may begin (for example, 2).
- Set Transfer Batch Size to 0 so the flow step branch fires rather than the piece-count branch.
- Save the routing.
- Run Generate Schedule.
What Changes When You Save
On the next run, EDGEBIC sets the downstream step's earliest start to the upstream start plus the flow step hours. It does not matter how long the upstream operation runs or how many pieces it makes: the lag is fixed in hours from the moment the operation starts. A flow step larger than the upstream run acts as a pure start-to-start lag that still ends after the upstream finishes. The two operations overlap on the Gantt, and the sequence completes sooner than it would with each step waiting for full completion.
How to Check It Worked
Open the Job View and find the two steps. The downstream step should start exactly the flow step hours after the upstream step starts, not after it ends. For the 8am coating example with a flow step of two, the next step should show a 10am start. If the downstream step still waits for full completion, confirm the flow step is greater than zero and that the transfer batch size on the same step is zero.
Common Mistakes
- Treating a tiny flow step as "off." A small flow step means the successor may start almost immediately after the predecessor starts, which is the most overlap possible. To remove the overlap, set the flow step to zero, not to a small fraction.
- Combining flow step with queue time. When both are set, EDGEBIC computes the queue time and then replaces it with the flow step result, discarding the queue. The anomaly report flags this. Use transfer delay for a handling lag on top of the flow step, or set the flow step to zero if the shift-aware queue is what you want.
- Setting the continuous-process flag on a discrete machine. That flag blocks the piece-count model for the whole machine, even when a routing step legitimately wants a transfer batch size. Only set it on genuinely continuous equipment.
- Expecting the flow step to react to quantity. Larger orders do not lengthen a flow step, because it is a fixed hours lag. If you need overlap that scales with pieces produced, use a transfer batch size instead, as in how to set a transfer batch size.
Where to Go Next
The flow step and the transfer batch size are the two lot-streaming models. If your machine makes discrete pieces, read how to set a transfer batch size, and for a side-by-side comparison see piece count versus time lag overlap. To put a step back on strict serial flow, see how to turn off lot streaming on a step. The full platform is at EDGEBIC, and more recipes live in the EDGEBIC How-To Library.
Expert Q&A: Deep Dive
Q: A very small flow step made the overlap huge, not tiny. Why?
A: A flow step is a start-to-start lag, so a small value means the next step may start almost immediately after the first one starts, which is the maximum overlap, not the minimum. If you meant to remove the overlap, set the flow step to zero rather than to a tiny number. Zero makes the downstream step wait for full upstream completion, which is the no-overlap behavior.
Q: My paint booth uses a flow step and I want to be sure a batch size can never override it. How?
A: Turn on the continuous-process flag for the paint booth work center. With that flag on, EDGEBIC always uses the flow step model and ignores any transfer batch size a routing step might carry. The anomaly check also flags the mismatched combination so you can clean it up, but the flag alone guarantees the flow step governs and the piece-count model is suppressed on that machine.
Frequently Asked Questions
Ready to Transform Your Production Scheduling?
User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.

User Solutions Team
Manufacturing Software Experts
User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.
Share this article
Related Articles
How to Create a Watched-File Integration in EDGEBIC
Create a watched-file integration in EDGEBIC: point it at the file your ERP drops, pick the target entity and import mask, set the debounce, and let a new file trigger the run.
How to Rehearse an Integration With the EDGEBIC Simulator
Use the built-in Simulator to provision demo data, watch real integration runs happen, and prove the mechanism before you point anything at a live ERP. Includes the tear-down rule.
How to Run an Integration Now and Pause All Schedules in EDGEBIC
Force one integration to run with Run Now, cancel a run in progress, disable a single definition, or tick Pause all schedules to stop every automatic sync for the session.
