---
alias: user-guide-create-schedule
description: "Create a schedule by defining data, scenarios, and optimization rules for automated planning"
---

# Create Schedule

:lock: Schedule.**Create**

:lock: Schedule.**CreateTemplate**

:lock: Schedule.**CreateFromTemplate**

## Overview

In order to create a **Schedule**, select New from the **Schedule** Entity Type page. A template can also be created using a similar procedure and there is also the possibility of using a template to create the new object as well. This selection can be done in the main entity menu.

### General Data

1. Enter a name for the **Schedule**.
2. Optionally, enter a description.
3. Select an existing State Model and then, a State Model State.

    !!! info
	    The only available mode for Scheduling, as of right now, is Automatic. This implies that Scheduling works by running an engine which returns an ordering for the required jobs (individual operations in a certain resource), according to a set of criteria defined by the user.

4. Optionally, define an Owner Role for the **Schedule**.
5. In the Default View property, define the default width of the window. Note that the width can be later adjusted in both the **Schedule** and **Schedule Scenario** windows.
6. The Default Frozen Period defines a period, in hours, starting at the beginning of the planning horizon, in which jobs are considered fixed and, should there be a re-scheduling, will not be changed. This relates to time delay between the replanning process and the implementation of the new plan, which may be too late to affect the most immediate operations.
7. The Time Quantum relates to granularity that the scheduling process will take into account, in minutes. All operation durations will be rounded to a multiple of this values, i.e., if the Time Quantum is 5, and an Operation lasts 2 minutes, then it will be treated as 5 minute one.
8. In the Default Operational Accurate Scenario, define the default length, in days, of the planning horizon to be considered for Operational Accurate Scenarios.
9. The Default Operational Fast Scenario defines the default length, in days, of the planning horizon to be considered for OperationalFastScenarios.
10. The Default Planning Horizon for Planning, define the default length, in days, of the planning horizon to be considered for Planning Scenarios.
11. The Holds processing mode refers to how Materials on hold are to be treated:

    * Include - they should be considered
    * Exclude - they should not be considered

12. The Future Holds Processing Mode refers to how Future Holds should be treated:

    * Ignore - Scheduling will not take the Future Holds into consideration
    * Stop - Scheduling will not consider any Steps/Jobs after the First Future Hold

13. Define how the **Schedule** will handle any job which cannot be scheduled due to not having any eligible **Resources** (considering also Durable and Employee Requirements). There are two possible options:

    * Ignore - Scheduling will not take the job into consideration
    * Error - Scheduling will generate an error for a job with those characteristics

14. Decide whether Area Groups are to be used. A **Material** should only be scheduled to Resources belonging to an Area within its current Area Group. If no **Resource** exists within the current **Material** Area Group for a certain Step within its Area Group, the **Material** may be scheduled to any **Resource** of any Area Group. In this case, for the subsequent steps, the **Material** should be kept in the new Area Group of the **Resource** to which it was scheduled.
15. Define if the setups should use local sorting. If set as `true`, the scheduler will always try to group similar characteristics together and apply a local sorter on each **Resource**.
16. Define whether to apply the Setup Time when there is a change on Characteristics. This setting refers to how the Default Setup Time, defined in each **Resource**, should be handled. If it is not activated, the system will charge the Default Setup Time whether the Setup Characteristic (defined at the **Step** level) has changed or not (in practice, this Setup Time will be charged at the start of each new Operation). If it is activated, the system will only charge the Default Setup Time whenever the Setup Characteristic of the Step has changed (a change in the **Service** the **Resource** is providing, for example). Note that if a **Setup Matrix** is defined for the **Resource**, the values defined in it for each possible Setup Characteristic changeover will override the values obtained by using the Default Setup Time in the fashion chosen in this property.
17. Define whether to schedule batches in risk, which allows for the *Minimum batch capacity usage* restriction to be violated if the due date of a certain **Material** could not be fulfilled otherwise.
18. Define whether to include Durables in the **Schedule** creation.
19. Define whether to enforce scheduled durables at Track-In.
20. Define whether to include personnel in the **Schedule** creation.
21. Define the schedule personnel mode:

    * All Certifications (default)
    * Position

22. Define whether **Employees** must be restricted to their area when scheduling personnel.
23. Define whether to enforce scheduled personnel at Track-In.
24. Select **Next** to continue to the next configuration section.

![Screenshot showing a configuration section for scheduling, with "Next" button highlighted.](images/schedule_creation.png)

### Optimization Criteria

In this tab, first choose the Scheduling Type: Forwards or Backwards. In Forwards Scheduling, tasks for the **Material** start from the present or Planned Start Date and progress forward until all jobs are scheduled, determining the End Date. In Backwards Scheduling, tasks start from the **Material** due date and progress backward until all jobs are scheduled, establishing the Start Date.

In the same tab you must choose the Optimization Criteria to be used for the Scheduling process. It is possible to combine different scenarios, either by adjusting the sliders or by inputting a weight in the text number next to each Criteria. All the weights used must add up to 100. The available criteria are:

* Minimize Setup Times
* Minimize Total Waiting Time
* Minimize Average Lateness
* Maximize Resource Utilization
* Minimize Maximum Lateness
* Minimize Deviation From Delivery Dates
* Maximize Priority Fulfillment
* Minimize Late Materials
* Minimize Quantity Weighted Cycle Time
* Minimize Priority Quantity Weighted Cycle Time
* Minimize Total Cycle Time

!!! info
	To better understand the Optimization Criteria, see the [[tutorials-scheduling-optimization-criteria]] page in the Scheduling tutorial.

![Screenshot showing a table or chart related to 1% Create Schedule optimization criteria.](images/create_schedule_optimization_criteria.png)

### Untie Sort Rules

In this tab, we can specify the default Untie Sort Rules (these may then be changed in each individual **ScheduleScenario**). The available Untie Sort Rules are:

* Execution Time
* Material Due Date
* Material Name
* Material Sequence
* None
* Operational Due Date
* Possible Start Date
* Priority
* Quantity
* Setup Characteristic
* Setup Time
* Wait Time

The rules are used in the order they are inputted, i.e., if the rule in the first position is unable to solve the tie, the rule in the second position is used, and so on.

!!! info
	To better understand the Untie Sort Rules, see the [[tutorials-scheduling-sort-rule]] page in the Scheduling tutorial.

![Screenshot showing a schedule creation interface with options to unbind sort rules.](images/schedule_creation_untie.png)

### Automatic Scheduling

In this tab, we can define specific configurations for automatic scheduling:

1. Select whether to Terminate Scenarios on Release, which will terminate all other **Schedule Scenarios** upon the release of a new **Schedule Scenario**.
2. Define if Operational Accurate Scenarios will be automatically rescheduled.
3. Define if Operational Fast Scenarios will be automatically rescheduled.
4. Define if Planning Scenarios will be automatically rescheduled.

For each of the rescheduling options selected, define:

* Frequency Scale (Days, Hours, Minutes or Weeks).
* Frequency, using the scale defined above.
* Date to start rescheduling.
* For Operational Accurate or Fast Scenarios, define whether the generated **Schedule Scenario** will be automatically released.

!!! info
	The Auto Release option is mutually exclusive between Operational Accurate and Operational Fast Scenarios.

![Screenshot showing a UI with an error in "Create Schedule" field.](images/schedule_creation_automatic_scheduling.png)

Select **Create** to complete the process and create the **Schedule**.