CTR074650_Contract_Documents.pdf

Docusign Envelope ID: FBFD47B1-CFC8-4273-8F34-412BD8349EC2

CTR074650

18th November 24

11/18/2024

Rev. 05/2023

Procurement

STATE OF ARIZONA

ARIZONA DEPARTMENT OF TRANSPORTATION

1655 W. Jackson St., MD 100P Phoenix, AZ 85007

REQUEST FOR PROPOSAL

SOLICITATION NUMBER: BPM006291

DESCRIPTION: City of Peoria ASCT

QUESTIONS: Inquiries regarding the solicitation are to be submitted online through the State’s e-Procurement system, Arizona Procurement Portal (APP) (https://app.az.gov/) using the Discussion Forum tab.

OFFERORS ARE STRONGLY ENCOURAGED TO READ THE ENTIRE SOLICITATION.

Aimee Fields Procurement Officer Phone: 602-712-8545 Email: afields@azdot.gov

This solicitation is issued in accordance with A.R.S. §41-2534 and A.A.C. R2-7-C301 et seq., Competitive Sealed Proposals.

“An Equal Opportunity Agency”

The Arizona Department of Transportation, in accordance with the provisions of Title VI of the Civil Rights Act of 1964 (78 Stat. 252.42 U.S.C. §§ 2000d-4) and the Americans with Disabilities Act (ADA), hereby notifies all bidders that it will affirmatively ensure that any contract entered into pursuant to this advertisement, disadvantaged business enterprises will be afforded full and fair opportunity to submit bids in response to this invitation and will not be discriminated against on the grounds of race, color, national origin in consideration for an award.

Persons that require a reasonable accommodation based on language or disability should contact ADOT’s Procurement Office by phone (602) 712-7466. Requests should be made as early as possible to ensure the State has an opportunity to address the accommodation.

Las personas que requieran asistencia (dentro de lo razonable) ya sea por el idioma o discapacidad deben ponerse en contacto con ADOT (602) 712-7466.

https://app.az.gov/

TABLE OF CONTENTS

Solicitation No: BPM006291 Available online at

SECTION PAGE

Notice 1

Table of Contents 2

Scope of Work 3

Special Terms and Conditions 23

Uniform Terms and Conditions 34

Federal Provisions 53

EXHIBITS

1 - Title VI/Non-Discrimination Assurances Appendix A 78

2 - Title VI/Non-Discrimination Assurances Appendix E 79

3 – 310PS DBE Certification of Final Payments 80

4 - Vicinity Map 81

5 – Project Locations 82

6 – Current Hardware installed at Project Intersections 83

SCOPE OF WORK

1. Statement of Need

1.1. Pursuant to the Arizona Procurement Code, A.R.S. §41-2501 et seq., the State of Arizona Department of Transportation (Department), on behalf of the City of Peoria (City) has a requirement for a qualified Contractor to furnish, install, and implement an Adaptive Signal Control Technology (ASCT) system.

2. Introduction and Background

2.1. An ASCT system is one in which some or all the signal timing parameters are modified in response to changes in the traffic conditions, in real time and independent of a human operator.

2.1.1. The purpose of providing adaptive control along this corridor is to improve safety and travel time efficiency and reduce congestion and vehicle delay along the corridor.

3. General Requirements

3.1. The Contractor shall furnish and install the ASCT system, including necessary travel time software (if required by the proposed solution), video detection equipment, licensing, servers, and performance reporting capabilities, to be integrated at all signalized intersections on existing City infrastructure along the study corridor based on detailed plans and technical specifications.

3.1.1. There are 28 Intersections involved in this project located in 2 Study Corridors.

3.1.1.1. The Deer Valley Road / Lake Pleasant Parkway intersection is listed in both study corridors and intersects one another.

3.2. The Contractor shall furnish and install the Project components in accordance with the requirements set forth in this document.

3.3. The Contractor shall install all hardware and/or software required to render the system fully operational.

3.4. The Project time frame is eight (8) months from issuance of the purchase order after the contract execution.

4. Specific Requirements

4.1. Performance Standards

4.1.1. The work outlined herein shall be performed in accordance with the requirements of the following documents:

4.1.1.1. Arizona Department of Transportation, Standard Specifications for Road and

Bridge Construction, 2021 Edition

4.1.1.2. Arizona Department of Transportation, Roadway Engineering Group, Construction Standard Drawings available on the Department’s website

4.1.1.3. Arizona Department of Transportation, Traffic Group, Manual of Approved Signs, available on the Department’s website

4.1.1.4. Arizona Department of Transportation, Traffic Group, Traffic Control Design

Guidelines, 2019 Edition, available on the Department’s website.

4.1.1.5. Manual on Uniform Traffic Control Devices for Streets and Highways, 2009 edition and Arizona Supplement to the 2009 edition, dated January 2012.

4.2. Operational Requirements of the ASCT System

4.2.1. The following requirements are provided to establish a standard for the hardware and software components of the ASCT system. The Contractor shall furnish and install all components in accordance with the requirements set forth in this section.

4.2.2. The system requirements are based on the Federal Highway Administration (FHWA) “Model Systems Engineering Documents for Adaptive Signal Control Technology Systems”, August 2012 document (FHWA-HOP-11-027).

4.2.3. System Minimum Requirements

FHWA-HOP-11-027

Concept of Operations Statements System Requirements

Reference Number

4.3. Adaptive Strategies

4.1.0-1 The system operator needs the ability to implement different strategies individually or in combination to suit different prevailing traffic conditions. These strategies include:

• The ASCT shall alter the adaptive operation to achieve required objectives in user-specified conditions.

• The system operator needs the ability to implement different strategies individually or in combination to suit different prevailing traffic conditions and/or achieve different user-defined objectives.

• The ASCT shall calculate a cycle length, optimum phase lengths, maximum phase lengths, and phase order of a single intersection, based on current measured traffic conditions and optimization objectives.

• For each signal group, the operator shall have control to define an individual objective. For example, near a freeway interchange or in a location with heavy turning movements, the queue management strategy may be specified, while on an arterial with long signal spacing the smooth flow objective may be specified.

Parameters include:

Cycle Length

Concept of Operations Statements System Requirements

Reference Number

• The ASCT shall calculate optimum cycle lengths according to the user- specified coordination strategy.

• The ASCT shall select cycle length based on a time-of-day schedule.

• The ASCT shall limit cycle lengths to a user-specified range.

• The ASCT shall provide maximum and minimum cycle lengths.

• The ASCT shall limit changes in cycle length to a user-specified value.

• The ASCT shall increase the limit for a user-specified number of cycles based on a change in conditions. The change in conditions shall be defined by a user-specified number of successive adaptive user-defined increases in cycle length at the maximum rate.

Offsets

• The ASCT shall calculate offsets to suit the current coordination strategy for the user-specified reference point for each signal controller along a coordinated route or within a group along a coordinated route.

Phase Times

4.1.0-1.0-1 • maximize the throughput and provide smooth flow along the coordinated route.

• The ASCT shall calculate phase lengths for all phases at each signal controller to suit the current coordination strategy.

• The ASCT shall provide maximum and minimum phase times.

4.1.0-1.0-2 • provide smooth flow along coordinated routes. • The ASCT shall not provide a phase length longer than the maximum value.

4.1.0-1.0-3 • distribute phase times in an equitable fashion. • The ASCT shall provide a user- specified minimum value for each phase at each signal controller and the ASCT shall not provide a phase length shorter than the minimum value.

4.1.0-1.0-4 • manage the lengths of queues at critical locations. • The ASCT shall limit the difference between the length of a given phase and the length of the same phase during its next service to a user- specified value.

4.1.0-1.0-5 • manage the locations of queues within the network. Queues

4.1.0-1.0-6 • At an isolated intersection, optimize operation with a minimum of phase failures based on the optimization objectives.

• When queues are detected at user- specified locations, the ASCT shall execute user-specified adaptive operation strategy, timing plan, and/or operational mode.

• When queues are detected at user- specified locations, the ASCT shall omit a user-specified phase at a user-specified signal controller.

4.1.0-3 The system operator needs to change the operational strategy (for example, from smooth flow to maximizing throughput or managing queues) based on changing traffic conditions.

• When current measured traffic conditions meet user-specified criteria, the ASCT shall alter the state of the signal controllers, maximizing the throughput of the coordinated route.

Concept of Operations Statements System Requirements

Reference Number

4.1.0-4 The system operator needs to detect repeated phase failures and control signal timing to prevent phase failures building up queues. The operator in this case is trying to prevent a routine queue from forming where it will block another movement in the cycle unnecessarily. For example, the operator may need to prevent a queue resulting from the trailing end of the through green from blocking the storage needed by an entering side-street left turn in the subsequent phase.

• The ASCT shall detect repeated phases that do not serve all waiting vehicles. (These phase failures may be inferred, such as by detecting repeated max- out.)

• The ASCT shall alter operations, to minimize repeated phase failures.

4.1.0-5 The system operator needs to minimize the chance that a queue forms at a specified location.

• The ASCT shall adjust offsets to minimize the chance of stopping vehicles approaching a signal that have been served by a user-specified phase at an upstream signal.

4.1.0-6 The system operator needs to modify the sequence of phases to support the various operational strategies.

• The ASCT shall provide a minimum of 16 different user-defined phase sequences for each signal.

• The ASCT shall not prevent a phase/overlap output by time-of-day.

• The ASCT shall not prevent a phase/overlap output based on an external input.

• The ASCT shall not prevent user- specified phases to be designated as coordinated phases.

4.2 Network Characteristics

4.2.0-1 The system operator needs to adaptively control up to 40 signals from the City TMC, located at 9875 N. 85th Avenue, Peoria, AZ.

• The ASCT shall control a minimum of 22 signals concurrently along the Lake Pleasant Pkwy Corridor, and 7 signals concurrently along the Deer Valley Rd corridor.

4.2.0-2 The system operator needs to be able to adaptively control up to 4 independent groups of signals. While the signals are relatively close, the traffic conditions are such that they will normally be coordinated as two (or more) separate and independent groups.

• The ASCT shall support groups of signals.

• The ASCT shall control a minimum of 4 groups of signals.

• Each group shall operate independently

• The boundaries surrounding signal controllers that operate in a coordinated fashion shall be altered by the system according to either a time of day schedule or traffic conditions.

• The system operator needs to vary the number of signals in an adaptively controlled group to accommodate the prevailing traffic conditions.

4.3 Coordination Across Boundaries

4.3.0-1 The system operator needs to adaptively control signals operated by the City of Peoria.

• The ASCT shall support NCTIP 2306 TMDD C2C data exchange using REST, JSON, or XML protocols.

• The ASCT shall not prevent the current ATMS external system from monitoring and controlling the signal controllers through standard NTCIP commands and status requests.

4.3.0-2 The system operator needs to send data to another system that would allow the other system to coordinate with the ASCT system. (Preferred)

• The ASCT shall send operational data to Regional Archive Data Server (RADS) external system. Operational data will at minimum include the standard high-resolution data for ATSPMs.

Transmission of the data logs will occur at minimum once per 15 minutes.

4.4 Security

4.4.0-1 The system operator needs to have a security management and administrative system that allows access and operational privileges to be assigned, monitored and

• The ASCT shall be implemented with a security policy that addresses the following selected elements:

o Local access to the ASCT.

Concept of Operations Statements System Requirements

Reference Number controlled by an administrator, and conform to the agency's access and network infrastructure security policies.

o Remote access to the ASCT.

o System monitoring.

o System manual override.

o Development o Operations o User login o User password o Administration of the system o Signal controller group access o Access to classes of equipment o Output activation o System parameters o Report generation o Configuration o Security alerts o Security logging o Security reporting o Database o Signal controller

4.5 Queueing Interactions

4.5.0-2 The system operator needs to detect queues within the system's boundaries and modify the ASCT operation to accommodate the queuing.

• When queues are detected at user- specified locations, the ASCT shall execute user-specified timing plan/operational mode and/or adaptive operation strategy.

• The ASCT shall detect the presence of queues at pre-configured locations.

• When queues are detected at user- specified locations, the ASCT shall omit a user-specified phase at a user- specified signal controller.

4.5.0-4 The system operator needs to store queues in locations where they can be accommodated without adversely affecting adaptive operation.

• The ASCT shall meter traffic into user- specified bottlenecks by storing queues at user-specified locations.

4.5.0-5 The system operator needs to prevent queues forming at user-specified locations.

• The ASCT shall maintain capacity flow through user-specified bottlenecks.

4.6 Pedestrians

4.6.0-2 The system operator needs to accommodate infrequent pedestrian operation while maintaining adaptive operation.

This is appropriate for pedestrian calls that are common but not so frequent that they drive the operational needs.

• When a pedestrian phase is called, the ASCT shall accommodate pedestrian crossing times during adaptive operations.

4.8 System Responsiveness

4.8.0-1 The system operator needs to modify the ASCT operation to closely follow changes in traffic conditions.

• The ASCT shall limit the changes in the direction of primary coordination to a user-specified frequency.

Concept of Operations Statements System Requirements

Reference Number

4.8.0-2 The system operator needs to constrain the selection of cycle lengths to those that provide acceptable operations, such as when resonant progression solutions are desired.

• The ASCT shall select cycle length from a list of user-defined cycle lengths.

4.8.0-3 The system operator needs to respond quickly to sudden large shifts in traffic conditions.

• When a large change in traffic demand is detected, the ASCT shall respond more quickly than normal operation, subject to user-specified limits. The user shall define “normal operation” and “quick” response times.

4.9 Complex Coordination and Controller Features

4.9.0-1.0-1 The ASCT needs to service a phase more than once per cycle while maintaining adaptive operation, when specified by the user.

• When specified by the user, the ASCT shall serve a vehicle phase more than once for each time the coordinated phase is served.

4.9.0-1.0-2 The ASCT needs to operate at least 8 overlap phases. • The ASCT shall provide a minimum of 8 phase overlaps.

4.9.0-1.0-3 The ASCT needs to operate 4 rings, 8 phases, and up to 4 phases per ring.

• The ASCT shall accommodate a minimum of 8 phases at each signal.

• The ASCT shall accommodate a minimum of 4 rings at each signal.

• The ASCT shall accommodate a minimum of 4 phases per ring.

4.9.0-1.0-4 The ASCT needs to permit different phase sequences under different traffic conditions or by time-of-day.

• Each permissible phase sequence shall be user-assignable to any signal timing plan.

• The ASCT shall provide a minimum of 16 different user-defined phase sequences for each signal.

• Each permissible phase sequence shall be executable by a time of day schedule.

• Each permissible phase sequence shall be executable based on measured traffic conditions.

4.9.0-1.0-5 The system operator needs allow one or more phases to be omitted (disabled) under certain traffic conditions or signal states while maintaining adaptive operation.

• The ASCT shall omit a user-specified phase when the cycle length is below a user-specified value.

• The ASCT shall omit a user-specified phase according to a time of day schedule.

• The ASCT shall omit a user-specified phase based on measured traffic conditions.

• The ASCT shall omit a user-specified phase based on the state of a user-specified external input.

4.9.0-1.0-6 The system operator needs to prevent one or more phases being skipped under certain traffic conditions or signal states.

• The ASCT shall prevent skipping a user-specified phase according to a time of day schedule.

• The ASCT shall prevent skipping a user-specified phase when the user-specified phase sequence is operating.

• The ASCT shall prevent skipping a user-specified phase based on the state of a user-specified external input.

4.9.0-1.0-9 The ASCT shall allow any phase to be designated as the coordinated phase.

• The ASCT shall not prevent user- specified phases to be designated as coordinated phases.

4.9.0-1.0-10 The ASCT shall allow the operator to specify which phase receives unused time from a preceding phase

• The ASCT shall assign unused time from a preceding phase that terminates early or is skipped to a user-specified phase as follows:

o Next phase o Next coordinated phase

Concept of Operations Statements System Requirements

Reference Number o User-specified phase

4.9.0-1.0-12 The ASCT shall allow the coordinated phase to terminate early under prescribed traffic conditions.

• The ASCT shall have the option for a coordinated phase to be released early based on a user-definable point in the phase or cycle.

4.9.0-1.0-13 The ASCT shall allow flexible timing of non- coordinated phases (such as late start of a phase) while maintaining coordination

• When specified by the user, the ASCT shall execute pedestrian recall on pedestrian phase adjacent to coordinated phases.

4.9.0-1.0-15 The ASCT shall allow flashing yellow to control permissive left turns.

• The ASCT shall not prevent the controller from displaying flashing yellow arrow left turns.

4.10 Monitoring, and Control

4.10.0-1.0-1 The system operator needs to monitor and control all required features of adaptive operation from the City TMC.

• The City’s TMC is located at 9875 N. 85th Avenue, Peoria, AZ.

4.10.0-1.0-5 The system operator needs to monitor and control all required features of adaptive operation from all City local controller cabinets.

4.10.0-1.0-7 The system operator needs to monitor and control all required features of adaptive operation from remote locations.

• Remote locations as deemed appropriate and necessary by the City.

4.10.0-2 The operator needs to access to the database management, monitoring and reporting features and functions of the signal controllers and any related signal management system from the access points defined for those system components.

• The ASCT shall not prevent access to the local signal controller database, monitoring or reporting functions by any installed signal management system.

4.11 Performance Reporting

4.11.0-2 The system operator needs to store and report data used to calculate signal timing and have the data available for subsequent analysis.

• The ASCT shall store results of all signal timing parameter calculations for a minimum of 90 days.

• The ASCT shall store the following measured data in the form used as input to the adaptive algorithm for a minimum of 6 months:

o volume o occupancy o queue length o Percent arrival on green o Percent time running adaptive o Average Cycle Length per intersection

• The ASCT shall report measures of current traffic conditions on which it bases signal state alterations.

• The ASCT shall report all intermediate calculated values that are affected by calibration parameters.

• The ASCT shall maintain a log of all signal state alterations directed by the ASCT.

4.11.0-3 The system operator needs to store and report data that can be used to measure traffic performance under adaptive control.

• The ASCT shall store results of all signal timing parameter calculations for a minimum of 90 days.

4.11.0-4 The system operator needs to store all operational data and signal timing parameters calculated by the adaptive system, and export selected data to a network drive.

• The ASCT shall export its systems log in the following formats:

o MS Excel

Concept of Operations Statements System Requirements

Reference Number o Text o CSV o Open source SQL database

• The ASCT shall store the event log for a minimum of 90 days.

• The ASCT shall provide data storage for a system size of 50 signal controllers. The data to be stored shall include the following:

o Controller state data o Reports o Log data o Security data o ASCT parameters o Detector status data

• The ASCT shall store data logs in standard databases supporting SQL queries with an open schema.

4.11.0-5 The system operator needs to report performance data in real time to Regional Archive Data Server (RADS). (Preferred)

• The ASCT shall send operational data to Regional Archive Data Server (RADS) external system. Operational data will at minimum include the standard high-resolution data for ATSPMs.

Transmission of the data logs will occur at minimum once per 15 minutes.

4.11.0-6 The system operator needs to be able to report the exact state of signal timing and input data for a specified period, to allow historical analysis of the system operation.

• The ASCT shall log the following events:

o Time-stamped vehicle phase calls o Time-stamped pedestrian phase calls o Time-stamped emergency vehicle preemption calls o Time-stamped railroad preemption calls o Time-stamped start and end of each phase o Time-stamped controller interval changes o Time-stamped start and end of each transition to a new timing plan.

4.11.0-7 The ASCT system needs to have the ability to generate historic and real-time reports that effectively support operation, maintenance and reporting of system performance and traffic conditions.

• The ASCT shall calculate and report relative data quality including:

o The extent data is affected by detector faults o Other applicable items

• The ASCT shall report comparisons of logged data when requested by the user:

o Day to day, o Hour to hour o Hour of day to hour of day o Hour of week to hour of week o Day of week to day week o Day of year to day of year

Concept of Operations Statements System Requirements

Reference Number

• The ASCT shall report stored data in a form suitable to provide explanations of system behavior to public and politicians and to troubleshoot the system.

• The ASCT shall maintain a log of all signal state alterations directed by the ASCT.

• The ASCT log shall include all events directed by the external inputs.

• The ASCT log shall include all external output state changes.

• The ASCT log shall include all actual parameter values that are subject to user-specified values.

• The ASCT shall maintain the log for a user-defined period.

• The ASCT shall archive the log to a local network drive, or in some other user-defined manner.

4.12 Failure Notification

4.12.0-1 The system operator needs to immediately notify maintenance and operations staff of alarms and alerts.

• In the event of a detector, communications, or adaptive processor failure, the ASCT shall issue an alarm to user-specified recipients.

• The ASCT system shall send an email, text message, or other user defined notification to all authorized recipients.

• The ASCT shall issue an alarm within 1 minute of detection of a failure.

4.12.0-3 The ASCT shall maintain a complete log of alarms and failure events.

• In the event of a failure, the ASCT shall log details of the failure in a permanent log.

• The permanent failure log shall be searchable, archivable, and exportable.

• In the event of a communications failure, the ASCT shall log details of the failure for a minimum of 90 days.

4.13 Preemption and Priority

4.13.0-2 The system operator needs to accommodate emergency vehicle preemption. When an intersection responds to an EV preemption, other signals within the coordinated group continue to operate adaptively. The preempted signal returns to adaptive control once the preemption is released.

• The ASCT shall resume adaptive control of signal controllers when preemptions are released.

• The ASCT shall operate normally at non-preempted signal controllers when special functions are engaged by a preemption event. (Examples of such special functions are a phase omit, a phase maximum recall or a fire route.)

4.14 Failure and Fallback

4.14.0-1 The system operator needs to fall back to TOD or isolated free operation, as specified by the operator, without causing disruption to traffic flow, in the event of equipment, communications and/or software failure.

• The ASCT shall release control to central system control when adaptive control fails.

• The ASCT shall switch to the alternate operation in real time without operator intervention.

• The ASCT shall release control to local operations to operate under its own time-of-day schedule.

• The ASCT shall use the following alternate data sources for operations in the absence of the real-time data from a detector:

o Data from a user-specified or automatically identified alternate detector, such as a detector in an adjacent lane on the same approach.

o Historical data gathered by the adaptive system prior to the detector failure.

Concept of Operations Statements System Requirements

Reference Number

• The ASCT shall execute user-specified actions when communications to one or more signal controllers fails within a group.

• In the event of loss of communication to a user-specified signal controller, the ASCT shall release control of all signal controllers within a user- specified group to local control.

• The ASCT shall switch to the alternate operation in real time without operator intervention. During adaptive processor failure, the ASCT shall provide all local detector inputs to the local controller.

4.15 Constraints

4.15.0-1.0-1 The ASCT system is constrained to use City approved controllers.

• The system shall interface with Econolite ASC/3 and Cobalt controllers running either ASC/3 or EOS firmware.

4.15.0-1.0-2 The ASCT system is constrained to use City approved detectors.

• The system shall interface with detectors from all manufacturers.

• The City’s detection type is video.

4.15.0-2 The system operator needs to use equipment and software acceptable under current agency IT policies and procedures.

• The vendor's adaptive software shall be fully operational within the following platforms:

o Windows-PC

4.16 Training and Support

4.16.0-1 The agency needs all staff involved in operation and maintenance to receive appropriate training to operate, adjust, fine-tune, and maintain the ASCT.

• The Contractor shall provide training on:

o ASCT system operations o Troubleshooting o Preventive maintenance and repair of equipment o System configuration o System administration o System calibration

• The Contractor’s training delivery shall include: printed course materials and references, electronic copies of presentations and references.

• The Contractor’s training shall be delivered at the Peoria

TMC.

• The Contractor shall provide a minimum of 24 hours of training for up to 10 staff members, over a period of 6 months.

4.16.0-2 The agency needs the system to fulfill all requirements for the life of the system. The agency therefore needs the system to be maintained to repair faults that are not defects in materials and workmanship.

• The Maintenance Vendor shall provide maintenance according to a separate maintenance contract. That contract should identify repairs necessary to preserve requirements fulfillment, responsiveness in effecting those repairs, and all requirements on the maintenance provider while performing the repairs.

Concept of Operations Statements System Requirements

Reference Number

4.16.0-3 The agency needs the system to fulfill all requirements for the life of the system. The agency therefore needs the system to remain free of defects in materials and workmanship that result in requirements no longer being fulfilled.

• The Vendor shall warrant the system to be free of defects in materials and workmanship for a period of 5 years. Warranty is defined as correcting defects in materials and workmanship (subject to other language included in the purchase documents).

Defect is defined as any circumstance in which the material does not perform according to its specification.

4.16.0-4 The agency needs the system to fulfill all requirements for the life of the system. The agency therefore needs support to keep the software and software environment updated as necessary to prevent requirements no longer being fulfilled.

• The Contractor shall provide routine updates to the software and software environment necessary to preserve the fulfillment of requirements while the maintenance contract is active. Preservation of requirements fulfillment especially includes all IT management requirements as previously identified.

• The Contractor shall respond to requests for software maintenance within a 24-hour period.

4.4. Project Management

4.4.1. The Contractor shall provide a Project Manager that will oversee the project throughout its duration. If the Project Manager becomes unable to oversee the project, a new Project Manager shall be made available and will be subject to approval by ADOT and the City.

4.4.2. The Contractor shall maintain a list of staff from the Contractor’s firm, ADOT, and the City who shall be informed of all decisions, concerns, changes, and progress related to the project.

4.4.3. The Contractor shall develop and maintain a schedule indicating all project milestones and deliverables.

4.4.3.1. The schedule shall be provided within two weeks of project initiation and will be subject to review and approval from ADOT and the City.

4.4.3.2. ADOT and the City shall provide any review comments and/or approvals to the Contractor within 14 days.

4.4.4. The Contractor shall hold a weekly status update meeting to discuss schedule and action item updates for the project team. The meeting shall include key staff from the Contractor’s firm, ADOT, and the City. The schedule and action items shall be updated and discussed each week to demonstrate progress, notify of any delays, and keep the team apprised of the status of all action items.

4.4.5. Materials furnished for this project shall conform to the requirements of this contract.

Materials shall be new, current production, and free from defects in design materials and workmanship.

4.4.6. The Contractor shall verify all quantities prior to ordering equipment or starting work. Any change to the quantities or scope of work following the start of the project must be reviewed and approved by ADOT and the City. Any extra or new work, not previously approved, that is done beyond the approved Contract Purchase Order will not be eligible for payment.

4.4.7. The Contractor shall inspect all signal poles, mast arms, cabinets, and conduit at each intersection prior to ordering equipment. The inspections shall certify that the intended ASCT equipment will be compatible with existing traffic signal infrastructure and software.

4.5. Furnish Software and Equipment

4.5.1. The Contractor shall furnish all necessary equipment and software required for the complete installation of an ASCT system at the specified intersections. All equipment and software shall conform to the requirements set forth in Section 4 of this scope of work.

4.5.2. The Contractor shall coordinate with the City for ASCT implementation and/or improvements at Deer Valley Road / Lake Pleasant Parkway intersection. This shall be done prior to ordering any equipment or software.

4.5.3. The ASCT system shall operate using the City’s existing video detection or Contractor supplied video detection. Any Contractor supplied detection shall be fully accessible, configurable, and adjustable from the City’s TMC.

4.5.4. The Contractor shall furnish and install the number of servers necessary to host and operate the ASCT software as specified in Section 4 of this scope of work.

4.5.5. The Contractor shall develop a schematic diagram(s) identifying the existing and proposed devices installed at each impacted signal. The diagram will show how the signals will connect with existing infrastructure and how the ASCT system will be linked to the network.

4.5.6. All equipment must have a certificate of compliance.

4.6. Installation

4.6.1. The scope of this document covers the installation and implementation of an Adaptive Signal Control Technology (ASCT) system at existing signalized intersections along two corridors in the City (Project). The Project corridors are:

4.6.1.1. Lake Pleasant Parkway, Loop 303 to 83rd Avenue (ADOT TRACS: T0295 01X)

4.6.1.2. Deer Valley Road, 107th Avenue to 79th Avenue (ADOT TRACS: T0453 01X)

4.6.2. The Project locations are defined in Exhibits 3 & 4, Proposed ASCT Project Intersections.

4.6.3. This project will add adaptive capabilities to the existing coordinated signal system.

4.6.4. All the capabilities of the existing coordinated system will be maintained.

4.6.4.1. The existing traffic signal communication and detection hardware and software shall remain in place at all Project intersections, unless otherwise specified by the City.

4.6.4.2. The ASCT system shall utilize the existing traffic control system without removing its ability to control the signals.

4.6.4.3. In the event that the ASCT system is turned off or encounters an error, the existing communication and detection system shall maintain the ability to control the traffic signals, unless otherwise specified by the City.

4.6.5. The ASCT system will be installed at the City’s Traffic Management Center (TMC) or, if distributed, at each project intersection, and will be maintained and operated by City staff. The City’s TMC is a central system used to connect and manage all existing signalized intersections within the City.

4.6.5.1. The City of Peoria TMC is located at :

9875 N. 85th Avenue, Peoria, AZ.

4.6.6. If a new server is necessary for the ASCT system, this shall be installed within the City’s

TMC.

4.6.7. The City shall retain the ability to disable the ASCT and manually control the signal timing parameters at any of the Project intersections.

4.6.8. Traffic control plans must be submitted to the Department prior to field installations if needed

4.6.8.1. An off-duty Law Enforcement Officer shall only be required if the Signals will be offline at any time.

4.6.9. Installation at the signalized intersections shall occur between the hours of 8:30 am and 4:00 Pm Monday through Friday. A City Signal Technician must be onsite whenever a cabinet must be accessed.

4.6.10. Installations shall be coordinated with the City in advance to ensure a City Signal Technician is available.

4.7. System Testing and Acceptance

4.7.1. The Contractor shall test and verify all system components and verify system acceptance.

This verification shall be completed in conjunction with the City and ADOT.

4.7.2. The Contractor shall develop System Acceptance Test (SAT) procedures for review and approval by ADOT and the City. The proposed SAT procedures shall be provided to the City and ADOT at least 30 days prior to system testing.

4.7.3. The SAT procedures shall provide a detailed description of each test to be performed on the system. The description shall include the purpose of the test and the System Requirement that it aims to verify. The SAT procedures shall include a verification of the conformance of all requirements listed in Section 2.3 of this scope of work.

4.7.4. Following ADOT and City approval of the SAT procedures, the Contractor shall coordinate with the City to determine an appropriate date/time to perform the SAT. The SAT shall demonstrate that the ASCT system is installed completely and accurately according to all System Requirements and contract documents. The SAT shall demonstrate that all system hardware and software is free of defects and operational issues.

4.7.5. The SAT shall consist of a 30-day testing period. During the testing period there shall be no failure of any Contractor-supplied materials. During the testing period, the Contractor shall maintain full access for all appropriate Contractor firm and City staff to be able to inspect equipment and verify operations.

4.7.6. The Contractor shall provide all staff and equipment needed to run the SAT and to correct any errors or issues found during testing. Technical staff from the Contractor’s firm who are familiar with the construction and intended operation of each system component shall be available to be on site to address issues within 24 hours of notification. The Contractor shall work with the City as needed to determine the correct solution required to be made in the Contractor supplied materials.

4.7.7. The Contractor shall maintain a log of all testing performed. The Contractor shall submit a sample testing log to the City as part of the equipment submittal process at the project start. The testing log shall also contain information about any reported system failure. At a minimum the following information shall be reported about any failure event

4.7.7.1. Date and time of event

4.7.7.2. Name of staff who reported the event

4.7.7.3. Description of the failure event

4.7.7.4. Notification of City engineer/appropriate staff

4.7.7.5. Description of troubleshooting performed

4.7.7.6. Date and time failure repair was completed

4.7.8. The following requirements apply to “Minor SAT Failures”

4.7.8.1. A minor SAT failure includes the failure of any Contractor-furnished equipment, or the failure of an entire communications circuit for more than fifteen (15) minutes, over any continuous twenty-four (24) hour period.

4.7.8.2. If a minor SAT failure occurs, any equipment that is deemed necessary to repair or replace shall be done so at no cost to the City. Following repair or replacement of any equipment, the testing can be repeated to ensure that the equipment successfully passes the SAT.

4.7.8.3. The Contractor shall supply all equipment necessary to test and troubleshoot the system.

4.7.8.4. If a minor SAT failure occurs, the 30-day test period shall be suspended until the equipment is repaired or replaced. The testing shall be recommenced following completion of the equipment repair or replacement. An additional twenty-four (24) hours shall be added to the remaining SAT testing time.

4.7.8.5. If a minor SAT failure occurs as a result of an issue or malfunction with the City communication system, the SAT will be suspended until the systems are repaired or restarted by the City. The testing shall recommence following successful repair or restart of City communications. The SAT schedule will not be impacted by this suspension; for instance, if five days of SAT were completed prior to the suspension, only twenty-five will remain in order to satisfy the SAT.

4.7.9. The following requirements apply to “Major SAT Failures”

4.7.9.1. A major SAT failure includes three communication failures of Contractor-furnished equipment, if it is determined that the failures were caused by improper installation by the Contractor, or, Contractor failure to correct an issue that adversely impacts public safety within four hours of notification.

4.7.9.2. The Contractor shall supply all equipment necessary to test the system.

4.7.9.3. If a major SAT failure occurs, the 30-day test period shall be halted. The testing shall recommence following completion of any necessary equipment repair or replacement. Following any equipment repair or replacement, the SAT will recommence but will be reset to day “0” of the 30 day SAT period.

4.7.9.4. All errors found during the SAT shall be corrected, with corrections approved by the Contractor and the City prior to the completion of the SAT.

4.8. Training and Documentation

4.8.1. The Contractor shall provide training to all necessary City staff in accordance with the

System Requirements set forth in Section 2.3 of this scope of work. System training shall include:

4.8.1.1. All ASCT system operations

4.8.1.2. System troubleshooting

4.8.1.3. Preventative equipment maintenance and repair

4.8.1.4. System configuration

4.8.1.5. System administration

4.8.1.6. System calibration

4.8.2. The Contractor shall deliver the ASCT system training at the City TMC.

4.8.3. The Contractor shall provide electronic and hard copy of all course materials, references, and presentations.

4.8.4. The Contractor shall deliver the ASCT system training in person to a minimum of ten (10)

City staff. Training shall occur over a minimum of three (3) cumulative days. The Contractor shall provide a minimum of three in-person (3) training sessions to City staff over a six (6) month period.

4.8.5. The Contractor shall provide a package of documentation for all ASCT system software and hardware installed with this project. The documentation package shall be submitted to ADOT and the City for review and approval prior to final acceptance. The documentation package shall include:

4.8.5.1. Drawings, including all electrical, power distribution, wiring, etc.

4.8.5.2. Schematics,

4.8.5.3. System architecture diagrams,

4.8.5.4. A software configuration report for each traffic signal in the system

4.8.5.5. All manuals and procedural documents that describe the use and maintenance of the system.

4.9. Maintenance, Support and Warranty

4.9.1. The Contractor shall provide support to the City for maintenance, support, and warranty of all equipment in accordance with Section 4 of this scope of work.

4.9.2. The Contractor shall include a maintenance contract as part of the overall project contract to maintain all software and hardware installed as part of the project. Under the maintenance contract, the Contractor shall also assist the City with providing routine maintenance to the project equipment. The Contractor shall also assist the City with any repairs or replacements that are required to the system components for the duration of the maintenance contract.

4.9.3. The maintenance contract shall remain active for a period of five (5) years.

4.9.4. The Contractor shall provide periodic software updates to maintain the acceptability of the ASCT system according to the requirements set forth in Section 2.3 of this scope of work for the duration of the maintenance contract.

4.9.5. The Contractor shall warranty all system components to be free of defects in materials and to be of sound workmanship for a period of five (5) years. A defect is defined as any event in which the equipment does not execute according to its intended and stated specification.

4.10. Project Locations

4.10.1. The ASCT system shall be installed and implemented at the following intersections:

4.10.2.

ADOT TRACS No. Corridor Study Intersections

T0295 01X

Lake Pleasant Parkway, Loop 303 to 83rd Avenue

1. Loop 303 / Lake Pleasant Parkway

2. Dixileta Drive / Lake Pleasant Parkway

3. Westwing Parkway / Lake Pleasant Parkway

4. Pinnacle Vista Drive / Lake Pleasant Parkway

5. Jomax Road / Lake Pleasant Parkway

6. Yearling Road / Lake Pleasant Parkway

7. Lake Pleasant Crossing / Lake Pleasant Parkway

8. Happy Valley Road / Lake Pleasant Parkway

9. Hatfield Road / Lake Pleasant Parkway

10. Calle Lejos / Lake Pleasant Parkway

11. Pinnacle Peak Road / Lake Pleasant Parkway

12. Williams Road / Lake Pleasant Parkway

13. Deer Valley Road / Lake Pleasant Parkway1

14. Lake Pleasant Road / Lake Pleasant Parkway

15. 95th Avenue / Lake Pleasant Parkway

16. 91st Avenue / Lake Pleasant Parkway

17. 87th Avenue / Lake Pleasant Parkway

18. 83rd Avenue / Lake Pleasant Parkway

19. Beardsley Road / Lake Pleasant Parkway/83rd Avenue

ADOT TRACS No. Corridor Study Intersections

20. Oraibi Drive / Lake Pleasant Parkway/83rd Avenue

21. Village Parkway / Lake Pleasant Parkway/83rd Avenue

22. Wescott Drive / Lake Pleasant Parkway/83rd Avenue

T0453 01X

Deer Valley Road, 107th Avenue to 79th Avenue

1. Deer Valley Road / 107th Avenue

2. Deer Valley Road / Lake Pleasant Parkway*

3. Deer Valley Road / 98th Avenue

4. Deer Valley Road / 95th Avenue

5. Deer Valley Road / 91st Avenue

6. Deer Valley Road / 87th Avenue

7. Deer Valley Road / 83rd Avenue

4.10.3. *The Deer Valley Road / Lake Pleasant Parkway intersection is in both projects (T0295

01X and T0453 01X). The Contractor will be required to coordinate with the City prior to beginning work or ordering equipment.

4.10.4. For a list of current hardware installed at each of the project intersections, see Exhibit 6 - Hardware installed at Project intersection.

4.11. Contractors Responsibilities

4.11.1. The Contractor shall provide adequate qualified staff to perform the Project.

4.11.2. The Contractor shall respond to request for software and hardware maintenance within a twenty (24)-hour period.

4.11.3. The Contractor shall coordinate with City staff to determine an appropriate time to gain entry to the City TMC, and gain access to the City servers and systems that will need to be integrated with the ASCT system.

4.11.4. The Contractor shall install all servers and equipment necessary to operate the ASCT system at the City TMC.

4.11.5. The Contractor shall install and integrate the ASCT software on all servers and necessary workstations in the City TMC. The ASCT software shall be installed on a minimum of seven (7) workstations at the Peoria TMC.

4.11.6. The Contractor shall configure all ASCT parameters and review with City staff prior to deploying the system to the field. The City shall review and approve of all parameters.

Following City approval, the contractor shall deploy the system for field operation.

4.11.7. Once the ASCT system is activated for field operation, the Contractor shall fine-tune all parameters to conform with the requirements in Section 2.3 of this scope of work.

4.11.8. The Contractor shall deploy and fine-tune the ASCT system prior to final approval from the City and ADOT. (line spacing)

4.11.9. The ASCT system must be fully complete to the standards set forth in this scope of work document within 8 months of a purchase order being issued. This schedule can fluctuate in the case of major disruptions in access to field equipment or infrastructure caused by a public health and safety threat, natural disaster, etc.

4.11.10. The Contractor shall notify the Department and the City immediately of any delays or potential deviation from the agreed upon schedule.

4.12. Department Responsibilities

4.12.1. ADOT reserves the right to inspect and approve all Contractor-procured equipment if delivery is made in stages. ADOT’s partial acceptance of the equipment shall not relieve the Contractor’s responsibility to correct any errors, without additional charge, and to provide clarification of ambiguities during the warranty and maintenance period.

4.12.2. ADOT shall provide final project acceptance upon review and approval of all equipment deliveries AND upon notification from the City that all ASCT system software and hardware has been furnished, integrated, passed all required testing, and all components are in good working order.

4.12.3. ADOT shall perform construction inspections to assure that all ASCT system components furnished and installed by the Contractor are done in accordance with the requirements set forth in Section 2.3 of this document.

4.12.4. The Department can reject and require the replacement of any materials ordered by the Contractor that do not meet the specific requirements set forth in Section 4 of this document. The Department is not responsible for any additional costs incurred by the Contractor to replace the materials. The Department reserves the right to inspect the delivered materials within fifteen (15) calendar days from the date of receipt.

4.13. City’s Responsibilities

4.13.1. The City shall be responsible for any repair or replacement of the following equipment that is deemed necessary for the successful operation of the ASCT system components:

4.13.1.1. Any existing communications equipment or any communications equipment not supplied by the Contractor.

4.13.1.2. Traffic controllers

4.13.1.3. Traffic controller cabinets and all other cabinet hardware, cables, and devices not supplied by the Contractor.

4.13.1.4. Traffic detection devices and associated equipment not supplied by the Contractor.

4.13.1.5. Other related signal operations infrastructure, including signal poles and appurtenances, cabinet foundations, pull boxes, and related wiring.

4.13.2. The City shall be responsible for repair or replacement of any of the following equipment that is deemed necessary for successful operation of ASCT software:

4.13.3. City-owned communications equipment in the TMC.

4.13.4. City-owned workstations and related peripherals.

4.13.5. City-owned Operating System software, browsers, and related standard general applications software (i.e. Microsoft Windows, PDF readers, etc.)

SPECIAL TERMS AND CONDITIONS

1. CONTRACT TERM

The term of any resultant contract shall commence on the effective day of award and shall continue for a period of twelve months (12) thereafter, unless terminated, cancelled or extended as otherwise provided herein.

2. CONTRACT EXTENSION

By mutual written contract amendment, any resultant contract may be…