My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
ITERIS, INC. 4 -2015
Clerk
>
Contracts / Agreements
>
I
>
ITERIS, INC. 4 -2015
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/26/2016 4:42:33 PM
Creation date
6/25/2015 10:54:04 AM
Metadata
Fields
Template:
Contracts
Company Name
ITERIS, INC.
Contract #
A-2015-056
Agency
PUBLIC WORKS
Council Approval Date
4/21/2015
Expiration Date
12/31/2018
Insurance Exp Date
4/1/2017
Destruction Year
2023
Document Relationships
ITERIS, INC.
(Amended By)
Path:
\Contracts / Agreements\I
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
87
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
B. Consultant shall lead a project Kick -Off Meeting with all agency representatives to <br />establish communication channels and protocols disouss the scope, schedule, and <br />budget; gather available Information; and obtain a thorough understanding of the goals <br />for the project. Specific topics to discuss include data collection needs, specific <br />programs or software used and specific construction items and procurement <br />methodologies. <br />C, Consultant shall conduct monthly progress meeting with participating agencles, <br />Consultant shall prepare agendas, provide status updates, discuss the progress and <br />direction of the work, and provide minutes for all meetings. Consultant may conduct <br />additional meetings as necessary during the course of the project to address immediate <br />Issues or needs. <br />D. Consultant is required to make presentations as necessary to OCTA or participating <br />agency's Council, designated Committee or interagency meetings to present project <br />purpose and results. <br />E. Consultant shall document and maintain separate project expenses for each <br />participating agency. <br />'Task 2: Develop and Implement Traffic Signal Synchronization Timing <br />Consultant shall collect all traffic data; perform field and existing traffic signal Inventory as <br />necessary in the project corridor to develop the optimal traffic signal synchronization plans. <br />A. Data Collection <br />f. Consultant shall conduct one 24-hour mid -week and two 24-hour weekend (Sat <br />and Sun) machine counts at every half -mile along the project, 24-hour data will <br />be used to determine the peak hour counts and synchronization. <br />2. Consultant shall collect vehicle classification counts at all locations where 24- <br />hour counts are taken. <br />8. Consultant shall conduct weekday and weekend peak period turning movement <br />counts (TMC) at each and every one of the project signalized intersections. <br />a. Weekday TMC counts shall be conducted for two hours of each peak <br />period (AM, Mid-day, and PM). <br />b. Weekend TMC counts shall be conducted for one 2 -hour peak period <br />(either on Saturday or Sunday). Exact time and day to be determined <br />from 24 hours counts. <br />4. Consultant shall conduct special video recording of pedestrian and bicycle <br />counts In all directions for 6 intersections. The video counts shall be continuous <br />from Sam to 7pm. Consultant to provide hourly counts of pedestrian and <br />bicycles report and copy or video. <br />6. Field Inventory and Exist Timing Parameters <br />Consultant shall perform thorough field inventory of all project Intersections <br />including trafflc signal controller, related hardware, geometric layout and existing <br />timing parameters as necessary for timing analysis. <br />S. Timing Analysis and Development of Synchronization Plans <br />1. Consultant shall work with the agencies to develop a model of the study area and <br />calibrate the model based on flold observations of existing conditions. Signal <br />simulation shall be conducted In Synchro/Sim Traffic 8.0. The corridor model must <br />be consistent with all aspects and seamlessly interface and interlace with the <br />County Wide Synchro Network as administered by OCTA GIS/RCADS database. <br />Node or intersection numbering scheme must remain consistent with ROADS. <br />
The URL can be used to link to this page
Your browser does not support the video tag.