Classic Bad Technology Predictions

By Mark J. Fletcher, ENP | 21 Jan 2012

For the most part I think that we can all agree that it's generally a bad idea to say something can't or won't be done. In addition to inciting the multitude of industrious thinkers that exist today to think even harder, technology is changing at such a rapid pace that almost anything is possible in the future.

I thought that I would put together a list of some common bad predictions that were made in the recent past, and maybe not so recent past, to remind everyone that anything is possible, and when it comes to anything" being something related to public safety that will save lives, there is even more "possibility". With that, I offer you Fletch's list of top 5 bad technology predictions:

5
"I think there is a world market for maybe five computers." - Thomas Watson, chairman of IBM, 1943.
(Some have estimated that there are upwards of one and 2 billion computers in the world today.)

4
"The Americans have made use of the telephone, but we do not. We have plenty of messenger boys." - Sir William Preece, chief engineer of the British Post Office, 1876.
(You mean have somebody write a note, and then deliver it for them?)

3
"The wireless music box has no imaginable commercial value. Who would pay for a message sent to nobody in particular?" - Opponents of David Sarnoff in response to his request for investment in the radio in the 1920s.
(They should have tweeted their views and opinions, or put them in a podcast, not publish them in the paper.)

2
"This 'telephone' has too many shortcomings to be seriously considered as a means of communication. The device is inherently of no value to us."
Western Union internal memo, 1876.
(No value to you, but to 6 billion other people apparently.)

1
"Unless you are under 30 years old, you will not have to be concerned about next generation 911 in your career." - Participant at the Great E911 Debate, Newport Rhode Island, 2011.
(Hey, I'm 50! And I'm worried about it now! NG911 is here today.)

As I mentioned last week, there's been far too much complexity around E 911 for the enterprise. IT administrators don't necessarily understand it, and quite often they fall back on the simple approach of "what is the law?" But don't get too wrapped up in what "the law says" in any particular state. You need to think about what level of service you need to provide to your employees under your care, using your telephone system.

Too often I see too many companies over rotating on their E 911 solution in the enterprise. They've never had anything before, they realize they got a huge problem now, and they put in an architecture that "sounds" like it's the best, or most precise. Another common mistake is to provide a required hosted E 911 solution for remote VPN users, or work-at-home employees who have an IP device, and then, without any further thought, roll out that same solution throughout the entire enterprise, not just externally where it's needed, but internally where it may not.

Understanding E 911 in the enterprise, and defining the problem and resolution, usually doesn't mean buying a particular box from 911 vendor XYZ Incorporated and plugging it in. E 911 is a process that requires potential system integration, maybe some database work, and a formalized standard operating procedure that covers moves adds and changes, new employee provisioning, and the removal of stale records as employees move on.

Just like there's no magic Accounting box that will automatically and autonomously prepare your financial statements with no input from your bookkeeper, there is no magic E 911 box that will automatically and autonomously manage your E 911 parameters in the public ALI databases, and quite frankly, the real amount of management that's required is that level may just surprise you.

I like to break E 911 in the enterprise down to three primary decision points:

Localized On-site Notification to Internal Staff
Assigned internal first responders should be aware that any E 911 call took place, and wherein the building the caller was located. This is not data that we are pushing to the PS/ALI database. It's internal information for use by our own internal employees that will assist public safety in locating the caller in need.

Support for Nomadic Behavior on my PBX, AND on my Network
Administrators, and the PBX itself, need to understand where users are, when they move, as well is when they enter or leave the environment, in the case of WLAN devices.

Support for Remote VPN Workers on my PBX, but NOT on my Network
As we flatten and consolidate the network, and allow employees to ubiquitously work from wherever they gain an Internet connection, we need to be cognizant about how we provide E 911 services using new a new native technology designed specifically for that class of user.

Unfortunately, enterprise 911 is teaming with "snake oil salesman" that drone on about cases of misfortune and million-dollar lawsuits. Sure, some of that is valid, but most of that stems from ill-fated procedures that have never been vetted or even audited for local compliance.

A new form of engagement, is the E 911 Risk Assessment Audit. It includes a site visit, discussion with your staff to determine specific requirements, as well as a review of the configuration on your PBX.

A good risk assessment audit can't be done over the phone, nor can you click a few questions on a webpage to get the magic answer. It's going to take a professional who understands E 911 compliance a face-to-face meeting to help you determine what you're going to need. And remember, if they just come in and throw dirt on the floor, they're probably going to try to sell you vacuum cleaner.