To rename a work center in EDGEBIC by User Solutions, open the Work Centers tab, select the machine, click Edit, change the Name, and click Update, then update the routing steps that reference it. The rename itself is one field. The part that catches people is the second half: routing steps store the work center name as text, and the scheduler matches on that text, so a rename without a routing update leaves steps with no machine.
This is the most common cause of a step that schedules with no resources, and it is entirely avoidable if you treat the rename as a two-part job from the start.
Before You Start
- You know which routings use the machine. Note the products that route through it before you rename, so you know exactly what to fix.
- You can edit routings and rerun the scheduler.
- You understand the rename is two steps: the machine, then every routing that names it.
Step 1: Rename the Work Center
Open the Work Centers tab, select the machine, and click Edit. Change the Name field, then click Update.
The machine is now renamed everywhere it is referenced by its stable identifier. That covers most of the system, but not the routing name text, which is the next step.
Step 2: Update the Routing Steps
Open the Bill of Routing for each product that routes through the machine, in the Grid View. Each step that uses the machine carries the work center name as text. Change that text to the new name.
This is the load-bearing step. The scheduler matches a routing step to a machine by this name, so a stale name means the step finds no machine and schedules with no resources.
Step 3: Save Each Routing
Click Save Steps on each routing you edited. Work through the full list of products that route through the machine before moving on.
Step 4: Reschedule and Confirm
Run Schedule / Re-Schedule, then confirm the renamed machine still receives its work. A step that came back with no resources is the signal that a routing name was missed.
What Changes When You Save
| Surface | Effect |
|---|---|
| The work center | Renamed everywhere it is referenced by identifier |
| Routing step name text | Must be updated by hand to match |
| Scheduler name match | Fails on any step still carrying the old name |
| Gantt display color | Unchanged; color is a separate setting |
How to Check It Worked
- Confirm the Work Centers grid shows the new name.
- Open a routing that used the machine and confirm the step now shows the new name.
- Run the scheduler and confirm the machine receives work. Look specifically for any operation that scheduled with no resources, which points at a routing you missed.
- Check a dispatch list or the utilization report for the machine to confirm its jobs are intact under the new name.
Common Mistakes
Renaming the machine but not the routings. The single most common consequence. Steps that still name the old machine schedule with no resources. Update every routing that references it.
Assuming one save covers everything. The rename is two parts: the machine, then each routing. There is no single button that rewrites the routing name text for you.
Expecting the color to follow the name. The Gantt color is a separate setting. Rename changes the name only; edit the color swatch if you want that different too.
Next
Renaming a work center is a two-part job: the machine, then every routing that names it, and skipping the second half is what strands a step with no resources. To review the machine's jobs before and after, use the work center utilization report. To retire a machine instead of renaming it, read how to deactivate a work center, and to change its Gantt color, how to name and color a work center for the Gantt. More single-task recipes are in the EDGEBIC how-to hub, and the platform overview is at /edgebic.
Expert Q&A: Deep Dive
Q: I renamed Mill-1 to CNC-Mill-A and now some jobs show a step with no machine assigned. What happened?
A: The routing steps that route through that mill still carry the old name, Mill-1, as text, and the scheduler matches a step to a machine by that name. Since no machine is called Mill-1 anymore, those steps find nothing and schedule with no resources. Open each routing that uses the mill, change the step's work center name to CNC-Mill-A, save the routing, and rerun the schedule. This is the single most common consequence of a rename, and it is why the rename is a two-part job, not one.
Q: How do I find every routing that uses a machine before I rename it?
A: Before you rename, note which products route through the machine so you know exactly which routings to fix afterward. A dispatch list or utilization report for that work center will show the jobs currently on it, which points you at the products whose routings reference it. Do the rename, then walk that list, updating the work center name on each routing step and saving. Finish with a schedule run and confirm the machine still receives work rather than leaving steps stranded.
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.