|
ITE Traffic Incident
Management E-mail Discussion Group Digest #16
December 7 to December 9, 1999
This digest contains the following messages:
#3. TIM
Liaisons - from
Corbin, John
#4. Teleconference and Internet access at TRB room
- from Barry Drogin
#5. I*TRB INCIDENT MANAGEMENT SEMINAR - 1/9/00 -
from Corbin, John
#6. TIM:I*EDL DOCUMENT ACCESS FOR TIM - from
Corbin, John
#7. Re: TIM:I*EDL DOCUMENT ACCESS FOR TIM - from
T. M. Kurihara
#8. Re: TIM:I*EDL DOCUMENT ACCESS FOR TIM - from
Barry Drogin
#9. TRB morning panel - from
Barry Drogin
#10. TIM: TRB morning panel -Reply - from
Ed Mark
#11. ITE*TIM COMMITTEE - from
Wilks, Tobasha
#12. RE: ITE*TIM COMMITTEE - from
Ken Brooke
#13. Re: TIM: ITE*TIM COMMITTEE - from
Barry Drogin
#14. Attention ITE*Tim Committee - from
Wilks, Tobasha
#15. Attention ITE*TIM COMMITTEE - from
Wilks, Tobasha
Disclaimer: Topics
that do not pertain to Traffic Incident Management have been omitted from
the discussion group digests to save the reader time when reviewing
messages, and to save space on the web server. See
Discussion Group Etiquette for examples of other
reasons a message may have been omitted from a digest.
-------------------- 3 --------------------
#3. TIM Liaisons - from
Corbin, John
Top
Date: Tue, 7 Dec 1999 18:19:20 -0600
From: "Corbin, John" <john.corbin@dot.state.wi.us>
Subject: TIM Liaisons
During the Leadership Team teleconference earlier today, I had "lost" the
web location of the current TIM Committee liaison listing. It's
still there at
http://www.trafficincident.org/papers/liaisons.html
Give it a look, and see what you think. If you have suggestions
or a surge of volunteerism for any of the few remaining vacant slots,
please let us know. Sorry for any confusion that I introduced
earlier in the day. (That's probably a blanket statement that I
should make at the end of every day.)
John M. Corbin, P.E., P.T.O.E.
Freeway Operations Engineer
Traffic Operations Center
Wisconsin Department of Transportation
633 West Wisconsin Avenue, Suite 1200
Milwaukee, Wisconsin 53203
phone: 414-227-2150
fax: 414-227-2164
john.corbin@dot.state.wi.us
Top
-------------------- 4 --------------------
#4. Teleconference and Internet access at TRB room
- from Barry Drogin
Top
Date: Wed, 08 Dec 1999 16:04:06 -0500
From: "Barry Drogin" <BDrogin@mtabt.org>
Subject: Teleconference and Internet access at TRB room
We can obtain analog phone lines in the Omni Shoreham Forum conference
room at a cost of $175 per install. That comes with unlimited local
and 1-800 dialing, and long distance at the hotel rate. For two
lines, it would cost us $350. A speaker phone would cost us an
additional $50.
For Internet access, it would be advantageous, after deciding whose ISP we
are using, to find their local dial-in number in the Washington area
(202). For teleconferencing, it would be advantageous to bounce at
least once to an agreeable local entity who could conference us into our
telecon line, or else to find a Washington telecon firm and number.
Hotel long distance rates can be pretty atrocious.
The communications department at the Omni has faxed me their telephone
service order form. The connection there is Jim Polombo,
telecommunication manager, at 202-756-5176. We should give them 1-2
week's notice. As to computer projectors, the AV department is
202-756-6799 or -6899.
Barry Drogin
ATMS Project Manager
ATMS Program Management Division/Engineering & Construction Dept.
MTA Bridges & Tunnels (Triborough Bridge and Tunnel Authority)
Robert Moses Building/Randall's Island
New York, NY 10035-0035
bdrogin@mtabt.org
(212) 870-6535
(212) 870-6515 fax
(917) 641-0533 pager
Top
-------------------- 5 --------------------
#5. I*TRB INCIDENT MANAGEMENT SEMINAR - 1/9/00 -
from Corbin, John
Top
Date: Wed, 8 Dec 1999 17:14:57 -0600
From: "Corbin, John" <john.corbin@dot.state.wi.us>
Subject: I*TRB INCIDENT MANAGEMENT SEMINAR - 1/9/00
The TRB Incident Management Seminar will be held from 8:15 AM to 1:15 PM
on Sunday, January 9, 2000 in Washington DC at the Omni Shoreham Hotel.
The
draft program below is subject to enhancement. The ITE TIM Committee
meeting will follow this event at 1:30 PM on January 9, 2000, also at the
Omni Shoreham Hotel.
Incident Management Seminar
Sunday January 9, 2000
Draft Program
Introduction of Speakers: Phil Masters, Ontario Ministry of Transportation
8:15 AM Welcome and Opening Remarks
Phil Masters, Ontario Ministry of Transportation
8:30 AM Overview of Incident Management
Jodi Carson, Civil Engineering Department - Montana State University
9:00 AM FHWA Update - Incident Management Tools
Dave Helman, Jon Obenberger, FHWA
9:30 AM ITE Traffic Incident Management Committee Update
John Corbin, Wisconsin DOT
9:40 AM Coffee Break
10:00 AM Panel: Incident Management Lessons from MDI's and Priority
Corridors
Phoenix -
New York -
I 95 Corridor - Steve Levine
Gary-Chicago-Milwaukee Corridor -
Seattle -
San Diego -
Los Angeles
Houston -
San Antonio - Pat Irwin
11:30 AM Coffee Break
Introduction of Speakers: Jodi Carson, Civil Engineering Department -
Montana State University
11:45 PM Program Evaluation
Vince Pearce, Booz-Allen & Hamilton
12:15 PM Photogrammetry in Incident Cleanup
C.D. Tyler, PB Farradyne Inc.
12:30 PM Incident Management Program Self Assement
C.D. Tyler, PB Farradyne Inc.
1:00 PM Wrap Up, Final Comments
Phil Masters, Ontario Ministry of Transportation
Top
-------------------- 6 --------------------
#6. TIM:I*EDL DOCUMENT ACCESS FOR TIM - from
Corbin, John
Top
Date: Wed, 8 Dec 1999 17:59:43 -0600
From: "Corbin, John" <john.corbin@dot.state.wi.us>
Subject: TIM:I*EDL DOCUMENT ACCESS FOR TIM
Have you ever accessed the USDOT Electronic Document Library?
There's a lot
- I mean a LOT - of neat stuff. Unfortunately, you have to know what
you
want to find it. Wouldn't it be nice if there was a web site with
links to
EDL documents of interest to specific user groups...for example the
Traffic
Incident Management community?!
As discussed by teleconference yesterday, Chuck Miller of Vanderbilt has
built a web page prototype illustrating a possible approach for Traffic
Incident Management EDL access. The prototype can be accessed at:
http://www.vuse.vanderbilt.edu/~cmiller/
TIMWEB/Prototype.htm
To quote Chuck...
"Several issues that need discussion are:
1) Is a Web site with links to documents focused on traffic incident
management of benefit to Committee members and others?
2) How will documents be identified for posting on the Web site?
3) Will links only be provided to documents at the EDL?
4) What categories should be used?"
Thanks to Chuck for this valuable prototype to stimulate further
discussion.
John M. Corbin, P.E., P.T.O.E.
Freeway Operations Engineer
Traffic Operations Center
Wisconsin Department of Transportation
633 West Wisconsin Avenue, Suite 1200
Milwaukee, Wisconsin 53203
phone: 414-227-2150
fax: 414-227-2164
john.corbin@dot.state.wi.us
Top
-------------------- 7 --------------------
#7. Re: TIM:I*EDL DOCUMENT ACCESS FOR TIM - from
T. M. Kurihara
Top
Date: Thu, 09 Dec 1999 00:37:56 -0500
From: "T. M. Kurihara" <tkstds@mindspring.com>
Subject: Re: TIM:I*EDL DOCUMENT ACCESS FOR TIM
John, I think there is a need for a framework for marking the documents,
parking them, and then retrieving based on search criteria, in addition to
what I see as a flat one-dimension list. The discussion and
agreement on a search model, relationships, and knowledge hierarchies is
not trivial, if you are looking for a robust capability to related EDL
entries to a need for information by the viewer.
The Library of Congress MARC standard for card catalogues has key words,
and other means of categorizing and organizing collection for finding and
retrieving. Given the primary component and subsystem functional view,
secondary categorization views may include the national ITS Architecture
user services or market packages. A tertiary search criteria may
include planning, procurement, concept of operations, testing,
performance, security planning, and deployment lessons learned. I
may be too theoretical and going beyond what you are intending.
There are information and library science practices and techniques that
may be used when designing the TIM EDL and for organizing the TIM EDL
collection. Some of the DOT EDL documents may have to be
re-categorized or put into a different categories for the TIM EDL
collection. \\TomK//
Top |