4-Attachment B - Supplemental Technical Specifications.pdf
PDF 157 KB Posted
- Attached to
- TSP Cloud-Based Construction
- Solicitation number
- 2024-08
- Issued by
- Alameda County, California
About this file
This is a supplemental technical specifications document for the Livermore Amador Valley Transit Authority (LAVTA) Cloud-Based Transit Signal Priority (TSP) System Upgrade Project, a construction contract involving the Cities of Livermore, Dublin, and Pleasanton in California. The project requires contractors to furnish, install, configure, and test NTCIP 1211-compliant TSP modules and associated traffic signal equipment across multiple signalized intersections. The contractor is responsible for removal of existing equipment, field integration with communications networks, and coordination of field testing and commissioning activities. LAVTA and its designated cloud-based TSP vendor retain sole responsibility for cloud system configuration, central system integration, and priority request processing. The contractor must submit a cutover plan for approval prior to any equipment replacement, provide a minimum of three working days advance notice to LAVTA and applicable city agencies before work begins, limit field work to one intersection per city at a time unless otherwise authorized, and submit permit applications no later than ten working days before construction activities.
The specifications require contractors to provide training at a minimum of one session per city covering system operation, troubleshooting, and maintenance at no additional compensation. Contractors must submit a baseline construction schedule prior to mobilization and provide regular progress updates. All costs associated with system integration, coordination, and testing must be included in bid prices, with network coordination and troubleshooting activities not eligible for separate payment. Warranty response is required within 48 hours during the warranty period, with documentation maintained in a warranty log. Final deliverables must include controller configurations, TSP settings, firmware versions, testing records, and as-built documentation in editable electronic format. Acceptance testing requires verification of hardware operation, successful communication with the cloud-based TSP system, and demonstration of one to two successful TSP priority requests per approach. Liquidated damages apply only to delays in final completion of physical work and do not apply to administrative tasks unless explicitly stated.
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
LAVTA Cloud-Based TSP Solution – Supplemental Technical Specifications
SECTION 4 – SCOPE OF WORK
Add to Section 4-1.01A
4-1.01A Roles and Responsibilities
The responsibilities of the parties under this Contract are as follows:
• Contractor Responsibilities:
o Perform all field-related work including furnishing, installing, configuring, and testing traffic signal controllers, controller cards, firmware, and NTCIP 1211-compliant TSP modules.
o Perform removal of existing equipment identified in the Contract Documents.
o Perform all field integration required to connect equipment to existing communications networks.
o Coordinate field testing and commissioning activities.
• LAVTA / Cloud Vendor Responsibilities:
o LAVTA and its designated cloud-based TSP vendor are solely responsible for cloud system configuration, central system integration, and priority request processing.
o Contractor shall not be responsible for procurement, licensing, or configuration of the cloud-based platform unless explicitly stated.
No additional compensation will be provided for work arising from misinterpretation of responsibilities.
Add to Section 4-1.01B
4-1.01B Cutover Plan
Prior to any equipment replacement, the Contractor shall submit a cutover plan for review and approval.
The plan shall include:
• Sequence of removal and installation activities
• Traffic signal operational impacts
• Temporary control measures
• Contingency / rollback procedures in the event of failure
No field cutover work shall begin without an approved plan.
Add to Section 4-1.01C
4-1.01C Work Sequencing Limitations
The Contractor shall:
• Perform work on no more than one (1) intersection per city at a time, unless otherwise authorized in writing by the Engineer
• Sequence work to minimize disruption to traffic and transit operations
Add to Section 4-1.01D
4-1.01D Advance Coordination
The Contractor shall provide a minimum of three (3) working days advance notice to:
• LAVTA
• The applicable City agency prior to performing work at any intersection.
Add to Section 4-1.01E
4-1.01E Training Requirements
Where new or modified equipment or procedures are introduced, the Contractor shall provide:
• A minimum of one (1) training session per city (and LAVTA if applicable)
• Instruction covering basic system operation, troubleshooting, and maintenance
Training is considered incidental to the Contract and no additional payment will be made.
Add to Section 4-1.01F
4-1.01F Final Deliverables Package
Prior to final acceptance, the Contractor shall provide a complete electronic deliverables package including:
• Final controller configurations and databases
• TSP settings and parameters
• Firmware versions
• Testing records
• As-built documentation (in editable format)
Add to Section 4-1.01G
4-1.01G Acceptance Testing
The Contractor shall coordinate with LAVTA and the cloud vendor to perform final acceptance testing.
Acceptance shall require:
• Verification of proper hardware operation
• Successful communication with the cloud-based TSP system
• Demonstration of a minimum of one (1) to two (2) successful TSP priority requests per approach, unless otherwise approved
Work shall not be considered complete until testing is successfully completed and documented.
SECTION 5 – CONTROL OF WORK
Add to Section 5-1.20B(2)
5-1.20B(2) Permit Coordination Timeline
The Contractor shall initiate permit applications no later than ten (10) working days prior to planned construction activities.
Add to Section 5-1.26A
5-1.26A Pre-Construction Site Verification
Prior to beginning work, the Contractor shall verify the condition of:
• Traffic signal cabinets
• Conduits
• Existing infrastructure
Any deficiencies shall be documented and reported prior to construction. Failure to verify existing conditions shall not constitute grounds for additional compensation.
Add to Section 5-1.27B
5-1.27B As-Built Documentation (Expanded)
As-built requirements shall include:
• Marked plan sets
• Final electronic configuration files
• Controller databases
• Firmware versions
All files shall be provided in native editable format, not PDF only.
Add to Section 5-1.36E:
5-1.36F Protection of Survey Monuments
The Contractor shall not perform construction activities within five (5) feet of any survey monument without written authorization.
Add to Section 5-1.47:
5-1.47A Warranty Response Requirements
During the warranty period:
• Contractor shall respond to service requests within 48 hours
• Maintain a warranty log documenting:
o Issue description o Date reported o Corrective action o Resolution date
SECTION 7 – LEGAL RELATIONS
Add to Section 7-1.02K(5):
• Work hour exceptions must be approved by:
o LAVTA and o The applicable City agency
7-1.02K(6) Extended Hours Request
Requests for extended work hours shall be submitted at least three (3) working days in advance.
SECTION 8 – PROSECUTION AND PROGRESS
Add to Section 8-1.10A:
8-1.10B Schedule Requirements
The Contractor shall submit:
• A baseline construction schedule prior to mobilization
• Regular updates reflecting actual progress
8-1.10C Liquidated Damages Clarification
Liquidated damages apply to delays associated with:
• Final completion of physical work
Liquidated damages do not apply to administrative tasks unless explicitly stated.
SECTION 9 – PAYMENT
Add to Section 9-1.03:
• All costs associated with system integration, coordination, and testing shall be included in bid prices.
• Network coordination and troubleshooting activities shall not be paid as separate items.
SECTION 10 – GENERAL
Add to Section 10.7:
10.7.02 System Compatibility
The Contractor shall:
• Verify compatibility of all equipment with each city’s traffic management system prior to installation
• Coordinate with city IT and traffic engineering staff as required
SECTION 12 – TEMPORARY TRAFFIC CONTROL
Add to Section 12-4.02A:
• Contractor shall submit a site-specific traffic control plan for each intersection
• Provide advance notice for any work affecting bus operations
• Maintain uninterrupted access for transit vehicles at all times
SECTION 15 – EXISTING FACILITIES
Add to Section 15-1.01:
• Contractor shall properly dispose or recycle salvaged equipment at approved facilities
• Contractor shall protect all emergency vehicle preemption equipment and ensure continuous operation
• Any damaged or missing components shall be reported immediately
SECTION 87 – ELECTRICAL SYSTEMS
Add to Section 87-10.01:
87-10.01E Software and Firmware Verification
The Contractor shall verify all firmware and software versions prior to installation.
87-10.01F Cloud Vendor Coordination
The Contractor shall coordinate with the cloud vendor to confirm compatibility prior to programming or installation.
87-10.01G Testing Procedures Submittal
The Contractor shall submit testing procedures for approval by LAVTA and all applicable agencies prior to execution.
87-10.02F Data Verification
The Contractor shall verify that installed equipment:
• Broadcasts required data
• Uses the correct format for cloud-based TSP operation
87-10.03B Backup Configuration
The Contractor shall create and submit a backup of configuration settings for each intersection.
File details come from the government source that posted it. Updated .