With FEMA under Presidential Executive Order to develop an "effective, reliable, integrated, flexible, and comprehensive system to alert and warn the American people", private companies active in the space must be asking, "Hey, will that put me out of business?" Others are asking, "Hmm, I wonder if I can sell FEMA something?" These are a pretty good questions considering the Executive Order takes FEMA beyond its historical responsibility of Presidential alerting only.
Well, the answer to both questions is probably "No".
Although FEMA intends to help stand up a modernized, comprehensive national alerting system through their IPAWS (Integrated Public Alert and Warning System) program, they're really planning to build a framework for others to hook in to...which can include private companies. The head of FEMA's National Continuity Programs Directorate, Damon Penn, likens IPAWS to the iPhone. Vendors will be able to build IPAWS apps, just like vendors build iPhone apps.
Of course, there will be rules to follow, just as there are rules for developing iPhone apps. In the IPAWS case, many of those rules have yet to be developed. The most mature rules are the Common Alerting Protocol (CAP) and technical specifications for the Commercial Mobile Alert System (CMAS). The latest version of CAP is expected to be approved by FEMA in the coming months. Once that happens, participants in the Emergency Alert System (EAS), mostly broadcasters, will need to update their equipment so it will work through IPAWS. Meantime, cable carriers are using the approved technical specifications to equip mobile devices to handle cell broadcast alerts through IPAWS.
Vendors who supply other types of alerts and warnings (land line telephone, sirens, texting, email, radio, network, etc) can follow the same path. Same is true of vendors involved with emerging means of alerting and warning (i.e. social media). They can also "build apps" for hooking into IPAWS.
So, no, IPAWS shouldn't put alert and warning vendors out of business. In fact, IPAWS could represent a market opportunity for vendors to shine and deliver value to customers. They'll need to pay attention, get engaged in the process, and follow the rules.
All the best,
Rick
Showing posts with label FEMA. Show all posts
Showing posts with label FEMA. Show all posts
Friday, June 25, 2010
Saturday, June 5, 2010
A Check Point for Our 2010 Top 10 Predictions
We continue to be amazed (and pleased) with the response to our first-of-the-year post where we made 10 predictions for alerts and notifications for 2010. The post continues to be viewed often. So, as we approach the mid-year point, we thought we ought to check ourselves to see how we're doing. So far, pretty good...although we probably need to keep our day jobs and not become fortune tellers (or stock traders). Here's our report card:
1. "Move from proprietary, stand-alone systems to highly-integrated systems." The concept is catching on. More people embrace it. A good example is the City of Philadelphia recently winning an award for their integrated notification solution. The award was The Emergency Management Digital Distinction Award given by Center for Digital Government and Emergency Management magazine.
2. "Common Alerting Protocol (CAP) will continue to take hold." We wouldn't say CAP has taken hold yet, but certainly awareness is growing. Anticipated approval soon by FEMA of CAP version 1.2 will help, as well as first of tests conducted by the new laboratory stood up to test vendor products for compliance. (See our post, "Common Alerting Protocol Seal of Approval".)
3. "IPAWS will become more visible." If emergency management and public safety officials don't know about FEMA's Integrated Public Alert and Warning System, it's not because IPAWS isn't trying. IPAWS representatives are showing up regularly at trade shows and other events to explain their vision and plans for an enhanced national alerting system.
4. "New industry leaders will begin to emerge." No real evidence to support this prediction. However, while helping a state agency build a short list of potential notification vendors, we were impressed with some of the demos we saw - including from a couple of companies we didn't know before. We'd still, however, like to see more impressive new concepts announced by industry.
5. "A highly-visible failure will occur." We're glad we haven't been right about this one...so far. Unfortunately, we're confident this prediction will come true...sooner or later.
6. "Growth in the use of social media for alerts and warnings." Since the first of the year, we've seen a number of communities announce plans to start posting emergency information on social media.
7. "Further commoditization of notifications including 'free services'". At least we figured out what makes one of the more visible of the "free services" tick. Well, perhaps we didn't figure it out. They told us. See our post, "Solving the Mystery of Nixle".
8. "More procurements for independent help." We've seen a few. For example, one capital city county we're aware of has notified a consulting company that they've been awarded a contract to analyze the county's mix of notification systems and make recommendations. (Full disclosure: our company, Galain, is a sub-contractor on the project.) Others are brewing.
9. "More patent lawsuits." We may have been wrong on this one. As far as we know, none has been filed beyond ones we reported on last year.
10. "Other large-scale systems announced." With funds so tight, few new initiatives have been announced. But, we know first-hand of several initiatives developing in large cities and states.
So, we'll give ourselves a B, maybe B-, for our mid-year report card. If we've been too kind in our self-evaluation, let us know.
By the way, this represents our 100th post for Emergency Management magazine. We're most appreciative of this opportunity. We're also pleased that this forum has helped our understanding of what's going on. In addition to making us stop and think for a few minutes here and there, we're given good feedback from the people who follow the blog. We thank you!
All the best,
Rick
1. "Move from proprietary, stand-alone systems to highly-integrated systems." The concept is catching on. More people embrace it. A good example is the City of Philadelphia recently winning an award for their integrated notification solution. The award was The Emergency Management Digital Distinction Award given by Center for Digital Government and Emergency Management magazine.
2. "Common Alerting Protocol (CAP) will continue to take hold." We wouldn't say CAP has taken hold yet, but certainly awareness is growing. Anticipated approval soon by FEMA of CAP version 1.2 will help, as well as first of tests conducted by the new laboratory stood up to test vendor products for compliance. (See our post, "Common Alerting Protocol Seal of Approval".)
3. "IPAWS will become more visible." If emergency management and public safety officials don't know about FEMA's Integrated Public Alert and Warning System, it's not because IPAWS isn't trying. IPAWS representatives are showing up regularly at trade shows and other events to explain their vision and plans for an enhanced national alerting system.
4. "New industry leaders will begin to emerge." No real evidence to support this prediction. However, while helping a state agency build a short list of potential notification vendors, we were impressed with some of the demos we saw - including from a couple of companies we didn't know before. We'd still, however, like to see more impressive new concepts announced by industry.
5. "A highly-visible failure will occur." We're glad we haven't been right about this one...so far. Unfortunately, we're confident this prediction will come true...sooner or later.
6. "Growth in the use of social media for alerts and warnings." Since the first of the year, we've seen a number of communities announce plans to start posting emergency information on social media.
7. "Further commoditization of notifications including 'free services'". At least we figured out what makes one of the more visible of the "free services" tick. Well, perhaps we didn't figure it out. They told us. See our post, "Solving the Mystery of Nixle".
8. "More procurements for independent help." We've seen a few. For example, one capital city county we're aware of has notified a consulting company that they've been awarded a contract to analyze the county's mix of notification systems and make recommendations. (Full disclosure: our company, Galain, is a sub-contractor on the project.) Others are brewing.
9. "More patent lawsuits." We may have been wrong on this one. As far as we know, none has been filed beyond ones we reported on last year.
10. "Other large-scale systems announced." With funds so tight, few new initiatives have been announced. But, we know first-hand of several initiatives developing in large cities and states.
So, we'll give ourselves a B, maybe B-, for our mid-year report card. If we've been too kind in our self-evaluation, let us know.
By the way, this represents our 100th post for Emergency Management magazine. We're most appreciative of this opportunity. We're also pleased that this forum has helped our understanding of what's going on. In addition to making us stop and think for a few minutes here and there, we're given good feedback from the people who follow the blog. We thank you!
All the best,
Rick
Wednesday, May 26, 2010
The Perfect Storm
Some people have been saying the recent Tennessee floods were result of "the perfect storm". Many things lined up to make this a particularly troublesome flood. We live just south of Nashville and, while our home was spared, over 100 families in our neighborhood weren't so lucky. (If consulting and blogging don't work out, I now have a fall-back career of removing duct work from crawl spaces.)
It's been gut-wrenching to see the damage, and to hear that stories from our neighborhood are not isolated. However, many of the stories people are talking about are positive. For the most part, middle Tennessee rallied. Emergency response efforts were strong. Volunteerism made the state truly worthy of its moniker of "The Volunteer State". And, believe it our not, many people are talking about how responsive FEMA has been. FEMA housing inspectors were out in force quickly. Relief checks arrived much faster than expected. The FEMA buzz is positive. In fact, most of the buzz is positive...despite the damage and hardships.
As proud as we Tennesseans are of our response to the floods, we had a lot of luck working for us. For example, it's somewhat of a fluke that few of us lost power for any significant amount of time. Our house on a hill was one of a few in the neighborhood to lose power. It's an eerie sight to see homes down the street, evacuated, with several feet of water in them and all of the lights on.
Because power outages were not widespread, we were able to watch local TV. Our local TV stations did a good job keeping us informed, even though they were having trouble getting from place-to-place because of flooded roads. For the most part, cable service was uninterrupted, no small feat since the local cable company's main facility was right in the path of the flood. Were it not for sandbags and a determined cable company, we could have easily experienced widespread cable outages.
Not so important for us to keep our HBO and cooking channels in service during an emergency, you may think. Well, think again. How many people receive their local TV stations through the cable, and don't know how to pick them up through the airwaves when cable is out...particularly since digital TV has come? And, what if the peak of the floods happened after we were asleep, instead of during the Kentucky Derby when so many of us were watching TV? What would have awakened us and told us our homes were about to be flooded so we could try to move belongings to the second floor before we were ordered to evacuate?
So, one of the things that concerns me is that we have potential to be lulled into complacency by our pride in our response. This was one heckuva flood, many would say the worst disaster to hit the area...ever. But, we're strutting our stuff about how well we're doing. Next time, though, we could easily lose access to TV, our mainstay of information. Instead of rallying, we could easily feel isolation and helplessness that others in similar situations have felt.
Don't get me wrong. We're a hardy and resourceful lot in middle Tennessee. We've made this our home for over 25 years by design. We love it here. But, in this particular disaster, we've also been a lucky lot. I hope we'll shore up our emergency alerting and communications capabilities so next time something major happens, we'll again be able to strut our stuff about how well we've responded.
All the best,
Rick
It's been gut-wrenching to see the damage, and to hear that stories from our neighborhood are not isolated. However, many of the stories people are talking about are positive. For the most part, middle Tennessee rallied. Emergency response efforts were strong. Volunteerism made the state truly worthy of its moniker of "The Volunteer State". And, believe it our not, many people are talking about how responsive FEMA has been. FEMA housing inspectors were out in force quickly. Relief checks arrived much faster than expected. The FEMA buzz is positive. In fact, most of the buzz is positive...despite the damage and hardships.
As proud as we Tennesseans are of our response to the floods, we had a lot of luck working for us. For example, it's somewhat of a fluke that few of us lost power for any significant amount of time. Our house on a hill was one of a few in the neighborhood to lose power. It's an eerie sight to see homes down the street, evacuated, with several feet of water in them and all of the lights on.
Because power outages were not widespread, we were able to watch local TV. Our local TV stations did a good job keeping us informed, even though they were having trouble getting from place-to-place because of flooded roads. For the most part, cable service was uninterrupted, no small feat since the local cable company's main facility was right in the path of the flood. Were it not for sandbags and a determined cable company, we could have easily experienced widespread cable outages.
Not so important for us to keep our HBO and cooking channels in service during an emergency, you may think. Well, think again. How many people receive their local TV stations through the cable, and don't know how to pick them up through the airwaves when cable is out...particularly since digital TV has come? And, what if the peak of the floods happened after we were asleep, instead of during the Kentucky Derby when so many of us were watching TV? What would have awakened us and told us our homes were about to be flooded so we could try to move belongings to the second floor before we were ordered to evacuate?
So, one of the things that concerns me is that we have potential to be lulled into complacency by our pride in our response. This was one heckuva flood, many would say the worst disaster to hit the area...ever. But, we're strutting our stuff about how well we're doing. Next time, though, we could easily lose access to TV, our mainstay of information. Instead of rallying, we could easily feel isolation and helplessness that others in similar situations have felt.
Don't get me wrong. We're a hardy and resourceful lot in middle Tennessee. We've made this our home for over 25 years by design. We love it here. But, in this particular disaster, we've also been a lucky lot. I hope we'll shore up our emergency alerting and communications capabilities so next time something major happens, we'll again be able to strut our stuff about how well we've responded.
All the best,
Rick
Friday, May 21, 2010
Broadcasters Want More Time to Update Emergency Alert System
There's a lot going on toward federally mandated update of the Emergency Alert System (EAS). This summer, FEMA will likely adopt Common Alerting Protocol (CAP) standards new digital equipment must use. A new standards-testing laboratory has been stood up. (See our earlier post.) FEMA, the FCC, and broadcast stations have plans in place for updating and adding Primary Entry Points (PEP), the broadcast stations that serve as the backbone of EAS. An EAS workshop was just announced by the FCC and FEMA. A national EAS exercise is in the works.
However, some broadcasters are concerned. They're not sure they'll have enough time to meet their deadlines. In comments filed with the FCC this week, the National Association of Broadcasters asked the feds to consider funding EAS training programs. NAB also said broadcasters, particularly in smaller communities, may have a tough time coming up with the money to buy the new equipment. At least, they want more time.
Once CAP standards are officially adopted, a 180-day window opens for broadcasters to have the new equipment in place. First, though, vendors must have their equipment CAP-certified by a new laboratory. Testing can't begin until CAP is adopted. Besides, says the NAB to the FCC, some stations and other EAS participants (schools and other public institutions) may not have money in their budgets for a mid-year expenditure. The NAB is not asking for a major change in the requirements, just more time.
Moving forward as fast as possible to update EAS is a good thing. The system is way overdue for overhaul, but the NAB has a good point. Having spent much of my teenaged years in a small radio station in rural Georgia, I can imagine the consternation over spending several thousand dollars on a new piece equipment that doesn't generate revenue. And, way back then, the radio business was more healthy. It seems to me that broadcasters generally welcome their role in EAS, even in these days when money is tighter and many stations don't employ as many people as they did back in the day. A larger window may make sense.
All the best,
Rick
However, some broadcasters are concerned. They're not sure they'll have enough time to meet their deadlines. In comments filed with the FCC this week, the National Association of Broadcasters asked the feds to consider funding EAS training programs. NAB also said broadcasters, particularly in smaller communities, may have a tough time coming up with the money to buy the new equipment. At least, they want more time.
Once CAP standards are officially adopted, a 180-day window opens for broadcasters to have the new equipment in place. First, though, vendors must have their equipment CAP-certified by a new laboratory. Testing can't begin until CAP is adopted. Besides, says the NAB to the FCC, some stations and other EAS participants (schools and other public institutions) may not have money in their budgets for a mid-year expenditure. The NAB is not asking for a major change in the requirements, just more time.
Moving forward as fast as possible to update EAS is a good thing. The system is way overdue for overhaul, but the NAB has a good point. Having spent much of my teenaged years in a small radio station in rural Georgia, I can imagine the consternation over spending several thousand dollars on a new piece equipment that doesn't generate revenue. And, way back then, the radio business was more healthy. It seems to me that broadcasters generally welcome their role in EAS, even in these days when money is tighter and many stations don't employ as many people as they did back in the day. A larger window may make sense.
All the best,
Rick
Thursday, February 11, 2010
FEMA Shows Off its Geo-Targeted Alert System Project
Yesterday, FEMA illustrated its Geo-Targeted Alerting System (GTAS) project, a prototype application of plume modeling and high resolution weather models that may eventually be used for alerting the public.
The application is essentially a map-based notification interface, however, it is connected to some very useful data. First, it receives high-resolution weather data and modeling feeds from the National Weather Service. These feeds allow emergency managers to visualize areas in the path of dangerous weather (currently or forecasted) and to select these areas for the issuance of highly targeted public emergency notifications. Further, the app provides built-in collaboration tools so emergency managers can can work with outside experts to clarify the information being presented.
Second, it offers toxic plume modeling capabilities that, when combined with atmospheric information, provides detailed information on the dispersion patterns of toxic substances. This information can also be used to guide the issuance of public alerts. The application can apparently model more than 500 toxic substances (based on the CAMEO chemicals database).
The application is designed to utilize the Common Alerting Protocol (CAP) for communicating with local emergency notification systems and National Weather Service transmitters. It will also interface with FEMA's upcoming Commercial Mobile Alert System (CMAS) through CAP.
The system was piloted in four FEMA regions last year, and several more pilots are scheduled for this year. FEMA says it expects the application to be generally available to emergency managers by 2013.
All the best,
Lorin
To receive a comprehensive Galain Solutions white paper: "Notifications Alerts & Warnings, The Next Generation," email us your request at resources@galainsolutions.com.
Galain Solutions, Inc.
www.galainsolutions.com
The application is essentially a map-based notification interface, however, it is connected to some very useful data. First, it receives high-resolution weather data and modeling feeds from the National Weather Service. These feeds allow emergency managers to visualize areas in the path of dangerous weather (currently or forecasted) and to select these areas for the issuance of highly targeted public emergency notifications. Further, the app provides built-in collaboration tools so emergency managers can can work with outside experts to clarify the information being presented.
Second, it offers toxic plume modeling capabilities that, when combined with atmospheric information, provides detailed information on the dispersion patterns of toxic substances. This information can also be used to guide the issuance of public alerts. The application can apparently model more than 500 toxic substances (based on the CAMEO chemicals database).
The application is designed to utilize the Common Alerting Protocol (CAP) for communicating with local emergency notification systems and National Weather Service transmitters. It will also interface with FEMA's upcoming Commercial Mobile Alert System (CMAS) through CAP.
The system was piloted in four FEMA regions last year, and several more pilots are scheduled for this year. FEMA says it expects the application to be generally available to emergency managers by 2013.
All the best,
Lorin
To receive a comprehensive Galain Solutions white paper: "Notifications Alerts & Warnings, The Next Generation," email us your request at resources@galainsolutions.com.
Galain Solutions, Inc.
www.galainsolutions.com
Wednesday, January 6, 2010
This is a test of the test
It's not unusual to hear radio and TV broadcasters stop programming to conduct their Emergency Alert System (EAS) test. "This is a test. This is only a test..." (I still have memorized the monthly test announcement I did as a broadcaster on a TV station in Georgia many years ago...that and the Boy Scout Law.)
This week in Alaska, though, the EAS test will be different. A full-blown EAS exercise is being conducted. FEMA, the FCC, the State of Alaska, and Alaska Broadcasters' Association will participate.
"This particular test is going to use the real code as if there was a national-level emergency and the president needed to talk to the American public. It's going to use the actual code that would be used during a national emergency," said Bryan Fisher, Chief of Operations at the Alaska Division of Homeland Security and Emergency Management.
The EAN is a code sent to broadcaster EAS equipment when a Presidential alert is issued. The code alerts broadcasters to an impending message from the White House, signaling them to follow activation procedures from the operating handbook. Once issued, programming is interrupted, EAS header codes are transmitted, attention signals are generated, and the monitoring source is selected that is carrying the Presidential message. Broadcasters are required to conduct weekly and monthly tests of EAS equipment, but the EAN originating from the President has never actually been tested. Based on reports, officials are planning a nationwide test some time next year.
In a FEMA press release, FCC Chairman Julius Genachowski said, “The Alaska exercise will help determine how to further improve the nation’s alerting system and better prepare us in our ongoing efforts to implement Next Generation EAS." The Governor of Alaska called "an excellent proving ground" the exercise.
Digitizing and expanding EAS is one of the initiatives FEMA and the FCC are involved in under FEMA's Integrated Public Alert and Warning System (IPAWS) program.
All the best,
Rick
This week in Alaska, though, the EAS test will be different. A full-blown EAS exercise is being conducted. FEMA, the FCC, the State of Alaska, and Alaska Broadcasters' Association will participate.
"This particular test is going to use the real code as if there was a national-level emergency and the president needed to talk to the American public. It's going to use the actual code that would be used during a national emergency," said Bryan Fisher, Chief of Operations at the Alaska Division of Homeland Security and Emergency Management.
The EAN is a code sent to broadcaster EAS equipment when a Presidential alert is issued. The code alerts broadcasters to an impending message from the White House, signaling them to follow activation procedures from the operating handbook. Once issued, programming is interrupted, EAS header codes are transmitted, attention signals are generated, and the monitoring source is selected that is carrying the Presidential message. Broadcasters are required to conduct weekly and monthly tests of EAS equipment, but the EAN originating from the President has never actually been tested. Based on reports, officials are planning a nationwide test some time next year.
In a FEMA press release, FCC Chairman Julius Genachowski said, “The Alaska exercise will help determine how to further improve the nation’s alerting system and better prepare us in our ongoing efforts to implement Next Generation EAS." The Governor of Alaska called "an excellent proving ground" the exercise.
Digitizing and expanding EAS is one of the initiatives FEMA and the FCC are involved in under FEMA's Integrated Public Alert and Warning System (IPAWS) program.
All the best,
Rick
Sunday, August 9, 2009
Nationwide Cell Alerting Moves Foward
There's a flurry of activity in the effort to expand the Emergency Alert System (EAS) to include cellular phone broadcast alerts. A recent forum, an upcoming deadline for Request for Information (RFI) responses, and a pronouncement by one of the program officials that specifications could be ready in October are all go-forward signs.
Perhaps most telling about what the feds are thinking now about the Commercial Mobile Alert Service (CMAS) program is the RFI (which can be viewed here). In the Request for Information due August 14th, the Department of Homeland Security (DHS) is looking for:
Perhaps most telling about what the feds are thinking now about the Commercial Mobile Alert Service (CMAS) program is the RFI (which can be viewed here). In the Request for Information due August 14th, the Department of Homeland Security (DHS) is looking for:
- information on capability gaps in initial deployment plans
- potential future enhancements because of technology advancements
- possible resources for research and development and test facilities
Beyond the RFI, a forum was recently held where interested parties could get updates from DHS Directorate of Science and Technology (S&T) officials in charge of the initial phase of the program. Program Director Denis Gusty said he hopes specifications will be ready in October for the "switch" that will be necessary to connect all of the pieces.
This is no easy task, particularly as S&T gets deeper and deeper into details. Carriers can be quite persnickety about connecting into someone else's equipment (particularly to offer a free service). And, hopefully, FEMA which has responsibility for the aggregation switch, will be quite persnickety about who hooks into the system and how they do it.
Once the switch design is public, carriers will have 28 months to put equipment in place to receive CMAS messages.
Technology aside, there are still significant outstanding questions. For example, exactly what can CMAS alerts be used for? Presumably, basically the same criteria would apply as for EAS alerts. Since the alerts could be considered less intrusive than interrupting radio and television broadcasts, could they be used for more purposes than EAS? (At least for now, the CMAS alerts would use text, not voice.) And, if so, who would have the authority to activate?
Another question will center around participation. The carriers are generally saying they'll participate. (Avoiding the wrath of the Federal Communciations Commission makes carrier participation compelling.) Then, will the public participate? The current plan would make the alerting capability available on new cell phones once CMAS is launched. Customers would have to opt-out to avoid receiving CMAS notifications.
And, here's one more significant question: how do emergency management professionals and industry make their opinions known?
Despite the outstanding questions, CMAS momentum can be a significant development in the world of alerting. Stay tuned!
All the best,
Rick
Subscribe to:
Posts (Atom)