Create blackout and maintenance schedules in Change Management

IT Service Management > Change Management > Configuring Change Management >

Use the Blackout and Maintenance windows to schedule a change. Blackout windows specify times during which normal change activity should not be scheduled. Maintenance windows specify times during which change requests should be scheduled. For example, create a blackout schedule for code freezes at the end of the year. blackout-maintenance-schedule

Role required: itil_admin or admin

Ensure that the Change Management - Collision Detector (com.snc.change.collision) plugin is activated.

Conflict detection uses blackout and maintenance schedules to find potential scheduling conflicts for the configuration items (CIs) associated with a change request. When conflict detection runs, either automatically or by manual request, conflict detection determines if either type of defined schedule applies to the change request. If a potential conflict is identified, a warning message appears and conflicts are listed within the Conflict form section. View conflicts in the Conflict calendar . Note: To use the business service as the source for a blackout or maintenance schedule, the business service must be converted to an application service. For instructions, see Convert business services to application services . For information about application services, see Application services .

Create a blackout or maintenance schedule. Option Description Create a blackout schedule Navigate to Change > Schedules > Blackout Schedules . Click New .

Create a maintenance schedule Navigate to Change > Schedules > Maintenance Schedules . Click New .

On the form, fill in the fields. Table 1. Blackout and Maintenance schedule form Field Description Name Unique name for the schedule. Description Short description about the schedule. Time zone Time zone for the schedule. Select Floating to evaluate planned start and end dates on the Change Request form for the logged-in user.

Source Source of the blackout or maintenance schedule. The available options are Service , Change Request , and CI Class . Note: When you select Service or Change Request from the Source list, the Applies to field does not appear. The Applies to field appears if you select CI Class as the Source, which in turn enables the selection of a CI Class . Applies to CI classification that the conflict detection is filtered on. You can select a dynamic CI group so that all the configuration items in that dynamic CI group will be taken into account for blackout and maintenance when conflict detection is run.

The dynamic CI group is seen as the parent CI to all the CIs that are within that group. If there are scheduling conflicts related to any of the CIs in the dynamic group, the conflict will be shown in the conflicts table of the dynamic CI group.

Condition Conditions to specify the CIs that the schedule applies to. This field does not appear when the Applies to field is set to None .

Note: Related fields used in conditions are not evaluated for blackout or maintenance schedules.

Open the form context menu and click Save . A blackout or maintenance schedule is created and the Schedule Entries, Child Schedules, and Referenced By related lists appear in the change. Note: The Blackout Schedule [cmn_schedule_blackout] table extends the Condition Schedule [cmn_schedule_condition] table, which in turn extends the Schedule [cmn_schedule] table. The Blackout Schedule table inherits the domain properties from the Schedule table which has the Domain and Domain path columns.

Because the Blackout schedule table uses the same Child Schedule and Schedule Entry tables as the Schedule table uses, the domain support is identical. The domain_master attribute is used to derive the domain from a parent record. For more information, see Domain support for schedules .

Create one or more schedule entries by completing the following steps: In the Schedule Entries related list of the new maintenance schedule, click New . Enter a unique name and define the time during which you want to schedule the maintenance. For more information about the schedule entries field, see Schedule entry fields .

A blackout or maintenance schedule is created.

Associate the configuration item with the maintenance schedule that is used in the change request.

Assign a maintenance schedule to configuration items You can review and determine the conflicts in a change schedule by assigning the maintenance schedules to configuration items (CI). After you assign a maintenance schedules to the CI, add the CI to the change request.

Parent Topic: <a class="link" href="../../../product/change-management/concept/c_ConflictDetection.html" title="Conflict detection identifies potential scheduling conflicts for a change request based on the configuration items (CIs), planned start date, and the planned end date in scope for the change. If a scheduling conflict exists, conflict detection also checks any related blackout or maintenance schedules and other active change requests to determine the scheduling conflict.">Conflict detection

Related concepts Conflict calendar

Related tasks Configure conflict analysis properties <a class="link" href="../../../product/change-management/task/monitor-maintenance-schedule.html" title="When a change request is configured to display the conflicts that are outside the maintenance schedule, conflict detection indicates whether the planned start and end dates occur outside the maintenance window or not. By reviewing the conflicts that are detected, you can modify the change schedule.">Configure a change request to monitor outside maintenance schedule conflicts Enable automatic change conflict detection Detect conflicts manually and review conflict details

Related topics Define a schedule Schedule entry fields Parent and child schedules