Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle...

37
Connected Vehicle Environment System Requirements 1

Transcript of Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle...

Page 1: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

Connected Vehicle EnvironmentSystem Requirements

1

Page 2: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

This material is based upon work supported by the U.S. Department of Transportation under Agreement No. DTFH6116H00013.

Any opinions, findings, and conclusions or recommendations expressed in this publication are those of the Author(s) and do not necessarily reflect the view of

the U.S. Department of Transportation.

2

Page 3: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

3

SPEAKERS

RYAN BOLLO

Project Manager,

City of Columbus

[email protected]

TOM TIMCHO

Technical Lead,

WSP

[email protected]

CHRISTOPHER TOTH

CV Systems Engineer,

WSP

[email protected]

Page 4: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

4

PURPOSE OF THIS WEBINAR

• Discuss System Requirements activities and get feedback from SMEs and public input.

WEBINAR CONTENT

• Smart Columbus Program Overview

• Connected Vehicle Environment Project Overview

• Smart Columbus Connected Vehicle Environment System Requirements

• Subject Matter Experts Panel

• Questions

• How to Stay Connected

WEBINAR PROTOCOL

• All participant lines have been muted during the webinar in order to reduce background noise

• Questions are welcome via chatbox during the Q&A Section

• The webinar recording and presentation materials will be posted on the Smart Columbus website

TODAY’S AGENDA

01 |

02 |

03 |

Page 5: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

$40 MILLION78 APPLIED • COLUMBUS WON

5

VISION:

To empower our residents to live their best lives through

responsive, innovative and safe mobility solutions.

MISSION:To demonstrate how an intelligent transportation system and

equitable access to transportation can have positive impacts

on every day challenges faced by cities.

OUTCOMES:

Page 6: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

CONNECTED VEHICLE

ENVIRONMENT

6

Page 7: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

7

DEPLOYMENT AREA

Page 8: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

8

ON-BOARD UNIT INSTALLATIONS

Vehicle Type Quantity

Light-Duty Vehicle

Private Vehicle 1019

City Fleet Vehicle 200

COTA Supervisor Vehicle 25

Emergency VehicleFire Truck/EMS 30

Police Cruiser 80

Heavy-Duty Vehicle Platoon Truck 10

Transit Vehicle

CEAV 6

COTA Transit Bus*

(fixed-route)350

COTA Paratransit Bus 80

Total 1,800

*Quantity may vary slightly depending on operational needs. Source: City of Columbus

Page 9: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

9

APPLICATIONS

Class Application

Ligh

t-D

uty

V

eh

icle

Eme

rge

ncy

V

eh

icle

He

avy-

Du

ty

Ve

hic

le

Tran

sit

Ve

hic

le

Traf

fic

Man

age

r

Tran

sit

Man

age

r

V2V Safety

Emergency Electronic Brake Light X

Forward Collision Warning X

Intersection Movement Assist X

Lane Change Warning/ Blind Spot Warning X

V2I Mobility

Transit Signal Priority X X

Freight Signal Priority/ Intent to Platoon Priority X

Emergency Vehicle Preemption X

Vehicle Data for Traffic Operations X

Transit Vehicle Interaction Event Recording X

V2I Safety

Red Light Violation Warning X

Reduced Speed School Zone X

For more information, please see the Connected Vehicle Environment Concept of Operations

Page 10: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

10

SYSTEM REQUIREMENTS

Page 11: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

11

Development Process

• Break down system into functional group categories.

• Develop technical requirements for system sub-components.

• Link requirements with user needs, constraints, and interfaces as described by the ConOps.

SYSTEM REQUIREMENTS

Page 12: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

12

Functional Group

Common

DSRC Messages

Roadside Equipment

Traffic Management Center

Transit Management Center

V2I Mobility

V2I Safety

V2V Safety

Vehicle Onboard EquipmentPlatooning Provider Central

Management System

Traffic Signal Controller / School Zone

Signal

RSU

Traffic CV Management

System

HDV OBU

HDV Databus

LDV OBU

LDV Databus

Network Time Source

Location and Time Source (GNSS)

Loc and Time Data Source

(GNSS)

Ohio CORS

Transit Vehicle OBU

Transit Vehicle Databus

Emergency Vehicle OBU

Emergency Vehicle Databus

Other OBU

Transit CV Management

System

Smart Columbus Operating

System

Security and Credentials

Management System

LDV Operator

Human Interface(existing)

23. Local

22. Backhaul

5. Over-the-Air (TBD)

6. DSRC

4. Local

9. DSRC7. Local

8. UI16. Backhaul 15. Backhaul

14. Satellite

11. Satellite

12. Satellite

13. Satellite

