[TrunkCom] Answering the Call: Communications Lessons Learned From the Pentagon Attack

[iDEN-i95-Beta-Marcel]

Answering the Call: Communications Lessons Learned From the Pentagon
Attack

Executive Summary

The tragic events of September 11th occurred in quick succession with
little or no warning of the impending danger.  Within moments of the
crash at the Pentagon, incident responders from public safety
organizations in the Washington, DC, metropolitan area and, in the later
stages, others from far beyond the metropolitan area borders, arrived on
the scene to support a variety of services including fire suppression,
emergency medical treatment, traffic control, search and rescue, and
crime scene investigation.

A total of 50 public safety agencies responded to the incident resulting

in approximately 900 radio users attempting communications with various
mission requirements and priorities to consider.
To determine the state of wireless communications at the Pentagon, the
Public Safety Wireless Network (PSWN) Program tapped multiple sources
with first-hand, on-site knowledge.  The program conducted 32 interviews
with first responders, technical representatives, and public information
officers from the public safety agencies that responded.  The PSWN
Program also attended police and fire Metropolitan Council of
Governments (COG) meetings, observed panel discussions about the
response to the attacks, and reviewed congressional testimony given by
numerous public safety officials.  The PSWN Program developed the
following findings regarding interoperable communications at the
Pentagon site:

-- Regional Planning and Coordination Effort.  Because of the unique
geographical and political environment of the Washington, DC,
metropolitan area, its public safety leaders realized many years ago
that any response to a major incident in the area would be a regional
response.  With the Metropolitan Council of Governments (COG) providing
a proactive forum for planning and coordination, local jurisdictions
instituted plans and procedures for mutual-aid interoperability.  In
fact, these plans are used on a daily basis by most local agencies,
greatly reducing confusion for responding agencies.

-- Training.  Washington, DC metropolitan area agencies regularly
conduct mass casualty and incident drills that bring together the
various local agencies to effect a large-scale response.  Through these
drills, agencies rehearse the necessary operational and communications
procedures.  Additionally, interoperability training takes form as a
daily occurrence for public safety personnel when responding to routine
incidents in other jurisdictions and using alternate radio systems to
support these operations.
-- Incident Command System.  The early establishment and strict
adherence to a formal ICS was a key factor supporting successful
communications at the Pentagon attack.  The ICS was flexible and
scalable, and allowed the Incident Commander to track and oversee all
facets of the operations.

-- Commercial Services Usage.  Major incidents, regardless of location,
have shown that commercial service networks are not designed to handle
the immense volume of calls generated at or near an incident scene.
Responders found that the only reliable form of communications were
their own, private land mobile radio systems.

-- Lack of Interoperability Among State and Federal Responders.  During
the initial response, the majority of local public safety responders
experienced no difficulty in establishing interoperable communications
on the scene.  This was because of the high-level of regional
coordination and agreements previously established.  However, as the
number of state and federal agencies (secondary responders) increased at
the site, interoperability presented new challenges.  No means of direct
interoperability were immediately available to these secondary response
agencies.

-- Interoperability Assets Inventory.  An inventory list of
interoperability assets (i.e., mobile command vehicles, switches, and
extra radios) available in the Washington, DC metropolitan region does
not exist.
-- "Total Interoperability" Requirement.  First responders require
seamless communications.  However, the level of interoperability
necessary to support operations for secondary, or support responders,
has not been documented.  The level of interoperability necessary to
support effective public safety operations after the first few critical
hours is also undefined.

The PSWN Program developed the following recommendations for public
safety agencies to enhance communications interoperability in responding
to routine and majors incidents:
* Develop regional and statewide communications systems that can support

interoperable communications among multiple agencies.
* Establish mutual-aid agreements and standard operating procedures --
not only among local agencies -- but also among state and federal public
safety agencies.
* Employ the Incident Command System (ICS) to enhance communications
efforts in emergency response situations.
* Conduct mass casualty and disaster response training drills to
identify existing capabilities and potential shortfalls.
* Conduct communications asset inventory to identify tools and their
capabilities.
* Adhere to common technology standards in the design, procurement, and
implementation of future public safety communications systems.

The PSWN Program is a joint initiative sponsored by the Department of
Justice and the Department of the Treasury.  The program works with the
public safety community at all levels of government to improve wireless
radio interoperability.
The PSWN Program brings together public safety officials from local,
state, federal, and tribal governments to increase wireless
interoperability among the Nation's fire, law enforcement, and emergency
medical services
departments.  The program conducts pilot projects and symposiums
nationwide, and provides the public safety community with comprehensive
information on wireless interoperability.

The Report is available here:
http://groups.yahoo.com/group/NEXTEL2/files/Answering_the_Call_Pentagon_Attack.pdf

--
    "NEXTEL1 IT'S NOT JUST NEXTEL"
Subscribe to Nextel1:  http://www.groups.yahoo.com/subscribe/NEXTEL1


  "NEXTEL2 FOR iDEN SOFTWARE DEVELOPERS"
Subscribe to Nextel2:  http://www.groups.yahoo.com/subscribe/NEXTEL2