2-Exhibit A - Scope of Services.pdf

DOT-ITB-25-4007-CO

EXHIBIT A – SCOPE OF SERVICES

A- 1 OF 9

State of Florida Department of Transportation

EXHIBIT A - SCOPE OF SERVICES

CLOUD BASED ARTERIAL MANAGEMENT (CBAM)

REGIONAL PLATFORM FOR TREASURE COAST

FOR

FLORIDA DEPARTMENT OF TRANSPORTATION –

DISTRICT FOUR

FINANCIAL PROJECT #: 453821-1-93-01 & Various

A- 2 OF 9

1. PURPOSE

The Florida Department of Transportation (FDOT) District Four is launching the Cloud-Based Arterial Management (CBAM) program in the Treasure Coast Region to support local Agencies. To support its operation, FDOT District Four is seeking bids from qualified vendors for the procurement, integration, and deployment of the necessary devices and software for the arterial program to function. This initial procurement will establish the foundation for CBAM, with a core focus on deploying a turn-key ATMS regional platform providing both cloud-based software and hybrid on-premise solutions with access for multiple users.

2. SIGNAL MAINTAINING AGENCY INVOLVEMENT

The CBAM program will initially be implemented in coordination with four Signal Maintaining Agencies (SMAs): Indian River County, Martin County, Saint Lucie County, and the City of Port Saint Lucie. All proposed solutions and devices must be compatible with the SMA’s existing infrastructure. In the case of upgrades or replacement of existing devices efforts should be made to identify SMA’s preferred solution for the purpose of compatibility and continued maintenance.

3. DEVICES AND SERVICES TO BE PROVIDED

The selected vendor shall provide all hardware, software, installation, integration, and support services necessary to deploy and maintain the base level needs for the CBAM! program as defined below. All software and hardware provided must be compatible with existing signal maintaining agency infrastructure. The scope includes, but is not limited to, the following:

ATMS Regional Platform (178 units) – Provide a regional platform for real-time monitoring and cloud-based access to the regional traffic signal system across the four identified SMAs.

The regional platform will include a minimum of 178 identified locations and must be compatible with each SMA’s existing in field controllers and signal system. The regional platform will allow FDOT and other invested agencies at a minimum read-only access to the signal timing controllers and will include security measures. The regional platform must be capable of expanding to include future intersections.

Private Cloud Hosted Device Manager (1 unit) – St. Lucie County intends to have a fully cloud hosted solution, with no hardware. Currently they have a hybrid solution, but intend to remove all hardware for a pure cloud based solution. This device is intended to support that intention specifically for St. Lucie County.

Real-Time Signal Optimization Software (16 units) – An add on option to the regional platform for 16 intersections equipped with a solution that can analyze traffic patterns and dynamically adjusting signal timing to optimize flow in real time.

Bluetooth with CV-RSU Element (8 units) – A unit that capable of collecting travel time data through Bluetooth and includes Connected Vehicle (CV) - Roadside Unit (RSU) components. A single corridor in Martin County is intended to be outfitted with 8 of these units.

Bluetooth Detection (8 units) – Additional 8 Bluetooth devices are intended to be equipped at various locations within the SMAs for the purpose of measuring travel time and congestion levels across the roadway network through Bluetooth detection.

A- 3 OF 9

GPS Time Clock (11 units) – GPS timeclocks for Martin County within 11 controllers will be deployed for the purpose of synchronizing timekeeping across signal controllers.

Vehicle Detection System – Traditional Cameras (7 units) – Equipment used to detect vehicle presence and movement for signal timing adjustments at 7 intersections in Martin County, St. Lucie County, and Indian River County. Each approach for each intersection will be outfitted with video detection cameras.

Uninterrupted Power Supply (UPS) (10) – Backup power solutions to maintain system functionality during power disruptions installed at 10 traffic signal cabinets in Martin County and St. Lucie County.

Traffic Signal Controller (6 units) – New signal controllers at 6 locations for City of Port St. Lucie to support the regional platform functionalities.

