How to Import Plant Holidays from a File in EDGEBIC

Importing plant holidays into EDGEBIC by User Solutions uses the PlantHoliday entity on the Import tab: map the holiday name and date columns, run the mask, and a whole year of closed days loads at once. It is the shortcut past adding statutory holidays and shutdown weeks one at a time, and re-running the same file never creates duplicates. Here is the task end to end.

For the shared import mechanics, see how to import work centers from Excel. To add a single holiday by hand instead, see how to add a plant holiday. Every task in this library is mapped on the EDGEBIC how-to hub.

Before You Start

• Your file lists one holiday per row, with a name and a date in every row. Both are mandatory.
• You know which closures are full days and which are partial. Partial-day closures need start and end times.
• You can reach the Settings tab, since Import lives there and is permission-controlled.

Step 1: Open Import and Pick PlantHoliday

Open the Settings tab, click the Import tab, and select PlantHoliday in the Entity Type list. This is the plant-wide calendar, distinct from a single work center's own holidays, which are configured on the work center.

Step 2: Build the Mask

Click Define New, name the mask something like Annual Holidays, click Get File, and pick your spreadsheet. For Excel, choose the Sheet. EDGEBIC reads the headings into File Header Titles for mapping.

Step 3: Map Name and Date, Plus Any Options You Need

Drag the holiday-name heading onto the Holiday name row and the date heading onto the Date row. Both carry the Req tick, so both must be mapped before the mask can run.

Then map the optional columns you have:

For a normal full day off, a name and a date are enough. For a half-day, leave the whole-day flag off and fill the start and end times.

Click Save.

Step 4: Run It

Select the mask and click Do It, pointing at the file if prompted. The Import Result dialog reports Created ... Updated ... Reused ... Failed .... A row that fails, usually because a date cell is blank or unreadable, is marked Failed while the rest of the run continues.

Step 5: Re-run Safely When the List Changes

Holidays are matched by name and date, so re-importing next year's revised file finds the entries that already exist and reuses them, adding only the new ones. If you need to change details on existing holidays, tick UpdateExistingRecords in the mask Options first; without it, matches are simply reused.

What Changes When You Import

The imported dates appear immediately on the plant calendar. The schedule itself does not move: an import changes calendar data, not the plan. Run the scheduler afterward so future work flows around the newly closed days. One log file is written per run and opened from the result dialog.

How to Check It Worked

Open the plant holiday calendar and confirm the imported dates are present, with the right descriptions and any partial-day windows. Then run Drive Schedule and spot-check a job that spanned a closed day: its operations should step over the holiday. For a definitive check, run the Scheduler Anomalies report plant-wide, where an operation booked on a plant-wide holiday surfaces as its own off-calendar check, covered in how to run the scheduler anomalies report.

Common Mistakes

• A blank or ambiguous date. Date is a key. A blank or a format the reader cannot parse fails the row.
• Expecting a half-day off from a whole-day flag. For a partial closure, leave whole-day off and supply the start and end times.
• Not re-running the scheduler. Holidays loaded but jobs still on those days almost always means the plan has not been rebuilt since the import.
• Confusing plant and work center holidays. PlantHoliday is site-wide. A single machine's downtime belongs on that work center.

Next Steps

• Load your shift patterns the same way with how to import shifts from a file.
• Control each mask's re-run behavior with how to set import options for a mask.
• See how the calendar shapes the plan on the EDGEBIC product page.