The security week that was: 12/16/11 (public safety alarm communications)

Are we missing the big picture?

The Alarm Industry Communications Committee (AICC) is campaigning to enact a ban on fire departments and police departments receiving alarm signals directly, but I'm going to tell you here that we're missing the boat on this whole legislation.

The language that upset the AICC is part of H.R. 3630, and specifically from a portion that is referred to as the "Jumpstarting Opportunity with Broadband Spectrum Act of 2011". This spectrum act is part of what you might call an omni-bus legislation in that it includes other elements, including payroll tax relief, FEMA flood relief and a lot of other stuff that really shouldn't be tied together in the first place...including this part on alarms into 9-1-1 dispatch centers. The measure passed the House of Representatives on Wednesday with a vote of 234 to 193, and it still included language that mentions: "nonhuman-initiated automatic event alerts, such as alarms, telematics, or sensor data, which may also include real-time voice, text, or video communications."

Despite the fears of the AICC, the text of the actual bill isn't encouraging your commercial or residential customers to send alarm signals directly to police dispatch. All it does is actually allow for the 700Mhz spectrum (old analog TV spectrum) and some other radio spectrums to be auctioned, as long as a portion of that spectrum is still available for use in national emergency communications, and one of the things it allows for that spectrum to be used for is signaling data.

But what the industry is up in arms about is that people have been convinced that this legislation is saying that your customers can send their alarms directly to the dispatchers, avoiding our central stations. Sure, as an industry we want those signals to come through our own central stations so we can get the $30/month or more that we can charge customers. That's just smart for our industry, so it's good that the AICC is campaigning for this legislation change. But the industry is up in arms over a mis-understanding. I even received a note from the AICC which called for every dealer to write their senator the note claimed that: "Allowing unverified alarm signals to go into 9-1-1 centers would cripple the emergency response system."

Now with all respect to our industry, and as a huge industry supporter myself, I still have to ask the obvious question: Aren't we already allowing unverified alarms to go into 9-1-1 centers? Be real: Do we actually verify these alarm signals? Sure, we may use "enhanced call verification" which means that we try to call a couple people on the contact list to see if it was an accident, and if we don't reach them, we assume it's a real alarm and pass it along to 9-1-1. But let's be very honest to ourselves here: Enhanced call verification is not actually "verification"; it's really a "verification attempt". Yes, it may weed out some of the bad alarms, but as an industry that tends to use ECV, we're still loading dispatch centers and police with bad calls, since 95% or more of alarm signals sent from our own stations to police are reported to be false alarms.

So, I have to ask, why are we worried about unverified alarm signals going to dispatch centers when we're mostly sending them false calls anyway? Why are we up in arms over what is an inconsequential element of this legislation?

In addition, there has never been a ban on police and fire departments from receiving dispatches directly. Plenty of police dispatch centers already monitor their own facilities and receive alarm signals directly from key assets, and this bill is only providing that as a continued possibility as it seeks to develop a "National Public Safety Communications Plan to govern the use of the spectrum licensed to the Administrator in order to meet long-term public safety communications needs."

And really, if you dig deeper into the actual bill, it becomes clear the AICC, SIA, ESA and others should have been more interested in the part of HR 3630 that sets up the "Public Safety Communications Planning Board" -- which will allow for the mobile handset makers and mobile wireless companies to sit on the public safety communications board, but which doesn't specifically allow for anyone other than the wireless cellular guys to advise this board...not you, not me, not anyone from the broad security or alarm industry. Really what is going on is that it's become assumed that certain government-controlled radio spectrum is going to end up in the hands of Verizon, AT&T and the like, and the advisory board for this whole deal is those same people. It's a situation of the wolf guarding the chicken coop! The only way around this is that if someone from the security industry is selected as a state/local government representative to "represent other interests of state and local governments."

I guess my point is that let's not overreact on small piece of irrelevant language; let's see the forest for the trees and focus on legislation that really shapes our industry, rather than nit-picking at the status quo.

Go here to read the full text of the H.R. 3630 bill (but have a good hour or so to devote to this):


In other news
Occupy Wall Street movement disrupts port operations, Mixed outlook for security industry in 2012, more

Several ports on the West Coast were forced to cease parts of their operations this week after protesters with the Occupy Wall Street movement staged blockades. ... Research firm Memoori is predicting a mixed outlook for the physical security industry in 2012. The UK-based research firm says that while the industry has turned in a “stellar performance” over the past couple of years, its performance is expected to decline in some aspects. ... Four people were killed and 75 were wounded when a man in the Belgian city of Liege hurled grenades and fired shots from an assault rifle into a crowd of holiday shoppers. ... A woman was arrested by police in Oklahoma after she allegedly tried to make meth in the back of a Walmart store.