Traffic Signal Controller Cabinet (10 units) – Replacement of 10 existing signal controller cabinets for Indian River County to support the regional platform and program growth.

PTZ Camera (8 units) – Pan-Tilt-Zoom cameras for remote monitoring and traffic surveillance at 6 locations for St. Lucie County.

Multi-Device Field Modem for CCTV Streaming (5 units) – 5 portable communication devices for real-time streaming video and data transmission including multiple modem ports.

Field Modem Device Server (1 unit) – Ongoing technical support and service for the multi-device field modems.

4. TECHNICAL REQUIREMENTS

4.1. General Requirements

4.1.1. The Vendor shall identify a single point of contact to support the Department as Project Manager.

4.1.2. The Vendor shall develop a Testing Plan for review and approval by the Department. The Testing Plan shall clearly identify procedures and pass/fail criteria for testing individual components and system functionality of the CBAM! program. The Department will utilize the Testing Plan to validate and accept the successful deployment prior to payment to the Vendor. Components or devices that fail testing shall be repaired or replaced as necessary and re-tested. ‘In the event a single component or device fails testing two (2) times, the item shall be replaced in its entirety and tested again.

4.1.3. It shall be the Vendor’s responsibility to provide any ancillary equipment such as cables, connectors, mounting rails, etc. with the provided hardware for a fully functional system.

4.1.4. Delivery of devices needs to be coordinated with the FDOT Project Manager prior to delivery.

4.2. ATMS Regional Platform

4.2.1. General Requirements

4.2.1.1. The regional platform must provide a remote view of the SMA’s controllers at a minimum of 178 identified intersections with an opportunity to assign different levels of accessibility for adjustments to be made.

4.2.1.2. The regional platform will be supported for a minimum of 3 years

4.2.1.3. All software, devices and hardware needed for the regional platform to be fully functional must be provided and configured for each SMA and FDOT

A- 4 OF 9

4.2.1.4. A cloud-hosted or hybrid deployment option shall be available for flexibility in infrastructure planning. The SMA’s infrastructure setup shall be as follows:

4.2.1.4.1. Martin County – Hybrid system (Cloud-based and server on premise)

4.2.1.4.2. Indian River County– Hybrid system (Cloud-based and server on premise)

4.2.1.4.3. St. Lucie County – full cloud-based system

4.2.1.4.4. City of Port St. Lucie – full cloud-based system

4.2.1.5. The regional platform must be able to communicate with field devices using the National Transportation Communications for Intelligent Transportation System (ITS) Protocols (NTCIP), provided those field devices can communicate using

NTCIP.

4.2.1.6. The regional platform must provide a web-based user interface through which users can access system functionality in addition to any traditionally installed software.

4.2.2. System Access & User Security

4.2.2.1. The regional platform shall provide secure, role-based access to authorized users through multi-factor authentication (MFA).

4.2.2.2. User accounts shall be managed by system administrators, supporting configurable access permissions and audit logs.

4.2.2.3. Authentication mechanisms shall include HTTPS encryption and compliance with cybersecurity standards to protect user credentials and sensitive data.

4.2.2.4. System access shall be available via a web-based interface with no requirement for proprietary software installations.

4.2.2.5. Logs of all user activity, security events, and configuration changes shall be maintained for audit and compliance purposes.

4.2.3. Performance Measurement Features

4.2.3.1. The regional platform shall generate performance reports and trend analyses, exportable in standard formats (CSV, PDF).

4.2.3.2. A dashboard interface shall provide customizable visualizations of system performance, including heat maps, data-driven alerts, and detector failure alerts.

4.2.3.3. It shall enable real-time scenario testing and predictive modeling for traffic signal optimization and congestion management.

4.2.4. Traffic Controller Access & Management

4.2.4.1. The regional platform shall provide remote access to traffic signal controllers, supporting real-time monitoring and configuration updates.

4.2.4.2. Communication with field controllers shall be established via secure protocols such as NTCIP, FTP, SNMP, and Web Services.

4.2.4.3. The regional platform shall allow scheduling of signal timing updates and remote diagnostics to reduce field visits.

