HART Downtown Tampa Autonomous Transit

Project Description: This project will provide automatic shuttle service to connect the Marion Transit Center with areas of heavy employment centers in downtown Tampa.

Project Status: Planned

Project Stakeholders:

• City of Tampa Smart Mobility Division
• FDOT CO
• Hillsborough Area Regional Transit Authority (HART)
• Tampa Hillsborough Expressway Authority
• Travelers

Project Service Packages:

• PT09: Transit Signal Priority (HART Autonomous Transit)
• PT13: Vehicle Turning Right in Front of a Transit Vehicle (HART Autonomous Transit)
• SU01: Connected Vehicle System Monitoring and Management (HART Autonomous Transit)
• SU04: Map Management (HART Autonomous Transit)
• SU08: Security and Credentials Management (HART Autonomous Transit)
• TI07: In-Vehicle Signage (HART Autonomous Transit)
• TM01: Infrastructure-Based Traffic Surveillance (HART Autonomous Transit)
• TM02: Vehicle-Based Traffic Surveillance (HART Autonomous Transit)
• TM03: Traffic Signal Control (HART Autonomous Transit)
• TM04: Connected Vehicle Traffic Signal System (HART Autonomous Transit)
• VS02: V2V Basic Safety (HART Autonomous Transit)
• VS03: Situational Awareness (HART Autonomous Transit)
• VS13: Intersection Safety Warning and Collision Avoidance (HART Autonomous Transit)

Project Information Flows:

