system architecture and standards plan webinar · 3 purpose of this webinar ... webinar content •...

1

SYSTEM ARCHITECTURE AND

STANDARDS PLAN WEBINAR

2

MANDY BISHOP, P.E., SI

City of ColumbusProgram Manager

[email protected]

SPEAKERS

DIANE NEWTON, PMP

HNTBConsultant Program Manager

[email protected]

GUNNAR RHONE, P.E.

HNTBConsultant Systems Engineer

[email protected]

mailto:[email protected]



3

PURPOSE OF THIS WEBINAR

• Share concept development activities from Smart Columbus with stakeholders

WEBINAR CONTENT

• Smart Columbus program overview

• Document purpose and overview

• Development process and tools

• High-level system architecture for Smart Columbus

• Standards

• Lessons learned

• How to stay connected

• Stakeholder Q&A

WEBINAR PROTOCOL

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

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

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

TODAY’S AGENDA

01 |

02 |

03 |

4

SMARTCOLUMBUS OVERVIEW

$40 MILLION78 APPLIED • COLUMBUS WON

5

VISION:

To empower our residents to live their best lives through

responsive, innovative and safe mobility solutions.

MISSION:To demonstrate how an intelligent transportation system and

equitable access to transportation can have positive impacts

on every day challenges faced by cities.

OUTCOMES:

6

USDOT PORTFOLIO

7

USDOT PORTFOLIO

Connected Vehicle Environment

• 100+ roadside units

• 1,500-1,800 on-board units

• 1,240 light duty vehicles

o 430 transit vehicles

o 110 emergency vehicles

o 12 freight vehicles

Connected Electric Autonomous Vehicles

• Scioto Mile Deployment (May Mobility)

o December 2018-September 2019

o 6 vehicles

• Linden Deployment (EasyMile)

o January 2020-January 2021

o 2-3 vehicles

Smart Mobility Hubs

• 6 locations to facilitate first-

mile/last-mile connections

o 2 of the 6 locations are also

CEAV stops

• Anchored by an interactive kiosk

8

USDOT PORTFOLIO

Operating System

• Big data and complex data exchange

• Analytics and visualization

• Data aggregation, fusion and

consumption

• Replicable and scalable

Multimodal Trip Planning App

• Publicly available app (Pivot)

• Backed by Common Payment System

Prenatal Trip Assistance

• Research study to improve

transportation for moms-to-be

• Up to 500 participants

Mobility Assistance

• Research study with app for turn-by-turn

navigation

• Increase independence

• Up to 30 participants

Event Parking Management

• Publicly available app (ParkColumbus)

• Probability of on-street parking

• Reserve private lot/garage spaces

9

SYSTEM ARCHITECTURE AND STANDARDS PLAN: DOCUMENT PURPOSE & OVERVIEW

10

• Define System Architecture

• Identify associated standards

• Document the lessons learned

PURPOSE

11

OVERVIEW

Source: USDOT Architecture Reference for

Cooperative and Intelligent Transportation

• This plan presents the following views for each of

the projects: o Physical View

o Enterprise View

o Communications View

o Functional Viewments

• Standards:o Identifies information exchange needs between systems

that are supported by standards

o Documents applicable standards that will be used to

ensure interoperability

o Identifies needs for new standards in emerging areas

12

OVERVIEW

Project V-Model Agile

Smart Columbus Operating System

Connected Vehicle Environment

Multimodal Trip Planning Application

Common Payment System

Mobility Assistance for People with Cognitive Disabilities

Prenatal Trip Assistance

Smart Mobility Hubs

Event Parking Management

Connected Electric Autonomous Vehicles

• The systems engineering methodology for each project varied

• Architecture development began during the procurement and/or requirements phase for each project◦ Draft followed requirements

◦ Final followed vendor selection and aligned with system design/development

13

ARCHITECTURE VIEWS AND PURPOSE

Source: USDOT Architecture Reference for Cooperative and Intelligent Transportation

14

• Eight Projects:

oFour architectures per project

▪ Multiple figures and tables for each

architecture

• Standards:

oCommunications

oConnected Vehicle

oPrivacy

oQuality

oVehicles

BY THE NUMBERS

352 PAGES

151 TABLES

73 FIGURES

15

DEVELOPMENT PROCESS AND TOOLS

16

GUIDANCE

• National ITS Architecture

• ARC-IT:o ISO/IEC/Institute of Electrical and Electronics Engineers (IEEE)

42010:2011

o Defines data and messages and the full environment in which stakeholder concerns are satisfied

o Four Views:▪ Physical, Enterprise, Communication and Functional

• SET-IT:o Service packages: describe portions of each of the four views that the

Architecture needs to implement a service.

o Not intended to tie to specific technology

• Regional ITS Architecture:o Ohio Statewide ITS Architecture (Mid-Ohio Regional Planning Commission)

17

PROCESS

FINAL

INPUTS CUSTOMIZATION PROGRAM

SET-IT (service packages)

– ARC-IT 8.2

Regional ITS Architecture

Concept of Operations

Requirements

City and engineering teams

Stakeholders

Overlaps

Interfaces

