My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
ORANGE COUNTY TRANSPORTATION AUTHORITY (5) - 2013
Clerk
>
Contracts / Agreements
>
O
>
ORANGE COUNTY TRANSPORTATION AUTHORITY (OCTA)
>
ORANGE COUNTY TRANSPORTATION AUTHORITY (5) - 2013
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/31/2021 10:14:57 AM
Creation date
2/27/2013 10:42:57 AM
Metadata
Fields
Template:
Contracts
Company Name
ORANGE COUNTY TRANSPORTATION AUTHORITY
Contract #
A-2013-021
Agency
PUBLIC WORKS
Council Approval Date
1/22/2013
Destruction Year
0
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
80
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).
View images
View plain text
COOPERATIVE AGREEMENT NO. C-2-2030 <br />ATTACHMENT A <br />segments for the 'Before' and 'After' runs. CONSULTANT shall notify and receive <br />approval from APM on number of runs and segments to be accomplished. <br />Project travel -time data will be collected using the floating car method, a laptop <br />computer, a GPS receiver unit, and Tru-Traffic v 10.0, only. <br />The report shall address likely optimization strategies for signal synchronization, <br />specifically focusing on how to consider PROJECT optimization: end — to — end vs. <br />coordinated zones. Ideally, the analysis should include the floating car data and data <br />collected as part of Task 2. However draft versions of the report can include previously <br />collected traffic, travel time, or other data, if considered relevant and available. The <br />evaluation report shall provide a very good understanding of traffic patterns on <br />PROJECT throughout the weekdays and throughout the weekend. Tru-Traffic Version <br />10.0 has the OCTA Corridor Synchronization Performance Index (CSPI) Calculation <br />formulas available for use as well as the calculations for the latest emissions for GHG <br />and other MOEs. These functions shall be utilized by the CONSULTANT in the draft <br />preliminary, draft final and final reports as specified herein. <br />The CONSULTANT shall perform due diligence with regard to existing and proposed <br />timing operations on arterials that intersect with the PROJECT. <br />CONSULTANT shall prepare a memorandum and present the findings to the Authority <br />outlining the findings of the 'Before' field study. The Authority may request a <br />presentation on the traffic patterns on PROJECT Scope and possible synchronization <br />strategies to address the traffic patterns (optimizing the fill corridor versus optimizing <br />segments identified with natural traffic breaks) to provide direction on the preferred <br />signal timing strategy. Any requested presentation shall include as much of the turning <br />movement, 24-hour machine counts, travel time, earlier city counts, etc. as available. <br />CONSULTANT shall finalize the memorandum based on comments received from the <br />Authority Project Manager and other involved AGENCIES and after incorporating the full <br />set of data collected by CONSULTANT as part of Task 2. <br />Deliverables — Task 4: <br />A memorandum documenting the results of the 'Before' study is to be distributed to the <br />APM and AGENCIES as a discussion item. More detailed analysis of project results <br />shall be included in Task 8: Project Report. <br />1. Electronic versions of all data files and memorandum to all PARTIES and <br />AGENCIES. <br />Task 5: Signal Timing Optimization and Implementation <br />CONSULTANT shall work with the APM and AGENCIES to develop a model of the <br />study area and calibrate the model based on field observations of existing conditions. <br />Signal synchronization optimization shall be conducted in Synchro 8.0. The corridor <br />model must be consistent with all aspects and seamlessly interface and interlace with <br />F:3 <br />
The URL can be used to link to this page
Your browser does not support the video tag.