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 />the County Wide Synchro Network as administered by the GIS/ROADS database. The <br />PROJECT Synchro 8.0 model and shall be easily imported and or exported from that <br />database. Node or intersection numbering scheme must remain consistent with <br />ROADS. Any modifications, additions, or removal of intersections or roadway segments <br />(nodes or links) must be approved by Authority Section Manager — Planning/GIS, <br />Planning and Analysis and the APM. CONSULTANT shall calibrate the model based on <br />travel time, delay studies, field observations of queue lengths, and saturation flows for <br />heavy movements at key intersections. Tru-Traffic Software version 10.0 or latest <br />release should be used, subsequent to initial Synchro optimization, to augment and <br />enhance green band throughput (offset, splits, phase rotation); and, to incorporate <br />specific off band coordinated traffic platoons into the corridor operation as required by <br />data analysis and field observations. <br />The CONSULTANT may use their own numbering scheme for use in Synchro analysis if <br />the volume balancing and other factors becomes an issue with node numbering in <br />regard to OCTA ROADS Database. If the CONSULTANT chooses to use this <br />methodology, the requirement for submittal of the database in the ROADS format is still <br />required. The extra node numbering used for volume balancing nodes and other factors <br />must be removed upon final submittal of the Synchro document that will be incorporated <br />into the ROADS database. These operations will be closely monitored and controlled <br />through the APM and the Section Manager of the GIS department of Planning. <br />CONSULTANT shall evaluate signal timing and coordination parameters with <br />consideration for the following: <br />o Optimize coordination timing using: <br />• Modified Phase Sequence Rotation <br />• Overlap or display output phase transfer techniques to reservice <br />phases with capacity problems (Ring — Barrier Logic) <br />• Protected/Permissive operations <br />o Phasing will be lead/lead only; or, <br />o Flashing Yellow Arrow technique may be employed for lead/lag <br />if controlling/owner AGENCY permits its use <br />• Harmonic cycling — double, half, third or other harmonic multiple, <br />• Other innovative techniques <br />o CONSULTANT will measure the saturation flow rates at key project <br />intersections during one peak hour where the overall intersection volume -to - <br />capacity ratio is greater than or equal to 0.8 as a calibration for the Synchro <br />model <br />o Timing parameters which provide adequate splits and corresponding offsets <br />which fully accommodate pedestrians within the split time. CONSULTANT <br />shall take into consideration the pedestrian timing parameters used by the <br />local AGENCY on a case by case basis. Pedestrian Intervals shall be <br />examined and retimed to current adopted standards by each respective <br />AGENCY. CONSULTANT should note that proposed new pedestrian timing <br />�7 <br />
The URL can be used to link to this page
Your browser does not support the video tag.