Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA Enterprise SCADA

TABLE OF CONTENTS

Application table

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedApr 24, 2025
  • 2 minute read

Application records are used to represent data from third-party applications. Application records are located in the Application table and are created and edited using the Application Row Edit dialog box.

The open architecture of AVEVA Enterprise SCADA allows data to be extracted from its databases via third and fourth generation languages, such as C and Microsoft SQL. The data can then be entered into custom-developed applications or third-party applications, such as spreadsheets and simulation packages.

The Application table is a simple, generic table that does not require the high overhead of the larger, more complex tables. Unlike the Analog, Status, and Rate tables, the Application table supports string variables; however, it does not provide any eventing or alarming options.

An application record may be used for a number of purposes:

  • It can hold a global variable for use within application programs (Application Calculation Engine (ACE), or CS scripts). The variable can be a string, numeric, and/or boolean value. For example, if many calculated records need to share a weekly computed factor, then the factor can be updated in the application record and used by all of the calculated records.

  • It can hold a calculated value. This value can be calculated by an ACE program attached to the record, or it can be set by a CS script run using the Job Scheduler (jsh). The ACE programs and CS scripts can perform alarming and eventing on the application record. For example, a CS script can be periodically invoked by making the job scheduler query the RealTime Microsoft SQL server and find out if more than five casual users are connected. If this is the case, the program can update the application string value to indicate that the server is normal or overused for casual use, and then generate the appropriate alarm and event messages.

  • It can contain a trigger for an ACE control program. For example, the application record might be used to invoke an emergency shutdown program that triggers programs that are attached to many status and analog devices and places them in the shutdown position.