Freq Of Nature

After 9/11 agencies trying to get on same wavelength
[Source: Washington Business Journal]

by James Ridgell

Words and terms such as "interoperability" and "Project 25" have been in the vocabulary of the public safety communications industry for some time now. However, after the Sept. 11 attacks and the attending communications breakdowns, the terms have taken on a new significance — and, in the case of interoperability, a new urgency.

Interoperability means the ability of radio equipment on different systems to communicate with each other. Project 25 refers to the process that developed standards for digital wireless communications interoperability.

A recent report commissioned by New York City shows that the inability of personnel from different organizations to communicate with one another cost the lives of dozens of first responders on Sept. 11.

The report states that New York police officers were able to hear warnings from a helicopter that the North Tower of the World Trade Center was glowing red, and most of the police officers exited the building safely — while dozens of firefighters, who could not hear these warnings, died when the tower collapsed.

The first responders at the Pentagon also experienced similar problems, because federal law enforcement personnel could not communicate with the local police officers and firefighters, which caused some confusion in the coordination of rescue efforts.

The communications breakdowns on Sept. 11 were not isolated incidents, but a symptom of a larger problem in achieving interoperability.

Interoperability doesn't just happen; it must be planned.

Historically, getting numerous agencies from different levels of government in the same area to work together on a communications interoperability plan can be a difficult task.

There can be many reasons for this, such as resistance to replacing and integrating an existing communications system with surrounding agencies or a lack of political control or simply a lack of funding to make the changes.

Sept. 11 taught us a painful lesson about our readiness, and the reasons for not having interoperability become lost in the drive for homeland security.

Project 25: A History

Even though Sept. 11 may have shown us the importance of Project 25 compliance and interoperability, most people have never heard of Project 25 and don't know how it was developed.

Project 25 is a joint effort among the Association of Public Safety Communications Officials, the federal government and the National Association of State Telecommunications Directors.

The intent was to develop standards for digital telecommunications technology, including standards for digital radio equipment that embraces elements of interoperability.

The Project 25 standards were established with input from three sources: the public safety community at federal, state and local levels; the telecommunications industry; and the Federal Communications Commission.

With the threat of terrorist attacks still very real and a large number of public-safety organizations likely to be involved in the response, the need for federal, state and local personnel to effectively communicate with each other has never been more clear, or more vital.

So vital, in fact, nearly all federal agencies now require compliance to Project 25 standards.

This requirement will certainly have an effect on state and local agencies as well, because the nation's airport security is being federalized.

For example, if there were an attack or other emergency situation at Baltimore/Washington International Airport, the federal personnel would have an absolute need to communicate efficiently with the surrounding state and local agencies.

In addition, because of BWI's location, personnel there may need to communicate with personnel from Baltimore, the District, Reagan National Airport and Dulles International Airport.

So you can see that Project 25 compliance and interoperability can, and probably will, have a widespread effect on state and local agencies.

Impact on Telecommunications

The establishment of Project 25 standards has had a profound impact on the telecommunications industry because most manufacturers base their design and development of new equipment on compliance with Project 25 standards.

Having said that, there is much work to be done to achieve interoperability.

First, the various agencies in the multiple jurisdictions must work together to define channels and procedures that determine interoperability.

Second, the technical barriers must be addressed. Achieving interoperability involves overcoming challenges such as varying frequency bands and incompatible technologies within frequency bands. The key is to establish a common denominator — a minimum set of technologies and procedures to ensure effective communications among people who respond to incidents.

Third, funding for new or upgraded communications systems can be one of the most challenging issues for smaller agencies with limited budgets.

Once the proper steps are taken, personnel from various agencies at different levels of government will be able to share information that could carry life and death significance.

It has been a year now since the attacks on the World Trade Center and the Pentagon. In many ways life in America has returned to normal, but talk to anyone involved in public safety at any level and they will tell you their lives are nothing like they were on Sept. 10, 2001.

Our leaders remind us almost daily that the possibility of another terrorist attack is not a matter of if, but when. We must never forget what happened on Sept. 11 or the lessons we learned as a result.

Fully interoperable communications not only makes sense, but it also provides the right tools for our first responders and law enforcement agencies to save more lives and thus deter terrorism by making us a less attractive and less newsworthy target.

James Ridgell is vice president for federal business in the Washington office of Waseca, Minn.-based EF Johnson Co., a provider of equipment to public-safety organizations.

posted by Tracy Justus at 10/1/2002