The BOR Drift Banner at the Kiosk in EDGEBIC

In EDGEBIC by User Solutions, the BOR drift banner is a non-blocking alert the kiosk raises when the live routing no longer matches the routing snapshot the job was scheduled against. A planner can edit a bill of routing at any time, but a job already on the schedule carries a frozen copy of the routing it was built from. When those two disagree, the operator deserves to know before they start setup, and the banner is how the kiosk tells them. This is a small but important piece of shop floor data collection: making sure the person at the machine is never working blind to a change made in the office.

Why a Job Carries a Frozen Routing

When EDGEBIC schedules a job, it does not simply point at the live bill of routing and hope it never moves. It preserves a snapshot of the routing at the moment the schedule was built, so the plan is reproducible and the actuals can be judged against the standard that was actually in force when the job was sequenced. That preservation is what makes reschedules stable.

The trade-off is that the master routing keeps living. A planner tightens a cycle time after a process improvement, adds queue time to reflect a real buffer, or repoints a step to a different work center. The scheduled job still holds the old snapshot until it is rescheduled. The drift banner exists to close that gap of awareness at the machine.

The Four Fields It Compares

At the kiosk idle screen, EDGEBIC compares the schedule-time snapshot to the live routing across exactly four fields:

If all four still match, the kiosk stays quiet. If any differs, the banner names the field and shows the old value beside the new one, such as "Cycle time (h): 0.14 to 0.12." Nothing is hidden, and nothing that matches is announced, so the banner only ever draws the eye to a genuine difference.

What the Operator Does With It

The banner is informational by design. It never blocks a punch, and the operator can start setup and run the job normally. Its whole purpose is to move a decision that used to happen by accident into the open:

• If the change is intentional and small, the operator notes it and carries on.
• If the change is a cycle-time or setup-time move, the operator can flag the planner so the schedule is refreshed against the new standard on the next run.
• If the change is a work center move, that is the one worth a pause. The schedule and its downstream steps were sequenced around the original machine, so the operator should confirm the intended routing with the planner before committing hours.

Because the actuals the operator records are facts kept separate from the plan, running the job does not silently rewrite anything. The banner simply guarantees the run happens with eyes open, and the reschedule that follows brings the plan back into line.

A Worked Example

A job was scheduled last week with a cycle time of 0.14 hours per piece. Yesterday a planner shortened it to 0.12 after a tooling change. This morning the operator brings the job up at the kiosk.

The idle screen shows: Cycle time (h): 0.14 to 0.12. The schedule was built against 0.14, so its planned hours reflect the slower standard. The operator starts the run, records the real hours and pieces, and tells the planner the routing moved. The planner reschedules, and the plan's remaining hours now reflect 0.12. Nothing was lost, and the floor never ran to a stale number without knowing it.

How It Fits the Rest of the Loop

The drift banner is the front door of a larger honesty story. It tells the operator the routing changed. The actuals they record then flow into the daily rollup, and a reschedule folds them forward with completed steps frozen in place. If you want the next link in that chain, see how a reschedule uses last night's actuals, and for the way captured time and pieces become plan inputs, what is production scheduling sets the frame.

The banner also complements the kiosk's other pre-run guardrails. Before the first run of a step, the prior-step actuals gate checks that upstream steps have actuals. Together they make the kiosk idle screen a short, honest brief: here is what changed since planning, and here is what is still owed upstream, before you commit an hour to the machine. This drift warning is also the only banner the terminal shows, and preventive maintenance and the EDGEBIC kiosk explains why maintenance reaches the plan through the machine's calendar on the planner side instead.

To see how all of this ties into the wider platform, start at the EDGEBIC shop floor guide or the EDGEBIC product overview.