To access the set-up of an auto event, click on SET UP > Auto Events > Auto Events. At the bottom of the screen (Area 5, the system displays a list of auto events for the sites you are allowed to administrate. They are sorted by site and in alphanumeric order on the description of the auto event with a possibility for an ascending or descending sort on each column.

Set up an auto event

1.Click on icn_add_black or right-click on the list and select Add.

2.Enter a Description.

3.Enter an Abbreviation to be used for graphical supervision.

4.Enter a Description for the auto event.

5.Indicate the Site on which the auto event will apply (choice required from the dropdown menu).

tog_minus        Configuration tab

1.Select the Command relays belonging to hardware installed on the site chosen for the auto event.

2.Indicate whether the signal is activated by a pulse; in this case, check the Pulse relay control box and specify the Pulse duration. If the box is unchecked then the relay will be closed throughout the whole activation period.

3.Define the registered period for the auto event.

a.Double-click on the entry field to indicate the start date and potentially the end date.

b.Click icn_plus to add another registered period.

c.Click on the icn_validate button to validate.

4.Choose the Operating period to determine the annual schedule for the access rule (required field). These are operating periods that were created previously.

5.Check the boxes corresponding to the actions to be carried out for this auto event from graphic monitoring. If no action has been authorised for this auto event, it will not be displayed on graphical monitoring screens.

a.Activate Working Status

b.Activate Stop Status

c.Activate Anomaly Status

icn_info

If access control relays or conditions have been entered, the site can no longer be modified.

In order to modify the site, all notions associated with the site must be removed before being able to modify it.

tog_minus        Conditions tab

1.Select the Activation condition in the drop-down menu (condition set up previously). If you select None, the condition will never be implemented.

2.Select the People concerned from the dropdown menu. These are groups of individuals as created previously, and are sorted by description in alphanumerical order. If the condition has been restricted to a group of individuals, only the people in this group will be taken into account for checking the auto event's execution. For the others, the auto event is in a Not created state. If a group of individuals has not been defined, al the individuals will be taken into account for checking the auto event's execution.

3.Activation if output is deactivated (travel). This indicator can be useful to define the behaviour of the auto event when the system or concentrator/master terminalis started or rebooted.

4.Activating Timer mode:

a.No > activation up to deactivation condition or end of authorisation or end of accountable period.

b.Yes > activation limited to the period of the timer or until the deactivation condition or end of authorisation or end of accountable period

5.Select the Deactivation condition in the drop-down menu (condition set up previously). If the choice is None, then the condition was never created.

6.Select the People concerned from the dropdown menu. These are groups of individuals as created previously, and are sorted by description in alphanumerical order.

7.Indicate the time before Actual deactivation after a period of (time between the moment when the condition is met and the command to deactivate the auto event exits).

8.Indicate the time before Reactivation possible after a period of (time between actual deactivation and the next activation command for auto event exits, e.g. time taken for sodium lamps to cool down).

9.Select the Anomaly condition in the drop-down menu (condition set up previously). If the choice is None, then the condition was never created.

10. Select the People concerned from the dropdown menu. These are groups of individuals as created previously, and are sorted by description in alphanumerical order.

11. Select the type ofWarning for the condition.

a.By relay (audible or visual local alarm). Select the command relay which triggered it from those proposed in the scrolling menu.

b.By software (pop-up window in supervision, define theacknowledgement of the associated anomaly),

c.By email (select email alert from the drop-down menu),

d.By SMS (select SMS alert from the drop-down menu).

12.Select the warning acknowledgement type:

a.Acknowledgement by auto event categorised as an anomaly.

b.Acknowledgment by timeout to stop the alarm at the end of the time entered in minutes and seconds.

13.Enter the Message displayed if anomaly.

14.Indicate the Waiting times before and after fault control.

15.Click the Save button to validate the creation of the auto event.

Clicking on Print allows you to run a report of the auto events configured.

See also:

Auto events and access rules