Chapter 15 Intelligent Transportation Systems

Transcription

1 Chapter 15 Intelligent Transportation Systems Intelligent Transportation Systems (ITS) are the integration of advanced communications technologies into the transportation infrastructure and in vehicles in order to improve transportation safety and mobility. ITS includes a broad range of wireless and wire line communications-based information and electronics technologies. ITS Implementation Examples of different ITS tools currently being deployed and utilized in the Richmond Region are defined as follows: Closed-Circuit Cameras: Video cameras that are used to monitor traffic at accidentprone areas for accidents, traffic conditions, breakdowns, and assisting in rerouting traffic away from congestion. They improve emergency response and breakdown assistance through reduction in delays. Changeable Message Signs: Electronic road signs, both portable and fixed, that display changeable messages. The signs are controlled remotely from the Traffic Operations Center and messages are changed to give real-time information to motorists. These signs are used in emergency situations to notify motorists already on the road of upcoming incidents, delays, road work, and suggest alternative routes. I-64 Message Sign: Courtesy of VDOT Traffic Signal Systems: Computerized control systems that enable traffic signal timing to be adjusted based on traffic conditions within the corridor. They optimize traffic flow, help avoid repeated stops along the same roadway, and reduce accidents. Emergency Vehicle Pre-emption Devices: Devices carried on ambulances, fire trucks, and other emergency vehicles which work with comparably equipped traffic signals throughout the Richmond Region. These devices enable traffic signals to automatically change (i.e. change to/or extend green time) so that emergency vehicles will have safe and speedy passage through intersections. Using the devices improves both safety and response time in emergency events as well as reduces response-related accidents. Chapter 15 Intelligent Transportation Systems 15-1

2 EZPass: An automated toll system using pre-paid electronic passes for frequent toll users of the Downtown Expressway, Powhite Parkway, Pocahontas Parkway, and other toll roads found throughout the state. Motorists may travel through special lanes equipped with EZPass detectors to subtract toll fares, continuing the flow of traffic but still have the option to travel through toll plazas where such lanes are not installed. This keeps traffic flowing through, reducing delays and congestion while improving safety for motorists Courtesy of VDOT and toll facility employees. Traffic Incident Management (TIM) Program: Designed to reduced incident durations and secondary accidents, and improve response and clearance times. Clearing roadway incidents requires the coordinated efforts of several entities. TIM sets in place a planned, coordinated approach to detect and remove incidents and restore traffic capacity safely and quickly. Using TIM decreases incident duration through improved detection, response, clearance, and motorist information. It also reduces delays and congestion, and improves accident survival rates and air quality. Roadway Sensors: Sensors embedded in or near roadways to either monitor traffic or environmental (weather) conditions. Some sensors monitor speed and volume of traffic. Other sensors detect precipitation and monitor temperatures on certain bridges and roadways in the Richmond Region. By comparing real-time traffic data to historical data, the sensors help identify abnormal congestion and roadway conditions. The environmental sensors also help quickly identify roadway pavements experiencing freezing temperatures so the Traffic Operations Center can dispatch crews and prevent unsafe conditions, ensuring the safety of motorists. Automatic Vehicle Location: A vehicle-tracking system currently implemented through GRTC to monitor transit vehicle locations. The system provides real-time location of transit, emergency, and other vehicles. Benefits include helping keep buses on schedule, maintain transfer times, improves incident response strategy, and may be used to monitor traffic congestion. Highway Advisory Radio: VDOT communication system broadcasting in the Richmond Region on 1620 AM, providing the public with information on emergency highway and bridge traffic conditions. Local tourism messages are also broadcast during times of non-emergency. The messages enables drivers to adjust travel plans and choose routes based on traffic conditions, helping overall traffic flow. #77 Cellular Call-In Program: Dedicated phone number for reporting roadway emergencies to the Virginia State Police, allowing motorists with cell phones an easy method to report accidents and incidents, assisting in timely incident detection and speed emergency response Chapter 15 Intelligent Transportation Systems

