EDGEBIC How-To

How to Schedule Around a Planned Shutdown Week in EDGEBIC

User Solutions TeamUser Solutions Team
|
7 min read

To schedule around a planned shutdown week in EDGEBIC, add a whole-day plant holiday for each closed day of the week, mark them recurring if the shutdown repeats annually, then reschedule the affected jobs. EDGEBIC by User Solutions removes those dates from every work center's capacity, so a rescheduled job flows its work before and after the closure. A holiday record covers one date, so a five-day shutdown is five records.

This is the shutdown procedure. For a single closure, see how to add a plant holiday in EDGEBIC; for the calendar mechanics, read EDGEBIC shifts and calendars explained. It is one of the task guides in the EDGEBIC how-to hub.

Before You Start

PrerequisiteWhy it matters
You know the exact shutdown datesEach closed working day becomes its own whole-day holiday.
You know which jobs overlap the weekThose are the jobs you reschedule so their work flows around the closure.
You know whether the shutdown recursAn annual shutdown is entered once with Recurring each year.

Step One: Add a Whole-Day Holiday Per Closed Day

  1. Open the Daily Hours tab, then the inner Holiday tab. The Plant Holidays page opens.
  2. Click Add Holiday.
  3. Enter a Name, for example "Summer Shutdown Mon", and the Date for the first closed day.
  4. Leave Closes the whole day checked so the entire day is blocked for every work center and shift.
  5. If the shutdown repeats every year, tick Recurring each year. Recurring holidays match on month and day, so only those matter.
  6. Confirm Active is checked, then Save. The grid shows Scope as Whole Day.
  7. Repeat for each remaining working day of the shutdown week. Weekends the plant already does not work need no holiday.

Step Two: Reschedule the Affected Jobs

Saving holidays changes the calendar but moves nothing on its own.

  1. On the Drive Schedule tab, tick the jobs whose work overlaps or runs near the shutdown week.
  2. Press Schedule + Re-Schedule.
  3. Confirm the dialog and let the pass complete.

The engine now treats the shutdown days as unavailable and replans the affected jobs so their operations land before or after the closed week.

What Changes When You Save

SurfaceEffect
Plant Holidays gridEach closed day appears immediately as Whole Day.
Work center capacity on those datesRemoved entirely for every work center on the global calendar.
Existing schedulesUnchanged until you reschedule, even if they now sit inside the closed week.
Rescheduled jobsFlow their work before and after the shutdown, skipping the closed days.
Completed workNever moved by the reschedule.

How to Check It Worked

  1. On the Plant Holidays grid, confirm each shutdown day is listed with Scope as Whole Day and, for an annual shutdown, Recurring ticked.
  2. Open an affected job in Job View and confirm no operation lands on any shutdown day.
  3. Confirm the job's finish moved out by the length of the closure, which is expected.
  4. Spot-check a work center's capacity view for the shutdown week and confirm it shows zero available hours.

A Worked Shutdown

The plant closes the first full week of August for annual maintenance, Monday through Friday. The plant already does not run weekends, so those two days need nothing.

On the Plant Holidays page you add five whole-day holidays, one per working day: Monday through Friday of that week, each with Closes the whole day checked and Recurring each year ticked because the shutdown repeats every summer. The grid now lists five rows, each with Scope reading Whole Day and Recurring marked.

Then you tick the jobs whose work runs anywhere near that week and press Schedule + Re-Schedule. A job that would have milled Tuesday now finds no capacity there, so the engine flows that work to the Friday before or the Monday after, and its finish moves out by the length of the closure. A job that could finish entirely before the shutdown is untouched by the closure, because its operations never needed those days.

Because the holidays are recurring, next August the closure is already in the calendar. You do not re-enter anything; you simply reschedule as the dates approach and the plant closure is honored automatically. Confirm the result by scanning a work center's capacity view for the shutdown week, where every day should read zero available hours.

Common Mistakes and Gotchas

  • Expecting one record to cover the week. A holiday covers a single date. Enter one whole-day holiday per closed working day.
  • Saving holidays but not rescheduling. The plan computed against the old calendar still stands. Reschedule the affected jobs after adding the holidays.
  • A work center on a custom calendar. Global plant holidays cover work centers on the global calendar. A machine with its own calendar follows its own rules; handle it with a per-day capacity override or its own closures.
  • Forgetting Recurring for an annual shutdown. Without it, you re-enter the holidays every year and risk a gap. Tick Recurring each year so the closure repeats automatically.
  • Leaving a holiday Inactive. An unticked Active box keeps the record but the scheduler ignores it, so the plant does not actually close.

For a single machine's closure rather than a plant-wide one, see how to block a machine for a maintenance day, and for a reduced-hours day, how to schedule a half-day holiday. After adding the closure, how to reschedule only the jobs that changed keeps the plant-wide replan tight.

Bring your shutdown dates and job list and we will plan around them against your data in one session. Contact US to book it, or read the EDGEBIC product overview first.

Add a whole-day plant holiday for each working day of the shutdown week on the Plant Holidays page. A holiday record covers one date, so a five-day shutdown is five records, each with Closes the whole day checked. For an annual shutdown, tick Recurring each year so the closure repeats on the same dates every year. Then reschedule the affected jobs so their work flows around the closed week.

A plant holiday record covers a single date, so a shutdown week is entered as one whole-day holiday per closed day. Weekends the plant already does not work need no holiday. Each record shows Scope as Whole Day in the grid. This keeps the closure explicit and auditable, one named day at a time.

No. Holidays only define the capacity the scheduler may use. Existing schedules stay exactly as they are, even if they now sit inside the closed week, until you run Drive Schedule again. Add the holidays, then reschedule the affected jobs so the engine replans them around the closure. Completed work is never moved by that reschedule.

Expert Q&A: Deep Dive

Q: We shut the whole plant the first week of August for maintenance. How do I make the scheduler avoid it every year?

A: On the Plant Holidays page, add a whole-day holiday for each working day of that week, tick Closes the whole day, and tick Recurring each year on each one. Recurring holidays match on month and day, so the closure repeats automatically. Then reschedule the affected jobs. The engine skips those dates entirely and flows their work before and after the shutdown, and you never re-enter it next year.

Q: I added the shutdown holidays but the Gantt still shows jobs running that week. What did I miss?

A: Saving a holiday never reschedules anything, so the plan computed against the old calendar still stands. Tick the jobs that overlap the shutdown week and press Schedule + Re-Schedule. If jobs still land in the week, confirm each day's holiday has Closes the whole day checked and Active on, and that the affected work centers follow the global calendar rather than a custom one.

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

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.

Let's Solve Your Challenges Together