Information Flow	Source Element	Destination Element	Status
equipment control commands	CAV Authorizing Center	THEA CAV Field Equipment	Planned
intersection control status	City of Tampa Field Equipment	THEA CAV Field Equipment	Planned
intersection geometry	CAV-ITS Map Update System	City of Tampa TMC	Planned
intersection geometry	CAV-ITS Map Update System	THEA CAV Field Equipment	Planned
intersection geometry	THEA CAV Field Equipment	Autonomous Shuttle Vehicle	Planned
intersection geometry	THEA CAV Field Equipment	TECO Street Car Line Vehicles	Planned
intersection geometry	THEA CAV Field Equipment	Vehicles	Planned
intersection infringement info	Autonomous Shuttle Vehicle	THEA CAV Field Equipment	Planned
intersection infringement info	Autonomous Shuttle Vehicle	Vehicles	Planned
intersection infringement info	City of Tampa Field Equipment	THEA CAV Field Equipment	Planned
intersection infringement info	Vehicles	Autonomous Shuttle Vehicle	Planned
intersection infringement info	Vehicles	THEA CAV Field Equipment	Planned
intersection safety application info	City of Tampa TMC	THEA CAV Field Equipment	Planned
intersection safety application status	THEA CAV Field Equipment	City of Tampa TMC	Planned
intersection safety warning	THEA CAV Field Equipment	Autonomous Shuttle Vehicle	Planned
intersection safety warning	THEA CAV Field Equipment	Vehicles	Planned
intersection status	THEA CAV Field Equipment	Autonomous Shuttle Vehicle	Planned
intersection status	THEA CAV Field Equipment	TECO Street Car Line Vehicles	Planned
intersection status	THEA CAV Field Equipment	Vehicles	Planned
local signal priority request	HART Transit Vehicles	City of Tampa Field Equipment	Planned
local signal priority request	TECO Street Car Line Vehicles	City of Tampa Field Equipment	Planned
map update notification	CAV Authorizing Center	CAV-ITS Map Update System	Planned
map update notification	City of Tampa TMC	CAV-ITS Map Update System	Planned
map updates	CAV-ITS Map Update System	City of Tampa TMC	Planned
map updates	CAV-ITS Map Update System	THEA CAV Field Equipment	Planned
misbehavior report	Autonomous Shuttle Vehicle	FDOT SCMS	Planned
misbehavior report	City of Tampa TMC	FDOT SCMS	Planned
misbehavior report	HART Transit Operations	FDOT SCMS	Planned
misbehavior report	TECO Street Car Line Dispatch	FDOT SCMS	Planned
misbehavior report	Vehicles	FDOT SCMS	Planned
right-of-way request notification	City of Tampa Field Equipment	City of Tampa TMC	Planned
roadway geometry	CAV-ITS Map Update System	THEA CAV Field Equipment	Planned
roadway geometry	THEA CAV Field Equipment	Autonomous Shuttle Vehicle	Planned
roadway geometry	THEA CAV Field Equipment	Vehicles	Planned
roadway warning system control	City of Tampa TMC	THEA CAV Field Equipment	Planned
RSE application information	CAV Authorizing Center	THEA CAV Field Equipment	Planned
RSE application install/upgrade	CAV Authorizing Center	THEA CAV Field Equipment	Planned
RSE application status	THEA CAV Field Equipment	CAV Authorizing Center	Planned
security credential revocations	FDOT SCMS	Autonomous Shuttle Vehicle	Planned
security credential revocations	FDOT SCMS	City of Tampa TMC	Planned
security credential revocations	FDOT SCMS	HART Transit Operations	Planned
security credential revocations	FDOT SCMS	TECO Street Car Line Dispatch	Planned
security credential revocations	FDOT SCMS	Vehicles	Planned
security credentials	FDOT SCMS	Autonomous Shuttle Vehicle	Planned
security credentials	FDOT SCMS	City of Tampa TMC	Planned
security credentials	FDOT SCMS	HART Transit Operations	Planned
security credentials	FDOT SCMS	TECO Street Car Line Dispatch	Planned
security credentials	FDOT SCMS	Vehicles	Planned
security policy and networking information	FDOT SCMS	Autonomous Shuttle Vehicle	Planned
security policy and networking information	FDOT SCMS	City of Tampa TMC	Planned
security policy and networking information	FDOT SCMS	HART Transit Operations	Planned
security policy and networking information	FDOT SCMS	TECO Street Car Line Dispatch	Planned
security policy and networking information	FDOT SCMS	Vehicles	Planned
signal control commands	City of Tampa TMC	City of Tampa Field Equipment	Planned
signal control plans	City of Tampa TMC	City of Tampa Field Equipment	Planned
signal control status	City of Tampa Field Equipment	City of Tampa TMC	Planned
signal fault data	City of Tampa Field Equipment	City of Tampa TMC	Planned
signal priority status	THEA CAV Field Equipment	HART Transit Vehicles	Planned
signal system configuration	City of Tampa TMC	City of Tampa Field Equipment	Planned
traffic control priority request	TECO Street Car Line Dispatch	City of Tampa TMC	Planned
traffic control priority status	City of Tampa TMC	HART Transit Operations	Planned
traffic control priority status	City of Tampa TMC	TECO Street Car Line Dispatch	Planned
traffic detector control	City of Tampa TMC	City of Tampa Field Equipment	Planned
traffic detector data	City of Tampa Field Equipment	City of Tampa TMC	Planned
traffic monitoring application info	City of Tampa TMC	THEA CAV Field Equipment	Planned
traffic monitoring application status	THEA CAV Field Equipment	City of Tampa TMC	Planned
traffic situation data	THEA CAV Field Equipment	City of Tampa TMC	Planned
transit schedule information	HART Transit Operations	HART Transit Vehicles	Planned
transit vehicle location data	HART Transit Vehicles	HART Transit Operations	Planned
transit vehicle schedule performance	HART Transit Vehicles	HART Transit Operations	Planned
vehicle control event	Autonomous Shuttle Vehicle	Vehicles	Planned
vehicle control event	Vehicles	Autonomous Shuttle Vehicle	Planned
vehicle location and motion	Autonomous Shuttle Vehicle	HART Transit Vehicles	Planned
vehicle location and motion	Autonomous Shuttle Vehicle	THEA CAV Field Equipment	Planned
vehicle location and motion	Autonomous Shuttle Vehicle	Vehicles	Planned
vehicle location and motion	HART Transit Vehicles	Autonomous Shuttle Vehicle	Planned
vehicle location and motion	HART Transit Vehicles	THEA CAV Field Equipment	Planned
vehicle location and motion	HART Transit Vehicles	Vehicles	Planned
vehicle location and motion	TECO Street Car Line Vehicles	THEA CAV Field Equipment	Planned
vehicle location and motion	Vehicles	Autonomous Shuttle Vehicle	Planned
vehicle location and motion	Vehicles	HART Transit Vehicles	Planned
vehicle location and motion	Vehicles	THEA CAV Field Equipment	Planned
vehicle path prediction	Autonomous Shuttle Vehicle	Vehicles	Planned
vehicle path prediction	Vehicles	Autonomous Shuttle Vehicle	Planned
vehicle signage application info	City of Tampa TMC	THEA CAV Field Equipment	Planned
vehicle signage application status	THEA CAV Field Equipment	City of Tampa TMC	Planned
vehicle signage data	HART Transit Vehicles	Autonomous Shuttle Vehicle	Planned
vehicle signage data	HART Transit Vehicles	Vehicles	Planned
vehicle signage data	THEA CAV Field Equipment	Autonomous Shuttle Vehicle	Planned
vehicle signage data	THEA CAV Field Equipment	Vehicles	Planned
vehicle signage local data	City of Tampa Field Equipment	THEA CAV Field Equipment	Planned
vehicle situation data	Autonomous Shuttle Vehicle	THEA CAV Field Equipment	Planned
vehicle situation data	Vehicles	THEA CAV Field Equipment	Planned

