Demonstration Site Map and Installation Schedule · 1/24/2020 · Demonstration Site Map and Installation Schedule – Final Report | Smart Columbus Program | iii Abstract The City

Smart Columbus

Demonstration Site Map and Installation Schedule

for the Smart Columbus

Demonstration Program

FINAL REPORT | January 24, 2020

Produced by City of Columbus

Notice

This document is disseminated under the sponsorship of the Department of Transportation

in the interest of information exchange. The United States Government assumes no liability

for its contents or use thereof.

The U.S. Government is not endorsing any manufacturers, products, or services

cited herein and any trade name that may appear in the work has been included

only because it is essential to the contents of the work.

Acknowledgment of Support

This material is based upon work supported by the U.S. Department of

Transportation under Agreement No. DTFH6116H00013.

Disclaimer

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.

Demonstration Site Map and Installation Schedule – Final Report | Smart Columbus Program | i

Acknowledgments

The Smart Columbus Program would like to thank project leads for each of the Smart Columbus projects for

their assistance in drafting and reviewing this Demonstration Site Map and Installation Schedule.

Demonstration Site Map and Installation Schedule – Final Report | Smart Columbus Program | iii

Abstract

The City of Columbus, Ohio, won the United States Department of Transportation Smart City Challenge,

receiving a pledge of $40 million to develop innovative transportation solutions. For its Smart Columbus

program, the City will use advanced technologies in the service of all ages and economic groups while

bridging the digital divide. The program will integrate Intelligent Transportation Systems and connected and

autonomous vehicle technologies into other operational areas. As owners and co-creators of the program,

the residents of Columbus will be closely engaged in driving the outcomes for each project.

This report, titled Smart Columbus Demonstration Program Site Map and Installation Schedule, identifies

the geographic area of the Smart Columbus program and the physical locations for all hardware elements of

the program’s projects. Locations discussed include those related to key issues, those currently containing

or proposed to contain roadside technology, and those related to operations of vehicles that are connected

using in-vehicle and roadside technology and operations of autonomous vehicles. In addition, this report

describes other efforts that align with the City’s proposed strategies for smart transportation design.

Information in this report will be updated if major changes arise while the demonstration effort is pending.

This report also outlines the installation schedule for each project, by type of physical infrastructure,

indicating:

• Responsible organization or individual

• Start and end dates for installation

• Milestone(s)

• Start and end dates for testing

While focusing on locations and schedule, this report also briefly describes the geographic boundaries of

each project and the issues the Smart Columbus program will address. More detailed overviews of the

proposed solutions are given in each project's systems engineering documentation which can be found on

the Smart Columbus website.1

1 www.smart.columbus.gov/

https://smartcolumbusprogram.sharepoint.com/TaskBWorking/www.smart.columbus.gov/

Demonstration Site Map and Installation Schedule – Final Report | Smart Columbus Program | v

Table of Contents

Project Descriptions ........................................................................................................... 1

1.1.1. Smart Columbus Operating System ........................................................................................ 2

1.1.2. Enabling Technologies ............................................................................................................... 2

1.1.3. Enhanced Human Services....................................................................................................... 3

1.1.4. Emerging Technologies.............................................................................................................. 4

Smart Columbus System of Systems.............................................................................. 4

2.1. Deployment Area ................................................................................................................. 7

2.2. Key Issues and Geographic Scope by Project .............................................................. 9

2.2.1. Connected Vehicle Environment .............................................................................................. 9

2.2.2. Multimodal Trip Planning Application/Common Payment System ...................................... 14

2.2.3. Mobility Assistance for People with Cognitive Disabilities .................................................... 15

2.2.4. Smart Mobility Hubs ................................................................................................................. 16

2.2.5. Prenatal Trip Assistance .......................................................................................................... 18

2.2.6. Event Parking Management .................................................................................................... 20

2.2.7. Connected Electric Autonomous Vehicles ............................................................................. 21

3.1. Connected Vehicle Environment .................................................................................... 25

3.2. Smart Mobility Hubs ......................................................................................................... 25

3.3. Connected Electric Autonomous Vehicles ................................................................... 26


4.1.1. Connected Vehicle Environment Infrastructure ..................................................................... 35

4.1.2. Connected Vehicle Environment Installation Locations ....................................................... 36

4.1.3. Connected Vehicle Environment Infrastructure Installation Entities and Responsibilities 45


4.2.1. Infrastructure Installation .......................................................................................................... 48

4.2.2. Overview of Infrastructure by Location ................................................................................... 49

4.2.3. Infrastructure Installation Entities and Responsibilities ......................................................... 62


4.3.1. Route Details ............................................................................................................................. 62

4.3.2. Station Locations ...................................................................................................................... 66

Table of Contents

vi | Smart Columbus Program | Demonstration Site Map and Installation Schedule – Final Report

4.3.3. Connected Electric Autonomous Vehicles ............................................................................. 70




Table of Contents

Demonstration Site Map and Installation Schedule – Final Report | Smart Columbus Program | vii

List of Tables

Table 1: Connected Vehicle Environment Project Scope .............................................................................. 3

Table 2: Multivehicle Crashes (January 2014 through December 2016) .................................................... 11

Table 3: Intersections with Highest Numbers of Vehicle Crashes Along Proposed Connected Vehicle

Environment Corridors (2017) ..................................................................................................................... 12

Table 4: Compliance with School Zone Speeds.......................................................................................... 13

Table 5: Connected Vehicle Environment Roadside Unit and Related Key Infrastructure Components .... 28

Table 6: Connected Vehicle Environment Onboard Unit Infrastructure Components and Installation

Locations ..................................................................................................................................................... 31

Table 7: Infrastructure Components at Smart Mobility Hub Locations ........................................................ 31

Table 8: Infrastructure Components at Connected Vehicle Autonomous Vehicle Stations ......................... 32

Table 9: Connected Vehicle Applications and Vehicle Classes for Smart Columbus Connected Vehicle

Environment ................................................................................................................................................ 34

Table 10: Connected Vehicle Application by Intersection ........................................................................... 36

Table 11: Characteristics of In-Vehicle Equipment by Vehicle Class .......................................................... 43

Table 12: Connected Vehicle Environment Installation Entities and Responsibilities ................................. 46

Table 13: Smart Mobility Hub Amenities by Location .................................................................................. 49

Table 14: Smart Mobility Hubs Infrastructure Installation Entities and Responsibilities.............................. 62

Table 15: Connected Electric Autonomous Vehicles Infrastructure Installation Entities and Responsibilities

.................................................................................................................................................................... 71

Table 16: Connected Vehicle Environment Installation Milestones............................................................. 73

Table 17: Connected Vehicle Environment Detailed Installation Activities and Schedule .......................... 74

Table 18: Smart Mobility Hubs Installation Milestones ................................................................................ 75

Table 19: Smart Mobility Hubs Detailed Installation Activities and Schedule ............................................. 75

Table 20: Connected Electric Autonomous Vehicles Installation Milestones .............................................. 76

Table 21: Connected Electric Autonomous Vehicles Detailed Installation Activities and Schedule ............ 76

Table 22: Acronym List ................................................................................................................................ 79

Table 23: Central Ohio Transit Authority Fixed-Route Vehicles .................................................................. 83

Table 24: Central Ohio Transit Authority Paratransit Vehicles .................................................................... 91

Table 25: Central Ohio Transit Authority Supervisor Vehicles ..................................................................... 93

Table 26: Police Vehicles ............................................................................................................................ 94

Table 27: Fire Vehicles ................................................................................................................................ 96

Table 28: Department of Public Service Fleet ............................................................................................. 99

Table 29: Franklin County Engineers Office Fleet ..................................................................................... 105

Table of Contents

viii | Smart Columbus Program | Demonstration Site Map and Installation Schedule – Final Report

List of Figures

Figure 1: Smart Columbus Projects .............................................................................................................. 2

Figure 2: Smart Columbus System of Systems ............................................................................................ 5

Figure 3: Smart Columbus Demonstration Site Map .................................................................................... 8

Figure 4: Connected Vehicle Environment High-Level Deployment Area .................................................. 10

Figure 5: Central Ohio Transit Authority Service Area ................................................................................ 15

Figure 6: Proposed Smart Mobility Hub Locations...................................................................................... 17

Figure 7: Major Cities and Freeways Franklin County, Ohio ...................................................................... 19

Figure 8: Downtown Columbus and the Short North Area .......................................................................... 21

Figure 9: Connected Electric Autonmous Vehicle Route from Linden Transit Center to St. Stephens

Community House ....................................................................................................................................... 23

Figure 10: Smart Columbus Program Key Infrastructure Installation Locations ......................................... 27

Figure 11: Connected Vehicle Environment Applications by Intersection ................................................... 44

Figure 12: Organizations Responsible for Connected Vehicle Environment Infrastructure Installation ..... 45

Figure 13: Smart Mobility Hub at Columbus State Community College ..................................................... 50

Figure 14: Smart Mobility Hub at Linden Transit Center ............................................................................. 51

Figure 15: Dockless Parking Sign and Parking Zone at Linden Transit Center .......................................... 52

Figure 16: Ride-Hailing Sign and Pavement Markings at Linden Transit Center ....................................... 52

Figure 17: Smart Mobility Hub Sign at Linden Transit Center ..................................................................... 53

Figure 18: Smart Mobility Hub at Columbus Metro Library – Linden Branch ............................................. 54

Figure 19: Smart Mobility Hub Sign at Metro Library – Linden Branch ...................................................... 55

Figure 20: Smart Mobility Hub Sign, Dockless Parking Sign, and Dockless Parking Zone at Metro Library

– Linden Branch .......................................................................................................................................... 55

Figure 21: Smart Mobility Hub at Northern Lights Park and Ride ............................................................... 56

Figure 22: Ride-Hailing Sign at Northern Lights Park and Ride ................................................................. 57

Figure 23: Smart Mobility Hub Sign, Dockless Parking Sign and Dockless Parking Zone at Northern Lights

Park and Ride ............................................................................................................................................. 57

Figure 24: Smart Mobility Hub at St. Stephens Community House ............................................................ 58

Figure 25: Smart Mobility Hub Sign at St. Stephens Community House .................................................... 59

Figure 26: Smart Mobility Hub at Easton Transit Center ............................................................................ 60

Figure 27: Smart Mobility Hub Sign at Easton Transit Center .................................................................... 61

Figure 28: Ride-Hailing Sign at Easton Transit Center ............................................................................... 61

Figure 29: Connected Electric Autonomous Vehicles Route Overview ...................................................... 64

Figure 30: Smart Columbus Connected Electric Autonomous Vehicles ..................................................... 65

Figure 31: Linden Transit Center Connected Electric Autonomous Vehicles Station ................................. 66

Figure 32: Rosewind Resident Council Connected Electric Autonomous Vehicles Station ....................... 67

Figure 33: Douglas Community Recreation Center Connected Electric Autonomous Vehicles Station ..... 68

Figure 34: St. Stephens Community House Connected Electric Autonomous Vehicles Station ................ 69

Figure 35: CEAV Charging Location and Infrastructure .............................................................................. 70

Demonstration Site Map and Installation Schedule – Final Report | Smart Columbus Program | 1

Introduction

The City of Columbus, Ohio, received a pledge of $40 million to develop innovative solutions to pressing

transportation issues. As the winner of the Smart City Challenge presented by the United States Department

of Transportation (USDOT), the City will use smart design and advanced technologies to serve all ages and

economic groups while bridging the digital divide. The Smart Columbus program will integrate Intelligent

Transportation Systems (ITSs) and connected and autonomous vehicle technologies into other operational

areas and leverage the new information these technologies provide. As owners and co-creators of the

program, the residents of Columbus will be closely engaged in driving the outcomes for each project.

This report, titled Demonstration Site Map and Installation Schedule, identifies the specific geographic area

of the Smart Columbus program.

Locations discussed include those related to key issues, those currently containing or proposed to contain

roadside technology, and those related to connected and automated vehicle (AV) operations. In addition,

this report describes other efforts that align with the City’s proposed strategies for smart transportation

design. Information in this report will be updated if major changes arise while the demonstration effort is

pending.

This report also outlines the installation schedule for each project, by type of physical infrastructure,

indicating:

• Responsible organization or individual

• Start and end dates for each element’s installation

• Milestone(s)

• Start and end dates for testing

This document focuses on those Smart Columbus projects that contain a physical infrastructure or hardware

component. Chapter 1 and Chapter 2 briefly describe all Smart Columbus projects and the issues each will

address. Chapter 3, Chapter 4, and Chapter 5 focus on projects that will deploy physical infrastructure or

hardware component, providing detailed site maps and installation schedules. More detailed descriptions of

proposed solutions are in the project-specific systems engineering documentation, which is on the Smart

Columbus website.2

PROJECT DESCRIPTIONS

Smart Columbus projects are grouped under three themes: Enabling Technologies, Enhanced Human

Services, and Emerging Technologies. The Smart Columbus Operating System (Operating System) is being

developed and will provide the backbone for all current and future smart city projects. Figure 1 shows the

Smart Columbus program projects, organized under the three themes, with all falling under the umbrella of

the Operating System.

2 www.smart.columbus.gov

Chapter 1. Introduction

2 | Smart Columbus Program | Demonstration Site Map and Installation Schedule – Final Report

Figure 1: Smart Columbus Projects

Source: City of Columbus

1.1.1. Smart Columbus Operating System

The Operating System will provide the backbone of Smart Columbus, bringing the innovations to life. It is

being designed and built to collect data from various sources, including public, nonprofit, education, and

private sector contributors. Inputs may come from other systems, from devices, or from people, all of which

are critical for building this ecosystem of innovation. Data will be available for analytics and visualization.

The Operating System platform is being designed for Big Data, Machine Learning and Artificial Intelligence,

Analytics, and complex data exchange. It will capture data and provide access for multiple users to

aggregate, fuse, and consume data.

Datasets to be housed in the Operating System include the Smart Columbus demonstration projects,

traditional transportation data, and data from other community partners, such as food pantries and medical

services. The Operating System will be scalable and will demonstrate the potential for serving city and

private-sector needs well beyond the life of the Smart City Challenge award period.

1.1.2. Enabling Technologies

Advanced enabling technologies leverage the existing transportation technology foundation in innovative

ways to enhance the transportation infrastructure’s ability to provide for safety and mobility. They empower

infrastructure deployments that increase the City’s capabilities by providing rich data streams and

infrastructure that can respond on demand. Currently just one project is planned under this theme, the

Connected Vehicle Environment (CVE) project. This project involves leveraging cutting-edge technology to

improve efficiency and safety in roadway corridors and intersections.

The CVE project aims to address high-crash and congested intersections and corridors. Crashes have

involved vehicles, bicyclists, and pedestrians. Congested corridors reduce mobility for emergency vehicles,

freight, and transit buses.



The CVE team selected corridors for the CVE project using regional crash data and considering presence of

enhanced transit services and recent infrastructure investments, as well as the corridors’ relationships to

other Smart Columbus projects. The specific issues targeted by the CVE project are discussed further in

Chapter 2.

The CVE project will use connected vehicle (CV) technologies and applications, focusing on building out the

physical CV hardware and software such as Roadside Units (RSUs), Onboard Units (OBUs), front and

backhaul communications, and equipment interfaces. The CVE will generate needed transportation-related

data that will be used by other Smart Columbus project applications. The project will also deploy CV-specific

applications that will leverage the data generated by the infrastructure to deliver real-time safety and mobility

services.

The CVE will connect up to 1,800 vehicles and 90 smart intersections across the Central Ohio region. The

CVE Safety applications will be installed in multiple vehicle types including transit buses, first responder

vehicles, city and partner fleet vehicles, and private vehicles. The software will allow emergency vehicles

and the Central Ohio Transit Authority (COTA) Cleveland Avenue CMAX Bus Rapid Transit (CMAX BRT)

fleet to receive priority at traffic signals when needed to maximize safety or efficiency. The Operating System

will process the data created by the connected system by aggregating it, making it anonymous, removing

identifying information, and storing it for later analysis and visualization.

CV infrastructure will be deployed along four major corridors or areas. In-vehicle device deployment will

target populations that are located near or that frequently use the infrastructure deployment corridors. Table

1 summarizes the CVE scope.

Table 1: Connected Vehicle Environment Project Scope

Infrastructure Applications and Data

100+ RSUs

The project will install ~100 RSUs and necessary communications equipment at ~90 signalized intersections in the project areas.

1,500 – 1,800 OBUs

The project will install OBUs on participating private, fleet, emergency, transit, and freight vehicles.

CV Applications

The project will deploy vehicle-to-vehicle safety, vehicle-to-infrastructure safety, and vehicle-to-infrastructure mobility applications.

Data Capture

The project will capture, relate, store, and respond to data generated by the infrastructure and used by the applications for traffic management.


