CONTENT

1. INTRODUCTION

CENTO is a multifunctional software platform for data collection, processing and display. This Manual describes the user tool in CENTO "Events".

It is assumed that the user is already familiar with the basic elements of the CENTO interface after reading the "User Manual" instructions.

"Events" in CENTO are designed to increase the observability of system operation by tracking changes in the system status and process equipment, logging events, and notifying users. Events help the personnel to timely react to changes in the technological process and system operation. To achieve these goals, CENTO offers user notification and acknowledgement features alongside event logging.

2. CENTO EVENTS

2.1. Event editor

To go to the Event editor, select the item in the main menu:

Settings > Events > Event editor.

Fig. 2.1 - Event editor in the CENTO menu

Figure 2.2. shows the interface of the Event editor.

Fig. 2.2 - Event editor

The Event editor page provides the option to:

1. Add a new event to the system 
2. Activate  or disable  selected events

3. Edit , copy , and delete in the "Actions" column

4. Delete any number of events 

5. Edit the number of records to be displayed

6. Search for events of interest by filtering  (the filter is located to the right of the table headings)

7. Edit event configuration 

8. Adjust the setpoint text 

2.2. Creating and editing an event in web-interface

An event can be created manually and automatically. Events are automatically created when the setpoint parameter is enabled. For a detailed description, refer to the "Setup Manual".

The text of setpoints can be edited in the Event editor interface.

To do this, click on the button . After that, the Setpoint editing window opens (see Fig. 2.3), where the wording of the setpoints for Triggering and/or Return can be modified, such as Upper/Lower warning limit, Upper/Lower alarm limit, and Upper/Lower physical limit. 

One or more variables can be specified in the setpoint triggering message:

• {{.tag_name}} - tag name;
• {{.tag_code}} - tag code;
• {{.tag_id}} - tag ID;
• {{.tag_code_or_id}} - tag code, if the code is empty, then its ID;
• {{.tag_limit}} - setpoint value;
• {{.tag_unit}} - tag units;
• {{.device_name}} - name of the device to which the tag is linked.

IMPORTANT: if {figure brackets} or dots are missing when writing these parameters, a validation error will occur.

If a parameter with an error (non-existent parameter) is entered, for example: {{.tag_name_2}}, the Operating journal will receive an event of the following type: < no value> > 10.

Fig. 2.3 - Setpoint editing page

To create a new event, click on the button .

Only an authorized user with appropriate rights can create and edit events. 

Fig. 2.4. shows the page for creating a new event. 

Fig. Event editor: creation page

The Event editor window contains the following fields:

Identifier contains the sequence number of the event (filled in automatically), can be changed if necessary.

Name is a field for entering the name of the event.

Object field is used to add an object from the CENTO Information Model (IM), to which the event refers (see "Information Model Setup Manual"). The IM object is selected from the IM drop-down tree.

Device is the device to which the event refers is added in this field. The device is selected from the drop-down device tree.

Event type switches the event type between "Single" and "With return" .

There are two types of events in CENTO – single and with return events. For system objects, there may be important state that the user should see in the active status (e.g., "Ground in a network with isolated neutral", "Switching on a sectionalizer", "Opening the emergency exit door"). Events reporting this important state are opening events. Events reporting the end of an important object state are closing events. These two types of events are events with return. Events with return should ALWAYS be paired: the second event ALWAYS closes the first one. Events in the active state are displayed in a separate tab of the operational log and disappear from there after triggering the closing event. Other events (regardless of their importance) are single events.

Tags field requires to specify the ID of the telemetering tag to which the event belongs;

Message is the message text that should be output when the event is triggered;

Formula field is used to enter a formula that describes the condition for the event to be triggered. Clicking on  will open the list of formulas for forming the event. Description of formulas is given in the Appendix. 

Dead time, (ms) field specifies the delay time for the event to be generated in milliseconds. It helps prevent false events, such as those caused by frequent device polling failures due to poor communication.