INPUTS CUSTOMIZATION PROGRAM

USDOT Comments

ARC-IT 8.3

Interface Control Document

System Design Document

Architecture Changes and Updates (Agile)

City and engineering teams

Stakeholders

Vendor teams

Overlaps

Interfaces

DRAFT

1818

SCHEDULE

AUG – SEP

2018

OCT – NOV

2018

DEC – FEB

2019

MARCH

2019

APR – SEP

2019

OCT – DEC

2019

JANUARY

2020

FEBRUARY

2020

MARCH

2020

Draft architecture development

(SET-IT)

Review with project teams

Update and document assembly

Submit baseline/final architecture

Project procurement

Project development and design

Updated architecture development

(project design, ARC-IT 8.3, architecture changes, all vendor input)

Review with project and vendor teams

Validation of overlap and interfaces

Editorial and document assembly

Final Smart Columbus architecture

Milestones

19

SYSTEM ARCHITECTURE FOR SMART COLUMBUS DEMONSTRATION

20

PROGRAM ARCHITECTURE

MMTPA Project

CVE Project

SMH Project

CEAV Project CPS Project

EPM Project

MAPCD ProjectPTA Project

Smart Columbus

Operating System

22

CEAV

CEAV Fleet Management SystemMMTPA


2: CEAV Fixed-Route Operations

2 Based on ARC-IT Physical Diagram r2 Jan 6 2020 VBV

SMART COLUMBUSCONNECTE D EL ECTRIC

AUTONOMOUS VEHI CL ES

CEAV SYSTEM BOUNDARY

CEAV FIXED-ROUTE OPERATIONS

CEAV System Operator

Transit Center Fixed-Route Operations

Transit Vehicle Schedule

Management

CEAV Operator

Transit Center Vehicle Assignment

Transit Center Operator Assignment

transit operationspersonnel input

(2A) transit schedule information +transit vehicle operator information

transit operationsstatus

(2C) transit and fare schedules +transit schedule adherence

information

(2B) transit vehicle schedule performance

transit vehicleoperator input

transit vehicleoperator display

transit vehicle operator availability

route assignment

Transit Center Data Collection

(3C) CEAV Archive Data

CEAV API

PHYSICAL ARCHITECTURE VIEW

Other Vehicle OBEs

COTA Back Office


0: CEAV Physical Architecture

2 Physical View Jan 9 2020 VBV



LAYER 0: ALL CEAV SERVICES

(1-2A) Short Range Wireless

Location and Time Data Source

RSECEAV OBE

CEAVCEAV Fleet Management System

MMTPA



CEAV Operator

CEAV Passenger

(1A) Short Range Wireless

(1-2A-D) Wide Area Wireless

Human InterfaceHuman Interface

Human Interface

(1A) Position LocationInterface

(2C) Center to Center

Human Interface


(2-3C) Center to Center


Information Flows

P-Interconnects

Layer 0 Layer 2

Physical

Objects

System Boundary

Functional Objects

24

PHYSICAL LEGEND

25

ENTERPRISE ARCHITECTURE VIEW

MMTPA

City of Columbus

MMTPA Vendor

Personal/Wireless

Devices (PWD)Traveler

COTA Back Office

COTA

Mobility Provider

Central System (MPCS)

Mobility Providers

Common Payment

System (CPS) Back Office

CPS Vendor

Smart Columbus Operating

System (OS)

Interactive Kiosk

Kiosk Vendor

3rd Party Vendors

3rd Party Data Sources


CEAV Fleet Management

System

0: MMTPA

2 Enterprise View (Operations) Jan 21 2020 VBV

SMART COLUMBUSMUL TI-MODAL TRI P

PLANNING APPLICATI ON

Owns +Operates

Owns +Operates +Maintains

Owns +Operates +Maintains City-Traveler MMTPA

Service Usage Agreement

City-Mobility Providers Information Exchange and Action Agreement

City-MMTPA Vendor System O&M Agreement


Expectation of Data Provision





Operates +Owns



Physical Objects

Stakeholders

Roles

Agreements

Expectations

26

ENTERPRISE LEGEND

27

PROGRAM ARCHITECTURE - ENTERPRISE


CEAV Operations

Staff

CEAV Stop Facility Owner

CEAV Operator

EPM VendorParking Facility

Operator

OS Vendor

Parking Operator

PTA Technology

Vendor

Prenatal Traveler

NEMT Mobility Provider

Managed Care Organizations

NEMT Driver

MAPCD Traveler

MAPCD Vendor

Caregiver

OSU

CPS Vendor

Financial Institution

MMTPA Vendor

Traveler

Mobility Providers

3rd Party Vendors

SMH Facility Owners

Kiosks Vendor

Experience Columbus

IK System Administrator

ECC Operator

Franklin County

First Responder

Authorizing Center Operator

Traffic Information

Providers

Private Vehicle Owner

Driver

City of Columbus

COTA

TrCVMS Staff

ODOT

SCMS Provider

TCVMS Staff

GNSS Service Provider

OBE Integrator

RSE Supplier

OBE Installer Garages

Customer Relations Manager

Public Agency Vehicle Owners

