New Search
My WebLink
|
Help
|
About
|
Sign Out
New Search
Eugene Master Traffic Communications Plan
COE
>
PW
>
Admin
>
Finance
>
Operating
>
2011
>
Eugene Master Traffic Communications Plan
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/12/2010 3:58:50 PM
Creation date
10/12/2010 1:46:04 PM
Metadata
Fields
Template:
PW_Operating
PW_Document_Type_ Operating
Reports
Fiscal_Year
2008
PW_Division
Maintenance
External_View
No
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
74
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
' 5. COMMUNICATIONS DEPLOYMENT ALTERNATIVES ANALYSIS <br />' This section includes a discussion of communications centers, an analysis of the <br />communications network and technology alternatives described in Section 4 for trunk lines and <br />unserved areas, and recommendations. <br />' 5.1 Communications Centers <br />Alternatives were not explored for replacing the Pearl Street hub since Public Works and ISD <br />' staffs agree the best solution is to relocate the hub to the Regional Information System (RIS). <br />As described in Section 2.2.1, RIS houses many of the City's servers in a secure, monitored <br />professional data room and is located less than one block from the Pearl Street facility. All future <br />' traffic servers will be located at RIS. These may include servers for the central traffic signal <br />system (currently located at Roosevelt), video, and a roadway weather information system. <br />Regardless of the communications technology used, Public Works has identified a need for a <br />1 new camera control server at RIS so that multiple camera images may be viewed at one time by <br />City staff at more than one location. A new camera control server will also support video image <br />sharing with other agencies, the media, and the traveling public. <br />' The Roosevelt Boulevard facility will remain a secondary communications center since the City <br />is confident that the Public Works Department will be located at this facility for many years to <br />' come. <br />5.2 Trunk Line Alternatives <br />1 Twisted pair copper cable and fiber optic cable are the two alternatives considered for the City's <br />trunk line corridors, which make up the backbone of the communications network. The following <br />corridors were identified as trunk lines: <br />' ■ Highway 99 ■ 6` Avenue <br />■ River Road ■ Franklin Boulevard <br />■ Coburg Road ■ Willamette Street/Amazon Parkway <br />' ■ 11` "Avenue <br />These corridors carry high volumes of traffic, have numerous interconnected traffic signals <br />today, and will include the installation of ITS devices, particularly CCTV cameras, in the future. <br />Other key corridors within the City are operated by ODOT (Beltline Highway and 1 -105) and <br />Lane County (Delta Highway). It is anticipated that these other agencies will install trunk line <br />communications infrastructure on their corridors in the future that will become an integral part of <br />' the regional communications backbone. <br />Table 7 includes a comparison of twisted pair copper cable (Alternative 1) and fiber optic cable <br />(Alternative 2) that considers feasibility, advantages, and disadvantages. Since FSK over <br />copper does not support higher bandwidth requirements, only Ethernet over copper was <br />considered for use in Alternative 1. Alternative 2 explores the use of Ethernet over fiber optic <br />' cable to support multiple transmission paths for data and video and to reduce the number of <br />fiber optic cables that would be required using analog transmissions. <br /> II <br />1 <br />' DKS Associates Eugene Master Traffic Communications Plan March 2008 <br />Page 26 <br />
The URL can be used to link to this page
Your browser does not support the video tag.