4.2.4.4. A central database shall store controller configurations, event logs, and performance history for analysis and troubleshooting.

4.2.5. Compatibility with Existing Controllers

4.2.5.1. The regional platform shall be compatible with the SMA’s existing traffic controllers currently deployed in the field. The current field controllers are as follows:

4.2.5.1.1. Martin County – Econolite Cobalt

4.2.5.1.2. Indian River County– Econolite Cobalt

4.2.5.1.3. St. Lucie County – Econolite Cobalt

4.2.5.1.4. City of Port St. Lucie – Econolite Cobalt and Trafficware 980 TS2

4.2.5.2. Controller firmware updates and configuration changes shall be managed remotely via the regional platform interface.

A- 5 OF 9

4.2.6. System Scalability & Integration

4.2.6.1. The regional platform shall be modular and scalable, supporting regional expansion and additional traffic management modules for future growth.

4.2.6.2. Integration with existing and new video and radar detection systems, connected vehicle technologies, and third-party data sources shall be supported for future growth.

4.2.6.3. API capabilities shall allow for external system interoperability, enabling data exchange with transportation agencies and third-party applications.

4.2.7. Training and Documentation

4.2.7.1. The Vendor shall provide each SMA (Martin County, St. Lucie County, City of Port

St. Lucie, and Indian River County) and FDOT either remote or in person training by a qualified technician in the proper operations, troubleshooting, configuration, administration, and calibration of the system, as well as, on preventive maintenance and repair of equipment.

4.2.7.2. The Vendor shall be responsible for providing all material necessary for the training session including, but not limited to:

Printed course materials Electronic copies of presentations System operations manuals

4.2.7.3. The Vendor shall also provide electronic and printed version of the manuals and references for all hardware and software supplied by the Vendor as part of the regional platform deployment. Materials shall include, but not be limited to:

User manuals Maintenance manuals Troubleshooting manuals

4.3. Private Cloud Hosted Device Manager

4.3.1. This Device Manager shall be provided to St. Lucie County to ensure that no hardware is needed for the regional platform to function

4.3.2. The device manager shall enable secure, centralized monitoring, configuration, and firmware management for field devices via cloud-based access.

4.3.3. The device manager will be cloud-based hosted, with no hardware or physical device needs.

4.4. Real-Time Signal Optimization Software

4.4.1. Software that supports signal timing optimization based on real-time traffic conditions.

4.4.2. Optimization features shall include cycle length adjustments, split time modifications, offset tuning, and coordination adjustments.

4.4.3. A rollback mechanism shall be available to revert to previous signal timing settings if needed.

4.4.4. The system shall allow simulation and previewing of proposed timing changes before deployment.

4.4.5. The solution shall be integrated into the regional platform

4.5. Travel Time Unit with CV/RSU Element

4.5.1. The Vendor shall provide Bluetooth travel time units with built in road side unit capabilities.

4.5.2. The units must have the ability to determine travel time based on Bluetooth readers.

4.5.3. The units must be compatible with existing devices and software

4.5.4. The unit must be capable of translating Connected Vehicle (CV) immediate forward messages (IFM) into the appropriate format compliant with Society of Automotive Engineers (SAE) J2735 standard to be transmitted by the roadside unit (RSU).

A- 6 OF 9

4.5.5. RSUs shall be provided with C-V2X capabilities and must be configurable to run at a minimum, the listed CV applications –TIM, RSA, and BSM. RSU shall be compatible with 5G and support C-V2X direct communications (LTE V2X PC5 mode 4), defined by 3GPP, Release 14 (or later).

4.5.6. The Vendor shall be responsible for providing all hardware necessary for a complete installation, including RSU mounting brackets and hardware; surge protection device (SPD) to be installed at the device; Power-over Ethernet (POE+) injector w/ AC adaptor power supply

4.5.7. The Vendor shall provide an RSU that meets the following standards:

Connected Vehicle Equipment Requirements and Standards Document Identifier Description 3GPP, Release 14 (or later) https://www.3gpp.org/ftp/Specs/latest/Rel-14