Project Functional Requirements (Element - Functional Object):

• Autonomous Shuttle Vehicle - Vehicle Basic Safety Communication
• 2: The vehicle shall provide its location with lane-level accuracy to on-board applications.


• Autonomous Shuttle Vehicle - Vehicle Control Automation
• 1: The vehicle shall monitor the area behind and in front of the vehicle to determine the proximity of other objects to the vehicle.


• Autonomous Shuttle Vehicle - Vehicle Control Warning
• 1: The vehicle shall monitor the area to the sides of the vehicle to determine the proximity of other objects to the vehicle and if a warning is needed.


• Autonomous Shuttle Vehicle - Vehicle Intersection Warning
• 1: Vehicle shall provide vehicle path information to identify if vehicle is performing an unpermitted movement at an intersection such as a stop sign violation or running a red light.


• Autonomous Shuttle Vehicle - Vehicle Map Management
• 1: The Vehicle shall make basemap, roadway geometry, intersection geometry and parking facility geometry information available to other onboard vehicle applications.


• Autonomous Shuttle Vehicle - Vehicle Situation Data Monitoring
• 1: The Vehicle shall obtain data collection parameters from Connected Vehicle Roadside Equipment.


• Autonomous Shuttle Vehicle - Vehicle Traveler Information Reception
• 1: The vehicle shall receive formatted traffic information from a center and present it to the driver.


• CAV Authorizing Center - Center Connected Vehicle Infrastructure Management
• 1: The Center shall be capable of monitoring the operational status of Connected Vehicle Roadside Equipment applications.
• 2: The Center shall be capable of modifying the operational status of Connected Vehicle Roadside Equipment applications.
• 3: The Center shall request Connected Vehicle Roadside Equipment maintenance actions from other responsible centers.
• 4: The Center shall be capable of modifying the operational status of Connected Vehicle Roadside Equipment.
• 5: The Center shall track the status of Connected Vehicle Roadside Equipment maintenance actions.
• 6: The Center shall be capable of installing software applications on Connected Vehicle Roadside Equipment.
• 7: The Center shall accept information from other Centers that indicates which Connected Vehicle Roadside Equipment needs maintenance.


• CAV-ITS Map Update System - Map Management
• 20: The Center shall provide basemap updates to Personal devices.
• 21: The Center shall provide intersection geometry updates to Vehicles.
• 22: The Center shall provide basemap updates to Vehicles.
• 24: The Center shall provide intersection geometry updates to Personal Devices.
• 27: The Center shall provide basemap updates to Connected Vehicle Roadside Equipment.
• 5: The Center shall provide basemap updates to other Centers.


• City of Tampa Field Equipment - Roadway Basic Surveillance
• 1: The field element shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the center for further analysis and storage, under center control.


