Intelligent Transportation Systems - City of Oakland

More documents

Recommendations

Info

• Institute of Electrical and Electronics Engineers (IEEE); • Institute of Transportation Engineers (ITE); • National Electrical Manufacturers Association (NEMA); • National Transportation Communications for ITS Protocol Joint Committee (NTCIP); and • Society of Automotive Engineers (SAE). Within the National Architecture, specific national standards developed by these organizations are associated with each data flow. As specific project architectures are developed for each City ITS project, it is important that the City document all of the relevant ITS standards for that project so that they can be considered during the project design. The national ITS standards are in various stages of development, testing, and formalization. As appropriate standards are finalized and published, these standards should be incorporated into City of Oakland ITS projects to the extent possible. To be eligible for federal funding for ITS projects, conformance with the National ITS Architecture as well as use of USDOT adopted ITS standards (where applicable) are required. The USDOT ITS standards web site (www.ITS-Standards.net) is a good source of current information on the status of each standard and how they can be obtained. 5.4.2 Architecture Development Process As the City of Oakland moves forward with future ITS projects, they will be expected to develop project architectures for all ITS projects that receive federal funding. One tool that can assist with the development of project architectures is Turbo Architecture. Turbo Architecture is a “high level, interactive software program that aids transportation planners and system integrators, both in the public and private sectors, in the development of a Regional and/or Project Architecture.” The resulting architecture is in a Microsoft Access database-compatible file that can be easily utilized in the future to further enhance and modify this first version. The architecture development process used in Turbo Architecture basically involves four major steps: • Project Inventory • Market Packages • Interconnects • Standards The first step is to develop a project inventory. The inventory consists of the physical entities, including agencies, vehicles, systems and field elements that are involved in the project. The inventory includes both existing and planned components. The next step is to determine the applicable market packages for the project. A market package is a group of technologies and data flows based on functionality. Each market package represents a function that can be deployed as an integrated capability. Many market packages can be deployed incrementally so advanced packages can be efficiently implemented based on earlier deployments. The market package selection process is typically performed after an inventory has been created. National ITS City of Oakland ITS Strategic Plan 62 September, 2003
Architecture Version 3.0 includes 63 Market Packages, which are listed in Table 5-1. From this list, relevant market packages are selected to ensure that the architecture meets the all of the project requirements. Table 5-1 – National ITS Architecture Market Packages Market Package ad1 ad2 ad3 apts1 apts2 apts3 apts4 apts5 apts6 apts7 apts8 atis1 atis2 atis3 atis4 atis5 atis6 atis7 atis8 atis9 atms01 atms02 atms03 atms04 atms05 atms06 atms07 atms08 atms09 atms10 atms11 atms12 atms13 atms14 atms15 atms16 atms17 atms18 atms19 avss01 avss02 avss03 avss04 avss05 Market Package Name ITS Data Mart ITS Data Warehouse ITS Virtual Data Warehouse Transit Vehicle Tracking Transit Fixed-Route Operations Demand Response Transit Operations Transit Passenger and Fare Management Transit Security Transit Maintenance Multi-modal Coordination Transit Traveler Information Broadcast Traveler Information Interactive Traveler Information Autonomous Route Guidance Dynamic Route Guidance ISP Based Route Guidance Integrated Transportation Management/Route Guidance Yellow Pages and Reservation Dynamic Ridesharing In Vehicle Signing Network Surveillance Probe Surveillance Surface Street Control Freeway Control HOV Lane Management Traffic Information Dissemination Regional Traffic Control Incident Management System Traffic Forecast and Demand Management Electronic Toll Collection Emissions Monitoring and Management Virtual TMC and Smart Probe Data Standard Railroad Grade Crossing Advanced Railroad Grade Crossing Railroad Operations Coordination Parking Facility Management Reversible Lane Management Road Weather Information System Regional Parking Management Vehicle Safety Monitoring Driver Safety Monitoring Longitudinal Safety Warning Lateral Safety Warning Intersection Safety Warning City of Oakland ITS Strategic Plan 63 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 and 34: agencies such as AC Transit and BAR
Page 35 and 36: In addition to selecting a signal s
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: 5.4 ARCHITECTURE RECOMMENDATIONS As
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 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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?