IEEE 1609.0-2013 (or later)

IEEE Guide for Wireless Access in Vehicular Environments (WAVE) – Architecture

IEEE 1609.2-2016 (or later)

IEEE Standard for WAVE – Security Services for Applications and Management Messages

IEEE 1609.3-2016 (or later)

IEEE Standard for WAVE – Networking Services

IEEE 1609.4-2016 (or later)

IEEE Standard for WAVE – Multi-Channel Operation

IEEE 1609.12-2016 (or later)

IEEE Standard for WAVE – Identifier Allocations

IEEE 802.3at-2009 Standard for Power over Ethernet

4.6. Bluetooth Detection

4.6.1. The Vendor shall provide Bluetooth travel time units with the ability to determine travel time based on Bluetooth readers.

4.6.2. The units must be compatible with existing devices and software

4.7. GPS Time Clock

4.7.1. The GPS time clocks shall support NTP and direct GPS-based timing to ensure accurate coordination of signal operations.

4.7.2. It shall be compatible with NEMA TS2 controllers, automatically adjusting for daylight saving time and leap seconds.

4.8. Vehicle Detection System

4.8.1. Vehicle Detection Camera shall provide high-accuracy real-time vehicle detection for intersection traffic management.

4.8.2. The system shall utilize advanced AI-based image processing to differentiate between vehicles, bicycles, and pedestrians.

4.8.3. It shall support multiple detection zones, configurable via a user-friendly interface for optimized traffic flow.

4.8.4. It shall be compatible with NEMA TS2 traffic controllers and support communication via

Ethernet or wireless connectivity.

4.8.5. Vehicle Detection System shall meet the requirements of FDOT Standard Specifications for Road and Bridge Construction – Section 660, latest version.

4.9. Uninterrupted Power Supply (UPS)

4.9.1. UPS must be compatible with Martin County and St. Lucie County controllers.

4.9.2. The UPS shall comply with NEMA TS2 and UL 508 standards.

A- 7 OF 9

4.9.3. The Vendor shall be responsible for providing all hardware necessary for a complete installation, including mounting brackets and hardware; surge protection device (SPD) to be installed at the device

4.9.4. UPS shall meet the requirements of FDOT Standard Specifications for Road and Bridge Construction – Section 685, latest version.

4.10. Traffic Signal Controller

4.10.1. The traffic signal controller shall be NEMA TS2 Type 2 compliant.

4.10.2. The controller shall have a user-friendly interface for easy configuration and monitoring

4.10.3. It shall support NTCIP communication protocols for seamless integration with the ATMS regional platform

4.10.4. The device shall include multiple Ethernet, USB, and serial ports for flexible connectivity and field device integration

4.10.5. The controller shall be compatible with City of Port St. Lucie’s existing signal system and infrastructure

4.10.6. Traffic Signal Controller shall meet the requirements of FDOT Standard Specifications for

Road and Bridge Construction – Section 671, latest version.

4.11. Traffic Signal Controller Cabinet

4.11.1. The traffic signal cabinet shall be NEMA TS2 Type 1 compliant.

4.11.2. The traffic signal controller must be weather resistant

4.11.3. It shall support standard 19-inch rack-mounted components, including controllers, power supplies, and conflict monitors

4.11.4. The cabinet shall provide modular power distribution, including filtered AC power and surge protection for connected devices.

4.11.5. The cabinet shall include an internal fan for temperature regulation

4.11.6. The cabinet shall include safety mechanisms to prevent unauthorized access

4.11.7. Traffic Signal Controller Cabinet shall meet the requirements of FDOT Standard

Specifications for Road and Bridge Construction – Section 676, latest version.

4.12. PTZ Camera

4.12.1. CCTV cameras will have pan-tilt-zoom capabilities.

4.12.2. CCTV cameras shall meet the requirements of FDOT Standard Specifications for Road and Bridge Construction – Section 682-1, latest version.

