Watch the video below to learn more about Singlewire’s approach to M2M or Machine-to-Machine for sending mass notification and emergency communication.
So we came up with Detect, Notify, Activate. Today, it's called M2M (Machine-to-Machine). That 's really where we fit. We worked with a train company, a German train company who had an interest in us. If they have a security threat down on a platform they want to notify every one of that but they also want to do other things.
So, their idea was when we send that certain message out to a particular platform, we want to not only notify the people on the platform, we want to notify the headquarters and some other individuals that this is going on and then when that notification sent reverse the direction of the escalator so anyone going down the escalator is now automatically returned.
I don't know how to say "whoa" in German, but that's what you'd expect if you were going down the escalator, and it comes back. That's really not - the notification is part of it, but it's only a small piece of it. You're really interacting with physical systems on both ends of that.
And really, notification should be attached to all kinds of things, not just a human saying there are doughnuts in the break room. Notifications can be attached to server events, the building events, the physical security events or video surveillance - all kinds of things.
And then, on the other end, you ought to be able to activate other systems as a result. It's vary rare that - if you're only sending a notification, and that's it, that's really paging. But if you're embedding it and integrating with all of these other things, you've got a complete system. And we spent a lot of time on our interfaces to make sure they're open and evolving with the interfaces that other people are building so that our system can drop in amidst these things, and you add that audio text component to it.