10. Satellite

17. Backhaul(Internet)

20. DSRC

27. Over-the-Air (Wi-Fi)

26. Local

2. DSRC1. Local

18. DSRC

19. DSRC

24. Backhaul(Internet)

25. Backhaul(Internet)

21. Backhaul

Traffic CV Mgmt. Staff

3. UI

Transit CV Mgmt. Staff

28. UI

Emergency Vehicle

Operator

29. UI

System Boundary

System Boundary

SYSTEM REQUIREMENTS

Step 1: Break down system into functional group categories.

Page 13: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

13

Functional Group

Common

DSRC Messages

Roadside Equipment

Traffic Management Center

Transit Management Center

V2I Mobility

V2I Safety

V2V Safety

Vehicle Onboard Equipment

System Boundary

System Boundary

SYSTEM REQUIREMENTS

Step 1: Break down system into functional group categories.

Platooning Provider Central

Management System

Traffic Signal Controller / School Zone

Signal

RSU

Traffic CV Management

System

HDV OBU

HDV Databus

LDV OBU

LDV Databus

Network Time Source

Location and Time Source (GNSS)

Loc and Time Data Source

(GNSS)

Ohio CORS

Transit Vehicle OBU

Transit Vehicle Databus

Emergency Vehicle OBU

Emergency Vehicle Databus

Other OBU

Transit CV Management

System

Smart Columbus Operating

System

Security and Credentials

Management System

LDV Operator

Human Interface(existing)

23. Local

22. Backhaul

5. Over-the-Air (TBD)

6. DSRC4. Local

9. DSRC7. Local

8. UI16. Backhaul 15. Backhaul

14. Satellite

11. Satellite

12. Satellite

13. Satellite

10. Satellite

17. Backhaul(Internet)

20. DSRC

27. Over-the-Air (Wi-Fi)

26. Local

2. DSRC1. Local

18. DSRC

19. DSRC

24. Backhaul(Internet)

25. Backhaul(Internet)

21. Backhaul

Traffic CV Mgmt. Staff

3. UI

Transit CV Mgmt. Staff

28. UI

Emergency Vehicle

Operator

29. UI

Page 14: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

14

SYSTEM REQUIREMENTS

Step 2: Develop technical requirements for system components

Page 15: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

15

SYSTEM REQUIREMENTS

Step 3: Link requirements with user needs, constraints, and interfaces as described by the ConOps

Page 16: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

16

REQUIREMENTS BY THE NUMBERS

Page 17: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

17

TONY ENGLISH

Lead System Design forWyoming CV Pilot

Trihydro

SUBJECT MATTER EXPERTS PANEL

MIKE SCHULMAN

Program Manager,

Crash Avoidance Metrics

Partnership

JIAQI MA

Assistant Professor,NEXT Mobility Lab Lead,University of Cincinnati

NICK HEGEMIER

Managing Director of Infrastructure,

Ohio Department of

Transportation

Page 18: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

18

• Four categories of requirements are discussed

• Interoperability

• Applications

• Human Machine Interface (HMI)

• Operations

• For each category:

• Description

• Example requirements

• Questions and Discussion

• Procurement

SUBJECT MATTER EXPERTS PANELREQUIREMENTS DISCUSSION

Page 19: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

1919

INTEROPERABILITY SYSTEM REQUIREMENTS

Communication on

specific interfaces (internal and

external) are constrained to

specific standards so that the

CVE can be easily expanded and

will be able to interact with

external systems that use the

same widely-accepted standards

Page 20: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

2020

INTEROPERABILITY SYSTEM REQUIREMENTS

Requirement ID Description

CVE-CN1648-V01 All CVE components that utilize DSRC shall comply with all of the following:1. SAE J2735_201603 - Dedicated Short Range Communications (DSRC) Message Set Dictionary.2. SAE J 2945/1 - On-Board System Requirements for V2V Safety Communications3. SAE J 2945/4 (draft) - DSRC Messages for Traveler Information and Basic Information Delivery4. IEEE 802.11p - Wireless Access in Vehicular Environments.5. IEEE 1609.2 - IEEE Standard for Wireless Access in Vehicular Environments -- Security Services for Applications and Management

Messages6. IEEE 1609.3 - IEEE Standard for Wireless Access in Vehicular Environments (WAVE) -- Networking Services.7. IEEE 1609.4 - IEEE Standard for Wireless Access in Vehicular Environments (WAVE) -- Multi-Channel Operation.8. NTCIP 1202 - NTCIP Object Definitions for Actuated Traffic Controllers.9. NTCIP 1211 - NTCIP Objects for Signal Control and Prioritization (SCP)