Franklin County +

City of Obetz +Construction Contractor +

ODOT

CEAV System Operator - City Information Provision Agreement

CEAV System Operator-CEAV Operator

Subcontractor Agreement

CEAV Operator and CEAV Operations Staff Employment

Agreement

CEAV System Operator-CEAV Stop Facility Owner Agreement

CEAV System Operator-GNSS Service Provider Service Usage

Agreement


Expectation of Data ProvisionExpectation of Data Provision

EPM Vendor-Traveler Service Usage

Agreement

City-EPM Vendor O&M Agreement +

City-EPM Vendor Procurement Agreement

City-Traffic Information Providers Information Provision Agreement

EPM Vendor-Parking Facility Operator Service Usage

Agreement

EPM Vendor-Parking Facility Operator Data Provision Agreement

(MOU)

Parking Facility Operator - Parking Operator Employment Agreement




NEMT Mobility Provider-PTA

Technology Vendor Service Usage

Agreement

City-MCOs Data Sharing Agreement

City-MCOs Reimbursement

Agreement



NEMT Mobility Provider-Driver Service Usage

Agreement

MCOs-PTA Technology Vendor Business Associate Agreement

MCOs-PTA Technology Vendor Service Agreement

MCOs-Prenatal Traveler Service Usage Agreement



OSU-MCOs Data Sharing Agreement

OSU-Prenatal Traveler Information Provision Agreement


City-MAPCD Vendor Information Provision Agreement

MAPCD Vendor-Caregiver Information Provision Agreement

MAPCD Vendor-MAPCD Traveler


OSU-MAPCD Traveler Information Provision

Agreement

OSU-MAPCD Vendor Information Provision

Agreement


City-MAPCD Vendor Operations & Maintenance (O&M) Agreement


CPS Vendor-Traveler CPS Service Usage Agreement

City-CPS Vendor System O&M Agreement

CPS Vendor-Financial Center/Institution

Merchant of Record Agreement

City-CPS Vendor Financial Agreement

CPS Vendor-Mobility Providers Sub-merchant

Agreement


City-Traveler MMTPA Service Usage

Agreement

City-Mobility Providers Information Exchange and Action

Agreement







Expectation of Action +Expectation of Data Provision


City-Facility Owners

Agreement

SMH Facility Owners-Kiosks Vendor Device Placement and Operations Agreement

SMH Facility Owners-Mobility Providers Shared Oprations

Agreement

City-Experience Columbus MOU for Kiosk Provision

City Permits for the Kiosk Installation


Kiosk Vendor-IK System Administrator Employment

Agreement

City-ECC Operator Employment Agreement

Franklin County-ECC Operator

Employment Agreement

Expectation of Action


Kiosks Vendor-Traveler Service Usage Agreement


Data Usage Agreement +System Usage Agreement


City-COTA Information Exchange

Agreement

City-Traffic CV Management Staff Employment Agreement

COTA-Transit CV Management Staff Employment Agreement

City-SCMS Provider Service Agreement

Presumption of Correct Operation


Expectation of Data ProvisionExpectation of Data Provision

Expectation of Information Provision

Brandmotion-Private Vehicle Owner

Application Usage Agreement

City-Private Vehicle Owner Application Usage AgreementCity-Private Vehicle Owner OBE Usage Agreement

City-RSE Supplier Agreement for RSE Devices

OBE Installer-OBE Installer Garages

Agreement for Space Use and Installation

City-Customer Relations Manager

Agreement

OBE Installer-Public Agency Vehicle

Owners/Garages Agreement for Space Use and Installation

City-Public Agency Vehicle Owner OBE Usage Agreement

City-Construction Contractor Agreement for RSU Installation +City-Franklin County-City of Obetz-ODOT-Construction

Contractor Agreement for RSU Installation for County Project

RSE Supplier-Traffic CV Management Staff


Software Development Agreement


ENTERPRISE VIEW -PROGRAM

28

COMMUNICATIONS PROFILE ARCHITECTURE VIEW

World Wide Web Browser / JSON / Wide Area Wireless

FLOWS-SOURCE-DEST

P-OBJECT-SOURCE P-OBJECT-DEST

ITS Application Information LayerINFORMATION-LAYER-STANDARD

Presentation LayerW3C XML, W3C HTML5, IETF JSON,

IETF GZIP, W3C CSS, IETF CSV

Transport LayerIETF TCP

Session LayerIETF TLS, Docker*

Network LayerIETF IPv4, IETF IPv6

Application LayerIETF HTTPS, IEFT SFTP, IETF WebSockets

Data Link LayerWide Area Wireless WAN

Physical LayerWide Area Wireless WAN

Secu

rity

Pla

neIE

TF H

TTP

Aut

h, IE

TF T

LS

ITS Application Information LayerINFORMATION-LAYER-STANDARD

Presentation LayerW3C XML, W3C HTML5, IETF JSON,

IETF GZIP, W3C CSS, IETF CSV

Transport LayerIETF TCP

Session LayerIETF TLS, Docker*

Network LayerIETF IPv4, IETF IPv6

Application LayerIETF HTTPS, IEFT SFTP, IETF WebSockets

