Overview

The Alarms Global Settings encompasses broad configurations for alarm management, including database settings for logging alarm events, determining behaviors upon system startup, and specific alarm handling parameters. Additionally, these properties offer robust audit trail capabilities, ensuring comprehensive tracking of various system events, user activities, and operational adjustments.

On this page:

Solution Example


Configurating Global Settings

The Global Settings interface is composed of three parts, they are:

  • Alarm Logging Database
  • Alarm Handling
  • Audit Trail

See more details on each of them in the sections below.

Alarm Logging Database

The Alarm Logging Database setting manages where and how alarms are logged. Users can choose the database type, define connection parameters, and configure the life span of stored alarm logs. See below a table with all available settings for alarm loggings:

Setting

Description

Database

The type of database used. The default option is SQL Lite. You can adjust this setting by clicking the gear icon.

Connection

The connection string for database connection.

Life Time

Defines the amount of time the data remains in the database (in days).

Alarm Handling

The Alarm Handling setting manages the alarms considering the operational status of the devices. See below a table with all available settings this section:

Setting

Description

Initial Disable Time on Startup

This setting determines the period during startup when alarms are disabled. It ensures that alarms are not triggered immediately upon startup, allowing the system to stabilize first.

Ignore Alarms During TimeDeadband

This option enables the system to ignore alarms during a specified TimeDeadband.

Enable LimitsByShift

Allows the user to set different alarm limits based on different work shifts. See our Alarms Limits by Shift Example.

LogUserFullName

Option to log the complete name of the user.

Audit Trail

The Audit Trail setting allows users to enable or disable system auditing. When active, users can select which actions, such as user logins, system warnings, or tag changes, are recorded, ensuring transparency and traceability.

Learn more on the Audit Trail page.


In this section:

  • No labels