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 />CONSULTANT will be required to design, procure, install, construct, and implement all <br />desired components of the PROJECT as described in this document. CONSULTANT <br />shall negotiate with OCTA and AGENCIES at the beginning of PROJECT to determine <br />what actually shall be installed and implemented to maintain budgetary control. <br />CONSULTANT, if required to install or replace any traffic signal control equipment <br />whether local intersection or central systems, shall perform due diligence in the <br />determination of what types of systems are to be installed. NTCIP compatible systems <br />shall be installed. Closed Loop Systems shall not be supplied nor installed. Sole <br />Source systems or systems that are a linked subset or part of a sole source central <br />system are not to be installed unless verification of need can be demonstrated to OCTA <br />APM and CAMM Contract Administration per OCTA standards and policies. In the <br />circumstance where a local intersection system controller is a necessary sole source <br />and there is no alternate substitute, the CONSULTANT shall procure the sole source <br />local intersection controller unit. The controller assembly and appurtenances housing <br />the local intersection system controller may be supplied by others. <br />Deliverables — Task 3: <br />1. Report documenting: <br />a. The field review (including photo logs) <br />b. Recommended mitigations to perceived problems <br />2. Electronic versions of the report and all data files <br />3. Necessary Construction Documentation <br />Task 4: `Before' Study <br />CONSULTANT shall conduct a 'Before' field study report representative of the times <br />and days for which synchronization plans will be developed. The report shall identify <br />Measures of Effectiveness (MOE) to evaluate the effects of the synchronization plans. <br />MOE's will likely include traffic flow, travel time, average speed, number of stops per <br />mile, number of intersections traversed on green vs. stopped by red (Greens per Red) <br />(note: Average Speed, Stops per Mile, and Greens per Red are the new OCTA MOE, <br />Corridor Synchronization Performance Index (CSPI)), fuel consumption reduction, <br />pollution reduction, and other pertinent items. The CONSULTANT shall include the <br />CSPI as part of the MOEs as they are easily identifiable by lay persons relevant to <br />demonstrating corridor improvements. The identified MOE's shall be compiled for the <br />corridor using the floating car method and from Synchro 8.0 and from Try -Traffic <br />Version 10.0. A minimum of five (5) runs will be completed in each direction for each of <br />the three weekday timing plans (a.m., midday, and p.m.), and a minimum of five (5) runs <br />will be completed in each direction during the Saturday midday plan. Number of runs <br />shall be consistent for both directions and time periods. Based on engineering judgment <br />and in conjunction with APM approval, CONSULTANT may subdivide the corridor into <br />7 <br />
The URL can be used to link to this page
Your browser does not support the video tag.