Data Link LayerWide Area Wireless WAN

Physical LayerWide Area Wireless WAN

Layers of ARC-IT

Communications Model

Protocols

Destination

Physical Object

Source Physical Object

Information Flow

Communications Profile Name

ITS

Standard

29

Name Source Destination Standard Profile

Intersection

geometry

RSE Emergency

Vehicle OBE

SAE J2735 DSRC-WSMP

COMMUNICATIONS PROFILE ARCHITECTURE VIEW

Profile

StandardSource Physical Object

Information Flow

Destination

Physical Object

30

FUNCTIONAL VIEW - EXAMPLE

Physical Object Functional Object Process

MMTPA MMTPA API Receive Requests and Send Responses

TIC Data Collection Collect Misc. Traveler Information

Collect Transit Operations Data

Collect Multimodal Data

Process and Send Data (to Operating System)

TIC Trip Planning Provide Interface for IK

Provide Interface for Mobility Providers

Provide Interface for COTA Back Office

Provide Trip Planning Information to Traveler

Confirm Traveler's Trip Plan

Provide Operator Interface for Trip Planning Parameters

Manage Traveler Profiles

Process Travel Services Provider Data

Provide Traveler Alert Interface

Provide Vehicle Route Calculation Data

Provide Operator Interface for Route Parameters

Manage Trip History

Collect Feedback

Trip Optimization Provide Multimodal Route Selection

Collect Traffic Data

Calculate Vehicle Route

Select Transit Route

Select Other Routes

Provide Traveler With Optimized Trip Route

Physical Objects

Functional Objects

High-Level

Processes

31

• What we will present today:o Physical Architecture View – Layer 0

o Enterprise Architecture View – Diagram

• What is not discussed (but is in the document):o Physical Architecture View Tables

▪ Elements

▪ Information Flows

▪ Functional Objects

o Functional Architecture View

o Communication Architecture View

o Enterprise Architecture View

▪ Table of Agreement and Status

▪ Roles and Responsibilities by Phase

ARCHITECTURES BY PROJECT

32

SMART COLUMBUS: ARCHITECTURE BY PROJECT

33

OS – PHYSICAL VIEW

Security Management

Information

Management

Data Utilization

MAPCD

EPM Central System (EPMCS)

PTA Central System

COTA Back Office

{Other Authorizing Centers} ex: City of

Columbus and Mobility Providers

CEAV Fleet Management System

Technology

Center

USDOT ITS

Data Hub

Transit CV Management

System


MMTPA

Personal/Wireless Devices (PWD)

OSU Researchers

MCOs

City Parking Meter System

(CPMS)

Traffic Information Provider

Parking Zone Availability

Data Consumers and 3rd Party Developers

OPERATING SYSTEM BOUNDARY

SMART COLUMBUSOPERATING SYSTEM

ALL SERVICE PACKAGES

Everyone

Technology Administration


(2B) Center to Center






Human Interface

(2C) Center to Center(3C) Center to Center

Human Interface

(2C) Center to Center(2C) Center to Center


0: Operating System (Comprehensive)

2 Physical View Dec 23 2019 DN

Interactive Kiosk (IK)Central Management System


Traffic CV Management

System




(2A) Wide Area Wireless








ITS Data

Warehouse

Performance

Monitoring

Applications

SET-IT

SET-IT

34

Operating System Technologies

Security Management3rd Party Vendors

City of Columbus

Information Management

Data Producers

Data UtilizationData

Consumers

EPM Central System

(EPMCS)

MMTPA


Center

Interactive Kiosk (IK) Central

Management System

PTA Central System

COTA

{Other Authorizing Centers}

City of ColumbusMobility Providers


Center

Technology CenterTechnology Administrator

Authorizing Center Operator


Center

MAPCD

COTA Back Office

Parking Zone Availability


(CPMS)

Personal/Wireless

Devices (PWD)

Traveler

Traffic Information

Providers

Data Usage Agreement



Op

erat

es

+O

wns

Technology Service Agreement +Licensing Agreement

Data Usage Agreement + System Usage Agreement



Software Development Agreement

Data Usage Agreement +System Usage Agreement

Operates + Develops +Maintains

Owns/Facilitates

Owns

Smart Columbus Project Centers

ENTERPRISE VIEWSMART COLUMBUSOPERATING SYSTEM

0: Operating System

2 Enterprise View Jan 15 2020 DN



Operates + Operates +Maintains

Operates + Operates +Maintains

Owns + Operates



Note: USDOT ITS Data Hub, OSU Researchers, MCOs, 3rd Party Data Sources are part of Data Consumers and Data Producers.

OS – ENTERPRISE VIEW

3535

CVE – PHYSICAL VIEW

V2V Basic

Safety

Transit Signal

Priority

Freight Signal

Priority

Emergency

Vehicle Preemption

Vehicle-Based

Traffic Surveillance

Intersection

Safety Warning and Collision Avoidance

Curve Speed

Warning

Vehicle

Maintenance

CV System

Monitoring and Management

Security and

Credentials Management

Vehicle OBE

Vehicle System

