Shutdown Calendar
The Shutdown Calendar is configured from Supply Planner → Supply Inputs → Shutdown Calendar (aggregation attributes: Settings → Supply → Calendars → Supply Calendars). This article is the standalone reference for the feature; for the rest of the Supply Inputs screen, start with Supply Inputs.
Shutdown Calendar
With the Shutdown Calendar you can create shutdown calendar events for Production, Procurement, and Transfer Routes from the interface, or upload the data from an Excel file, SQL Server, Psql Server, or Arkieva Enterprise.
A Shutdown Calendar in Arkieva defines periods during which supply activity — production, procurement, or transfers — is not permitted at a given location, supplier, or route. It is the mechanism that communicates real-world operational constraints (plant closures, supplier holidays, route blackout days) directly to the DRP and LP engine so that planned orders are never proposed inside those windows.
Note that shutdown calendar constraints apply only to orders generated by Arkieva's planning engines — orders imported from an external ERP system are not affected and will appear in the plan regardless of any defined shutdown periods
Constrained Date Differs by Supply Type
The shutdown constraint does not apply to the same date field across all supply types. Understanding which date is constrained is critical to setting the right shutdown window:
Supply Type | Constrained Date | DRP/LP Behavior | Key Note |
Production | Production date | Not allowed if date is in shutdown | Straightforward — no production on shutdown days |
Procurement | Order Date (= Delivery Date − Lead Time) | Not allowed if Order Date is in shutdown | Receipts may still land in shutdown if order was placed before |
Transfer | Ship Date | Not allowed if Ship Date is in shutdown | Arrival date may fall in shutdown period |
Example A — Not Allowed
Parameter | Value | Notes |
Shutdown Period | 10-Jan to 15-Jan | End date (15-Jan) is non-inclusive |
Delivery Date | 20-Jan | Target receipt date |
Lead Time | 7 days | From Vendors by Stock table |
Order Date (calculated) | 13-Jan ( 20 Jan -7 Jan) | 10 ≤ 13 < 15 → falls inside shutdown |
How to Set the Attribute
- Navigate to Settings → Supply → Calendars → Supply Calendars to configure the item aggregation level for each calendar type. This is a one-time setting that determines the aggregation level at which supply calendars operate.
- Select the desired item attribute from each dropdown (e.g. Item Family, Item Group, or any custom attribute configured in your tenant).
- The available options in each dropdown reflect the item hierarchy attributes defined in your data model.
- In addition to the standard attributes, you can define custom item attributes — grouping any set of items together for shutdown purposes — and these will automatically appear as options in the dropdown
How to Configure a Shutdown Calendar
- Navigate to Shutdown Calendar: Go to Supply Planner → Supply Inputs → Shutdown Calendar
- Select the Calendar Scope and Period: Choose Location (for Production), Supplier (for Procurement), or Route (for Transfers)
- Enter Shutdown Period: Provide a Start Date and End Date. Remember: the end date is non-inclusive (timestamp-based)
- Add a Description (optional): Label the shutdown (e.g. "Annual Plant Maintenance", "Holiday Closure") for easy identification
- Save the record: The shutdown record is now active and will be enforced on the next DRP run
- Run DRP: Execute the DRP engine — it will automatically respect all active shutdown periods
- Review Results: Verify in planning worksheet that no production / procurement / transfer orders have been proposed within the shutdown window
Configuration Tips & Best Practices
1. Always double-check the end date
Because the end date is non-inclusive, many planners accidentally leave a gap of one day. If you want to block through 15-Jan, set the end date to 16-Jan.
2. Coordinate with the Vendors by Stock table for Procurement
Procurement shutdown enforcement relies on lead times from the Vendors by Stock table. If those lead times are incorrect, the Order Date calculation will be wrong and DRP may allow orders that should be blocked — or block orders that should be allowed. Always validate vendor lead times before running DRP across a shutdown period.
3. Verify shutdown records after each DRP run
After running DRP, spot-check the plan to confirm no orders have been proposed inside shutdown windows. If unexpected orders appear, verify that the shutdown record is saved correctly, the location/supplier/route is matched, and the date range covers the intended period.
Quick Reference Summary
Supply Type | Applies to | Constrained Date | Arrival/Receipt Allowed in Shutdown? |
Production | Location | Production Date | N/A |
Procurement | Supplier | Order Date (Delivery − Lead Time) | Yes, if Order Date is before shutdown |
Transfer | Route | Ship Date | Yes, Arrival Date may be inside shutdown |
Related articles