Type is a drop-down list used to specify the importance or category of the event.

Acknowledgement is a switch to activate the function of user acknowledgement of event notification;

Sound field is used to select a sound for notification. The drop-down list contains those sounds that are loaded through the Sound Editor (see item 3). The selected sound can be listened to using the button  to the right of the "Sound" field. 

Before acknowledgement is a switch to play the selected sound before the event is acknowledged;

Sound repeats field is used to set the number of repetitions of sound playback when the event occurs.

Warning! Modern browsers block playback of sounds in a browser by default, so sound alerts may not be played. To allow CENTO to play sounds in the browser, follow the steps below (an example is given for Chrome):

1. Left click to the left of the address bar (see Fig. 2.5).

2. Select "Site settings".

Fig. 2.5 - Site settings

3. In the opened window, go to Privacy and security → Site settings → Additional permissions → Content → Additional content settings → Sound, and select Allow (see Fig. 2.6).

Fig. 2.6 - Allow sound

4. Refresh the CENTO page.

After filling in all the required fields, click  and update the configuration (see Fig. 2.7). 

Fig. 2.7 - Update  configuration

If selecting With return in the Event type, the Event editor window displays additional fields with the general heading With return (see Fig. 2.8). These fields are the same as those used for the Single event type.

Fig. 2.8 -  With return event editor window

2.3. Creating and editing events using Excel

Events can be configured using Excel files. This function is available on the page /CENTO/web/ui/configuration_loader/index (Settings > Configuration Files) (see Fig. 2.9). 

Fig. 2.9 - Import/Export configuration file page

To configure events, download the events.xlsx file by clicking the button , then fill in the appropriate cells in the new line of the table in the Events tab (see Fig. 2.10).

Fig. 2.10 - Events tab in the events.xslx file

To create an event, fill in the following columns:

Event ID is an event unique number.

Name is the name of the event.

Event type is one_position or two_position event.

Event status is responsible for the event status: 1 - event is enabled, 0 - event is disabled.

Device ID is a device identifier to which the event refers.

The device is not required to be filled in, it is generated when downloading an Excel file to help with debugging (displays the path of the linked device).

Object ID is an IM object identifier to which the event refers.

Object does not need to be filled in, it is generated when downloading an Excel file to help in debugging (displays the path of the linked object).

Tags is a tag (parameter) Identifier to which the event refers.

Formula defines the condition under which the event is to be triggered. Description of formulas is given in the Appendix.

Dead time, ms is a field to enter the delay time, in milliseconds, for the event to be triggered.

Event type code is a code, which is entered according to the Event type directory using a separate tab in this file.

Event type name is a name of the event type, the field is filled in automatically when uploading-downloading the configuration file.

Message is a message text that should be displayed in the logs when the event is triggered.

Acknowledgement is responsible for the event acknowledgement. True - acknowledgement is enabled, False - acknowledgement is disabled.

Sound ID specifies an ID of a sound file loaded through the sound editor.

Sound name is a name of the sound file, the field is filled in automatically when loading-unloading the configuration file.

Repeat count is used to set the number of repetitions of sound playback when the event is triggered.

Infinity repeat is responsible for repeating the sound until the user acknowledges the event. True - infinite repetition is enabled, False - infinite repetition is disabled.

After all required fields are filled in, the file should be uploaded using the button  on the Import/Export configuration file page (see Fig. 2.9). In the window that appears (see Fig. 2.11), select the filled in events.xlsx file. The system will automatically validate the file to ensure it is correctly filled in and formatted (see Fig. 2.12).

Fig. 2.11 - Upload configuration file window

Fig. 2.12 - Validating the configuration file

If errors are detected, they will be displayed in the file upload window. After all errors are eliminated, the Write configuration button will become available.

After uploading the file, the configuration should be refreshed to apply the changes (see Fig. 2.7).

