--- sourceDocument: Zurich Service Management sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/service-management-for-the-enterprise Release : - zurich ft:locale : - en-US ft:publication_title : - Zurich Service Management ft:clusterId : - sm4e bundleId : - sm4e workflow : - Technology --- # Configure a maintenance schedule # Configure a maintenance schedule {#ariaid-title1} * Release version: Zurich * * Updated July 31, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read After creating a maintenance plan, define specific criteria for determining when the plan should be executed. ## Before you begin Role required: sm_admin ## About this task Depending on the asset or CI for which you are setting up maintenance plans, you can create a single plan or multiple plans. For example, you can set up plans for a class of computer to be rebooted on the first and fifteenth of every month. Note: Plan carefully when defining multiple maintenance 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 do not conflict with one another. Based on the templates associated with the plan, one or more service management work orders and facilities requests are auto-generated. Maintenance schedules can be based on either duration or meter and can be triggered by the first occurring related condition. For example, on the Maintenance Schedule form, select Duration or Meter as the trigger for an automobile maintenance schedule and then define the duration as three months and the meter as 5,000 miles. The schedule is triggered by whichever comes first. With the Duration or Meter trigger selected, the Next run time and Next run value fields are populated in the Maintenance Plan Records related list on the Maintenance Plan form. Note: In a maintenance plan record, the time stamp displayed in the Next run time field is not the same as the time set for executing the planned maintenance. The Next action field in the Planned Maintenance Nightly Run record displays the actual scheduled job execution time for the planned maintenance. When the scheduled job runs, it will check whether the value in the Next run time field is less than the time set of the next planned maintenance nightly run job and if it is, the system will generate a request. A planned nightly maintenance is not executed and a request is not generated based on the next run time. ## Procedure 1. Navigate to AllPlanned MaintenanceMaintenance Plans. 2. Click the number of the maintenance plans you want to associate to a maintenance schedule. 3. In the Maintenance Schedules related list, click New, specify a meaningful Name and Short description, fill in the form, and then click Submit. Note: If the form is configured to show the Next action field, you can select the date and time for the first maintenance to be performed. {#t_DefineAMaintSched__table_apw_f2w_mr__entry__2} | Field | Description | |-|-| | Plan | Name of the maintenance plan that this schedule is a part of. | | Active | Select the check box to activate the schedule for the maintenance plan. | | Trigger | Timing condition that triggers the execution of the plan. * Duration: Maintenance to be performed based on time. Depending on your selection, additional fields appear to define the duration. * Meter: Maintenance to be performed based on count. The Every and Field fields appear. * Condition: Maintenance to be performed when a certain condition is met. The Filter condition field appears * Script: Apply advanced criteria for running a maintenance plan. The Script field appears. * Duration or Meter: Maintenance to be performed based on both time and count, whichever comes first. You must specify the duration and meter details. {#t_DefineAMaintSched__ul_ozt_l2w_mr} | | Trigger type | Duration category for the maintenance schedule. For example, if you select Monthly, the Due day of month field appears so you can specify which day of each month to run maintenance. Different fields appear depending on the trigger type selected. This field appears when Duration is selected for Trigger. | | Repeat | Frequency of the repetition. This field appears when Interval is selected for Trigger type. | | Due day of week | Day of week to repeat on. This field appears when Weekly is selected for Trigger type. | | Due day of month | Day of the month to repeat on. This field appears when Monthly or Annuallyis selected for Trigger type. | | Due month | Month to repeat on. This field appears when Annually is selected for Trigger type. | | Due time | Time of day in hours, minutes, and seconds. This field appears for all trigger types except Interval. | | Every | Number of occurrences, such as miles or pages, that must be recorded before the maintenance plan is executed. Must be greater than zero (0). This field appears when Meter is selected for Trigger. | | Field | Field 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. | | Table | Lists the table associated with the assets or CIs selected for maintenance. This field appears when Meter or Condition is selected for Trigger. | | Lead time | Number 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. | | Condition | Condition that determines if the maintenance schedule should run. This field appears when Condition is selected for Trigger. | | Script | Script that determines if the maintenance schedule should run. This field appears when Script is selected for Trigger. Maintenance runs if the script returns true. The "current" variable is available and represents the record that is undergoing maintenance, for example, a CI. | [Table 1. Maintenance schedule] {#t_DefineAMaintSched__table_apw_f2w_mr} 4. Specify whether the next planned maintenance should occur at the originally calculated time/meter value or whether to restart the meter/interval calculation from the time that the work order was completed. See [Property settings for Planned Maintenance](https://www.servicenow.com/docs/QlK80lBpsJBlxz5YSobh8w "You configure Planned Maintenance properties at Planned Maintenance > Properties ."). * **[Changes to maintenance schedules](https://www.servicenow.com/docs/8YmkAiblxHIBAfedPu23BQ)** If you make and save changes to an existing maintenance schedule, any previously associated records are updated accordingly. *[\>]: and then