Making the Gantt Speak: Colors, Labels, and Layouts in EDGEBIC

A production Gantt earns its wall space when a supervisor can read plant status from across the room, and that comes down to three configurable layers in EDGEBIC by User Solutions: what each bar color means (operation states), what each bar says (caption tokens), and how each screen is arranged (layouts that save themselves). Color coding is not decoration. It is the difference between a chart people glance at and a chart people interrogate.

This post covers all three layers: the state vocabulary and its priority rules, the token engine behind bar captions including the hour roll-ups, and the layout persistence that keeps every planner's screen their own. For how the states connect to plan-versus-reality reading, pair this with reading the Gantt planned versus actual.

Layer 1: Colors Are States, and States Are Vocabulary

Every bar on the EDGEBIC Schedule View Gantt carries an operation state. The color is just the paint; the state is the meaning:

Three rules govern how the states interact, and they are worth teaching to everyone who reads the chart:

Priority is deliberate. When more than one state could apply, the higher-priority one wins, and ERP Actuals sits at the top: externally fed actual dates outrank every local state, including a work center replacement. If a bar seems stuck in the ERP color, the fix is in the feed (which arrives through the same import-export masks as other ERP data), not on the Gantt.

Completed is a shade, not a state. Completion paints an opaque fill over the whole bar while the caption and borders still render. It deliberately overrides every state color, because "this is finished" is the one message that should never be ambiguous. The shade applies when the whole job is complete or when that individual operation is complete, and completing or reopening a job repaints an open Gantt live.

Overridden never persists. The pending-change color exists only in memory on your screen; it is never stored. Save and it transitions to Applied, Resource Replaced, Actual Start Applied, or Planned Applied depending on what you did; discard and it reverts. The full drag mechanics are in the drag-and-drop rescheduling guide.

Every color is configurable per state in the scheduler configuration, and each state can be switched off entirely. The legend strip at the top of the Gantt is generated from the same configuration, so the chart and its legend cannot disagree. Practical advice: run the defaults for a few weeks before customizing, then encode your house language (many shops brighten Downstream Changed, since it is the "someone must look at this" flag).

Layer 2: Captions Are a Token Language

The text on each bar is composed from a configurable caption pattern per work center. By default it identifies the job and the operation, which answers "what is this bar?" But the token engine goes much further, with twelve schedule-sourced fields available:

That is where captions become a reporting surface. A milling lane whose bars each read "JOB-2026-0101 · Mill · 6.0 of 16.5 h · 36%" answers the morning meeting's first three questions without anyone opening a report. And because the pattern is per work center, different lanes can speak to different audiences: remaining hours where the bottleneck lives, percent complete where assembly tracks progress toward ship dates. Identifying the constraint lane and instrumenting it hardest is the same thinking as production bottleneck identification generally.

Configuration is a checklist, not code: open the scheduler configuration, tick the fields you want in the data-source list, or edit the per-work-center pattern directly. Restraint wins; three or four tokens per bar is the practical ceiling before captions crowd each other at normal zoom.

One more caption surface worth knowing: the routing Designer's nodes have their own separate display-field pattern for showing live planned and actual figures under a node title in a scheduled job's diagram. Same token idea, deliberately independent pattern per surface, so the Designer canvas and the Gantt each stay tuned to their own job.

Layer 3: Layouts That Save Themselves

The third layer is the arrangement of the screens around the chart, and its distinguishing feature is that there is nothing to remember to do. Every user-configurable grid and tree in EDGEBIC (the job trees, the per-work-center grids, the report panes, dozens of surfaces) automatically remembers column widths, order, visibility, pinning, sorting, grouping, and filters, per user. Layouts restore when you open the screen and save when you navigate away or close the window. There is no Save Layout button because there is no save step.

Two details make this production-grade rather than merely convenient. First, updates reconcile: when a new version ships a new column, it appears in your saved layout instead of hiding itself behind your old arrangement. Second, persistence is per user, so the planner who lives in hour columns and the supervisor who lives in dates each keep their own screen without negotiating.

Focus Tools: Making One Thing Loud

Color coding fails when everything is loud. EDGEBIC ships several ways to quiet the chart around what matters right now:

• Job filter. The left panel's checkboxes control which jobs render; on first open every job is checked, and your selection is remembered while you work. Unchecking down to one job is the fastest "show me just this" there is.
• Shade other jobs. Right-click a bar and shade or un-shade every other job's operations, dimming the rest of the plant so one job stands out without changing the filter.
• The lead-time tail. The slate display-only bar after a job's last operation is intentionally styled unlike any operation state, so promised-date information never masquerades as schedulable work.
• Parallel markers. Bars carrying the parallel symbol identify lockstep machines whose siblings move together, so a multi-machine operation reads as one unit.
• Timeline commands. Today jumps the view to now; Timescale Zoom In and Out change the grain; Horizon End Later and Horizon Start Earlier grow or shrink the visible range a month at a time.

A Configuration Worth Copying

If you want a starting recipe, this one holds up in practice:

1. Keep default state colors for two weeks; teach the vocabulary before repainting it.
2. Put Remaining Hours in the caption on your constraint work center's lane only.
3. Add % Complete to final-operation lanes feeding shipping.
4. Brighten Downstream Changed; it is your review queue.
5. Leave Completed at a strong neutral; it should read as "done" from distance.
6. Let each planner arrange their own grids; the layouts will follow them.

Then watch the morning meeting change. When the chart answers "what state is this job in, who moved what, and how many hours remain," the meeting stops reconstructing status and starts making decisions, which is the entire promise of visual production scheduling. The two pieces carrying most of that reading load, the status strip on each bar and the legend generated from your own configuration, are covered in the status strip and the legend on the EDGEBIC Gantt.

The Chart Is a Language; Teach It Once

Color coding, captions, and layouts are how a schedule stops being a database and starts being a shared language on the floor. User Solutions has been refining that language with manufacturers since 1991, from ten-person shops to the US Navy, GE, BAE Systems, and Cummins, and the lesson repeats: the plants that improve are the ones where everyone reads the same picture the same way.

See the full EDGEBIC platform, start with the visual scheduling pillar guide, or bring your current wall chart to a demo and let US show you what it looks like speaking in states and tokens.