Remote Vehicle OBE

Location and Time Data

Source


System

School Zone Management

System

Traffic Management

Center


System


System

RSE

Traffic Signal Controller

CORS

Network Time Source

Security Credentials

Management System

Heavy Duty Vehicle OBE

HDV System

Emergency Vehicle OBE

EV System

Transit Vehicle OBE

TrV System

Vehicle Service Center

Field Maintenance

Equipment

LAYER 0: ALL CVE SERVICESSMART COLUMBUSCONNECTED VEHICLEE N V I R O N M E N T

0: CVE: All

2 Based on ARC-IT Physical Diagram r3 Jan 20 2020 JB

Vehicle Operator

(1A) Vehicle On-Board



TrCVMS Staff

TCVMS Staff

(2A) Field to Field

(1D) Center to Field

Human Interface

Human Interface

(2D) Center to Field

(2D) Wide Area Wireless

(2C) Wide Area Wireless



(2B) Center to Field







(1A) Network Time Protocol(2C) Center to Center




(2B-C) Center to Field


Human Interface

(2C) Human Interface




(2-4C-D) Wide Area Wireless

(2-4D) Wide Area Wireless

(2-4D) Wide Area Wireless


Maintenance Field Personnel

Human Interface

(2-4A) Field to Field

Human Interface

CVE SYSTEM BOUNDARY

SET-IT

SET-IT

SET-IT

SET-IT

SET-IT

SET-IT

SET-IT

SET-IT

SET-IT

SET-IT

36

CVE – ENTERPRISE VIEW

Vehicle OBE

Private Vehicle Owner

Driver


System (OS)

City of Columbus

School Zone Management

System

Traffic Management

Center


System

COTA

TrCVMS Staff


System

RSE

Traffic Signal Controller

CORS

ODOT

Network Time Source

Security Credentials

Management System

Heavy Duty Vehicle OBE

Emergency Vehicle OBE

Transit Vehicle OBE

SCMS Provider

TCVMS Staff



Source

OBE Integrator

RSE Supplier

OBE Installer Garages

Customer Relations Manager

Public Agency Vehicle Owners

Vehicle Service Center

Franklin County +

City of Obetz +Construction Contractor +

ODOT

Maintenance Field Personnel

Field Maintenance Equipment

SMART COLUMBUSCONNECTED VEHICLEE N V I R O N M E N T

0: CVE

2 Enterprise View (Operations) Jan 20 2020 JB

Note: Individual Vehicles/Vehicle Systems are not shown for clarity. Vehicles include Vehicle Systems and Vehicle OBEs. Vehicle Owner owns the vehicles and Drivers operate the vehicles and vehicle OBE. Vehicle Usage Agreement may exist between the Driver and Vehicle Owner

City-COTA Information Exchange

Agreement

City-Traffic CV Management Staff


COTA-Transit CV Management Staff Employment Agreement

City-SCMS Provider Service Agreement

Presumption of Correct Operation




Expectation of Information Provision

Brandmotion-Private Vehicle Owner

Application Usage Agreement

City-Private Vehicle Owner Application Usage Agreement

City-Private Vehicle Owner OBE Usage Agreement

City-RSE Supplier Agreement for RSE Devices

OBE Installer-OBE Installer Garages

Agreement for Space Use and Installation

City-Customer Relations Manager Agreement

OBE Installer-Public Agency Vehicle

Owners/Garages Agreement for Space Use and Installation

City-Public Agency Vehicle Owner OBE Usage Agreement

City-Construction Contractor Agreement for RSU Installation +City-Franklin County-City of Obetz-ODOT-Construction Contractor

Agreement for RSU Installation for County Project

RSE Supplier-Traffic CV Management Staff Employment Agreement

37

MMTPA – PHYSICAL VIEW

MMTPA


COTA Back Office

Mobility Provider Central System

(MPCS)

Common Payment System (CPS) Back

Office


(OS)

Interactive Kiosk3rd Party Data Sources


0: MMTPA


MMTPA SYSTEM BOUNDARY

LAYER 0: MMTPA



Traveler






(2B-C) Wide Area Wireless

Human Interface

Human Interface

(2B-C) Wide Area Wireless(2C) Center to Center


Infrastructure

-Provided

Trip Planning

and Route

Guidance

SET-IT

38

MMTPA

City of Columbus

MMTPA Vendor

Personal/Wireless


COTA Back Office

COTA

Mobility Provider

Central System (MPCS)

Mobility Providers

Common Payment


CPS Vendor


System (OS)

Interactive Kiosk

Kiosk Vendor

3rd Party Vendors




System

0: MMTPA




Owns +Operates

Owns +Operates +Maintains

Owns +Operates +Maintains City-Traveler MMTPA










Operates +Owns



MMTPA – ENTERPRISE VIEW

39

CPS – PHYSICAL VIEW

Integrated

Multi-Modal

Electronic

PaymentCommon Payment System (CPS) Back

Office


Financial Centers (FIN)

Interactive Kiosk

COTA Back Office


Mobility Provider Central Systems

(MPCS)

Mobility Provider Payment Equipment

COTA On-Board Payment Equipment