CVE-FN1308-V01 An RSU shall acquire time from the Location and Time Source (LTS) interface in accordance with J2945/1 section 6.2.4.

CVE-FN1309-V01 An RSU shall acquire location from the LTS interface in accordance with J2945/1 section 6.2.1.

CVE-FN1311-V01 An RSU shall use Coordinated Universal Time (UTC) time for all logged data (e.g., events logs, probe vehicle data) based on the format defined in J2735 section 6.19 and epoch of January 1st 1970.

Page 21: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

2121

INTEROPERABILITY QUESTIONS/FEEDBACK

1. Aside from adhering to existing communications and messaging standards, what other

requirements should be included to maximize the likelihood of interoperability with other

CV systems?

2. Are there certain data elements in standards that should be included or interpreted

differently? For instance, are there optional field of J2735 that are critical to implement?

3. Are there any messages that are being considered for future standards that should be

considered for the CV Environment?

Page 22: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

2222

CV APPLICATION SYSTEM REQUIREMENTS

Requirements that describe and

constrain the communications

and functions that enable CV

Applications

V2V Safety

V2I Safety

V2I Mobility

Page 23: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

2323

CV APPLICATION SYSTEM REQUIREMENTS

Requirement ID Description

CVE-FN1298-V01 An LDV OBU (host) shall issue an alert to the LDV Operator via the HMI when the OBU-equipped

(host) vehicle will enter an RSU-equipped school zone over the active school zone speed limit

CVE-FN1299-V01 An LDV OBU (host) shall issue an alert when the OBU-equipped (host) vehicle is inside of an RSU-

equipped school zone over the active school zone speed limit

CVE-FN1300-V01 The LDV OBU (host) shall parse received RSMs to identify the school zone speed limit (J2945/4).

CVE-FN1301-V01 The LDV OBU (host) shall parse received RSMs to identify when the school zone speed limit is active.

CVE-FN1302-V01 The LDV OBU (host) shall parse received RSMs to identify the applicable regions of use geographical

path (J2945/4).

CVE-FN1303-V01 The LDV OBU (host) shall issue a school zone alert when all of the following conditions are

concurrently met:1. OBU-equipped (host) vehicle is traveling towards the segment where the situational awareness applies.

2. The OBU-equipped (host) vehicle is expected to enter the school zone but not below the school zone speed limit (given its current

location, motion, and expected braking rate).

3. During active school zone hours

CVE-FN1304-V01 The LDV OBU (host) shall issue a school zone alert when all of the following conditions are

concurrently met:1. OBU-equipped (host) vehicle is within the segment where the situational awareness applies.

2. OBU-equipped (host) vehicle is traveling above the school zone speed limit.

3. During active school zone hours

Page 24: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

2424

CV APPLICATION QUESTIONS/FEEDBACK

1. Columbus wants to make sure that it is deploying applications that are deployment-ready.

What level of specificity is needed in the requirements to ensure this?

2. What is the best way to verify these applications meet their functional/performance

requirements and have been demonstrated in an operational environment?

3. Is there a strong use case for which it may be beneficial to use data available though the

OBD-II port vs. data gathered from sensors on the OBU for populating the BSM and for

use in safety applications?

Page 25: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

2525

HMI REQUIREMENTS

Requirements that constrain the

manner in which the driver is

alerted (output of CV

applications).

Apply methods used by CV pilot

sites for choosing the type of HMI

to implement.

Source: https://www.kaspersky.com/blog/evolution-of-human-car-interaction/6953/

Page 26: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

2626

HMI SYSTEM REQUIREMENTS

Requirement ID Description

CVE-IF1246-V01 An LDV OBU shall issue alerts to the LDV Operator via an HMI

CVE-FN1123-V01 The HMI shall present alerts to drivers using a devise that drivers are familiar with and limits driver interaction.

CVE-FN1286-V01 An LDV OBU (host) shall issue an alert to the LDV Operator via the HMI when a red-light violation will occur at an RSU-equipped intersection

CVE-FN1202-V01 The LDV OBU shall provide messages that can be seen and/or heard by the LDV Operator via the HMI from the LDV Vehicle Operator's normal seating position

CVE-FN1214-V01 The LDV OBU Auditory signals (via the HMI) shall be loud enough to overcome masking sounds from road noise, the cab environment, and other equipment

CVE-FN1213-V01 The LDV OBU shall provide a visual output that is similar in look and feel from various applications when presenting information to LDV Operators via the HMI

Page 27: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

2727

HMI QUESTIONS/FEEDBACK

1. What should be considered when designing output that is presented to drivers?

2. Given that Columbus will be undertaking a recruitment effort to have these devices

installed on private vehicles, are there any aspects of an HMI that will make a private

