Our system integrator is using AVEVA SP OMI 2023R2 for our Building Management System (BMS). We are looking into an alert software on company level. Proposed alert software offers a REST API, which is used for triggering, acknowledging and resolving incidents, requires that our system be able to make outbound connections on TCP port 443 (for HTTPS).
System integrator tells us that they will need to use the scripts to send the alarms as alerts over this alert software's REST API. Since the alarms are defined inside the objects, they need to write the script for each object inside the galaxy; filter any ‘Priority 1’ alarm and when triggered, run the script for each alarm and send the json payload. This creates the following issues:
- Performance issue: It may happen that in event of several alarms triggering at the same time, the scripts may be slow to execute and there is also a fear of a script failing to execute and not sending the alert to alert software.
- Difficult management: the scripts need to be written for each object separately and not one script on galaxy level. This makes both the implementation and the maintenance difficult.
Questions:
- Are the two issues mentioned above true?
- the scripts will be a copy paste for all galaxy objects or tailored?
- Is there any better way to achieve the goal?
- If another alert software offers connecting via OI gateway, is it better to use OPCUA from OI Gateway, to manage the alerts or the REST API can do the job equally well?