3 Central Region ITS Architecture The Virginia Department of Transportation designated the Richmond Region under the Central Region ITS Architecture, a blueprint for the deployment of ITS in the region. The Architecture is a living document that changes and evolves as ITS projects in the region are implemented; plans and priorities change, and needs and services evolve. The Architecture serves as a planning tool for current and future ITS projects by identifying possible data sources and links needed for deployment and operations. It provides guidance and information for initial stages of projects, focusing on integration of systems to gain the maximum benefit of each system s information and capabilities across the transportation network. Stakeholders utilize the Architecture to define what needs to be in place to address needs and issues in the transportation network. ITS projects both short term and long term as well as the initial stages of project deployment are supported by the Central Region ITS Architecture, providing assistance in development to implementation and monitoring. The components of the Architecture are available in various forms including the VDOT website, in documents, and an associated database. The database in particular holds the key components of the Architecture, formatted in Microsoft Access and created in Turbo Architecture software. According to the United State Department of Transportation (USDOT), an ITS architecture must include at a minimum the following components: 1. Description of the region 2. Identification of the participating agencies and stakeholders 3. Operational concept that identifies roles and responsibilities of stakeholders 4. Any agreements required for operations 5. System functional requirements at a high level 6. Interface requirements and information exchanges with planned and existing systems and subsystems 7. Identification of ITS standards supporting regional and national interoperability 8. Sequence of projects required for implementation 9. Procedures and responsibilities for maintaining the architecture The transportation planning processes involved with ITS projects can be categorized into three types and vary in how projects are funded as well as requirements and deliverables as a result of each process: 1. Local/Transit Agency Planning Process 2. Commonwealth of Virginia Planning Process 3. MPO Planning Process In June 2009, VDOT released for the Central Region ITS Architecture two documents for maintenance and implementation. The maintenance plan describes responsibility for Chapter 15 Intelligent Transportation Systems 15-3

4 maintaining the architecture and the time table for maintenance with the VDOT Richmond Office serving as the lead for maintaining the Architecture currently. Based on the requirements listed by USDOT, the Central Region ITS Architecture includes: A description of the region covered List of ITS stakeholders Inventory of ITS elements List of ITS services and elements involved Functional requirements of key elements Interfaces between elements (interconnects and architecture flows) Applicable ITS standards Agreements required for deployment The maintenance plan reviews procedures for modifying the architecture for periodic project-related revisions and more substantial updates including how changes are identified, requested, reviewed, and implemented as well as a timeline for when changes will be released. Any ITS stakeholder in Virginia can propose a change to the architecture following a review process with VDOT and other ITS stakeholders. The implementation plan provides information on how to approach integrating the Central Region ITS Architecture into transportation planning and defining projects that will address the transportation needs. It assists in identifying projects in the Architecture that are to be planned and deployed with the goal of supporting effective and efficient deployment of ITS in the region. Shown on Map 15-1 are the locations of the existing ITS infrastructure currently maintained by VDOT for the Central Region District including closed circuit television cameras, road weather information stations, highway radio advisory towers, highway radio coverage areas, and variable message boards. Most of the infrastructure is centered on the Richmond Region as it serves as a key intersection for I-295, I-95, and I Chapter 15 Intelligent Transportation Systems

5 Map 15-1: VDOT Central Region Architecture Chapter 15 Intelligent Transportation Systems 15-5

