- Home
- Blog
- EDGEBIC How-To
- How to Name and Color a Work Center for the Gantt…
How to Name and Color a Work Center for the Gantt in EDGEBIC
To name and color a work center for the Gantt in EDGEBIC by User Solutions, set its WC ID and name on the configuration, then pick a Back Color for its bars, with optional Fore Color for text and Border Color for the outline. These are display settings: they make the schedule readable at a glance without touching how it is calculated.
A Gantt that all reads the same shade is a Gantt nobody reads. A few minutes assigning colors to machine families turns the board into something an operator can scan from across the shop. This page is the per-machine styling; for the schedule-wide color rules, read Gantt colors and labels in EDGEBIC.
Before You Start
- The work center already exists (how to add a work center).
- You have a naming convention. Function plus number, such as
CNC-Mill-1orWeld-1, keeps IDs readable and sortable. - You have a small palette in mind, ideally one hue per machine family so the board reads by type.
Step 1: Open the Work Center for Editing
Open the Workcenter tab. On the Work Center Management grid, click ✏️ Edit on the target work center's row. The Work Center Configuration dialog opens on the Basic Information tab.
Step 2: Set the ID and Name
Two identifiers sit at the top of the tab:
| Field | Purpose |
|---|---|
| WC Id | The stable identifier routings, schedules, and reports reference. Keep it short and consistent, and avoid changing it once the machine is in use |
| Name | The display label. Free to change; use it for a fuller description than the ID |
Both auto-generate by default. Edit them to your convention.
Step 3: Pick the Bar Colors
Set the colors used for this machine's bars on the Gantt:
| Field | What it colors |
|---|---|
| Back Color | The bar background, the main color operators see |
| Fore Color | The bar text; pick one that stays legible on the back color |
| Border Color | The bar outline |
The default back color is transparent, so a machine that has never been colored can show near-invisible bars. Pick a solid back color to fix that.
A practical scheme: assign one hue per machine family and vary the shade within it. Give the mills blues, the welders greens, the finishing cells ambers, and let each individual machine take a lighter or darker step of its family color. An operator then reads the board by type at a distance and by machine up close, without hunting for a legend. Keep the palette small and deliberate; a board where every machine is a different bright color is as hard to scan as one where they all match.
Step 4: Save
Click Save. The grid shows the color swatch beside the machine's ID, and its Gantt bars pick up the new colors on the next render.
What Changes When You Save
| Surface | Effect |
|---|---|
| Work Center grid | Shows the ID, name, and color swatch |
| Gantt bars for this machine | Render in the chosen back, fore, and border colors on the next view |
| The schedule itself | Unchanged; colors and names are display only |
Because these are display settings, existing bars recolor on the next Gantt render without a reschedule. Only a genuine capacity or routing change requires Drive Schedule. The color also shows as a swatch beside the machine's ID in the Work Center grid, so the palette you choose is visible on the setup screen as well as the schedule.
How to Check It Worked
- Confirm the color swatch and the ID and name on the machine's grid row.
- Open the Gantt and find a bar for this machine. It should show the chosen back color with legible text.
- Scan the board: machines in the same family should read as one color, and different families should stand apart.
Common Mistakes
Leaving the back color transparent. Default-transparent bars look invisible against the timeline. Always set a solid back color.
Fore color that vanishes on the back color. Dark text on a dark bar, or light on light, makes labels unreadable. Pick a fore color with real contrast against each back color.
Changing the WC ID after machines are in use. Routings, schedules, and reports reference the ID. Rename the display name for a clearer label; leave the ID stable, and if it must change, update the routings that point at it.
Using every color in the box. A palette with one hue per machine family reads better than a rainbow. Deliberate beats colorful.
Next
Names and colors are the cheapest readability win in EDGEBIC: a stable ID, a clear name, and one hue per machine family make the Gantt scannable without changing a single scheduled hour. For what the bars can say beyond color, see how to change what a Gantt bar label shows. More single-task recipes are in the EDGEBIC how-to hub, and the platform overview is at /edgebic.
Expert Q&A: Deep Dive
Q: Our Gantt is a wall of bars in the same shade and operators cannot tell the mills from the welders. What is the fastest fix?
A: Give each work center a distinct back color on its configuration. Pick a small, deliberate palette, one hue per machine family, so mills read one color and welders another across the whole board. Set a fore color that stays legible on each back color, so bar text does not disappear. This is per-machine display styling and does not touch the schedule, so you can recolor the whole shop in a few minutes and the next Gantt render shows it.
Q: We renamed a work center and now some reports look inconsistent. Did we break something?
A: Renaming the display name is safe, but changing the WC ID is the risky one, because routings, schedules, and reports all reference the ID. If you edited the ID rather than the name, existing references still point at the old identifier and things read inconsistently. Keep the ID stable once a machine is in use, and change the display name instead when you want a clearer label. If the ID must change, plan to update the routings that reference it.
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.