1.1.3. Enhanced Human Services

The Enhanced Human Services theme aims to meet human needs through technology, focusing on

prevention and problem remediation to improve quality of life. Projects under this theme will improve access

to jobs, healthcare, and events. Specific projects include:

• Multimodal Trip Planning Application (MMTPA)/Common Payment System (CPS) – This project will

provide a single way to plan, book, and pay for a door-to-door multimodal trip in the Columbus region

that includes multiple modes of transportation.

• Smart Mobility Hubs (SMHs) – This project will deploy Interactive Kiosks (IKs) for access to

technology resources for people without smartphones so they can transfer between various modes of

transportation.



• Mobility Assistance for People with Cognitive Disabilities (MAPCD) – This project will develop an

application to help people with cognitive disabilities navigate around the Columbus area and use the

fixed-route transit system.

• Prenatal Trip Assistance (PTA) – This project will develop an application to provide access for

prenatal travelers to on-demand transportation for prenatal doctor visits.

• Event Parking Management (EPM) – This project will help Columbus-area travelers find, reserve, and

pay for parking in the downtown and Short North regions.

1.1.4. Emerging Technologies

New technologies that are currently developing or that will be developed over the next five to 10 years will

substantially alter the business and social environment. By focusing on key Emerging Technologies, the City

will be able to demonstrate potential solutions to future transportation and data collection challenges.

The current project under this theme is the Connected Electric Autonomous Vehicles (CEAV) project. This

project was initiated because the use of connected and automated shuttles has been widely proposed as a

solution to the first-mile/last-mile (FMLM) problem. Therefore, this project will address, investigate and

develop solutions to the social and technical challenges associated with the use of CEAV technology for

safer and more efficient access to jobs.

The CEAV project will develop holistic modeling and simulation tools that will help people solve the

connected and automated mobility technical challenges. After the tools are developed, proof-of-concept

work and pilot deployments will demonstrate that connected and automated mobility can solve the FMLM

problem and improve access to jobs.

SMART COLUMBUS SYSTEM OF SYSTEMS

The Smart Columbus program has many interrelated systems that work together to provide a System of

Systems (SoS). Information from various projects is shared with the Operating System. Real-time and

archived data are maintained in the Operating System for use by other Smart Columbus projects and future

applications. The SoS provides Smart Applications (Apps), smart vehicles, and infrastructure to travelers in

the Columbus area. The Operating System enables the SoS to share data with many other internal and

external systems, providing the framework for the services provided.

The smart infrastructure element of the SoS contains field device items such as the RSUs in the CVE

project corridors and IKs in the SMH locations. CVs include the installed OBUs in various vehicle types.

Apps include the software that will deliver other Smart Columbus project capabilities such as those provided

by the MMTPA/CPS and PTA projects.

The Operating System is the repository for all performance data from the smart infrastructure and smart

vehicles and the hosting platform that allows direct integration of the Apps.

Finally, the CVE project depends on the Security Credential Management System (SCMS), Continuously

Operating Reference System (CORS), and Global Network Satellite System (GNSS) services.

Figure 2 shows the relationship of the SoS to external travelers and systems. The focus for this document is

to describe the challenges associated with each project that will be addressed by installing infrastructure

that contains a smart component: CVE, SMH, and CEAV. The document will also describe the individual

elements that will be installed as part of each of the project as well as where and when they will be installed.



Figure 2: Smart Columbus System of Systems



High-Level Deployment Map

Smart Columbus will demonstrate effective implementation of a comprehensive portfolio of connected

technologies that solve focused, relatable City issues and enhance mobility across the region. Like most

midsized cities in the United States, the City of Columbus is divided into several neighborhoods, commercial

districts, and other geographic zones that are connected by highways, transit, people, and culture. While

some projects will be deployed within specific areas of the City, many projects will be deployed citywide and

be integrated with the Operating System.

2.1. DEPLOYMENT AREA

Figure 3 captures the following known elements of the deployment area for the projects:

• For CVE, the deployment corridors are highlighted, including Cleveland Avenue, High Street, Morse

Road, and Alum Creek Drive. The intersections where Freight Signal Priority (FSP) will be deployed

are highlighted to indicate the freight corridors. In addition, the CMAX BRT corridors are indicated for

reference. Lastly, the ZIP codes from which private vehicles will be recruited (and where installation

will be targeted) are shaded blue.

• For MMTPA/CPS, the first release of the application includes both COTA and the Ohio State

University (OSU) Campus Area Bus Service (CABS) as key providers. These service routes are

called out on the map.

• For MAPCD, the OSU callout box indicates the project’s background and focus on the OSU

Prevocational Integrated Education and Campus Experience (PIECE) program, from which focus and

test group participants were recruited to help refine the application’s functionality. The testing of

MAPCD also centered on OSU’s campus; the application includes both COTA and CABS buses.

MAPCD deployment is not limited to PIECE program participants; deployment is Citywide in

collaboration with OSU and ARC Industries, a community organization that helps find employment for

adults with developmental disabilities. ARC Industries is not shown on the map as it is an

administrative office only, not one of the employment/job center origins or destinations for the project.

• For PTA, Franklin County, Ohio, is the focused recruiting and participation area for this application.

• For SMH, the proposed hub locations are called out. The existing and proposed amenities,

infrastructure installation locations and schedule of deployment are discussed in detail later in this

report.

• For CEAV, both the Smart Circuit and Linden routes are called out, with stations identified. Of the two

CEAV site infrastructure installation locations, only the Linden route is discussed in detail later in this

report, as it is the element deployed by the Smart Columbus CEAV project.

• For EPM, the downtown and Short North areas of Columbus are highlighted, because this application

will focus on parking providers in these areas and visitors traveling into and within these areas.

Chapter 2. High-Level Deployment Map


Figure 3: Smart Columbus Demonstration Site Map

Source: google.com/maps , City of Columbus

http://www.google.com/maps/



2.2. KEY ISSUES AND GEOGRAPHIC SCOPE BY PROJECT

This section briefly summarizes the issues to be addressed by the Smart Columbus projects and identifies

their geographic location and boundaries; however, it is not intended to provide a thorough examination of

all the issues each project is designed to address. Each project’s concept of operations, trade study, or

operational concept provides a more detailed justification for the project. All systems engineering documents

for the Smart Columbus projects can be found on the Smart Columbus website.3

2.2.1. Connected Vehicle Environment

The CVE project is focused to address safety and mobility issues, and also considers potential challenges

traffic and transit managers face and provides data that may be useful to them. CVE issues are:

• Vehicle operator safety

• Intersection safety

• School zone speed adherence

• Transit vehicle schedule adherence

• Emergency response times

• Freight-related traffic congestion

• Data gaps for:

Traffic management

Transit management

Solutions to these issues were developed considering data related to crashes, transit vehicle schedules,

and emergency response times. The following major corridors and areas comprise the CVE project area:

• High Street (Fifth Avenue to Morse Road): South–north arterial through Columbus characterized by

dense mixed-use development; travels through Short North, OSU, and a dense urban neighborhood.

• Morse Road (High Street to Stygler Road): West-east route primarily flanked by strip mall or retail

development.

• Cleveland Avenue (Second Avenue to Morse Road): Southwest/northeast route has dense mixed-

use urban development; traverses one of the Columbus opportunity neighborhoods of Linden.

• Alum Creek Drive (SR-317 to I-270) serves a freight area in Columbus near Rickenbacker Airport.

Figure 4 shows the high-level geographic area of the deployment corridors, which were selected based on

stakeholder input, regional crash data, and locations of logistics companies that will participate in the

vehicle-side deployment. Details about specific infrastructure elements and applications by intersection will

be presented later in this document.

3 https://smart.columbus.gov/projects/

https://smart.columbus.gov/projects/



Figure 4: Connected Vehicle Environment High-Level Deployment Area

Source: opendata.columbus.gov, City of Columbus

2.2.1.1. SAFETY

Crashes are costly in terms of reduced mobility (congestion due to crashes), incident management,

emergency response, increased insurance premiums, vehicle repair costs, roadside repair costs, medical

costs, and loss of life. Generally, a lack of awareness of things such as location and speed of the driver’s

vehicle or of other vehicles on the part of one or more drivers is the cause of crashes between vehicles. The

current system has no method for improving driver alertness, especially in crash-imminent situations. Crash

data from the Ohio Department of Public Safety (DPS) indicates there was an average of five non-

intersection crashes per day along the proposed CV corridors during a 3-year span from January 2014 to

December 2016. These non-intersection crashes resulted in 1.77 injuries per day and one fatality every 219

days. CV technology will be used to enable applications targeted toward reducing these crashes. In the

CVE project, both vehicle-to-vehicle (V2V) and vehicle-to-infrastructure (V2I) safety applications will be

deployed to address this issue. The CVE project focuses primarily on the V2I safety applications, since they

are specific to the individual intersections of the project area.

Non-intersection crashes typically occur because a vehicle operator does not stop fast enough when

approaching the back of a slow-moving queue, follows a leading vehicle too closely, or cannot react in time

when a leading vehicle slows down suddenly. Angle crashes may occur at access points (such as a

driveway) when a vehicle crosses a traffic stream. Sideswipe crashes usually result from a vehicle

encroaching into another vehicle’s path during a lane change. The CVE could be used to enable

applications targeted toward reducing these non-intersection-related crashes that are most prominent along

the corridors of interest.

A crash is intersection-related if it occurs within, on an approach to, or on an exit from an intersection and

results from an activity, behavior, or control related to the movement of traffic through the intersection. Traffic

signals control the flow of vehicles, bicyclists, and pedestrians at signalized intersections. These signals

http://opendata.columbus.gov/



indicate to the vehicle operator to proceed toward and through the intersection (green); to clear the

intersection or prepare to stop (yellow); or slow down to a stop (red). A lack of awareness by one or more

drivers caused by location and speed of the driver’s vehicle or of other vehicles, or traffic control equipment,

is the cause of crashes. The current system does not have a method of improving driver alertness,

especially in crash-imminent situations.

Table 2 breaks down the number and type of multivehicle crashes on the corridors that are targeted for use

by light-duty vehicle (LDV) operators: Cleveland Avenue, High Street, and Morse Road.

Table 2: Multivehicle Crashes (January 2014 through December 2016)

Crash Type Total Crashes Resulting Number

of Injuries Resulting Number

of Fatalities

Non-Intersection-Related

Rear-end 1,292 438 1

Angle 820 257 2

Sideswipe, same direction

635 87 0

All others 239 79 0

Total 2,986 861 3

Intersection-Related

Rear-end 875 345 0

Angle 1225 648 1

Sideswipe, same direction

189 22 0

All others 109 67 1

Total 2,398 1,082 2

Source: Ohio DPS

In addition to overall intersection-related crashes, the City also considered the intersections with the highest

crash rates in the Central Ohio region. Table 3 shows 19 of the 100 intersections with the highest crash

rates in the Central Ohio region in 2017; these 19 are along the High Street, Morse Road, and Cleveland

Avenue corridors.4, 5

4 Mid-Ohio Regional Planning Commission – Previous High-Crash Intersections. Available at http://www.morpc.org/wp-

content/uploads/2017/12/001.Previous_HCL.pdf

5 Mid-Ohio Regional Planning Commission – Top 100 Regional High-Crash Intersections (2017). Available at http://www.morpc.org/wp-content/uploads/2017/12/001.HCL_2014_2016_Top100.pdf

http://www.morpc.org/wp-content/uploads/2017/12/001.Previous_HCL.pdf

http://www.morpc.org/wp-content/uploads/2017/12/001.Previous_HCL.pdf

http://www.morpc.org/wp-content/uploads/2017/12/001.HCL_2014_2016_Top100.pdf



Table 3: Intersections with Highest Numbers of Vehicle Crashes Along Proposed Connected

Vehicle Environment Corridors (2017)

2017 Rank 2016 Rank Location

3 8 Cleveland Avenue and Innis Road

4 18 Karl Road at Morse Road

8 22 Morse Road at Westerville Road

10 40 Cleveland Avenue at Hudson Street

11 21 Cleveland Avenue at Oakland Park

18 4 Cleveland Avenue at Morse Road

40 7 Morse Road at Northtowne Boulevard/Walford Street

41 35 Morse Road at Sunbury Road

44 29 High Street at Fifth Avenue

57 – Cleveland Avenue at 11th Avenue

65 75 McCutcheon Road at Stelzer Road

68 59 Morse Road at Stelzer Road

76 79 Morse Road at Sinclair Road

88 82 Cleveland Avenue at Weber Road

94 – High Street at North Broadway

97 80 Henderson Road at High Street

– 45 Cleveland Avenue at Fifth Avenue

– 77 Morse Road at Tamarack Boulevard

– 95 Seventh Avenue at High Street

Source: Mid-Ohio Regional Planning Commission

The CVE will be used to enable applications targeted toward reducing the types of crashes, listed in Table

2, which are most prominent at intersections in the corridors of interest shown in Figure 4 (above). Through

the CVE system, driver alertness can be improved by providing necessary alerts, especially in crash-

imminent situations.

2.2.1.2. SCHOOL ZONE AWARENESS

To enhance safety around schools, speed limits are reduced to 20 miles per hour during certain hours of

school days. Stakeholders have said that school zone speeding is an issue, especially on corridors that

have higher speed limits during non-school zone hours, such as High Street, Cleveland Avenue, and Morse

Road. In some cases, vehicle operators do not notice the signs, do not pay attention to the signs, or do not

properly interpret the signs. Speeding in school zones diminishes safety, for school children in particular.

Speed data were obtained for Cleveland Avenue in the school zone for the Linden STEM Academy, and for

High Street in the school zone for the Our Lady of Peace School. Data assessment determined that while



speed compliance rates varied along each corridor and for each direction, the overall speed compliance rate

(traveling at or less than 20 miles per hour) was only 18 percent. Table 4 shows the speed assessment

results.

Table 4: Compliance with School Zone Speeds

School & Location Date & Time Direction

Actual Speed Traveled

N 0–20 mph 20–35 mph 35+ mph

Linden STEM Academy, Cleveland Avenue, south of Manchester

May 30, 2018 7:30 a.m.–4:30 p.m.

NB 2% 83% 15% 4,478

SB 29% 61% 10% 4,130

Our Lady of Peace School, High Street, north of Dominion

May 30, 2018 7 a.m.–3:30 p.m.

NB 10% 89% 1% 5,711

SB 40% 59% 1% 3,723

Total All 18% 75% 7% 18,042


Note: N = Total number of observations. Rows may not sum to 100 percent due to rounding errors.

The CVE will be used to enable applications targeted toward improving driver awareness of speed along the

corridors shown in Figure 11 in Chapter 4 to improve compliance with school speed zones.

2.2.1.3. HIGH-PRIORITY VEHICLE DELAY

To succeed, transit and paratransit services must be reliable, with each route adhering to a schedule.

However, these vehicles may fall behind schedule for reasons such as traffic and weather. People may then

have to wait longer at bus stops or ride for a longer time. Similarly, increased travel times for freight

movement along signalized corridors because of congestion, incidents, and/or adverse weather conditions

can reduce the City’s ability to attract and keep industries that rely on efficient operations. Similarly, traffic at

signalized intersections reduces emergency vehicle ability to quickly navigate through a corridor. When an

emergency vehicle approaches an intersection with a red signal, it must slow down to ensure all conflicting

movements yield before proceeding through the intersection. The ability to arrive quickly at an emergency is

critical for police, fire, and emergency medical service (EMS) providers.

The CVE project’s implementation of FSP, Transit Signal Priority (TSP), and Emergency Vehicle Preemption

(EVP) will improve movement of these vehicles through the signalized intersections along the corridors

shown in Figure 11 in Chapter 4. This will reduce delays to transit, freight, and emergency services. The

location for these applications was chosen considering the transit, police, fire, emergency, and freight

resources that traverse these areas and intersections, along with the presence of COTA’s CMAX BRT line.

2.2.1.4. DATA FOR TRAFFIC AND TRANSIT MANAGEMENT

Managing a transportation system effectively requires collection of system operations data. This data can be

used to implement near- and long-term operations strategies such as adjusting traffic signal timing and

providing travel time data via a Data Management System (DMS). The current traffic management system



relies on loop and video detector data to detect the presence and speed of vehicles at fixed locations and to

manually assess conditions through closed-circuit video feeds. The primary drawback to this traffic

management approach is that video feeds are only available in locations where CCTV cameras are located.

Through the safety systems proposed in the CVE project, traffic managers will be able to receive low-cost

comprehensive vehicle location and motion data that can be used to generate operational metrics that can

be used to improve system operations. Transit managers will be able to assess the number of alerts or

warnings issued to a transit vehicle operator during operations with the data received through the proposed