• City of Tampa Field Equipment - Roadway Signal Control
• 1: The field element shall control traffic signals under center control.
• 10: The field element shall receive request for transit vehicle signal priority.
• 11: The field element shall receive request for commercial vehicle signal priority.
• 14: The field element shall provide data to the Connected Vehicle Roadside Equipment.
• 15: The field element shall receive requests for emergency vehicle signal preemption.
• 6: The field element shall return traffic signal controller operational status to the center.
• 9: The field element shall report current intersection signal timing information to roadside equipment for transmission to connected vehicles.


• City of Tampa TMC - Center Connected Vehicle Infrastructure Management
• 4: The Center shall be capable of modifying the operational status of Connected Vehicle Roadside Equipment.
• 6: The Center shall be capable of installing software applications on Connected Vehicle Roadside Equipment.
• 7: The Center shall accept information from other Centers that indicates which Connected Vehicle Roadside Equipment needs maintenance.


• City of Tampa TMC - Center Map Management
• 1: The Center shall collect updates to basemaps from Map Update Systems .
• 2: The Center shall collect updates to intersection geometry from Map Update Systems.
• 3: The Center shall provide roadway geometry updates to Map Update Systems.
• 4: The Center shall provide intersection geometry updates to Map Update Systems.


• City of Tampa TMC - ITS Management Support
• 1: The ITS Object shall provide its network address, service offerings and metrics characterizing those services to vehicles within the broadcast range of the ITS Object's short range communications equipment.
• 2: The ITS Object shall provide its network address, service offerings and metrics characterizing those services to the Object Registration and Discovery Service.
• 3: The ITS Object shall obtain network addresses from the Object Registration and Discovery Service.
• 4: The ITS Object shall make network address information available to onboard applications.
• 5: The ITS Object shall provide its configuration and operational status information to the Service Monitor
• 6: The ITS Object shall acquire regulatory information relevant to the operation of the ITS Object from the CCMS.


• City of Tampa TMC - ITS Security Support
• 1: The ITS Object shall obtain security policy information from the Cooperative Intelligent Transportation System Credentials Management System (CCMS).
• 10: The ITS Object shall maintain cryptographic secret information so that those secrets are accessible only to ITS Security Support, and not to any other Functional Object.
• 11: The ITS Object shall request pseudonymous credentials from the CCMS.
• 12: The ITS Object shall provide messages (that it receives) that indicate potential misbehavior/malfunction to the CCMS.
• 13: The ITS Object shall request permissions from the Center that manages permissions requests.
• 2: The ITS Object shall request enrollment credentials from the CCMS.
• 3: The ITS Object shall obtain the CCMS' trust credentials.
• 4: The ITS Object shall provide a mechanism for on-board applications to digitally sign messages using keys secured by the CCMS' trust authority.
• 5: The ITS Object shall provide a mechanism for on-board applications to authenticate messages secured by the CCMS' trust authority.
• 6: The ITS Object shall provide a mechanism for on-board applications to encrypt messages using keys secured by the CCMS' trust authority.
• 7: The ITS Object shall provide a mechanism for on-board applications to decrypt messages using keys secured by the CCMS' trust authority.
• 8: The ITS Object shall obtain a list of revoked credentials from the CCMS.
• 9: The ITS Object shall make the list of revoked credentials available to on-board applications.


• City of Tampa TMC - TMC Basic Surveillance
• 1: The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements under remote control of the center.
• 7: The center shall remotely control devices to detect traffic.


• City of Tampa TMC - TMC In-Vehicle Signing Management
• 1: The center shall format and output sign information such as traffic and road conditions to field equipment that supports in-vehicle signage communications.


• City of Tampa TMC - TMC Signal Control
• 1: The center shall remotely control traffic signal controllers.
• 10: The center shall adjust signal timing in respond to a signal prioritization, signal preemption, pedestrian call, multi-modal crossing activation, or other requests for right-of-way.
• 6: The center shall implement control plans to coordinate signalized intersections based on data from sensors.


• City of Tampa TMC - TMC Situation Data Management
• 1: The center shall collect traffic probe data from vehicles via roadside field equipment.


