What Is a Short-Confirm Flag on a Routing Step?

A short-confirm flag is a per-step opt-in that tells the scheduler to reschedule the missing hours when an operation is marked complete with fewer hours logged than were planned. It exists so a plant can hold one operation to a stricter standard than the rest of the routing without changing a plant-wide rule. In EDGEBIC by User Solutions the flag lives on the routing step itself, and it only takes effect under one of the three site-wide partial-confirm policies.

How it works

A short confirm happens when an operator stamps an operation finished but the logged hours total materially less than the plan expected. The engine detects the gap with a tolerance of about half a minute, which is there to absorb rounding rather than to forgive real shortfalls. What happens next is a site decision, not a step decision, and there are three possible rules.

The first rule trusts the operator's stamp on every step. The gap is written off and the schedule reclaims the time. The second rule forward-shifts every gap, re-allocating the unlogged hours onto a future slot through the normal capacity search. The third rule is the middle position: trust the stamp by default, except on steps that carry a short-confirm flag. That third rule is the only one where the flag does anything at all.

Under the first two policies the flag is inert. Set it or clear it and nothing about the schedule changes, because the site rule already decides the outcome for every step uniformly. That is deliberate. The flag is an exception mechanism, and an exception mechanism that could override a plant-wide policy would not be an exception, it would be a second policy.

The flag is a plain true or false on the routing step, defaulting to false, so an existing routing behaves exactly as it did before the concept existed. You turn it on only where you have a reason.

A concrete example

Think of two operations in a finishing department. One is a spray booth where the standard allows a generous window because the operator has to wait for coverage to look right. The other is a precision grinding cell where the cycle is fixed by the machine and a missing hour means a part is not to size yet.

The site rule is written for the spray booth, because most of the department looks like the spray booth. When an operator taps complete at three in the afternoon on a job that logged seven of its eight planned hours, that eighth hour was padding. Trusting the stamp is right: the booth is free, the job is done, and re-allocating an hour of imaginary work would push the next job out for nothing.

The grinding cell is the opposite. An hour missing there is an hour of grinding that has not happened. Left alone, the plan quietly loses it and the next operation starts on a part that is not ready. Flagging the grinding step tells the engine to treat its shortfall as owed. On the next reschedule the missing hour is placed on the next slot the cell has free, and the downstream operations move with it.

Same plant, same policy, two steps, two behaviors. That is the whole design.

How EDGEBIC uses it

The flag sits on the routing step alongside the other timing fields, so it is edited where hours, setup, and queue time are edited. The site-wide rule it depends on is set once under the scheduling policy options, and the term for the whole mechanism is covered in partial confirm behavior. Choosing between the three rules, and understanding which one your plant already runs, is walked through in how to set partial confirm behavior in EDGEBIC.

When a shortfall is forward-shifted, the engine schedules only the remaining hours rather than the full planned duration, and the historical portion stays exactly where it happened. That carry-forward, and what the resulting rows look like on a job, is explained in how partial completions carry forward in EDGEBIC. Completed work is never rewritten, which is why the shortfall becomes a new future allocation rather than an edit to a finished row. See why actuals are immutable in EDGEBIC for the rule that makes that necessary.

Used sparingly, the flag is a precision instrument: it lets a shop keep a forgiving default while refusing to lose the hours that genuinely matter. Used everywhere, it is just the forward-shift policy with extra steps. For the wider vocabulary, see the manufacturing glossary, and to see confirm handling inside a live plan, explore EDGEBIC.