Reading Operation Description Fields on a Gantt Bar

Every caption on an EDGEBIC Gantt bar is assembled from tokens, so the text is a little language you can configure. A token pulls one field from the schedule, the job number, the product, a planned date, an actual date, hours, and the operation description pattern composes those tokens into the bar's caption. Change the pattern and you change what every bar on that machine tells you. EDGEBIC by User Solutions builds bar captions this way so the chart shows the information your shop actually reads, not a fixed label you are stuck with.

This post explains what the fields are, how to read them, and how to set them per work center so each lane carries the right detail. It sits under the visual scheduling guide and complements Gantt colors and labels in EDGEBIC, which covers the color states; here the focus is the text.

The Caption Is Composed, Not Fixed

The words on a bar are not a hard-coded label. They are the output of a pattern made of tokens, where each token resolves to one field of the operation's schedule record. By default the pattern identifies the job and the operation, which is enough to tell the bars apart. But the pattern is yours to change, and the fields available go well beyond identity.

The same token engine renders the caption on the scheduler Gantt and the details line under a node in the routing designer, so the two surfaces speak the same language. Learn the tokens once and they read consistently wherever schedule text appears.

The Fields You Can Show

The tokens fall into a few groups. Identity tokens name the work: the job number, the product. Date tokens place it in time: planned start and end, and the actual dates once they exist. Then there are the tokens that carry the most operational value, the hour and progress fields sourced from the schedule table.

The hour and total tokens ship switched off, so a fresh install keeps captions simple. You turn them on where they earn their place. A bar that shows remaining hours and percent complete stops being just a rectangle in a time slot and becomes a status line: this operation, this much left, this far along. That is the difference between reading a bar's position and reading its work content, which matters because a bar's length is elapsed time, not hours, as covered in how the Gantt shows a job spanning shifts.

Patterns Are Per Work Center

Captions are set per work center, and that is a feature, not a limitation. Different machines want different information on their bars.

A constraint machine benefits from remaining hours and percent complete, because those bars are the ones a planner watches most closely. A simple, fast machine may only need the job number, because extra detail just clutters a lane where nothing ever goes wrong. Setting the pattern per work center lets each lane carry what matters for that machine.

When you do want consistency, there is an apply-to-all option so you can push one pattern to every work center at once. And on the routing designer's Scheduled Job BOR view, individual work-center nodes have their own separate pattern for the details line under the node, edited inline, so the diagram and the Gantt can show different fields when that suits the job. The point throughout is that the caption is a decision, made where it is most useful, not a fixed format imposed on the whole plant.

Reading Hours Without Being Fooled by Length

The most valuable thing the caption fields do is separate work from time. On a Gantt, the eye wants to read a long bar as a lot of work, but length is elapsed calendar time. A bar stretched over a weekend can hold the same hours as a short bar inside one shift.

The hour tokens fix that. Turn on planned hours and the bar states its work content in the caption, independent of how far it stretches. Turn on actual and remaining hours and it states progress. Now you read a spanning bar correctly: the width is when, the caption is how much. This is the everyday reason to enable the hour tokens on the machines you care about, and it connects directly to what planned vs actual hours means.

One practical note on the actual-hours tokens. The detail behind them, the daily hour breakdown, is not loaded by the standard schedule query, so EDGEBIC fetches it with a targeted backfill only when a pattern actually uses an hour token. That keeps the chart fast when the tokens are off. If you add an actual-hours token and a bar reads zero, refresh so the backfill completes; if it still reads zero, no hours have been logged against that operation yet, and the token is correctly showing nothing.

A Worked Example: Turning Bars Into Work Orders

Acme Industries runs three machines its supervisors dispatch from directly: the mill, the lathe, and the paint booth. The supervisors want the bars on those machines to read like work order lines.

The planner opens the scheduler configuration and, for each of the three work centers, sets the operation description pattern to combine the job number, the product, and the remaining-hours token, then adds percent complete for progress. On the mill lane, a bar now reads as the job, the part, the hours left, and how far along it is. A supervisor glancing at the lane can dispatch and check status from the captions alone.

The other machines in the plant stay on the default caption, because they run simple, short operations where the extra detail would only crowd the lane. Because patterns are per work center, the three dispatch machines get the rich captions and the rest stay clean. Later, when the plant standardizes, the planner uses apply-to-all to push one agreed pattern everywhere at once.

The result is that the same Gantt serves two audiences: a planner reading colors and positions across the whole plant, and supervisors reading work-order captions on the three machines they run. Nothing about the schedule changed. Only what the bars say changed, and it changed exactly where it helped.

Teach the Caption Once

A Gantt is only as useful as it is readable, and readability is a choice. User Solutions has built scheduling tools for manufacturers since 1991, for shops and for names like Cummins and the US Navy, and the token-based caption is one of the ways the chart adapts to a shop instead of forcing the shop to adapt to it. Decide what each machine's bars should say, set the pattern, and every bar on that lane speaks the same clear language from then on.

Pick the fields that matter, set them per machine, and let the captions do the talking. Bring your work-order format to a demo and we will build it into the bars. Give US a chance to make the chart read the way your floor already thinks.