Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.

Create blackout and maintenance schedules

Log in to subscribe to topics and get notified when content changes.

Create blackout and maintenance schedules

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.

Before you begin

Change Management - Collision Detector (com.snc.change.collision) is activated.

Role required: itil_admin or admin

About this task

Conflict detection uses blackout and maintenance schedules to find potential scheduling conflicts for the configuration items 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 Change conflict calendar.

Procedure

  1. Complete one of the following steps to create a schedule.
    OptionDescription
    Create a blackout schedule
    1. Navigate to Change > Administration > Blackout Schedules.
    2. Click New.
    Create a maintenance schedule
    1. Navigate to Change > Administration > Maintenance Schedules.
    2. Click New.
    Note: When Conflict Detection is executed, it does not evaluate maintenance schedules referenced on a configuration item record.
  2. Complete the form, as appropriate.
    Field Description
    Name Enter a name for the schedule.
    Description Enter a description for the schedule.
    Time zone Select the 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 Select the source of the blackout or maintenance schedule. The available options are Business Service, Change Request, and CI Class.
    Note: When you select Business Service or Change Request in the Source choice list, the Applies to field does not appear. The Applies to field appears if you select CI Class as the Source which in turn allows the selection of a CI Class on which you can apply the schedule.
    Applies to Select the CI classification to which the conflict detection is filtered.
    Condition Select the conditions to specify the CIs to which the schedule applies.

    This field does not appear when Applies to is set to None.

    Note: Related fields used in conditions are not evaluated for blackout or maintenance schedules.
  3. 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.
    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. As the Blackout schedule table makes use of the same Child Schedule and Schedule Entry tables as the Schedule table, domain support is identical, where the domain_master attribute is used to derive Domain from a parent record. For more information, refer Domain support for schedules .

What to do next

Associate one or more schedule entries with this newly created schedule. Users can start applying schedules to determine when changes are implemented to CIs.
Feedback