• FDOT SCMS - CCMS Authorization
• 1: The Center shall generate credential identifiers using facilities that are independently owned and operated from one another.


• FDOT SCMS - CCMS Misbehavior Reporting and Action
• 1: The Center shall accept misbehavior reports from ITS Objects.


• FDOT SCMS - CCMS Provisioning
• 1: The Center shall provide security and regulatory policy information to ITS Objects.


• FDOT SCMS - CCMS Revocation
• 1: The Center shall place certificates on the revocation list of those certificates that are associated with misbehavior.


• FDOT SCMS - ITS Security Support
• 1: The ITS Object shall obtain security policy information from the Cooperative Intelligent Transportation System Credentials Management System (CCMS).


• HART Transit Operations - Center Connected Vehicle Infrastructure Management
• 1: The Center shall be capable of monitoring the operational status of Connected Vehicle Roadside Equipment applications.


• HART Transit Operations - ITS Management Support
• 1: The ITS Object shall provide its network address, service offerings and metrics characterizing those services to vehicles within the broadcast range of the ITS Object's short range communications equipment.
• 2: The ITS Object shall provide its network address, service offerings and metrics characterizing those services to the Object Registration and Discovery Service.
• 3: The ITS Object shall obtain network addresses from the Object Registration and Discovery Service.
• 4: The ITS Object shall make network address information available to onboard applications.
• 5: The ITS Object shall provide its configuration and operational status information to the Service Monitor
• 6: The ITS Object shall acquire regulatory information relevant to the operation of the ITS Object from the CCMS.


• HART Transit Operations - ITS Security Support
• 1: The ITS Object shall obtain security policy information from the Cooperative Intelligent Transportation System Credentials Management System (CCMS).
• 10: The ITS Object shall maintain cryptographic secret information so that those secrets are accessible only to ITS Security Support, and not to any other Functional Object.
• 11: The ITS Object shall request pseudonymous credentials from the CCMS.
• 12: The ITS Object shall provide messages (that it receives) that indicate potential misbehavior/malfunction to the CCMS.
• 13: The ITS Object shall request permissions from the Center that manages permissions requests.
• 2: The ITS Object shall request enrollment credentials from the CCMS.
• 3: The ITS Object shall obtain the CCMS' trust credentials.
• 4: The ITS Object shall provide a mechanism for on-board applications to digitally sign messages using keys secured by the CCMS' trust authority.
• 5: The ITS Object shall provide a mechanism for on-board applications to authenticate messages secured by the CCMS' trust authority.
• 6: The ITS Object shall provide a mechanism for on-board applications to encrypt messages using keys secured by the CCMS' trust authority.
• 7: The ITS Object shall provide a mechanism for on-board applications to decrypt messages using keys secured by the CCMS' trust authority.
• 8: The ITS Object shall obtain a list of revoked credentials from the CCMS.
• 9: The ITS Object shall make the list of revoked credentials available to on-board applications.


• HART Transit Operations - Transit Center Priority Management
• 1: The center shall analyze transit vehicle schedule performance to determine the need for priority along certain routes or at certain intersections.
• 2: The center shall send requests for priority along routes or at intersections to traffic management.
• 3: The center shall define business rules that govern use of transit vehicle signal priority, communicate these rules to the transit vehicle, and monitor transit vehicle requests for priority at signalized intersections.


• HART Transit Vehicles - Transit Vehicle Signal Priority
• 1: The transit vehicle shall determine the schedule deviation and estimated times of arrival (ETA) at transit stops.
• 2: The transit vehicle shall send priority requests to traffic signal controllers at intersections, pedestrian crossings, and multimodal crossings on the roads (surface streets) and freeway (ramp controls) network that enable a transit vehicle schedule deviation to be corrected.


