SMS and Voice Notification for Remote Alarms

Ignition
,
1

Let me preface this by saying I'm fairly new to SCADA design in general.

I've designed this Perspective project and am now trying to set up Alarm Notifications in the Gateway. We've purchased the Alarm Notification, SMS Notification, and Voice Notification modules to be able to do this.

The original intention was to use the SMS Notification module with an Airlink/carrier sim card and Voice Notification with a VOIP. This would fulfill the user's need for SMS alarms (or iOS push notifications) and Voice calls (for critical alarms).

However, I found there are many ways to accomplish what I'm doing and I don't know if my original plan is the most efficient or cheapest way to go about it.

Here are some other methods that lead to the same results:
A) Use an SMPT to send emails to phone carrier gateway(s) for SMS and VOIP for voice (this saves from having to purchase an Airlink and monthly cost of an active SIM card)

B) Use Twilio for both SMS and Voice (allows configuration all in one place and would not need multiple subscriptions)

C) Use Win911 for alarms (much higher startup cost, but allows to a perpetual license so there isn't a need for monthly subscription)

For reference, there is internet access at the Gateway and this system is likely seeing less than 20 alarms a week. The site also has access to a phone line from an autodialer that is being removed.

What have you done in the past for remote alarms? Is there a method you prefer with your systems? Any other recommendations here?

2

A) Use an SMPT to send emails to phone carrier gateway(s) for SMS and VOIP for voice (this saves from having to purchase an Airlink and monthly cost of an active SIM card)

B) Use Twilio for both SMS and Voice (allows configuration all in one place and would not need multiple subscriptions)

C) Use Win911 for alarms (much higher startup cost, but allows to a perpetual license so there isn't a need for monthly subscription)

A) Have done this, works ok but can appear in junk text folders on some phones, also some carriers restrict this and or want to charge money for it. Is reliant on an internet connection.

B) Have also done this, pretty easy to set up, generally a pain to get the client set up with, as they use 2FA for the account with mobile phone authentication, so either you who is administering the account can log in, or the client who pays the bills, but only one of you can be on the 2FA for the login, which is annoying. Is also very fast to send messages as they queue nicely. Again, need a constant ethenet connection.

C) Never used this, seems clunky and yet another software platform to support. Also looks like it needs an internet connection.

D)Use a hardware SMS dialler for notifications. Fully self contained, if ignition and the dialler have power and connection to each other, the message will be sent. Only requires the SMS carrier to be online, no worries about ISP issues or IT outages or IT firewall issues. If using a SIM card, use a business one that has a decent management portal, clients never remember to top up prepaid SIMs from experience.

In my experience, most of our clients want the hardware SMS module, they are wary of anything that relies on the internet for critical notifications. They then also want Twilio as it is much simpler and easier for non critical notifications.