6 Richmond Region ITS Work Group The MPO took action at its July 21, 2004 meeting to accept the Richmond Regional ITS Architecture Report and the Richmond Regional ITS Architecture Deployment Plan Report. The ITS Architecture Report identifies the region s framework for institutional agreements and technical integration of ITS. It defines the pieces of the region s systems (e.g., traffic signal operations, freeway management, emergency management, public transit operations, etc.) and the information exchanged between them. The ITS Architecture Deployment Plan outlines the vision for ITS deployment and identifies and prioritizes projects and market packages that are needed to implement the ITS architecture of a high, medium, and low priority basis. It helps to prioritize funding decisions by having a comprehensive shared approach to regional ITS programs so that the infrastructure can be incrementally built out over a 20-year time horizon and allow integration among key foundations of the system as it grows and expands. As part of the MPO s July 21, 2004 action on ITS, the MPO s Technical Advisory Committee (TAC) was designated with conducting annual reviews of these documents with VDOT providing technical assistance of these services and with TAC and RRPDC staff reporting on the implementation status of ITS projects and providing recommendations for updates and/or changes to the region s ITS architecture report and deployment plan. It was recommended that such reviews be conducted at the January TAC meeting and the MPO took further action to direct that it be provided with an annual report on ITS applications and implementation including the status of ITS projects, funding, and new technologies based on work by VDOT staff to prepare proposed projects for consideration in the upcoming VDOT Six-Year Improvement Plan. Note that due to staffing issues and work priorities, staff did not follow-up on the MPO s 2004 action and VDOT maintained and conducted ITS-related planning activities. The RRPDC was advised by VDOT in late March 2009 that the Richmond Regional ITS Architecture Deployment Plan Report had been updated. Staff had received the Virginia Central Region ITS Architecture Implementation Plan, Version 1.0 and the Virginia Central Region ITS Architecture Maintenance Plan, Version 1.0 dated June 2009 and held meetings with VDOT staff in September 2009 to discuss the MPO s role in ITS architecture and formation of a regional ITS technical workgroup. Presentations were given by VDOT and RRPDC staffs at the July 16, 2009 and September 17, 2009 TAC meetings, with staff s initial recommendation to establish an ITS TAC resource and work group. Staff also conducted several visits to an ITS/Highway Safety work group in Hampton Roads. At the February 18, 2010 TAC meeting, staff presented a proposal for the establishment of a Richmond Region ITS/TAC work group composed of local government planners and traffic operations engineers, and staff from VDOT, FHWA, GRTC, RMA, CRAC, VDRPT and RideFinders. The establishment of a Richmond Region ITS/TAC work group was discussed 15-6 Chapter 15 Intelligent Transportation Systems

7 again at the March 22, 2011 CTAC meeting as part of a presentation on the status of ITS in the region, prompting a new proposal and review of additional members. The MPO took action at its June 9, 2011 meeting to establish the Richmond Region ITS Work Group under the MPO s Technical Advisory Committee (TAC) to provide planning and programming support and assistance for TAC on ITS related matters, with work group members appointed by TAC members (for their respective jurisdictions/agencies) and with representatives from the Crater Planning district Commission and the FHWA Virginia Division office, and with the direction that the work group s duties and responsibilities are subject to TAC review, consideration and action. The primary responsibilities for the ITS/TAC work group are as follows: 1. Provide a regional forum for discussion of ITS related issues, projects, plans and programs. 2. Facilitate and promote use and maintenance of the VDOT Central Region ITS Architecture. 3. Promote and assist in integrating the ITS architecture into the regional planning process. 4. Provide recommendations to TAC on ITS projects, programs and services for development and/or funding consideration. The TAC ITS Work Group as designated by the MPO consists of the following: Virginia Department of Transportation (VDOT) Federal Highway Administration (FHWA) Greater Richmond Transit Company (GRTC) Richmond Metropolitan Authority (RMA) Capital Region Airport Commission (CRAC) Virginia Department of Rail and Public Transportation (DRPT) RideFinders Richmond Regional Planning District Commission Crater Planning District Commission Local Jurisdictions Chapter 15 Intelligent Transportation Systems 15-7

