An imported work center schedules only when it has three things: at least one instance, at least one shift, and an active flag. An import that mapped the name but skipped any of the three leaves the machine present but unable to offer a single working window. EDGEBIC by User Solutions names exactly which one is missing through its pre-flight check and anomaly report, so the repair is targeted.
This post is part of the EDGEBIC troubleshooting guide. It covers the three requirements, how the tools tell them apart, and how to fix the import so it does not happen again.
The Three Things a Machine Needs
A machine cannot produce capacity from a name alone. Scheduling requires all three of these, and an import that leaves any one blank produces a machine that looks configured but offers nothing.
| Requirement | What happens when it is missing |
|---|---|
| At least one instance | The engine has no physical slot to allocate, so capacity checks always fail |
| At least one shift | The engine finds no working windows and never places a job near term |
| Active flag on | The machine is treated as switched off and skipped entirely |
Imports commonly miss the instance count and the shift assignment, because those often live in a source column that was blank, unmapped, or stored differently in the old system.
How the Tools Tell Them Apart
You do not have to guess which requirement is missing. EDGEBIC checks this in two places.
Before scheduling, the pre-flight validator checks that every machine on a routing has at least one instance and at least one shift. A machine with no instances fails pre-flight with a no-instances message. A machine with no shifts fails with a no-shifts message. Fixing pre-flight failures first means you do not burn a full scheduling run on a machine that was never going to place a job.
After scheduling, the anomaly report's configuration-gap check fires when a machine carries schedules but currently resolves no shift, whether because it never had them or because they were later removed. Its detail names the machine and confirms that neither the plant-wide shifts are on nor its own shift rows exist.
Read which one the tool names, because instances and shifts are separate causes with separate fixes.
The Fixes
No shifts. Turn on the plant-wide shifts for the machine so it inherits the global working calendar, or add its own shift rows if it needs a different calendar than the plant. The work center setup guide covers both paths, and giving one machine its own calendar covers the second.
No instances. Set the instance count to the number of physical units the machine represents. One machine is one instance; a bank of four identical units is four.
Inactive. Set the active flag on. An inactive machine is intentionally skipped, so this is only a fix if the machine should have been active.
After any of these, re-run scheduling. A machine that was pushing its jobs far into the future for lack of windows will start placing them near term.
Fix the Import, Not Just the Machine
Repairing each imported machine by hand solves today's problem and guarantees tomorrow's. An import mask maps spreadsheet or database columns to work center fields, and the instance count, the plant-wide shifts flag, and the active flag can all be mapped from the source. Mapping them once means every future import arrives schedulable. EDGEBIC's flexible import and export approach is built around this: the mask is where you encode the mapping so imports are repeatable rather than one-off. The troubleshooting guide links the neighboring capacity symptoms.
An imported machine schedules only when it has at least one instance, at least one shift, and an active flag. An import that mapped the name and description but not the instance count, the shift assignment, or the active status leaves the machine present but unable to offer any working window. The pre-flight validator and the anomaly report both name exactly which of the three is missing.
Run the pre-flight check before scheduling, or the anomaly report after. A machine with no shifts shows a configuration-gap finding that names it and reports it has neither the plant-wide shifts turned on nor its own shift rows. A machine with no instances fails pre-flight with a no-instances message. The two are separate causes with separate fixes, so read which one the tool names before changing anything.
Turn on the plant-wide shifts for the machine, which lets it inherit the global working calendar without entering its own rows. If the machine needs a different calendar than the plant, add its own shift rows instead. Either way the machine gains working windows on the next scheduling run. An import mask can set the plant-wide shifts flag directly so future imports arrive schedulable.
Yes. An import mask maps spreadsheet or database columns to work center fields, so the instance count, the plant-wide shifts flag, and the active flag can all be mapped from the source data. Mapping them once means every future import arrives ready to schedule rather than needing manual repair afterward. That is the durable fix versus patching each imported machine by hand.
Expert Q&A: Deep Dive
Q: I imported 40 machines from our old system and jobs on a dozen of them fail with a no-capacity error. The other 28 schedule fine. What did the import miss?
A: Compare a failing machine to a working one on three fields: instance count, the plant-wide shifts flag or its own shift rows, and the active flag. The 12 that fail almost certainly have a zero instance count or no shift assignment, because those are the two fields an import commonly skips when the source column was blank or unmapped. Run the pre-flight check to confirm which field each machine is missing, fix them, and update the import mask to map those columns so the next import does not repeat it.
Q: The anomaly report says an imported machine has schedules but no shifts. How can it have schedules if it has no shifts?
A: The schedules were created when the machine had shifts, or were carried in from the source data, and the shifts were later removed or never imported. The configuration-gap check fires whenever a machine carries schedules but currently resolves no shift, so it catches both a machine that lost its shifts and one that arrived without them. Turn on the plant-wide shifts or add the machine's own shift rows, then re-run scheduling to regenerate a valid plan against real working windows.
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
An Operation Moved and the Machine Was Free: Finding the Hidden Cause
A job slid and every machine shows open hours. Tooling is the cause the Gantt cannot draw. How to rule it in or out in two minutes before you chase calendars.
An Operation Shows Running Forever Though All Hours Are Logged
A step stays in progress after every hour is logged because completion is an explicit stamp, not an hours threshold. How to close it and stop it recurring.
Another User Changed This Record: Causes and Fixes
EDGEBIC refuses a save when the record moved after you loaded it. The usual cause is a colleague, but the message also appears when you are alone. How to read it and what to do.