4.12.3. Vendor shall be responsible for providing all the hardware necessary for a complete installation, including mounting brackets and hardware; surge protection device (SPD) to be installed at the device; Power-over Ethernet (POE+) injector w/ AC adaptor power supply; and all other equipment identified by the Vendor.

4.13. Multi-Device Field Modem for CCTV Streaming

4.13.1. Multi-Device Field Modem shall support high-bandwidth, low-latency video streaming for real-time CCTV surveillance in traffic management applications.

4.13.2. The device shall utilize multiple cellular network connections (4G/5G) to ensure uninterrupted, high-quality video transmission.

4.13.3. It shall be compact, rugged, and weather-resistant, designed for deployment in outdoor and mobile environments.

4.13.4. The modem shall support IP-based streaming protocols (RTSP, RTMP, NDI, etc.) for seamless integration with traffic management centers.

4.13.5. Equipped with remote management capabilities, allowing for real-time monitoring, diagnostics, and firmware updates over the cloud.

4.14. Field Modem Device Server

A- 8 OF 9

4.14.1. Ongoing technical support, service, and data management plan covering at a minimum 3 years for the multi-device field modems.

5. SUBMITTALS AND OTHER PROJECT RELATED INFORMATION

5.1. The Vendor shall submit a project schedule that clearly identifies targeted project milestones, specific work activities and related time durations for the project such as, but not limited to procurement, coordination, configuration, and testing timeframes.

5.2. Submit proposed training outline for the ATMS regional platform prior to substantial completion for approval by the FDOT.

5.3. Any omissions or lack of detail in the specifications outlined in this Scope of Work shall be interpreted as requiring adherence to the highest industry standards for commercial project services. Only materials and workmanship of superior quality shall be used. All interpretations of this Scope of Work shall be based on this principle.

6. WARRANTY

6.1. The awarded Vendor shall warranty / guarantee all of the work and materials utilized in this project for a period of thirty-six months, which shall commence from the date of invoice acceptance by the Department.

6.2. The Vendor shall upon written notice from the Department, make any needed repairs to the installation at no cost to the Department. Unless otherwise agreed to in writing by the Department, all repairs shall be made and completed by the Vendor within thirty days of the date of the written notice by the Department. This warranty / guarantee shall include all labor, materials and any other costs involved.

6.3. The Vendor shall provide routine updates to the software and software environment necessary to preserve the fulfillment of the requirements.

6.4. The Vendor will provide additional training in the instance software updates are made that change the functionality of the platform.

7. DELIVERY ADDRESS

The successful Vendor will deliver the goods and services to District Four Treasure Coast Operations Office.

Florida Department of Transportation – District Four Treasure Coast Operations Center c/o Kris Kehres 3601 Oleander Avenue Fort Pierce, FL 34982

8. FINANCIAL CONSEQUENCES

Payment shall be made only after receipt and approval of goods and services unless advance payments are authorized by the Chief Financial Officer of the State of Florida under Chapters 215 and 216, Florida Statutes. Deliverable(s) must be received and accepted in writing by the Contract Manager on the Department’s invoice transmittal forms prior to payment. If the Department determines that the performance of the Vendor is unsatisfactory, the Department shall notify the Vendor of the deficiency to be corrected, which correction shall be made within a timeframe to be specified by the Department. The Vendor shall, within five days after notice from the Department, provide the Department with a corrective action plan describing how the Vendor will address all issues of contract non-performance, unacceptable performance, failure to meet the minimum performance levels, deliverable deficiencies, or contract non-compliance. If the corrective action

A- 9 OF 9

plan is unacceptable to the Department, the Vendor shall be assessed a non-performance retainage equivalent to 10% of the total invoice amount. The retainage shall be applied to the invoice for the then-current billing period. The retainage shall be withheld until the vendor resolves the deficiency.

If the deficiency is subsequently resolved, the Vendor may bill the Department for the retained amount during the next billing period. If the Vendor is unable to resolve the deficiency, the funds retained may be forfeited at the end of the agreement period.

***END OF EXHIBIT A – SCOPE OF COMMODITY***