Stevens Creek Boulevard and De Anza Boulevard Traffic Signal Synchronization Project

1) OVERVIEW The City of Cupertino (City) is requesting professional traffic engineering services to retime, coordinate, implement, evaluate, and document traffic signal operations along Stevens Creek Boulevard and De Anza Boulevard. The Project includes 28 unique signalized intersections on two principal arterial corridors and is intended to provide near-term, measurable operational benefits through updated traffic signal timing rather than roadway widening or major construction. The consultant shall perform a complete signal-retiming process, including existing data review, field observations and data collection, signal and communications inventory, existing conditions analysis, traffic operations modeling, timing alternatives, final timing plans, implementation, multiperiod fine-tuning, before-and-after evaluation, database and record updates, and final reporting. 2) BACKGROUND Stevens Creek Boulevard and De Anza Boulevard function as Cupertinos primary east-west and north-south arterial corridors. They serve regional and local trips, employment centers, commercial areas, schools, De Anza College, residential neighborhoods, I-280, SR-85, frequent VTA routes, pedestrians, and bicyclists. Stevens Creek Boulevard serves VTA routes 523, 23, 51, and 55. De Anza Boulevard serves routes 55, 51, and 25. Travel patterns and traffic volumes have changed since prior comprehensive timing efforts due to development, changing land uses, altered commute patterns, freeway congestion, increased multimodal activity, and roadway changes. These conditions have contributed to inconsistent progression, delay near freeway ramps and commercial nodes, side-street inefficiencies, and community concerns. Stevens Creek Boulevard is identified as the Citys highest-ranked Vision Zero Corridor of Concern. De Anza Boulevard is also a high-priority corridor and the Citys highest volume corridor. Timing improvements must maintain safe pedestrian and bicycle operation while improving overall corridor efficiency. Previous De Anza Boulevard retiming produced a 9 percent average travel-time reduction, a 12 percent speed increase, 29 percent fewer stops, and a reported 44:1 five-year benefit-cost ratio. The City seeks comparable, verifiable benefits from this Project. The Project performance targets include: Approximately 8 to 15 percent reduction in corridor travel time. Approximately 20 to 30 percent reduction in stops. Improved peak travel-time reliability and incident recovery. Reasonable side-street operations. Safe pedestrian and bicycle timing. Complete and maintainable timing and system documentation. These percentages are performance targets rather than guarantees. The selected consultant shall establish defensible baseline conditions and recommend realistic final performance objectives based on observed conditions. 3) SITE LOCATION Stevens Creek Boulevard: 15 Listed Intersections 1. Tantau Avenue 2. Finch Avenue 3. Wolfe Road/Miller Avenue 4. Perimeter Road 5. Portal Avenue 6. Blaney Avenue 7. Torre Avenue 8. De Anza Boulevard 9. Bandley Drive 10. Saich Way 11. Stelling Road 12. Mary Avenue 13. SR-85 northbound ramp 14. SR-85 southbound ramp 15. Bubb Road/Peninsula Avenue De Anza Boulevard: 14 Listed Intersections 1. Homestead Road 2. I-280 northbound ramp 3. I-280 southbound ramp 4. Mariani Avenue 5. Lazaneo Drive 6. Stevens Creek Boulevard 7. Rodrigues Avenue 8. McClellan Road/Pacifica Drive 9. Bollinger Road 10. Fallenleaf Avenue/Clarendon Avenue 11. Kentwood Drive 12. SR-85 northbound ramp 13. SR-85 southbound ramp 14. Rainbow Drive The Stevens Creek Boulevard/De Anza Boulevard intersection appears in both corridor lists and is one unique signalized intersection. The total Project inventory is therefore 28 unique signals. The City may add or remove locations only through written authorization. 4) PROJECT TASKS/REQUIREMENTS Task 1. Project Management and Coordination 1.1 Kickoff and Project Organization Conduct a kickoff meeting to confirm scope, objectives, roles, communication protocols, decision authority, schedule, data needs, system access, agency coordination, deliverable formats, and review period 1.2 Project Management Plan Within ten business days after kickoff, submit a plan containing the work breakdown structure, detailed schedule, staffing plan, data and file procedures, version control, deliverable register, agency coordination plan, and invoice procedures. 1.3 Meetings and Coordination Schedule and coordinate monthly management meetings with advance agendas, minutes, and action items within three business days. Task Deliverables: Kickoff agenda and minutes. Project Management Plan. Baseline and updated schedules. Monthly invoices. Meeting agendas, minutes, decision log, and action-item log. Task 2. Data Review, Collection, and Verification 2.1 Existing Data Review Review existing timing plans, controller databases, counts, travel-time information, geometry, lane configurations, turn restrictions, speeds, school schedules, construction, prior retiming reports, communications, signal plans, and applicable City plans. The review shall include existing coordination patterns, time-of-day schedules, cycles, splits, offsets, phase sequences, permissive periods, pedestrian and bicycle timing, detection settings, maximum and gap settings, clearance intervals, preemption and priority functions, controller clocks, and other relevant database parameters. Identify data gaps and inconsistencies. 2.2 Data Collection and Field Verification Plan Submit a data collection and field verification plan identifying the following: Data collection and field inventory locations. Proposed dates and analysis periods. Count types, durations, and methodologies. School-calendar considerations. Travel-time study procedures and number of repeated runs. Field observation procedures. File formats and data-submittal standards. This plan shall distinguish between: Information available from existing records. Information requiring field verification. New data that must be collected. 2.3 Signal System and Database Inventory At each Project signal, document existing timing and controller database information. Verify the following: Controller type and firmware. Cabinet and communications equipment. Coordination operation and time-of-day schedules. Detection equipment and detection zones. Malfunctioning equipment and failed detection. Communications interruptions. Controller clock drift. Database and timing-sheet discrepancies. Pedestrian and bicycle timing and detection. Preemption and priority functions. Controller or firmware limitations. Ramp-terminal constraints. Other material field conditions affecting signal operations. Provide documentation and identify discrepancies between field conditions, controller databases, timing sheets, and central-system records. 2.4 Turning-Movement Counts Collect quality-controlled turning-movement counts at Project signals during City-approved analysis periods. Counts shall distinguish: Passenger vehicles. Bicycles. Pedestrians. U-turns. Lane utilization. Other movements necessary for signal timing and operational analysis. At a minimum, the counts shall address: Weekday morning periods. Weekday midday periods. Weekday evening periods. Two appropriate weekend periods. 2.5 24-Hour Traffic Counts Collect 24-hour traffic counts at City-approved corridor segments. Use the data to document and confirm: Hourly demand patterns. Peak-period timing and duration. Directional distribution. Existing time-of-day schedule transitions. Weekday and weekend differences. Other demand characteristics relevant to signal coordination. 2.6 Bicycle and Pedestrian Counts In addition to the pedestrian and bicycle volumes documented through turning-movement counts, collect information necessary to evaluate: Pedestrian clearance requirements. Pedestrian demand and movement patterns. Bicycle movements and lane utilization. Pedestrian and bicycle detection reliability and deficiencies. Operational conditions affecting pedestrian and bicycle signal timing. This work shall supplement, rather than duplicate, the multimodal data collected under Task 2.4. 2.7 Baseline Travel-Time and Stop Studies Conduct floating-car, probe-based, or other City-approved travel-time studies in each direction and analysis period. Document: Total travel time. Running time. Number and location of stops. Average and segment speeds. Travel-time variability. Bottleneck locations. Date and time. Weather. Incidents. Construction and other relevant conditions. Conduct sufficient repeated runs to establish a defensible baseline for comparison with proposed and implemented timing plans. 2.8 Operational Field Observations at Select Locations Perform targeted field observations to document operational conditions requiring focused attention. Coordinate these observations with travel-time studies and traffic counts when practical, while maintaining separate documentation of observed conditions. Conditions to be evaluated shall include: Queue formation and spillback. Freeway ramp interactions. Turn-pocket and storage constraints. Signal grouping and progression considerations. Side-street operations. Pedestrian timing constraints. Bicycle operations. Transit operations. Conditions that may be incompatible with potential timing strategies. Other recurring or location-specific operational issues. Observation locations shall include, but not be limited to: De Anza Boulevard southbound between Stevens Creek Boulevard and Bollinger Road during the p.m. peak hour. De Anza Boulevard northbound between Rainbow Drive and the SR-85 northbound ramp during the a.m. peak hour. Stevens Creek Boulevard eastbound and westbound between the SR-85 northbound ramp and Bubb Road/Peninsula Avenue during the a.m. and p.m. peak hours. 2.9 Data Quality Control Review all collected and compiled data for: Completeness. Consistency. Equipment error. Outliers. Database discrepancies. Atypical field conditions. Document quality-control procedures and any adjustments made to the data. Recollect deficient data at no additional cost when the deficiency results from consultant equipment, staffing, methodology, processing, or quality-control failure. Task Deliverables: Existing-data inventory. Draft and Final Data Collection and Field Verification Plan. Signal inventory matrix and completed field forms. Photographic documentation. Existing timing sheets and electronic inventory files. Raw and processed traffic counts, diagrams, and summaries. Pedestrian and bicycle datasets. Travel-time and stop-study datasets. Field observation logs. Editable electronic files in City-approved formats. Task 3. Existing Conditions Analysis and Documentation 3.1 Operations Assessment Analyze the traffic counts, multimodal data, travel-time studies, field observations, and signal inventory information collected under Task 2. Evaluate and document: Existing corridor progression and coordination. Travel times, speeds, stops, and variability. Bottlenecks and recurring delay. Queue formation and spillback. Freeway ramp interactions. Turn-pocket and storage constraints. Side-street conditions. Pedestrian and bicycle operations. Weekday and weekend demand differences. Compatibility of existing infrastructure and operations with potential signal timing strategies. Task Deliverables Prepare a draft and final Existing Conditions Technical Memorandum summarizing: Traffic demand and multimodal conditions. Corridor travel times and stops. Bottlenecks and queue interactions. Side-street and ramp-terminal conditions. Pedestrian and bicycle operations. Timing, database, and field discrepancies. Deficiencies and recommended next steps. Revise the memorandum in response to City comments. Task 4. Modeling, Alternatives Analysis, and Timing Development 4.1 Model Development Develop microsimulation models for the required corridors and periods. Reflect geometry, traffic, pedestrian, bicycle, phasing, actuation, coordination, speeds, saturation flow, lane utilization, queues, ramp interaction, and transit effects. 4.2 Calibration and Validation Calibrate and validate using travel times, stops, queues, bottlenecks, lane utilization, saturation, side-street delay, and recurring spillback observed and documented during Tasks 2 and 3. Perform additional field observations as necessary to satisfactorily calibrate and validate the model. Document assumptions and adjustments. 4.3 Timing Alternatives Evaluate and develop time-of-day and coordination timing plans, including but not limited to cycle lengths, splits, offsets, phase sequences, coordination reference points, zones, time-of-day schedules, transitions, maximums, and gap settings. for all recommended schedules. Coordination plans shall be developed as appropriately based upon travel patterns observed and documented during Task 3, but should include, as a minimum, the following scenarios for each corridor or segment: Weekday a.m. peak hour Weekday mid-day Weekday p.m. peak hour Weekday off-peak Weekend peak Weekend off-peak Corridors may be divided into segments (for example, Stevens Creek Blvd east of De Anza Blvd and Stevens Creek Blvd west of De Anza Blvd) if cycle length optimization analysis suggests that improved overall performance would result. 4.4 Measures of Effectiveness As appropriate, preliminarily evaluate measures of effectiveness related to travel time, stops, delay, speed, reliability, queue length, cycle failure, throughput, side-street delay, pedestrian delay, bicycle accommodation, fuel, emissions, and person throughput as appropriate. Do not optimize one measure at the unreasonable expense of safety or other modes. 4.5 Draft Timing Plans Prepare complete draft timing plans and independently check mathematical consistency, coordination, pedestrian timing, clearance intervals, controller compatibility, phase sequence, maximums, transitions, preemption interaction, time-of-day consistency, and database accuracy. Task Deliverables: Base models and calibration/validation memorandum. Existing and alternative performance summaries. Draft implementation-ready timing plans. Recommended time-of-day schedules. Electronic model, input, and output files. Draft Timing Development Technical Memorandum. Task 5. Implementation and Field-Tuning 5.1 Timing Implementation Implement approved draft plans in coordination with City staff. Before implementation, back up databases; confirm compatibility, clocks, approvals, pedestrian and clearance timing, detection operation, and immediate availability of rollback files. 5.2 Field Fine-Tuning Observe and fine-tune over multiple days and periods, including weekday peaks and weekend periods. Address progression, stops, platoon arrival, queue discharge, side-street delay, spillback, phase failure, ramp interaction, pedestrians, bicycles, schools, and transitions. 5.3 Stabilization Allow an appropriate stabilization period, perform follow-up observations, and resolve timing-related deficiencies within the authorized scope. Task Deliverables: Draft and final Implementation Plan. Backup files and implementation checklist. Implementation and field observation logs. Fine-tuning change log. Updated timing sheets, models, and databases. Deficiency and resolution log. Implementation completion memorandum. Task 6. Before-and After Studies and Measures of Effectiveness 6.1 After Data Collection Collect after data using methods, routes, periods, day types, sample sizes, and quality-control procedures reasonably consistent with the before data. Identify weather, school, holiday, construction, event, incident, demand, and roadway factors affecting comparability. 6.2 Measures of Effectiveness Evaluate measures of effectiveness related to corridor travel time by direction and period, stops, speed, reliability, progression, queues, spillback, side-street effects, and transit effects where data are available. Additional measures may include delay, fuel, emissions, throughput, and benefit-cost ratio. 6.3 Performance Findings Compare observed results with baseline conditions, modeled forecasts, Project targets, prior performance, and funding objectives. Explain material differences and identify causes, refinements, limitations, corrective actions, and optional follow-up work when targets are not achieved. 6.4 Benefit-Cost Documentation Prepare a benefit-cost assessment using an accepted methodology and clearly documented assumptions. Task Deliverables: After-study plan and raw data. Processed data and before-and-after tables. Travel-time, stop, and reliability summaries. Performance graphics and benefit-cost analysis when required. Corrective-action recommendations. Draft Before-and-After Evaluation Memorandum. Task 7. Documentation, Database Updates, Training, and Closeout 7.1 Final Timing Documentation Prepare field-verified timing sheets, time-of-day schedules, coordination plans, controller databases, central database updates, offset and split tables, phase-sequence documentation, implementation records, and change logs. 7.2 Electronic Project Archive Provide raw and processed data, counts, travel-time files, inventories, photographs, existing and final timing files, models, calibration files, outputs, calculations, meeting records, quality-control records, implementation logs, evaluations, and reports in native editable and PDF formats. 7.3 Draft Final Report Prepare an executive summary and full technical report covering existing conditions, data, inventory, modeling, alternatives, timing, implementation, fine-tuning, results, performance targets, multimodal and side-street considerations, limitations, and benefit-cost findings. 7.4 Final Report and Funding Closeout Address City comments and submit the final report. Support VTA reporting, invoice support, monitoring, audit, records retention, performance reporting, funding reconciliation, and closeout. Task Deliverables: Final timing sheets, databases, and models. Time-space diagrams for all coordination plans. Organized electronic Project archive. Draft final report and comment-response matrix. Final report, final schedule, final budget summary, and deliverable index. Funding-program closeout support. 5) General Requirements and Considerations 1. Applicable Standards Comply with current applicable laws, regulations, standards, and guidance, including the California MUTCD, federal MUTCD when applicable, Highway Capacity Manual, City procedures, controller and signal-system standards, VTA funding requirements, field safety requirements, and professional standards of care. Notify the City of conflicts and obtain written direction. 2. Professional Responsibility Work requiring a California license shall be performed under the responsible charge of an appropriately licensed professional. Final engineering documents shall be signed or sealed when legally required or requested. 3. Quality Assurance and Quality Control Independently review all material before submittal and identify preparers and reviewers. Correct consultant-attributable errors, inconsistencies, omissions, corrupted files, and nonconforming work without additional compensation. 4. City Review Allow approximately ten business days for City review of major drafts unless otherwise scheduled. City review does not relieve the consultant of professional responsibility. Provide a comment-response matrix with revised major deliverables. 5. Data and Deliverable Ownership Project-specific data, calculations, models, timing files, databases, reports, photographs, and work products become City property upon payment, subject to the agreement. Provide native editable files without access restrictions. 6. Field Safety Be responsible for personnel safety. Use high-visibility clothing, appropriate traffic-safety practices, qualified personnel, and approved traffic-control plans. No lane closure or cabinet work may occur without required approvals. 7. Record Retention and Audit Support Maintain complete Project and financial records for the period required by the agreement and funding program, organized for review by the City, VTA, auditors, and other authorized parties. 8. Changes in Scope Do not perform out-of-scope work or exceed a task budget without written authorization. Requests for additional services shall describe the reason, scope, deliverables, schedule effect, staffing, fee, assumptions, and consequences of not performing the work. 9. City Responsibilities The City anticipates providing available timing and signal records, traffic data, plans, system information, access, review comments, decisions, coordination assistance, known construction or event information, and staff participation. The proposal shall identify additional required City support