(FBOX)

CPS Web Portal

MMTPA

Service Provider Web Portal

CPS SYSTEM BOUNDARY

SMART COLUMBUSCOMMON PAYMENT

SYSTEM

0: CPS


LAYER 0: CPS



(2C) Center to Field

(1A-C) Center to Center






(2B) Wide Area Wireless

(2B) Center to Field

SET-IT

40

CPS – ENTERPRISE VIEW

COTA Back Office

COTA

City of Columbus

Mobility Provider Central Systems (MPCS)

Mobility Providers

Common Payment


CPS Vendor

Financial Centers (FIN) Financial

Institution

CPS Web Portal

Mobility Provider Payment

Equipment

COTA On-Board Payment

Equipment (FBOX)

Personal/Wireless


Interactive Kiosk

Service Provider Web

Portal

EPM Central System

(EPMCS)

0: CPS


SMART COLUMBUSCOMMON PAYMENT

SYSTEM

CPS Vendor-Traveler CPS Service Usage Agreement


City-Mobility Providers Information Exchange and Action

Agreement

City-CPS Vendor System O&M Agreement




CPS Vendor-Financial Center/Institution

Merchant of Record Agreement

City-CPS Vendor Financial Agreement

City-COTA Agreement

CPS Vendor-Mobility Providers Sub-merchant Agreement


41

MAPCD – PHYSICAL VIEW

MAPCD

Caregiver Personal/Wireless Devices


(OS)

Traveler Personal/Wireless Devices

COTA Back Office

MAPCD SYSTEM BOUNDARY

LAYER 0: MAPCD

SMART COLUMBUSMOBIL ITY ASSISTANCE

FOR PEOPLE WITH COGNI TI VE DISABILI TI ES

0: MAPCD


Caregiver

MAPCD TravelerHuman Interface





Human Interface

Infrastructure-

Provided Trip

Planning and

Route Guidance

SET-IT

42

MAPCD – ENTERPRISE VIEW

MAPCDCity of

Columbus

MAPCD Traveler

MAPCD Vendor

Caregiver

Caregiver Personal/Wireless Devices


System (OS)


OSU

COTACOTA Back

Office

0: MAPCD


SMART COLUMBUSMOBIL ITY ASSISTANCE

FOR PEOPLE WITH COGNI TI VE DISABILI TI ES

City-MAPCD Vendor Information Provision

Agreement

MAPCD Vendor-Caregiver Information Provision Agreement

MAPCD Vendor-MAPCD Traveler


OSU-MAPCD Traveler Information Provision Agreement

OSU-MAPCD Vendor Information Provision Agreement


City-MAPCD Vendor Operations &

Maintenance (O&M) Agreement

Operates +Owns


43

PTA – PHYSICAL VIEW

0: PTA


PTA SYSTEM BOUNDARY

LAYER 0: PTA

SMART COLUMBUSPRE NATAL TRI P

ASSISTANCE

PTA Central System


R4B NEMT Mobility Provider System

MCOs

Driver Personal Information Device


(OS)

OSU Researchers

Cloud Communications

System

Prenatal Traveler

NEMT Driver




Human Interface



(2C) Human Interface(2C) Center to Center

(2C) Center to Center (2-4C) Wide Area Wireless

Wide Area Wireless




Infrastructure-

Provided Trip

Planning and

Route Guidance

SET-IT

44

PTA – ENTERPRISE VIEW

PTA Central System

PTA Technology

Vendor


Prenatal Traveler

R4B NEMT Mobility Provider System

NEMT Mobility Provider

MCOsManaged Care Organizations

Driver Personal Information

DeviceNEMT Driver


System (OS)

City of Columbus

OS Vendor

OSU Researchers

OSU

Cloud Communicatio

ns System

0: PTA


SMART COLUMBUSPRE NATAL TRI P

ASSISTANCE

Employs

NEMT Mobility Provider-PTA Technology Vendor Service Usage Agreement

City-MCOs Data Sharing Agreement

City-MCOs Reimbursement

Agreement



NEMT Mobility Provider-Driver Service Usage Agreement

MCOs-PTA Technology Vendor Business Associate Agreement

MCOs-PTA Technology Vendor Service Agreement

MCOs-Prenatal Traveler Service Usage Agreement



OSU-MCOs Data Sharing Agreement

OSU-Prenatal Traveler Information Provision Agreement


45

SMH – PHYSICAL VIEW

MMTPA

Payment Device

Interactive Kiosk (IK) Central Management

System


Emergency Call Centers

Smart Mobility Hub Facility


Interactive Kiosk

Bike-Share Ride-Hailing

Bike Racks Car-Share

Dockless Parking Electric Vehicle Charging

Park and Ride

COTA Public Transit Stop

3rd Party Data Souces

LAYER O: ALL SMH SERVICESSMART COLUMBUSSMART MOBILITY HUBS

SMH SYSTEM BOUNDARY

0: SMH: All Service Packages

2 Physical View Jan 18 2020 JB

ECC Operator



(1A) Contact or Proximity


Human Interface

Human Interface

Human Interface


(2C) Wide Area Wireless(1-2C) Center to Center

