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

Best practices

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

When the system alarm is configured to be re-routed, the third-party application is responsible for raising the event associated with the system alarm. A new UpdateSendEvent Application Programming Interface (API) has been created to be called by the third-party application.

The third-party application should only use the UpdateSendEvent API to raise the system alarm event. Since AVEVA has no control over how a third-party application is written, AVEVA asks that you follow the guidelines below to maintain the stability and reliability of the AVEVA Enterprise SCADA system:

  • Third-party applications should call neither the existing SendEvent API nor a Business Logic Tier (BLT) SpoolMsg to raise the system alarm event. Instead, they should only call the new UpdateSendEvent API to raise the system alarm event.

  • Third-party applications not making use of System Alarm Routing feature have no restriction as to which SendEvent APIs or BLTs they can call.