• HART Transit Vehicles - Transit Vehicle V2V Safety
• 1: The transit vehicle shall exchange current vehicle location and motion information with other vehicles in the vicinity.
• 2: The transit vehicle shall provide to other vehicles an indication of its intent to leave a transit stop.
• 3: The transit vehicle shall provide a warning to the transit vehicle operator if a nearby vehicle is a collision threat as the transit vehicle prepares to leave a stop or station.
• 4: The transit vehicle shall identify if another vehicle is pulling in front of it to make a right turn using location information received from other vehicles.
• 5: The vehicle shall broadcast transit vehicle behavioral information (pulling out, about to stop, etc.) to other vehicles in the vicinity.
• 6: The vehicle shall acquire transit vehicle trajectory information.


• TECO Street Car Line Dispatch - ITS Security Support
• 1: The ITS Object shall obtain security policy information from the Cooperative Intelligent Transportation System Credentials Management System (CCMS).
• 2: The ITS Object shall request enrollment credentials from the CCMS.
• 3: The ITS Object shall obtain the CCMS' trust credentials.


• TECO Street Car Line Dispatch - Transit Center Fixed-Route Operations
• 1: The center shall generate transit routes and schedules based on such factors as parameters input by the system operator, road network conditions, incident information, operational data on current routes and schedules, and digitized map data.


• TECO Street Car Line Vehicles - Transit Vehicle On-Board Vehicle Signing Communications
• 1: The transit vehicle shall notify nearby vehicles using short range communications when making a passenger stop, merging, and performing other operations that require cooperation from surrounding traffic.


• TECO Street Car Line Vehicles - Transit Vehicle Signal Priority
• 1: The transit vehicle shall determine the schedule deviation and estimated times of arrival (ETA) at transit stops.
• 2: The transit vehicle shall send priority requests to traffic signal controllers at intersections, pedestrian crossings, and multimodal crossings on the roads (surface streets) and freeway (ramp controls) network that enable a transit vehicle schedule deviation to be corrected.


• TECO Street Car Line Vehicles - Transit Vehicle V2V Safety
• 1: The transit vehicle shall exchange current vehicle location and motion information with other vehicles in the vicinity.
• 2: The transit vehicle shall provide to other vehicles an indication of its intent to leave a transit stop.
• 3: The transit vehicle shall provide a warning to the transit vehicle operator if a nearby vehicle is a collision threat as the transit vehicle prepares to leave a stop or station.
• 4: The transit vehicle shall identify if another vehicle is pulling in front of it to make a right turn using location information received from other vehicles.
• 5: The vehicle shall broadcast transit vehicle behavioral information (pulling out, about to stop, etc.) to other vehicles in the vicinity.


• THEA CAV Field Equipment - ITS Management Support
• 1: The ITS Object shall provide its network address, service offerings and metrics characterizing those services to vehicles within the broadcast range of the ITS Object's short range communications equipment.
• 2: The ITS Object shall provide its network address, service offerings and metrics characterizing those services to the Object Registration and Discovery Service.
• 3: The ITS Object shall obtain network addresses from the Object Registration and Discovery Service.
• 4: The ITS Object shall make network address information available to onboard applications.
• 5: The ITS Object shall provide its configuration and operational status information to the Service Monitor
• 6: The ITS Object shall acquire regulatory information relevant to the operation of the ITS Object from the CCMS.


• THEA CAV Field Equipment - ITS Security Support
• 1: The ITS Object shall obtain security policy information from the Cooperative Intelligent Transportation System Credentials Management System (CCMS).
• 10: The ITS Object shall maintain cryptographic secret information so that those secrets are accessible only to ITS Security Support, and not to any other Functional Object.
• 11: The ITS Object shall request pseudonymous credentials from the CCMS.
• 12: The ITS Object shall provide messages (that it receives) that indicate potential misbehavior/malfunction to the CCMS.
• 13: The ITS Object shall request permissions from the Center that manages permissions requests.
• 2: The ITS Object shall request enrollment credentials from the CCMS.
• 3: The ITS Object shall obtain the CCMS' trust credentials.
• 4: The ITS Object shall provide a mechanism for on-board applications to digitally sign messages using keys secured by the CCMS' trust authority.
• 5: The ITS Object shall provide a mechanism for on-board applications to authenticate messages secured by the CCMS' trust authority.
• 6: The ITS Object shall provide a mechanism for on-board applications to encrypt messages using keys secured by the CCMS' trust authority.
• 7: The ITS Object shall provide a mechanism for on-board applications to decrypt messages using keys secured by the CCMS' trust authority.
• 8: The ITS Object shall obtain a list of revoked credentials from the CCMS.
• 9: The ITS Object shall make the list of revoked credentials available to on-board applications.


