About the Event Editor

You use the Event Editor to define actions to take in response to events that occur in a process. One event may invoke multiple actions, or one action may be invoked by many events.

An event can be defined as a changing point or alarm state, or even a time of day.

Based on an event, you can perform the following actions:

  • Set point values
  • Acknowledge or clear alarms
  • Create log file entries
  • Invoke specific user-defined actions
  • Invoke Basic Control Engine scripts to execute user-defined logic

At run-time, the Basic Control Engine monitors for events and executes the configured actions.

The Basic Control Engine is based on a multi-threaded design, which allows the system to invoke and execute multiple Basic Control Engine scripts concurrently.

The order of execution of event actions is a sequential execution from top to bottom.

Note: The script is run in parallel with all actions that are being executed for the event. In other words, the Basic Control Engine does not wait for the script to complete before it initiates the next action defined for the event.

Any action can be invoked by any event.

A few of the ways actions and events may be combined are:

Combined Actions and Events Description
Point Actions Based on Point Events Passes information between points.
Point Actions Based on Alarm Events Allow a physical indication of an alarm, such as activating a light on a control panel.
Events Whose Actions Call A User-Defined Routine or Script Defines custom functions that are invoked in response to configured system events.
Note: The Basic Control Engine calls a startup script when the Event Manager starts up and a termination script when it shuts down. These scripts are initially null (that is, they do not do anything). You can use these scripts to perform initialization and termination tasks, such as restoring and saving the value of a global variable. The two scripts are:

You will find copies of these scripts in your project's \scripts directory.