Using CitectSCADA > Configuring and Processing Alarms > Using custom alarm filters > Efficiency considerations

Efficiency considerations

Cicode takes longer to implement than predefined filters. To avoid unnecessary processing of alarms that have already been checked, smart custom filters are enabled by default to minimize the processing necessary for large alarm record counts.

Smart custom filters mean that the first time a query is run, each alarm record will be checked by your function. Subsequent screen displays or record changes will then only call the function for changed or new records.

For most queries, this is how you would want your system to behave. However, there maybe special queries where you wish to turn this behavior off and check each alarm record.

An example might be if you were to request changed or new alarms in the last 10 seconds. In this case the "smart" filtering will not return the desired alarms because some records will not have changed, yet they may be included or excluded from your query.

Two mechanisms exist to control this:

See Also