Home
Setup guide
Install and connect your Security Center SaaS application.
System automation
About schedules
A schedule is an entity that defines a set of time constraints that can be applied to a multitude of situations in the system. Each time constraint is defined by a date coverage (daily, weekly, ordinal, or specific) and a time coverage (all day, fixed range, daytime, and nighttime).

Pre-deployment guide
Review requirements, order, and activate your Security Center SaaS system.
Setup guide
Install and connect your Security Center SaaS application.
- Getting started
- User management
- Device management
- System automation
  - What is system automation?
    System automation in Security Center SaaS is a workflow to trigger actions based on schedules or events. It helps administrators manage repeatable tasks with less effort, so they can focus on higher‑value work.
  - Process overview for using automation entities
    To trigger a series of actions manually, on a schedule, or based on events in your system, you can set up automation entities.
  - About events
    An event is a record of an activity or incident that occurred in the system. Security personnel can monitor events in real time and investigate them later. Events can also trigger automations in the system.
  - About schedules
    A schedule is an entity that defines a set of time constraints that can be applied to a multitude of situations in the system. Each time constraint is defined by a date coverage (daily, weekly, ordinal, or specific) and a time coverage (all day, fixed range, daytime, and nighttime).
    - Date coverage options for schedules
      Date coverage determines which dates a schedule applies to. The following table lists the date coverage options available for schedules in Security Center SaaS:
    - Understanding twilight schedules
      A twilight schedule is a schedule that dynamically adjusts its coverage based on a specified location and the time of year. You can configure it to cover either daytime or nighttime. It is primarily used to adjust camera settings to match lighting conditions. Twilight schedules can only be applied to entities with a configured location.
  - Creating schedules
    To define a set of time constraints for a multitude of situations, such as when a user can log on to the system or when video from a surveillance camera can be recorded, you can create schedules and then apply them to specific entities.
  - Adding audio files
    You can add new audio files that can be played when users receive an alarm in Security Center SaaS, or used with the Play a sound action.
  - About automation entities
    An automation entity is a repeatable process in Security Center SaaS. It consists of two parts: a trigger that defines what starts the automation, and a response that defines the actions that follow.
  - Creating an automation entity
    To begin configuring an automation, you must create an automation entity.
  - Configuring automation triggers
    To determine when an automation runs, you must select and configure a trigger type.
  - Configuring automation responses
    To define what happens when an automation is triggered, you must add response actions to the automation.
  - Advanced settings for automation entities
    Advanced settings allow you to define the automation’s scope, activation periods, and other configuration options in Security Center SaaS.
  - Adding automations to maps
    To allow Security Center SaaS operators to manually trigger automations directly from maps, you can add automations as map objects.
  - Event data
    Event data is the contextual information that accompanies every event. It can be used to add conditions to automation triggers and to contextualize automation responses. Different types of data are available depending on the type of event.
  - Special operators for event conditions
    Special operators can be used to evaluate event data from camera events and custom events for use in automations.
  - Contextualized actions
    For event‑based automations, you can use data from the triggering event to contextualize the response actions. With contextualized actions, a single automation can handle multiple automation scenarios.
  - Understanding threat levels
    A threat level is a predefined scenario that you activate for a specific area or the entire system to manage special situations, such as a business event or emergency evacuation. Activating a threat level triggers a series of actions tailored to the scenario. Deactivating the threat level returns the system to regular operation.
  - Creating threat levels
    To configure a list of actions to activate in special situations for a specific area or the entire system, you can create a threat level.
  - Scenario: Responding to a fire using threat levels
    In case of a fire, threat levels can be used to facilitate evacuation and response by triggering actions to sound a fire alarm, unlock doors, and bookmark camera recordings.
  - Scenario: Responding to a gunman using threat levels
    If a gunman or shooter is spotted, threat levels can be used to block access to areas, trigger alarms, and bookmark camera recordings.
  - Converting event-to-actions to automations
    You can convert legacy event-to-actions to automations using the Automation task.
  - Converting scheduled tasks to automations
    You can convert legacy scheduled tasks to automations using the Automation task.
- Map design
User guide
Perform daily operations and monitor your facilities in the Security Center SaaS application.
Genetec ClearID
Set up and use ClearID in Security Center SaaS.
Federation
Set up and use Federation in Security Center SaaS.
Appliances
Install, configure, and use your cloud-managed appliances.
Troubleshooting
Get quick and easy access to troubleshooting content for Security Center SaaS.
Supported devices
Review the supported devices list.
Supported features
Review the supported features list.
Technical support
Learn how and where to find support to help you solve technical issues.
Glossary

About schedules

2026-08-28

A schedule is an entity that defines a set of time constraints that can be applied to a multitude of situations in the system. Each time constraint is defined by a date coverage (daily, weekly, ordinal, or specific) and a time coverage (all day, fixed range, daytime, and nighttime).

Schedules can be used in many situations, such as automations, recordings, and events.

Time zones for schedules

The time zone used in a schedule is based on the local time zone of the context or entity where it is applied. For example, if a camera is configured for continuous recording using a 9:00 am to 5:00 pm schedule, the schedule adapts to the camera's local time.

If a schedule is applied to a context or entity that has no time zone settings, such as an event-to-action or a user's logon schedule, the schedule uses the local time of the server hosting Security Center SaaS.

Note:

In event-to-actions, you can turn on Use source time from the configuration window to use the time zone of the source entity.