citizen more or less inclined to participate?

3. What factors should go into deciding which HMI to procure? Given that Columbus is

looking to procure (not design from scratch) an HMI, should requirements governing the

types of alerts guide the selection of an HMI, or is it more reasonable to allow the

selected HMI to constrain the design of the alerts?

Page 28: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

2828

OPERATIONAL SYSTEM REQUIREMENTS

Specifes system security

processes, how updates should

be managed, and outlines how

the system is monitored

Outlines the responsibilities of

each actor in the CVE

Page 29: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

2929

OPERATIONAL SYSTEM REQUIREMENTS

Requirement ID Description

CVE-MT1595-V01 DPS shall maintain a list of OBU equipment and contact information for vehicle owners that have

OBUs installed

CVE-MT1593-V01 DPS shall manage Support Staff to troubleshoot and diagnose RSU and OBU issues.

CVE-FN1449-V01 The Traffic CV Management System shall monitor the status of RSUs

CVE-PR1458-V01 The Traffic CV Management System shall notify designated personnel within five minutes of a monitored function becoming unavailable

CVE-SR1459-V01 Monitoring systems shall be used to detect abnormal unauthorized activity on an IP connection.

CVE-SR1460-V01 The Traffic CV Management System shall monitor the DSRC communications performance to detect DoS attacks

CVE-SR1461-V01 The Traffic CV Management System should investigate and monitor the data traffic usage to detect unapproved use of the IP connection

CVE-FN1463-V01 The Traffic CV Management System shall monitor tamper alert devices

Page 30: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

3030

OPERATIONS QUESTIONS/FEEDBACK

1. What is the best way to provide application/functional updates to OBUs after they have

been installed in private vehicles? How should equipment failure be handled, considering

we are not intending to have face-to-face engagements with drivers?

2. What changes in traffic management activities should the Department of Public Service

expect to operate and maintain the CV Environment once it is installed?

Page 31: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

3131

NEXT STEPS – PROCUREMENT

System Requirements provide specifications

and constraints on hardware, software, and

services (such as installation) that will ultimately

be procured

A balance must be found between existing City

policy for procurement, and the processes that

will be developed for procuring CV equipment.

Page 32: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

3232

PROCUREMENT QUESTIONS/FEEDBACK

1. Is it recommended that the same vendor be used to supply both the software and

hardware for a given device?

2. What are the advantages and disadvantages of using multiple OBU vendors? Multiple

RSU vendors?

Page 33: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

33

Installation Development

Ongoing – March 2019

Interface Control Document

December 2018 – April 2019

System Design

February 2019 – August 2019

Test Plan

May 2019 – September 2019

Equipment and Service Procurement

January 2019 – July 2019

Deploy / Test on roadside and in vehicles

August 2019 – August 2020

CV Environment Live

July 2020

WHERE WE GO FROM HERE

Page 34: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

34

USDOT SMART CITY CHALLENGE

PROGRAM INQUIRIES:

Kate Hartman, Chief - Research, Evaluation

and Program Management

Intelligent Transportation Systems

Joint Program Office

[email protected]

SMART COLUMBUS INQUIRIES:

Alyssa Chenault, Communications

Project Manager

[email protected]

Upcoming Smart Columbus Webinars:

• Prenatal Trip Assistance ConOps – 11/14

• Event Parking Management System

Requirement – 11/15

• Common Payment System System

Requirements – 11/28

• Overview of Emerging Technologies:

Connected Electric Autonomous Vehicles and

Truck Platooning – 1/30

HOW TO STAY CONNECTED

Webinar recording and materials will be available at itsa.org and smart.columbus.gov

Page 35: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

35

COMMENTS

Public comment period open for the CONNECTED VEHICLE ENVIRONMENT System Requirements:

• October 29th to November 12th

• Where to find it:• View the System Requirements at: https://smart.columbus.gov/projects

• Click CONNECTED VEHICLE ENVIRONMENT

• Direct link to file: https://smart.columbus.gov/uploadedFiles/Projects/SCC-B-SysReq-CVE-FINAL%20v1.1.pdf

• How to comment:• Please email comments to Korina Depenhart: [email protected]

• Subject line: Connected Vehicle Environment Comments

• Include your contact information

• State whether or not you represent a vendor interest

Page 36: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

36

QUESTIONS?

Page 37: Connected Vehicle Environment System Requirements · COTA Supervisor Vehicle 25 Emergency Vehicle Fire Truck/EMS 30 Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 Transit Vehicle

37

SIGN UP FOR OUR E-NEWSLETTERContact:

[email protected]

Columbus.gov/smartcolumbus

@SmartCbus

LEARN MORE