8 Richmond Region ITS Inventory As one of the Richmond Region ITS Work Group s initial tasks, development began on a preliminary version of all current ITS infrastructure deployed in the Richmond Region The inventory serves as a useful planning tool to supplement information from the VDOT Central Region ITS Architecture and provides reference information for other jurisdictions in the Richmond Region of current infrastructure and possible connections to future or multijurisdictional projects. Provided below are the inventory lists based on the type of infrastructure. Figure 15-1: VDOT Highway Advisory Radio Locations Route Mile Post Lane Description Ashland Exit 92 I-95 SB 92 I EB Exit 167 I EB/WB Exit 205 Truck Weigh 36 I-95 NB Scales I NB/SB Exit 61 Figure 15-2: VDOT Dynamic Message Sign Locations Route Direction Mile Marker Description Latitude Longitude I-295 SB 36.1 DMS I-295 NB 39.6 DMS I-64 EB DMS I-64 EB 182 DMS I-64 WB DMS I-64 WB 207 DMS I-85 NB 60.3 DMS I-95 NB 41.9 DMS I-95 NB 46 DMS I-95 NB 59.3 DMS I-95 NB 66.1 DMS I-95 SB 81.3 DMS I-95 SB 89 DMS I-95 SB 94.3 DMS I-95 NB 100 DMS 15-8 Chapter 15 Intelligent Transportation Systems

9 Figure 15-3: VDOT Weather Station Locations Station Latitude Longitude Altitude 288 at I64 Goochland ft. Rt. 58 Bypass Clarksville ft. I-295 at Varina-Enon Bridge ft. I-295 at Woodman Rd ft. I-85 at Rt. 1 Brunswick County ft I-95 at Appomattox River Bridge ft. I-95 at Falling Creek ft. I-95 over James River ft. Meadow Rd. over I ft. Rt. 150 Willey Bridge ft. Figure 15-4: Hanover County Dual-Sided Flashing Alert Sign Locations Location Description RT 33 and RT 54 Intersection Sliding Hill Road at Atlee Station Road Intersection US 360 Near Bell Creek Road-Eastbound US 360 Near Colony Drive-Westbound RT 301 Near Rural Point Road, New Ashcake Road Intersection Creighton Road Near Cold Harbor Road Courthouse Area Near RT 301/RT 54 intersection US 1 Near Town Limits South of Town Trainham Road and Beaverdam Road in Village US 1 Near RT 30 RT 33 Near Ashland Road U.S. Rt. 360 Near Intersection with Walnut Grove Road Northwest Corner of the Intersection of Green Bay and Tyler Station Roads Ashland - Intersection of Rt. 54 and U.S. Rt. 1 Chapter 15 Intelligent Transportation Systems 15-9

10 Figure 15-5: VDOT Closed Circuit Television Cameras Locations Route Direction Mile Marker Description I-64 EB I-64 at Staples Mill Exit (MM 185.2) I-64 EB 184 I-64 at Broad St./Glenside Dr. (MM 184) I-64 EB 179 I-64 at Broad St./Short Pump Exit (MM 179) I-64 WB 177 I-64 at I-295 West End I-64 EB 200 I-64 at I-295 East of Richmond (Exit 200) I-64 WB I-64 at Mechanicsville Tnpk. I-95 NB 62.8 I-95 at Route 288 I-95 NB 84 I-95 at I-295 (Exit 84) I-95 NB 86 I-95 at Sliding Hill Rd. (Exit 86) I-95 NB 66 I-95 north of Willis Rd. (Exit 64) I-64 WB 192 I-64 west of exit 192 (Shockoe Valley Bridge) I-95 NB 73 I-95 south of Maury St. (Exit 73) I-95 SB 54 I-95 at Temple Ave. (Exit 54) I-95 NB 79 I-95 south of Hermitage Rd. (Exit 80) I-95 SB 74 I-95 at Franklin St. (Exit 74B) I-95 NB 75 I-95 at I-64 East (Exit 75) I-95 NB 76 I-95 at First St. (Exit 76A) I-95 SB 76 I-95 at Belvidere St. (Exit 76B) I-95 SB 77.4 I-95 north of Lombardy St. (Mile 77.4) I-95 SB 78 I-95 at Boulevard (Exit 78) I-95 SB 78.8 I-95 at I-64 West (Exit 79) I-95 SB 91.7 I-95 at Route 54 (Exit 92) I-95 SB 53 I-95 at Southpark Blvd. (Exit 53) I-95 NB 51.5 I-95 N at I-85 I-95 SB 61.4 I-95 at Rte.10 I-95 NB 89.1 I-95 N just South of Lewistown Rd 288 SB 1 Rte.288 S North of Rte 1 I-64 EB 195 I-64 E at Laburnum Ave (Exit 195) I-195 NB 3.1 I-195 N at Laburnum I-195 NB 2.2 I-195 at Bland St I-95 SB 69 I-95 at Bells Road I-64 EB 75 I-64 EB at Rt 288 I-95 SB 98 I-95 SB at Rt Chapter 15 Intelligent Transportation Systems