• THEA CAV Field Equipment - RSE Device Management
• 1: The field element shall monitor the operational status (state of the device, configuration, and fault data) of connected sensors (such as traffic, infrastructure, environmental, security, speed) and devices (such as highway advisory radio, dynamic message signs, automated roadway treatment systems, barrier and safeguard systems, cameras, traffic signals, ramp meters, short range communications equipment, security surveillance equipment).
• 10: The field element shall implement configuration commands received from authorized Field Support Equipment.
• 2: The field element shall send operational status of connected field equipment to the maintenance center.
• 3: The field element shall send collected fault data to the maintenance center for repair.
• 4: The field element shall include a local interface that provides operational status and fault data for connected field equipment to field personnel.
• 5: The field element shall include a local interface that allows field personnel to command diagnostic tests on connected field equipment.
• 6: The field element shall provide operational status information to the Service Monitor.
• 7: The field element shall implement configuration commands received from an authorized Center.
• 8: The field element shall implement operational status commands received from an authorized Center.
• 9: The field element shall implement operational status commands received from authorized Field Support Equipment.


• THEA CAV Field Equipment - RSE Intersection Management
• 1: The field element shall communicate with passing vehicles to provide the current signal phase and timing information for all lanes and approaches at a signalized intersection.


• THEA CAV Field Equipment - RSE Intersection Safety
• 2: The roadway equipment shall communicate with approaching vehicles to alert and warn drivers of potential stop sign, red light, and non-motorized user crossing conflicts or violations.
• 3: The roadway equipment shall collect vehicle path information sent by a vehicle.


• THEA CAV Field Equipment - RSE Map Management
• 1: The field element shall collect broadcasted vehicle location and motion information.
• 10: The field element shall provide intersection geometry updates to proximate Vehicles.
• 11: The field element shall provide parking facility geometry information to proximate Personal devices.
• 12: The field element shall provide roadway geometry updates to proximate Vehicles.
• 2: The field element shall aggregate vehicle location data.
• 3: The field element shall provide roadway geometry update information to proximate Vehicles.
• 5: The field element shall provide intersection geometry update information to proximate Vehicles.
• 7: The field element shall provide intersection geometry update information to proximate Personal devices.
• 8: The field element shall provide vehicle location data to Centers.
• 9: The field element shall provide basemap updates to proximate Vehicles.


• THEA CAV Field Equipment - RSE Situation Monitoring
• 1: The field element shall collect traffic-related data including snapshots of measured speed and heading and events including starts and stops, speed changes, and other vehicle control from vehicles.
• 2: The field element shall collect provide vehicle situation data to a center for archival.
• 3: The field element shall provide data collection parameters to vehicles.


• THEA CAV Field Equipment - RSE Traffic Monitoring
• 1: The field element shall communicate with on-board equipment on passing vehicles to collect current vehicle position, speed, and heading and a record of previous events (e.g., starts and stops, link travel times) that can be used to determine current traffic conditions.
• 2: The field element shall aggregate and forward collected probe information to the center.
• 3: The field element shall aggregate and forward collected probe information to other field elements.


• Vehicles - ITS Management Support
• 6: The ITS Object shall acquire regulatory information relevant to the operation of the ITS Object from the CCMS.