To make working with events more convenient, CENTO provides the option to edit the event configuration partially using Excel.

To do this, on the page /CENTO/web/ui/event_editor/index (menu item Settings > Events > Event editor (see Fig. 2.1 - Fig. 2.2), search for an events using the filtering , then click on the button and select Download in the drop-down list. After that, the file events.xlsx will be downloaded to the PC, containing only the filtered events from the Events editor.

Actions when filling/editing the columns of the Excel table are similar to the actions during uploading from the Import/Export configuration file menu (see Fig. 2.9 - Fig. 2.10).

NOTE: when adding a new event, crossing Event ID is unacceptable as an incomplete event configuration is unloaded. The new ID should not match the existing one in the system (configuration).

To upload the changes made to the file, click on the button  select Upload from the drop-down list. Events that were not taken into account when downloading the Excel file will remain unchanged

IMPORTANT: partial upload/download is not compatible with previously downloaded Excel files. If an Excel file was downloaded using an earlier version of the service (prior to the introduction of the partial upload/download feature), it cannot be uploaded back - an error message saying "Version incompatibility" appears. 

2.4. Flashing on the diagram

The flashing of an object on the diagram can be configured in the following ways:

1. Flashing by tag

This method is relevant if the system does not have and does not plan to customize the information model.

To customize the flashing of a diagram object by tag:

A) Set up an event that will contain the formula, for example, connection loss (ti40027171 != 1) or restoration of connection (ti40027171 == 1) with the device (see Fig. 2.13). The formula can refer not only to the device status, any tags registered in the system can be applied here, in this example, the device status is used as a special case. For more details on the available formulas and expressions, please refer to the Setup Manual. 

Fig. 2.13 - Event for tag flashing

B) Create a calculated tag with the formula [devstatusNN], where NN is the device id (see Figure 2.14). The binding to devstatus is used for example. The tag to be used for the designated purpose may get the value from the real device or may be based on other tags.

Fig. 2.14 - Calculated tag to create tag flashing on the diagram

C) Set up an object on the diagram, in the rules of which the calculated tag from point b will be applied (see Fig. 2.15).

Figure 2.15 - Example rules with the tag created in step b.

D) After saving the diagram and updating the configuration, if the status of the NN device changes, the system will start it flashing on the diagram until acknowledged.

2. Flashing by the information model object 

For this method to work, the information model should be configured, and the required information model object should be selected in the event setting (Object field). In this case, the diagram object should be active (see more details in the "Diagrams Development Manual") and bound to the information model object selected in the event.

Let us consider an example of this solution.

A) Create an event with the selected object of the information model in the Object field (see Fig. 2.15).

Fig. 2.15 - Creating an event with the information model object.

B) Create an active object on the diagram bound to the object of the information model, which was selected in the event settings (see Fig. 2.16).

Fig. 2.16 - Creating a diagram object bound to the information model.

3. NOTIFICATIONS SETTINGS

3.1. Creating and editing notifications

CENTO has the function to notify users about an event triggered via e-mail.

To configure notifications, go to the /CENTO/web/ui/notifications_configuration/index page (menu item Settings > Events > Notifications (see Fig. 2.1). The configuration of the mail server is described in the "Setup Manual, Mail servers".

Fig. 3.1 - Notifications interface

In the interface presented, the user has the ability to:

1. Create notifications;

2. Edit notifications.

The notification table has the following columns. 

1. Name is the name of the notification.
2. Emails are the e-mail addresses that have been configured to receive notifications.
3. Dispatch period is the time of the day allowed for sending notifications.
4. Iteration period is the minimum time interval between notifications, meaning notifications cannot be sent to the recipient more frequently than this set period.
5. Operation threshold is the number of event triggers required before a notification is sent.
6. State is on/off.
7. Actions are operations available to the user that can be performed in response to an event (edit , copy , delete ).​​​​​​​