11 Figure 15-6: VDOT Traffic Counter Locations Route Site Location Jurisdiction Name MI S HOPKINS RD. Richmond MI E FOREST RD. Henrico MI E FOREST RD. Henrico MI E RAMP FR I-295 Chesterfield MI E RAMP FR I-295 Chesterfield MI E HERMITAGE RD. Henrico MI W WISTAR RD. Henrico MI E STAPLES MILL RD. (ON BROAD ST.) Richmond MI E STAPLES MILL RD (ON BROAD ST.) Richmond MI E JOHNSTON WILLIS DRIVE Chesterfield MI W ROBIOUS RD. Chesterfield MI. W RTE 156 SB Henrico MI E RAMP FR SR 33/ SR 249 New Kent MI E RAMP FR LABURNUM Henrico MI E RAMP FR GASKINS Henrico MI E RAMP TO GASKINS Henrico MI W RAMP FR RTE 156 (AIRPORT DR.) Henrico 64 BETWEEN EXIT 211 (TALLEYSVILLE) AND EXIT 205 New Kent MI E RTE 60 RAMP Chesterfield MI W RAMP FR JAHNKE RD. Chesterfield MI N RAMP FR RTE 656 Hanover MI N RAMP FR RTE 301 Henrico MI N RAMP FR TEMPLE AVE Chesterfield MI N DEEPWATER TERMINAL UNDERPASS Richmond MI N RAMP FR RTE 301 (BELVIDERE-NEAR DIAMOND) Richmond MI S RAMP FR RTE 802 Hanover MI S RAMP FR RTE 73 (PARHAM RD.) Henrico MI S ROBIN HOOD RD. Richmond MI S RAMP TO EXIT 73 Richmond MI S RAMP FR RTE 746/620 Chesterfield MI E RTE 1601 (DALEBROOK DR) Chesterfield M W DALEBROOK DR. (N) Chesterfield MI N RTE 76 Richmond MI N CANAL STREET Richmond MI S RAMP TO GROVE AVE. Richmond MI. S HARRISON ST. Richmond 288 North of Chesterfield County Line Powhatan MI S OF JAMES RIVER BRIDGE Powhatan MI S I-64 EB (GORE) Goochland MI N RAMP FR RTE 10 Chesterfield MI S RAMP FR COURTHOUSE RD. Chesterfield MI S RTE 250 Goochland MI S OF RTE 250 Goochland Chapter 15 Intelligent Transportation Systems 15-11