• Vehicles - ITS Security Support
• 1: The ITS Object shall obtain security policy information from the Cooperative Intelligent Transportation System Credentials Management System (CCMS).
• 10: The ITS Object shall maintain cryptographic secret information so that those secrets are accessible only to ITS Security Support, and not to any other Functional Object.
• 11: The ITS Object shall request pseudonymous credentials from the CCMS.
• 12: The ITS Object shall provide messages (that it receives) that indicate potential misbehavior/malfunction to the CCMS.
• 13: The ITS Object shall request permissions from the Center that manages permissions requests.
• 2: The ITS Object shall request enrollment credentials from the CCMS.
• 3: The ITS Object shall obtain the CCMS' trust credentials.
• 4: The ITS Object shall provide a mechanism for on-board applications to digitally sign messages using keys secured by the CCMS' trust authority.
• 5: The ITS Object shall provide a mechanism for on-board applications to authenticate messages secured by the CCMS' trust authority.
• 6: The ITS Object shall provide a mechanism for on-board applications to encrypt messages using keys secured by the CCMS' trust authority.
• 7: The ITS Object shall provide a mechanism for on-board applications to decrypt messages using keys secured by the CCMS' trust authority.
• 9: The ITS Object shall make the list of revoked credentials available to on-board applications.


• Vehicles - Vehicle Basic Safety Communication
• 2: The vehicle shall provide its location with lane-level accuracy to on-board applications.


• Vehicles - Vehicle Control Automation
• 1: The vehicle shall monitor the area behind and in front of the vehicle to determine the proximity of other objects to the vehicle.


• Vehicles - Vehicle Intersection Warning
• 1: Vehicle shall provide vehicle path information to identify if vehicle is performing an unpermitted movement at an intersection such as a stop sign violation or running a red light.


• Vehicles - Vehicle Map Management
• 1: The Vehicle shall make basemap, roadway geometry, intersection geometry and parking facility geometry information available to other onboard vehicle applications.


• Vehicles - Vehicle Situation Data Monitoring
• 1: The Vehicle shall obtain data collection parameters from Connected Vehicle Roadside Equipment.


• Vehicles - Vehicle Traveler Information Reception
• 1: The vehicle shall receive formatted traffic information from a center and present it to the driver.

Standards:

• (None-Data) - Secure Internet (ITS)
• TUF - Secure Internet (ITS)
• US: GTFS real-time - Secure Wireless Internet (ITS)
• US: GTFS static - Secure Wireless Internet (ITS)
• US: Misbehavior reporting - Secure Internet (ITS)
• US: NTCIP Message Sign - SNMPv3/TLS
• US: NTCIP Roadside Unit - SNMPv3/TLS
• US: NTCIP Signal Priority - SNMPv3/TLS
• US: NTCIP Signal System Masters - SNMPv3/TLS
• US: NTCIP Traffic Signal - SNMPv3/TLS
• US: NTCIP Transportation Sensors - SNMPv3/TLS
• US: NTCIP Warning Device - SNMPv3/TLS
• US: SAE Basic Safety Messages - WAVE WSMP
• US: SAE Lane-Level Mapping - Secure Internet (ITS)
• US: SAE Lane-Level Mapping - WAVE WSMP
• US: SAE Other J2735 - Secure Internet (ITS)
• US: SAE Other J2735 - WAVE TCP
• US: SAE Other J2735 - WAVE WSMP
• US: SAE Signal Control Messages - WAVE WSMP
• US: SAE Signal Preemption - WAVE TCP
• US: SAE Traveler Info - WAVE WSMP
• US: Security Credentials - Secure Internet (ITS)
• US: TCIP - Secure Internet (ITS)

Project Operational Concepts:

Roles and Responsibilities

• Travelers
• Operate vehicle.
• Provide vehicle communication of wrong-way driving, collision warning, and location.


• Hillsborough Area Regional Transit Authority (HART)
• Coordinate with the City of Tampa for traffic signal priority.
• Provide autonomous transit shuttle in mixed traffic using autonomous and connected vehicle technologies.


• Tampa Hillsborough Expressway Authority
• Operate traffic network safely and efficiently with utililization of Connected Vehilcle technologies.
• Provides security for CAV communications between vehicles and the roadside.


• City of Tampa Smart Mobility Division
• Obtain traffic images and traffic flow data from City of Tampa CCTVs and field sensors, and maintain operational control of all field equipment.
• Operate traffic network safely and efficiently with utililization of Connected Vehilcle technologies.
• Operate traffic signal systems on city-owned arterials.
• Provides security for CAV communications between vehicles and the roadside.


• FDOT CO
• Provide security and credentials management support and certificates for connected vehicle operations.