IEEE SCC32 Incident Management Working Group
14 - 15 Aug, Piscattoway, NJ
Meeting Minutes
Chair, Kamal Karna
Vice Chair, TBD
Secretary, Ken
Brooke
Consultant: David
Kelley
Consultant: John
Lathrop
(Held in conjunction with Incident Management Workshop sessions, which
are not covered in these minutes.)
Attendance (from Sign-In Roster).
Called to order at 1600, 14 Aug; reconvened 1000 15 Aug
Appproval of Minutes:
No previous minutes, as this is the initial meeting of the Working
Group
Approval of Agenda:
The agenda
was followed as shown in the handout.
Committee Reports: Committees are being formed. No reports submitted
yet.
Old Business: No old business, as this is the initial meeting
of the working group.
New Business:
Presenters are requested to provide electronic
copies of all presentations to the IEEE website.
Submission procedures:
|
All presentations are considered to be
in the
Public Domain
(unless we are notified otherwise)
|
Kamal Karna
made a welcoming presentation, and general orientation discussions
were held among the attendees.
The Chair made the following subgroup chairmanship appointments:
TMC Centric: Charles Berger
Public Safety: Ron Miner
IM Application Developer: TBD
Emergency Communications: TBD
Scene Management: TBD
HAZMAT Operations: TBD
Technology Evaluations: TBD
John Lathrop gave a presentation consisting of exerpts
from the TCIP Incident Management meeting 7-8 Aug in Boston.
Ken Brooke gave a presentation concerning the definition
and scope of Incident Management.
Bob Barrett showed an EMS-centric view of the architecture, including
The
Emergency Management Subsystem Interfaces and Standards
The
Emergency Vehicle Subsystem Interfaces and Standards
John Corbin presented the Southwestern Wisconsin Incident Management
(SWIM) view of incident management.
David Kelley also offered a TCIP-centric
view of incident management.
James Mona provided some verbal comments concerning his experiences
in sharing information between centers in Connecticut.
Kurt Aufscnieder made the point that incidents were multi-center, multi-discipline,
and at all levels of complexity.
Brian Fariello gave the San Antonio TransGuide view of incident management.
Mike Ogden gave the TTI version of a definition of incident management.
Ann Lorscheider gave the North Carolina perspective on incident management.
Ron Miner gave the Va DOT version of the definition of incident.
Ivor Knight stated that real-time video should be included in the working
groupís discussions (such as from closed circuit television cameras
monitoring a freeway).
Steve Meer gave a presentation outlining a view of TMC and EMC relationships.
Since this was presented on the flip-chart, Stephen Meer accepted an action
to convert the sheets into an electronic format for posting on the website.
Technical Material:
Ken Brooke provided the following examples of previous data element
standarization work
National Highway Traffic Safety Administration EMS Division:
80
EMS Data Points and their Definitions (def.zip, 43K, 01/03/96)
This document contains the 80 EMS data points and their definitions
as agreed upon by at the August 1993 Uniform Pre-Hospital Emergency Medical
Services (EMS) Data Conference sponsored by the National Traffic Safety
Administration. The documents is compressed to 43 K and when extracted
is 215K and is 72 pages in Word Perfect format.
Federal Bureau of Inestigation:
National Oceanographic and Atmospheric Administration:
United States Coast Guard National Response Center:
The following candidate definitions of "incident" were submitted by attendees
for consideration by the group:
-
1. Traffic Incident: An event or occurrence that disrupts or distorts the
flow of traffic on the highway system.
-
2. Traffic Incident Management: The coordinated application of human and
technological resources to minimizing impacts of traffic incidents and
to fully utilizing available highway capacity.
-
3. Incident Management: Unified, coordinated, preplanned response. Best
use of all resources and personnel, minimizing impacts.
-
4. Prioritized Goals:
I. Preservation of human life (safety of public responders)
II. Restoration of flow (secondary - diversion)
III. Restoration/salvage of property.
-
5. Incident: Planned vs unplanned. A disruption or distortion of flow.
Scale of severity from minor (a piece of retread one foot from edge line)
to major (declared state of emergency, as from a hurricane).
-
6. Transportation Incident: Any event of a non-recurring nature which interrupts
the normal movement of traffic, goods or services on the transportation
system.
-
7. Transportation Incident Management: The planned response, or reaction,
to mitigate an event which has occurred on the transportation system. There
are various levels of incident management. It can be the actions of one
person or the coordinated response of multiple agencies.
-
8. Incident Management: An event requiring a coordinated response from
operations and participating agencies with equipment and/or human resources
to minimize the disruption to the traveling public and provide appropriate
emergency response in the most timely, efficient manner possible.
-
9. Incident Management: The coordination/allocation of technology, agencies,
equipment and manpower to detect, respond, and clear roadway incidents.
-
10. IACP Critical Incident: ìAny natural or man-made event, civil
disturbance, or any other occurrence of unusual or severe nature which
threatens to cause or causes the loss of life or injury to citizens and/or
sever damage to property and requires extraordinary measures to protect
lives, meet human needs, and achieve recovery.î
-
11. NFPA Emergency Incident: ìAny situation to which the fire department
responds to deliver emergency services, including rescue, fire suppression,
emergency medical care, special operations, and other forms of hazard control
and mitigation.î
Action Item Summary & Status:
1. Stephen Meer: Convert his flip-chart
presentation into an electronic version and to post it to the IEEE website.
Due by next meeting.
Incident Management Schedule:
-
Next IM Working Group Meeting: 29 Sep 97, at the Sheraton Hotel in Reston,
VA; in conjunction with the ITSA/IEEE/SAE Mayday & Incident Management
Workshop
-
Joint SAE/IEEE Workshop #1 on Incident Management, 30 Sep - 1 Oct, at the
Sheraton Hotel in Reston, VA
-
IEEE IM Workshop #2, Mid-Nov 97, TBD
-
IEEE IM Workshop #3, Mid-March 98, West Coast
Adjournment:
Adjorned at approximately 1200, 15 Aug.
Incident Management Secretary
29 Sep 97
IEEE/ITS
Home Page