Human Interface

Human Interface


SMH Traveler


First Responder

Human Interface

SITE AMENITIES

Infrastructure-

Provided Trip

Planning and

Route Guidance

Transit Security

Smart Mobility

Hub Amenities

SET-IT

SET-IT

46

SMART COLUMBUSSMART MOBILITY HUBS

MMTPA

City of Columbus

Payment Device

Traveler

Interactive Kiosk (IK) Central Management

System

Personal/Wireless

Devices (PWD)

SMH Facility Owners

Kiosks Vendor

Mobility Providers

Experience Columbus

Interactive Kiosk

3rd Party Vendors

3rd Party Data Souces



System (OS)

Emergency Call Centers

ECC Operator

Franklin County

First Responder

0: SMH

2 Enterprise View (Operations) Jan 18 2020 JB





City-Facility Owners Agreement

SMH Facility Owners-Kiosks Vendor Device Placement and Operations Agreement

SMH Facility Owners-Mobility Providers Shared Oprations

Agreement

City-Experience Columbus MOU for

Kiosk Provision

City Permits for the Kiosk Installation

Operates +Owns


Kiosk Vendor-IK System Administrator Employment

Agreement

OwnsCity-ECC Operator Employment

Agreement

Franklin County-ECC Operator




Kiosks Vendor-Traveler Service

Usage Agreement

SMH – ENTERPRISE VIEW

47

EPM – PHYSICAL VIEW




Office

City Parking Meter System (CPMS)

Ungated Parking Facility (UFAC)

Gated Parking Facility System (GFAC)


(OS)

Parking Operator EPM360 Application

(OPAPP)

Traffic Information Provider

SMART COLUMBUSEVENT PARKI NG MANAGEMENT

0: EPM


EPM SYSTEM BOUNDARY

LAYER 0: EPM

Parking Operator

Traveler

(2A-B) Wide Area Wireless



(1-2B-C) Center to Center


Human Interface

Human Interface

Human Interface

(1-2A-B) Center to Center

(2A) Center to Center



Regional

Parking

Management

SET-IT

48

EPM – ENTERPRISE VIEW

Personal/Wireless


EPM Central System

(EPMCS)

City of Columbus

EPM Vendor

Common Payment


CPS Vendor


(CPMS)

Ungated Parking Facility

(UFAC)

Parking Facility Operator

Gated Parking Facility System

(GFAC)


System (OS)

OS Vendor

Parking Operator EPM360

Application (OPAPP)

Parking Operator

Traffic Information

Providers

SMART COLUMBUSEVENT PARKI NG MANAGEMENT

0: EPM


Owns +Operates

Owns +Operates +Maintains +

Develops

Owns +Operates +Maintains +

Develops

Ow

ns +

Op

erat

es

Owns

EPM Vendor-Traveler Service Usage

Agreement

City-EPM Vendor O&M Agreement +City-EPM Vendor

Procurement Agreement

City-Traffic Information Providers Information Provision

Agreement

EPM Vendor-Parking Facility Operator Service Usage Agreement

EPM Vendor-Parking Facility Operator Data Provision Agreement (MOU)

Parking Facility Operator - Parking

Operator Employment Agreement




Use

s

49

CEAV – PHYSICAL VIEW

Other Vehicle OBEs

COTA Back Office


0: CEAV Physical Architecture

2 Physical View Jan 9 2020 VBV



LAYER 0: ALL CEAV SERVICES

(1-2A) Short Range Wireless

Location and Time Data Source

RSECEAV OBE

CEAVCEAV Fleet Management System

MMTPA


(OS)


CEAV Operator

CEAV Passenger


(1-2A-D) Wide Area Wireless

Human InterfaceHuman Interface

Human Interface



Human Interface




Transit Fixed-

Route

Operations

Transit Fleet

Operations

Transit

Passenger

Counting

Transit Security

Transit

Traveler

Information

Transit Vehicle

Tracking

Autonomous

Vehicle Safety

Systems

V2V Basic

Safety

SET-IT

SET-IT

SET-IT

SET-IT

SET-IT

SET-IT

SET-IT

SET-IT

50


Source


RSE

CEAV OBE


CEAVCEAV Fleet

Management System

MMTPA


System (OS)

City of Columbus

CEAV Operations

Staff

CEAV Stop Facility Owner

CEAV Operator

COTACOTA Back

Office

Other Vehicle OBEs

0: CEAV




CEAV System Operator - City

Information Provision Agreement

CEAV System Operator-CEAV

Operator Subcontractor

Agreement

CEAV Operator and CEAV Operations Staff Employment Agreement

CEAV System Operator-CEAV Stop Facility Owner Agreement

CEAV System Operator-GNSS Service Provider




Operates +Owns +

Maintains


CEAV – ENTERPRISE VIEW

51

RELATIONSHIPS BETWEEN PROJECTS

53

OS POINTS OF INTERFACE

MAPCD

MMTPA


CEAV Fleet

Management System

Transit CV Management System

PTA Central System



traveler archive data

Trip Dataroad network conditions + Data Archive Coordination

EPM Archive Data

CEAV Archive Data

