CONNECTED VEHICLES Lessons Learned & Best Practices - 2026 Edition - guidance for planning and design of connected vehicle systems

Sep 15, 2026

Uploaded by Ben

Connected Vehicles Lessons Learned & Best Practices (2026 Edition) provides an engineering-focused guidance resource for planning, designing, deploying, and operating connected vehicle systems. It outlines roles and responsibilities, emphasizes coordination with District and local maintenance personnel, and highlights constraints related to networking configuration and integration with central systems such as SunGuide, SCMS, and DEPOT. The document also clarifies assumptions, definitions, and revision references, while noting that the guidance is not all-inclusive and internal links require an FDOT account.

LanguageEnglish

CategoryResearch & Report

FormatPDF

Pages117

Reading Time4 h 55 min

AccessFree to download

Section 1 : Introduction

1.1 Background

1.1.1 History

1.2 Purpose

1.2.1 Organization of this Document

1.2.2 Assumptions Made

1.2.3 Users and Intended Audience

1.3 Revisions and References

1.3.1 Revisions

1.3.2 References

1.4 Definitions of Terms and Acronyms

Section 2 : Planning and Project Development

2.1 Introduction

2.2 Design Project Scoping Statewide Planning Process Overview

2.3 District and Regional Planning Process Overview

2.3.1 Long Range Transportation Plans

2.3.2 Regional TSM&O Plans

2.4 TSM&O Project Planning Overview

2.4.1 10-Year ITS Cost Feasible Plan

2.4.2 Regional ITS Architectures

2.4.3 FDOT Five Year Work Program

2.5 Preliminary Project Development

2.5.1 PD&E Process and Scoping

2.5.2 Tailored Systems Engineering Analysis

2.6 Project Evaluation/Studies/Research

Section 3 : Design Considerations

3.1 Preliminary Engineering Considerations

3.1.1 Systems Engineering Updates

3.1.2 Field Reviews

3.1.3 Stakeholder Coordination

3.1.4 Technology

2026 Edition CONNECTED VEHICLES Lessons Learned & Best Practices 2026 Edition December 2025 2026 Edition DISCLAIMER: This document is intended to be an informational resource and does not relieve Engineers of Record of the responsibility to design a fully functional and implementable system. The following guidance is based upon previous experience in the project management, planning, design, deployment, and operation of connected vehicle systems within Florida and has been made available to assist in project efforts; but does not supersede engineering judgement. Designers and Construction Contractors must coordinate with District and local maintaining personnel to fully understand current conditions, project requirements, and limitations of the available system(s)—including networking configuration constraints, integration with central systems (e.g., SunGuide, SCMS, DEPOT), known operational issues, maintenance considerations, pace of technology, and more. Furthermore, this document is not intended to be all inclusive. The Engineer of Record shall be responsible for all aspects of design and Construction Contractors shall be responsible for all aspects of construction—including coordination efforts, procedural steps, and processes of the Department that are not explicitly referenced or defined in this document—based on individual experience and project-specific field conditions. Please note that some links are internal and only accessible with an FDOT account and can be made available upon request to the District TSM&O or Central Office CAV team. This redacted version redacts all the default IPs and credentials to field devices and systems. 2026 Edition Table of Contents Section 1 : Introduction ................................................................................................................................ 1 1.1 Background ....................................................................................................................................... 1 1.1.1 History ..................................................................................................................................... 1 1.2 Purpose ............................................................................................................................................. 1 1.2.1 Organization of this Document ............................................................................................... 1 1.2.2 Assumptions Made ................................................................................................................. 2 1.2.3 Users and Intended Audience ................................................................................................. 2 1.3 Revisions and References ................................................................................................................. 2 1.3.1 Revisions ................................................................................................................................. 2 1.3.2 References .............................................................................................................................. 2 1.4 Definitions of Terms and Acronyms ................................................................................................. 3 Section 2 : Planning and Project Development............................................................................................. 7 2.1 Introduction ...................................................................................................................................... 7 2.2 Design Project Scoping Statewide Planning Process Overview........................................................ 7 2.3 District and Regional Planning Process Overview ............................................................................ 8 2.3.1 Long Range Transportation Plans .....................................................................

FAQs

What is the purpose of the 2026 Edition connected vehicles guidance document?

It provides informational guidance drawn from prior connected vehicle project experience to support planning, design, deployment, and operation efforts. It is intended to assist project efforts without replacing engineering judgment.

Who is responsible for design and construction according to the disclaimer?

The Engineer of Record remains responsible for all aspects of design, while Construction Contractors are responsible for all aspects of construction. Contractors must coordinate procedural steps and processes not explicitly defined in the document.

What types of system constraints and integrations does the document emphasize?

It highlights coordination needs related to current conditions and limitations, including networking configuration constraints and integration with central systems such as SunGuide, SCMS, and DEPOT, along with known operational issues and maintenance considerations.

Sep 15, 2026

Uploaded by Ben