CVE system. Since these applications focus on data and utility to specific users, there is no geographic

boundary for their implementation.

The CVE Concept of Operations (ConOps) contains a more detailed description of the project’s proposed

solutions. All systems engineering documents are on the Smart Columbus website.6

2.2.2. Multimodal Trip Planning Application/Common Payment System

The MMTPA/CPS project will help Columbus residents and visitors plan and pay for trips involving several

different modes of transportation. In this section, the current limitations are first described. The solutions

proposed by the MMTPA/CPS project are then outlined briefly.

Columbus has no system that allows travelers to seamlessly plan or pay for a trip involving multiple

transportation options. Some residents do not have bank accounts (are “unbanked”) and cannot access

alternative modes of transportation including car- and bike-sharing systems. Service gaps in the current

system summarized in the MMTPA/CPS ConOps are:

• Since apps are not interconnected, travelers must download and install multiple apps and register

multiple payment media to plan and pay for multimodal trips

• There is no comprehensive platform to plan, book, and pay for multimodal transportation

• City agencies do not control the trip data, and face obstacles when requesting trip data from mobility

providers

• Trips are not optimized for ride-sharing

• Unbanked users must rely on cash for transportation options

• There are no incentives for mobility providers to be part of a Mobility as a Service (MaaS) solution

• There are no incentives for travelers to engage in multimodal trips

Through this project, the City aims to fill the service gaps in the system, allowing travelers to create

multimodal trips and pay once using an account-based system that will be linked to different payment media

and modes of transportation. Options for multimodal trips will include walking, fixed-route bus service, car-

sharing, ride-hailing, bike-sharing, paratransit, and scooters.

The MMTPA/CPS ConOps contains a more detailed description of the project’s proposed solution. All

systems engineering documents are on the Smart Columbus website.7

The geographic scope of the MMTPA/CPS is citywide and beyond, encompassing all COTA’s service area

shown in Figure 5 below and extending into outlying communities that are further serviced by mobility

6 https://smart.columbus.gov/projects/ 7 https://smart.columbus.gov/projects/





providers. COTA’s service area includes all of Franklin County and parts of Delaware, Fairfield, Licking, and

Union counties. Outlying communities are characterized by lower-density commercial, retail, and housing

development. The Columbus region is growing in both urban and suburban areas, growth that has

contributed to increased congestion and need for better transportation alternatives to move people between

urban and suburban areas and employment centers. The Mid-Ohio Regional Planning Commission

(MORPC) has projected that by 2040 COTA’s service area will experience a 13 percent increase in

population, 15 percent increase in employment, and 13 percent increase in highway traffic congestion.

Figure 5: Central Ohio Transit Authority Service Area

Source: COTA

2.2.3. Mobility Assistance for People with Cognitive Disabilities

The MAPCD project will help Columbus residents with cognitive disabilities use public transit independently

using COTA’s fixed-route bus system. In this section, the current limitations are first described. The solutions

proposed by the MAPCD project are then outlined briefly.

People with cognitive disabilities who wish to independently use public transit services in Columbus must

either qualify for special paratransit services in accordance with federal law or be able to safely use fixed-

route bus service without assistance. The MAPCD mobile application will feature a highly accurate, turn-by-



turn navigator designed to be sufficiently intuitive such that senior adults and people with cognitive

disabilities and visual impairments can use it to travel independently.

This project’s goal is to enable people with cognitive disabilities to travel more independently on fixed-route

bus service in a safe and easy-to-use manner and to provide cost-efficient mobility options and a greater

degree of independence.

The MAPCD Trade Study contains a more detailed description of the project’s proposed solution. All


For the MAPCD project, as the deployment map in Figure 3 above indicates, the boundaries for the project

revolve around key partners in the effort: OSU and its PIECE program, and the nearby COTA and CABS

transit routes. These are shown on the map, although participants will be recruited from all areas of the city.

2.2.4. Smart Mobility Hubs

The SMH project will improve transportation options for people living in areas that need economic

improvement. In this section, the targeted areas and their associated current limitations are first discussed.

The solutions proposed by the SMH project are then outlined briefly.

Linden is a high-opportunity Columbus neighborhood in need of economic improvement. Linden residents

face numerous socio-economic challenges, including low household income, lack of major employers

nearby, and high infant mortality rates. These problems are compounded by the lack of access to

transportation options. Easton is a high-traffic retail destination and job center in the northeast part of

Columbus. Although Easton is a major employment center, the jobs in this community have a high turnover

rate . Research has shown that a major contributor to this type of job instability is the lack of reliable

transportation, including FMLM challenges related to safety and mobility.

The current COTA system satisfies some needs of travelers in these areas. For instance, COTA provides

transit routes between fixed bus stops and several park-and-ride locations. However, COTA cannot currently

coordinate multimodal trips or help people plan trips outside of an acceptable distance from COTA’s CMAX

BRT corridor. Service gaps in the current system include:

• Lack of physical facilities offering trip-planning, multimodal transit options, and other amenities at

centralized locations

• Limited FMLM transportation options; these limitations make it difficult for transit-dependent residents

to access basic services such as healthcare, grocery stores, and banking

• Inadequate optimization of ride-sharing

• Exclusion of unbanked users and users without smartphones from travel options

• Lack of adequate safety features at transit facilities

The purpose of the SMH project is to deploy transportation facilities that provide travelers with consolidated

transportation amenities such as interactive kiosks, provide access to comprehensive trip-planning tools (via

MMTPA/CPS), and fill in the gaps in the current service listed above. These services will be particularly

useful in helping people complete FMLM and multimodal trip options.





The SMH ConOps contains a more detailed description of the project’s proposed solution. All systems

engineering documents are on the Smart Columbus website.9

The location of COTA stops along the Cleveland Avenue corridor that coincide with CMAX BRT service was

a key factor in selecting the SMH sites. These locations provide Linden-area residents better access to jobs

and services in the Easton and Downtown Columbus areas. Considering user feedback collected through

focus groups and surveys, the following six initial SMH deployment locations were selected (Figure 6):

• Columbus State Community College

• Linden Transit Center

• St. Stephens Community House

• Metro Library – Linden Branch

• Northern Lights Park and Ride

• Easton Transit Center

Figure 6: Proposed Smart Mobility Hub Locations

Source: Google Earth Pro, City of Columbus





2.2.5. Prenatal Trip Assistance

The PTA project will help people who use nonemergency medical transportation (NEMT) provided through

Medicaid benefits get to their prenatal appointments more easily. This section explains the current

challenges and outlines the PTA project’s proposed solutions.

The infant mortality rate conveys the number of children who die before their first birthday out of 1,000 live

births. Franklin County, Ohio, home of the state’s capital of Columbus, has one of the highest rates of infant

mortality in the United States, at 8.2 deaths per 1,000 live births. CelebrateOne is a division of the Mayor’s

Office that works to reduce infant mortality in the City of Columbus. CelebrateOne found that most deaths in

the county were occurring in eight “hot spots.” All the hot spots were impoverished neighborhoods. More

than half of the infant deaths were related to prematurity, with birth defects and sleep-related deaths being

the other most frequently identified causes.

Receipt of early and adequate prenatal care is essential for preventing the two main causes of infant

mortality, preterm birth (< 37 weeks of gestation), and congenital anomalies. Safe and reliable transportation

to prenatal care appointments remains a constant challenge for women living in poverty in our community.

Bus passes are often outside women’s budgets, and bus stops are not always near women’s homes and/or

prenatal care provider facilities. Medical care for most women living in poverty in Greater Columbus is paid

for by a Medicaid Managed Care Organization (MCO). While these plans do provide transportation to and

from medical appointments during pregnancy and during the 8‐week postpartum period, services may

present challenges such as lack of reasonable convenience. Therefore, some women elect to pursue other

transportation options. Further, while all MCOs serving the local community provide nonemergency medical

transportation (NEMT) in some form, many do not cover other important health‐related trips such as trips to

the pharmacy, food bank, or grocery store.

Even though most impoverished women have a mobile phone—many of which are smartphones (albeit with

limited data plans)—the transportation providers (predominantly taxis) currently used by the MCOs are low-

tech, with no mobile alerts or two‐way communication capabilities.

Gaps in the current system include:

• NEMT trips can only be scheduled through a call center.

• Access to on-demand transportation is limited.

• City agencies do not control the trip data, and face obstacles when requesting trip data from NEMT

mobility providers or MCOs.

• Trips are not being optimized for real-time changes.

• There is a lack of communication between the mobility provider, prenatal traveler, and medical office.

• Uncertainty in time of return trip makes providing service difficult and reduces prenatal traveler’s

acceptance of the system.

• Medical offices do not know whether a prenatal traveler simply did not show up for the ride or if they

actively canceled the trip; in the latter case, the appointment may need to be rescheduled.

• The prenatal traveler cannot receive information about the driver.

• Real-time information on driver location and arrival time is not available.

• Members do not have a reliable method to provide complaints to MCOs.

The PTA project will enhance mobility and increase opportunity and customer service for prenatal travelers

who use NEMT provided through Medicaid benefits. PTA will provide sources of high-quality data for the



Ohio Department of Medicaid (ODM), MCOs, and others involved in tracking the prenatal care of Columbus

Medicaid recipients. The improvements provided through this project will fill the gaps listed above.

The PTA ConOps contains a more detailed description of the project’s proposed solution. All systems


PTA will be deployed and participants will be recruited throughout Franklin County, Ohio (Figure 7).

Figure 7: Major Cities and Freeways Franklin County, Ohio






2.2.6. Event Parking Management

The EPM project will help people find parking more easily when they arrive at their destinations in

Downtown Columbus and Short North areas. This section explains the current challenges and outlines the

EPM project’s proposed solutions.

The City must balance parking among various groups so that residents, visitors, business owners, and

workers can park in harmony with each other. The City’s existing parking regulations aim to create a

comprehensive approach to parking management, supply, and operation. The existing parking infrastructure

includes loading zones, single space meters, garages, surface lots, taxi-only parking, valet, no-parking

zones, permit parking, and resident-only parking. The City has dedicated teams responsible for many

relevant factors, including parking issues, studies, policy, permits, loading zones, parking meters, and

parking enforcement. However, the City also recognizes that public on-street and private parking is limited in

many commercial, residential, historic, and mixed-use neighborhoods. During large events, weekday

commutes, and on weekends, parking demand usually outweighs the capacity nearest the destination

location, leading to longer drive times and increased traffic congestion as drivers attempt to find parking.

Under the current system, Columbus parking is managed by a conglomeration of public and private entities.

Online sites provide private parking and payment options, but each only encompasses part of the City’s

available parking. Travelers must research all parking websites and other resources to gain a complete view

of the full range of parking options, which can lead to confusion and frustration. More traffic delays occur

because of the extended search for parking, fuel consumption increases, and air quality declines.

Specifically, in the Short North area, the High Street corridor grew faster than parking capacity and

transportation options. Negative parking experiences could reduce local tourism and business patronage.

The Columbus Short North Parking Study identified the need for more information on parking availability.

This need is also reaffirmed in visitor satisfaction surveys conducted by Experience Columbus.

The proposed EPM system will allow users to identify currently projected parking availability near their

destination and help reduce the additional driving required now to finding parking. Benefits of an EPM

system include reduced emissions, increased knowledge of available parking in the City, and reduced

congestion around events.

The EPM ConOps contains a more detailed description of the project’s proposed solution. All systems


The EPM project focuses on the Downtown and Short North areas for parking garage, surface lot, parking

meter, and loading zone information. The parking meter and loading zone information will be expanded

citywide, but the ConOps will focus on the Downtown and Short North areas. The Downtown boundaries are

consistent with those of the central business district, which is bounded by SR-315 on the west, I-70 on the

south, I-71 on the east, and I-670 on the north. In addition, the Short North area includes the High Street

corridor from I-670 on the south, Dennison Avenue on the west, Third Street on the east, and Fifth Avenue

on the north.

Figure 8 presents the geographic boundaries for the EPM project.





Figure 8: Downtown Columbus and the Short North Area


2.2.7. Connected Electric Autonomous Vehicles

In addition to examining and documenting societal challenges to AV adoption, and more importantly, the

CEAV project seeks to provide a concrete positive effect on the community. Because the City has been

engaged with the Linden neighborhood through other projects, the lack of FMLM solutions has been

documented, particularly those FMLM solutions that would connect transit to other community resources.

The City and its local communities sought better (more convenient and reliable) connection between the

community and services through first-mile/last-mile/only-mile connections through transit. In addition, with

COTA as a key partner, project partners sought to grow COTA ridership by encouraging a modal shift to

public transit by increasing the attractiveness and availability of end to end transit options.



The Linden CEAV route was selected to best solve these challenges. This route has been developed with

stakeholder groups and created with the following localized goals:

• Connecting the community to jobs and services including:

Community centers

Opportunity centers

Food sources

Support services

SMHs

• Improving safety and mobility of travelers by mitigating first-mile/last-mile/only-mile challenges

• Encouraging transit use by expanding locations served and implementing efficient schedules and

integrated solutions

The CEAV Operational Concept contains a more detailed description of the project’s proposed solution. All


The route that will be deployed in Linden will extend between St. Stephens Community House and the

Linden Transit Center, both of which are designated as SMHs within the Smart Columbus project portfolio.

These hubs will provide access to mobility options at chosen areas of community focus, such as transit

stops, libraries, and community centers, to improve mobility for the surrounding area. The goal of this route

is to connect the community center with the COTA’s CMAX BRT line and neighboring community.

Figure 9 presents a high-level view of the route that will be deployed in Linden.





Figure 9: Connected Electric Autonmous Vehicle Route from Linden Transit Center

to St. Stephens Community House

Source: Google Earth, City of Columbus


Program Deployment Site Map and Installation Schedule

Three Smart Columbus projects will involve installing infrastructure: CVE, SMH, and CEAV. Figure 10

shows the infrastructure components that will be installed for each project. The components and

corresponding tables are outlined below.

3.1. CONNECTED VEHICLE ENVIRONMENT

Infrastructure components that will be installed as part of the CVE project include RSUs, OBUs, Ethernet

switches, Connected Vehicle Co-processor (CVCP) cards, fiber optic cables, termination panels, fiber

optical transceivers, bracket arms, signal controllers, and dual panel assembly. Figure 10 shows the

locations where CVE components will be installed.

Table 5 includes the below identified RSU installation details:

• Month and intersection planned for the installation

• Intersections where RSUs will be installed

• Key RSU components

• Installation dates

• Manufacturers

Table 6 includes the following OBU installation details:

• Vehicle type

• Partners

• Quantity

• Components

• Schedule

• Location

Refer to Section 4.1 and Section 5.1 for a detailed list of infrastructure components and installation

schedule information for the CVE project.

3.2. SMART MOBILITY HUBS

Infrastructure components that will be installed as part of the SMH project include interactive kiosks, SMH

signs, and pavement markings. Figure 10 shows the SMH components that will be installed at each of the

SMH locations. Table 7 also depicts the infrastructure to be installed at each of the SMH locations, along

with the schedule of installation for each component.


schedule information for the SMH project.

Chapter 3. Program Deployment Site Map and Installation Schedule


3.3. CONNECTED ELECTRIC AUTONOMOUS VEHICLES

Infrastructure components that will be installed as part of the CEAV project include signage, concrete station

pads, and electrical outlets for vehicle charging. Figure 10 shows the CEAV components that will be

installed at each of the CEAV stations. Table 8 also depicts the infrastructure installed at each CEAV

location, along with the schedule of installation for each component.


schedule information for the CEAV project.



Figure 10: Smart Columbus Program Key Infrastructure Installation Locations





Table 5: Connected Vehicle Environment Roadside Unit and Related Key Infrastructure Components

Intersection ID# Primary Street Secondary street

Key Infrastructure Elements (P = Proposed) Schedule

RSU Manufacturer Standard CVE

Equipment* Signal Controller Bracket Arm

Layer 3 Ethernet Switch

Dual Panel Assembly

Key Infrastructure

Elements

Roadside Units

4017 High Street Fifth Avenue P

Sept 9, 2019 - Jan 31, 2020

Feb 26, 2020 - Mar 19, 2020

Kapsch

4018 High Street King Avenue/Seventh Avenue P Kapsch

4103 High Street Ninth Avenue P Danlaw

4019 High Street 10th Avenue P Danlaw

4107 High Street 11th Avenue P Kapsch

4020 High Street Chittenden Avenue P Danlaw





4024 High Street 18th Avenue P Siemens

4025 High Street Woodruff Avenue P Kapsch

4026 High Street Lane Avenue P Kapsch

4027 High Street Northwood Avenue P P Kapsch

4028 High Street Patterson Avenue P Kapsch

4029 High Street Hudson Street P P Siemens

4007 High Street Dodridge Street P P Danlaw

