How to Set a One-Job-Per-Day Work Center in EDGEBIC

To set a one-job-per-day work center in EDGEBIC by User Solutions, turn on the One Per Day Flag on the Work Centers screen and set the machine's Number Of Instances to the number of physical chambers. The control lives on the work center record itself, not on the routing. Once saved and rescheduled, each instance runs at most one job per calendar day. A three-chamber heat-treat furnace can hold three different jobs at once, but a fourth job for the same day waits for the next day. This is exactly how batch equipment behaves on the floor, and the flag makes the schedule respect it.

This recipe is one specific task. To understand how EDGEBIC decides which instance a job lands on, read how EDGEBIC picks an instance: load balancing versus one per day.

Before You Start

• The Work Centers screen open, with the machine you want to constrain selected.
• The real count of physical chambers, cells, or units on that machine.
• A clear reason for the constraint: batch equipment where one load per unit per day is the physical limit, or a process that needs a dedicated setup for the whole day.

Step by Step

1. Open the Work Centers screen and select the machine.
2. Turn on the One Per Day Flag.
3. Set Number Of Instances to the number of physical chambers or cells (for example, 3 for a three-chamber furnace).
4. Save the work center.
5. Run Generate Schedule (Full Reschedule applies the constraint to existing plans).

What Changes When You Save

On the next run, EDGEBIC schedules this machine instance by instance instead of pooling its capacity. When it places a job, it looks for a chamber that has no other job on that date and assigns the first free one. It then keeps that job on the same chamber across every shift the job spans, so the job does not hop between chambers mid-run. A chamber already holding a different job that day is skipped. The result is at most one job per chamber per day, with as many simultaneous jobs as you have chambers.

Jobs that would have overflowed onto a busy chamber slide to the next day instead, which lengthens lead times when demand exceeds daily chamber count. That is the honest picture of a constrained resource.

How to Check It Worked

Run the diagnostic snapshot for the plant, or filter it to a specific job. In the resources section, group the allocations by work center and date. Each instance should appear with at most one distinct job per date. If any instance shows two jobs on the same date, the flag is not being honored. Confirm the flag is actually saved to the database rather than only set in the form, correct the instance count, and reschedule.

Common Mistakes

• The flag is set in the form but not saved. A one-per-day setting that never reached the database lets two jobs share a chamber. After saving, verify by rescheduling and reading the diagnostic snapshot, not by trusting the form.
• The instance count does not match the physical machine. If the count is higher than the real number of chambers, EDGEBIC will happily schedule more jobs than the machine can hold. Set the count to the true physical number.
• Expecting parallelism from a single instance. One instance with the flag on dedicates the machine to one job per day and produces no parallel work. If you need several jobs at once, you need several instances.
• Reassignment when a chamber goes down mid-run. If a job spans days and its assigned chamber later gets a downtime event, EDGEBIC may not move it automatically. Add the downtime event and reschedule so the job re-homes to a free chamber.

Where to Go Next

One-per-day is one of several ways to shape a work center's behavior. If you are weighing a dedicated chamber against a pool of interchangeable machines, read how to add a machine to a pool. For the full platform, see EDGEBIC, or browse the EDGEBIC How-To Library.