Sites Overview

Sites Basics

A site represents an entity that is monitored by evalink talos. In the real world, this can be a stationary or a mobile object: a building, a car, a mobile surveillance unit, or a single device with a panic button.

A site can receive alarms from a number of sources:

• a connected transmitter

• an integration – for example, an incoming email

• a third party, via a webhook or via evalink talos API

A site can also generate alarms itself: from the schedules, status rules, and workflows configured for it.

info

In the alarm details and in evalink talos UI, a site may sometimes be referred to as a device.

Objects Created for a Site

A site can have the following basic objects created for it:

• workflows that allow to fully or partially automate alarm management scenarios

info

For details, see section Workflow Reference.

• Alarm dispatcher to sort and forward incoming alarms

info

For details, see section Working with Alarm Dispatcher.

• a schedule or a number of schedules that can trigger workflows or can be checked by workflows to make decisions

info

For details, see section Work with Schedules.

• functional statuses that monitor the state of the site and trigger alarms whenever an unhealthy behavior is discovered

info

For details, see section Work with Site Statuses.

• rules and procedures that allow to handle various external, internal conditions, and combinations of those

• integrations – the connected equipment

info

For details, see section Work with Site Integrations.

• virtual devices, such as different virtual receivers

info

For details, see section Work with Virtual Receiver Integrations.

Alarms Processing by a Site

After accepting an alarm, a site:

• customizes it, if configured to do so

• logs the resulting alarm

• outputs the resulting alarm: reports or dispatches it to the configured destinations, or sends it for further processing

info

For details, see section Trigger and Process Alarms.

Site Properties

A site can be a part of your company hierarchy structure. It can be part of a Site Group, Organizational Unit or Service Company.

info

For details, see section Work with Site Groups.

For each site, you can set up its own reporting configuration. For details about working with reports, see section Work with Reports.

Some site settings are global, only Admin and Manager users can configure them on a company level.

Other settings are individual for each site and you can configure them on a site level.

Admins, Managers and Operators can access individual site pages. Some site elements, like contacts and workflows, can be accessed by all roles, including Operators Minimal, outsite of site pages, for example, in wokflow view.