4006 High Street Arcadia Avenue P P Kapsch

4009 High Street Olentangy Street P Danlaw

4032 High Street Kelso Road P Danlaw

4033 High Street Weber Road P Danlaw

4034 High Street Pacemont Road P Danlaw

4035 High Street Como Avenue P Kapsch

4036 High Street North Broadway P Kapsch

4037 High Street Oakland Park P Danlaw

4038 High Street Torrence Road P Danlaw

4040 High Street Acton Road P Kapsch

4042 High Street Cooke Road P P Kapsch

4043 High Street Henderson Road P P Kapsch

4044 High Street Dominion Boulevard P P Kapsch

4045 High Street Weisheimer Road P P Kapsch

4047 High Street Morse Road P P Siemens

3405 Morse Road Indianola Avenue P P Danlaw








Dual Panel Assembly

Key Infrastructure

Elements

Roadside Units

3407 Morse Road Sinclair Road/I-71 SB P P

Sept 9, 2019 - Dec 19, 2019

Feb 15, 2020 to Feb 25, 2020

Danlaw

3408 Morse Road I-71 NB P P Danlaw

3446 Morse Road Evanswood Drive P P Danlaw

3409 Morse Road Sandy Lane Road P P Kapsch

3410 Morse Road Maize Road P P Danlaw

3411 Morse Road McFadden Road P P Danlaw

3412 Morse Road Karl Road P P Danlaw

3413 Morse Road Northland Ridge Boulevard P P Danlaw

3414 Morse Road Tamarack Boulevard P P Danlaw

3415 Morse Road Heaton Road P P Danlaw

3416 Morse Road Walford Street/Northtowne Boulevard P P Danlaw

3417 Morse Road Malin Street P P Kapsch

3440 Morse Road Cleveland Avenue P P Kapsch

3290 Morse Road Chesford Road P P Danlaw

3291 Morse Road Westerville Road P P Danlaw

3209 Morse Road Sunbury Road P P P Siemens

3237 Morse Road Morse Crossing P P P Kapsch

3231 Morse Road Easton Loop P P P Siemens

3228 Morse Road Stelzer Road P P P Kapsch

3161 Morse Road I-270 SB P P Siemens

3162 Morse Road I-270 NB P P Kapsch

3163 Morse Road Appian Way P P P Siemens

3093 Morse Road L Brands Driveway P Kapsch

3092 Morse Road Stygler Road P P P Kapsch

3010 Cleveland Avenue Second Avenue P

Sept 9, 2019 - Jan 10, 2020

Mar 20, 2020 - Apr 3, 2020

Kapsch

3012 Cleveland Avenue Fifth Avenue P Danlaw

3013 Cleveland Avenue 11th Avenue P Danlaw

3014 Cleveland Avenue Windsor Avenue P P Kapsch

3015 Cleveland Avenue 17th Avenue P Kapsch

3017 Cleveland Avenue 20th Avenue P Kapsch

3018 Cleveland Avenue 24th Avenue P P Kapsch

3019 Cleveland Avenue Duxberry Avenue P P Kapsch

3020 Cleveland Avenue Hudson Street P P Kapsch

3021 Cleveland Avenue Myrtle Avenue P P Kapsch

3022 Cleveland Avenue Genessee Avenue P P Siemens








Dual Panel Assembly

Key Infrastructure

Elements

Roadside Units

3023 Cleveland Avenue Aberdeen Avenue P P Kapsch

3024 Cleveland Avenue Weber Road P P Kapsch

3154 Cleveland Avenue Oakland Park Avenue P Kapsch

SIG4060 Cleveland Avenue Huy Road P Kapsch

SIG4065 Cleveland Avenue Innis Road P Kapsch

SIG4930 Cleveland Avenue Northern Lights P Kapsch

SIG4070 Cleveland Avenue Elmore Avenue P P Kapsch

SIG4055 Cleveland Avenue Cooke Road P Kapsch

3159 Cleveland Avenue Ferris Road P Danlaw

SR317_ACD Alum Creek Drive London Groveport Road P

Mar 2020 – May 2020

Apr 6, 2020 - Apr 10, 2020

Kapsch

SIG4770 Alum Creek Drive Spiegel Drive P P P Kapsch

SIG4850 Alum Creek Drive Rohr Road P P P Kapsch

SIG4950 Alum Creek Drive Global Ct. P P Kapsch

SIG4775 Alum Creek Drive Toy Road P P Kapsch

GRPT_ACD Alum Creek Drive Groveport Road P P Kapsch

I270EB_ACD Alum Creek Drive I-270 EB P Kapsch

I270WB_ACD Alum Creek Drive I-270 WB P Kapsch

Node #270032.3 I-270 Morse Road P P

Aug 23, 2019 - Nov 15, 2019

No RSUs

N/A

Node #270027.7 I-270 Cleveland Avenue P P N/A

Node #071116.2 I-71 Morse Road P P N/A

Node #071110.9 I-71 Eleventh Avenue P P N/A

Node #315004.4 SR-315 Lane Avenue P P N/A

Node #315006.2 SR-315 North Broadway P P N/A

Note: P = Proposed. *Standard CVE equipment includes Dedicated Short-Range Communication devices, Layer 2 Ethernet switches, CV application modules, interconnect cable, termination panels, and optical transceivers.




Table 6: Connected Vehicle Environment Onboard Unit Infrastructure Components and Installation Locations

Vehicle Type Partners Quantity

OBU Components (P = Proposed) Schedule

OBU Installation Locations Under-Dash Module/OBU

Digital Antenna

Power Control Cables

4A Fuse Reset Switch

External Accessories

Cables

Heads-up

Display

Component Installation in Vehicles

Light-Duty Vehicles

Public Service City Fleet Vehicles

198 P P P P P P P Feb 3, 2020 – Mar 24, 2020 1850 East 25th Avenue, Columbus 43219

Private Vehicles 1019 P P P P P P P Feb 10, 2020 – Oct 6, 2020

1248 E Dublin Rd, Columbus, OH 43229 1101 E Hudson St, Columbus, OH 43211 1392 Dolle Ave, Columbus, OH 43211 930 Kinnear Road, Columbus, OH 43212 550 E Spring St, Columbus, OH 43215

COTA Supervisor Vehicles 25 P P P P P P P May 22, 2020 – May 28, 2020 1600 McKinley Avenue, Columbus 43222

Heavy-Duty Vehicles

County Engineer 6 P P P P P P P Feb 24, 2020 – Feb 25, 2020 TBD

Private Freight 14 P P P P P P Feb 26, 2020 – Mar 3, 2020 TBD

Emergency Vehicles

Police Cruiser Vehicles 80 P P P P P P Apr 15, 2020 – May 11, 2020 4211 Groves Road, Columbus 43232

Fire Truck/ EMS 30 P P P P P P P Mar 4, 2020 – Apr 14, 2020 4211 Groves Road, Columbus 43232

Transit Vehicles COTA Transit Bus 350 Feb 3, 2020 – Jun 3, 2020 1600 McKinley Avenue, Columbus 43222

COTA Paratransit Bus 80 May 29, 2020 – Sept 23, 2020 1600 McKinley Avenue, Columbus 43222

Total 1802


Table 7: Infrastructure Components at Smart Mobility Hub Locations

SMH Location

Primary Street

Secondary street

Infrastructure to be Installed (P = Proposed) Schedule

IK Bike-Share Dock

Dockless Parking Zone

Smart Mobility Hub Sign

Car-Share Sign

Dockless Parking Sign

Ride-Hailing Sign

Pavement Makings

Concrete Installation

Signs Pavement Markings

CoGo Infrastructure

Install Kiosk Concrete Installation

Columbus State Community College

Cleveland Avenue

Mt Vernon Avenue

P P P P P P P Jan 1, 2020 – Jan 31, 2020

Jan 1, 2020 – Jan 31, 2020

Feb 6, 2020 – Feb 7, 2020

Jan 16, 2020 – Jan 31, 2020

Linden Transit Center*

Cleveland Avenue

11th Avenue

P P P P P P P P Oct 24, 2019 – Nov 27, 2019

Oct 18, 2019 – Oct 24, 2019

Feb 6, 2020 – Feb 7, 2020

Jan 6, 2020 – Jan 15, 2020

Oct 15, 2019 – Nov 4, 2019

Metro Library – Linden Branch

Cleveland Avenue

Kohr Place P P P P P P P P Oct 24, 2019 – Nov 27, 2019

Oct 16, 2019 – Oct 22, 2019

Feb 6, 2020 – Feb 7, 2020

Jan 16, 2020 – Jan 31, 2020

Northern Lights Park and Ride

Cleveland Avenue

Northern Lights Service Driveway

P P P P P P P P Oct 24, 2019 – Nov 27, 2019

Oct 23, 2019 – Oct 24, 2019

Jan 16, 2020 – Jan 31, 2020

Oct 2, 2019 – Oct 22, 2019



SMH Location

Primary Street

Secondary street

Infrastructure to be Installed (P = Proposed) Schedule

IK Bike-Share Dock

Dockless Parking Zone

Smart Mobility Hub Sign

Car-Share Sign

Dockless Parking Sign

Ride-Hailing Sign

Pavement Makings


Signs Pavement Markings

CoGo Infrastructure

Install Kiosk Concrete Installation

St. Stephens Community House*

17th Avenue

St. Stephens Community House

P P P P P P P P Oct 24, 2019 – Nov 27, 2019

Oct 16, 2019 – Oct 22, 2019

Feb 6, 2020 – Feb 7, 2020 Jan 6, 2020 –

Jan 15, 2020

Easton Transit Center

Stelzer Road Transit Drive

P P P P Oct 24, 2019 – Nov 27, 2019

Feb 6, 2020 – Feb 7, 2020

Jan 6, 2020 – Jan 15, 2020

Note: SMH locations with * have AV shuttle service.


Table 8: Infrastructure Components at Connected Vehicle Autonomous Vehicle Stations

CEAV Station Location Primary Street Secondary street


CEAV Storage Location

Charging Outlets

Signage Vehicle Assembly

Vehicle Wrapping

Signage Installation


Testing Route Setup

Full Route Setup

Linden Transit Center Cleveland Avenue 11th Avenue P P Dec 11, 2019 – Dec 13, 2019

Dec 16, 2019 - Dec 19, 2019

Jan 24, 2020

Jan 17, 2020

Dec 16, 2019 Jan 6, 2020 – Jan 17, 2020

Rosewind Resident Council Brooks Avenue Chittenden Avenue P P Dec 11, 2019 – Dec 13, 2019

Dec 16, 2019 - Dec 19, 2019

Jan 24, 2020

Jan 17, 2020

Dec 16, 2019 Jan 6, 2020 – Jan 17, 2020

Douglas Community Recreation Center

Windsor Avenue Cleophus Kee Boulevard P P Dec 11, 2019 – Dec 13, 2019

Dec 16, 2019 - Dec 19, 2019

Jan 24, 2020

Jan 17, 2020

Dec 16, 2019 Jan 6, 2020 – Jan 17, 2020

St. Stephens Community House 17th Avenue Billiter Boulevard P P P P Dec 11, 2019 – Dec 13, 2019

Dec 16, 2019 - Dec 19, 2019

Jan 24, 2020

Jan 17, 2020

Dec 16, 2019 Jan 6, 2020 – Jan 17, 2020



Smart Columbus Infrastructure by Project

As stated in Chapter 3, three Smart Columbus projects will involve installing infrastructure: CVE, SMH, and

CEAV. While Chapter 3 provided the associated map and tables, this chapter describes the type of

infrastructure that will be installed in more detail, provides an overview of where the items will be installed,

and summarizes the parties responsible for their installation.


Deploying the CVE requires installing both roadside and in-vehicle devices, along with software applications

that process and analyze messages to develop the alerts and warnings for drivers. This equipment will be

installed at both CVE intersections and other strategic locations called “communication node sites” or just

“nodes.”

Table 5 in Chapter 3 lists the roadside components that will be installed at each intersection or node, along

with manufacturer and schedule information. The roadside components to be installed are:

• Dedicated Short-Range Communication (DSRC) RSU Units: RSUs from three different

manufacturers will be used at different CVE intersections. All RSUs will have a Power-over-Ethernet

(PoE) injector for power supply, antennas for coordinating locations using a global positioning system

(GPS), and mounting brackets.

• CVCPs: Each intersection will be equipped with an Econolite CVCP card, which will be installed in

the Cobalt-C signal controller expansion slot.

• Signal Controllers: Cobalt-C signal controllers will be installed at CVE intersections. Some of the

intersections may already have Cobalt-C controllers. Intersections with proposed signal controllers

are listed in Table 5 (See Chapter 3).

• Dual Panel Assemblies: Each node will have an equipment cabinet and a fiber termination cabinet.

The cabinets will be connected through a dual panel assembly installed underground.

• Interconnect Cables: Interconnect cables will be used at all CVE intersections to connect the traffic

signal cabinets between the intersections and to connect RSUs and wireless radios to the signal

cabinets. The interconnect cables will be 144-strand fiber optic cable, 24-strand fiber optic cable, and

Cat 5E cable.

• Ethernet Switches: As part of the CVE communication network, CommNet layer 2 Ethernet

switches will be installed at CVE intersections, CISCO IE 4010 Layer 3 switches will be installed at

nodes, and CISCO 3850 Ethernet switches and Juniper firewalls will be installed at the Traffic

Management Center (TMC).

• Power: All CVE intersections with RSUs will support a PoE interface. The PoE injector will be

installed in the controller cabinet at locations with access to power. Specific details will be coordinated

with the parties responsible for installation (see Chapter 5).

Chapter 4. Smart Columbus Infrastructure by Project


• Mounting Hardware: To mount RSUs vertically, Pelco Astro-Bracs and gusseted tubes or Kapsch

swivel backplate will be used. The mounting configuration will vary if an RSU is installed on a bracket

arm, mast arm, or span wire).

Table 6 (Chapter 3) lists OBU components for different types of vehicles and gives the installation schedule.

OBU elements will include:

• Under-Dash Module: The under-dash module in vehicles is called an OBU.

• Digital Antenna(s): A digital antenna includes a satellite receiver module, a GNSS receiver module,

and a dual-channel DSRC transceiver module all in a single, weatherproof externally mounted

magnetic unit.

• Power Control Cables: The OBU will be directly connected to the vehicle battery using the supplied

four-wire wiring harness. Power control cables will be used to connected to the vehicle battery, with a

second connection to the accessory power. Other connections that will using power cables include

high-definition multimedia interfaces (HDMI), touch-screen interface dual universal serial buses

(USBs), USB mini-Bs, and antenna connectors.

• Human-Machine Interface (HMI): A 4-inch Heads-Up Display (HUD) was selected for the HMI to be

used. HUDs will only be installed in private LDVs for the CVE demonstration.

• Mounting Hardware: OBUs will be installed on several types of vehicles, including LDVs and heavy-

duty vehicles (HDVs). These include private vehicles, COTA transit buses, and fleet vehicles from the

City police, fire, and emergency entities. OBUs will have four mounting tabs for all vehicle types and

will usually be mounted under the dash using nylon wire-ties. Mounting locations may differ according

to the type of the vehicle. OBUs will be mounted such that the vehicles could be returned to their

original pre-installation condition. Specific installation requirements for these individual vehicle types

will be determined after OBU delivery.

An important aspect of the CVE deployment is the software (the CV applications) that will reside on both the

RSUs and the OBUs. To address the issues identified in Chapter 1, these applications will use the

messages exchanged via DSRC to provide alerts and warnings to the drivers. Vehicle type is a variable that

will also be considered as the City plans for installation. Vehicle type will dictate the number and placement

of antennas and the need for an HMI (and, if needed, the type of HMI that will be installed).

For reference, and to the extent that the applications and vehicle type influence the configuration of the

roadside and vehicle equipment, Table 9 contains a matrix of the CV applications and vehicle types planned

for deployment. Applications that reside on the RSU are highlighted in gray, while the non-highlighted cells

are V2V applications or applications designed for back-office use.

Table 9: Connected Vehicle Applications and Vehicle Classes for Smart Columbus

Connected Vehicle Environment

Class Application Name

Vehicle OBU Class

LD

Vs

Em

erg

ency

Vehic

le

HD

Vs

Tra

nsit

Vehic

le*

V2V Safety Emergency Electronic Brake Light Warning ✓ - - ✓



Class Application Name

Vehicle OBU Class

LD

Vs

Em

erg

ency

Vehic

le

HD

Vs

Tra

nsit

Vehic

le*

Forward Collision Warning ✓ – – ✓

Intersection Movement Assist ✓ – – ✓

Lane Change Warning/Blind Spot Warning ✓ – – ✓

V2I Mobility Transit Signal Priority* – – – ✓

Freight Signal Priority* – – ✓ –

