What Is a Target Level in Scheduling? EDGEBIC Definition

A target level records at which level a target date was set: on the whole job, on one specific operation, or nowhere at all. In EDGEBIC by User Solutions, a target date is a statement of intended timing, and it can be attached either to a manufacturing order as a whole or to a single scheduled operation. The target level carries which of those happened, and it drives how the bar renders on the Gantt.

The everyday version: a note on the whole project saying we want this done in March, versus a note on one task saying the inspector arrives on the ninth so that step happens then. Both are targets. They are not the same instruction, and you would not want to confuse them when reading the plan.

For the broader vocabulary of planning, see the manufacturing glossary.

How a Target Level Works

Three values exist.

None means no target date is set. This is the normal state for the great majority of operations, which simply schedule wherever the sequence and the available capacity put them.

Job means the target was set at the manufacturing order level. The whole production schedule for that job carries the intent, so the target is a statement about the order rather than about any single step in it.

Work Center means the target was set on one specific scheduled operation. The intent is local: this step, at this time. Other steps arrange themselves around it rather than around a job-wide date.

The distinction is easy to overlook and important to keep. A job-level target says the order is expected to land around a certain time. An operation-level target says one particular step is pinned and the rest of the routing accommodates it. Those produce different plans, and a planner reading a Gantt without knowing which is in play cannot explain why a bar sits where it does.

The reason the value is recorded rather than inferred is that both cases end up looking similar on the board once scheduling has run. An operation may appear anchored either because someone pinned that step or because the job as a whole carries a date and this happens to be the step where that shows most clearly. The target level says which.

That is also why it feeds the coloring on the Gantt. A targeted operation should look different from an ordinary one, and a step someone deliberately pinned should be distinguishable from one carrying a job-wide expectation.

A Concrete Example

Job 42 runs saw, mill, heat treat, assemble, inspect. Heat treatment is the plant's constraint, flagged as the bottleneck, and it is booked solid for weeks.

Case one: a customer requires delivery in the third week of the month, and the planner sets a target on the manufacturing order. That target's level is Job. It expresses an expectation about the whole order, and the engine plans the routing to meet it. On the Gantt, the job carries a target and the bars reflect it.

Case two: the heat treat oven has one free window on the eleventh, and that window is the only realistic slot this month. The planner targets the heat treat operation itself to that date. That target's level is Work Center. It anchors one step, and everything else in the routing arranges around it: the saw and mill work is planned backward so the parts arrive in time, and assembly and inspection are planned forward from when the oven releases them.

Both jobs now show a target on the board. Without the target level, the two look interchangeable and a planner cannot tell whether the eleventh came from a customer requirement on the order or from a deliberate decision about the oven. With it, the distinction is visible at a glance, and the reason the plan looks the way it does is recoverable months later.

How EDGEBIC Uses It

The target level is carried on the scheduled operation:

• It distinguishes job-wide intent from step-level intent, so an order-level target date reads differently from a target placed on one operation.
• It drives the Gantt color coding, which is how a targeted operation is made visually distinct from an ordinary scheduled one.
• It pairs with constraint anchoring, since a work center flagged as the bottleneck is the usual reason a planner pins one specific operation rather than the whole job.

For the constrained step a target usually pins, see what is an anchor step in scheduling. For the durable planner pin that expresses forward intent without a target, see what is a planned start pin in scheduling. To set one, follow how to anchor a job to a target start date.