Operations and expense

Although the Application Calculation Engine (ACE) supports the use of all AVEVA Enterprise SCADA methods in your ACE code (acecode), it is important to consider the time a routine will take to execute. ACE works best when the input and output configuration facilities are emphasized. Your acecode is capable of supporting Fldget and Fldput inside an ACE routine; however, these operations take longer, and are therefore more expensive to system performance. Any routine that consumes more time than 1 millisecond can significantly impact ACE performance. Large operations triggered by the ACE routines should be launched asynchronously to minimize the impact on other ACE routines.

Note: ACE is not intended to be used as a soft-PLC engine for software routines that are better suited to running in a station environment. Indiscriminate use of the ACE will significantly impact AVEVA Enterprise SCADA performance and may require additional hardware to improve operating performance.

It is not possible to run more than one instance of an ACE Configuration (aceconfig) routine simultaneously. Running an instance of a routine refers to running both the acecode and the aceconfig associated with one record. On the same note, you should never use acecode to lock or manipulate Aceconfig tables. This causes the ACE to become unresponsive as it is unable to access and update records. If you add a lock to the Aceconfig table and forget to remove it, the Engine is unable to lock the Aceconfig table by itself and it will wait indefinitely for the lock to be removed. Even though the ACE Process would restart, the same issue would reoccur; thus, freezing the ACE.