Emergency Vehicle Preemption* – ✓ –

Vehicle Data for Traffic Operations ✓ ✓ ✓ ✓

Transit Vehicle Interaction Event Recording – – – ✓

V2I Safety Red Light Violation Warning (RLVW) ✓ – – ✓

Reduced Speed School Zone Warning (RSSZW) ✓ – – ✓


Note 1: *Part of the Multimodal Intelligent Traffic Signal System (MMITSS) signal priority bundle. MMITSS (or similar) require

applications deployed on both the RSU and the OBU.

Note 2: Applications that reside on the RSU are highlighted in gray, while the non-highlighted cells are V2V applications or applications

designed for back-office use.

4.1.1. Connected Vehicle Environment Infrastructure

4.1.1.1. ROADSIDE EQUIPMENT

The City will procure 100 DSRC RSUs to be deployed at the traffic-signal-equipped intersection locations

identified in Chapter 2. Presently, 95 DSRC RSUs are expected to be procured for deployment and five for

spares. The roadside equipment integrator will supply all necessary radios, cables, power supplies,

mounting hardware, electrical connectors, and any other equipment necessary to achieve the full

functionality and connectivity expected from the RSU according to the contract with the City.

The foundation for the CVE project is the Columbus Traffic Signal System (CTSS), which is a high-speed

network backbone. When complete, the CTSS will interconnect the region’s 1,250 traffic signals and provide

uniform signal coordination capability throughout the system. CTSS Phase E, which will connect all CVE

corridors (detailed in the CVE ConOps) except for Alum Creek Drive, was completed in December 2019.

The CTSS expansion to connect Alum Creek Drive in the next CTSS phase is expected to be complete in

May 2020 before the CVE project goes live.

4.1.1.2. ONBOARD UNIT EQUIPMENT

The City will install OBU equipment on different vehicle types and the characteristics for each configuration

of the OBU equipment installation will vary depending on the vehicle type. The OBU equipment includes



under-dash module, digital antenna, power control cables, reset switch and other external accessory cables.

The main component that will vary across vehicle types with OBU installation is the HUD. It is the 4-inch

display which provides HMI to the drivers that will only be installed in private LDVs for the CVE

demonstration. Table 11 provides more information of the vehicle types, and the characteristics of each

configuration.

4.1.2. Connected Vehicle Environment Installation Locations

4.1.2.1. ROADSIDE UNITS

All signalized intersections along the CVE network will be equipped with RSUs.

The CVE network will also include dedicated fiber optic cable pairs connected to dedicated local (in-cabinet)

Layer 2 switches and signal controllers, which will be interconnected in aggregate to dedicated Layer 3

switches (located in separate communications cabinets), and which will ultimately terminate at the City of

Columbus TMC. The electrical contractor responsible for installing the RSU will have all the proposed CVE

infrastructure components and installation location information from the CVE plan sheets that will be in the

procurement and contract documents. The CVE network will parallel the existing networks for CTSS and

Columbus MetroNet (the City’s business network) but will be physically isolated from them.

Table 10 lists all signalized intersections along the CVE network that will be equipped with RSUs, as well as

the intersection identifiers that will be referenced in the installation plans used by the RSU integrator and by

the City for tracking and maintaining the RSU and associated equipment.

Table 10: Connected Vehicle Application by Intersection

Intersection ID Primary Road Cross-Street CV Application

High Street Corridor (south to north)

4017 High Street Fifth Avenue RLVW

EVP

4018 High Street King Avenue/Seventh Avenue RLVW

EVP

4103 High Street Ninth Avenue RLVW

EVP

4019 High Street 10th Avenue RLVW

EVP


EVP

4020 High Street Chittenden Avenue RLVW

EVP


EVP


EVP





EVP


EVP


EVP

4025 High Street Woodruff Avenue RLVW

EVP

4026 High Street Lane Avenue RLVW

EVP

4027 High Street Northwood Avenue RLVW

EVP

4028 High Street Patterson Avenue RLVW

EVP

4029 High Street Hudson Street RLVW

EVP

4007 High Street Dodridge Street RLVW

EVP

4006 High Street Arcadia Avenue RLVW

EVP

4009 High Street Olentangy Street RLVW

EVP

4032 High Street Kelso Road RLVW

EVP

4033 High Street Weber Road RLVW

EVP

4034 High Street Pacemont Road RLVW

EVP

4035 High Street Como Avenue

RLVW

RSSZW

EVP

4036 High Street North Broadway

RLVW

RSSZW

EVP

4037 High Street Oakland Park RLVW

EVP




4038 High Street Torrence Road RLVW

EVP

4040 High Street Acton Road RLVW

EVP

4042 High Street Cooke Road RLVW

EVP

4043 High Street Henderson Road RLVW

EVP

4044 High Street Dominion Boulevard

RLVW

RSSZW

EVP

4045 High Street Weisheimer Road

RLVW

RSSZW

EVP

4047 High Street Morse Road RLVW

EVP

Morse Road Corridor (west to east)

3405 Morse Road Indianola Avenue RLVW

EVP

3407 Morse Road Sinclair Road/I-71 SB RLVW

EVP

3408 Morse Road I-71 NB RLVW

EVP

3446 Morse Road Evanswood Drive RLVW

EVP

3409 Morse Road Sandy Lane Road RLVW

EVP

3410 Morse Road Maize Road RLVW

EVP

3411 Morse Road McFadden Road RLVW

EVP

3412 Morse Road Karl Road RLVW

EVP

3413 Morse Road Northland Ridge Boulevard RLVW

EVP

3414 Morse Road Tamarack Boulevard RLVW

EVP




3415 Morse Road Heaton Road RLVW

EVP

3416 Morse Road Walford Street/Northtowne Boulevard RLVW

EVP

3417 Morse Road Malin Street RLVW

EVP

3440 Morse Road Cleveland Avenue RLVW

EVP

3290 Morse Road Chesford Road RLVW

EVP

3291 Morse Road Westerville Road RLVW

EVP

3209 Morse Road Sunbury Road RLVW

EVP

3237 Morse Road Morse Crossing RLVW

EVP

3231 Morse Road Easton Loop RLVW

EVP

3228 Morse Road Stelzer Road RLVW

EVP

3161 Morse Road I-270 SB

RLVW

EVP

FSP

3162 Morse Road I-270 NB

RLVW

EVP

FSP

3163 Morse Road Appian Way

RLVW

EVP

FSP

3093 Morse Road L Brands Driveway

RLVW

EVP

FSP

3092 Morse Road Stygler Road

RLVW

EVP

FSP

Cleveland Avenue (south to north)




3010 Cleveland Avenue Second Avenue

RLVW

EVP

TSP

3012 Cleveland Avenue Fifth Avenue

RLVW

EVP

TSP

3013 Cleveland Avenue 11th Avenue

RLVW

EVP

TSP

3014 Cleveland Avenue Windsor Avenue

RLVW

EVP

TSP


RLVW

EVP

TSP


RLVW

EVP

TSP


RLVW

EVP

TSP

3019 Cleveland Avenue Duxberry Avenue

RLVW

EVP

TSP

3020 Cleveland Avenue Hudson Street

RLVW

EVP

TSP

3021 Cleveland Avenue Myrtle Avenue

RLVW

EVP

TSP

3022 Cleveland Avenue Genessee Avenue

RLVW

EVP

TSP

3023 Cleveland Avenue Aberdeen Avenue

RLVW

RSSZW

EVP

TSP




3024 Cleveland Avenue Westerville Road

RLVW

RSSZW

EVP

TSP

3154 Cleveland Avenue Oakland Park Avenue

RLVW

EVP

TSP

SIG4060 Cleveland Avenue Huy Road

RLVW

EVP

TSP

SIG4065 Cleveland Avenue Innis Road

RLVW

EVP

TSP

SIG4930 Cleveland Avenue Northern Lights

RLVW

EVP

TSP

SIG4070 Cleveland Avenue Elmore Avenue

RLVW

EVP

TSP

SIG4055 Cleveland Avenue Cooke Road

RLVW

EVP

TSP

3159 Cleveland Avenue Ferris Road

RLVW

EVP

TSP

Alum Creek Drive (south to north)

SR317_ACD Alum Creek Drive London Groveport Road RLVW

FSP

GRPT_ACD Alum Creek Drive Groveport Road RLVW

FSP

SIG4950 Alum Creek Drive Global Court RLVW

FSP

SIG4775 Alum Creek Drive Toy Road RLVW

FSP

SIG4850 Alum Creek Drive Rohr Road RLVW

FSP

SIG4770 Alum Creek Drive Spiegel Drive RLVW

FSP




I270EB_ACD Alum Creek Drive I-270 EB RLVW

FSP

I270WB_ACD Alum Creek Drive I-270 WB RLVW

FSP


Note: EVP = Emergency Vehicle Preemption; FSP = Freight Signal Priority; RLVW = Red Light Violation Warning; RSSZW =

Reduced Speed School Zone Warning; TSP = Transit Signal Priority.

4.1.2.2. ONBOARD UNITS

For various types of vehicles, Table 11 outlines the in-vehicle equipment proposed, listing also the partner or

source for the equipment and how many vehicles will receive the equipment. These combinations are

important because they dictate the applications deployed, HMI type (if any), data logging and data transfer

requirements, and any special provisions for coordinating the installation. The quantities shown represent

the Smart Columbus goal. The minimum number of installations planned is 1,500, and the maximum is

1,802; the difference between the minimum and the maximum mostly reflects uncertainty in the number of

private vehicles that will receive CVE equipment.

Appendix B describes the vehicle types that will receive CVE equipment and lists the quantities each type

will receive, organized by organization (City, COTA, or Franklin County). The number of personal vehicles

that will receive equipment depends on the outcome of recruiting efforts.

Different vehicle types have different installation requirements. For private vehicles, the number will vary

widely depending on the type of vehicles owned by the citizens recruited for participation. For the known

vehicle types, the requirements identified to date are:

• COTA: Through-hole antenna mounting may be permitted on COTA’s coaches manufactured by

Gillig if the antenna does not interfere with other existing antennae and, preferably, if it replaces an

existing unused antenna left in the vehicle to prevent water incursion. On New Flyer coaches,

antennae will be mounted to the fiberglass roof deflector and use the existing conduit path into the

vehicle. LDVs will not allow for through-hole antenna placement.

• City DPS (Police): No through-hole mounting of the antenna will be allowed. Vehicles will have an

accessible secure trunk and the OBU will be mounted there. Placement of antenna and OBU and

approach to obtaining vehicle power must be approved for each vehicle type prior to installation.

• City DPS (EMS): Through-hole mounting of the antenna will be allowed. Vehicles will have an

accessible OBU mounted under the dash or under the passenger seat. Placement of antenna, and


• City DPS (Fire): Through-hole mounting of the antenna will not be allowed. Vehicles will have an

accessible OBU mounted under the dash or under the passenger seat. Placement of antenna and


• Franklin County Engineer’s Office: No through-hole mounting of the antenna will be allowed.

Vehicles without an accessible secure trunk must have the OBU mounted under the dash on the

sidewall. Form factor and location of the HMI, placement of antenna and OBU, and approach to

obtaining vehicle power must be approved for each vehicle type prior to installation.



• Private Freight Operator: No through-hole mounting of the antenna will be allowed. Location of

antenna and OBU, and approach to obtaining vehicle power must be approved for each tractor type

before installation.

Table 11: Characteristics of In-Vehicle Equipment by Vehicle Class

Vehicle Type Partner or Source # of Vehicles

Onboard Unit Equipment Characteristics

LDV Private vehicle 1,019 All V2X safety apps, HMI, no data logging, integrator-led installation

Public service city fleet vehicle

198 All V2X safety apps, HMI, no data logging, coordination of installation with City fleets

COTA supervisor vehicle 25 All V2X safety apps, HMI, no data logging, coordination with COTA maintenance

Emergency Vehicle

Public safety fire truck/Emergency medical services)

30 EVP only, minimal HMI (EVP granted), no data logging, integration with siren, coordination of installation with City fleet

Public safety police cruiser

80 EVP only, minimal HMI (EVP granted), no data logging, integration with siren, coordination of installation with City fleet

HDV Private freight vehicle 14 BSM and FSP only, no HMI, no data logging, coordination with fleet owner

County engineer 6 BSM only, no HMI, no data logging, coordination with fleet owner

Transit Vehicle

COTA transit bus*

(fixed-route)

350 All V2X Safety Apps, TSP, no HMI, data logging and offloading, coordination with COTA maintenance

COTA paratransit bus 80 All V2X Safety Apps, no HMI, data logging and offloading, coordination with COTA maintenance

Total 1,802 (maximum total planned)


*Only the buses designated for the C-MAX BRT service will have active TSP. All others should be TSP-capable but are

not expected to be activated at the start of the deployment period. BSM = basic safety message; FSP = Freight Signal

Priority; HMI = human-machine interface; V2X = either V2I (vehicle-to-infrastructure) or V2V (vehicle-to-vehicle).

4.1.2.3. CONNECTED VEHICLE ENVIRONMENT INSTALLATION MAP

Figure 11 presents an overview of the CVE project, showing the intersections, the applications that will be

available at each intersection, and the elements (such as schools, police and fire stations, and freight

corridors) that led to the selection of the intersection/application combination proposed. The applications

used on each RSU will depend on the problem(s) identified for that RSU’s location.



Figure 11: Connected Vehicle Environment Applications by Intersection





4.1.3. Connected Vehicle Environment Infrastructure Installation Entities and

Responsibilities

Installation of all CVE infrastructure elements will require the participation of several entities working

together to develop the plans, quantities, and configuration for the equipment to be installed at each

intersection and in vehicle type. Figure 12 identifies all parties involved.


Figure 12: Organizations Responsible for Connected Vehicle Environment

Infrastructure Installation

The CVE project manager (PM) will serve as a conduit between the interested and vested parties within the

Smart Columbus program, to include the equipment and integration vendors, the Smart Columbus Program

Management Office (PMO), the Operating System team, the Smart Columbus Communications team, other

city departments and divisions (i.e. Traffic Management, Operations, Public Safety, and Fleet), Smart

Columbus partners (i.e., COTA, Franklin County, DriveOhio/Ohio Department of Transportation), and other

Smart Columbus projects. Each of these entities either offers inputs into the CVE, desires data from the

CVE, or offers or desires some combination of both.

Table 12 summarizes all entities and their roles and responsibilities regarding hardware element installation.



Table 12: Connected Vehicle Environment Installation Entities and Responsibilities

Organization Responsibilities

Smart Columbus PMO

CVE Project Team

Operating System Project Team

Communications PM

The CVE PM: Overarching project manager and technical lead responsible for coordinating all parties and ensuring that each meet their obligations according to their respective scopes, schedules, and budgets.

Communications PM: Identify, recruit, and manage private-sector participants.

CVE Project Team: Oversee coordination of OBU integrator and fleet owners. Coordination with Drive Ohio/Ohio Department of Transportation for implementation of security credentials. Review all items that are delivered as part of the scope before acceptance.

Operating System Team: Data testing and integration. Provides remote access to the CVE Network and Operating System (as necessary) to the RSU Infrastructure Integrator (vendor). The backend interface to allow for uploading of this data to the Operating System will be the responsibility of the Operating System Team, the design will be dependent on the approach implemented and will be completed during recurring sprint planning sessions. CV event data from the shuttle shall be uploaded to the Operating System weekly, at a minimum.

Coordinate and track installation of all equipment: Work with City fleets to schedule install for police, fire, and emergency vehicles, tracking quantity of OBU installations by vehicle type, quantity and RSU by configuration type.

Coordinate with the hardware integrators to provide a test and integration lab that will allow the roadside and in-vehicle integrators and City traffic engineering staff to work together for overall system integration and testing activities to occur. Bench space, power, internet, GNSS services, and access to both the CV network and the traffic signal network will be made available for two staff members.

City of Columbus Department of Technology

Responsible for the programming and configuration of Layer 3 Ethernet Switches at all the communication node locations and firewalls at TMC. They are also responsible for the set-up of IPV6 and public IPV4 networks.

Systems Integrator The City will procure services of separate systems integrators responsible to purchase, configure, install, test, operate, and maintain roadside infrastructure elements and in-vehicle components.

Note: Later cells in this table describe the roadside and in-vehicle integrators.

City of Columbus Fleets (Police, Fire, Emergency)

Provide supervised access for purpose of installation of the OBU hardware in City-owned fleet vehicles. Installation is expected to occur during normal business hours between 9 a.m. and 5 p.m., Monday through Friday.

A maximum of eight vehicles will be made available for a given day, however this number is subject to change based on availability.




