System Requirements for Smart Mobility Hubs for the Smart … · 2019-06-26 · Smart Mobility Hubs SyRS for Smart Columbus Demonstration Program – Draft Report | 1 122 Chapter

Smart Columbus 1

System Requirements 2

for Smart Mobility Hubs 3

for the Smart Columbus 4

Demonstration Program 5

www.its.dot.gov/index.htm 6

Draft Report – October 4, 2018 7

8

Source: City of Columbus – November 2015 9

10

Produced by City of Columbus 11

U.S. Department of Transportation 12

Office of the Assistant Secretary for Research and Technology 13

Notice 14

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

Transportation in the interest of information exchange. The United States Government 16

assumes no liability for its contents or use thereof. 17

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

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

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

Acknowledgement of Support 21

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

Transportation under Agreement No. DTFH6116H00013. 23

Disclaimer 24

Any opinions, findings, and conclusions or recommendations expressed in this 25

publication are those of the Author(s) and do not necessarily reflect the view of 26

the U.S. Department of Transportation. 27

Technical Report Documentation Page

1. Report No.

2. Government Accession No.

3. Recipient’s Catalog No.

4. Title and Subtitle

Smart Columbus Systems Requirements for Smart Mobility Hubs for Smart Columbus Demonstration Program

5. Report Date

September 25, 2018

6. Performing Organization Code

7. Author(s)

Andy Wolpert (City of Columbus), Alex Kavanagh (HNTB), Matt Graf (HNTB), Robert James (HNTB), Jeffrey Kupko (Michael Baker)

8. Performing Organization Report No.

9. Performing Organization Name and Address

City of Columbus 90 West Broad Street Columbus, OH 43215-9004

10. Work Unit No. (TRAIS)

11. Contract or Grant No.

DTFH6116H00013

12. Sponsoring Agency Name and Address

U.S. Department of Transportation (USDOT) Federal Highway Administration (FHWA) Office of Acquisition and Grants Management 1200 New Jersey Avenue, SE Mail Drop: E62-204 Washington, DC 20590

13. Type of Report and Period Covered

Draft Report

14. Sponsoring Agency Code

HOIT-1

15. Supplementary Notes

Kate Hartman, AOR; Sarah Tarpgarrd, AO

16. Abstract

The Smart City Demonstration Program is intended to improve access through expanded mobility options in major job centers, enhance visitor experience by better connecting visitors to transportation options, stimulate regional economic prosperity and compete globally through smart logistics, better connect Columbus residents to safe, reliable transportation that can be accessed by all, and support the efficient movement of people and goods through environmentally sustainable practices.

This System Requirement Specification (SyRS) serves as the second in a series of engineering documents intended to describe the Smart Mobility Hubs (HUBS), building upon the Concept of Operations (ConOps) Document. The SyRS describes a set of requirements that, when realized, will satisfy the expressed needs of the HUBS. This document includes the identification, organization, presentation, and modification of the requirements for the HUBS. This SyRS addresses conditions for incorporating operational concepts, design constraints, and design configuration requirements as well as the necessary characteristics and qualities of individual requirements and the set of all requirements.

17. Keywords

Smart City, system requirements, HUBS, Smart Mobility Hubs

18. Distribution Statement

19. Security Classif. (of this report)

Unclassified

20. Security Classif. (of this page)

Unclassified

21. No. of Pages

136

22. Price

N/A

Form DOT F 1700.7 (8-72) Reproduction of completed page authorized

28

U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology

Intelligent Transportation Systems Joint Program Office

Smart Mobility Hubs SyRS for Smart Columbus Demonstration Program – Draft Report | i

Table of Contents 29

Chapter 1. Introduction ....................................................................................................................... 1 30

1.1 Document Purpose .......................................................................................................................................... 1 31

1.2 Project Scope ................................................................................................................................................... 1 32

1.3 Requirements Process .................................................................................................................................... 4 33

1.4 References ....................................................................................................................................................... 5 34

Chapter 2. System Description .......................................................................................................... 7 35

2.1 System Context................................................................................................................................................ 7 36

2.1.1. Interactive Kiosk .................................................................................................................................. 7 37

2.1.2. Wi-Fi ..................................................................................................................................................... 7 38

2.1.3. Park and Ride ...................................................................................................................................... 7 39

2.1.4. USB Charging...................................................................................................................................... 7 40

2.1.5. Emergency Call Button ....................................................................................................................... 7 41

2.1.6. Interactive Voice Response ................................................................................................................ 8 42

2.1.7. Real-Time Data Display ...................................................................................................................... 8 43

2.1.8. Personal Wireless Device ................................................................................................................... 8 44

2.1.9. Designated Passenger Pickup/Drop Off Zones ................................................................................ 8 45

2.1.10. Dockless Device Parking Zones ........................................................................................................ 8 46

2.2 System Modes and States ............................................................................................................................ 12 47

2.3 Major System Characteristics ....................................................................................................................... 13 48

2.3.1. System Capabilities ........................................................................................................................... 13 49

2.3.2. System Conditions ............................................................................................................................ 13 50

2.4 User Characteristics ...................................................................................................................................... 14 51

2.5 Assumptions and Dependencies .................................................................................................................. 15 52

2.6 System Constraints ....................................................................................................................................... 16 53

2.7 Operational Scenarios ................................................................................................................................... 16 54

Chapter 3. System Requirements .................................................................................................... 17 55

3.1 Functional Requirements .............................................................................................................................. 18 56

3.2 Performance Requirements .......................................................................................................................... 28 57

3.3 Interface Requirements ................................................................................................................................. 30 58

3.3.1. External Interface Requirements ..................................................................................................... 31 59

3.4 Data Requirements ........................................................................................................................................ 33 60

3.5 Security Requirements .................................................................................................................................. 36 61

3.6 Non-Functional Requirements ...................................................................................................................... 39 62

Table of Contents

U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office

ii | Smart Mobility Hubs SyRS for Smart Columbus Demonstration Program – Draft Report

3.6.1. Physical Requirements ..................................................................................................................... 39 63

3.6.2. Availability and Recoverability Requirements ................................................................................. 43 64

3.6.3. Maintainability Requirements ........................................................................................................... 45 65

3.6.4. Storage and Transport Requirements ............................................................................................. 46 66

3.6.5. Disposal Requirements ..................................................................................................................... 47 67

3.7 Enabling Requirements ................................................................................................................................. 48 68

3.7.1. Information Management Requirements ......................................................................................... 50 69

3.7.2. Life-Cycle Sustainability Requirements ........................................................................................... 50 70

3.8 Policy and Regulation Requirements ........................................................................................................... 52 71

Chapter 4. Engineering Principles ................................................................................................... 57 72

4.1 Methods of Verification .................................................................................................................................. 57 73

4.2 Reference Architecture .................................................................................................................................. 57 74

Appendix A. Document Terminology and Conventions ............................................................... 59 75

A.1 Reference Conventions ................................................................................................................................. 59 76

Appendix B. Requirements by System Functional Groups ......................................................... 63 77

Appendix C. Relationship Matrices ................................................................................................. 95 78

Appendix D. Acronyms and Definitions ....................................................................................... 133 79

Appendix E. Glossary ..................................................................................................................... 135 80

81

Table of Contents



Smart Mobility Hubs SyRS for Smart Columbus Demonstration Program – Draft Report | iii

List of Tables 82

Table 1: References ...................................................................................................................................... 5 83

Table 2: System Functional Groups ............................................................................................................ 10 84

Table 3: Expected Interfaces ....................................................................................................................... 11 85

Table 4: New HUBS System Modes of Operation ...................................................................................... 12 86

Table 5: Smart Mobility Hubs Stakeholders and User Classes ................................................................... 14 87

Table 6: Assumptions and Dependencies ................................................................................................... 15 88

Table 7: System Constraints ....................................................................................................................... 16 89

Table 8: List of Requirement Types ............................................................................................................. 17 90

Table 9: Functional Requirements .............................................................................................................. 18 91

Table 10: Performance Requirements ........................................................................................................ 28 92

Table 11: External Interface Requirements by Functional Group ............................................................... 31 93

Table 12: Data Requirements ..................................................................................................................... 34 94

Table 13: Security Requirements ................................................................................................................ 36 95

Table 14: Physical Requirements ................................................................................................................ 40 96

Table 15: Availability and Recovery Requirements ..................................................................................... 43 97

Table 16: Maintainability Requirements ...................................................................................................... 45 98

Table 17: Storage and Transport Requirements ......................................................................................... 46 99

Table 18: Disposal Requirements ............................................................................................................... 47 100

Table 19: Enabling Requirements ............................................................................................................... 48 101

Table 19: Information Management Requirements ..................................................................................... 50 102

Table 20: Life-Cycle Sustainability Requirements ....................................................................................... 51 103

Table 21: Policy and Regulation Requirements .......................................................................................... 53 104

Table 22: Methods of Verification ................................................................................................................ 57 105

Table 23: Requirements Numbering Convention ........................................................................................ 59 106

Table 24: Requirements Organized by Functional Groups ......................................................................... 63 107

Table 25: User Needs Mapped to Requirements ........................................................................................ 95 108

Table 26: Constraints Needs Mapped to Requirements ............................................................................. 99 109

Table 27: Interfaces Mapped to Requirements ........................................................................................ 101 110

Table 28: Related Requirements .............................................................................................................. 103 111

Table 29: Established Relations per Requirement .................................................................................. 108 112

Table 30: Acronym List .............................................................................................................................. 133 113

Table 31: Glossary .................................................................................................................................... 135 114

115

Table of Contents


iv | Smart Mobility Hubs SyRS for Smart Columbus Demonstration Program – Draft Report

List of Figures 116

Figure 1: Cleveland Avenue Corridor ............................................................................................................ 3 117

Figure 2: HUBS Stakeholder Requirements Definition Process ................................................................... 4 118

Figure 3: Smart Mobility Hubs Context Diagram........................................................................................... 9 119

Figure 4: Monolithic Versus Microservice Reference Architecture .............................................................. 58 120

121



Smart Mobility Hubs SyRS for Smart Columbus Demonstration Program – Draft Report | 1

Chapter 1. Introduction 122

This Systems Requirements Specification (SyRS) is intended to communicate the requirements of the 123

Smart Columbus Smart Mobility Hubs (HUBS) project to the technical community who will specify and 124

build the system. The SyRS is a “black-box” description of what the HUBS must do, but not how it will do 125

it. The document contains descriptions of inputs, outputs, and required relationships between inputs and 126

outputs. 127

1.1 Document Purpose 128

This System Requirement Specification (SyRS) serves as the second in a series of engineering 129

documents intended to describe the HUBS, building upon the Concept of Operations (ConOps) 130

Document. The SyRS describes a set of requirements that, when realized, will satisfy the expressed 131

needs on the HUBS. This document includes the identification, organization, presentation, and 132

modification of the requirements for the HUBS. These requirements are derived from the user needs, 133

constraints and interfaces that the HUBS facilities are expected to implement. This SyRS addresses 134

conditions for incorporating operational concepts, design constraints, and design configuration 135

requirements as well as the necessary characteristics and qualities of individual requirements and the set 136

of all requirements. 137

This document was developed based on 1233-1998 Institute of Electrical and Electronics Engineers 138

(IEEE) Guidance for Developing System Requirements Specifications and contains the following 139

sections: 140

Chapter 1. Introduction provides an overview of the HUBS project and key elements that guide 141

the development of this SyRS document, including an overview of the project, the stakeholders, 142

requirements development process, and referenced materials. 143

Chapter 2. System Description focuses on describing and extending the system concepts 144

established in the Concept of Operations, including any system capabilities, conditions, 145

constraints, and decomposing the system into its Functional Groups (FGs) for establishing 146

requirements. 147

Chapter 3. System Requirements contains the requirements for each FG that make up the 148

system. 149

Chapter 4. Engineering Principles provides a description of engineering principles applied to 150

the system and requirements definition process. 151

1.2 Project Scope 152

In 2016, the U.S. Department of Transportation (USDOT) awarded $40 million to the City of Columbus, 153

Ohio, as the winner of the Smart City Challenge. With this funding, Columbus intends to address the most 154

Chapter 1. Introduction


2 | Smart Mobility Hubs SyRS for Smart Columbus Demonstration Program – Draft Report

pressing community-centric transportation problems by integrating an ecosystem of advanced and 155

innovative technologies, applications, and services to bridge the sociotechnical gap and meet the needs 156

of residents of all ages and abilities. In conjunction with the Smart City Challenge, Columbus was also 157

awarded a $10 million grant from Paul G. Allen Philanthropies to accelerate the transition to an electrified, 158

low-emissions transportation system. 159

With the award, the city established a strategic Smart Columbus program with the following vision and 160

mission: 161

Smart Columbus Vision: Empower residents to live their best lives through responsive, 162

innovative, and safe mobility solutions 163

Smart Columbus Mission: Demonstrate how Intelligent Transportation Systems (ITS) and 164

equitable access to transportation can have positive impacts of every day challenges faced by 165

cities. 166

To enable these new capabilities, the Smart Columbus program is organized into three focus areas 167

addressing unique User Needs: enabling technologies, emerging technologies, and enhanced human 168

services. Deployment of the HUBS primarily addresses needs within the enhanced human services 169

program focus area. 170

The HUBS project is one of the nine projects in the Smart Columbus program and is considered the 171

future of consolidated transportation centers. The purpose of the HUBS project is to deploy transportation 172

facilities that provide travelers with consolidated transportation amenities such as interactive kiosks, 173

provide access to comprehensive trip-planning tools [via Multi-Modal Trip Planning Application 174

(MMTPA)/Common Payment System (CPS)] and real-time transportation information, and are designed to 175

accommodate multiple modes of transportation from a single location including bike-share, car-share and 176

mobility providers. These services are particularly useful in the completion of first mile/last mile (FMLM) 177

and multimodal trip options. Benefits of a HUBS system include enhanced integration and connectivity of 178

the transportation system across and between modes, improved efficiency of the surface transportation 179

system, and increased accessibility and mobility of travelers. 180

The geographic scope of the proposed HUBS project deployment includes the Cleveland Avenue corridor 181

coinciding with COTA’s Bus Rapid Transit (CMAX) service and the Easton commercial district, providing 182

those in the Linden area better access to jobs and services in the Easton and Downtown Columbus 183

Commercial districts. 184

Six initial HUBS deployment locations, shown in Figure 1: Cleveland Avenue Corridor were selected 185

based on user feedback and surveys: 186

St. Stephen’s Community House 187

Easton Transit Center 188

Columbus State Community College 189

Northern Lights Park and Ride 190

Easton Transit Center 191

Metro Library – Linden Branch 192





193

Source: City of Columbus 194

Figure 1: Cleveland Avenue Corridor 195




1.3 Requirements Process 196

The requirements established for this project will govern the HUBS system’s development cycle and are 197

an essential factor in further defining and clarifying the scope and feasibility of development for the 198

system. This process will also provide the basis for the technical description of deliverables in the form of 199

a system‐level specification and defined interfaces at the system boundaries. Figure 2: HUBS 200

Stakeholder Requirements Definition Process provides a high-level view of the project’s stakeholder 201

requirements definition process. 202

203


Figure 2: HUBS Stakeholder Requirements Definition Process 205

USDOT and City of Columbus Laws and Regulations

Smart Columbus Project Procedures, Standards and Directives

City Agreements

ITS Industry Standards

Concept of Operations Operational Constraints and Policies

CONTROLS

Smart Columbus

Project Management

Plan

System of Systems

Documentation

HUBS Concept of

Operations

Stakeholder Needs

Project Performance

Plan

Constraints

INPUTS

Evaluate stakeholder

needs

Elicit stakeholder

requirements

Establish and define

system requirements

Evaluate distributed

SoS architecture and

feasibility of system

Map requirements to

User Needs in RTM

tool for development

ACTIVITIES

Stakeholder

requirements

Verification Plan

Initial RTVM

System feasibility

findings

Concept of production

with agreement on

system boundaries

MOE needs and data

Validation criteria

OUTPUTS

ITS and Technology Standards

Smart Columbus Program Communications Plan

ENABLERS





Once the project’s requirements are established they will be formally placed under configuration control 206

using Helix ALM software developed by Perforce. This software will enable the program to centrally 207

capture, relate, reuse and decompose requirements across projects and map them to User Needs. The 208

tools enable the City and project leads to perform reviews, view the approval status of requirements, and 209

track and manage changes throughout the application life cycle. 210

1.4 References 211

Table 1: References contains documents, literature, and working group sessions used to gather input for 212

this document. 213

Table 1: References 214

Document

Number Title Revision

Publication

Date

FHWA-JPO-

17-518

Smart Columbus Systems Engineering Management

Plan (SEMP) for Smart Columbus Demonstration

Program

https://rosap.ntl.bts.gov/view/dot/34764

– January 16,

2018

– Beyond Traffic: The Smart City Challenge – Phase 2

– Volume 1: Technical Application

https://www.columbus.gov/WorkArea/DownloadAsse

t.aspx?id=2147487896

– May 24,

2016

1233-1998 IEEE Guidance for Developing System

Requirements Specifications

– 1998

INCOSE‐TP‐

2003‐002‐

03.2.2

INCOSE Systems Engineering Handbook 3.2.2 2011

– Systems Engineering Guidebook for Intelligent

Transportation Systems

3.0 2009

FHWA-JPO-

17-523

Concept of Operations for the Multimodal Trip

Planning Application/Common Payment System for

the Smart Columbus Demonstration Program

2.0 August 10,

2018

N/A Smart Columbus Operating System

https://www.smartcolumbusos.com N/A N/A


216

217

https://rosap.ntl.bts.gov/view/dot/34764

