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.