COTA Provides unsupervised access to the qualified installer at COTA’s two garage facilities located at McKinley Avenue (fixed-route fleet) and Fields Avenue (paratransit/other) during overnight hours between 8 p.m. and 4 a.m., 7 days a week. A maximum of eight vehicles will be made available for a given shift. Available vehicles will be parked in a designated area each night.

COTA staff will work with the installer to integrate the OBU with the bus on-vehicle network that enables transferring the logged CV data via Wi-Fi upon the vehicle’s return to the garage.

COTA will provide the server hardware.

Franklin County Engineer’s Office

Provide supervised access for purpose of installation of the OBU hardware in two county-owned fleet vehicles. Installation will be expected to occur at the county’s maintenance facility located at Dublin Road.

Conduct precision survey and mapping work to support the data gathering requirements for this effort and will be provided to the RSU Infrastructure Integrator (vendor) to convert this point data into the corresponding MAP message.

Private Freight Operator Provide supervised access to the vehicles at its facility located in the Rickenbacker region.

RSU Infrastructure Integrator (vendor)

Prepare and submit a detailed work plan and schedule that meets the Smart Columbus schedule.

Participate in weekly status meeting with the CVE Management Team.

Initiate procurement of the hardware and software components necessary to meet the infrastructure requirements for CVE in accordance with the approved schedule and work plan.

Prepare and submit installation plans for each of the four major RSU configurations:

o General

o School zone-enabled

o TSP-enabled

o FSP-enabled

Provide a central management system that allows for health and status monitoring, software updates, and other operational features.

Responsible to support the necessary test activities, as developed by a separate third party to Smart Columbus, and to demonstrate that the infrastructure components meet all mandatory requirements.

Required to provide necessary training and guidance to the electrical contractor to support the installation of RSUs and any other necessary roadside equipment.

Responsible for managing the inventory of RSUs including their storage before installation and maintain records for device installation and configuration.

Provide on-site training to City staff and prepare and submit final Standard Operating Procedures along with a user training guide no later than April 2020.




In-Vehicle Systems Integrator (vendor)

Provide necessary staff, facilities, tools, equipment, and training necessary to procure, prepare, install, and maintain the OBUs for the estimated 1,000 private, and 800 public fleet participants, for the duration of the operational period, which goes live in July 2020 and ends on March 31, 2021. All installation materials should be provided in advance of the scheduled installations.

Provide product sheets for the major components of the system proposed to be installed. This includes the OBU, HMI(s), antenna(s) and other components of the installed system visible to the participant.

Manage the inventory of OBUs including their storage before installation and maintains records of device installation and configuration.

Provide a mobile-accessible, online portal through which participants can schedule installation.

Contracts and oversees with installer(s) and coordinate as needed with project team and fleet owners for police, fire, emergency, and freight operator) for installations taking place at their facilities.

Provides all materials and tools to complete the installation.

Develop the back-office software platform that will parse the logs from the COTA vehicles and make them available for review via a simple dashboard.

Coordinate with the Ohio Department of Transportation (ODOT) security credential provider (ISS) to have any equipment provisioned with the correct security certificates prior to shipment or as it aligns with the project goals.

Electrical Contractor Responsible for the construction of the physical network infrastructure associated with the CVE.

Installation of RSUs, PoE modules, GPS antennas, etc., that the RSU Infrastructure Integrator vendor provides.



This section describes the type of infrastructure that will be installed at each hub location, gives an overview

of where the items will be installed, and summarizes the parties responsible for the installation.

4.2.1. Infrastructure Installation

The SMH project is primarily infrastructure-oriented. An IK will be installed at each location and is intended

to be the anchor of the hub. Although the IK will contain other Smart Columbus applications (specifically,

MMTPA/CPS), configuration of these applications is outside the scope of the SMH project. In addition to the

IK, other installed infrastructure at each location depends on the available site amenities.

Table 13 summarizes amenities by SMH location; the summaries were developed through the stakeholder

engagement process the ConOps plan describes.



Table 13: Smart Mobility Hub Amenities by Location

Location

Amenities

IK

Wi-F

i

Park

and R

ide

Pic

k-u

p/D

rop-o

ff Z

ones

Car-

Share

Bik

e-S

hare

Bik

e R

acks

Dockle

ss P

ark

ing

Real-T

ime D

ispla

y

Com

pre

hensiv

e T

rip-P

lannin

g

EC

B

Ele

ctr

ic V

ehic

le C

harg

ing *

AV

Shuttle

**

Columbus State Community College

P P – – P E E P E P P – –

Linden Transit Center P E – P – P – P E P P – P


P P – P P P E P E P P – –

Northern Lights Park and Ride P P E P P – E P E P P P –


P P – P P P E P – P P – P

Easton Transit Center P E E P – P E – E P P – –

Note: P = proposed, E = existing * While defined in the SMH project documents, this will be pursued outside of the scope of this

project by the private property owner. ** This is part of the CEAV project, another project in the Smart Columbus portfolio.


4.2.2. Overview of Infrastructure by Location

The focus of the installation at each of the SMH locations is the IK. While each location will vary in terms of

amenities provided, typical improvements include installing IK, signage, pavement markings (both added

and removed) to indicate ride-hailing and car-sharing locations, dockless bike- and scooter-parking zones,

and CEAV station locations.

4.2.2.1. COLUMBUS STATE COMMUNITY COLLEGE

The Columbus State Community College (see Figure 13) attracts largely local commuter students and is a

major employment center. COTA serves this site, which also contains a CMAX BRT station. A considerable

number of transit-users use this site, which offers public Wi-Fi and real-time transit information displays. An

IK will be installed at this site. At the IK, users can access features such as the Pivot app, which is a

comprehensive trip planning application that will be deployed as part of the Smart Columbus MMTPA/CPS

project and an emergency call button (ECB). The site will also offer a dockless parking zone and car-share

amenities at the southwest corner of Cleveland Avenue and Mt. Vernon Avenue. Signs and pavement

markings images are not shown on Figure 13 because they have not been installed at this SMH location at

the time of publication.



Figure 13: Smart Mobility Hub at Columbus State Community College

Note: Improvements shown are not to scale and are only used for location representation.


4.2.2.2. LINDEN TRANSIT CENTER

The Linden Transit Center is a COTA location (see Figure 14) within a revitalized area that includes direct

access to healthcare and daycare centers. The facility offers public Wi-Fi, real-time transit information

displays, and it will feature an IK at which users can access the Pivot app and an ECB. Bike-sharing docks,

a dockless parking zone, and reserved space for ride-hailing pick-up/drop-off will also be available at this

location, which will also be a station for the automated shuttle as part of the CEAV project (see Section 4.3

for further details). Figure 15, Figure 16 and Figure 17 show signage and pavement markings installed at

Linden Transit Center.



Figure 14: Smart Mobility Hub at Linden Transit Center





Figure 15: Dockless Parking Sign and Parking Zone at Linden Transit Center


Figure 16: Ride-Hailing Sign and Pavement Markings at Linden Transit Center




Figure 17: Smart Mobility Hub Sign at Linden Transit Center


4.2.2.3. METRO LIBRARY – LINDEN BRANCH

An IK will be deployed at the Columbus Metro Library – Linden Branch, located on Cleveland Avenue

between Kenmore Road and Kohr Place (see Figure 18). The IK will provide users with the Pivot app and

an ECB. This location will also provide bike-sharing docks and reserved car-sharing and ride-hailing

services, which will help bridge the gap for pedestrians between the adjacent Linden Transit Center and

Northern Lights Park and Ride facilities. Figure 19 and Figure 20 show the signage and pavement

markings installed at Metro Library – Linden Branch location.



Figure 18: Smart Mobility Hub at Columbus Metro Library – Linden Branch





Figure 19: Smart Mobility Hub Sign at Metro Library – Linden Branch


Figure 20: Smart Mobility Hub Sign, Dockless Parking Sign, and Dockless Parking Zone at





4.2.2.4. NORTHERN LIGHTS PARK AND RIDE

The Northern Lights Park and Ride is a new COTA-operated facility at the Northern Lights shopping center

(see Figure 21). This site has infrastructure to support future electric vehicle (EV) charging stations. This

location will include an IK at which users can access the Pivot app and an ECB. The Northern Lights Park

and Ride will also provide space for dockless device parking, car-sharing spaces, ride-hailing pick-up/drop-

off, and bike-share docks. Figure 22 and Figure 23 show some of the signs and pavement markings

installed at this SMH location.

Figure 21: Smart Mobility Hub at Northern Lights Park and Ride





Figure 22: Ride-Hailing Sign at Northern Lights Park and Ride


Figure 23: Smart Mobility Hub Sign, Dockless Parking Sign and Dockless Parking Zone at

Northern Lights Park and Ride




4.2.2.5. ST. STEPHENS COMMUNITY HOUSE

St. Stephens Community House is located near the intersection of 17th and Joyce avenues (see Figure

24). The lobby at the St. Stephens Community House will house an IK, which will provide users access to

the Pivot app and an ECB. This project will provide zones for dockless parking, bike-sharing and ride hailing

pick-up/drop-off, and car-sharing amenities at the community house, which will also be a station for the

automated shuttle as part of the CEAV project (see Section 4.3 for further details). Figure 25 show some of

the signs and pavement markings installed at this SMH location.

Figure 24: Smart Mobility Hub at St. Stephens Community House





Figure 25: Smart Mobility Hub Sign at St. Stephens Community House


4.2.2.6. EASTON TRANSIT CENTER

The Easton Transit Center is near the intersection of Stelzer Road and Transit Drive (see Figure 26) and

serves transit and FMLM needs of travelers accessing the Easton Center district. Operated by COTA, it is

currently equipped to provide many of the SMH-defined services. An IK will be installed at the transit center

at which users can access the Pivot app and an ECB. A bike-share dock and ride-hailing amenities will also

be available at the transit center. Figure 27 and Figure 28 show SMH signs installed at Easton Transit

Center.



Figure 26: Smart Mobility Hub at Easton Transit Center





Figure 27: Smart Mobility Hub Sign at Easton Transit Center


Figure 28: Ride-Hailing Sign at Easton Transit Center




4.2.3. Infrastructure Installation Entities and Responsibilities

Several entities will need to work together to develop the plans, quantities, and configurations for the SMH

equipment to be installed at each of the locations. Table 14 summarizes roles and responsibilities related to

hardware element installation.

Table 14: Smart Mobility Hubs Infrastructure Installation Entities and Responsibilities


Smart Columbus PMO

SMH Project Team


Communications PM

SMH Project Team: Coordinate installation and testing activities. Also perform site surveys, develop installation plans, and procure installation contractor. Help property owners coordinate agreements with mobility providers.

Communications PM: Identify, recruit, and manage private-sector participants.

Operating System: Test and integrate data.


Enter into agreements with mobility providers and IK vendor to access site.

Enter into agreement with City for installation of amenities.

COTA Enter into agreements with mobility providers to access COTA-operated sites.

Enter into agreements with IK vendor to access Easton Transit Center.


Columbus Metro Library – Linden Branch

Enter into agreements with mobility providers to access to the site.


IK Vendor Install IKs and connect them to the network.

Operate and maintain the IKs.

Enter into agreements with St. Stephens Community House and COTA for access to private properties.

City of Columbus Enter into agreement with IK vendor for permits

Install signs.

Install thermoplastic pavement markings for designated parking stalls and dockless zones.

Install concrete for bike-share dock and dockless zone.

Coordinate the placement of bike-share docking stations with the Columbus Department of Recreation and Parks.



This section provides an overview of the Linden CEAV route, focusing on the infrastructure that will be

installed at each station location, the flow and direction of the CEAV route into and out of each station

location. and the parties responsible for installation.

4.3.1. Route Details

The route chosen for the Linden CEAV runs between St. Stephens Community House and COTA’s Linden

Transit Center, both of which are designated as SMHs in an out-and-back-style operation. The goal of this



route is to connect the center users with the CMAX BRT line and neighboring community. This route

connects the centers via the following four stations (see Figure 29; distinct colors differentiate travel

directions):

• Station 1: Linden Transit Center (COTA)

• Station 2: Rosewind Resident Council

• Station 3: Douglas Community Recreation Center

• Station 4: St. Stephens Community House

Figure 30 shows what the CEAVs look like.



Figure 29: Connected Electric Autonomous Vehicles Route Overview




Figure 30: Smart Columbus Connected Electric Autonomous Vehicles




4.3.2. Station Locations

4.3.2.1. LINDEN TRANSIT CENTER (CENTRAL OHIO TRANSIT AUTHORITY)

COTA’s Linden Transit Center is at the intersection of Cleveland Avenue and 11th Avenue (see Figure 31).

COTA’s CMAX BRT is available on Cleveland Avenue. CEAV service from the Linden Transit Center will

connect travelers to the nearby neighborhood community and its resources. The transit center is also a

designated SMH location, at which travelers will have access to other transportation modes and an IK

containing embedded touchscreen displays with access to the Pivot app and an ECB. The transit center will

also provide travelers with bike-sharing, ride-hailing and dockless device parking.

Figure 31: Linden Transit Center Connected Electric Autonomous Vehicles Station


4.3.2.2. ROSEWIND RESIDENT COUNCIL

The CEAV station at Rosewind Resident Council (see Figure 32) will connect travelers from a nearby

residential community to the COTA’s CMAX BRT line on Cleveland Avenue. It will provide access to multiple

mobility options at St. Stephens Community House or Linden Transit Center SMH locations.



Figure 32: Rosewind Resident Council Connected Electric Autonomous Vehicles Station


4.3.2.3. DOUGLAS COMMUNITY RECREATION CENTER

At the Douglas Community Recreation Center (see Figure 33), travelers from nearby residential and

community resources will be connected to recreational facilities and to the COTA’s CMAX BRT line on

Cleveland Avenue. This CEAV station will also provide access to multiple mobility options at the nearby

St. Stephens Community House or Linden Transit Center SMH locations.



Figure 33: Douglas Community Recreation Center Connected Electric Autonomous Vehicles

Station


4.3.2.4. ST. STEPHENS COMMUNITY HOUSE

St. Stephens Community House is on 17th Avenue near Joyce Avenue. The CEAV station at this location is

shown in Figure 34. The CEAV route service from the community house to Linden Transit Center will

provide travelers access to COTA’s CMAX BRT line on Cleveland Avenue as well as to the nearby

residential communities and recreation center. St. Stephens Community House is also a designated SMH

location where travelers will be able to access other modes of transportation and an IK with embedded

touchscreen that provides users access to the Pivot app and an ECB. Travelers will also be able to use

resources such as car- and bike-sharing services and dockless device parking.

St. Stephens Community House site will also serve as the charging, storage, and maintenance facility for all

the CEAV vehicles when they are not in service. Figure 35 shows the storage and charging infrastructure of

the CEAVs



Figure 34: St. Stephens Community House Connected Electric Autonomous Vehicles Station




Figure 35: CEAV Charging Location and Infrastructure


4.3.3. Connected Electric Autonomous Vehicles

The proposed route will be served by two CEAV shuttles in service at any time. Service frequency

necessary to address FMLM/only-mile challenges was decided considering the ridership data available

during the demonstration period. Presently, 24-minute total route loop time and 12-minute headways are

proposed. Station departure times will be scheduled to complement nearby COTA services.

The AV vendor will also supply onboard operators for the vehicles. These individuals, who will be properly

trained, will always be on board when a vehicle is operating. The number of operators trained to operate the

AV shuttles will be determined by shift time per operator.

4.3.3.1. INFRASTRUCTURE INSTALLATION ENTITIES AND RESPONSIBILITIES

Several entities will need to work together to develop the plans, quantities, and configurations for the

signage to be installed at each of the CEAV station locations. Table 15 summarizes roles and

responsibilities for the hardware element installation.



Table 15: Connected Electric Autonomous Vehicles Infrastructure Installation

Entities and Responsibilities


Smart Columbus PMO

CEAV Project Team


Communications PM

CEAV project team: coordinate installation and testing activities

Communications PM: Communication surrounding the demonstration, press releases, answering FAQs and community outreach

Operating System: test and integrate data

Coordinate stakeholders and vendor

City of Columbus Fabricate and install signage at Douglas Community Recreation Center, Rosewind Resident Council, and St. Stephens Community House stations

Fabricate signage and provide to COTA for installation at Linden Transit Center

Install concrete landing pads for stations servicing Rosewind Resident Council and Douglas Community Recreation Center

St. Stephens Community House Provide guidance and approval for storage, charging, and maintenance location

Enter into agreement with AV vendor for site access

COTA Install signage for CEAV station at Linden Transit Center

Enter into agreement with AV vendor for site and restroom access

AV vendor Install storage and charging outlets at the St. Stephens Community House

Coordinate with stakeholders and SMH Project team on final station locations

Enter into agreements with property owners to access sites


Demonstration Site Map and Installation Schedule – Draft Report | Smart Columbus Program | 73

