--- alias: user-guide-manage-resource-scheduling description: "Manage resource scheduling details, including batching configurations and capacity settings for operations" --- # Manage Scheduling/Batching :lock: Resource.**Edit** ## Overview This operation is used to define and manage the **Resource** Scheduling details. ## Setup No specific setup is required other than to meet the precondition of the transaction. ## Preconditions * No specific setup is required other than to meet the preconditions of the transaction. ## Sequence of Steps ### Step 1: Manage Resource Scheduling If the **Scheduling** module is properly licensed in the system, the **Scheduling** section will be enabled and you will be able to define the **Resource** **Scheduling** information. 1. Select the Dispatch Schedule Type which can be Dispatching or Scheduling. If Dispatching is selected, the **Resource**, when marked as Include in Planning, will be considered for Planning. If Scheduling is selected, the **Resource** will be both considered for Planning and Scheduling. 2. Specify whether the **Resource** should be included in Schedules of type Planning or not. If a **Resource** has the Dispatch Schedule Type set as Scheduling, it is both considered for Planning and Scheduling. 3. Define the Scheduling Type: * Batch - a **Resource** of a certain capacity, capable of processing multiple **Materials** together, where the start and end job is the same for all. * Machine - a **Resource** that processes only one **Material** at a time. * Tunnel - a **Resource** like a conveyor belt that processes multiple **Materials** continuously. !!! note If the Scheduling Type is Batch, please refer to the [[user-guide-manage-resource-scheduling#step-2-manage-batching|Manage Batching]] section. 4. Select whether an operation can continue in non-working time, if it has started during a working time period. 5. Specify the Saturation (between 0-1). This is a cut-off value after which the scheduler will look for alternative **Resources** when scheduling an operation. Zero means saturated - the scheduler will always look for an alternative when the higher priority ones are busy. One means non-saturated - the scheduler will always try to schedule the operations on their high-priority **Resources**, unless their delivery dates are at risk. When that happens, it will try to use the all alternative **Resources**. 6. Optionally, select a Setup Matrix to be used when scheduling the **Resource**. 7. Define the default Setup Time and the time frame (Days, Hours, Minutes or Seconds). 8. Optionally, define the Track-In Tolerance. This defines the number of jobs ahead that you can start at the particular **Resource**, with the normal Track-In. For example, if it is defined as one, it indicates that one of the two first **Material** jobs for the **Resource** can be tracked-in. 9. Define whether the **Resource** is set as the preferred **Resource**. 10. Select the Resource Capacity Mode out of the two options: Finite or Infinite. !!! info The Resource Capacity Mode property is directly related to the `RESINFINITE` property in the Scheduling engine, with the direct mapping: * 0 - Finite capacity * 1 - Infinite capacity 11. Select whether to exclude the **Resource** from Scheduling, typically a temporary exclusion. 12. Optionally, define an Availability Date. If defined, for Scheduling purposes, the **Resource** will only be considered after that date. 13. Define the Efficiency (between 0 and 1). The efficiency is used to adjust the processing time - for example, a **Resource** with an efficiency of 0.5 (50%) takes twice the processing time to perform a certain operation. 14. Define the Default Schedule View (Day, Week or Month). 15. Check the Use Timeline Time as Default to use a timeline as the default schedule view. 16. Optionally, define the number of hours to restrict the Scheduling jobs to be displayed in the **Resource** view. 17. Specify the Scheduling View Mode for this **Resource**. The available options are: * Material - The scheduling engine will take the existing work in progress in its current form and schedule it appropriately. * Production Order - The scheduling engine will set production quantity targets per Production Order Step, schedule them to **Resources** and track the quantities. !!! info For more information, see [[tutorials-scheduling-modes]]. 18. Select **Update** to complete the operation. ![Screenshot showing a resource management interface with a "Manage Resource Scheduling" heading and an update button.](images/manage_scheduling.png) !!! info If the Resource State Model State contains a defined Exclude From Scheduling attribute, the system will automatically set the Exclude From Scheduling property, based on the Resource's current State. ### Step 2: Manage Batching If the Scheduling Type is **Batch**, a new section named **Batch Configuration** will be available in the **Manage Resource Scheduling** wizard, and you will be able to define the **Resource** **Batching** information. 1. Optionally, define the Minimum Batch Capacity Usage after which the **Resource** can begin processing. 2. Define the Material Split Mode - Allowed or Not Allowed. This option defines if the system is allowed to split the Material quantity of a chosen Batch Material if it surpasses the maximum limit of the Batch Size. 3. Optionally, choose the Processing Mode - Batch or Material. If the Processing Mode chosen is Batch, choose: * Batch Type - from the Lookup table [[batchtype-lt]]. * Load Mode - None, Offline, or Resource. If you choose Offline or Resource, you will need to specify the Load Start Mode (After Release or Before Release). The default state for the Load Start Mode is After Release. * Container Type - from the Lookup table [[containertype-lt]]. ![Screenshot showing a UI with options for managing batching, including a field referencing the "Container Type" from the nearby lookup table.](images/manage_batching.png) !!! warning The settings you choose in the Manage Batching section will dictate the Resource Information associated with a given [[user-guide-batch-index]]. Once you associate a Resource with a Batch, the changes in the Manage Batching section will not carry over to the Resource Information in the [[user-guide-batch-page]]. Additionally, if the Resource Container Type and Batch Container Type are defined, they must match.