12 Route Site Location Jurisdiction Name MI E RAMP FR RTE 33 Henrico MI E RAMP FR RTE 627 Hanover MI W RAMP FR RTE 360 Hanover MI W RAMP FR WOODMAN Henrico MI E RTE 360BUS Hanover MI E RTE 360 BUS Hanover MI W RTE 646 Richmond MI E MIDLOTHIAN TURNPIKE Richmond MI N ACKLEY AVENUE Henrico MI S. WOODMAN RD. Henrico MI FR HUNTERS MILL DR. Henrico MI S US 60 Chesterfield 288 Chesterfield EXIT 152 Goochland 64 I-64 RAMP TO SR 33 Henrico 64 I-64 EAST MM Henrico 64 I-64 EAST WELCOME CENTER RAMP New Kent 64 I-64 MM 217 New Kent 64 I MI FROM FAIRFIELD AVE Henrico 64 I-64 EXIT 200 Henrico 64 I-64 EXIT 214 New Kent 64 I-64 I-295 SHORT PUMP Henrico 64 I-64 MM 179 Henrico 64 I-64 MM 199 Henrico 64 I-64 WEST 0.43 MI FROM MASONIC LN Henrico 64 I-64 WEST EXIT 148 Goochland 64 I-64 West MM Goochland 64 I-64 West MM Goochland 64 I-64 West MM Goochland 64 I-64 WEST MM 182 Henrico 64 I-64 WEST MM 191 Richmond 64 I-64 WEST WELCOME CENTER RAMP New Kent 95 AT GORE MAURY ST RAMPS TO I-95 S AND I-95 N Richmond 95 I-95 N MM 74 Richmond 95 I-95 EXIT 73 Richmond 95 I-95 EXIT 75 Richmond 95 I-95 EXIT 75 Richmond 95 I-95 RAMP FROM I-295 WEST Henrico 95 I-95 RUFFIN MILL VMS SIGN Chesterfield 95 I-95 NORTH MM 96.6 Hanover 95 I-95 NORTH MM 96.6 Hanover 95 I-95 NORTH RAMP TO SR 288 WEST Chesterfield 95 I-95 NORTH BELVIDERE ST. Richmond 95 I-95 NORTH MM75 Richmond 95 I-95 HERMITAGE RD OVERPASS Henrico 95 I CCS SITE Richmond Chapter 15 Intelligent Transportation Systems

13 Route Site Location Jurisdiction Name 95 I-95 EXIT 92 Hanover 95 I-95 MM 67 Chesterfield 95 I-95 MM 81.2 Henrico 95 I-95 RAMP TO I-295 EAST Henrico 95 I-95 SB RAMP FROM WILLIS RD Chesterfield 95 I-95 SCOTT RD OVERPASS Henrico 95 I-95 South Exit 69 Richmond 95 I-95 South Exit 69 Richmond 95 I-95 SOUTH MM 80 Richmond 95 I-95 SOUTH SHOULDER AT MM78 Richmond 195 I-195 North Cary St Exit Richmond 295 I-295 EXIT 28 Henrico 295 I-295 EXIT 43D Henrico 295 I-295 I-95 SOUTH RAMP MERGE Henrico 295 I-295 EAST COLLECTOR I-64 Henrico 295 I-295 EAST MM 44 Henrico 295 I-295 East MM 52 Henrico 295 I-295 EAST;SOUTH OF SR 895 Henrico 295 I-295 MM 29 Henrico 295 I-295 MM 29 Henrico 295 I-295 MM 31 Henrico 295 I-295 MM 31 Hanover 295 I-295 MM 50 Henrico 295 I-295 MM 50 Henrico 295 I-295 MM 20 Henrico 295 I-295 NORTH MM 36 Hanover 295 I-295 NORTH MM 39 Hanover 295 I-295 MM 36 Hanover 295 I-295 SOUTH RAMP TO SR 895 WEST Henrico 295 I-295 SOUTH MM 10 Henrico 295 I-295 RAMP TO I-95 NORTH Henrico 295 I-295 WEST COLLECTOR I-64 Henrico 295 I-295 WEST COLLECTOR I-95 Henrico 295 I-295 WEST MM 44 Henrico 295 I-295 West MM 52 Henrico Chapter 15 Intelligent Transportation Systems 15-13

14