Installation Schedule

In this chapter, milestones are indicated for each infrastructure element’s installation and testing for the

CVE, SMH, and CEAV projects.


CVE RSUs and OBUs will be installed by trained and qualified manufacturer installers. Installations will be

overseen by the Smart Columbus PMO as defined in Table 12 (Section 4.1.3). The OBU installations will

require the most planning, as OBUs will need to be retrofitted to a variety of privately-owned vehicles and

COTA buses. For the RSUs, in addition to the detailed installation plans that will accompany the invitation for

bid for the electrical contractor, the RSU integrator will be responsible for providing installation training

materials. For the OBUs, the in-vehicle integrator will submit an installation plan for meeting the CVE user

needs and system requirements. Installers will need to follow the installation safety requirements. In

addition, diagrams of OBU installation (including OBU, antenna, HUD/HMI, and speaker, if applicable) will

be provided for each vehicle type prior to installation. Lessons learned in the United States Department of

Transportation (USDOT) CV pilots will be applied as appropriate to the CVE installation process.

The high-level installation schedule for the CVE infrastructure installation is presented in Table 16, which

highlights only the milestone (major) activities. Detail-level test dates are in the CVE Test Plan document.

Table 16: Connected Vehicle Environment Installation Milestones

Date Task Description

March 2019 Develop installation plans Inspected each RSU location.

Measured the conduit runs for cable.

Documented location of each device installation location.

Developed construction plans.

Test conducted for clearance of exiting conduit to accept additional cables.

February 2020 Begin installation (RSUs) Install RSUs.

February 2020 Begin installation (OBUs) Install 1,500 to 1,800 OBUs.

February 2020 Begin infrastructure testing Begin testing the equipment installed (RSUs).

April 2020 End installation (RSUs) Complete installation of all RSUs.

July 2020 End infrastructure testing (RSUs)

Perform final acceptance test of all equipment installed (RSUs).

October 2020 End vehicle installation and testing (OBUs)

Perform final acceptance test of all equipment installed (OBUs).


Chapter 5. Installation Schedule


Table 17 presents additional detail on currently planned CVE infrastructure installation activities, including

estimated start and end dates. As described above, as contracts with integrators and contractors are

finalized, the City will clarify the activities and specify exact dates and may add more activities.

Table 17: Connected Vehicle Environment Detailed Installation Activities and Schedule

Task Timeline

Site surveys (intersections) November 2018 – January 2019

Site installation plans December 2018 – April 2019

RSU System Integrator procurement March 2019 – July 2019

OBU System Integrator procurement March 2019 – July 2019

Electrical contractor procurement April 2019 – August 2019

Equipment delivery (RSU) September 2019 – January 2020

Equipment delivery (OBU) November 2019 – June 2020

Application development for RSUs September 2019 – December 2019

Application development for OBUs (light vehicles) September 2019 – May 2020

Application development for OBUs (other vehicles) September 2019 – May 2020

Participant recruitment February 2020 – September 2020

Installation training and guidance (RSU) November 2019 – January 2020

Antenna testing (OBU) November 2019 – December 2019

OBU installation February 2020 – October 2020

Pre-wiring of intersections August 2019 – October 2019

RSU installation February 2020 – April 2020

Delivery of Central Management System (RSU Health Monitoring) February 2020 – June 2020

Interoperability test December 2019 – February 2020

Development of acceptance test criteria February 2020

Acceptance testing June 2020

Regression testing (until acceptance) June 2020 – July 2020

Demonstration period July 7, 2020 – March 31, 2021



Installations at the SMH locations will be overseen by the Smart Columbus PMO, as indicated in Table 14

(Section 4.2.3). Smart Columbus will work with the installation contractor and IK vendor to develop the

specific activities involved in completing the installation and testing for all elements. The high-level

installation schedule for the SMH infrastructure is presented in Table 18, which highlights the milestone

activities and dates for completion.



Table 18: Smart Mobility Hubs Installation Milestones


March 2019 Complete installation plans Inspected each SMH location

Documented the location of each installation location

Developed construction plans

Developed signage for the individual SMH facilities

August 2019 Begin construction (non-IK elements)

Installed non-IK amenities such as signage, pavement markings, and bike racks

December 2019 Complete construction (non-IK elements)

Performed final component verification of all items installed

January 2020 Begin installation (IKs) Install six IKs

January 2020 Complete installation (IKs) Perform final acceptance test of all IK functionality, beginning the week of January 20, 2020.


The City has developed a list of activities that must be completed to ensure traceability from systems

engineering planning documents to installation plans and test results. Table 19 captures the agreements

that will be necessary for all parties to successfully install and test the infrastructure at each SMH location.

Table 19: Smart Mobility Hubs Detailed Installation Activities and Schedule

Task Timeline

Site surveys November 2018 – January 2019

Site installation plans December 2018 – March 2019

Sign production August 2019 – September 2019

Sign installation October 2019 – November 2019

Agreements with property owners April 2019 – September 2019

Beginning of construction August 2019

Beginning of IK installation January 2020

Agreements between property owners and mobility providers July 2019 – February 2020

Acceptance test criteria and test plan April 2019 – October 2019

Completion of construction December 2019

Completion of IK installation January 2020

Integration of MMTPA/CPS into IK system January 2020 – March 2020

Component and system verification January 2020 – February 2020

Acceptance testing February 2020

Regression testing (until acceptance) February 2020

Demonstration period February 2020





Installation of elements at each CEAV station will be overseen by the Smart Columbus PMO, as indicated in

Table 15 (Chapter 4). Smart Columbus will work with property owners and the AV vendor to identify the

specific activities needed to install all elements and test the vehicle(s) for acceptance.

The high-level installation schedule for the CEAV project is presented in Table 20, which highlights the

milestone activities and dates for completion.

Table 20: Connected Electric Autonomous Vehicles Installation Milestones


June 2019 Vendor notice to proceed

Vendor began a detailed assessment of the proposed route and station locations.

July 2019 – October 2019

Complete factory testing

Components and vehicles were verified on site with vendor.

December 2019 Vehicle delivery CEAVs were tested on site in Columbus and non-vehicle amenities (storage, charging, and maintenance infrastructure) were installed according to the plans.

January 9, 2020 Station installations

Concrete landing pads and signage for CEAV stations installed at CEAV stations.

January 23, 2020 Final on-site acceptance testing

Preliminary on site acceptance testing of the CEAV vehicle and route operations was held in December 2019 and final testing will be conducted in January 2020.

January 27, 2020 Standard operating procedures

Standard operating procedures for the vehicles, stations, and routes, will be reviewed and approved by the City prior to launch of service.

January 28, 2020 Service start Passenger service launches will start, with partner preview and media days, followed by public service start.


The City has developed a list of activities (Table 21) that must be completed so that the pathway from

systems engineering documents to installation plans and test results can be traced.

Table 21: Connected Electric Autonomous Vehicles Detailed Installation Activities and

Schedule

Task Timeline1

Acceptance test criteria, test plan and procedures, training plan June 2019 – November 2019

Site assessment June 2019 – October 2019

Factory acceptance July 2019 – October 2019

Provide proof of vehicle insurance September 2019

Final route and operating parameters October 2019 – November 2019

Vehicle delivery December 2019

Completed licenses, permits December 2019



Task Timeline1

Vehicle operator training December 2019 – January 2020

Signage and concrete installed at stations January 2020

Preliminary acceptance testing (component and system verification)

January 16, 2020

Final acceptance/operational test January 23, 2020

Tabletop exercise January 23, 2020

Regression testing (until acceptance) January 24, 2020

Final standard operating procedures January 27, 2020

Integration of AV vehicle data to Operating System January 28, 2020

Demonstration period January 28, 2020 – January 27, 2021


1 If a start and end month are not provided, the task will be completed entirely within the month provided in the timeline column.


Acronyms and Definitions

Table 22 contains project-specific acronyms used throughout this document.

Table 22: Acronym List

Abbreviation/Acronym Definition

ADA Americans with Disabilities Act

Apps Smart Applications

AV Automated Vehicle

BRT Bus Rapid Transit

BSM Basic Safety Message

CABS Campus Area Bus Service

CEAV Connected Electric Autonomous Vehicles

CMAX COTA’s Bus Rapid Transit (BRT) Service

ConOps Concept of Operations

CORS Continuously Operating Reference System

COTA Central Ohio Transit Authority

CPS Common Payment System

CTSS Columbus Traffic Signal System

CVCP Connected Vehicle Co-processor

CVE Connected Vehicle Environment

DMS Data Management System

DPS Department of Public Safety

DSRC Dedicated Short Range Communication

ECB Emergency Call Button

EMS Emergency Medical Services

EPM Event Parking Management

EV Electric Vehicle

EVP Emergency Vehicle Preemption

FMLM First Mile/Last Mile

FSP Freight Signal Priority

GNSS Global Network Satellite System

GPS Global Positioning System

HDMI High-Definition Multimedia Interface

Appendix A. Acronyms and Definitions



HDV Heavy-Duty Vehicle

HMI Human-Machine Interface

HUD Heads-up Display

IK Interactive Kiosk

ISP Internet Service Provider

IT Information Technology

ITS Intelligent Transportation Systems

KOS Kiosk Operating System

LDV Light-Duty Vehicle

MaaS Mobility as a Service

MAPCD Mobility Assistance for People with Cognitive Disabilities

MCO Managed Care Organization

MMITSS Multimodal Intelligent Traffic Signal System

MMTPA Multimodal Trip Planning Application (Pivot Application)

MORPC Mid-Ohio Regional Planning Commission

NEMT Non-Emergency Medical Transportation

OBU Onboard Unit

ODM Ohio Department of Medicaid

ODOT Ohio Department of Transportation

Operating System Smart Columbus Operating System

OSU The Ohio State University

PIECE Prevocational Integrated Education and Campus Experience

PM Project Manager

PMO Project Management Office

PoE Power-over-Ethernet

PTA Prenatal Trip Assistance

RLVW Red Light Violation Warning

RSSZW Reduced Speed School Zone Warning

RSU Roadside Unit

SCC Smart City Challenge

SCMS Security Credential Management System

SMH Smart Mobility Hub

SoS System of Systems

TBA to be assigned

Appendix A. Acronyms and Definitions



TMC Traffic Management Center

TSP Transit Signal Priority

USB Universal Serial Bus

USDOT United States Department of Transportation

V2I Vehicle-to-Infrastructure

V2V Vehicle-to-Vehicle

V2X V2V or V2I



List of Connected Vehicles Deployed by Partner

Table 23: Central Ohio Transit Authority Fixed-Route Vehicles

Vehicle Number Year Description Branding

1007 2010 2010 Gillig LF 40FT

1004 2010 2010 Gillig Hybrid LF 40FT



1008 2010 2010 Gillig LF 40FT

1009 2010 2010 Gillig LF 40FT

1010 2010 2010 Gillig LF 40FT

1011 2010 2010 Gillig LF 40FT

1012 2010 2010 Gillig LF 40FT

1013 2010 2010 Gillig LF 40FT

1014 2010 2010 Gillig LF 40FT

1015 2010 2010 Gillig LF 40FT

1016 2010 2010 Gillig LF 40FT

1017 2010 2010 Gillig LF 40FT

1018 2010 2010 Gillig LF 40FT

1019 2010 2010 Gillig LF 40FT

1020 2010 2010 Gillig LF 40FT

1021 2010 2010 Gillig LF 40FT

1022 2010 2010 Gillig LF 40FT

1023 2010 2010 Gillig LF 40FT

1024 2010 2010 Gillig LF 40FT

1025 2010 2010 Gillig LF 40FT

1026 2010 2010 Gillig LF 40FT

1027 2010 2010 Gillig LF 40FT

1028 2010 2010 Gillig LF 40FT

1029 2010 2010 Gillig LF 40FT

1030 2010 2010 Gillig LF 40FT

1031 2010 2010 Gillig LF 40FT

Appendix B. List of Connected Vehicles Deployed by Partner



1032 2010 2010 Gillig LF 40FT

1033 2010 2010 Gillig LF 40FT

1034 2010 2010 Gillig LF 40FT

1035 2010 2010 Gillig LF 40FT

1036 2010 2010 Gillig LF 40FT

1037 2010 2010 Gillig LF 40FT

1038 2010 2010 Gillig LF 40FT

1039 2010 2010 Gillig LF 40FT

1040 2010 2010 Gillig LF 40FT

1041 2010 2010 Gillig LF 40FT

1042 2010 2010 Gillig LF 40FT

1043 2010 2010 Gillig LF 40FT

1044 2010 2010 Gillig LF 30FT

1045 2010 2010 Gillig LF 30FT

1046 2010 2010 Gillig LF 30FT

1101 2011 2011 Gillig LF 40FT

1102 2011 2011 Gillig LF 40FT

1103 2011 2011 Gillig LF 40FT

1104 2011 2011 Gillig LF 40FT

1105 2011 2011 Gillig LF 40FT

1106 2011 2011 Gillig LF 40FT

1107 2011 2011 Gillig LF 40FT

1108 2011 2011 Gillig LF 40FT

1109 2011 2011 Gillig LF 40FT

1110 2011 2011 Gillig LF 40FT

1111 2011 2011 Gillig LF 40FT

1112 2011 2011 Gillig LF 40FT

1113 2011 2011 Gillig LF 40FT

1114 2011 2011 Gillig LF 40FT

1115 2011 2011 Gillig LF 40FT

1116 2011 2011 Gillig LF 40FT

1117 2011 2011 Gillig LF 40FT

1118 2011 2011 Gillig LF 40FT

1119 2011 2011 Gillig LF 40FT




1120 2011 2011 Gillig LF 40FT

1121 2011 2011 Gillig LF 40FT

1122 2011 2011 Gillig LF 40FT

1123 2011 2011 Gillig LF 40FT

1124 2011 2011 Gillig LF 40FT

1125 2011 2011 Gillig LF 40FT

1126 2011 2011 Gillig LF 40FT

1127 2011 2011 Gillig LF 40FT

1128 2011 2011 Gillig LF 40FT

1129 2011 2011 Gillig LF 40FT

1130 2011 2011 Gillig LF 40FT

1131 2011 2011 Gillig LF 40FT

1132 2011 2011 Gillig LF 40FT

1133 2011 2011 Gillig LF 40FT

1134 2011 2011 Gillig LF 40FT

1135 2011 2011 Gillig LF 40FT

1136 2011 2011 Gillig LF 40FT

1137 2011 2011 Gillig LF 40FT

1138 2011 2011 Gillig LF 30FT

1139 2011 2011 Gillig LF 30FT

1140 2011 2011 Gillig LF 30FT




1201 2012 2012 Gillig LF 40FT

1202 2012 2012 Gillig LF 40FT

1203 2012 2012 Gillig LF 40FT

1204 2012 2012 Gillig LF 40FT

1205 2012 2012 Gillig LF 40FT

1206 2012 2012 Gillig LF 40FT

1207 2012 2012 Gillig LF 40FT

1208 2012 2012 Gillig LF 40FT

1210 2012 2012 Gillig LF 40FT

1211 2012 2012 Gillig LF 40FT




1212 2012 2012 Gillig LF 40FT

1213 2012 2012 Gillig LF 40FT

1214 2012 2012 Gillig LF 40FT

1215 2012 2012 Gillig LF 40FT

1216 2012 2012 Gillig LF 40FT

1217 2012 2012 Gillig LF 40FT

1218 2012 2012 Gillig LF 40FT

1219 2012 2012 Gillig LF 40FT

1220 2012 2012 Gillig LF 40FT

1221 2012 2012 Gillig LF 40FT

1222 2012 2012 Gillig LF 40FT

1223 2012 2012 Gillig LF 40FT

1209 2012 2012 Gillig LF 40FT

1319 2013 2013 Gillig CNG LF 35FT

1301 2013 2013 Gillig CNG LF 40FT

1303 2013 2013 Gillig CNG LF 40FT

1304 2013 2013 Gillig CNG LF 40FT

1302 2013 2013 Gillig CNG LF 40FT

1305 2013 2013 Gillig CNG LF 40FT

1306 2013 2013 Gillig CNG LF 40FT

1307 2013 2013 Gillig CNG LF 40FT

1308 2013 2013 Gillig CNG LF 40FT

1309 2013 2013 Gillig CNG LF 40FT

1310 2013 2013 Gillig CNG LF 40FT

1311 2013 2013 Gillig CNG LF 40FT

1312 2013 2013 Gillig CNG LF 40FT

1313 2013 2013 Gillig CNG LF 40FT

1314 2013 2013 Gillig CNG LF 40FT

1315 2013 2013 Gillig CNG LF 40FT

1316 2013 2013 Gillig CNG LF 40FT

1317 2013 2013 Gillig CNG LF 40FT

