Emergency notification systems of the recent past were almost exclusively acquired and used by single agencies. Earlier in the decade, it was not uncommon to see Emergency Management using one system, Police or Fire using another, and Public Works using yet another. Typically, there was no attempt at collaboration between agencies (that’s putting it mildly). Even within the same department, different systems may have existed in separate locations.
Although this is still the situation in many municipalities, a growing trend is developing around breaking the traditional ENS boundaries. As such, next-generation systems will move from being single-entity controlled to highly-networked, multi-agency controlled.
Why the move?
First, since 9/11, interoperability has been the industry buzz word. The tragic lessons of that day taught us that communication silos are dangerous, both to the public and to first responders. While interoperability is still a term used most frequently in describing radio systems, the change in thinking surrounding this issue has spilled over into other areas including emergency notification. Walls are being broken down.
Second, the technology has changed. Ten years ago, systems were isolated, hardware-based solutions, residing inside operations centers, and typically attached to dedicated telephone lines. While there are still plenty of these around (and arguments can still be made for taking this approach), the movement today is toward an Internet-based, software-as-a-service (SaaS) model, with no software or hardware residing in the EOC at all. In the future, such a model will be pervasive. And, emergency notification will be but one configurable "module" within a wider, more robust online incident management suite.
Third, funding mechanisms are changing. Years ago, grant restrictions were set up to encourage capital expenditures and hardware acquisition, and to discourage monthly "service fees." As desired solution delivery is changing to a SaaS approach, so are certain funding limitations.
So what does this mean for emergency managers?
First, the breadth and depth of communications across boundaries will continue to grow. A coordinated response is clearly best, and IP-based tools (including emergency notification) that aid in this will mature. Learning to use these effectively and collaboratively will be of high priority.
Second, operating policies will become more complex. Determining who has the authority and responsibility for launching a public alert through a multi-jurisdictional system can be tricky in the heat of battle. Policies and procedures must be clearly outlined, and users across differing cultures and geographic areas must be trained to understand them. Also, solution functions such as security, administrative management and reporting see heightened importance.
Third, multi-jurisdictional funding arrangements will become more common-place (and more complex). When multiple agencies are tapping a central resource, the question of proper and equitable funding always arises. Inter-agency deals will need to be crafted to allow for cost sharing across disparate departments.
While the move to a more connected, multi-jurisdictional approach to notification is not without its challenges, the benefits appear to outweigh the problems. NG ENS will help facilitate a more integrated and interoperable approach to notifying the public and first responders.
What do you think? Do you know of success stories relating to multi-jurisdictional deployments of ENS? Let us know. We'd love to hear from you.
All the best,
-Lorin
To receive a comprehensive Galain Solutions white paper: "Notifications Alerts & Warnings, The Next Generation" go to http://galainsolutions.com/resources.html.
Galain Solutions, LLC
www.galainsolutions.com
Friday, December 11, 2009
Next-Generation ENS Part III: Moving from Single-entity to Multi-jurisdictional Control
Labels:
em_alerts,
em_disaster,
em_health,
em_infrastructure,
em_safety
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment