Cities Index.
Attachment 3 - Smart Signals Project Description.pdf

Richmond City Council
December 5, 2023

Document
Attachment 3 - Smart Signals Project Description.pdf
Meeting
December 5, 2023
Body
Richmond City Council
Pages
2
Original file
1.4 MB
Text extracted from the city's file for reading and search. Open the original on pub-richmond.escribemeetings.com. That file is the official record.

COMMISSIONERS
Federal Glover,
Chair

Newell Arnerich,
Vice Chair
Ken Carlson
Paul Fadelli
Loella Haskew
David Hudson
Chris Kelley
Aaron Meadows
Sue Noack
Renata Sos
Lamar Thorpe

Timothy Haile,
Executive Director

2999 Oak Road
Suite 100
Walnut Creek
CA 94597
PHONE: 925.256.4700
FAX: 925.256.4701
www.ccta.net

March 21, 2023

Attn: Daniel Chavarria
City of Richmond
Email: [email protected]
Subject: Summary of Smart Signals Project for the City of Richmond

Dear Mr. Chavarria,
For the Countywide Smart Signals project, The signals located at the following intersections have been identified to be included in the project and are proposed to receive Smart Signal upgrades:

Signal No. Primary Street Secondary Street
1 San Pablo Ave Macdonald Ave
2 San Pablo Ave Barrett Ave
3 San Pablo Ave Roosevelt Ave
4 San Pablo Ave Clinton Ave
5 San Pablo Ave Solano Ave
6 San Pablo Ave Garvin Ave
7 San Pablo Ave Esmond Ave
8 San Pablo Ave McBryde Ave
9 San Pablo Ave Robert Miller Dr
10 San Pablo Ave La Puerta Rd
11 23rd St Rheem Ave
12 23rd St Lincoln Ave
13 23rd St Garvin Ave
14 23rd St Roosevelt Ave
15 23rd St Barrett Ave
16 23rd St Nevin Ave
17 23rd St Macdonald Ave
18 23rd St Bissell Ave
19 23rd St Ohio Ave
20 23rd St Virginia Ave
21 23rd St Cutting Blvd

Public Works Director/Staff
City of Richmond
March 21, 2023

Page 2 ends

Th
e recommended upgrades for signals located in Richmond include:
• Signal controller firmware updates
• Video/Radar detection
• Ethernet Over Copper (EOC) for communication between the signals • Pan-Tilt-Zoom (PTZ) cameras
• An Advanced Traffic Management System (ATMS)
• Traffic signal synchronization, and
• Video Analytics.

T
he list may be modified as needed. Please let us know if there are any additional considerations, or if there are any questions. Our consultant, AMG, is preparing the Concept of Operations (ConOps) for this project, and we would like to include the final version of the intersections and upgrades into the document.

Based on preliminary estimates, the upgraded equipment, including cost of construction, is shown below. Please note that the City will be responsible to provide the minimum match of 11.47%.
• Total Number of Signals – 21
• To
tal funding – $1,589,984
• Local match required – $182,336
A
Funding Agreement will follow shortly and distributed to the City and all jurisdictions.

Please contact me at [email protected] or 925-256-4701 if you have any questions.

Regards,
J
ohn Hoang
Director, Planning
Cc: Joy Bhattacharya,
Vice President, Director of Innovative Transportation Solutions (AMG)

March 17, 2023
Draft Systems Engineering
Management Plan
SMART

SIGNALS

CCTA Smart Signals Systems Engineering Management Plan-Draft | Page i Revision History
Name Date Version Summary of
Changes
Approver
Vasavi
Pannala
01/19/2023 1 Initial Draft
Clay
Kellinger
3/3/2023 1.1 Adding
Content

Kasra
Behbahani
3/8/2023 1.2 Reviewed
Joy
Bhattacharya
3/10/2023 1.3 Review
Rich Shinn 3/13/2023 1.3 Comments
John Hoang 3/13/2023 1.3 Comments
Clay
Kellinger
3/13/2023 1.4 CCTA
comment
changes

CCTA Smart Signals Systems Engineering Management Plan-Draft | Page ii

TABLE OF CONTENTS
REVISION HISTORY ....................................................................................................................................... I

1. PURPOSE OF DOCUMENT ......................................................................................................................... 1 ORGANIZATION OF THE REPORT .................................................................................................................. 1

2. SCOPE OF PROJECT ................................................................................................................................... 2 PROJECT OVERVIEW ...................................................................................................................................... 2 SOLUTION ...................................................................................................................................................... 3

3. TECHNICAL PLANNING AND CONTROL .................................................................................................... 5 WORK BREAKDOWN STRUCTURE ................................................................................................................. 5 PROJECT DELIVERABLES ................................................................................................................................ 7 CHANGE CONTROL ........................................................................................................................................ 8 SCHEDULE ..................................................................................................................................................... 9

4. SYSTEMS ENGINEERING PROCESS ........................................................................................................... 9

5. TRANSITIONING CRITICAL TECHNOLOGIES ............................................................................................ 15

6. INTEGRATION OF THE SYSTEM .............................................................................................................. 17

7. INTEGRATION OF THE SYSTEMS ENGINEERING EFFORT ....................................................................... 17

8. APPLICABLE DOCUMENTS ...................................................................................................................... 19

CCTA Smart Signals Systems Engineering Management Plan-Draft | Page 1

1. Purpose of Document
This document presents the Systems Engineering Management Plan (SEMP), developed to guide the planning, design, procurement, and deployment processes of the Contra Costa County Transportation Authority’s (CCTA’s) Safety and Mobility of Arterial (Smart) Signals project. The Smart Signals project will develop, manage, and implement Intelligent Transportation Services (ITS) initiatives that will improve multimodal mobility, maximize highway and major arterial system throughput, reduce environmental impact, and improve operational efficiency and safety throughout the Contra Costa County. This project also serves as a transit signal priority, emergency vehicle preemption, and data communication infrastructure solution for the signal systems. This project lays a foundation for Smart Cities initiatives which connect Intelligent Transportation Services to other Smart City Systems on a countywide basis.

This document explains the Systems Engineering Process intended for the project. A Systems Engineering process is an iterative process used throughout the life cycle of a project.

Since this SEMP is developed early in the lifecycle of the project, several versions might be released during the life of the project. This version of the SEMP is based on the work that is completed for the Project listed below:
• Defined Vision, Goals and Objectives
• Meetings with each of the 20 jurisdictions in Contra Costa County (19 cities/towns and unincorporated County) and transit agencies
• Needs Assessment
• Identification and Evaluation of signal infrastructure • Identified solutions and concepts
• Created probable cost estimates for each agency
• Identified project benefits
• Identified base package
• Support design, procurement, implementation, operation & maintenance

ORGANIZATION OF THE REPORT
The document is organized as follows:

Section 1: Purpose of Document– This section includes the purpose of the SEMP and organization of the document.

Section 2: Scope of the Project – Explains the scope of the project and project components.

CCTA Smart Signals Systems Engineering Management Plan-Draft | Page 2 Section 3: Technical Planning and Control – This section lists the task deliverables planned for the Project and describes the plan for reviewing the technical deliverables.

Section 4: Systems Engineering Process – Describes the Systems Engineering process that the Project will follow.

Section 5: Transitioning Critical Technologies – This section lists various critical technologies proposed for the Project.

Section 6: Integration of the System – This section includes guidelines for the preparation of Integration Plan in the later phases of the Project.

Section 7: Integration of the Systems Engineering Effort – This section addresses the integration of the multi-disciplinary organizations or teams that will be performing the systems engineering activities.

Section 8: Applicable Documents – This section lists the applicable documents which are inputs to the project.

2. Scope of Project

PROJECT OVERVIEW
Contra Costa County is home to 19 cities/towns and numerous unincorporated communities.

There are approximately 1400 traffic signals within the County, Caltrans-owns and various city-owned. Most of these traffic signals are located either along major arterials, including State Routes, identified as Routes of Regional Significance (RSS) or other major and minor arterials in the cities/towns.

The existing traffic signal systems in most jurisdictions located within Contra Costa County are legacy systems and are outdated or antiquated compared to newer traffic signal systems.

These signal systems currently lack the communication infrastructure such as fiber and cellular/wireless-based communication, which makes it difficult to implement traffic signal synchronization and coordination between traffic signals along an arterial. Most corridors do not currently include Signal Control and Prioritization (SCP) technologies to promote transit usage to reduce delay and travel times for transit vehicles and reduce response time for emergency vehicles.

These deficiencies result in severe traffic congestion within the cities/towns and may result in spillover onto freeways and cause a chain reaction of congestion along local arterials. The current system contributes to overall commuter travel times and delays, increases

CCTA Smart Signals Systems Engineering Management Plan-Draft | Page 3 greenhouse gas emissions and fuel consumption, as well as incidents and collisions. These deficiencies were documented following extensive discussions with the cities and towns regarding traffic signal operation within the Contra Costa County.

CCTA and the project Stakeholders have initially identified these deficiencies, which are translated as the following project goals.
► Improve safety and minimize crashes, injuries, and fatalities between motorists, bicyclists, and pedestrians.
► Optimize mobility along major corridors and RSS.
► Advance to Smart City and Internet of Things (IOT) solutions.

SOLUTION
The Smart Signals project will develop, manage, and implement ITS initiatives that improve the safety and efficiency of multimodal mobility, maximize highway and arterial system throughput, and improve operational efficiency, safety, and reduce environmental impact throughout the county. By upgrading the existing legacy systems and providing interconnectivity throughout Contra Costa County signal systems, the county’s traffic signal systems can be prepared for future emerging technologies including connected and/or autonomous vehicles, big data, integrated corridor management (ICM), enable implementation of incident management strategies and Smart Cities initiatives. This solution can enhance the sharing of real-time information between agencies and the public using existing and next generation ITS technologies.

The upgraded traffic signal systems and signal interconnect will help smooth traffic flow and ease recurring traffic congestion by expanding mode choice options and reducing travel time on local streets and roads. Upgraded traffic signals will benefit pedestrians and transit commuters by reducing wait times at intersections, improving total travel time for all modes while making transit and pedestrian more viable transportation options. The Smart Signal systems would also improve the safety of the pedestrians, bicyclists, vulnerable road users, and people with disabilities by deployment of detection systems.

To accomplish these goals, CCTA is applying a Smart Signal approach that will include the implementation of ITS equipment including upgraded traffic signal controllers and cabinets, upgraded Advanced Traffic Management System (ATMS) for each agency to provide remote command and control from a centralized Traffic Management Center (TMC) or Traffic Operations Center (TOC) location, Closed-circuit Television (CCTV) cameras, SCP for transit and emergency vehicles, and vehicle detection systems deployed on predefined designated arterials and state routes. These improvements will provide local cities and Caltrans day-to- day county-wide traffic management capabilities in addressing recurrent traffic congestion as well as provide CCTA capabilities for managing the system during non-recurring traffic

CCTA Smart Signals Systems Engineering Management Plan-Draft | Page 4 congestion caused by diverted traffic due to major incidents on the freeway or during any evacuation efforts.

The Smart Signals project’s key features and benefits include:
► Providing infrastructure for a countywide traffic management system ► Upgrading local signal controllers and signal system hardware, software, and firmware ► Deploying bicycle and pedestrian detection software for vulnerable road user protection ► Providing SCP, including Transit Signal Priority (TSP) and Emergency Vehicle Preemption (EVP) capabilities
► Enabling local event management signal timing options ► Taking a proactive approach to safety by identifying “near miss” situations for analysis ► Enabling cities and CCTA to proactively manage day-to-day traffic ► Enabling cities to proactively manage traffic on local streets that has diverted off the freeway due to a major freeway incident
► Identifying alternative routes with timing optimized for incident management ► Allowing shared control and operation, improving cross jurisdictional traffic management
► Allowing cities/CCTA access to monitor all CCTV cameras and traffic signals for the purpose of optimizing day-to-day operations

Deployment of the Smart Signals Project is expected to result in operational and safety improvements for all modes of transportation, such as:
► Decrease in travel time,
► Decrease in total delay,
► Reduction in number of stops
► Reduction in secondary accidents
► Decrease in fuel consumption and greenhouse gas emissions ► Promotion of transit ridership
► Reduction of response time for emergency vehicles

When operating together, these enhancements increase safety and reliability, and support environmental sustainability, economic development, and equitable access for all travelers.

Table 1 identifies the organization structures that encompass all stakeholders with a brief description of the role to be played by each stakeholder. This includes the management work groups, including the Project Lead Team (PLT), the Project Management Team (PMT), the Project Development Team (PDT), the Project Systems Engineer (PSE), the Core Advisory Committee Group (CACG), and multi-disciplinary technical teams that will work together as a team to support the project.

CCTA Smart Signals Systems Engineering Management Plan-Draft | Page 5 Table 1: Stakeholder Role(s)
Stakeholder Role(s)
Tim Haile Executive Director of CCTA, Executive leadership and PLT. 19 Mayors of jurisdictions in
Contra Costa County
Executive Leadership and PLT Responsible for review and approval of project improvements within the City’s right-of-way. These jurisdictions own and operate numerous signals in Contra Costa County and will own, operate, and maintain the planned systems.

CCTA Staff PMT, project sponsor.

Advanced Mobility Group PMT, PSE
Design Consultant(s)/
Engineer(s)
PDT, perform PS&E for project field elements.

Construction Contractor(s) PDT, construct and install field elements.

Integration Consultant(s) PDT, integrate project field elements.

CCTA Technical Staff CACG
CCTA Traffic Engineers CACG
Local Cities Own and operate numerous signals in Contra Costa County.

Responsible for review and approval of project improvements within the City’s right-of-way. Will own, operate, and maintain the planned systems.

Transit Agencies Infrastructure will need integration with systems.

The SEMP is a living document that will be updated as the project progresses. The current version of the SEMP is the draft framework version prepared by the PSE on behalf of the project sponsor. The complete version will be prepared in conjunction with the Systems Engineer and Development Teams as the project progresses and the design and integration consultants are selected for the project.

3. Technical Planning and Control

WORK BREAKDOWN STRUCTURE
► WBS-1 - Select Project Management Team and Project Systems Engineering: CCTA, the project sponsor, selects a System Engineer to lead the systems engineering process for the Smart Signals Project.
► WBS-2 - Prepare Systems Engineering Management Plan: The Systems Engineer will prepare and maintain the Systems Engineering Management Plan (SEMP) to guide the planning, design, procurement, and deployment processes of the Smart Signals Project. ► WBS-3 - Public Outreach and Meeting with the Stakeholders: Multiple meetings will be held between all the stakeholders to discuss the project and user needs.

CCTA Smart Signals Systems Engineering Management Plan-Draft | Page 6 ► WBS-4 - Prepare Concept of Operations and Identify User Needs: The System Engineer will develop the Concept of Operations (ConOps), which will describe the characteristics of the proposed system from the perspective of the system operator(s). The ConOps provides a high-level understanding of the activities the planned systems will support. ► WBS-5 - Prepare System Requirements: The System Engineer will identify and develop a list of technical requirements and functionalities that are essential and/or desirable to be included in the new systems. These requirements will be based on the ConOps and discussions with stakeholders at meetings.
► WBS-6 - Prepare Verification/Acceptance Plan: The System Engineer will develop a verification/acceptance plan describes in the Project Deliverables section below. ► WBS-7 - Prepare Request for Proposal (RFP) for Project Design Team: CCTA will prepare and submit a request for proposal for bids to be the Project Design Team of this project. ► WBS-8 - Select System Project Design Team: CCTA will select project design team to prepare the Plans, Specifications, and Estimate (PS&E) for the project. ► WBS-8 - Prepare Agreement(s): CCTA will plan and approve the agreements between CCTA and the selected Design Team.
► WBS-9 - Develop PS&E for Project Field Elements: The design team will develop the plans illustrating the improvements and upgrades at all intersections. The team will develop the specification for the procurement of all infrastructure, hardware, and software as needed for the project. The team will also develop a cost estimate for the project.
► WBS-10 - Prepare RFPs to select Contractor to Construct Field Elements and Project Systems Integrator: CCTA will prepare and submit a request for proposal to select the construction contractors and Project Systems Integrator for this project. ► WBS-11 - Prepare Agreement(s): Prepare agreements for construction contractors and the Project Systems Integrator.
► WBS-12 - Deploy Systems and Construct/Integrate Project Field Elements:

Construction contractors and the Systems Integrator will work to deploy and integrate field elements for the project per the PS&E package developed by the Project Design Team.
► WBS-13 - System Testing, Verification, Validation, and Acceptance: The System Engineer will work with CCTA, various cities/towns, and public agency stakeholders during the acceptance testing to verify that each element of the deployed systems is working as required.
► WBS-14 - Operation and Maintenance (O&M) Plan: The System Vendors will develop the Operation and Maintenance Plan as described in the Project Deliverables section below.
► WBS-15 - Project Evaluation: CCTA will evaluate the effectiveness of the deployed system by evaluating Key Performance Index’s (KPIs), benefits and cost, before-and- after studies, and lessons learned to assess the effectiveness of the project.

CCTA Smart Signals Systems Engineering Management Plan-Draft | Page 7

PROJECT DELIVERABLES
The Systems Engineering process as applied to the project will produce, at a minimum, the following documents.
► Project Management Plan (under separate cover): The Project Plan defines and describes all the tasks that need to be performed to accomplish the Project. Each task is described in enough detail that the assigned personnel can replicate the documented task. It is also critical that the products of each task, the schedule for each task, and the available budget are established.
► Systems Engineering Management Plan (this document)
► Concept of Operations (under separate cover): This document provides a high-level system operational overview of the project.
► High Level Requirements (under separate cover): This document describes what the system is to do, how well it is to perform, and under what conditions. These requirements set the technical scope of the system to be built. ► Inspection Plan (under separate cover): This document defines inspection criteria such as what materials are to be inspected, how the inspection is executed, what characteristics are to be inspected, test equipment used, and work center and inspection specifications.
► Verification Plan (under separate cover): This plan provides steps for acceptance tests ranging from equipment factory tests to system acceptance tests. CCTA’s consultant will prepare the test plans to verify the provided system meets the specified requirements. ► Validation Plan (under separate cover): This plan lists the validation activities, including validation requirements, that need to be performed by system users to validate how well the system satisfy their needs.

Other documents included in the Systems Engineering process will be developed by CCTA selected Systems Integrator as separate work. The guidelines to prepare these two documents are listed in the later sections of this document.
► Operations and Maintenance Plan (under separate cover): This document documents the equipment, hardware, procedures, resources, training, and support needed for operating and maintaining the system built by CCTA for the cities to operate. A Memorandum of Understanding (MOU) between CCTA & local agencies will be developed as part of the O&M plan.
► Systems Integration Plan (under separate cover): This document shows how the integration steps of the system are to be done iteratively with verification. This plan defines the sequence of activities that will integrate software components into sub- systems and sub-system into the entire systems.
► Detailed Design Plan (under separate cover): This document provides detailed descriptions and specifications of all system components including PS&E).

CCTA Smart Signals Systems Engineering Management Plan-Draft | Page 8 ► Testing Plan (under separate cover): This document assures all the elements of the system are subjected to a structured review process directed at verifying compliance with the physical, functional, and operational requirements at each level of system development and deployment. This document contains all the test requirements and procedures, who is responsible for testing, and the internal integration testing schedule for each set of integration use case scenarios.

CHANGE CONTROL
A Change Control Board (PMT, PLT) will establish baseline templates and/or reports for each of our project deliverables. A baseline template is an approved configuration that can be changed only through formal change control procedures. Configurations serve as references for further activities. An ‘approved’ status for a configuration means that all items composing the configuration are final. IBM’s Engineering Lifecycle Management (ELM) and e-Builder tools will be used to manage the deliverables of these six baseline subcomponents:

• Requirements Baseline: For requirements documentation and management activities; • Functional Baseline: For system and interface specifications and architectural descriptions;
• Design Baseline: For solution design containing hardware, software, data, and tools components;
• Documentation Baseline: For project documents (e.g., plans, safety, estimates); • Test History: To trace integration, verification, validation, and test activities (e.g., procedures, reports); and
• Modification History: For reports generated from the change management tool to trace accepted change requests considered in the project baseline. • All changes to baselines, such as change orders, will be submitted and approved in e- Builder. E-Builder is the program management tool used by CCTA which augments the document control process by implementing pre-built workflows for all approval and submittal processes. Initially, the systems engineer or integrator puts the baseline documents on e-builder. If a change request is made, the Change Control Board (PMT and PLT) will evaluate the change request and involve the Project Technical Team if needed, then decide on approval of the change request. The Systems Integrator will then implement the approved change. E-Builder’s role in change control is shown in the Change Control Diagram in Figure 1.

CCTA Smart Signals Systems Engineering Management Plan-Draft | Page 9

Figure 1: Change Control Diagram

SCHEDULE
Table 2: Estimated Schedule of Project Tasks
Tasks Schedule
Project Engineering November – August 2023
Plan, Specifications, &
Estimate
August – June 2024
Construction Fall 2024 – Spring 2025
Systems Integration Spring 2025 – Fall 2025
Project Close Out December 2025

4. Systems Engineering Process
The CCTA Project team will utilize a Systems Engineering Process to outline the process in which to develop and closely adhere to a design process that is acceptable to CCTA and the project

CCTA Smart Signals Systems Engineering Management Plan-Draft | Page 10 stakeholders. CCTA will utilize the services of consultants and input from stakeholders to confirm that this process is followed.

A Systems Engineering process is an iterative approach to technical management, procurement, system design, product realization, and technical evaluation at each level of the system, beginning at the top and propagating those processes through a series of steps that eventually lead to a preferred system solution, and then continue through detailed design, deployment, integration, verification, and initial operations.

The Systems Engineering process for the Project will follow the V-Model as defined in the FHWA Systems Engineering for Intelligent Transportation Systems Guide and illustrated in Figure 2.

Figure 2: System “V” Diagram

Table 3: Existing or Ongoing ITS Strategies and Packages based on 2023 Regional ITS Architecture
Stakeholder Strategies System
Caltrans D-4 SR 4 East ICM ATMS
Caltrans D-4 Transportation
Management System
DM01 - ITS Data Warehouse - CHP/MTC 2
MC08 - Maintenance and Construction
Activity Coordination - SMART Corridors

CCTA Smart Signals Systems Engineering Management Plan-Draft | Page 11 Stakeholder Strategies System
PS10 - Wide-Area Alert - California
Highway Patrol-02
PS12 - Disaster Response and Recovery -
ICM and TMC
PS13 - Evacuation and Reentry
Management Local Cities/Counties -02
PS14 - Disaster Traveler Information -
SMART Corridors
PT09 - Transit Signal Priority - SR-4
SMART
SU04 - MTC Regional Map Management
TI01 - Broadcast Traveler Information -
Caltran District 4 ( Traffic Operations) - 01
TI02 - Personalized Traveler Information -
ICM
TM01 - Infrastructure-Based Traffic
Surveillance - ICM
TM03 - Traffic Signal Control - ICM
TM06 - Traffic Information
Dissemination- Caltrans District 4 (Traffic
Operations)
TM07 - Regional Traffic Management -
Caltrans District 4(Traffic Operations)-02
TM08 - Traffic Incident Management
System - California Highway Patrol
TM09 - Integrated Decision Support and
Demand Management - Contra Costa
Transportation Authority
PS03 - Emergency Vehicle Preemption -
East Bay ICM
PT09 - Transit Signal Priority - SR-4
SMART
TM01 - Infrastructure-Based Traffic
Surveillance - ICM
TM03 - Traffic Signal Control - ICM
CCTA CCTA Countywide Connected Data
Center
CCTA Centralized Transit Priority
PT09: Transit Signal Priority – CCTA
Centralized TSP
TM09: Integrated Decision Support and
Demand Management
PT14 - Multi-modal Coordination -
Regionwide
TM07 - Regional Traffic Management -
CCTA Smart Signals

CCTA Smart Signals Systems Engineering Management Plan-Draft | Page 12 Stakeholder Strategies System
MTC MTC Bay Area 511 DM01: ITS Data Warehouse - Bay Area NextGen 511 System
TI01: Broadcast Traveler Information -
Bay Area NextGen 511 System
TI01: Broadcast Traveler Information -
Bay Area 511 IVR
TI01: Broadcast Traveler Information -
Bay Area 511 Website
TI02: Personalized Traveler Information -
Bay Area NextGen 511 System
TI02: Personalized Traveler Information -
Bay Area 511 IVR
TI02: Personalized Traveler Information -
Bay Area 511 Website
TI04: Infrastructure-Provided Trip
Planning and Route Guidance - Bay Area
NextGen 511 System

County
Connection
(CCCTA)
County Connection Connected Vehicle
(CV) Transit Signal Priority (TSP)
PT09: Transit Signal Priority
Tri-Delta
(ECCTA)
Tri Delta Transit Operations System
Tri Delta Transit Vehicle
DM01 - ITS Data Warehouse - Bay Area
NextGen 511 System
PS02 - Emergency Response - MTC
Transit Incident Management Application
PT04 - Transit Fare Collection
Management - Clipper
PT05 - Transit Security - Subregional
Transit Agencies Infrastructure
Monitoring-02
PT17 - Transit Connection Protection -
Passenger Connection Protection
PT17 - Transit Connection Protection -
CCTA
TM08 - Traffic Incident Management
System - MTC Transit Incident
Management Application
PT04 - Transit Fare Collection
Management - Clipper

CCTA Smart Signals Systems Engineering Management Plan-Draft | Page 13 Stakeholder Strategies System
PT17 - Transit Connection Protection -
Passenger Connection Protection

AC Transit AC Transit Operations System
AC Transit Bus Arrival Information
System
AC Transit Bus Yard
AC Transit Operations System
AC Transit Vehicles
AC Transit/BART Deman Response
Vehicles
DM01 – ITS Data Warehouse
PS02 – Emergency Response
PT01 – Transit Vehicle Tracking
PT02 – Transit Fixed-Route Operations
PT03 – Dynamic Transit Operations
PT06 Transit Fleet Management
PT07 – Transit Passenger Counting
PT08 – Transit Traveler Information
PT09 – Transit Signal Priority

Table 4: Planned or Future ITS Strategies and Packages Regional ITS Architecture Plans Stakeholder Strategies Market Packages
Caltrans D-4 Contra Costa Decision Support
System
TM09: Integrated Decision Support and Demand
Management
CCTA Contra Costa Decision Support
System
CCTA Smart Signals
TM01: Infrastructure-Based Traffic Surveillance
TM03: Traffic Signal Control
TM06: Traffic Information Dissemination
TM09: Integrated Decision Support and Demand
Management
PT14: Multi-modal Coordination

AC Transit AC Basic Transit Vehicle
Equipment
VS01 – Autonomous Vehicle Safety Systems

Table 5: Project Standards
Standard
Group
Document ID Title
ASTM ASTM E2468-05
ASTM E2665-08
Standard Practice for Metadata to
Support Archived Data Management
Systems
Standard Specifications for Archiving ITS-
Generated Traffic Monitoring Data

CCTA Smart Signals Systems Engineering Management Plan-Draft | Page 14 Standard
Group
Document ID Title
IEEE IEE 1512
IEE1512.3
Standard for Common Incident
Management Message Sets for use by
Emergency Management Centers
Standard for Hazardous Material
Incident Management Message Sets for
Use by Emergency Management Centers
ITE ITE ATC 5201
ITE ATC 5202

ITE ATC API
ITE ITS Cabinet

ITE TMDD
Advanced Transportation Controller
(ATC)
Model 2070 Controller Standard
Application Programming Interface (API)
Standard for the Advanced
Transportation Controller (ATC)
ITS Standard Specification for Roadside
Cabinets
Traffic Management Data Dictionary
(TMDD) and Message Sets for External
Traffic Management Center
Communications (MS/ETMCC)
SAE SAE J2313
SAE J2354
SAE J2735
SAE J3067
On-Board Land Vehicle Mayday
Reporting Interface
Message Set for Advanced Traveler
Information System(ATIS)
Dedicated Short Range Communications
(DSRC) Message Set Dictionary
Candidate Improvements to Dedicated
Short Range Communications (DSRC)
Message Set Dictionary [SAE J2735]
Using Systems Engineering Methods
NTCIP NTCIP 1201
NTCIP 1202
NTCIP 1205
NTCIP 1206
NTCIP 1208
NTCIP 1211

Global Object Definitions
Object Definitions for Actuated Traffic
Signal Controller (ASC) Units
Object Definitions for Closed Circuit
Television (CCTV) Camera Control
Object Definitions for Data Collection
and Monitoring (DCM) Devices
Object Definitions for Closed Circuit
Television (CCTV) Switching
Data Element Definitions for Object
Definitions for Signal Control and
Prioritizations (SCP)
ANSI ANSI ASC X12 TS–813 Electronic Filing of Tax Return Data APTA APTA TCIP-S-001 Standard for Transit Communications Interface Profiles

CCTA Smart Signals Systems Engineering Management Plan-Draft | Page 15 Standard
Group
Document ID Title
GTFS
Discussion
Group
GTFS
GTFS-Realtime
General Transit Feed Specification (GTFS)
Static
General Transit Feed Specification (GTFS)
Realtime
ISO ISO 19091
ISO 21217
ISO 21320-1
Intelligent transport systems ––
Cooperative ITS –– Using V2I and I2V
communications for applications related
to signalized intersections
Intelligent transport systems ––
Communications access for land mobiles
(CALM) –– Architecture
Information technology — Document
Container File — Part 1: Core
USDOT RSU V4 USDOT Roadside Unit (RSU) Specification
Document – Version 4
IETF IETF RFC 7230
IETF RFC 4180

Hypertext Transfer Protocol (HTTP/1.1):

Message Syntax and Routing
Common Format and MIME Type for
Comma-Separated Values (CSV) Files
NIST NIST FIPS PUB 140-2 Security Requirements for Cryptographic Modules
NEMA NEMA TS 2
NEMA TS 4
NEMA TS 5
NEMA TS 8
Traffic Controller Assemblies with NTCIP
Requirements
Hardware Standards for Dynamic
Message Signs (DMS) with NTCIP
Requirements
Portable Traffic Signal Systems (PTSS)
Standard Control Circuit and Pilot
Devices
Cyber and Physical Security for
Intelligent Transportation Systems (ITS)

5. Transitioning Critical Technologies
Critical technologies are those technologies which prevent the system from meeting its goals/objectives and providing the functionality required. There are no backups to critical technologies needed for the “solution” described in the previous sections. With this definition, all technologies in the proposed system are critical. The technologies that will be used in this Project are:

CCTA Smart Signals Systems Engineering Management Plan-Draft | Page 16

1. Traffic Signal Control (TSC) enables traffic signals to assign the right- of-way at intersections. Traffic Signal Controllers are the physical devices assigned to an intersection that are usually stored in traffic cabinets. They can control a single intersection, multiple closely spaced intersections, or a midblock crosswalk. Traffic Signal Controllers electrically switch signals to traffic lights and pedestrian walk signals. TSCs can be pretimed, semi- actuated, or fully actuated; meaning both vehicle and pedestrian signals can either be programmed to use predetermined duration and timing intervals or use vehicle and pedestrian detectors to activate a certain phase (change it from red to green) of the signals.

2. Communications (Fiber and/or Ethernet) in modern ITS networks require ever-increasing data rates to facilitate real-time communications between a wide variety of remote field devices and traffic control centers. Fiber optic links between controllers and traffic control centers provide greater b andwidth, longer transmission distances, and more signal immunity than twisted pair copper and coax options. Fiber Optic cables will be a necessity to install at select locations to provide this increased functionality to the traffic control center. With the cost of fiber up, wireless/ cellular communication , or Ethernet over Copper (EOC) will also be an option for this project to be within the project budget.

3. Hybrid Traffic Detection refers to the use of multiple sensor technologies to detect and monitor traffic on roadways . A hybrid detection system uses a combination of sensors, radars, cameras, and software to collect data on vehicle speed, volume, flow, vehicle classification, etc., in addition to providing the detection calls to the signal controller to operate the traffic signals. A hybrid traffic detection system can provide more reliable and detailed information on traffic, including the detection of vehicles, pedestrian, bicyclist, and other vehicle classifications, which can improve safety and mobility at the intersection.

4. Video Analytics are used to comply with California privacy laws while detecting events and objects and communicating this event to the traffic signal controllers or the traffic control centers. These devices detect vul nerable road users (i.e. pedestrians and bicyclists), motor vehicles, and their movements. These devices may use Pan Track Zoom (PTZ) camera technology which allows for a wider field of view and reliable control for remote operators. Video detection edge devices may be used or existing fiber communication to TMC can be used to inform users of special traffic events such as a car going the wrong way, a car on fire, a pedestrian jaywalking, and near miss collisions.

5. Signal Control and Prioritization (SCP) gives preferential treatment (priority) to facilitate the movement of fleet vehicles such as transit, emergency services, and commercial fleets through signalized intersections. TSP and EVP are subsets of SCP that give signal priority to transit and emergency vehicles respectively. The innovative method for setting up Signal Control Prioritization is to use cloud- based systems or Vehicle to Infrastructure (V2I) communication instead of installing intersection infrastructure.

6. Automated Traffic Signal Performance Measures (ATSPM) is a group of performance measures, data collection and data analysis tools that show real- time and a history of performance at signalized intersections.

CCTA Smart Signals Systems Engineering Management Plan-Draft | Page 17

6. Integration of the System
System Integration will be a joint effort of CCTA and selected System Integrator. The System Integrator will be responsible for leading the efforts for successful integration of the various components of the Project. The System Integrator will be responsible for developing the Integration Plan for the project, which working with vendors and contractors to get a clear understanding of the various methods that they will use to ensure successful integration of the developed components into a fully functioning system that meets the requirements from the RFP and other Contract documents.

System Integration will occur in a phased approach starting with elements combined into components which are then combined into subsystems and then into a system. As each phase is ready, it will be first tested as a standalone system before testing as part of the existing system. The exact testing to be performed will be detailed in the individual device acceptance test plans, the system acceptance test plan, and the Verification and Validation Plans.

7. Integration of the Systems Engineering
Effort
This project includes 19 cities/towns, county, Caltrans, and transit providers. The larger the number of teams, the more critical and important the integration efforts are. It is critical that each stakeholder understands their roles and responsibilities for the project and how they can support the tasks from the WBS. Table 5 identifies the roles and responsibilities and the stakeholders responsible for approval along with the decision gates for each of the tasks identified as part of the WSB outlined in Section 3:

Technical Planning and Control. Decision gates represent critical activities that must be satisfactorily completed and approved before a task is considered complete. Each team will need to be aware of the status of activities coming directly before tasks their team is responsible for, as well as communicating with teams on tasks coming directly after to assist with the transition between tasks.

Table 5: Task Decision Gates
Critical Activity Deliverable Completed
By
Approval By Prerequisite
Select PMT and PSE PMT and PSE CCTA Executive
Leadership
None
Prepare Systems
Engineering
Management Plan
Draft & Final SEMP Advanced
Mobility
Group
CCTA, All
Public
Agency
Stakeholders
Select PMT and PSE

CCTA Smart Signals Systems Engineering Management Plan-Draft | Page 18 Critical Activity Deliverable Completed
By
Approval By Prerequisite
Public Outreach and
Meeting with the
Stakeholders
Meeting with
Stakeholders
CCTA and
Advanced
Mobility
Group
CCTA, All
Public
Agency
Stakeholders
Select PMT and PSE
Prepare Concept of
Operations (ConOps)
Draft & Final Report Advanced
Mobility
Group
CCTA and
Public
Agency
Stakeholders
SEMP
Prepare System
Requirements
Draft & Final System
Requirements
Advanced
Mobility
Group
CCTA and
Public
Agency
Stakeholders
Concept of
Operations
Prepare Verification/
Acceptance Plan
Draft & Final
Verification/
Acceptance Plan
Design and
System
Integrator
Contractors

PMT (AMG
and CCTA),
Public
Agency
Stakeholders
System
Requirements
Prepare Requests for
Proposal (RFP) for
Project Design Team
(PDT)
Draft & Final
Requests for Proposal
Advanced
Mobility
Group,
CCTA
Executive
Leadership
Systems
Requirements and
ConOps
Prepare Agreements Designer Agreements Advanced
Mobility
Group
CCTA Board Varies
Develop Plans,
Specifications, and
Estimate (PS&E) for
Project Field Elements
Draft & Final PS&E Design PDT PMT (AMG
and CCTA)
RFP for PDT
selection

Prepare RFPs to select
Contractor to
Construct Field
Elements and
Draft & Final
Requests for Proposal

PDT PMT (AMG
and CCTA)
PS&E
Prepare Agreement(s) Construction and
System Integrator
Agreements
PMT CCTA Board RFP for Contractor
selection
Deploy Systems and
Construct/Integrate
Project Field Elements
Systems deployed in
field
System
Integrator,
Contractors

PMT (AMG
and CCTA),
Public
Agency
Stakeholders
Select System
Vendors
System Testing and
Acceptance
Completed Systems System
Vendors

PMT (AMG
and CCTA)
Deploy systems and
construct/integrate

CCTA Smart Signals Systems Engineering Management Plan-Draft | Page 19 Critical Activity Deliverable Completed
By
Approval By Prerequisite
project field
elements
Operation and
Maintenance (O&M)
Plan
Draft & Final
Operation and
Maintenance Plan
System
Vendors

PMT (AMG
and CCTA),
Public
Agency
Stakeholders
System Testing and
Acceptance
Project Evaluation Evaluation Plan PMT PMT (AMG
and CCTA),
Public
Agency
Stakeholders
Operation &
Maintenance Plan

8. Applicable Documents
The following is a list of references used in the development of the SEMP:
► FHWA/Caltrans Systems Engineering Guidebook for ITS, version 3.0, November 2009. ► Smart Signals Project Fact Sheet, CCTA.

CONTRA COSTA COUNTYWIDE SMART SIGNALS

Contra Costa Transporta�on Authority (CCTA) is leading a Countywide Smart Signals Project (Project) to upgrade traffic signal and communica�on systems at 328 intersec�ons within Contra Costa County throughout the 19 ci�es/towns and unincorporated communi�es located along major arterial streets and roads designated as Routes of Regional Significance.

PURPOSE + NEED | Exis�ng traffic
signal systems in most ci�es within Contra
Costa County consist of outdated legacy
systems that lack fiber and/or ethernet
base communica�on making traffic signal
synchroniza�on and coordina�on
between traffic signals difficult.

Addi�onally, most corridors need Signal
Control and Priori�za�on (SCP)
technologies that can promote transit
usage and mode shi�. These opera�onal
deficiencies result in severe traffic
conges�on within the ci�es which can
also lead to spillover on the freeways;
increasing commuter travel �mes,
greenhouse gas emissions, fuel
consump�on, and accidents.

SOLUTION | Implementa�on of the planned Intelligent Transporta�on System (ITS) elements will unify Contra Costa County’s signal technology and communica�on systems to op�mize traffic flow. It will provide an interconnected Advanced Traffic Management System (ATMS) with the ability to monitor traffic condi�ons in real-�me, safely, and efficiently manage incidents, and share informa�on between agencies and the public.

BENEFITS

SAFETY
Upgrading traffic signal equipment
and applying smart control
systems at intersec�ons will:
► Improve emergency service
response �me;
► Help first responders and law
enforcement manage traffic or
crime incidents; and
► Implement Video analy�cs
that can iden�fy near miss
situa�ons, prevent future
occurrences, and reduce
secondary accidents.

OPERATIONAL

IMPROVEMENTS
Signal synchroniza�on and
implementa�on of SCP
technologies will:
► Smooth traffic flow and
reduce idling;
► Increase average speed;
► Decrease travel �me and total
delay;
► Reduce greenhouse gas
emissions; and
► Increase transit reliability by
improving on-�me service.

TRAFFIC MANAGEMENT

ENHANCEMENTS
Shared control and improved cross
jurisdic�onal traffic management will:
► Provide ci�es and Caltrans access to
monitor all videos and signals in
real-�me;
► Op�mize day-to-day traffic
opera�ons and manage local events
through signal �ming op�ons;
► Effec�vely manage arterial traffic
during major incidents on the
freeway, evacua�ons, or major
events; and
► Enable ci�es to priori�ze transit and
emergency vehicles.

The goals of the project are to improve safety, optimize mobility, prepare for emerging transportation technologies, and advance Smart Cities.

CONTACT | John Hoang, Director, Planning - CCTA
Phone: 925.256.4729 I E-mail: [email protected]

KEY PROJECT FEATURES
► Traffic signal system upgrades
► ATMS upgrades for each agency to provide
remote command and control at a centralized
Traffic Management Center (TMC) loca�on
► Close Circuit Television (CCTV) cameras
► Pedestrian and bicycle detec�on system
► Shared control and opera�on to allow cross
jurisdic�onal traffic management
► Automated data collec�on
► SCP for transit and emergency vehicles
► Vehicle detec�on system on designated
arterials and state routes
FUNDING + SCHEDULE
Project Phase Total Cost Fund Source Start Date
Planning/ Conceptual $250,000 Measure J Jul-22
Environmental Studies (PA&ED) $440,280 Measure J Mar-23 Design Engineering (PS&E) $1,651,050 Local Match, OBAG 3* Sep-24 Construc�on $28,433,092 Local Match, OBAG 3, LPP-F** Sep-25 Total $ 30,774,422
*One Bay Area Grant (OBAG) 3 federal funding provided by Metropolitan Transportation Commission (MTC). ** Local Partnership Program – Formulaic (LPP-F) state funding provided by California Transportation Commission (CTC).

STAKEHOLDERS
An�och Brentwood Clayton Concord Danville
El Cerrito Hercules Lafayete Mar�nez Moraga
Oakley Orinda Pinole Pitsburg Pleasant Hill
Richmond San Pablo San Ramon Walnut Creek Contra Costa County The project is being implemented in collaboration with Central Contra Costa Transit Authority (County Connection), Eastern Contra Costa Transit Authority (Tri Delta Transit), Western Contra Costa County Transit (WestCAT), Alameda-Contra Costa Transit District (AC Transit), Bay Area Rapid Transit (BART), California Department of Transportation (Caltrans), and MTC.

← All documents from this meeting