> For the complete documentation index, see [llms.txt](https://help.sequorplatform.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sequorplatform.io/documentacao/documentation-en/registrations/registrations-backoffice/calendar-registration.md). # Calendar Registration #### Factory Calendar in Sequor MES The module **Calendar** is responsible for structuring and managing the **work and downtime periods** of the plant.\ Through it, Sequor MES defines **workdays, holidays, scheduled shutdowns, and operating shifts**, ensuring that all production, capacity, and resource availability calculations are aligned with the factory reality. #### Module Objective Allow **the planning and control of the plant's productive time**, by configuring: * Workdays and non-working days; * Regional and national holidays; * Shifts and working hours by day of the week; * Special operating schedules. > 💡 **Tip:** the correct calendar configuration is essential for OEE reports, production capacity, time entries, and order planning. ## 1. Access to the module In the Sequor MES main menu, go to:\ **Registrations → Calendar**

### 1.1. Initial listing screen The main screen displays all calendars registered in the system, allowing records to be created, edited, or duplicated. | Field | Description | | ------------------- | ------------------------------------------------------------- | | **Calendar Code** | Unique identifier (e.g.: CA-2025). | | **Description** | Descriptive calendar name (e.g.: Annual Calendar 2025). | | **Valid From / To** | Calendar validity period. | | **Status** | Indicates whether the calendar is **Active** or **Inactive**. | > 💡 **Tip:** keep only **one active calendar per plant and period** to avoid overlapping rules.

## 2. Calendar Registration Tabs When creating or editing a calendar, the system displays five main tabs that bring together all plant operating configurations. ### 2.1. Tab **General** In this tab, the **basic data and validity period** of the calendar are defined. | Field | Description | | ------------------------- | ------------------------------------------- | | **Calendar Code** | Calendar identification (e.g.: CA-2025). | | **Description** | Calendar name (e.g.: Annual Calendar 2025). | | **Valid From / Valid To** | Start and end dates of validity. | | **Active** | Defines whether the calendar is in use. | > **Example:**\ > Code: CA-2025\ > Validity: 01/01/2025 to 12/31/2025\ > Status: Active

> 💡 **Tip:** use the **duplicate** feature to generate next year's calendar, keeping the rules and adjusting only dates and holidays. ### 2.2. Tab **Non-Working Day** In this tab, the **non-productive days** that are not classified as national holidays — such as **scheduled shutdowns** or **regional holidays**. | Field | Description | | ------------------------ | -------------------------------------------------------------- | | **Non-Working Day Type** | Event classification (Regional Holiday, Plant Shutdown, etc.). | | **Description** | Event name (e.g.: Scheduled Shutdown, RS State Day). | | **Date** | Date of the non-working day. | | **Active** | Defines whether the event is in effect. | > 💡 **Example:** > > * Type: Plant Shutdown > * Description: Scheduled Shutdown > * Date: 11/09/2025

Non-Working Day Tab - Calendar Registration

> ⚠️ **Attention:** if there is overlap between a holiday and a plant shutdown, the day will automatically be considered **non-working**. ### 2.3. Tab **Holiday** Allows registration of **national and local holidays** that impact plant operations. | Field | Description | | --------------- | --------------------------------------------------- | | **Description** | Holiday name (e.g.: Christmas, Labor Day). | | **Date** | Holiday date. | | **Active** | Defines whether the holiday is valid in the period. | > 💡 **Tip:** keep all registered holidays — including movable ones — to avoid incorrect capacity and work-hour reporting. > **Example:** > > * Universal Fraternity Day – 01/01/2025 > * Labor Day – 01/05/2025 > * All Souls' Day – 11/02/2025 > * Christmas – 12/25/2025

### 2.4. Tab **Work Hours** In this tab, the **standard work shifts**, by day of the week, throughout the validity period. | Field | Description | | -------------------- | ----------------------------------------------- | | **Day of the Week** | Selection from Monday to Sunday. | | **Shift** | Shift code and name (e.g.: T01A – Shift 01 A). | | **Start / End Time** | Start and end times of each shift. | | **Day Transition** | Marking for shifts that go past midnight. | | **Active** | Defines whether the shift is active on the day. | > **Example of 3x8 structure:** > > * Shift 01A: 06:00 – 14:00 > * Shift 02A: 14:00 – 22:00 > * Shift 03B: 22:00 – 06:00 *(Day transition: Active)* > ⚠️ **Attention:** mark **Day Transition** whenever the shift crosses midnight, ensuring correct time and availability calculations.

### 2.5. Tab **Work Schedule for Special Day** This tab allows configuring **work schedule exceptions** for specific days, without changing the standard shifts from the previous tab.\ It is used in situations such as **reduced shifts, collective overtime, or special dates**. | Field | Description | | --------------------------------- | ------------------------------------------------------- | | **Description** | Name of the special schedule (e.g.: Special Shift 01). | | **Date** | Date of application of the schedule. | | **Shift / Start Time / End Time** | Definition of specific shifts and times. | | **Day Transition** | Indicates whether the shift crosses midnight. | | **Active** | Enables execution of the schedule on the specified day. | > **Example:** > > * Description: Special Shift 01 > * Date: 08/28/2025 > * Shifts: > * T01A – 06:30 to 14:30 > * T02A – 14:30 to 22:30 > * T03B – 22:30 to 06:30 (Day transition: Active)

Work Schedule for Special Day Tab - Calendar Registration

> **Application:** this configuration replaces the normal schedule **only on the indicated date**, without changing the rest of the weekly schedule. ## 3. Best practices * Keep one **calendar per plant** or operational unit. * Use **standardized names** (e.g.: CA-2025, CA-2026). * Register all **fixed and movable holidays** of the year. * Review **shifts and day transitions** before activation. * Record **scheduled shutdowns and special days** with clear descriptions. * Always **verify the validity period** and keep only **one active calendar per plant**.