How to Anchor a Job to a Target Start Date in EDGEBIC

To anchor a job to a target start date in EDGEBIC, mark the constraint work center as a bottleneck, then use Set Anchor for Selected Jobs on the Workcenter Details tab to pin the bottleneck operation to a date. EDGEBIC by User Solutions then plans that operation at its target, schedules everything upstream backward to feed it, and schedules everything downstream forward from it. Both the bottleneck flag and the anchor date are required. Set only the flag and the job still schedules plain forward.

This is the anchoring procedure. For the theory, read EDGEBIC TOC anchor scheduling explained; for a worked run, see the TOC bottleneck anchor scheduling example. It is one of the task guides in the EDGEBIC how-to hub.

Before You Start

Step One: Mark the Work Center as a Bottleneck

1. Open the Work Center editor for the constraint resource, for example your heat-treat oven or a single busy mill.
2. Set Is Bottleneck to on.
3. Save.

This flag tells the engine which resource is the plant constraint. On its own it changes load analysis and buffer sizing, not the schedule. The next step is what actually activates anchor mode.

For the standalone version of this step, see how to flag a work center as a bottleneck.

Step Two: Set the Anchor Date

1. Open the Workcenter Details tab.
2. Select the job (or jobs) whose constraint operation you want to pin.
3. Use Set Anchor for Selected Jobs and enter the required date and time for the bottleneck operation to begin.
4. Save.

The next scheduling run detects the target start date and switches the whole job into anchor mode.

What Changes When You Run

Once a job carries an anchor date, the engine changes strategy for that job:

• The anchored operation is planned at its target date, packing the bottleneck as tightly as possible.
• Everything upstream is scheduled backward from the anchor, so material and prior operations arrive just in time to feed the constraint.
• Everything downstream is scheduled forward from the anchor's end.
• Buffers are inserted around the split: protective time in front of the anchor so upstream hiccups do not starve the bottleneck, and time after it so downstream hiccups do not eat the due date.

The anchor is the strongest instruction a job can carry. It wins over whole-order backward direction and everything else except recorded actuals. Because of that, setting a target start date on any operation of a job that was previously scheduled backward quietly converts it into an anchored job on the next run.

The reason this matters in practice is that the constraint sets the pace for the whole plant. A push scheduler fills each machine as fast as it can, which piles work in front of the bottleneck, inflates work-in-process, and leaves the constraint idle waiting for a steady feed. Anchoring inverts that: the constraint gets its capacity reserved at the target date with the highest priority, and every other operation is timed to keep it fed rather than to maximize its own throughput. That is the Theory of Constraints practice of subordinating everything to the one resource that governs output.

How to Check It Worked

1. Open the anchored job in Job View and confirm the bottleneck operation starts exactly at the target date you set.
2. Read the upstream operations. Their scheduled starts should be back-calculated so each finishes just in time to feed the constraint, which is why an upstream step can legitimately start earlier than the job's own start date.
3. Read the downstream operations. They should chain forward from the anchor's end, with any protective gap sitting between the constraint and the first downstream step.
4. Check Days Late. A well-anchored job should show a committed end date with margin, not an optimistic one.

Common Mistakes and Gotchas

• Setting the bottleneck flag but no anchor date. This is the number one reason a job schedules plain forward when you expected the anchor. Both conditions are required. Set the date on the Workcenter Details tab.
• Anchoring a work center that is not actually the tightest resource. The anchor still fires, but the protective buffers use small fixed values instead of demand-proportional ones. Confirm the anchored resource really is the constraint for that job at that quantity.
• Marking many work centers as bottlenecks. The Theory of Constraints protects exactly one constraint. Spreading the flag across the plant dilutes the whole point.
• Editing the routing after anchoring. If the bottleneck step is removed or its work center is changed after the anchor was set, the match fails and the job falls back to forward scheduling. Re-anchor after routing edits.
• Expecting the anchor on a completed step to hold. If the bottleneck operation is already finished, its actuals are preserved and the remaining steps schedule forward. You cannot backward-plan to work that has already happened.

To understand how the buffers are sized and how the anchor interacts with backward and forward direction, read TOC buffers and direction precedence in EDGEBIC, and to add the safety margin the anchor makes room for, how to protect a due date with a buffer.

Bring a routing with a real constraint and we will anchor a job against your data in one session. Contact US to book it, or read the EDGEBIC product overview first.