Traffic Projections Clause Samples
The Traffic Projections clause defines the expected volume or flow of data, goods, or users over a specified period within the context of the agreement. Typically, it outlines estimated numbers or ranges, which may be used for planning capacity, setting performance benchmarks, or determining pricing structures. By establishing clear expectations regarding anticipated traffic, this clause helps both parties align resources and manage risk related to over- or under-utilization.
Traffic Projections. Coordinate with others (Segment C Engineer is preparing traffic projections of Segments B-4 and C) as they prepare traffic projections for the opening-year, design-year (opening year +20) and pavement design year (opening year + 30) for the mainlanes, ramps, cross streets, interchanges, intersections, and frontage roads. Utilize the traffic data to prepare the geometric schematic design.
Traffic Projections. Future traffic conditions for the opening year will be developed based on past traffic data. Other planned developments will be included as appropriate, as mutually agreed upon with the City of ▇▇▇ Arbor. The City will be asked to comment on the methodology for the opening year (2015) traffic projections. The number of buses (including UMHS shuttles and line buses) that may use the Intermodal Station will be estimated based on input from AATA and UM Parking & Transportation Services staff. Future trip generation and trip distribution for the parking deck will be based on the traffic characteristics determined from the existing parking lot (M71) and the traffic counts performed at the intersections within the study area. The amount of pick-up and drop-off vehicle activity will be estimated based on previous pick-up and drop-off data collected near the area and the estimated ridership of the rail passenger facility. The pick-up and drop-off activity may be represented by private automobiles and/or taxis. The study area for the traffic analysis will include the intersections listed in the Traffic Data section, including the following roadway segments: ▇▇. ▇▇▇ ▇▇▇▇▇▇ City of ▇▇▇ Arbor ▇▇▇▇▇▇ Road Station PSA Amendment No. 2 SmithGroupJJR No. 50156.001 May 31, 2012 Page 5 • ▇▇▇▇ Avenue between Huron Street and ▇▇▇▇▇▇ Street • ▇▇▇▇▇▇ Road between ▇▇▇▇▇▇ Street and Bonisteel Boulevard • ▇▇▇▇▇▇ Street/Depot Street between ▇▇▇▇ Avenue/▇▇▇▇▇▇ Road and Main Street • Maiden Lane between ▇▇▇▇▇▇ Road and Broadway Street/Plymouth Road • Broadway Street between Summit Street and Maiden Lane The intersection capacity analysis will be conducted for five scenarios: • Existing (2012) • No-build opening year (2015) • Opening year with facility (2015) – ▇▇▇▇▇▇ Road Station site • Opening year with facility (2015) – Amtrak Station site A horizon year analysis is not included as part of this scope of work. The morning and afternoon peak-hour level of service (LOS), vehicle delay, and vehicle queue results will be provided for the intersections listed in the Traffic Data section and presented in tables that compare the scenarios. The methodology of the Highway Capacity Manual (HCM) will be used for the analysis of the signalized and un-signalized intersections, and the traffic signal network will be modeled using Synchro and SimTraffic software. In urbanized areas, LOS D is generally considered acceptable for peak-hour conditions. The intersections that do not meet LOS D will be e...
Traffic Projections. 4.1. Develop background turning movement traffic projections at the study intersections for the following peak hours:
a. Weekday AM peak hour b. Weekday PM peak hour c. Weekend peak hour
4.2. Calculate the number of estimated trips destined to/from the event each day, including passenger vehicle trips to/from parking location and shuttle trips to/from the event space.
4.3. Assign event trips to a transportation mode. Determine the distribution percentages of event vehicular traffic to each project intersection.
Traffic Projections. The WSB team will complete traffic projections for year of opening, 10 years out and 20 years out for each of the intersections to be counted. Draft projections will be provided for review and comment. Future volumes will be based on planned development and historic growth rates. The regional model will not be used.
Traffic Projections. The CONSULTANT, in accordance with Procedure 525-030- 120, “Design Traffic Procedure”, may be required to estimate future design hour and design peak hour traffic volumes using travel demand models (FSUTMS), historical traffic growth, land use data or other appropriate traffic forecasting methodologies defined by the DEPARTMENT.
Traffic Projections. The Engineer shall utilize the traffic volume data collected in Task
Traffic Projections. (a) The Licensee shall submit annual cargo-wise traffic projections to the Licensor.
(b) The Licensee shall submit monthly reports on actual cargo-wise traffic and annual variance of actual traffic against annual projections and estimates envisaged in the Approved DPRs.
Traffic Projections. The determination of future traffic has been accomplished using the Florida Standard Urban Transportation Model Structure and the Northeast Regional Planning Model (NERPM) Version 4.2 network and socio-economic data. The model base year is 2005 and the design year is 2035. Model network has also been developed for interim years 2015 and 2025. Socio-economic data has also been developed for each year from 2010 to 2035. The basis of the transportation network data was the 2015 model for the Phase IV analysis. The First Coast TPO master project list was reviewed to ensure only the network that is projected to be in place in 2020 is used. For Phase IV, the 2015 network was used with the following specific modifications discussed at the methodology meeting and follow-up correspondence:
Traffic Projections. Existing and projected traffic volumes for the project corridor(s) are required for the short-, mid-, and long-term designs. The ENGINEER shall provide the following: Meetings/Teleconferences - The ENGINEER shall participate in working meetings or teleconferences with the STATE, the Transportation Planning and Programming Division of TxDOT (TPP), and other pertinent agencies. The first meeting shall be the kickoff meeting to verify the project schedule, points of contact, study methodology including definition of required analysis scenarios and necessary analysis to be conducted, data sources, traffic factors, DocuSign Envelope ID: 9E4E3B84-8519-409C-AEF8-0383FB0D2E89 development of design traffic volumes, and documentation required to address project specific criteria required by the STATE; (up to 5 meetings) The ENGINEER shall prepare meeting notes and the decisions regarding the study design process and proposed methodology shall be documented in a preliminary meeting memorandum and submitted for review and approval by the STATE; Methodology Development - The ENGINEER shall develop a proposed methodology for estimating traffic projections for each component of the project corridor; (Submit paperwork request for TPP (2124 Form and maps, etc.) The ENGINEER shall review the methodology with the STATE. Based on these discussions, the ENGINEER shall address comments and incorporate revisions, as necessary, to the methodology; The ENGINEER shall submit a memorandum outlining the final methodology for estimating traffic projections for the State’s review and approval; Existing Traffic Counts and Data Review - The ENGINEER shall review necessary project related traffic data provided by the STATE. This data shall consist of traffic volume counts, corridor or study area historical count year data from permanent count stations, vehicle classification data and historical truck data; The ENGINEER shall submit an Existing Traffic Report detailing the findings. In addition the ENGINEER shall provide the existing traffic numbers on the stick diagram. The report and stick diagrams shall be submitted to the STATE for review and approval;