To set partial-confirm behavior in EDGEBIC, open Settings and then the Schedule tab, find the Partial-Confirm Behavior group, and choose how a short confirm is handled: trust the operator's Actual End, forward-shift the remaining hours, or trust the stamp except on flagged steps; then click Save. In EDGEBIC by User Solutions a short confirm is when an operator marks an operation finished but logged fewer hours than planned, and this policy decides whether the next reschedule writes off the gap or re-plans it, all without ever moving completed work.
This post covers one policy setting. For the whole Settings and Schedule screen, see how to configure scheduling policy in EDGEBIC; the full task library is at the EDGEBIC how-to hub.
Before You Start
- You can reach the Settings tab; it is permission-controlled.
- You know how your shop treats a close-out: is the operator's finish the ground truth, or should unfinished hours stay in the plan?
- You understand this affects future work only. Completed operations never move on a reschedule.
The Steps
- Open the Schedule policy tab. From the main navigation open Settings, then the Schedule sub-tab.
- Find the Partial-Confirm Behavior group. Scroll to the group of that name.
- Choose the option. Pick one:
- Trust the operator's Actual End writes off the missing hours; the finish stamp is final.
- Forward-shift the remaining hours (default) re-plans the gap on a future slot; downstream steps queue behind it.
- Trust Actual End unless the step is flagged short trusts the stamp everywhere except on routing steps flagged for strict tracking.
- Save. Click Save. The next scheduler run uses the new policy; there is no restart.
- Run the scheduler and watch how a short-confirmed operation's gap is handled downstream.
What Changes When You Save
| Surface | Effect |
|---|---|
| Trust the operator's Actual End | The finish stamp is final; missing hours are written off, pulling later work earlier. |
| Forward-shift the remaining hours | The planned-minus-logged gap is re-planned on a future slot; downstream steps queue behind it. |
| Flagged variant | Strict forward-shift only on steps you flag; everything else trusts the stamp. |
| Completed operations | Never move, under any option. |
| Stored data | None. Only the next reschedule's placement of future work changes. |
How to Check It Worked
Log a short confirm on a test operation, recording fewer hours than planned, then run the scheduler. With Forward-shift the remaining hours, the missing hours should reappear as future work and downstream steps should queue behind them. Switch to Trust the operator's Actual End, save, and re-run; the gap should now be written off and later work pulled earlier. If the same short confirm produces the two different downstream outcomes, the policy is taking effect.
Common Mistakes
Expecting completed work to move. No option moves a completed operation. Partial-confirm behavior only decides how the gap from a short confirm is treated in future planning.
Choosing trust when hours must stay visible. If you trust the Actual End, the missing hours are written off and disappear from the plan. In a shop where unfinished work must stay tracked, forward-shift is the safer default.
Forgetting to Save and run. Policy is read at the next scheduler run. Change the option, click Save, then run; nothing changes until you do.
Flagging everything instead of a few steps. The flagged variant is meant for a handful of critical operations. Flag broadly and you have effectively chosen forward-shift for everything, just less obviously.
What to Do Next
Partial-confirm behavior is one of several policy decisions on the same screen. How to configure scheduling policy in EDGEBIC walks the full group, and how to count only primary hours in job totals in EDGEBIC covers a related roll-up choice. To manage how far the engine looks for capacity, see how to set the capacity search window in EDGEBIC, and the EDGEBIC product page shows where the policy screen sits in the platform.
Expert Q&A: Deep Dive
Q: An operator closed a job having logged fewer hours than planned, and now downstream steps have shifted later. Is that a bug?
A: No, that is the default partial-confirm behavior working. With Forward-shift the remaining hours selected, a short confirm re-plans the gap between planned and logged hours onto a future slot, and downstream steps queue behind it, so the unfinished work stays visible in the plan. If in your shop the operator's close-out is the real ground truth and the missing hours should simply be written off, open Settings and then Schedule, and in the Partial-Confirm Behavior group choose Trust the operator's Actual End. Save and run the scheduler. The completed operation itself never moves; only the treatment of the gap changes.
Q: We want to trust operators most of the time but stay strict on a couple of critical operations. Can we do both?
A: Yes, that is exactly what the third option is for. In the Partial-Confirm Behavior group choose Trust Actual End unless the step is flagged short. Then the operator's finish stamp is trusted everywhere except on the specific routing steps you flag for strict tracking, where a short confirm forward-shifts the missing hours instead. That lets you keep the light-touch, trust-the-operator model across the plant while enforcing tight tracking on the few operations where an unfinished gap must never disappear. Save the policy and run the scheduler; the flagged steps behave strictly and the rest trust the close-out.
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.