https://www.columbus.gov/WorkArea/DownloadAsset.aspx?id=2147487896

https://www.columbus.gov/WorkArea/DownloadAsset.aspx?id=2147487896

https://www.smartcolumbusos.com/




218

219




Chapter 2. System Description 220

2.1 System Context 221

The HUBS Facility is the physical site that consolidates the amenities of the HUBS System, which include 222

an interactive kiosk, real-time information displays, pick-up/drop-off areas, bikeshare docks, bike racks, 223

and parking spaces for mobility providers, park and ride, and carshares. Individual HUBS facilities will 224

vary in size, configuration and available services. The following are descriptions of components that may 225

be available at a HUBS facility: 226

2.1.1. Interactive Kiosk 227

Traveler interactive kiosks will be installed on free standing pylons at HUBS facilities. These kiosks will 228

display real-time travel related information and provide an embedded touch screen display to serve as a 229

direct interface between travelers and the MMTPA/CPS, providing the traveler the ability to plan, schedule 230

and pay for trips using multimodal options available at the HUBS facility, along with additional information 231

and instruction such as directing the traveler to a Transportation Network Company (TNC) pickup 232

location. 233

2.1.2. Wi-Fi 234

HUBS facilities will be equipped with public Wi-Fi that will allow a traveler to access the MMTPA/CPS and 235

other transportation information on his or her personal wireless device. 236

2.1.3. Park and Ride 237

Designated parking spaces will be available at select HUBS locations and allow a traveler the option to 238

complete a segment of his or her trip using a personal vehicle and parking at HUBS facility, where he or 239

she can utilize the HUBS amenities to continue his or her trip using alternate modes of transportation. 240

2.1.4. USB Charging 241

Powered USB ports will be available at the HUBS location to allow travelers to recharge personal 242

electronic devices like cellular phones, tablets, and other wireless devices while planning a trip or waiting 243

for transportation services. 244

2.1.5. Emergency Call Button 245

Kiosks will include an emergency call button that, when activated, will send notification of the help request 246

directly to the 911 emergency call center operated by the City of Columbus and initiate an audio 247

connection between the distressed traveler and an operator at the emergency call center. The emergency 248

Chapter 2. System Description



call button will be a physical button which may be a located on the interactive kiosk pylon or 249

independently at the HUBS facility. 250

2.1.6. Interactive Voice Response 251

Kiosks will include capability to connect to an Interactive Voice Response (IVR) system that will allow 252

travelers to interact with the MMTPA and trip planning tools through use of voice commands. The IVR 253

system is a function of the MMTPA project and where it is described in greater detail. 254

2.1.7. Real-Time Data Display 255

Real-Time Data Displays will be present at HUBS facilities and will post current transit information, public 256

notifications and other information on kiosk displays and/or on other display monitors at some existing 257

facilities. 258

2.1.8. Personal Wireless Device 259

A personal wireless device such as a cell phone or tablet may be used at HUBS facilities to access the 260

MMTPA via public Wi-Fi or through a personal data plan. Wi-Fi access may include the development of a 261

HUBS home webpage that displays or provides links to real-time information that will be displayed on 262

kiosk screens at the HUBS facility. Additionally, trip confirmation codes and other trip information may be 263

sent to the personal wireless device upon traveler request and used to gain access to TNC’s or to unlock 264

bikes at bike-sharing docks. 265

2.1.9. Designated Passenger Pickup/Drop Off Zones 266

Loading zones will be available at HUBS locations in the form of pull off lanes and/or parking spaces 267

located away from travel lanes that will allow safe transfer of passengers between modes of 268

transportation. These zones will primarily be used for mobility providers and will be clearly marked with 269

signage and pavement markings. 270

2.1.10. Dockless Device Parking Zones 271

Designated zones will be established for parking dockless devices such as scooters, electric bikes, etc. to 272

prevent interference between this rapidly increasing mode of transportation and other services offered at 273

the HUBS facilities. 274

275





Figure 3: Smart Mobility Hubs Context Diagram shows a context diagram for the new HUBS system. 276

277


Figure 3: Smart Mobility Hubs Context Diagram 279

280




Table 2: System Functional Groups provides FGs resulting from the proposed system diagram 281

deconstructed into its major components/functionality. 282

Table 2: System Functional Groups 283

Ref No. Functional Group High-Level Functionality

CTP Comprehensive Trip

Planning

CTP features will be made available to travelers at

HUBS by providing access to the MMTPA/CPS

functions, which include providing the traveler the

ability to plan, schedule and pay for trips using

multimodal options available at the HUBS facility.

ECB Emergency Call Button When activated, the ECB will send notification of the

help request directly to the 911 emergency call

center operated by the City of Columbus and initiate

an audio connection between the distressed traveler

and an operator at the emergency call center.

DOCKLESS Dockless Device Zone Designated zones will be established for parking

dockless devices such as scooters, electric bikes,

etc.

KIOSK Interactive Kiosk KIOSKS will display real-time transit related

information and provide an embedded touch screen

display to serve as a direct interface between

travelers and the MMTPA/CPS, providing the traveler

the ability to plan, schedule and pay for trips using

multimodal options available at the HUBS facility,

along with additional information and instruction such

as directing the traveler to a Transportation Network

Company (TNC) pickup location.

PARKRD Park and Ride PARKRD will designate physical space at a HUBS

facility for park and ride vehicle parking spaces.

RACKS Bike Racks RACKS will provide physical bike racks at a HUBS

facility for travelers to park and secure privately

owned bikes.

SHAREBIKE Bike-sharing SHAREBIKE will install docking stations for bike-

share operations at the HUBS facility

SHARECAR Car-sharing SHARECAR will designate physical space at a

HUBS facility for car-sharing vehicle parking spaces.

SHARERIDE Ride-sharing SHARERIDE will designate physical space at a

HUBS facility for passenger pickup and drop off by

TNCs.





Ref No. Functional Group High-Level Functionality

USB USB Charging Powered USB ports will be available at the HUBS

facility to allow travelers to recharge personal

electronic devices like cellular phones, tablets, and

other wireless devices while planning a trip or waiting

for transportation services.

WIFI Wi-Fi Enabled HUBS facilities will be equipped with public Wi-Fi that

will allow a traveler to access the MMTPA/CPS and

other transportation information using a personal

wireless device.


Table 3: Expected Interfaces summarizes the interfaces, facilities, communications and messages used 285

in the system. The reader should reference these figures and table throughout this section to foster a 286

better understanding of the system concept. 287

Table 3: Expected Interfaces 288

Interface ID

(FROM HELIX)

Source

Element

Destination

Element Data Flow

Communication

Media

HUBS-IX2431-v01 IK Touch

Screen

MMTPA/CPS

Application

Request for trip

planning services

