Intelligent Transportation Systems - City of Oakland

More documents

Recommendations

Info

SIGNAL SYSTEM COSTS (Order of Magnitude only; depends on desired features) CONTROLLER TYPES (Base options – existing integrated controllers) TABLE 3.3 - SIGNAL SYSTEM EVALUATION ITS FUNCTIONS STRENGTHS INSTALLATION HISTORY NTCIP COMPLIANCE (Maturity Level) BI Tran QuicNet (McCain) $15,000 (server) $150,000 for Base System • Type 170 • Type 2070 • McCain Vector (NEMA) • Capability for ATMS functional integration • Traffic adaptive • DMS/CCTV integration capability • Mature system • Extensive deployment history • Capable of interfacing with 170/2070 and McCain NEMA controllers • Currently used on San Pablo Avenue as part of SMART Corridors Program • Medium Eagle Actra $25,000 (server) $100,000 for Base System • Eagle EPAC300 (NEMA) • Eagle EPIC140 (NEMA) • 2070 with EPAC firmware • Capability for ATMS functional integration • Traffic adaptive • DMS/CCTV integration capability • Backed by Siemens and Eagle • Long history of traffic control system • Traffic adaptive SCOOT (Split Cycle Offset Optimization Technique) interface • Limited systems in Bay Area • Medium Econolite Aries $10,000 (server) $25,000 for Base System • Econolite ASC/2 (NEMA) • Limited • Inexpensive • Simple to use • Limited in expandability • Not an open architecture • Low Econolite/ Siemens/ Gardner Systems Icons $15,000 (server) $150,000 for Base System • Econolite ASC/2 (NEMA) • Type 2070 with Next Phase firmware • Traconex • Capability for ATMS functional integration • Traffic adaptive • DMS/CCTV integration capability • Traffic adaptive Rhodes interface • Limited systems in place • High Econolite Pyramids $15,000 (server) $150,000 for Base System • Type 170 with Wapiti firmware • Type 2070 with Oasis firmware • Capability for ATMS functional integration • CCTV integration capability • Incident Management module • Modular architecture allows features and functions to be added as desired • Limited systems in use • Medium Naztec Streetwise $15,000 (server) $150,000 for Base System • Naztec 980, 981 (NEMA) • Type 2070 with Naztec Firmware • Naztec 970 (NEMA for 332/336 cabinet) • Capability for ATMS functional integration • Traffic adaptive under development • DMS/CCTV integration capability • Mature system • Over 10 deployments in the Bay Area • More NTCIP features developed • Currently works with Naztec firmware or controllers only • High City of Oakland ITS Strategic Plan 28 September, 2003
In addition to selecting a signal system, the City can also consider options for replacement of signal controllers. In the Needs Assessment workshop, it was determined that the City is moving towards implementation of Type 170 controllers. Type 170 controllers are based on the State of California’s traffic controller specification, and are already in use with existing BI Tran firmware along San Pablo Avenue and Hegenberger and planned for Broadway. Firmware is simply the vendor-specific software that is installed on a signal controller. To provide additional alternatives for controller selection, the following traffic controllers and software were evaluated: • Type 170 Controller • Type 2070 Controller • Eagle EPAC 300 (NEMA TS2) • McCain Vector (NEMA TS2) • Econolite ASC2 (NEMA TS2) • Naztec 981 and 970 (NEMA TS2) These controllers meet nearly all of the functional requirements developed in Section 3.1. The Type 170 controller is a mature, standardized controller that was initially developed for Caltrans. Type 170 controllers will operate with firmware from many vendors as long as that firmware is compatible with the central signal system. The main disadvantage of the Type 170 controller is that it is not NTCIP compliant. The Type 2070 controller is the newer advanced transportation management controller developed by the State of California, which is currently being adopted at the national level as Advanced Traffic Controller (ATC). A number of different vendors can provide 2070 controllers and these controllers will work with most signal systems. The 2070 controller is NTCIP compliant. The Eagle, McCain, Econolite and Naztec controllers listed above are NEMA type controllers. NEMA controllers come as either TS1 or TS2 standards. These options are discussed in more detail below. Any of these controllers would be viable for citywide implementation in Oakland, provided that the signal controllers can communicate with the central signal system. The different systems are compared in terms of controller types, ITS functions, main strengths and weaknesses, NTCIP compliance and costs below in Table 3.4. This comparison is based on subjective analysis of the controller history, performance and references and other information that identified the performance and capabilities of the controller type. City of Oakland ITS Strategic Plan 29 September, 2003
Page 1 and 2: Citywide ITS Strategic Plan Final R
Page 3 and 4: CITY OF OAKLAND CITYWIDE ITS STRATE
Page 5 and 6: 6.7.3 Long-Term Communications Plan
Page 7 and 8: SECTION 1 Introduction 1.1 PURPOSE
Page 9 and 10: The vision of the Citywide ITS Stra
Page 11 and 12: SIC SMFO SONET SR2S STP TAT TBS TCT
Page 13 and 14: through the thoughtful and effectiv
Page 15 and 16: the downtown area) is time-based. D
Page 17 and 18: Most of the controllers throughout
Page 19 and 20: 2.3.2 Bay Area Regional ITS Archite
Page 21 and 22: • San Pablo Avenue • Telegraph
Page 23 and 24: 2.4.2 Other Oakland Plans The plann
Page 25 and 26: Port of Oakland Airport Roadway Pro
Page 27 and 28: SECTION 3 Signal System As part of
Page 29 and 30: In the Needs Assessment workshop, s
Page 31 and 32: Table 3.2 - High Priority Corridors
Page 33: agencies such as AC Transit and BAR
Page 37 and 38: TS-1 and TS-2 Options In addition t
Page 39 and 40: Alternative 3: Hybrid System A thir
Page 41 and 42: 4.1.2 Traveler Information Requirem
Page 43 and 44: • Cameras mounted with a pan-tilt
Page 45 and 46: These detectors can be installed in
Page 47 and 48: • LED Hybrid - LED hybrid signs j
Page 49 and 50: ecently completed the design of a P
Page 51 and 52: • Full closure or four quadrant r
Page 53 and 54: oute information is typically disse
Page 55 and 56: 4.3.3 Internet Access The Internet
Page 57 and 58: A more sophisticated approach opera
Page 59 and 60: EVP Recommendations - The Oakland F
Page 61 and 62: SECTION 5 High-Level System Archite
Page 63 and 64: These seven user services can be ex
Page 65 and 66: Figure 5.2 - High-Level Center-to-C
Page 67 and 68: 5.4 ARCHITECTURE RECOMMENDATIONS As
Page 69 and 70: Architecture Version 3.0 includes 6
Page 71 and 72: SECTION 6 Communications Network 6.
Page 73 and 74: have an effect on the alternatives
Page 75 and 76: Figure 6.1 - Communications Topolog
Page 77 and 78: • Fault tolerance. If a communica
Page 79 and 80: Table 6.1 - Bandwidth Comparison D
Page 81 and 82: There are three different types of
Page 83 and 84: This same hardwire configuration ca
Page 85 and 86:
August 2003 City of Oakland ITS Str
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
surveillance purposes in the near f
Page 93 and 94:
7.1.3 Communications Infrastructure
Page 95 and 96:
Table 7.1 - TMC Equipment List Cont
Page 97 and 98:
7.3.2 Equipment Room The equipment
Page 99 and 100:
than 5’6” wide by 7’ long. Th
Page 101 and 102:
September 2003 City of Oakland ITS
Page 103 and 104:
o High Street o MacArthur Boulevard
Page 105 and 106:
• The City of Oakland Fire Depart
Page 107 and 108:
8.2 MEDIUM-TERM PROJECTS This secti
Page 109 and 110:
• The City’s Fire Department sh
Page 111 and 112:
8.3 LONG-TERM PROJECTS This section
Page 113 and 114:
73rd Ave Maritime Street 7th St. Ai
Page 115 and 116:
Table 8.2 - Medium-Term Deployment
Page 117 and 118:
SECTION 9 Operations and Management
Page 119 and 120:
Incident Management Systems Safety
Page 121 and 122:
• Signal Technicians - 5.5 FTE Wi
Page 123 and 124:
• Optical Time Domain Reflectomet
Page 125 and 126:
diagnostic equipment, maintain an a
Page 127 and 128:
9.7 O&M COSTS This section provides
Page 129 and 130:
management, etc.) or the integratio
Page 131 and 132:
Lighting Act of 1972, Part 2 of Div
Page 133:
• TEA 21 Funds • ITS Earmark Fu
show all

Intelligent Transportation Systems - City of Oakland

Create successful ePaper yourself

Delete template?

Save as template?