Traffic CV Management System

Data Archive Coordination

CEAV Route

Real-Time Location

Trip and Usage Data

Parking Payment Archival Data

User Feedback

user profile

Parking Availability Probability

Interactive Kiosk (IK)Central Management

System

SMH Archive Data

Data Feeds

Administrative, Health, Usage and Monitoring

SMH Project

MMTPA Project

CEAV Project

MAPCD Project

CVE Project

PTA ProjectEPM Project

54

MMTPA/CPS – SMH – CEAV POINTS OF INTERFACE

MMTPA


Office



Interactive Kiosk

transaction status

payment request

transit schedule adherence information +transit and fare schedules

Request User Profile

user profile

Payment Authorization Code +Verify/Provide Account

Information

traveler payment information +user account setup +

user profile

Verify/Provide Account Information

traveler payment information +user profile

Payment Request Information

Funds Availability Information +transaction status

Funds Availability Information +transaction status

Payment Request Information

trip request +user profile

trip plan

trip plan

trip request +user profile

trip confirmation

trip confirmation

Trip History

Trip Notification and Alerts

trip feedback

TripBookings

Wi-Fi Internet Coordination

SMH Project

CPS Project

MMTPA Project

CEAV Project

55

• Internal◦ Smart Columbus Operating System

• External◦ Vehicle systems

◦ School zone management system

◦ Traffic signal controller

◦ SCMS

◦ CORS

◦ Network time source

◦ Location and time data source

• Interfaces were previously presented in the CVE ICD webinar:◦ https://www.ite.org/events-meetings/ite-calendar/smart-columbus-program-

connected-vehicle-environment-webinar-on-system-design-and-interface-control-document-review/

CVE POINTS OF INTERFACE

https://www.ite.org/events-meetings/ite-calendar/smart-columbus-program-connected-vehicle-environment-webinar-on-system-design-and-interface-control-document-review/

56

COTA POINTS OF INTERFACE

MAPCD

MMTPA


Office

CEAV Fleet

Management System

COTA Back Office

Smart Columbus

Operating System

transit and fare schedules +transit schedule adherence information

Trip Updates

Request Barcode

transit traveler information coordination

Barcode

user profile

MMTPA Project

CEAV Project

MAPCD ProjectCPS Project

transit schedule information + Real-Time Arrivals

OS Project

transit trip request

transit trip plan

trip confirmation

Request User Profile

57

APPLICATION OF ITS AND OTHER STANDARDS

58

ITS STANDARDS

Connected Vehicle

IEEE 1609.2/CAMP SCMS

ISO 19091

SAE J2735-2016

SAE J2945/1

USDOT RSU 4.1

Signal Controller

NTCIP 1202-ASC

Time and Location

NMEA 0183

NTP

NTRIP

Service Positioning

GTFS/GTFS-Realtime

SMART Wayfinding Specification

59

OTHER STANDARDS/REGULATIONS

Vehicle Standards/Regulations

USDOT Autonomous Vehicle-

Related Standardization Activities

FMVSS

Transit Safety Standards

LADOT Mobility Data

Specifications

Privacy Standards/Regulations

HIPAA

PCI-DSS 3.2

SOC 2

Quality Standards/Regulations

AWS Framework

ISO 9001 QMS

60

• Multi-modal transportation:

◦ Applicability of existing transit standards

◦ Mobility Data

▪ Los Angeles Mobility Data Specification

• Common payment:

◦ Certain standards were applied: PCI-DSS

◦ Use of agreements to solidify partnerships, data exchange,

payment flow/process

◦ Opportunities to expand ITS standards in this area

OPPORTUNITIES/NEEDS

61

LESSONS LEARNED

62

LESSONS LEARNED

• Individual project versus program level

• Time management

• Application of SET-IT

o Creating awareness of established services packages and

associated elements

o Standard vs. Personalization vs. Customization

• Consistency between projects

o Clarity in terminology and definitions

• Application of standards

63

PUBLIC COMMENTS NEEDED

Public comment period open for the System Architecture and Standards Plan:

• March 3 to March 17

Where to find it:

1. View the System Architecture and Standards Plan at: https://d2rfd3nxvhnf29.cloudfront.net/2020-02/SCC-B-SASP-UPDATED_2-25-2020.pdf

How to comment:

1. Please email comments to: [email protected]

2. Subject line: SASP Comments

3. Include your contact information

4. State whether or not you represent a vendor interest

https://d2rfd3nxvhnf29.cloudfront.net/2020-02/SCC-B-SASP-UPDATED_2-25-2020.pdf


64

STAY CONNECTED

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

HOW TO STAY CONNECTED

SMART COLUMBUS INQUIRIES:

Alyssa Chenault,

Communications Project Manager

[email protected] Human Use Approval Summary 4/2/20

SMH Test Results and Launch 4/14/20

Upcoming Smart Columbus Webinars:


65

QUESTIONS?

66

SIGN UP FOR OUR E-NEWSLETTERContact:

[email protected]

Smart.Columbus.gov

@SmartCbus

LEARN MORE

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

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

reflect the view of the U.S. Department of Transportation.

67