This article, which is a commercial for a particular solution made some good points about the anticipated growth in what they call "the alarm industry," which in our vernacular is warnings. See The next frontier of risk mitigation and disaster management.
Because of some prominent warning failures, I expect there will be a burgeoning industry of lawyers willing to take on clients who have been "injured" by either a failure to warn, late warnings or those that go awry.
In the above link, they had a list of considerations that I liked--not tied to hardware/software, but functionality. You might consider these in constructing your warning system.
Structuring a solution around effective monitoring and alerting requires an organization to ask these questions:
- What is our appropriate alerting?
- How quickly do we need to react?
- Who is able to help?
- Who needs to be informed?
- How time-critical is the alerting?
- How do we know the right people received the alerting instructions?
- Which alerting procedures can be safely automated?
- What kind of risks can arise?
- Are there any legal requirements to follow?
- Who logs all of these activities? Who is ultimately responsible for the automated alarm plan – and how is this managed from an IT perspective?