1318 2013 2013 Gillig CNG LF 40FT

1320 2013 2013 Gillig CNG LF 35FT

1321 2013 2013 Gillig CNG LF 35FT




1322 2013 2013 Gillig CNG LF 35FT

1323 2013 2013 Gillig CNG LF 35FT

1324 2013 2013 Gillig CNG LF 35FT

1325 2013 2013 Gillig CNG LF 35FT

1326 2013 2013 Gillig CNG LF 35FT

1327 2013 2013 Gillig CNG LF 35FT

1328 2013 2013 Gillig CNG LF 35FT

1329 2013 2013 Gillig CNG LF 35FT

1330 2013 2013 Gillig CNG LF 35FT

1401 2014 2014 Gillig CNG LF 30FT

1402 2014 2014 Gillig CNG LF 30FT

1403 2014 2014 Gillig CNG LF 30FT

1404 2014 2014 Gillig CNG LF 30FT

1405 2014 2014 Gillig CNG LF 30FT

1406 2014 2014 Gillig CNG LF 30FT

1407 2014 2014 Gillig CNG LF 30FT

1408 2014 2014 Gillig CNG LF 30FT

1409 2014 2014 Gillig CNG LF 35FT

1410 2014 2014 Gillig CNG LF 35FT

1411 2014 2014 Gillig CNG LF 35FT

1412 2014 2014 Gillig CNG LF 35FT

1413 2014 2014 Gillig CNG LF 35FT

1414 2014 2014 Gillig CNG LF 35FT

1415 2014 2014 Gillig CNG LF 35FT

1416 2014 2014 Gillig CNG LF 40FT

1417 2014 2014 Gillig CNG LF 40FT

1418 2014 2014 Gillig CNG LF 40FT

1419 2014 2014 Gillig CNG LF 40FT

1423 2014 2014 Gillig CNG LF 40FT

1420 2014 2014 Gillig CNG LF 40FT

1421 2014 2014 Gillig CNG LF 40FT

1422 2014 2014 Gillig CNG LF 40FT

1424 2014 2014 Gillig CNG LF 40FT

1425 2014 2014 Gillig CNG LF 40FT




1426 2014 2014 Gillig CNG LF 40FT

1427 2014 2014 Gillig CNG LF 40FT

1428 2014 2014 Gillig CNG LF 40FT

1429 2014 2014 Gillig CNG LF 40FT

1430 2014 2014 Gillig CNG LF 40FT

1431 2014 2014 Gillig CNG LF 40FT

1432 2014 2014 Gillig CNG LF 40FT

1433 2014 2014 Gillig CNG LF 40FT

1434 2014 2014 Gillig CNG LF 40FT

1435 2014 2014 Gillig CNG LF 40FT

1436 2014 2014 Gillig CNG LF 40FT

1501 2015 Gillig CNG LF 35FT









































1601 2016 2016 Gillig CNG LF 40FT

1602 2016 2016 Gillig CNG LF 40FT

1603 2016 2016 Gillig CNG LF 40FT

1604 2016 2016 Gillig CNG LF 40FT

1605 2016 2016 Gillig CNG LF 40FT

1606 2016 2016 Gillig CNG LF 40FT

1607 2016 2016 Gillig CNG LF 40FT

1608 2016 2016 Gillig CNG LF 40FT

1609 2016 2016 Gillig CNG LF 40FT

1610 2016 2016 Gillig CNG LF 40FT

1611 2016 2016 Gillig CNG LF 40FT

1612 2016 2016 Gillig CNG LF 40FT

1613 2016 2016 Gillig CNG LF 40FT

1614 2016 2016 Gillig CNG LF 40FT

1615 2016 2016 Gillig CNG LF 35FT

1616 2016 2016 Gillig CNG LF 35FT

1617 2016 2016 Gillig CNG LF 35FT

1618 2016 2016 Gillig CNG LF 35FT

1702 2017 2017 Gillig CNG LF 30FT




1619 2016 2016 Gillig CNG LF 40FT CMAX


1701 2017 2017 Gillig CNG LF 30FT

1703 2017 2017 Gillig CNG LF 30FT

1704 2017 2017 Gillig CNG LF 30FT

1705 2017 2017 Gillig CNG LF 30FT

1706 2017 2017 Gillig CNG LF 30FT

1707 2017 2017 Gillig CNG LF 35FT

1708 2017 2017 Gillig CNG LF 35FT

1709 2017 2017 Gillig CNG LF 35FT

1710 2017 2017 Gillig CNG LF 35FT

1711 2017 2017 Gillig CNG LF 35FT

1712 2017 2017 Gillig CNG LF 35FT

1713 2017 2017 Gillig CNG LF 35FT














2018 TBD Qty (est. 31)






Table 24: Central Ohio Transit Authority Paratransit Vehicles

Vehicle Number Year Make and Model

1362 2013 2013 CHEVY 4500 CHAMPION

1363 2013 2013 CHEVY 4500 CHAMPION

1364 2013 2013 CHEVY 4500 CHAMPION

1365 2013 2013 CHEVY 4500 CHAMPION

1366 2013 2013 CHEVY 4500 CHAMPION

1367 2013 2013 CHEVY 4500 CHAMPION

1369 2013 2013 CHEVY 4500 CHAMPION

1461 2014 2014 CHEVY 4500 CHAMPION

1462 2014 2014 CHEVY 4500 CHAMPION

1463 2014 2014 CHEVY 4500 CHAMPION

1464 2014 2014 CHEVY 4500 CHAMPION

1465 2014 2014 CHEVY 4500 CHAMPION

1466 2014 2014 CHEVY 4500 CHAMPION

1467 2014 2014 CHEVY 4500 CHAMPION

1468 2014 2014 CHEVY 4500 CHAMPION

1469 2014 2014 CHEVY 4500 CHAMPION

1470 2014 2014 CHEVY 4500 CHAMPION

1471 2014 2014 CHEVY 4500 CHAMPION

1472 2014 2014 CHEVY 4500 CHAMPION

1473 2014 2014 VPG MV-1

1474 2014 2014 VPG MV-1

1475 2014 2014 VPG MV-1

1476 2014 2014 VPG MV-1

1477 2014 2014 VPG MV-1

1478 2014 2014 VPG MV-1

1479 2014 2014 VPG MV-1

1480 2014 2014 VPG MV-1

1481 2014 2014 VPG MV-1

1482 2014 2014 VPG MV-1

1483 2014 2014 VPG MV-1

1484 2014 2014 VPG MV-1

1661 2016 2016 CHEVY 4500 CHAMPION

1662 2016 2016 CHEVY 4500 CHAMPION




1663 2016 2016 CHEVY 4500 CHAMPION

1664 2016 2016 CHEVY 4500 CHAMPION

1665 2016 2016 CHEVY 4500 CHAMPION

1666 2016 2016 CHEVY 4500 CHAMPION

1667 2016 2016 CHEVY 4500 CHAMPION

1668 2016 2016 CHEVY 4500 CHAMPION

1669 2016 2016 CHEVY 4500 CHAMPION

1670 2016 2016 CHEVY 4500 CHAMPION

1671 2016 2016 CHEVY 4500 CHAMPION

1672 2016 2016 CHEVY 4500 CHAMPION

1673 2016 2016 CHEVY 4500 CHAMPION

1674 2016 2016 CHEVY 4500 CHAMPION

1675 2016 2016 CHEVY 4500 CHAMPION

1676 2016 2016 CHEVY 4500 CHAMPION

1677 2016 2016 CHEVY 4500 CHAMPION

1678 2016 2016 CHEVY 4500 CHAMPION

1679 2016 2016 CHEVY 4500 CHAMPION

1680 2016 2016 CHEVY 4500 CHAMPION

1861 2018 2018 Ford Transit
























Table 25: Central Ohio Transit Authority Supervisor Vehicles

Vehicle Number Year, Make and Model Body Style

4011 2009 Chevrolet Malibu Hybrid Sedan



4026 2012 Chevrolet Malibu LS Sedan

4028 2015 Ford Explorer AWD SUV






4034 2012 Honda Civic CNG SDN















6051 2015 Ford Transit Connect XLT Cargo Minivan



Vehicle Number Year, Make and Model Body Style





Table 26: Police Vehicles

Brass Tag Year Make Model Color Type Assigned To

26543 2016 FORD INT UTILITY WHITE M Zone 1 – 6 PCT






26424 2015 FORD TRANSIT 250 WHITE M Zone 1 – 6 PCT












































26988 2017 FORD INT UTILITY WHITE M Zone 1 – MW









27010 2017 FORD INT UTILITY WHITE M Zone 1 – CRT

















27456 2017 FORD TRANSIT 250 WHITE M Zone 4 – EMW





26188 2015 FORD INT UTILITY WHITE M Zone 4 – CWC



27392 2017 FORD INT UTILITY WHITE M Zone 4 -CWC


Table 27: Fire Vehicles

Vehicle Designation Brass Tag Year Make Model

ENGINE 06 28300 2019 SUTPHEN ENGINE

MEDIC 6 27854 2018 HORTON MEDIC

MEDIC 806 27811 2018 FORD MEDIC

EMS12 27475 2017 FORD EXPLORER

BATALLION 2 27470 2017 FORD EXPLORER



BATALLION 3 24933 2013 FORD EXPLORER


LADDER 08 28205 2019 PIERCE AERIAL LADDER







RESCUE 16 25223 2012 SUTPHEN RESCUE



EMS 13 24923 2013 FORD EXPLORER



ISU 19 26779 2015 INTERNATIONAL AIR SUPPLY

X-ISU 19 23063 2008 SPARTAN AIR SUPPLY

RSU 19 25789 2014 INTERNATIONAL RESCUE SUPPORT







ENGINE 29 24336 2011 FERRERA ENGINE


X-BATALLION 02 24932 2013 FORD EXPLORER




X-EMS12 24922 2013 FORD EXPLORER

X-EMS15 24925 2013 FORD EXPLORER

X-ENGINE 01 23095 2009 SPARTAN ENGINE




X-ENGINE 18 17359 2006 SUTPHEN ENGINE












X-LADDER 03 17352 2005 SUTPHEN PLATFORM

X-LADDER 05 17238 2002 AMERICAN LAFRANCE AERIAL LADDER

X-LADDER 08 23052 2008 AMERICAN LEFRANCE AERIAL LADDER


X-LADDER 15 17234 2001 AMERICAN LAFRANCE AERIAL LADDER



X-LADDER 28 23054 2008 AMERICAN LEFRANCE AERIAL LADDER

X-MEDIC 05 24318 2011 HORTON MEDIC















X-RESCUE 02 17364 2005 SUT``PHEN RESCUE

X-RESCUE 04 17363 2005 SUTPHEN RESCUE

X-RESCUE 16 17366 2005 SUTPHEN RESCUE

X-SO 2 24930 2013 FORD EXPLORER

X-EMS 11 TBD

X-MEDIC 14 TBD




Table 28: Department of Public Service Fleet

Equipment No. Year Make Model Description

25837 2014 FORD FOCUS FOCUS S 4DR SEDAN FWD





25845 2014 FORD E350 E350 XL SD PASS VAN 2WD

25955 2014 FORD TRANSIT CONNECT TRANSIT CONNECT XLT PVAN FWD

25888 2014 FORD TRANSIT CONNECT TRANSIT CONNECT XLT PVAN FWD

25783 2014 FORD ESCAPE ESCAPE S 4DR SUV FWD

25784 2014 FORD ESCAPE ESCAPE S 4DR SUV FWD

25785 2014 FORD ESCAPE ESCAPE SE 4DR SUV 4WD




25127 2013 FORD F150 F150 XL 2DR REG CAB 4WD



25134 2012 FORD F350 F350 XL SD STYSIDE REG CAB 4WD





25182 2012 FORD F350 F350 XL SD 2DR REG CAB 4WD

25770 2013 FORD F150 F150 XL 2DR SPR CAB 2WD

25909 2014 FORD F150 F150 XL 2DR CRW CAB 4WD



27302 2017 FORD F350 F350 XL REG CAB 4WD PLOW

27323 2017 FORD F350 F350 XL REG CAB 4WD




27327 2017 FORD F350 F350 XL REG CAB 4WD PLOW




23235 2007 FORD F150 F150 XL STYLESIDE REG CAB 2WD


23295 2008 FORD F250 F250 XL SD STYSIDE CRW CAB 2WD

23580 2008 FORD RANGER RANGER XL 2DR REG CAB 2WD










24588 2012 FORD F350 F350 XL SD STYSIDE CRW CAB DRW




24334 2012 INHCL 7400 7400 WORK STAR SINGLE AXLE DUMP W/ PLOW

24335 2012 INHCL 7400 7400 WORK STAR SINGLE AXLE DUMP W/ PLOW

24594 2012 INHCL 7400 7400 WORK STAR SINGLE AXLE

25825 2014 FRGHT 114SD GALION SA DUMP TRUCK CNG W/PLOW





25475 2013 FORD E150 E150 ECONO CARGO VAN 2WD

25450 2013 FORD TRANSIT CONNECT TRANSIT CONNECT XLT CVAN FWD



26853 2016 FORD TRANSIT TRANSIT 150 CARGO VAN 2WD



24950 2012 FORD EXPEDITION EXPEDITION XL EL 4DR SUV 2WD




25102 2013 FORD ESCAPE ESCAPE SE 4DR SUV FWD


25474 2013 FORD EXPEDITION EXPEDITION XL 4DR SUV 2WD

















24621 2011 FORD F150 F150 2DR REG CAB 2WD


















































25451 2013 Ford Transit






26807 2016 FORD TRANSIT TRANSIT 150 CARGO VAN 2WD


27987 2019 FORD F250 19-FORD F250 XL SUPERCAB 4WD- E85


23502 2008 FORD F350 F350 XL SD STYSIDE SPR CAB 4WD
















25771 2014 FORD F250 F250 XL SD 2DR SPR CAB 2WD SRW


25834 2014 FORD F350 F350 XL STYSIDE SPR CAB 2WD SRW

25842 2014 FORD F350 F350 XL STYSIDE SPR CAB 2WD SRW

25846 2014 FORD F350 F350 XL STYSIDE REG CAB 2WD SRW




27035 2016 FORD F550 DAKOTA ALTEC LIFT AT30-G 4WD

27037 2016 FORD F550 DAKOTA ALTEC LIFT AT30-G 4WD

25581 2013 FORD F550 DAKOTA VERSALIFT AERIAL 29 FT

25582 2013 FORD F550 DAKOTA VERSALIFT AERIAL 29 FT

27505 2018 PTRBL 220 MNTR SIGNTK 220 MAINTAINER SIGN TRUCK




28053 2016 FRGHT M2-106 DAKOTA ALTEC LIFT AT40-P 2WD

21802 2006 GMCXX C8500 TOPKICK C8500 PLATFORM TRUCK

21803 2006 GMCXX C8500 TOPKICK C8500 AERIAL BUCKET TRUCK 54FT

21813 2005 GMCXX C8500 TOPKICK C8500 TOPKICK AERIAL BUCKET TRUCK

27522 2018 PTRBL 220 MNTR SIGNTK 220 MAINTAINER SIGN TRUCK

28195 2019 Ford Escape

28180 2019 Ford F350

28181 2019 Ford F350

28182 2019 Ford F350

28183 2019 Ford F350


26367 2015 FORD TRANSIT CONNECT TRANSIT CONNECT XL CVAN FWD

26630 2016 FORD FOCUS FOCUS SE 4DR SEDAN FWD

26788 2016 FORD TRANSIT TRANSIT 350 XL CVAN 2WD



27715 2018 NISSN LEAF 18-NISSAN-LEAF-4DR-SEDAN-EV












28437 2020 Toyota Prius




28456 2019 Kia Niro

28457 2019 Kia Niro




27703 2018 Nissan Leaf


Table 29: Franklin County Engineers Office Fleet

ID Year Make Model VIN

987 2018 International Tandem axle plow/dump truck 1HTWHTAT8JH438722

992 2012 International Tandem axle plow/dump truck 1HTWHAZT5CH043621

985 2018 International Tandem axle plow/dump truck

257 2016 International Single axle plow/dump truck

220 2015 International Single axle plow/dump truck

828 1989 International Lowboy

M61 2018 Ford F-550 1FDUF5GTXHEB30570

xE61 2011 Pierce Contender 4P1CT02M94A003717

E61 2012 Pierce Velocity 4P1CVO1D6CA013048

25-Medic132 2016 Ford/Horton F-550 1FDUF5GT7GEC62507

25-Engine132 2019 Pierce Velocity 4P1BAAFF9LA020843


Documents

Demonstration Site Map and Installation Schedule · 1/24/2020 · Demonstration Site Map and Installation Schedule – Final Report | Smart Columbus Program | iii Abstract The City