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