(car-share, ride-share,

bike-share,

paratransit, account

information and

payment request data

Application

Programming

Interface,

Secured Internet

Browser over Wi-Fi

HUBS-IX2432-v01 MMTPA/CPS

Application

IK Touch

Screen

Real-time trip planning

data associated with

mode of transport

(public transportation,

ride-sharing services,

bike-sharing, etc.),

payment

authorization, and

confirmations

Application

Programming

Interface,

Secured Internet

Browser over Wi-Fi

HUBS-IX2433-v01 Emergency

Call Button

Columbus

Emergency

Call Center

Request for

emergency services,

voice and location

data

Telephone




Interface ID

(FROM HELIX)

Source

Element

Destination

Element Data Flow

Communication

Media

HUBS-IX2434-v01 Columbus

Emergency

Call Center

Emergency

Call Button

Emergency response

service, notifications,

and voice data

Telephone

HUBS-IX2435-v01 IK System Personal

Wireless

Device

Wireless Internet

Access for IK system

and public use

Wireless Network

Interface Card

HUBS-IX2436-v01 Personal

Wireless

Device

MMTPA/CPS

Application

Request for trip

planning services

(car-share, ride-share,

bike-share,

paratransit, account

information and

payment request data)

Wireless Ethernet

HUBS-IX2437-v01 IK System USB

Charging

Power only (no signal)

for electronic device

charging

Universal Serial Bus

(USB)

HUBS-IX2438-v01 IK Touch

Screen

IVR System Request for

information

accessibility, voice

data

IVR

HUBS-IX2439-v01 IVR System IK Touch

Screen

Information delivery

via voice data

IVR


2.2 System Modes and States 290

Table 4: New HUBS System Modes of Operation defines the modes of operations for the new HUBS 291

system. 292

Table 4: New HUBS System Modes of Operation 293

Mode Definition

Normal Operation Normal operation mode occurs while interactive kiosks are online,

Wi-Fi is fully accessible, and users can utilize the MMTPA/CPS to

evaluate real time transportation conditions throughout the corridor to

make decisions on modal choices. Buses, TNCs, cars (car-share),

and bikes are readily available to user with minimal delay.





Mode Definition

Degraded Conditions Degraded mode refers to a localized or systemic event that results in

diminished access to a component of the MMTPA/CPS resulting in

trip disruption to users; or when appropriate travel options are not

readily available to users within a reasonable amount of time; or

when full corridor travel is not possible or permitted due to system

unrelated event such as a traffic incident or other emergency event.

Failure Conditions Failure mode results in the complete systemic disruption of the user’s

ability to access the MMTPA/CPS or transportation modes. This may

be due to a network or other system equipment problem, or physical

lack of bus, TNC, bike service, etc.

Maintenance Maintenance mode occurs when the system is operating in Backup

mode or Failure mode to restore, repair, or replace system

components. These are planned events and should occur during off

peak hours to minimally impact users, and proper notification should

be given to potential users in advance of the event when practical.


2.3 Major System Characteristics 295

2.3.1. System Capabilities 296

The HUBS system will be created by providing physical amenities and network connectivity that will give 297

travelers more transportation options, real-time transportation information, and improved access to trip 298

planning services offered through use of the MMTPA/CPS. This system will improve accessibility to 299

first/last mile trip options and is expected to increase ridership of the CMAX BRT service that is currently 300

operated by COTA within the HUBS project limits. Trip data involving HUBS features will be collected and 301

used by City and COTA officials to improve transportation planning decision making and services. 302

2.3.2. System Conditions 303

The HUBS is generally expected to perform under most conditions, providing travelers with area transportation 304

information and access to trip planning tools and modes of transportation. Situations that may result in 305

degraded or no performance include: 306

Loss of Communications – The loss of network connectivity at the Interactive Kiosk will result in 307

failure to use trip planning tools like MMTPA/CPS. Travelers would be limited to using personal 308

wireless devices and data plans to use these features. Trip data will also be unavailable to the 309

OS during a communications loss event. 310

Severe weather events or incidents impacting roadway network in vicinity of HUBS – 311

Temporary unavailability of some modes of transportation may result if transit, vehicles and/or 312

bikes are not able to physically access the HUBS facility or experience significant delays traveling 313

to the site. 314




2.4 User Characteristics 315

This section defines the stakeholders, user classes, and their roles and responsibilities for the HUBS 316

system. Stakeholders refers to an individual or organization affected by the activities, inputs and outputs 317

of the system being developed. They may have a direct or indirect interest in the system and their level of 318

participation may vary. This includes public agencies, private organizations or the traveling public (end 319

users) with a vested interest, or a "stake" in one or more aspect of the HUBS as identified in Table 5: 320

Smart Mobility Hubs Stakeholders and User Classes. User Classes are based on the perception of 321

the system and the needs identified. Some key personnel may serve in multiple roles based on the user 322

needs and functions. 323

Table 5: Smart Mobility Hubs Stakeholders and User Classes 324

User Classes Description

City of Columbus The City, through Smart Columbus, will provide the project deployment

functions necessary to establish the operational system and provide testing

and verification. The City also will maintain the Operating System, the

MMTPA, and data dashboards to analyze the use of the HUBS.

COTA As the public transit provider in central Ohio and Columbus, Central Ohio

Transit Authority (COTA) is central to the design and implementation of the

HUBS. It is envisioned that COTA will serve as the backbone of the

transportation system, tying into the HUBS facilities and linking travelers to

multimodal options for FMLM connections.

Third-Party Agency Typically, a public or private transportation provider or planning agency

utilizing data from the Smart Columbus project to improve the efficiency and

accuracy of their services.

Travelers Travelers are end users that utilize the features of HUBS to begin, pass

through, or complete their trip. Travelers interact with HUBS in several ways:

They use the physical HUBS facility to transfer or connect between modes

of transportation; for example, a user may transfer from a ride-sharing

service to a COTA fixed route bus, or from COTA fixed route bus to a bike-

sharing service.

They use the kiosk terminal or Wi-Fi connectivity provided at the HUBS

facility to interact with the MMTPA/CPS to plan, reserve, and pay for one or

more components required to complete their trip.

They activate the emergency call button feature for emergency services

during an incident.





User Classes Description

Mobility Providers Mobility Providers are private businesses, nonprofits, and quasi-governmental

agencies that offer one or more modes of transportation for use by travelers in

exchange for payment. These include car-sharing services, ride-sharing

services, ride-hailing companies, bike-sharing services and private car/van

pools from ride matching services. A bike-sharing service may maintain a

physical space at the HUBS where travelers can pick up or drop off a bicycle

when transitioning to or from a COTA bus.

Property

Owners/Stakeholders

Agencies partnering with the City to permit the deployment of a HUBS facility

within the limits of their property. Agreements between these agencies and the

City will be made to address operating and maintenance expectations of the

HUBS facility and equipment.

City of Columbus

Emergency Dispatch

Center

The Emergency Dispatch Center will interact with Travelers and other users of

the kiosks to intake emergency call information and deploy the appropriate

resources to respond to the emergency.


2.5 Assumptions and Dependencies 326

Table 6: Assumptions and Dependencies lists the known assumptions and dependencies that 327

represent a risk to the HUBS project and can affect the ability to meet the desired functionality, maintain 328

the project schedule or meet performance goals. 329

Table 6: Assumptions and Dependencies 330

Assumption Corresponding Risk Dependency Degree

Stakeholder/City

agreements will be in

place prior to HUBS

deployment

Installation of

equipment on

stakeholder property

cannot begin unless

agreements are

executed

All physical HUBS

improvements at

respective stakeholder

site

Critical


332




2.6 System Constraints 333

Table 7: System Constraints defines the system constraints in the new HUBS system. 334

Table 7: System Constraints 335

Constraint ID Constraint

HUBS-CN001-v01 COTA needs mobility providers to respect existing infrastructure and

agreements at their facilities.

HUBS-CN002-v01 Effective distance and capabilities of existing Wi-Fi coverage.

HUBS-CN003-v01 City and Stakeholders are evaluating the types of materials, specifically

advertisements, that may be permittable to post on Kiosk screens.

HUBS-CN004-v01 Physical right of way and existing infrastructure may limit the features that a

specific HUBS facility can offer.


2.7 Operational Scenarios 337

Chapter 6 of the Concept of Operations for the Smart Mobility Hubs Project for the Smart Columbus 338

Demonstration Program, captures and documents the operational scenarios. 339

340




Chapter 3. System Requirements 341

This section of the document lists the identified requirements for the EPM project. The requirements are 342

organized first by requirement type, then by system and services (i.e. functional requirements (FR) for 343

functional group 1, then FR for functional group 2, etc.). Each requirement type has a requirement 344

identifier (see Appendix A) along with its description, a reference number that identifies traceability to 345

user needs, user scenarios and/or policies and constraints. Each requirement also has a verification 346

method (see Section 4.1 Methods of Verification for method definitions). 347

Table 8: List of Requirement Types describes the classifications of requirement types in this document. 348

Table 8: List of Requirement Types 349

Type Description

Functional (FN) FN Requirements specify actionable and qualitative behaviors (e.g.

functions, tasks) of the core system of interest.

Performance (PR) PRs specify quantifiable characteristics of operations that define the

extent, or how well, and under what conditions a function or task is to be

performed (e.g. rates, velocities).

Interfaces (IF) IF Requirements define how the system will interact, communicate, or

exchange data with external systems (External IF) and how core system

elements interact with other parts of the system (Internal IF).

Data (DR) DRs define the data collected, transformed, and stored from various

sources as well as identifies new data that is expected to be generated.

Security (SR) SRs specify what is necessary to protect the integrity and operability of

the system, its microservices, connections, and data. This includes

physical security as well as cyber prevention, detection, identification,

response and recovery requirements.

Non-Functional (NF) NF Requirements define the characteristics of the overall operation of

the system.

Physical (PY) PY Requirements specify the construction, durability, adaptability and

environmental characteristics of the system.

Availability and Recovery

(AR)

AR Requirements define the times of day, days of year, and overall

percentage the system can be used, when it will not be available for use,

and recovery point and time objectives.

Maintainability (MT) MT Requirements specify the level of effort required to locate and

correct an error during operation

Chapter 3. System Requirements



Type Description

Storage and Transport (ST) ST Requirements specify the physical location and environment for the

system, including designated storage facility, installation site, repair

facility, requirements for transporting equipment, etc.

Disposal (DP) DP Requirements specify the items related to the disposal of

project/system components, due to either failure replacements, removal,

end-of-life upgrade, or retirement

Enabling (EN) EN Requirements specify details concerning the management of

information as well as the production of the system and its life cycle

sustainment.

Information Management

(IM)

IM Requirements specify the acquisition, management, and

ownership of information from one or more sources, the custodianship

and the distribution of that information to those who need it

Life-Cycle (LC) LC Sustainability Requirements define what items the project or system

will review, measure, and analyze as part of its commitment to quality

during the life cycle of the system including development, integration,

verification, validation and training

Policy and Regulation (RG) RG Requirements specify relevant and applicable organizational policies

or regulations that affect the development, operation or performance of

the system (e.g. Information technology (IT) and labor policies, reports

to regulatory agencies, health or safety criteria, etc.). This section also

includes new policy and regulation imposed to realize the system.


3.1 Functional Requirements 351

The requirements in Table 9: Functional Requirements are organized by the functional groups and are 352

related to the user needs the HUBS ConOps identified. 353

Table 9: Functional Requirements 354

ReqID Description References

Verification

Method

HUBS-

FN2290-

V01

The bike sharing system shall have a

docking station for the bikes.

HUBS-UN005-v01

HUBS-UN011-v01

HUBS-CN2427-v01

Inspection






Verification

Method

HUBS-

FN2291-

V01

The docking station shall accept a

code generated (through verified

payment) for unlocking the bikes.

HUBS-UN011-v01 Demonstration

HUBS-

FN2292-

V01

The docking station shall allow the

user to enter the operational status of

the just docked bike. The operational

status could include the need for

preventative and repair maintenance.


HUBS-

FN2293-

V01

The docking station shall be solar

powered.

HUBS-UN011-v01 Inspection

HUBS-

FN2294-

V01

The docking station shall collect the

number of bikes docked.

HUBS-UN011-v01

HUBS-UN001-v01

Demonstration

HUBS-

FN2295-

V01

The docking station shall track the %

solar charge complete

HUBS-UN001-v01

HUBS-UN011-v01

Demonstration

HUBS-

FN2296-

V01

The docking station shall track the date

and time when a bike in unlocked.

HUBS-UN001-v01

HUBS-UN011-v01

Test

HUBS-

FN2297-

V01

The docking station shall track the date

and time when a bike is locked.

HUBS-UN001-v01

HUBS-UN011-v01

Test





Verification

Method

HUBS-

FN2298-

V01

The docking station shall track the

operational status of the docking

station.

HUBS-UN001-v01

HUBS-UN011-v01

Demonstration

HUBS-

FN2310-

V01

The car share system shall have

dedicated parking lot for car share

vehicles at the HUBS facility.

HUBS-UN005-v01

HUBS-CN2424-v01

HUBS-CN2427-v01

Inspection

HUBS-

FN2322-

V01

The ECB shall be capable of

interfacing with the E911 telephone

system.

HUBS-UN015-v01

HUBS-IX2433-v01

HUBS-IX2434-v01

Test

HUBS-

FN2323-

V01

When an ECB alarm is triggered, the

ECB system shall perform the

following functions (1) sound a loud

noise for perimeter awareness, (2)

establish a bidirectional voice-enabled

communication medium from the IK to

the Columbus Emergency Call Center

(CECC) (3) activate the IK camera and

send the video stream to the CECC.

HUBS-UN007-v01

HUBS-UN015-v01

HUBS-IX2433-v01

HUBS-IX2434-v01

Test

HUBS-

FN2335-

V01

The IK system shall support multiple

languages. At a minimum, English and

Spanish shall be supported. The

system shall maintain English as its

default language setting and provide

users the ability to select a language of

choice.







Verification

Method

HUBS-

FN2336-

V01

The system shall detect and

automatically notify the IK system

administrator when a functional

abnormality has occurred such as (1)

inability to communicate through an

interface, (2) inability to send/receive

data, (3) service requests and queries

extend longer than ten seconds, (3)

invalid or missing data has been

detected.

HUBS-UN001-v01

HUBS-UN002-v01

HUBS-UN003-v01

HUBS-UN004-v01

HUBS-UN006-v01

HUBS-UN008-v01

HUBS-UN010-v01

Test

HUBS-

FN2337-

V01

The system shall incorporate

automation tools to enable automatic

resolution of system abnormalities,

security incidents, faults, and errors (to

the extent possible).

HUBS-UN002-v01 Test

HUBS-

FN2338-

V01

All communications links shall utilize

Transmission Control Protocol/Internet

Protocol (TCP/IP) and possess high-

speed bandwidth and availability to

perform the functionalities described

within this SyRS.

HUBS-UN003-v01

HUBS-UN004-v01

HUBS-UN006-v01

HUBS-UN007-v01

HUBS-UN008-v01

HUBS-UN010-v01

Test

HUBS-

FN2339-

V01

All system errors, warnings, and self-

correcting actions shall be recorded in

an exportable ASCII text file system

log.






Verification

Method

HUBS-

FN2340-

V01

The system shall incorporate

automatic shut down and restart

features that preserve system integrity

and minimizes potential damage in the

event of power failures.

HUBS-UN003-v01

HUBS-UN004-v01

HUBS-UN006-v01

HUBS-UN007-v01

HUBS-UN008-v01

HUBS-UN010-v01

Demonstration

HUBS-

FN2341-

V01

The IK system shall limit the use of

internet to the approved applications,

services, and features offered through

the interactive display, including trip

planning and payment via

MMTPA/CPS, Emergency Call Button,

and USB Charging.


HUBS-

FN2342-

V01

The system shall be designed for

unattended operation under normal

circumstances, exclusive of manual

data entry, public user access, and

routine administrative functions.

HUBS-UN002-v01

HUBS-UN003-v01

Demonstration

HUBS-

FN2343-

V01

The Operating System shall be used to

capture HUBS traveler behavior,

visualizations and other data-related

business insights.







Verification

Method

HUBS-

FN2344-

V01

IK touch screen content shall allow

customers to view information and the

format shall be configurable to support

kiosks for different operating locations

and functionality, including location

awareness and SMH services offered

at each particular location.

HUBS-UN001-v01

HUBS-UN003-v01

HUBS-UN006-v01

HUBS-UN010-v01

Demonstration

HUBS-

FN2345-

V01

The public touch screen interface shall

prohibit unauthorized users from

accessing the operating system or any

GUI, kiosk, or network controls or

settings.

HUBS-UN002-v01 Test

HUBS-

FN2346-

V01

The touch screen interface and its

controls shall conform to the applicable

accessibility requirements of the

Americans with Disabilities Act (ADA).


HUBS-

FN2347-

V01

The touch screen interface shall be

designed to withstand intentional or

unintentional misuse (e.g. repeated

tapping of keys) without system

malfunction.






Verification

Method

HUBS-

FN2348-

V01

The touch screen interface shall

maintain a unique identifier for each

kiosk in order to diagnose system

malfunctions, provide information to

the ECB service, as well as customize

content per SMH location (location

awareness).

HUBS-UN002-v01 Test

HUBS-

FN2349-

V01

The touch screen interface shall not

permit access to data integrated

through IK system interfaces that are

deemed to be confidential or

inappropriate for public use.

HUBS-UN002-v01 Test

HUBS-

FN2350-

V01

The touch screen interface shall utilize

a commercial off-the-shelf Kiosk

Operating System (KOS) that resides

on top of the PC Operating System

(Latest version of Windows, Linux, or

Raspberry OS), in accordance with the

software requirements outlined in this

SyRS.


HUBS-

FN2351-

V01

Where source data is not available in

real-time, the touchscreen shall utilize

PDF and/or service board websites in

the short term such as transit route

maps, location specific services or

tourism information, etc.

HUBS-UN003-v01

HUBS-UN006-v01

HUBS-UN008-v01

HUBS-UN010-v01

HUBS-CN2426-v01

Demonstration






Verification

Method

HUBS-

FN2352-

V01

The standby screen may incorporate a

demonstration of the use of the screen,

general information, and/or animation.

HUBS-UN003-v01

HUBS-UN013-v01

Demonstration

HUBS-

FN2353-

V01

The touch screen shall display a static

or animated screen or series of

screens when the kiosk is not in use

(as determined by a preset standby

period of inactivity).

HUBS-UN003-v01

HUBS-UN013-v01

HUBS-CN2426-v01

Demonstration

HUBS-

FN2354-

V01

Users shall exit standby mode by

touching the screen or activating any

other kiosk controls. When standby

mode is exited, the system shall

display an initial start page with links to

various sub-menus and content pages

that allow the user to reach all

information contained within the

system.

HUBS-UN003-v01

HUBS-UN013-v01

Test

HUBS-

FN2388-

V01

The ride share system shall have

designated curb space allocated for

pick-up from rideshare and taxi

services.

HUBS-UN005-v01

HUBS-UN014-v01

HUBS-CN2424-v01

HUBS-CN2427-v01

Inspection

HUBS-

FN2394-

V01

USB charging outlets shall be USB

Type A 3.X standard.






Verification

Method

HUBS-

FN2395-

V01

The USB Charging service shall

deliver free charging for travelers at all

SMH locations to charge mobile

devices when in transit.


HUBS-

FN2403-

V01

HUBS shall permit electronic devices

equipped with internet capabilities

(phone, tablet, computer) to connect to

the internet wirelessly using radio

waves.

HUBS-UN004-v01

HUBS-CN2428-v01

HUBS-CN2430-v01

Demonstration

HUBS-

FN2404-

V01

Wi-Fi enabled technologies shall

operate independently and shall not

affect or be affected by other wireless

access devices in the event of failure.

HUBS-UN004-v01

HUBS-CN2428-v01

Test

HUBS-

FN2405-

V01

HUBS may consider IEEE 802.11ai to

enable Fast Initial Link Set-up (FILS)

methods to enhance end-user

experience in high-density WLAN

environments.

HUBS-UN004-v01

HUBS-CN2428-v01

Demonstration

HUBS-

FN2406-

V01

Wi-Fi technologies shall follow IEEE

802.11 b/g/n standards to enable multi-

gigabit throughput in the 2.4 GHz,

5GHz and 60GHz spectrum bands.

HUBS-UN004-v01

HUBS-CN2428-v01

Demonstration






Verification

Method

HUBS-

FN2407-

V01

An active session with internet access

shall be provisioned for the user when

that user accepts the terms and

conditions of service.

HUBS-UN004-v01

HUBS-CN2428-v01

HUBS-CN2430-v01

Test

HUBS-

FN2408-

V01

An active session with internet access

shall not be provisioned for the user

when that user declines the terms and


HUBS-UN004-v01

HUBS-CN2428-v01

HUBS-CN2430-v01

Test

HUBS-

FN2422-

V01

All visual information should be

provided with a TTY capbaility.


HUBS-

FN2423-

V01

Kiosk shall include a titanium speaker

that can be set 6dB above the ambient

noise of the daytime environment and

set to a lower volume at night.


HUBS-

FN2441-

V01

The system shall reset back to the

default language at the end of a user

session or after a period of 2 minutes

of inactivity.


HUBS-

FN2442-

V01

Dedicated paved area shall be made

available for dockless devices

(scooters, ebikes, etc.) at the HUBS

facility.






Verification

Method

HUBS-

FN2443-

V01

Boundaries, symbols and/or text

description of designated area for

dockless devices shall be clearly

outlined on pavement with paint.



356

3.2 Performance Requirements 357

This section provides the performance requirements (PR) for the system of interest (i.e. what the system 358

will do). The requirements in Table 10: Performance Requirements are organized by the functional 359

groups and are related to the user needs the HUBS ConOps identified. 360

Table 10: Performance Requirements 361


Verification

Method

HUBS-

PR2275-

V01

The placement of bike racks shall not

impede flow of vehicle or pedestrian

traffic.

EPM-CN1677-v01

HUBS-UN011-v01

HUBS-UN005-v01

Inspection

HUBS-

PR2301-

V01

The bike share company shall not


traffic.

HUBS-UN005-v01

HUBS-UN011-v01

HUBS-CN2427-v01

Demonstration






Verification

Method

HUBS-

PR2302-

V01

The bikes parked in violation of the

permit or other Federal or City codes

or are vandalized or inoperatble shall

be re-parked in a correct manner or

removed within four (4) hours of

receiving the notices.

HUBS-UN005-v01

HUBS-UN011-v01

Demonstration

HUBS-

PR2382-

V01

The Park and Ride facility shall allow

24/7 public access to the vehicles.

HUBS-UN005-v01

HUBS-UN014-v01

Demonstration

HUBS-

PR2383-

V01

The Park and Ride facility shall allow

parked vehicles to maintain unimpeded

access to roadway/driveway entrances

and exits.

HUBS-UN005-v01

HUBS-CN2427-V01

HUBS-UN014-v01

Demonstration

HUBS-

PR2384-

V01

The Park and Ride facility shall ensure

the parked vehicles do not impede the

regular flow of travel in the public right

of way.

HUBS-UN005-v01

HUBS-UN014-v01

HUBS-CN2427-V01

Demonstration

HUBS-

PR2385-

V01

The Park and Ride facility shall ensure

the vehicles not be parked in a way

that impedes the 5 feet clearance on

sidewalks needed for ADA

compliance.

HUBS-UN005-v01

HUBS-UN014-v01

Demonstration





Verification

Method

HUBS-

PR2392-

V01

The City may designate parking areas

or restrict car parking within certain

areas.

HUBS-UN005-v01

HUBS-UN014-v01

HUBS-CN2427-v01

Demonstration

HUBS-

PR2411-

V01

Wi-Fi technologies shall support up to

X number of users simultaneously

connected.

HUBS-UN004-v01

HUBS-CN2428-v01

Demonstration

HUBS-

PR2450-

V01

The dockless parking zone shall not


traffic.


HUBS-

PR2451-

V01

All software and security systems shall

be reviewed quarterly for updates or as

updated as new versions become

available.


HUBS-

PR2452-

V01

Interactive Kiosk displays shall meet

City outdoor advertisement brightness

standards and be capable of adjusting

brightness based on varying outside

light conditions.



3.3 Interface Requirements 363

The HUBS IF Requirements allow dynamic and configurable functionality among internal components of 364

the Smart Columbus System of Systems (SoS) and external systems that provide data or some other 365

stated functionality as per the User Needs. IF Requirements are categorized into two groups – Internal 366

IFs and External IFs – which will help further clarify system boundaries. 367





3.3.1. External Interface Requirements 368

Table 11: External Interface Requirements by Functional Group describes the External IF 369

requirements for each FG identified in Table 2: System Functional Groups, and the requirements are 370

related to the User Needs identified in the HUBS ConOps. The requirements are related to the user 371

needs the HUBS ConOps identified. 372

Table 11: External Interface Requirements by Functional Group 373


Verification

Method

HUBS-

IF2315-

V01

The CPS application shall be deployed

and available for use at the IK display

through the MMTPA application.

HUBS-UN003-v01

HUBS-IX2431-v01

Demonstration

HUBS-

IF2316-

V01

The MMTPA application shall be

deployed and available for use at the

IK display.

HUBS-UN003-v01

HUBS-IX2432-v01

Demonstration

HUBS-

IF2325-

V01

A (hardware or software) Emergency

Call Button (ECB) interface shall be

designed for public users to alert the

Columbus Emergency Call Center

officials in an emergency situation.

HUBS-UN007-v01

HUBS-UN015-v01

HUBS-IX2433-v01

Test

HUBS-

IF2355-

V01

The kiosk shall provide a secured,

direct-connect interface to facilities for

operational administration through a

wireless network interface card (NIC)

or a local fiber resource.

HUBS-UN003-v01

HUBS-IX2435-v01

Test





Verification

Method

HUBS-

IF2356-

V01

The IK system shall provide access to

a web or app based interface with the

MMTPA/CPS system to provide

comprehensive trip planning services

and disseminate information regarding

mobility providers, parking providers,

and availability of various modes of

transportation to the traveling public.

HUBS-UN003-v01

HUBS-IX2431-v01

Demonstration

HUBS-

IF2357-

V01

The interface to other HUB services

offered at the HUBS location (e.g. Car,

Bike, and Ride Sharing) shall be

provided through the MMTPA/CPS

interface, which provides

comprehensive trip planning services

for the HUBS traveler.

HUBS-UN003-v01

HUBS-IX2432-v01

Demonstration

HUBS-

IF2359-

V01

The IK touch screen shall provide

users with a link to display any current

system-wide or other alerts that

describe events having a significant

impact on transit services.

HUBS-UN010-v01

HUBS-IX2431-v01

Demonstration

HUBS-

IF2360-

V01


users with a link to the COTA Real-

Time Display.

HUBS-UN006-v01

HUBS-IX2431-v01

Test

HUBS-

IF2361-

V01


users with a link to various static maps.

HUBS-UN003-v01

HUBS-UN006-v01

HUBS-IX2431-v01

Demonstration






Verification

Method

HUBS-

IF2362-

V01


users with a link to Visitor Information,

which includes location-aware

content.

HUBS-UN010-v01

HUBS-IX2431-v01

Demonstration

HUBS-

IF2363-

V01

The IK display should include a

minimum of X USB ports for charging

mobile devices to HUBS travelers.

HUBS-UN009-v01

HUBS-IX2437-v01

Demonstration

HUBS-

IF2389-

V01

The ride sharing service shall be

provided through the MMTPA

application.

HUBS-UN014-v01

HUBS-IX2432-v01

Demonstration

HUBS-

IF2396-

V01

USB device charging should be

integrated at each IK display.

HUBS-UN009-v01

HUBS-IX2439-v01

Inspection

HUBS-

IF2409-

V01

Wi-Fi services shall be provided by the

IK display.

HUBS-UN004-v01

HUBS-IX2438-v01

Test


3.4 Data Requirements 375

The DRs for the core system of interest defines the data collected, transformed and stored from various 376

sources and identifies new data that is expected to be generated. The requirements in Table 12: Data 377

Requirements are organized by the functional groups and are related to the user needs identified the 378

HUBS ConOps identified. 379




Table 12: Data Requirements 380


Verification

Method

HUBS-

DR2283-

V01

The bike share company shall collect

and share data in a manner that does

not compramise the privacy of the

Citizens.


HUBS-

DR2284-

V01

The bike share company shall maintain

and share a list of deployed bikes,

listed by unique identifier with the City

monthly.


HUBS-

DR2285-

V01


and share a list of lost, stolen and

vandalized bike with the City monthly.

HUBS-UN002-v01

HUBS-UN002-v01

Demonstration

HUBS-

DR2286-

V01


and share a record of maintenance

activities including but not limited to

identification number and maintenance

performed with the City monthly.


HUBS-

DR2287-

V01


and share a record of reported

collisions with the City monthly.


HUBS-

DR2320-

V01

ECB shall be record the time, date,

and location upon activation.

HUBS-UN007-v01

HUBS-UN015-v01

Test






Verification

Method

HUBS-

DR2321-

V01

The street address of the HUBS facility

shall be sent to the CECC to notify

dispatchers of location of the help

request.

HUBS-UN015-v01

HUBS-UN007-v01

HUBS-IX2433-

V01

Test

HUBS-

DR2328-

V01

The Kiosk touch screen interface shall

allow Travelers to access data

contained in the Operating System

through the MMTPA application such

as schedule information, static service

information (e.g. fares), trip planning

information, real-time service

information, transit bulletins, and

maps.

HUBS-UN001-v01

HUBS-UN003-v01

HUBS-UN006-v01

HUBS-UN009-v01

HUBS-UN010-v01

Demonstration

HUBS-

DR2329-

V01

The Kiosk touch screen interface

content shall include static and real-

time traveler information to the extent

that each data element is available

from the Operating System retrieved

through the GTFS Real-time data

feed. Arrivals in the next hour for that

location should be displayed on the

screen.

HUBS-UN001-v01

HUBS-UN013-v01

Demonstration

HUBS-

DR2400-

V01

Wi-Fi enabled technologies shall track

number of clients per access point.






Verification

Method

HUBS-

DR2401-

V01

Wi-Fi technologies shall log user

connection timestamp, IP, MAC, OS,

device manufacturer, sites visited,

connection status, connection length.

HUBS-UN004-v01 Test


3.5 Security Requirements 382

The SRs for the core system of interest specifies what is necessary to protect the integrity and operability 383

of the system, its microservices, connections, and data. This includes physical security as well as cyber 384

prevention, detection, identification, response and recovery requirements. The requirements in Table 13: 385

Security Requirements are organized by the functional groups and are related to the user needs 386

identified the HUBS ConOps identified. 387

Table 13: Security Requirements 388


Verification

Method

HUBS-

SR2308-

V01

The docking station shall permit the

locking of the bicycle frame and one

(1) wheel to the rack.


HUBS-

SR2376-

V01

The IK system components shall be

protected by firewalls and equipped

with security detection, prevention, and

response mechanisms to guard

against intentional and unintentional

threats to the integrity of the system

arising from unauthorized access,

computer viruses and worms, system

abnormalities or faults, and other

sources of potential harm.







Verification

Method

HUBS-

SR2377-

V01

The IK system shall accommodate

multiple tiers of user data security to

allow distinct privileges to access data

based on user roles (e.g. public user,

administrator, service accounts, City

and COTA personnel, data miner,

external agency, etc.)

HUBS-UN001-v01

HUBS-UN002-v01

HUBS-UN003-v01

Demonstration

HUBS-

SR2378-

V01

The system shall be designed to

preserve the privacy of individual

public users of the system and provide

data protection, such as encrypting

login credentials, payment information,

and other sensitive data captured

through the kiosk and transmitted over

Wi-Fi or fiber.


HUBS-

SR2379-

V01

The system shall detect and

automatically alert the IK system

administrator when a security incident

has been detected such as (1) kiosk

access door has been opened, (2)

cybersecurity alert has been logged by

the unified threat management

software (anti-virus, malware

detection, etc.), (3) misuse of kiosk

features such as recreational web

browsing through the interactive

display or attempts to intercept

communications between interfaces.

HUBS-UN002-v01 Test





Verification

Method

HUBS-

SR2380-

V01

The integrity of IK system applications,

communications, and network links

shall be secured through mechanisms

such as password authentication.


HUBS-

SR2416-

V01

A timer shall be implemented to track

the length of time a connection has

been active.

HUBS-UN004-v01

HUBS-CN2428-v01

Test

HUBS-

SR2417-

V01

The load on each access point shall be

monitored and flagged when there is

an overloading issue associated with

the access point.

HUBS-UN004-v01

HUBS-CN2428-v01

Test

HUBS-

SR2418-

V01

The upload and download speed on

each access point shall be tracked,

monitored, and changed as necessary.

HUBS-UN004-v01

HUBS-CN2428-v01

Demonstration

HUBS-

SR2419-

V01

Usage shall be tracked on all Wi-Fi

technologies, per device, in order to

validate proper usage of public

wireless as per COTA internet usage

policy.

HUBS-UN004-v01

HUBS-CN2428-v01

Demonstration

HUBS-

SR2420-

V01

Communications to Wi-Fi hot spots

and zones shall be on a separate

VLAN from City networks.

HUBS-UN004-v01

HUBS-CN2428-v01

Inspection






Verification

Method

HUBS-

SR2421-

V01

Wi-Fi technologies shall terminate a

connection if any of the following

conditions have been met (1) a

violation of Wi-Fi technology usage

has been identified (2) connection has

extended beyond 2 hours.

HUBS-UN004-v01

HUBS-CN2428-v01

Test

HUBS-

SR2453-

V01

All software and security systems shall

be reviewed quarterly for updates or as

updated as new versions become

available.



3.6 Non-Functional Requirements 390

NF Requirements for the core system of interest specifies define the characteristics of the overall 391

operation of the system such as availability, maintainability, reliability, safety, environmental, human 392

factors, and ergonomics. 393

3.6.1. Physical Requirements 394

PY Requirements specify the construction, durability, adaptability and environmental characteristics of the 395

system such as installation location, device weight limits, dimension and volume limitations, temperature 396

regulations, layout, access for maintenance, and growth and expansion characteristics. The requirements 397

in Table 14: Physical Requirements are organized by the functional groups and are related to the user 398

needs identified the HUBS ConOps identified. 399




Table 14: Physical Requirements 400


Verification

Method

HUBS-

PY2278-

V01

The bike racks shall be located on

paved or pervious, dust-free surface

with a slope no greater than three

percent (3%)


HUBS-

PY2279-

V01

The bike racks shall have a vertical

clearance of at least six (6) ft.


HUBS-

PY2280-

V01

The bike racks shall have an access

aisle with a minimum width of five (5)

feet


HUBS-

PY2305-

V01

The docking station shall be located on

paved or pervious surface with a slope

of less than three percent (3%)


HUBS-

PY2306-

V01

The docking station shall have a

vertical clearance of at least six (6)

feet.


HUBS-

PY2307-

V01

The docking station shall have an

access aisle with a minimum width of

five (5) feet.







Verification

Method

HUBS-

PY2312-

V01

The parking lots shall have a vertical

clearance of at least twelve (12) feet.

HUBS-UN005-v01

HUBS-UN014-v01

Inspection

HUBS-

PY2313-

V01

The parking lots shall be located on

paved or pervious surfaces with a

slope of less than three percent (3%).

HUBS-UN005-v01

HUBS-UN014-v01

Inspection

HUBS-

PY2369-

V01

All portions of the hardware and

communications system shall be

locked and secured to minimize the

risk of tampering or damage by

unauthorized individuals.


HUBS-

PY2370-

V01

Equipment shall be oriented and

ventilated in a manner consistent with

applicable workplace safety,

ergonomics, and operated within the

environmental parameters

recommended by the equipment

manufacturers.


HUBS-

PY2371-

V01

Hardware shall be protected from

environmental perils during transport,

storage, installation, and operation

such as moisture, humidity, weather,

dust, smoke, heat, static electricity,

magnetic fields, and vibration.






Verification

Method

HUBS-

PY2372-

V01

The system power supply shall be

installed in accordance with national

and local electrical codes and all

central hardware shall be provided with

an adequate supply of continuous AC

power (i.e., protected from spikes and

surges).


HUBS-

PY2386-

V01

The Park and Ride facility shall have a

vertical clearance of at least twelve

(12) feet.

HUBS-UN005-v01

HUBS-UN014-v01

Inspection

HUBS-

PY2387-

V01

The Park and Ride facility shall have

an access aisle with a minimum width

of five (5) feet

HUBS-UN005-v01

HUBS-UN014-v01

Inspection

HUBS-

PY2398-

V01

The hardware shall withstand indoor

and outdoor environmental conditions

such as high and low temperatures,

humidity, rain, snow, etc.


HUBS-

PY2412-

V01

Wi-Fi equipment shall withstand indoor

and outdoor environmental conditions

such as high and low temperatures,

humidity, rain, snow, etc.

HUBS-UN004-v01

HUBS-CN2428-

V01

Demonstration






Verification

Method

HUBS-

PY2454-

V01

The parking lots shall be located on

paved or pervious surfaces with a

slope of less than three percent (3%).



3.6.2. Availability and Recoverability Requirements 402

AR Requirements define the times of day, days of year, and overall percentage the system can be used 403

and when it will not be available for use. It also specifies the recovery time objective (RTO) of the system, 404

which is the time frame permitted for a system to become operational; the recovery point objective (RPO), 405

which specifies up till what point in time shall the data be restored; and how the system is expected to 406

restore services (e.g. failover, backups, etc.) in an event of a failure. The ability to recover quickly from a 407

system failure or disaster depends on a blend of technologies and having a predefined plan for recovering 408

the data on new hardware, when appropriate. 409

The requirements in Table 15: Availability and Recovery Requirements are organized by the functional 410

groups and are related to the user needs identified the HUBS ConOps identified. 411

Table 15: Availability and Recovery Requirements 412


Verification

Method

HUBS-

AR2274-

V01

The capacity of bike racks per HUBS

location should be equal to 5% of the

total number of parking spaces or X of

daily transit trips, whichever is greater.


HUBS-

AR2282-

V01

The docking station shall be designed

for persistent always-on availability,

maintaining continuous operation 24

hours a day, 7 days a week, 365 days

a year.

HUBS-UN011-v01 Analyze





Verification

Method

HUBS-

AR2318-

V01

The ECB service shall be made

available 24 hours a day, 7 days a

week, 365 days a year.

HUBS-UN007-v01

HUBS-UN015-v01

Analyze

HUBS-

AR2326-

V01

The Kiosk system shall incorporate

system redundancies to the extent

practical to guard against failure of

individual hardware, software, network,

or communications components and

ensure maximum, persistent always-on

availability, maintaining continuous

operation 24 hours a day, 7 days a

week, 365 days a year.

HUBS-UN003-v01

HUBS-UN004-v01

HUBS-UN006-v01

HUBS-UN007-v01

HUBS-UN008-v01

HUBS-UN010-v01

Analyze

HUBS-

AR2381-

V01

At least one (1) parking space for ADA

shall be available at each of the hub

locations for every 30 spaces. One out

of six of the ADA spaces must be van

accessible. An accessible car parking

space must be a minimum of 96 inches

wide and a van space must be a

minimum of 132 inches wide (a van

space may be 96 inches if the access

aisle is 96 inches or wider)

HUBS-UN005-v01

HUBS-UN014-v01

Inspection

HUBS-

AR2399-

V01

The Wi-Fi network shall be fault

tolerant and maintain continuous

network uptime outside of the

scheduled maintenance, 24-hour per

day, 365-day per year.

HUBS-UN004-v01 Analyze






3.6.3. Maintainability Requirements 414

MT Requirements for the system specify the level of effort required to locate and correct an error during 415

operation, establishing a quantitative requirement for planned and unplanned support (e.g. mean and 416

maximum times to repair or resolve issues, number of people and skill levels required, support equipment 417

necessary, maintenance staff hours, time and frequency of preventative maintenance, etc.). 418

The requirements in Table 16: Maintainability Requirements are organized by the functional groups 419

and are related to the user needs identified the HUBS ConOps identified. 420

Table 16: Maintainability Requirements 421


Verification

Method

HUBS-

MT2299-

V01

Each bike shall have a unique identifier

that is visible to the user.


HUBS-

MT2300-

V01

Each bike shall have permanently fixed

real-time GPS tracking device in order

to track ridership data

HUBS-UN001-v01

HUBS-UN011-v01

Inspection

HUBS-

MT2367-

V01

The system shall be designed such

that administrative and maintenance

activities that require the system to be

taken off line can occur at periods of

lowest public utilization (e.g. overnight)

to maintain maximum system

availability for public users.


HUBS-

MT2368-

V01

The kiosk and back office IK system

shall be maintained by vendor.


HUBS-

MT2390-

V01

Each vehicle shall comply with all

applicable State and local laws.






Verification

Method

HUBS-

MT2391-

V01

Each vehicle shall have a unique

identifier that is visible to the user.


HUBS-

MT2397-

V01

The system contractor shall perform

maintenance, replacement, and annual

functional testing for all USB ports.

HUBS-UN002-v01

HUBS-UN009-v01

Demonstration

HUBS-

MT2410-

V01

Wi-Fi devices shall be managed and

maintained by vendor

HUBS-UN004-v01

HUBS-CN2428-

V01

Demonstration


3.6.4. Storage and Transport Requirements 423

ST Requirements specify the physical location and environment for the system, including designated 424

storage facility, installation site, repair facility, requirements for transporting equipment, etc. The 425

requirements in Table 17: Storage and Transport Requirements are organized by the functional groups 426

and are related to the user needs identified the HUSB ConOps identified. 427

Table 17: Storage and Transport Requirements 428


Verification

Method

HUBS-

ST2281-

V01

The bike racks shall support a bicycle

in a stable upright position.

HUBS-UN001-

v01

Inspection

HUBS-

ST2309-

V01

The docking station shall support a

bicycle in a stable upright position.

HUBS-UN001-

v01

Inspection






Verification

Method

HUBS-

ST2314-

V01

The vehicles shall be parked only

within designated parking spots at

HUBS.

HUBS-UN005-

v01 HUBS-

UN014-v01

Demonstration


3.6.5. Disposal Requirements 430

The DP Requirements specify the items related to the disposal of project/system components, due to 431

either failure replacements, removal, end-of-life upgrade, or retirement. The requirements in Table 18: 432

Disposal Requirements are organized by the functional groups and are related to the user needs 433

identified the HUBS ConOps identified. 434

Table 18: Disposal Requirements 435


Verification

Method

HUBS-

DP2327-

V01

Replacement and disposal of damaged

parts on kiosk shall be performed by

vendor.

HUBS-UN003-

v01

Demonstration


437




3.7 Enabling Requirements 438

EN Requirements specify details concerning the management of information as well as the production of 439

the system and its lifecycle sustainment, including development, integration, verification, validation and 440

training. 441

Table 19: Enabling Requirements 442


Verification

Method

HUBS-

EN2317-

V01

The ECB service shall undergo end-to-

end testing by vendor on an annual

basis.

HUBS-UN007-v01

HUBS-UN015-v01

Demonstration

HUBS-

EN2330-

V01

The Kiosk system shall contain the

minimum required system components

for touch screen kiosk products,

including (a) the kiosk display

strategically installed at six SMH

locations as outlined in Chapter 2, (b)

the kiosk software installed over an

existing operating system (Latest

version of Windows, Linux, or

Raspberry OS) as outlined by the

product's system requirements, (c)

back-office application server (d) back-

office database (e) back-office storage

drives and, (f) back-office backup

drives.


HUBS-

EN2331-

V01

All hardware shall undergo testing

procedures and shall include (1)

factory acceptance testing, (2)

installation testing, and (3)

performance testing.







Verification

Method

HUBS-

EN2332-

V01

The system shall be designed with an

open architecture intended to facilitate

expansion of the functionality and/or

scale of the IK system as new data

sources, applications, features,

standards, and/or technologies emerge

in the future.

HUBS-UN003-v01

HUBS-UN008-v01

HUBS-UN010-v01

Demonstration

HUBS-

EN2333-

V01

The touch screen interface design

elements and page renderings shall be

flexible to enable future enhancements

as information and data quantity and

quality improves/evolves over time,

including modular graphics, design

templates controlling color schemes,

fonts, backgrounds, etc., and

implementation of web development

best practices, version control,

notation, and documentation.


HUBS-

EN2402-

V01

Wi-Fi enabled technologies should be

configured to create wireless mesh

network to deliver Wi-Fi service zone

at each facility. The coverage zone

enables mobile users to enter and exit

individual access point surface area

without loss of connectivity, seamlessly

transitioning the signal to another

access point within the zone.

HUBS-UN004-v01 Test

443




3.7.1. Information Management Requirements 444

IM Requirements specify the acquisition, management, and ownership of information from one or more 445

sources, the custodianship and the distribution of that information to those who need it, and its ultimate 446

disposition through archiving or deletion. The requirements in Table 20: Information Management 447

Requirements are organized by the functional groups and are related to the user needs identified the 448

HUBS ConOps identified. 449

Table 20: Information Management Requirements 450


Verification

Method

HUBS-

IM2364-

V01

The IK system shall perform daily

background verification of all external

web links and provide immediate

notification to the IK system

administrator if any link fails

verification.

HUBS-UN003-

v01 HUBS-

UN006-v01

HUBS-UN010-

v01

Demonstration

HUBS-

IM2365-

V01

The IK system backup files (server

clone snapshot and data backups)

shall be tested quarterly for

recoverability integrity.

HUBS-UN002-

v01 HUBS-

UN003-v01

Demonstration

HUBS-

IM2366-

V01

The system shall capture and log all

data entered through the touch screen

interface for further analysis at the

back office for purposes of enhancing

location aware services and improving

safety at each designated location.

HUBS-UN001-

v01 HUBS-

UN003-v01

Demonstration


3.7.2. Life-Cycle Sustainability Requirements 452

LC Sustainability Requirements define what items the project or system will review, measure, and analyze 453

as part of its commitment to quality during the life cycle of the system. The capacity to change or enhance 454

the product and life cycle processes can be designed into the system architecture to enable the cost-455





effective sustainment of the system throughout its life cycle. This design attribute should be established 456

early in the system’s development to provide a basis for planning each incremental development effort. 457

The requirements in Table 21: Life-Cycle Sustainability Requirements are organized by the functional 458


Table 21: Life-Cycle Sustainability Requirements 460


Verification

Method

HUBS-

LC2445-

V01

Additional space for dockless

equipment zone should be made

available if warranted by increased

demand for this service.

HUBS-UN011-v01

HUBS-UN014-v01

Inspection

HUBS-

LC2455-

V01

Additional parking spaces should be

made available if warranted by

increased demand for Park & Ride

services.

HUBS-UN011-v01

HUBS-UN014-v01

Inspection

HUBS-

LC2456-

V01

Bike racks should be modular in

construction so that additional racks

may be installed in the future with

similar overall functional and aesthetic

qualities.

HUBS-UN003-v01

HUBS-UN011-v01

Inspection

HUBS-

LC2457-

V01

Docking stations should be modular in

construction so that additional racks

may be installed in the future with

similar overall functional and aesthetic

qualities.

HUBS-UN003-v01

HUBS-UN011-v01

Inspection





Verification

Method

HUBS-

LC2458-

V01

Additional parking spaces should be

made available if warranted by

increased demand for car sharing

services.

HUBS-UN011-v01

HUBS-UN014-v01

Inspection

HUBS-

LC2459-

V01

Additional space for pick up/drop off

zone should be made available if

warranted by increased demand for

ride sharing services.

HUBS-UN011-v01

HUBS-UN014-v01

Inspection

HUBS-

LC2460-

V01

The touch screen interface shall be

designed with flexibility to allow future

expansion such as enlargement or the

addition of new software tools, data

sources, or other needs that may

emerge in the future.



3.8 Policy and Regulation Requirements 462

RG Requirements for the system of interest specifies relevant and applicable organizational policies and 463

regulations that affect the development, operation or performance of the system (e.g. IT and labor 464

policies, reports to regulatory agencies, health or safety criteria, etc.). This section also includes new 465

policy and regulation imposed to realize the system. 466

The requirements in Table 22: Policy and Regulation Requirements are organized by the functional 467






Table 22: Policy and Regulation Requirements 469


Verification

Method

HUBS-

RG2276-

V01

The locations of the bike racks shall be

approved by the City or property

owner.

HUBS-UN011-

v01 HUBS-

CN2427-V01

HUBS-UN005-

v01

Demonstration

HUBS-

RG2303-

V01

The docking stations shall be primarily

located within the public right-of-way,

along public streets and sidewalks,

parks, trails, parking lots/garages,

events venues, etc. or be located on

private property, provided that the

property owner agrees to allow 24/7

public access to the Docking station.

HUBS-UN005-

v01 HUBS-

UN011-v01

HUBS-CN2427-

V01

Inspection

HUBS-

RG2373-

V01

Installation of interactive kiosks in the

City shall comply with building and

construction city codes of Columbus,

OH

HUBS-UN002-

v01 HUBS-

UN003-v01

Inspection

HUBS-

RG2374-

V01

The system shall adhere to object-

oriented design principles to facilitate

replacement or modification of

individual components of the IK system

without impacting the overall system.

HUBS-UN003-

v01 HUBS-

UN008-v01

HUBS-UN010-

v01

Demonstration





Verification

Method

HUBS-

RG2375-

V01

The system shall adhere to the current

guidelines and principles set forth in

the National ITS Architecture

developed by the U.S. Department of

Transportation ITS Joint Program

Office.

HUBS-UN003-

v01

Demonstration

HUBS-

RG2393-

V01

The locations of the parking lots shall

be approved by the City or property

owner.

HUBS-UN005-

v01 HUBS-

UN014-v01

HUBS-CN2427-

V01

Demonstration

HUBS-

RG2413-

V01

Usage on all Wi-Fi technologies shall

be limited to users for recreational

purposes (non-business usage) and to

deliver transportation-related services

to the public, including but not limited

to comprehensive trip planning,

emergency services, etc.

HUBS-UN004-

v01 HUBS-

CN2428-V01

HUBS-IX2436-

V01

Demonstration

HUBS-

RG2414-

V01

Users may be redirected to a landing

page designated by vendor or property

owner when connecting to Wi-Fi

technologies once the user accepts the

terms and conditions of service.

HUBS-UN004-

v01 HUBS-

CN2428-V01

Demonstration

HUBS-

RG2415-

V01

Wi-Fi technologies shall present the

user with a landing page designated

by vendor or property owner to display

the Free Wi-Fi terms and conditions of

service and prompt the user to accept.

HUBS-UN004-

v01 HUBS-

CN2428-V01

Test






Verification

Method

HUBS-

RG2444-

V01

The locations of the parking lots shall

be approved by the City or property

owner.

HUBS-UN005-

v01 HUBS-

UN014-v01

HUBS-CN2427-

V01

Demonstration

HUBS-

RG2447-

V01

The locations of the dockless device

zones shall be approved by the City or

property owner.

HUBS-UN005-

v01

Inspection

HUBS-

RG2461-

V01

The locations of the docking stations

shall be approved by the City or

property owner.

HUBS-UN005-

v01 HUBS-

UN011-v01

Demonstration


471

472

473




Chapter 4. Engineering Principles 474

This section describes engineering principles that guide composition of the HUBS. 475

4.1 Methods of Verification 476

The software and hardware components that make up the HUBS will be individually verified, then 477

integrated to produce top-level assemblies and microservices. These assemblies will also be individually 478

verified before being integrated with others to produce larger, evolving assemblies until the complete 479

system has been integrated and verified. Throughout this process, the Smart Columbus program will 480

utilize the Helix Requirements Management tool to capture, track and trace requirements starting with the 481

user needs defined in the ConOps, through development, testing and deployment. This approach and 482

software tool will be instrumental through the design and development phases of the project. 483

The requirements also maintain a verification method, which details the plan for verifying the requirement 484

based on its stated definition. For each requirement, one of the verification methods listed in Table 23: 485

Methods of Verification is assigned. Using the requirements defined in the previous section. 486

Table 23: Methods of Verification 487

Type Description

Inspection Verification through a visual, auditory, olfactory or tactile comparison.

Demonstration Verification that exercises the system software or hardware as it is designed to

be used, without external influence, to verify the results are specified by the

requirement.

Test Verification using controlled and predefined inputs and other external elements

(e.g. data, triggers, etc.) that influence or induce the system to produce the

output specified by the requirement.

Analyze Verification through indirect and logical conclusion using mathematical

analysis, models, calculations, testing equipment and derived outputs based on

validated data sets.


4.2 Reference Architecture 489

Historically, software systems have been developed as a single, monolithic unit constructed from a blend 490

of hand-built custom technologies. The more features added, the more complicated the system becomes 491

to work with contributing to high-risk, high-maintenance dependencies and a software structure that 492

resembles spaghetti code, making software exceedingly difficult and costly to manage over time. The 493

Chapter 4. Engineering Principles



architecture of the Smart Columbus program breaks apart this model by designing a set of small, discrete, 494

independent and standardized processes (i.e., FGs) that produce a service and can be plugged in for a 495

cleaner, more efficient build. Figure 4: Monolithic Versus Microservice Reference Architecture 496

provides an illustration of the reference architecture for monolithic verses services by FG. 497

498


Figure 4: Monolithic Versus Microservice Reference Architecture 500

As Figure 4: Monolithic Versus Microservice Reference Architecture depicts, system features in a 501

monolithic application are hard-wired into the application and cannot be used otherwise. In theory, the 502

entire system would need to be cloned. On the other hand, a modular design allows services to operate 503

independently, making plug and play features easy and quick to configure, deploy and scale. 504

The HUBS system is mindfully designed to leverage this model to create an SoS targeted for 505

performance, agility and scalability in a manageable way. Each API (application programming interface) 506

establishes a set of rules and principles for how the prepackaged FG microservice will integrate. The 507

communications bus will be built over hardware infrastructure and governed by software, which will 508

enable FG microservices to communicate securely while operating independently. 509




Appendix A. Document Terminology and 510

Conventions 511

A.1 Reference Conventions 512

The following conventions are used through this document: 513

Titles of externally referenced documents or sources are underlined. 514

Titles of internally referenced exhibits, sections, etc. are italicized. 515

A.1.1 Requirement Numbering Convention 516

Each requirement contains a unique ID for traceability and configuration management. Requirements for 517

all projects in the Smart Columbus program will follow the same convention. This identifier contains six 518

elements partitioned into three segments, each representing an identifiable attribute of the requirement. 519

The convention is as follows: 520

521

Table 24: Requirements Numbering Convention 522

Description

Data Type,

Casing

Number of

Characters/Digits

Project

Abbreviation

The designated Smart Columbus project

acronym (e.g. CVE, HUBS, etc.)

String, upper

case

Variable

Appendix A. Document Terminology and Conventions



Description

Data Type,

Casing

Number of

Characters/Digits

Requirement

Type Code

FN: Functional

PR: Performance

IF: Interface

DR: Data

SR: Security

RG: Policy and Regulation

PY: Physical

AR: Availability and Recovery

MT: Maintainability

ST: Storage and Transport

DP: Disposal

IM: Information Management

LC: Life Cycle Sustainability

CN: Constraints

String, upper

case

2

Requirement

Number

An integer incrementing by one, indicating

the number of requirements established.

Integer 3

“v” Static

Character

Static letter “v” represents the requirement

version.

Character 1

Version Number An integer incrementing by one, indicating

the number of revisions made to the

requirement.

Integer 2


An example of a Functional Requirement for the Transit Pedestrian Indicator application under the 524

Connected Vehicle Environment, would be “HUBS-KIOSK-SR053-v01” in which the following applies: 525

“HUBS” is the Project Abbreviation 526

“FNSR053” is the requirement type code coupled with the 3-digit Requirement Number 527

“v01” is the static “v” coupled with the 2-digit version number 528

A.1.2 Requirements Table Headings 529

The columns in the requirements tables throughout this document have the following definitions: 530

ReqID: a unique identifier providing a reference to a specific requirement. 531

Description: Statement of the business function or conditions the system must meet. 532

Appendix A. Document Terminology and Conventions




Reference: Additional requirement(s), documents, standards, etc. relating to the function or 533

condition the system must meet. 534

A.1.3 Conformance 535

Requirements listed in this document use the following terminology: 536

SHALL: indicates the definition is an absolute requirement of the specification. 537

SHALL NOT: Indicates the definition is an absolute prohibition of the specification. 538

SHOULD (RECOMMENDED): Indicates there may exist valid reasons or circumstances to omit a 539

particular item, but the full implications must be understood and carefully weighed before 540

choosing a different course. 541

SHOULD NOT (NOT RECOMMENDED): Indicates there may exist valid reasons or 542

circumstances when a particular function of condition is acceptable or even useful, but the full 543

implications should be understood and the case carefully weighed before implementing any 544

function or condition described with this label. 545

MAY (OPTIONAL): Indicates an item is truly optional. Some vendors may choose to include or 546

implement Optional Requirements to add value or enhance their overall product while other 547

vendors may omit the same Optional Requirement to reduce cost, increase time to market, etc. 548

An implementation which does not include an Optional Requirement SHALL be interoperable with 549

implementations which does include the Optional Requirement, though perhaps with reduced 550

functionality. In the same vein an implementation which does include an Optional Requirement 551

SHALL be interoperable with an implementation which does not include the Optional 552

Requirement (with the exception for the feature the option provides). 553




Appendix B. Requirements by System 554

Functional Groups 555

Table 25: Requirements Organized by Functional Groups organizes requirements defined in Chapter 556

3. System Requirements into its functional groups. This organization is intended for ease of use and 557

quick reference during system design. 558

Table 25: Requirements Organized by Functional Groups 559

Functional Group ReqID Description

Bike Racks (RACKS) HUBS-AR2274-V01 The number of bike racks per HUBS location should

be equal to 5% of the total number of parking spaces

or X of daily transit trips, whichever is greater.

Bike Racks (RACKS) HUBS-PR2275-V01 The placement of bike racks shall not impede flow of

vehicle or pedestrian traffic.

Bike Racks (RACKS) HUBS-RG2276-V01 The locations of the bike racks shall be approved by

the City or property owner.

Bike Racks (RACKS) HUBS-PY2278-V01 The bike racks shall be located on paved or pervious,

dust-free surface with a slope no greater than three

percent (3%)

Appendix B. Requirements by System Functional Groups




Bike Racks (RACKS) HUBS-PY2279-V01 The bike racks shall have a vertical clearance of at

least six (6) ft.

Bike Racks (RACKS) HUBS-PY2280-V01 The bike racks shall have an access aisle with a

minimum width of five (5) feet

Bike Racks (RACKS) HUBS-ST2281-V01 The bike racks shall support a bicycle in a stable

upright position.

Bike Sharing

(SHAREBIKE)

HUBS-AR2282-V01 The docking station shall be designed for persistent

always-on availability, maintaining continuous

operation 24 hours a day, 7 days a week, 365 days a

year.

Bike Sharing

(SHAREBIKE)

HUBS-DR2283-V01 The bike share company shall collect and share data

in a manner that does not engage the privacy of the

Citizens.

Bike Sharing

(SHAREBIKE)

HUBS-DR2284-V01 The bike share company shall maintain and share a

list of deployed bikes, listed by unique identifier with

the City monthly.






Bike Sharing

(SHAREBIKE)


list of lost, stolen and vandalized bike with the City

monthly.

Bike Sharing

(SHAREBIKE)


record of maintenance activities including but not

limited to identifiction number and maintenance

performed with the City monthly.

Bike Sharing

(SHAREBIKE)


record of reported collisions with the City monthly.

Bike Sharing

(SHAREBIKE)

HUBS-FN2290-V01 The bike sharing system shall have a docking station

for the bikes.

Bike Sharing

(SHAREBIKE)

HUBS-FN2291-V01 The docking station shall accept a code generated

(through verified payment) for unlocking the bikes.

Bike Sharing

(SHAREBIKE)

HUBS-FN2292-V01 The docking station shall allow the user to enter the

operational status of the just docked bike. The





operational status could include the need for

preventative and repair maintenance.

Bike Sharing

(SHAREBIKE)

HUBS-FN2293-V01 The docking station shall be solar powered.

Bike Sharing

(SHAREBIKE)

HUBS-FN2294-V01 The docking station shall collect the number of bikes

docked.

Bike Sharing

(SHAREBIKE)

HUBS-FN2295-V01 The docking station shall track the % solar charge

complete

Bike Sharing

(SHAREBIKE)

HUBS-FN2296-V01 The docking station shall track the date and time

when a bike in unlocked.

Bike Sharing

(SHAREBIKE)

HUBS-FN2297-V01 The docking station shall track the date and time

when a bike is locked.

Bike Sharing

(SHAREBIKE)

HUBS-FN2298-V01 The docking station shall track the operational status

of the docking station.






Bike Sharing

(SHAREBIKE)

HUBS-MT2299-V01 Each bike shall have a unique identifier that is visible

to the user.

Bike Sharing

(SHAREBIKE)

HUBS-MT2300-V01 Each bike shall have permanently fixed real-time GPS

tracking device in order to track ridership data

Bike Sharing

(SHAREBIKE)

HUBS-PR2301-V01 The bike share company shall not impede flow of


Bike Sharing

(SHAREBIKE)

HUBS-PR2302-V01 The bikes parked in violation of the permit or other

Federal or City codes or are vandalized or inoperatble

shall be re-parked in a correct manner or removed

within four (4) hours of receiving the notices.

Bike Sharing

(SHAREBIKE)

HUBS-RG2303-V01 The docking stations shall be primarily located within

the public right-of-way, along public streets and

sidewalks, parks, trails, parking lots/garages, events

venues, etc. or be located on private property,

provided that the property owner agrees to allow 24/7

public access to the Docking station.





Bike Racks

(SHAREBIKE)

HUBS-PY2305-V01 The docking station shall be located on paved or

pervious surface with a slope of less than three

percent (3%)

Bike Sharing

(SHAREBIKE)

HUBS-PY2306-V01 The docking station shall have a vertical clearance of

at least six (6) feet.

Bike Sharing

(SHAREBIKE)

HUBS-PY2307-V01 The docking station shall have an access aisle with a

minimum width of five (5) feet.

Bike Sharing

(SHAREBIKE)

HUBS-SR2308-V01 The docking station shall permit the locking of the

bicycle frame and one (1) wheel to the rack.

Bike Sharing

(SHAREBIKE)

HUBS-ST2309-V01 The docking station shall support a bicycle in a stable

upright position.

Car Sharing

(SHARECAR)

HUBS-FN2310-V01 The car share system shall have dedicated parking lot

for car share vehicles at the HUBS facility.






Car Sharing

(SHARECAR)

HUBS-PY2312-V01 The parking lots shall have a vertical clearance of at

least twelve (12) feet.

Car Sharing

(SHARECAR)

HUBS-PY2313-V01 The parking lots shall be located on paved or pervious

surfaces with a slope of less than three percent (3%).

Car Sharing

(SHARECAR)

HUBS-ST2314-V01 The vehicles shall be parked only within designated

parking spots at HUBS.

Comprehensive Trip

Planning (CTP)

HUBS-IF2315-V01 The CPS application shall be deployed and available

for use at the IK display through the MMTPA

application.

Comprehensive Trip

Planning (CTP)

HUBS-IF2316-V01 The MMTPA application shall be deployed and

available for use at the IK display.

Emergency Call

Button (ECB)

HUBS-EN2317-V01 The ECB service shall undergo end-to-end testing by

vendor on an annual basis.





Emergency Call

Button (ECB)

HUBS-AR2318-V01 The ECB service shall be made available 24 hours a

day, 7 days a week, 365 days a year.

Emergency Call

Button (ECB)

HUBS-DR2320-V01 ECB shall be record the time, date, and location upon

activation.

Emergency Call

Button (ECB)

HUBS-DR2321-V01 The street address of the HUBS facility shall be sent

to the CECC to notify dispatchers of location of the

help request.

Emergency Call

Button (ECB)

HUBS-FN2322-V01 The ECB shall be capable of interfacing with the E911

telephone system.

Emergency Call

Button (ECB)

HUBS-FN2323-V01 When an ECB alarm is triggered, the ECB system

shall perform the following functions (1) sound a loud

noise for perimeter awareness, (2) establish a

bidirectional voice-enabled communication medium

from the IK to the Columbus Emergency Call Center

(CECC) (3) activate the IK camera and send the video

stream to the CECC.






Emergency Call

Button (ECB)

HUBS-IF2325-V01 A (hardware or software) Emergency Call Button

(ECB) interface shall be designed for public users to

alert the Columbus Emergency Call Center officials in

an emergency situation.

Interactive Kiosk

(KIOSK)

HUBS-AR2326-V01 The Kiosk system shall incorporate system

redundancies to the extent practical to guard against

failure of individual hardware, software, network, or

communications components and ensure maximum,

persistent always-on availability,

maintaining continuous operation 24 hours a day, 7

days a week, 365 days a year.

Interactive Kiosk

(KIOSK)

HUBS-DP2327-V01 Replacement and disposal of damaged parts on kiosk

shall be performed by vendor.

Interactive Kiosk

(KIOSK)

HUBS-DR2328-V01 The Kiosk touch screen interface shall allow Travelers

to access data contained in the Operating System

through the MMTPA application such as schedule

information, static service information (e.g. fares), trip

planning information, real-time service information,

transit bulletins, and maps.

Interactive Kiosk

(KIOSK)

HUBS-DR2329-V01 The Kiosk touch screen interface content shall include

static and real-time traveler information to the extent

that each data element is available from the Operating

System retrieved through the GTFS Real-time data





feed. Arrivals in the next hour for that location should

be displayed on the screen.

Interactive Kiosk

(KIOSK)

HUBS-EN2330-V01 The Kiosk system shall contain the minimum required

system components for touch screen kiosk products,

including (a) the kiosk display strategically installed at

six SMH locations as outlined in Chapter 2, (b) the

kiosk software installed over an existing operating

system (Latest version of Windows, Linux, or

Raspberry OS) as outlined by the product's system

requirements, (c) back-office application server (d)

back-office database (e) back-office storage drives

and, (f) back-office backup drives.

Interactive Kiosk

(KIOSK)

HUBS-EN2331-V01 All hardware shall under go testing procedures and

shall include (1) factory acceptance testing, (2)

installation testing, and (3) performance testing.

Interactive Kiosk

(KIOSK)

HUBS-EN2332-V01 The system shall be designed with an open

architecture intended to facilitate expansion of the

functionality and/or scale of the IK system as new

data sources, applications, features, standards, and/or

technologies emerge in the future.

Interactive Kiosk

(KIOSK)

HUBS-EN2333-V01 The touch screen interface design elements and page

renderings shall be flexible to enable future

enhancements as information and data quantity and

quality improves/evolves over time, including modular






graphics, design templates controlling color schemes,

fonts, backgrounds, etc., and implementation of web

development best practices, version control, notation,

and documentation.

Interactive Kiosk

(KIOSK)

HUBS-FN2335-V01 The IK system shall support multiple languages. At a

minimum, English and Spanish shall be supported.

The system shall maintain English as its default

language setting and provide users the ability to select

a language of choice.

Interactive Kiosk

(KIOSK)

HUBS-FN2336-V01 The system shall detect and automatically notify the

IK system administrator when a functional abnormality

has occurred such as (1) inability to communicate

through an interface, (2) inability to send/receive data,

(3) service requests and queries extend longer than

ten seconds, (3) invalid or missing data has been

detected.

Interactive Kiosk

(KIOSK)

HUBS-FN2337-V01 The system shall incorporate automation tools to

enable automatic resolution of system abnormalities,

security incidents, faults, and errors (to the extent

possible).

Interactive Kiosk

(KIOSK)

HUBS-FN2338-V01 All communications links shall utilize Transmission

Control Protocol/Internet Protocol (TCP/IP) and





possess high-speed bandwidth and availability to

perform the functionalities described within this SyRS.

Interactive Kiosk

(KIOSK)

HUBS-FN2339-V01 All system errors, warnings, and self-correcting

actions shall be recorded in an exportable ASCII text

file system log.

Interactive Kiosk

(KIOSK)

HUBS-FN2340-V01 The system shall incorporate automatic shut down

and restart features that preserve system integrity and

minimizes potential damage in the event of power

failures.

Interactive Kiosk

(KIOSK)

HUBS-FN2341-V01 The IK system shall limit the use of internet to the

approved applications, services, and features offered

through the interactive display, including trip planning

and payment via MMTPA/CPS, Emergency Call

Button, and USB Charging.

Interactive Kiosk

(KIOSK)

HUBS-FN2342-V01 The system shall be designed for unattended

operation under normal circumstances, exclusive of

manual data entry, public user access, and routine

administrative functions.






Interactive Kiosk

(KIOSK)

HUBS-FN2343-V01 The Operating System shall be used to capture HUBS

traveler behavior, visualizations and other data-related

business insights.

Interactive Kiosk

(KIOSK)

HUBS-FN2344-V01 IK touch screen content shall allow customers to view

information and the format shall be configurable to

support kiosks for different operating locations and

functionality, including location awareness and SMH

services offered at each particular location.

Interactive Kiosk

(KIOSK)

HUBS-FN2345-V01 The public touch screen interface shall prohibit

unauthorized users from accessing the operating

system or any GUI, kiosk, or network controls or

settings.

Interactive Kiosk

(KIOSK)

HUBS-FN2346-V01 The touch screen interface and its controls shall

conform to the applicable accessibility requirements of

the Americans with Disabilities Act (ADA).

Interactive Kiosk

(KIOSK)

HUBS-FN2347-V01 The touch screen interface shall be designed to

withstand intentional or unintentional misuse (e.g.

repeated tapping of keys) without system malfunction.





Interactive Kiosk

(KIOSK)

HUBS-FN2348-V01 The touch screen interface shall maintain a unique

identifier for each kiosk in order to diagnose system

malfunctions, provide information to the ECB service,

as well as customize content per SMH location

(location awareness).

Interactive Kiosk

(KIOSK)

HUBS-FN2349-V01 The touch screen interface shall not permit access to

data integrated through IK system interfaces that are

deemed to be confidential or inappropriate for public

use.

Interactive Kiosk

(KIOSK)

HUBS-FN2350-V01 The touch screen interface shall utilize a commercial

off-the-shelf Kiosk Operating System (KOS) that

resides on top of the PC Operating System (Latest

version of Windows, Linux, or Raspberry OS), in

accordance with the software requirements outlined in

this SyRS.

Interactive Kiosk

(KIOSK)

HUBS-FN2351-V01 Where source data is not available in real-time, the

touchscreen shall utilize PDF and/or service board

websites in the short term such as transit route maps,

location specific services or tourism information, etc.

Interactive Kiosk

(KIOSK)

HUBS-FN2352-V01 The standby screen may incorporate a demonstration

of the use of the screen, general information, and/or

animation.






Interactive Kiosk

(KIOSK)

HUBS-FN2353-V01 The touch screen shall display a static or animated

screen or series of screens when the kiosk is not in

use (as determined by a preset standby period of

inactivity).

Interactive Kiosk

(KIOSK)

HUBS-FN2354-V01 Users shall exit standby mode by touching the screen

or activating any other kiosk controls. When standby

mode is exited, the system shall display an initial start

page with links to various sub-menus and content

pages that allow the user to reach all information

contained within the system.

Interactive Kiosk

(KIOSK)

HUBS-IF2355-V01 The kiosk shall provide a secured, direct-connect

interface to facilities for operational administration

through a wireless network interface card (NIC) or a

local fiber resource.

Interactive Kiosk

(KIOSK)

HUBS-IF2356-V01 The IK system shall provide access to a web or app

based interface with the MMTPA/CPS system to

provide comprehensive trip planning services and

disseminate information regarding mobility providers,

parking providers, and availability of various modes of

transportation to the traveling public.





Interactive Kiosk

(KIOSK)

HUBS-IF2357-V01 The interface to other HUB services offered at the

HUBS location (e.g. Car, Bike, and Ride Sharing) shall

be provided through the MMTPA/CPS interface, which

provides comprehensive trip planning services for the

HUBS traveler.

Interactive Kiosk

(KIOSK)

HUBS-IF2359-V01 The IK touch screen shall provide users with a link to

display any current system-wide or other alerts that

describe events having a significant impact on transit

services.

Interactive Kiosk

(KIOSK)


the COTA Real-Time Display.

Interactive Kiosk

(KIOSK)


various static maps.

Interactive Kiosk

(KIOSK)


Visitor Information, which includes location-aware

content.






Interactive Kiosk

(KIOSK)

HUBS-IF2363-V01 The IK display should include a minimum of X USB

ports for charging mobile devices to HUBS travelers.

Interactive Kiosk

(KIOSK)

HUBS-IM2364-V01 The IK system shall perform daily background

verification of all external web links and provide

immediate notification to the IK system administrator if

any link fails verification.

Interactive Kiosk

(KIOSK)

HUBS-IM2365-V01 The IK system backup files (server clone snapshot

and data backups) shall be tested quarterly for

recoverability integrity.

Interactive Kiosk

(KIOSK)

HUBS-IM2366-V01 The system shall capture and log all data entered

through the touch screen interface for further analysis

at the back office for purposes of enhancing location

aware services and improving safety at each

designated location.

Interactive Kiosk

(KIOSK)

HUBS-MT2367-V01 The system shall be designed such that administrative

and maintenance activities that require the system to

be taken off line can occur at periods of lowest public

utilization (e.g. overnight) to maintain maximum

system availability for public users.





Interactive Kiosk

(KIOSK)

HUBS-MT2368-V01 The kiosk and back office IK system shall be

maintained by vendor.

Interactive Kiosk

(KIOSK)

HUBS-PY2369-V01 All portions of the hardware and communications

system shall be locked and secured to minimize the

risk of tampering or damage by unauthorized

individuals.

Interactive Kiosk

(KIOSK)

HUBS-PY2370-V01 Equipment shall be oriented and ventilated in a

manner consistent with applicable workplace safety,

ergonomics, and operated within the environmental

parameters recommended by the equipment

manufacturers.

Interactive Kiosk

(KIOSK)

HUBS-PY2371-V01 Hardware shall be protected from environmental perils

during transport, storage, installation, and operation

such as moisture, humidity, weather, dust, smoke,

heat, static electricity, magnetic fields, and vibration.

Interactive Kiosk

(KIOSK)

HUBS-PY2372-V01 The system power supply shall be installed in

accordance with national and local electrical codes

and all central hardware shall be provided with an

adequate supply of continuous AC power (i.e.,

protected from spikes and surges).






Interactive Kiosk

(KIOSK)

HUBS-RG2373-V01 Installation of interactive kiosks in the City shall

comply with building and construction city codes of

Columbus, OH

Interactive Kiosk

(KIOSK)

HUBS-RG2374-V01 The system shall adhere to object-oriented design

principles to facilitate replacement or modification of

individual components of the IK system without

impacting the overall system.

Interactive Kiosk

(KIOSK)

HUBS-RG2375-V01 The system shall adhere to the current guidelines and

principles set forth in the National ITS Architecture

developed by the U.S. Department of Transportation

ITS Joint Program Office.

Interactive Kiosk

(KIOSK)

HUBS-SR2376-V01 The IK system components shall be protected by

firewalls and equipped with security detection,

prevention, and response mechanisms to guard

against intentional and unintentional threats to the

integrity of the system arising from unauthorized

access, computer viruses and worms, system

abnormalities or faults, and other sources of potential

harm.





Interactive Kiosk

(KIOSK)

HUBS-SR2377-V01 The IK system shall accommodate multiple tiers of

user data security to allow distinct privileges to access

data based on user roles (e.g. public user,

administrator, service accounts, City and COTA

personnel, data miner, external agency, etc.)

Interactive Kiosk

(KIOSK)

HUBS-SR2378-V01 The system shall be designed to preserve the privacy

of individual public users of the system and provide

data protection, such as encrypting login credentials,

payment information, and other sensitive data

captured through the kiosk and transmitted over Wi-Fi

or fiber.

Interactive Kiosk

(KIOSK)

HUBS-SR2379-V01 The system shall detect and automatically alert the IK

system administrator when a security incident has

been detected such as (1) kiosk access door has

been opened, (2) cybersecurity alert has been logged

by the unified threat management software (anti-virus,

malware detection, etc.), (3) misuse of kiosk features

such as recreational web browsing through the

interactive display or attempts to intercept

communications between interfaces.

Interactive Kiosk

(KIOSK)

HUBS-SR2380-V01 The integrity of IK system applications,

communications, and network links shall be secured

through mechanisms such as password

authentication.






Park & Ride (PRKRD) HUBS-AR2381-V01 At least one (1) parking space for ADA shall be

available at each of the hub locations for every 30

spaces. One out of six of the ADA spaces must be

van accessable. An accessible car parking space

must be a minimum of 96 inches wide and a van

space must be a minimum of 132 inches wide (a van

space may be 96 inches if the access aisle is 96

inches or wider)

Park & Ride (PRKRD) HUBS-PR2382-V01 The Park and Ride facility shall allow 24/7 public

access to the vehicles.

Park & Ride (PRKRD) HUBS-PR2383-V01 The Park and Ride facility shall allow parked vehicles

to maintain unimpeded access to roadway/driveway

entrances and exits.

Park & Ride (PRKRD) HUBS-PR2384-V01 The Park and Ride facility shall ensure the parked

vehicles do not impede the regular flow of travel in the

public right of way.

Park & Ride (PRKRD) HUBS-PR2385-V01 The Park and Ride facility shall ensure the vehicles

not be parked in a way that impedes the 5 feet

clearance on sidewalks needed for ADA compliance.





Park & Ride (PRKRD) HUBS-PY2386-V01 The Park and Ride facility shall have a vertical

clearance of at least twelve (12) feet.

Park & Ride (PRKRD) HUBS-PY2387-V01 The Park and Ride facility shall have an access aisle

with a minimum width of five (5) feet

Ride Sharing

(SHARERIDE)

HUBS-FN2388-V01 The ride share system shall have designated curb

space allocated for pick-up from rideshare and taxi

services.

Ride Sharing

(SHARERIDE)

HUBS-IF2389-V01 The ride sharing service shall be provided through the

MMTPA application.

Ride Sharing

(SHARERIDE)

HUBS-MT2390-V01 Each vehicle shall comply with all applicable State

and local laws.

Ride Sharing

(SHARERIDE)

HUBS-MT2391-V01 Each vehicle shall have a unique identifier that is

visible to the user.






Ride Sharing

(SHARERIDE)

HUBS-PR2392-V01 The City may designate parking areas or restrict car

parking within certain areas.

Ride Sharing

(SHARERIDE)

HUBS-RG2393-V01 The locations of the parking lots shall be approved by


USB Charging (USB) HUBS-FN2394-V01 USB charging outlets shall be USB Type A 3.X

standard.

USB Charging (USB) HUBS-FN2395-V01 The USB Charging service shall deliver free charging

for travelers at all SMH locations to charge mobile

devices when in transit.

USB Charging (USB) HUBS-IF2396-V01 USB device charging should be integrated at each IK

display.

USB Charging (USB) HUBS-MT2397-V01 The system contractor shall perform maintenance,

replacement, and annual functional testing for all USB

ports.





USB Charging (USB) HUBS-PY2398-V01 The hardware shall withstand indoor and outdoor

environmental conditions such as high and low

temperatures, humidity, rain, snow, etc.

Wi-Fi Enabled (WIFI) HUBS-AR2399-V01 The Wi-Fi network shall be fault tolerant and maintain

continuous network uptime outside of the scheduled

maintenance, 24-hour per day, 365-day per year.

Wi-Fi Enabled (WIFI) HUBS-DR2400-V01 Wi-Fi enabled technologies shall track number of

clients per access point.

Wi-Fi Enabled (WIFI) HUBS-DR2401-V01 Wi-Fi technologies shall log user connection

timestamp, IP, MAC, OS, device manufacturer, sites

visited, connection status, connection length.

Wi-Fi Enabled (WIFI) HUBS-EN2402-V01 Wi-Fi enabled technologies should be configured to

create wireless mesh network to deliver Wi-Fi service

zone at each facility. The coverage zone enables

mobile users to enter and exit individual access point

surface area without loss of connectivity, seamlessly

transitioning the signal to another access point within

the zone.






Wi-Fi Enabled (WIFI) HUBS-FN2403-V01 HUBS shall permit electronic devices equipped with

internet capabilities (phone, tablet, computer) to

connect to the internet wirelessly using radio waves.

Wi-Fi Enabled (WIFI) HUBS-FN2404-V01 Wi-Fi enabled technologies shall operate

independently and shall not affect or be affected by

other wireless access devices in the event of failure.

Wi-Fi Enabled (WIFI) HUBS-FN2405-V01 HUBS may consider IEEE 802.11ai to enable Fast

Initial Link Set-up (FILS) methods to enhance end-

user experience in high-density WLAN environments.

Wi-Fi Enabled (WIFI) HUBS-FN2406-V01 Wi-Fi technologies shall follow IEEE 802.11 b/g/n

standards to enable multi-gigabit throughput in the 2.4

GHz, 5GHz and 60GHz spectrum bands.

Wi-Fi Enabled (WIFI) HUBS-FN2407-V01 An active session with internet access shall be

provisioned for the user when that user accepts the






Wi-Fi Enabled (WIFI) HUBS-FN2408-V01 An active session with internet access shall not be

provisioned for the user when that user declines the


Wi-Fi Enabled (WIFI) HUBS-IF2409-V01 Wi-Fi services shall be provided by the IK display.

Wi-Fi Network

Maintenance (WIFI)

HUBS-MT2410-V01 Wi-Fi devices shall be managed and maintained by

vendor

Wi-Fi Enabled (WIFI) HUBS-PR2411-V01 Wi-Fi technologies shall support up to X number of

users simultaneously connected.

Wi-Fi Enabled (WIFI) HUBS-PY2412-V01 Wi-Fi equipment shall withstand indoor and outdoor

environmental conditions such as high and low

temperatures, humidity, rain, snow, etc.

Wi-Fi Enabled (WIFI) HUBS-RG2413-V01 Usage on all Wi-Fi technologies shall be limited to

users for recreational purposes (non-business usage)

and to deliver transportation-related services to the

public, including but not limited to comprehensive trip

planning, emergency services, etc.






Wi-Fi Enabled (WIFI) HUBS-RG2414-V01 Users may be redirected to a landing page designated

by vendor or property owner when connecting to Wi-Fi

technologies once the user accepts the terms and


Wi-Fi Enabled (WIFI) HUBS-RG2415-V01 Wi-Fi technologies shall present the user with a

landing page designated by vendor or property owner

to display the Free Wi-Fi terms and conditions of

service and prompt the user to accept.

Wi-Fi Enabled (WIFI) HUBS-SR2416-V01 A timer shall be implemented to track the length of

time a connection has been active.

Wi-Fi Enabled (WIFI) HUBS-SR2417-V01 The load on each access point shall be monitored and

flagged when there is an overloading issue associated

with the access point.

Wi-Fi Enabled (WIFI) HUBS-SR2418-V01 The upload and download speed on each access

point shall be tracked, monitored, and changed as

necessary.





Wi-Fi Enabled (WIFI) HUBS-SR2419-V01 Usage shall be tracked on all Wi-Fi technologies, per

device, in order to validate proper usage of public

wireless as per COTA internet usage policy.

Wi-Fi Enabled (WIFI) HUBS-SR2420-V01 Communications to Wi-Fi hot spots and zones shall

be on a separate VLAN from City networks.

Wi-Fi Enabled (WIFI) HUBS-SR2421-V01 Wi-Fi technologies shall terminate a connection if any

of the following conditions have been met (1) a

violation of Wi-Fi technology usage has been

identified (2) connection has extended beyond 2

hours.

Interactive Kiosk

(KIOSK)

HUBS-FN2422-V01 All visual information should be provided with a TTY

capbaility.

Interactive Kiosk

(KIOSK)

HUBS-FN2423-V01 Kiosk shall include a titanium speaker that can be set

6dB above the ambient noise of the daytime

environment and set to a lower volume at night.






Interactive Kiosk

(KIOSK)

HUBS-FN2441-V01 The system shall reset back to the default language at

the end of a user session or after a period of 2

minutes of inactivity.

Dockless device zone

(DOCKLESS)

HUBS-FN2442-V01 Dedicated paved area shall be made available for

dockless devices (scooters, ebikes, etc.) at the HUBS

facility.


(DOCKLESS)

HUBS-FN2443-V01 Boundaries, symbols and/or text description of

designated area for dockless devices shall be clearly

outlined on pavement with paint.

Ride Sharing

(SHARERIDE)

HUBS-RG2444-V01 The locations of the parking lots shall be approved by



(DOCKLESS)

HUBS-LC2445-V01 Additional space for dockless equipment zone should

be made available if warranted by increased demand

for this service.


(DOCKLESS)

HUBS-RG2447-V01 The locations of the bike racks shall be approved by






Interactive Kiosk

(KIOSK)

HUBS-FN2448-V01 Current transit route maps, location specific services

or tourism information, etc. shall be saved on Kiosk

system so that data is available to be displayed even

during periods of communication failure.

Interactive Kiosk

(KIOSK)

HUBS-FN2449-V01 System files shall be "revolving" or self appending so

that old data is continually overwritten and system

data does not reach capacity of available memory.


(DOCKLESS)

HUBS-PR2450-V01 The dockless parking zone shall not impede flow of


Interactive Kiosk

(KIOSK)

HUBS-PR2451-V01 All software and security systems shall be reviewed

quarterly for updates or as updated as new versions

become availabe.

Interactive Kiosk

(KIOSK)

HUBS-PR2452-V01 Interactive Kiosk displays shall meet City outdoor

advertisement brightness standards and be capable of

adjusting brightness based on varying outside light

conditions.






Interactive Kiosk

(KIOSK)

HUBS-SR2453-V01 All software and security systems shall be reviewed

quarterly for updates or as updated as new versions

become available.

Park & Ride (PRKRD) HUBS-PY2454-V01 The parking lots shall be located on paved or pervious

surfaces with a slope of less than three percent (3%).

Park & Ride (PRKRD) HUBS-LC2455-V01 Additional parking spaces should be made available if

warranted by increased demand for Park & Ride

services.

Bike Racks (RACKS) HUBS-LC2456-V01 Bike racks should be modular in construction so that

additional racks may be installed in the future with

similar overall functional and aesthetic qualities.

Bike Sharing

(SHAREBIKE)

HUBS-LC2457-V01 Docking stations should be modular in construction so

that additional racks may be installed in the future with

similar overall functional and aesthetic qualities.





Car Sharing

(SHARECAR)

HUBS-LC2458-V01 Additional parking spaces should be made available if

warranted by increased demand for car sharing

services.

Ride Sharing

(SHARERIDE)

HUBS-LC2459-V01 Additional space for pick up/drop off zone should be

made available if warranted by increased demand for

ride sharing services.

Interactive Kiosk

(KIOSK)

HUBS-LC2460-V01 The touch screen interface shall be designed with

flexibility to allow future expansion such as

enlargement or the addition of new software tools,

data sources, or other needs that may emerge in the

future.

Bike Sharing

(SHAREBIKE)

HUBS-RG2461-V01 The locations of the docking stations shall be

approved by the City or property owner.





Appendix C. Relationship Matrices

Table 26: User Needs Mapped to Requirements contains a preliminary list of project specific data

elements identified as required for the proper functionality of the system. The list is not meant to be

exhaustive at this time given the evolutionary nature of agile projects, rather provides insight into

where the data may be retrieved.

Table 26: User Needs Mapped to Requirements

User Need ID Requirement ID

HUBS-UN001-v01

HUBS-DR2283-V01

HUBS-DR2284-V01

HUBS-DR2328-V01

HUBS-DR2329-V01

HUBS-UN002-v01

HUBS-DR2285-V01

HUBS-DR2285-V01

HUBS-DR2286-V01

HUBS-LC2460-V01

HUBS-UN003-v01

HUBS-AR2326-V01

HUBS-DP2327-V01

HUBS-DR2328-V01

HUBS-FN2423-V01

HUBS-FN2422-V01

HUBS-FN2441-V01





HUBS-FN2448-V01

HUBS-FN2449-V01

HUBS-PR2451-V01

HUBS-SR2453-V01

HUBS-LC2456-V01

HUBS-LC2457-V01

HUBS-UN004-v01

HUBS-AR2326-V01

HUBS-AR2399-V01

HUBS-DR2400-V01

HUBS-DR2401-V01

HUBS-PR2452-V01

HUBS-UN005-v01

HUBS-PR2275-V01

HUBS-RG2276-V01

HUBS-FN2442-V01

HUBS-FN2443-V01

HUBS-RG2444-V01

HUBS-RG2447-V01

HUBS-PR2450-V01

HUBS-PY2454-V01

HUBS-RG2461-V01






HUBS-UN006-v01

HUBS-AR2326-V01

HUBS-DR2328-V01

HUBS-UN007-v01

HUBS-AR2326-V01

HUBS-DR2321-V01

HUBS-EN2317-V01

HUBS-UN008-v01

HUBS-AR2326-V01

HUBS-UN009-v01

HUBS-DR2328-V01

HUBS-UN010-v01

HUBS-AR2326-V01

HUBS-DR2328-V01

HUBS-UN011-v01

HUBS-AR2274-V01

HUBS-PR2275-V01

HUBS-RG2276-V01

HUBS-AR2282-V01

HUBS-LC2455-V01

HUBS-LC2456-V01

HUBS-LC2445-V01

HUBS-LC2457-V01





HUBS-LC2458-V01

HUBS-LC2459-V01

HUBS-RG2461-V01

HUBS-UN012-v01

HUBS-FN2323-v01

HUBS-UN013-v01

HUBS-DR2329-V01

HUBS-UN014-v01

HUBS-AR2381-V01

HUBS-MT2391-V01

HUBS-MT2390-V01

HUBS-RG2444-V01

HUBS-LC2455-V01

HUBS-LC2445-V01

HUBS-LC2458-V01

HUBS-LC2459-V01

HUBS-UN015-v01

HUBS-AR2318-V01

HUBS-DR2321-V01

HUBS-EN2317-V01

Source: City of Columbus





Table 27: Constraints Needs Mapped to Requirements

Constraint

ID Reference Requirement ID

HUBS-

CN2424-V01

Constraint 1 HUBS-FN2310-V01

HUBS-FN2388-V01

HUBS-

CN2425-V01

Constraint 2

HUBS-

CN2426-V01


HUBS-FN2353-V01

HUBS-

CN2427-V01

Constraint 4 HUBS-RG2276-V01

HUBS-FN2290-V01

HUBS-FN2310-V01

HUBS-FN2388-V01

HUBS-PR2301-V01

HUBS-RG2303-V01

HUBS-PR2383-V01

HUBS-UN014-v01

HUBS-PR2384-V01

HUBS-PR2392-V01

HUBS-RG2393-V01




Constraint

ID Reference Requirement ID

HUBS-

CN2428-V01


HUBS-FN2404-V01

HUBS-FN2405-V01

HUBS-FN2406-V01

HUBS-FN2407-V01

HUBS-FN2408-V01

HUBS-MT2410-V01

HUBS-PR2411-V01

HUBS-

CN2429-V01

Constraint 6

HUBS-

CN2430-V01


HUBS-FN2407-V01

HUBS-FN2408-V01






Table 28: Interfaces Mapped to Requirements

Interface ID Reference Requirement ID

HUBS-

IX2431-V01

Interface 1.1 HUBS-IF2315-V01

HUBS-IF2356-V01

HUBS-IF2357-V01

HUBS-IF2359-V01

HUBS-IF2360-V01

HUBS-IF2361-V01

HUBS-IF2362-V01

HUBS-

IX2432-V01


HUBS-IF2389-V01

HUBS-

IX2433-V01

Interface 2.1 HUBS-DR2321-V01

HUBS-FN2322-V01

HUBS-FN2323-V01

HUBS-IF2325-V01

HUBS-

IX2434-V01

Interface 2.2 HUBS-FN2322-V01

HUBS-FN2323-V01

HUBS-

IX2435-V01

Interface 3 HUBS-IF2355-V01




Interface ID Reference Requirement ID

HUBS-

IX2436-V01

Interface 4 HUBS-RG2413-V01

HUBS-

IX2437-V01

Interface 5 HUBS-IF2363-V01

HUBS-

IX2438-V01


HUBS-

IX2439-V01







Table 29: Related Requirements

Requirement ID Related Requirements

HUBS-ST2281-V01 HUBS-UN001-v01

HUBS-SR2308-V01 HUBS-UN011-v01


HUBS-PY2312-V01 HUBS-UN005-v01

HUBS-UN014-v01


HUBS-UN014-v01


HUBS-UN014-v01

HUBS-IF2362-V01 HUBS-UN010-v01

HUBS-IX2431-V01






HUBS-IX2437-V01

HUBS-IM2364-V01 HUBS-UN003-v01

HUBS-UN006-v01

HUBS-UN010-v01


HUBS-UN003-v01


HUBS-UN003-v01





HUBS-RG2373-V01 HUBS-UN002-v01






HUBS-UN003-v01


HUBS-UN008-v01

HUBS-UN010-v01




HUBS-UN002-v01

HUBS-UN003-v01









HUBS-UN014-v01


HUBS-UN014-v01


HUBS-IX2432-V01


HUBS-IX2439-V01



HUBS-IX2438-V01


HUBS-CN2428-V01


HUBS-CN2428-V01







HUBS-CN2428-V01


HUBS-CN2428-V01


HUBS-CN2428-V01


HUBS-CN2428-V01


HUBS-CN2428-V01


HUBS-CN2428-V01


HUBS-CN2428-V01






HUBS-CN2428-V01


Table 30: Established Relations per Requirement

Requirement ID

Related

User Needs

Related

Constraints

Related

Interfaces

Related

Requirements

HUBS-AR2274-

V01

HUBS-UN011-

v01

HUBS-PR2275-

V01

HUBS-UN011-

v01

HUBS-UN005-

v01

EPM-CN1677-

V01

HUBS-RG2276-

V01

HUBS-UN011-

v01

HUBS-UN005-

v01

HUBS-CN2427-

V01

HUBS-PY2278-

V01

HUBS-UN011-

v01





Requirement ID

Related

User Needs

Related

Constraints

Related

Interfaces

Related

Requirements

HUBS-PY2279-

V01

HUBS-UN011-

v01

HUBS-PY2280-

V01

HUBS-UN011-

v01

HUBS-ST2281-

V01

HUBS-UN001-

v01

HUBS-AR2282-

V01

HUBS-UN011-

v01

HUBS-DR2283-

V01

HUBS-UN001-

v01

HUBS-DR2284-

V01

HUBS-UN001-

v01

HUBS-DR2285-

V01

HUBS-UN002-

v01

HUBS-UN002-

v01

HUBS-DR2286-

V01

HUBS-UN002-

v01

HUBS-DR2287-

V01

HUBS-UN001-

v01

HUBS-FN2290-

V01

HUBS-UN005-

v01

HUBS-UN011-

v01




Requirement ID

Related

User Needs

Related

Constraints

Related

Interfaces

Related

Requirements

HUBS-CN2427-

V01

HUBS-FN2291-

V01

HUBS-UN011-

v01

HUBS-FN2292-

V01

HUBS-UN011-

v01

HUBS-FN2293-

V01

HUBS-UN011-

v01

HUBS-FN2294-

V01

HUBS-UN011-

v01

HUBS-UN001-

v01

HUBS-FN2295-

V01

HUBS-UN001-

v01

HUBS-UN011-

v01

HUBS-FN2296-

V01

HUBS-UN001-

v01

HUBS-UN011-

v01

HUBS-FN2297-

V01

HUBS-UN001-

v01

HUBS-UN011-

v01

HUBS-FN2298-

V01

HUBS-UN001-

v01





Requirement ID

Related

User Needs

Related

Constraints

Related

Interfaces

Related

Requirements

HUBS-UN011-

v01

HUBS-MT2299-

V01

HUBS-UN011-

v01

HUBS-MT2300-

V01

HUBS-UN001-

v01

HUBS-UN011-

v01

HUBS-PR2301-

V01

HUBS-UN005-

v01

HUBS-UN011-

v01

HUBS-CN2427-

V01

HUBS-PR2302-

V01

HUBS-UN005-

v01

HUBS-UN011-

v01

HUBS-RG2303-

V01

HUBS-UN005-

v01

HUBS-UN011-

v01

HUBS-CN2427-

V01

HUBS-PY2305-

V01

HUBS-UN011-

v01




Requirement ID

Related

User Needs

Related

Constraints

Related

Interfaces

Related

Requirements

HUBS-PY2306-

V01

HUBS-UN011-

v01

HUBS-PY2307-

V01

HUBS-UN011-

v01

HUBS-SR2308-

V01

HUBS-UN011-

v01

HUBS-ST2309-

V01

HUBS-UN001-

v01

HUBS-FN2310-

V01

HUBS-UN005-

v01

HUBS-CN2424-

V01

HUBS-CN2427-

V01

HUBS-PY2312-

V01

HUBS-UN005-

v01

HUBS-UN014-

v01

HUBS-PY2313-

V01

HUBS-UN005-

v01

HUBS-UN014-

v01





Requirement ID

Related

User Needs

Related

Constraints

Related

Interfaces

Related

Requirements

HUBS-ST2314-

V01

HUBS-UN005-

v01

HUBS-UN014-

v01

HUBS-IF2315-

V01

HUBS-UN003-

v01

HUBS-IX2431-

V01

HUBS-IF2316-

V01

HUBS-UN003-

v01

HUBS-IX2432-

V01

HUBS-EN2317-

V01

HUBS-UN007-

v01

HUBS-UN015-

v01

HUBS-AR2318-

V01

HUBS-UN015-

v01

HUBS-UN007-

v01

HUBS-DR2320-

V01

HUBS-UN007-

v01

HUBS-UN015-

v01

HUBS-DR2321-

V01

HUBS-UN015-

v01

HUBS-UN007-

v01




Requirement ID

Related

User Needs

Related

Constraints

Related

Interfaces

Related

Requirements

HUBS-IX2433-

V01

HUBS-FN2322-

V01

HUBS-IX2433-

V01

HUBS-IX2434-

V01

HUBS-UN015-

v01

HUBS-FN2323-

V01

HUBS-IX2433-

V01

HUBS-IX2434-

V01

HUBS-UN007-

v01

HUBS-UN015-

v01

HUBS-IF2325-

V01

HUBS-UN007-

v01

HUBS-UN015-

v01

HUBS-IX2433-

V01

HUBS-AR2326-

V01

HUBS-UN003-

v01

HUBS-UN004-

v01

HUBS-UN006-

v01

HUBS-UN007-

v01

HUBS-UN008-

v01

HUBS-UN010-

v01





Requirement ID

Related

User Needs

Related

Constraints

Related

Interfaces

Related

Requirements

HUBS-DP2327-

V01

HUBS-UN003-

v01

HUBS-DR2328-

V01

HUBS-UN001-

v01

HUBS-UN003-

v01

HUBS-UN006-

v01

HUBS-UN009-

v01

HUBS-UN010-

v01

HUBS-DR2329-

V01

HUBS-UN001-

v01

HUBS-UN013-

v01

HUBS-EN2330-

V01

HUBS-UN003-

v01

HUBS-EN2331-

V01

HUBS-UN002-

v01

HUBS-EN2332-

V01

HUBS-UN003-

v01

HUBS-UN008-

v01

HUBS-UN010-

v01




Requirement ID

Related

User Needs

Related

Constraints

Related

Interfaces

Related

Requirements

HUBS-EN2333-

V01

HUBS-UN002-

v01

HUBS-FN2335-

V01

HUBS-UN012-

v01

HUBS-FN2336-

V01

HUBS-UN001-

v01

HUBS-UN002-

v01

HUBS-UN003-

v01

HUBS-UN004-

v01

HUBS-UN006-

v01

HUBS-UN008-

v01

HUBS-UN010-

v01

HUBS-FN2337-

V01

HUBS-UN002-

v01

HUBS-FN2338-

V01

HUBS-UN003-

v01

HUBS-UN004-

v01

HUBS-UN006-

v01

HUBS-UN007-

v01





Requirement ID

Related

User Needs

Related

Constraints

Related

Interfaces

Related

Requirements

HUBS-UN008-

v01

HUBS-UN010-

v01

HUBS-FN2339-

V01

HUBS-UN002-

v01

HUBS-FN2340-

V01

HUBS-UN003-

v01

HUBS-UN004-

v01

HUBS-UN006-

v01

HUBS-UN007-

v01

HUBS-UN008-

v01

HUBS-UN010-

v01

HUBS-FN2341-

V01

HUBS-UN003-

v01

HUBS-FN2342-

V01

HUBS-UN002-

v01

HUBS-UN003-

v01

HUBS-FN2343-

V01

HUBS-UN003-

v01




Requirement ID

Related

User Needs

Related

Constraints

Related

Interfaces

Related

Requirements

HUBS-FN2344-

V01

HUBS-UN001-

v01

HUBS-UN003-

v01

HUBS-UN006-

v01

HUBS-UN010-

v01

HUBS-FN2345-

V01

HUBS-UN002-

v01

HUBS-FN2346-

V01

HUBS-UN008-

v01

HUBS-FN2347-

V01

HUBS-UN002-

v01

HUBS-FN2348-

V01

HUBS-UN002-

v01

HUBS-FN2349-

V01

HUBS-UN002-

v01

HUBS-FN2350-

V01

HUBS-UN002-

v01

HUBS-FN2351-

V01

HUBS-UN003-

v01

HUBS-UN006-

v01

HUBS-UN008-

v01

HUBS-UN010-

v01





Requirement ID

Related

User Needs

Related

Constraints

Related

Interfaces

Related

Requirements

HUBS-CN2426-

V01

HUBS-FN2352-

V01

HUBS-UN003-

v01

HUBS-UN013-

v01

HUBS-FN2353-

V01

HUBS-UN003-

v01

HUBS-UN013-

v01

HUBS-CN2426-

V01

HUBS-FN2354-

V01

HUBS-UN003-

v01

HUBS-UN013-

v01

HUBS-IF2355-

V01

HUBS-UN003-

v01

HUBS-IX2435-

V01

HUBS-IF2356-

V01

HUBS-UN003-

v01

HUBS-IX2431-

V01

HUBS-IF2357-

V01

HUBS-UN003-

v01




Requirement ID

Related

User Needs

Related

Constraints

Related

Interfaces

Related

Requirements

HUBS-IX2432-

V01

HUBS-IF2359-

V01

HUBS-UN010-

v01

HUBS-IX2431-

V01

HUBS-IF2360-

V01

HUBS-UN006-

v01

HUBS-IX2431-

V01

HUBS-IF2361-

V01

HUBS-UN003-

v01

HUBS-UN006-

v01

HUBS-IX2431-

V01

HUBS-IF2362-

V01

HUBS-UN010-

v01

HUBS-IX2431-

V01

HUBS-IF2363-

V01

HUBS-UN009-

v01

HUBS-IX2437-

V01





Requirement ID

Related

User Needs

Related

Constraints

Related

Interfaces

Related

Requirements

HUBS-IM2364-

V01

HUBS-UN003-

v01

HUBS-UN006-

v01

HUBS-UN010-

v01

HUBS-IM2365-

V01

HUBS-UN002-

v01

HUBS-UN003-

v01

HUBS-IM2366-

V01

HUBS-UN001-

v01

HUBS-UN003-

v01

HUBS-MT2367-

V01

HUBS-UN002-

v01

HUBS-MT2368-

V01

HUBS-UN002-

v01

HUBS-PY2369-

V01

HUBS-UN002-

v01

HUBS-PY2370-

V01

HUBS-UN002-

v01




Requirement ID

Related

User Needs

Related

Constraints

Related

Interfaces

Related

Requirements

HUBS-PY2371-

V01

HUBS-UN002-

v01

HUBS-PY2372-

V01

HUBS-UN002-

v01

HUBS-RG2373-

V01

HUBS-UN002-

v01

HUBS-UN003-

v01

HUBS-RG2374-

V01

HUBS-UN003-

v01

HUBS-UN008-

v01

HUBS-UN010-

v01

HUBS-RG2375-

V01

HUBS-UN003-

v01

HUBS-SR2376-

V01

HUBS-UN003-

v01





Requirement ID

Related

User Needs

Related

Constraints

Related

Interfaces

Related

Requirements

HUBS-SR2377-

V01

HUBS-UN001-

v01

HUBS-UN002-

v01

HUBS-UN003-

v01

HUBS-SR2378-

V01

HUBS-UN003-

v01

HUBS-SR2379-

V01

HUBS-UN002-

v01

HUBS-SR2380-

V01

HUBS-UN003-

v01

HUBS-AR2381-

V01

HUBS-UN014-

v01

HUBS-UN005-

v01

HUBS-PR2382-

V01

HUBS-UN005-

v01

HUBS-UN014-

v01

HUBS-PR2383-

V01

HUBS-UN005-

v01

HUBS-CN2427-

V01




Requirement ID

Related

User Needs

Related

Constraints

Related

Interfaces

Related

Requirements

HUBS-UN014-

v01

HUBS-PR2384-

V01

HUBS-UN005-

v01

HUBS-UN014-

v01

HUBS-CN2427-

V01

HUBS-PR2385-

V01

HUBS-UN005-

v01

HUBS-UN014-

v01

HUBS-PY2386-

V01

HUBS-UN005-

v01

HUBS-UN014-

v01

HUBS-PY2387-

V01

HUBS-UN005-

v01

HUBS-UN014-

v01

HUBS-FN2388-

V01

HUBS-UN005-

v01

HUBS-UN014-

v01

HUBS-CN2424-

V01





Requirement ID

Related

User Needs

Related

Constraints

Related

Interfaces

Related

Requirements

HUBS-CN2427-

V01

HUBS-IF2389-

V01

HUBS-UN014-

v01

HUBS-IX2432-

V01

HUBS-MT2390-

V01

HUBS-UN014-

v01

HUBS-MT2391-

V01

HUBS-UN014-

v01

HUBS-PR2392-

V01

HUBS-UN005-

v01

HUBS-UN014-

v01

HUBS-CN2427-

V01

HUBS-RG2393-

V01

HUBS-UN005-

v01

HUBS-UN014-

v01

HUBS-CN2427-

V01

HUBS-FN2394-

V01

HUBS-UN009-

v01

HUBS-FN2395-

V01

HUBS-UN009-

v01




Requirement ID

Related

User Needs

Related

Constraints

Related

Interfaces

Related

Requirements

HUBS-IF2396-

V01

HUBS-UN009-

v01

HUBS-IX2439-

V01

HUBS-MT2397-

V01

HUBS-UN002-

v01

HUBS-UN009-

v01

HUBS-PY2398-

V01

HUBS-UN009-

v01

HUBS-AR2399-

V01

HUBS-UN004-

v01

HUBS-DR2400-

V01

HUBS-UN004-

v01

HUBS-DR2401-

V01

HUBS-UN004-

v01

HUBS-EN2402-

V01

HUBS-UN004-

v01

HUBS-FN2403-

V01

HUBS-UN004-

v01

HUBS-CN2428-

V01

HUBS-CN2430-

V01





Requirement ID

Related

User Needs

Related

Constraints

Related

Interfaces

Related

Requirements

HUBS-FN2404-

V01

HUBS-UN004-

v01

HUBS-CN2428-

V01

HUBS-FN2405-

V01

HUBS-UN004-

v01

HUBS-CN2428-

V01

HUBS-FN2406-

V01

HUBS-UN004-

v01

HUBS-CN2428-

V01

HUBS-FN2407-

V01

HUBS-UN004-

v01

HUBS-CN2428-

V01

HUBS-CN2430-

V01

HUBS-FN2408-

V01

HUBS-UN004-

v01

HUBS-CN2428-

V01

HUBS-CN2430-

V01

HUBS-IF2409-

V01

HUBS-UN004-

v01




Requirement ID

Related

User Needs

Related

Constraints

Related

Interfaces

Related

Requirements

HUBS-IX2438-

V01

HUBS-MT2410-

V01

HUBS-UN004-

v01

HUBS-CN2428-

V01

HUBS-PR2411-

V01

HUBS-UN004-

v01

HUBS-CN2428-

V01

HUBS-PY2412-

V01

HUBS-UN004-

v01

HUBS-CN2428-

V01

HUBS-RG2413-

V01

HUBS-IX2436-

V01

HUBS-UN004-

v01

HUBS-CN2428-

V01

HUBS-RG2414-

V01

HUBS-UN004-

v01

HUBS-CN2428-

V01





Requirement ID

Related

User Needs

Related

Constraints

Related

Interfaces

Related

Requirements

HUBS-RG2415-

V01

HUBS-UN004-

v01

HUBS-CN2428-

V01

HUBS-SR2416-

V01

HUBS-UN004-

v01

HUBS-CN2428-

V01

HUBS-SR2417-

V01

HUBS-UN004-

v01

HUBS-CN2428-

V01

HUBS-SR2418-

V01

HUBS-UN004-

v01

HUBS-CN2428-

V01

HUBS-SR2419-

V01

HUBS-UN004-

v01

HUBS-CN2428-

V01




Requirement ID

Related

User Needs

Related

Constraints

Related

Interfaces

Related

Requirements

HUBS-SR2420-

V01

HUBS-UN004-

v01

HUBS-CN2428-

V01

HUBS-SR2421-

V01

HUBS-UN004-

v01

HUBS-CN2428-

V01

HUBS-FN2422-

V01

HUBS-UN003-

v01

HUBS-FN2423-

V01

HUBS-UN003-

v01

HUBS-FN2441-

V01

HUBS-UN003-

v01

HUBS-FN2442-

V01

HUBS-UN005-

v01

HUBS-FN2443-

V01

HUBS-UN005-

v01

HUBS-RG2444-

V01

HUBS-UN005-

v01

HUBS-UN014-

v01

HUBS-CN2427-

V01





Requirement ID

Related

User Needs

Related

Constraints

Related

Interfaces

Related

Requirements

HUBS-LC2445-

V01

HUBS-UN011-

v01

HUBS-UN014-

v01

HUBS-RG2447-

V01

HUBS-UN005-

v01

HUBS-FN2448-

V01

HUBS-UN003-

v01

HUBS-FN2449-

V01

HUBS-UN003-

v01

HUBS-PR2450-

V01

HUBS-UN005-

v01

HUBS-PR2451-

V01

HUBS-UN003-

v01

HUBS-PR2452-

V01

HUBS-UN004-

v01

HUBS-SR2453-

V01

HUBS-UN003-

v01

HUBS-PY2454-

V01

HUBS-UN005-

v01

HUBS-LC2455-

V01

HUBS-UN011-

v01

HUBS-UN014-

v01

HUBS-LC2456-

V01

HUBS-UN003-

v01




Requirement ID

Related

User Needs

Related

Constraints

Related

Interfaces

Related

Requirements

HUBS-UN011-

v01

HUBS-LC2457-

V01

HUBS-UN003-

v01

HUBS-UN011-

v01

HUBS-LC2458-

V01

HUBS-UN011-

v01

HUBS-UN014-

v01

HUBS-LC2459-

V01

HUBS-UN011-

v01

HUBS-UN014-

v01

HUBS-LC2460-

V01

HUBS-UN002-

v01

HUBS-RG2461-

V01

HUBS-UN005-

v01

HUBS-UN011-

v01




Appendix D. Acronyms and Definitions 1

Table 31: Acronym List contains project specific acronyms used throughout this document. 2

Table 31: Acronym List 3

Abbreviation/Acronym Definition

ADA Americans with Disabilities Act

API Application Programming Interface

ConOps Concept of Operations

COTA Central Ohio Transit Authority

CPS Common Payment System

EV Electric Vehicle

FHWA Federal Highway Administration

IEEE Institute of Electrical and Electronics Engineers

IT Information Technology

ITS Intelligent Transportation System

MMTPA Multimodal Trip Planning Application

PCI Payment Card Industry

PII Personally Identifiable Information

QR Quick Response

RFP Request for Proposal

RFQ Request for Quote

S Scenario

SC Smart Columbus

SCC Smart City Challenge

SCMS Security and Credentials Management System

SOS System of Systems

UC Use Case

Appendix D. Acronyms and Definitions



Abbreviation/Acronym Definition

UI User Interface

USDOT U.S. Department of Transportation





Appendix E. Glossary 5

Table 32: Glossary contains project specific terms used throughout this document. 6

Table 32: Glossary 7

Term Definition

App Software application

Travelers (end users) The Travelers (residents and visitors) in Columbus who will be

interacting with the EPM system to view, plan, reserve, and navigate to

desired parking

Commercial-off-the-shelf

system (COTS)

Software or hardware product that are ready-made and available for

sale to the public

Data Management System

(DMS)

A secure, SaaS web-based application that allows management of an

entire parking meter network

Data privacy The reasonable expectation that data of a sensitive nature will be kept

confidential, sanitized and/or encrypted, and respectfully and

responsibly maintained by all users, managers, and collectors of the

data

Data retention The continued storage of data for compliance or business reasons

Data security The tools, policies, practices, and procedures used to protect data

from being accessed, manipulated or destroyed or being leveraged by

those with a malicious intent or without authorization, as well as the

corrective actions taken when data breaches are suspected or have

been identified.

Dedicated Short Range

Communications (DSRC)

A two-way short- to medium-range wireless communications capability

that permits very high data transmission critical in communications-

based active safety applications

Dependency When one Project, agency, or entity requires data or functionality

provided by another Project, agency, or entity to meet its objectives

Enabling Technologies An innovation that alone or paired with an existing solution produces a

better end user solution at a rapid rate

Experience Columbus An organization whose mission is to market and promote Columbus

services, attractions, and facilities to visitors, meeting planners,

convention delegates, and residents

Appendix E. Glossary



Term Definition

Failure operations When a complete failure of the intersection occurs, primarily due to

loss of power or other malfunctions.

Multimodal transportation Travel that is performed with more than one mode of transportation.

Normal operations When a signalized intersection is cycling through its pre-planned

phases correctly, servicing all approaches, including pedestrian

phases.

Open-data Information that is freely available for anyone to use and republish as

they wish.

Open-source concepts The notion of open collaboration and voluntary contribution for

software development by writing and exchanging programming code.

Personally Identifiable

Information (PII)

Information used in security and privacy laws that can be used to

identify an individual, such as vehicle, traveler, and payment

information.

Parking facility Land or a structure used for light-duty vehicle parking.

Procurement The act of obtaining or acquiring goods, services or works, from a

competitive bidding process.

Real-time data Information that is delivered immediately after collection.

Roadside equipment All equipment located on the roadside, including any or all of the

following items: traffic signal controllers, pedestrian detection

equipment, GPS receiver, a Dedicated Short Range Communication

radio, a processing unit, and an audio pedestrian interface.

System analytics or data

analytics

The analysis of data, procedures or business practices to locate

information which can be used to create more efficient solutions

Third-party Organizations not affiliated with the Smart Columbus Program.

Transportation Network

Companies (TNCs)

Private businesses, non-profits, and quasi-governmental agencies that

offer one or more types of transportation for use in exchange for

payment.

Source: City of Columbus8

U.S. Department of Transportation ITS Joint Program Office – HOIT

1200 New Jersey Avenue, SE Washington, DC 20590

Toll-Free “Help Line” 866-367-7487

www.its.dot.gov

[FHWA-JPO-17-###]

http://www.its.dot.gov/

Documents

System Requirements for Smart Mobility Hubs for the Smart … · 2019-06-26 · Smart Mobility Hubs SyRS for Smart Columbus Demonstration Program – Draft Report | 1 122 Chapter