{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":15099,"path":"field-service-management/work-order-management/configure-work-plan.md","title":"Configure a work schedule","bundle":null,"doc_type":null,"release":"australia","body":"\n# Configure a work schedule\n\nAfter creating a work plan, it’s important to define specific criteria to determine when the plan should be executed. This includes defining the start date and end date for the plan's execution. To create a flexible work schedule for the plan, you can configure multiple work schedules for it and assign them accordingly.\n\n## Before you begin\n\nRole required: sn\\_fsm\\_planned\\_wm.planned\\_work\\_admin and model\\_manager\n\nCreate a work plan before configuring a work schedule for the plan.\n\n## About this task\n\nYou can create a single schedule or multiple schedules for a work plan. For example, a flexible work schedule can be created for multiple assets that belong to the same work plan based on their installation date.\n\n**Note:** Plan carefully when defining multiple work schedules for the same plan. For example, you set up one schedule to replace a printer cartridge every three months. You set up another schedule to replace the cartridge after every 10,000 pages is printed. This conflict could cause the cartridge to be replaced twice in the same week. Ensure that your schedules don’t conflict with one another.\n\nYou can also create planned work schedules through the Planned Work Management Workspace. Navigate to **All** > **Planned Work Management** > **Workspace**, and then select the **List** icon \\(\\[Omitted image \"ListIcon.png\"\\] Alt text: List icon.\\).\n\n## Procedure\n\n1. Navigate to **All** > **Planned Work Management** > **Work Plans**.\n\n2. Open the work plan that you want to associate with a work schedule.\n\n3. In the **Planned Work Schedules** related list, select New.\n\n4. On the form, fill in the fields.\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nName\n\n\n\nName of the planned work schedule.\n\n
\n\nShort description\n\n\n\nBrief summary of the planned work schedule.\n\n
\n\nTrigger\n\n\n\nTiming condition that triggers the execution of the plan. - **Duration:** work to be performed based on time. Depending on your selection, additional fields appear to define the duration.\n- **Meter:** work to be performed based on count. The **Every** and **Field** fields appear.\n- **Condition:** Maintenance to be performed when a certain condition is met. The **Filter Condition** field appears.\n- **Script:** Apply advanced criteria for running a maintenance plan. The **Script** field appears.\n- **Duration or Meter:** Maintenance to be performed based on both time and count, whichever comes first. You must specify the duration and meter details.\n\nWith the Duration or Meter trigger selected, the **Next run time** and **Next run value** fields are populated in the Planned Work Records related list on the Work Plan form.\n\nFor more information on triggers and examples, see [Learn about triggers for work schedules](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/field-service-management/schedule-trigger-types.md)\n\n
\n\nPlan\n\n\n\nName of the work plan that this schedule is a part of.This field is automatically set to the name of the work plan.\n\n
\n\nActive\n\n\n\nOption to enable the schedule for a work plan.\n\n
\n\nDuration Details\n\n
\n\nTrigger type\n\n\n\nDuration category for the work schedule. For example, if you select **Multiple days of the week**, the **Due days of week** field appears so you can specify on which days in a week planned work should be performed. Different fields appear depending on the trigger type selected. This field appears when **Duration** is selected for **Trigger**.\n\n
\n\nMonthly type\n\n\n\nSelect either Fixed or Floating to mention a particular day of the month to run the schedule.This field appears when the **Trigger type** field is set to **Monthly**.\n\n
\n\nAnnually type\n\n\n\nSelect either Fixed or Floating to specify a particular day and month in a year to run the schedule. This field appears only when the **Trigger type** field is set to **Annually**.\n\n
\n\nRepeat every\n\n\n\nSpecify how often the schedule should repeats. For example, if you select weekly repetitions, specify the frequency such as every week or every two weeks.\n\n
\n\nRepeat\n\n\n\nFrequency of the planned work schedule to repeat. This field appears when the **Trigger type** field is set to **Interval**.\n\n
\n\nDue day of week\n\n\n\nDay of week to repeat on. This field appears when **Weekly** is selected for **Trigger type**.\n\n
\n\nDue day of month\n\n\n\nDay of the month to repeat on. This field appears when **Monthly** or **Annually** is selected for **Trigger type**.\n\n
\n\nDue month\n\n\n\nMonth to repeat on. This field appears when **Annually**is selected for **Trigger type**.\n\n
\n\nDue time\n\n\n\nTime of day in hours, minutes, and seconds. This field appears for all trigger types except Interval.\n\n
\n\nLead time\n\n\n\nNumber of days prior to the **Requested Due by** date to determine the date on which work should begin. That date is pre-filled in the **Scheduled start** field for the task. This field appears when **Duration** is selected for **Trigger**.\n\n
\n\nPreserve calculated interval\n\n\n\nOption to restart the interval calculation from the time that the work order was completed.This field appears when **Interval**, **Monthly**, or **Annually** is selected for **Trigger type** and **Fixed** is selected for the **Monthly type** and **Annually type** field.\n\n
\n\nCondition\n\n\n\nCondition that determines if the maintenance schedule should run.This field appears when **Condition** is selected for Trigger.\n\n
\n\nScript\n\n\n\nScript that determines if the maintenance schedule should run. For example, Maintenance runs if the script returns true. The \"current\" variable is available and represents the record that is undergoing maintenance, for example, a CI.This field appears when **Script** is selected for **Trigger**.\n\n
\n\nMeter Details\n\n
\n\nTable\n\n\n\nLists the table associated with the assets or CIs selected for maintenance. This field appears when Meter or Condition is selected for Trigger.\n\n
\n\nField\n\n\n\nField used to define what the occurrences in the **Every** field apply to. For example, if the pages field is entered, the **Every** field can contain the number of pages that are printed before the action defined in the plan is performed. This field appears when **Meter** is selected for Trigger.\n\n
\n\nEvery\n\n\n\nNumber of occurrences, such as miles or pages that must be recorded before the work plan is executed. The value must be greater than zero \\(0\\).This field appears when **Meter** is selected for Trigger.\n\n
\n\nPreserve calculated meter\n\n\n\nOption to restart the meter calculation based on the value defined in the **Every** field.\n\n
\n\nEffectivity Details\n\n
\n\nStart planned schedule based on\n\n\n\nOption based on which the planned work schedule should determine its start date.- Date\n- Field Value\n- Schedule\n- Calculated\n\n**Note:**\n\n - Configure the extension point sn\\_fsm\\_planned\\_wm.PWMScheduleStartExtensionPoint to calculate the start date for the work schedule.\n - For calculated work schedules, schedule occurrences are not automatically updated if changes are made to the extension point implementation after the schedule occurrence has been created.\n\n\n
\n\nEffective Start\n\n\n\nEffective start date from when the planned work is scheduled to work.\n\n
\n\nEffective start reference\n\n\n\nField value that should be used to determine the start date of the planned work. Effective start reference displays the list of fields from the table that is selected to create conditions for the work plan. For example, Printer \\[cmdb\\_ci\\_printer\\]This field appears only when **Field Value** is selected from **Start planned schedule based on**.\n\n
\n\nSchedule\n\n\n\nName of the schedule that should be used to calculate the start date of the work plan.This field appears only when **Schedule** is selected from **Start planned schedule based on**.\n\n
\n\nEnd planned schedule based on\n\n\n\nValue that determines the end date of a planned work schedule.- Date\n- Field Value\n- Frequency\n\n\n
\n\nFrequency\n\n\n\nDetermine how often the planned work is scheduled to be performed. For example, if frequency is mentioned as 4, the planned work cycle will run for four times and ends after the fourth iteration.\n\n
5. Select **Submit**.\n\n\n## Result\n\nThe schedule is created for a work plan. The Schedule Occurrences related list is added to the schedule to track the occurrence of maintenance cycles for the schedule.\n\nThe schedule occurrences are created automatically for duration-based schedules. However, if a different trigger option is selected for a schedule, the occurrence is created only when the specified condition or meter value is met. The creations of schedule occurrences depend on the effective end date. If no effective end date is specified, the application generates the next occurrence of the schedule. For more information, see [View schedule occurrences for a planned work](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/field-service-management/work-order-management/view-schedule-occurrences-for-a-planned-work.md).\n\n"}}