Pinellas Connected Community ATCMTD CAV Project

Project Description: The Pinellas Connected Community (PCC) Advanced Transportation and Congestion Management Technologies Deployment (ATCMTD) Connected and Automated Vehicle (CAV) project aims to improve travel times on key corridors in the Pinellas County, which has a high demand arterial network. The project aims to extend the capabilities of the Pinellas Smart City (PSC) Advanced Transportation Management System (ATMS), Connected Mobility Platform (CMP), Connected Mobility Command Center (CMCC), and Smart City Data Platform (SCDP). It includes adding CAV Roadside Units (RSUs) to the existing RSU road network, and intersection video analytics (IVA), mobile video analytics (MVA) and mobile routing analytics (MRA), including hardware and software with PSC ATMS, CMP, CMCC, and SCDP interfaces. The project uses a Decision Support System (DSS) and demand management tool for load balancing and rerouting. The project uses Artificial intelligence (AI) in the IVA and MRA applications to determine congestion and crash risk.

Project Status: Planned

Project Stakeholders:

Project Inventory:

Interconnect and Flow

Diagrams

Project Service Packages:

Project Information Flows:

Information Flow	Source Element	Destination Element	Status
archive status	Pinellas County Connected Mobility Platform(CMP)	911 Emergency Call Centers	Planned
archive status	Pinellas County Connected Mobility Platform(CMP)	City of Clearwater Traffic Control Center	Planned
archive status	Pinellas County Connected Mobility Platform(CMP)	City of St. Petersburg Traffic Control Center	Planned
archive status	Pinellas County Connected Mobility Platform(CMP)	FDOT District 7 Tampa Bay SunGuide Center	Planned
archive status	Pinellas County Connected Mobility Platform(CMP)	Pinellas County Smart City Data Platform(SCDP)	Planned
archive status	Pinellas County Connected Mobility Platform(CMP)	Pinellas County Traffic Management Center	Planned
archive status	Pinellas County Connected Mobility Platform(CMP)	Private Traveler Information Services	Planned
archive status	Pinellas County Connected Mobility Platform(CMP)	PSTA Transit Management Center	Planned
asset ID	Pinellas County Field Equipment	Personnel Device	Planned
asset location safety warning	Pinellas County Traffic Management Center	Pinellas County Maintenance Vehicles	Planned
asset locations	Personnel Device	Pinellas County Traffic Management Center	Planned
asset locations	Pinellas County Maintenance Vehicles	Personnel Device	Planned
asset locations	Pinellas County Maintenance Vehicles	Pinellas County Traffic Management Center	Planned
broadcast traveler information	Pinellas County Traffic Management Center	Private Travelers Personal Computing Devices	Planned
broadcast traveler information	Pinellas County Traffic Management Center	Vehicles	Planned
crossing call	Pedestrians	Pinellas County Field Equipment	Planned
crossing permission	Pinellas County Field Equipment	Pedestrians	Planned
data publication	Pinellas County Connected Mobility Platform(CMP)	Pinellas County Smart City Data Platform(SCDP)	Planned
data query publication	Pinellas County Connected Mobility Platform(CMP)	Pinellas County Smart City Data Platform(SCDP)	Planned
decision support information	FDOT District 7 Tampa Bay SunGuide Center	FHP Vehicles	Planned
decision support information	Pinellas County Traffic Management Center	FHP Vehicles	Planned
device control request	City of Clearwater Traffic Control Center	Pinellas County Traffic Management Center	Planned
device control request	City of St. Petersburg Traffic Control Center	Pinellas County Traffic Management Center	Planned
device control request	FDOT District 7 Tampa Bay SunGuide Center	Pinellas County Traffic Management Center	Planned
device control request	Pinellas County Traffic Management Center	City of Clearwater Traffic Control Center	Planned
device control request	Pinellas County Traffic Management Center	City of St. Petersburg Traffic Control Center	Planned
device control request	Pinellas County Traffic Management Center	FDOT District 7 Tampa Bay SunGuide Center	Planned
device data	City of Clearwater Traffic Control Center	Pinellas County Traffic Management Center	Planned
device data	City of St. Petersburg Traffic Control Center	Pinellas County Traffic Management Center	Planned
device data	FDOT District 7 Tampa Bay SunGuide Center	Pinellas County Traffic Management Center	Planned
device data	Pinellas County Traffic Management Center	City of Clearwater Traffic Control Center	Planned
device data	Pinellas County Traffic Management Center	City of St. Petersburg Traffic Control Center	Planned
device data	Pinellas County Traffic Management Center	FDOT District 7 Tampa Bay SunGuide Center	Planned
device status	City of Clearwater Traffic Control Center	Pinellas County Traffic Management Center	Planned
device status	City of St. Petersburg Traffic Control Center	Pinellas County Traffic Management Center	Planned
device status	FDOT District 7 Tampa Bay SunGuide Center	Pinellas County Traffic Management Center	Planned
device status	Pinellas County Traffic Management Center	City of Clearwater Traffic Control Center	Planned
device status	Pinellas County Traffic Management Center	City of St. Petersburg Traffic Control Center	Planned
device status	Pinellas County Traffic Management Center	FDOT District 7 Tampa Bay SunGuide Center	Planned
emergency archive data	911 Emergency Call Centers	Pinellas County Connected Mobility Platform(CMP)	Planned
environmental conditions data status	Private Weather Information Providers	Pinellas County Traffic Management Center	Planned
equipment control commands	CAV Authorizing Center	Pinellas County CAV Field Equipment	Planned
equipment control commands	Pinellas County Traffic Management Center	Pinellas County CAV Field Equipment	Planned
incident command information coordination	911 Emergency Call Centers	Pinellas County Traffic Management Center	Planned
incident command information coordination	FDOT District 7 Tampa Bay SunGuide Center	Pinellas County Traffic Management Center	Planned
incident command information coordination	Pinellas County Traffic Management Center	911 Emergency Call Centers	Planned
incident information	City of Clearwater Traffic Control Center	Pinellas County Traffic Management Center	Planned
incident information	City of St. Petersburg Traffic Control Center	Pinellas County Traffic Management Center	Planned
incident information	FDOT District 7 Tampa Bay SunGuide Center	Pinellas County Traffic Management Center	Planned
incident information	Pinellas County Traffic Management Center	City of Clearwater Traffic Control Center	Planned
incident information	Pinellas County Traffic Management Center	City of St. Petersburg Traffic Control Center	Planned
incident information	Pinellas County Traffic Management Center	FDOT District 7 Tampa Bay SunGuide Center	Planned
incident scene images	FHP Vehicles	Pinellas County Traffic Management Center	Planned
incident scene status	FHP Vehicles	FDOT District 7 Tampa Bay SunGuide Center	Planned
intersection control status	Pinellas County Field Equipment	Pinellas County CAV Field Equipment	Planned
intersection geometry	CAV-ITS Map Update System	City of Clearwater Traffic Control Center	Planned
intersection geometry	CAV-ITS Map Update System	City of St. Petersburg Traffic Control Center	Planned
intersection geometry	CAV-ITS Map Update System	FDOT District 7 Tampa Bay SunGuide Center	Planned
intersection geometry	CAV-ITS Map Update System	Pinellas County CAV Field Equipment	Planned
intersection geometry	CAV-ITS Map Update System	Pinellas County Traffic Management Center	Planned
intersection geometry	Pinellas County CAV Field Equipment	County Fire EMS/Rescue Vehicles	Planned
intersection geometry	Pinellas County CAV Field Equipment	Pinellas County Maintenance Vehicles	Planned
intersection geometry	Pinellas County CAV Field Equipment	Private Travelers Personal Computing Devices	Planned
intersection geometry	Pinellas County CAV Field Equipment	PSTA Transit Vehicles	Planned
intersection geometry	Pinellas County CAV Field Equipment	Vehicles	Planned
intersection infringement info	Pinellas County CAV Field Equipment	Pinellas County Field Equipment	Planned
intersection infringement info	Vehicles	Pinellas County CAV Field Equipment	Planned
intersection management application info	Pinellas County Traffic Management Center	Pinellas County CAV Field Equipment	Planned
intersection management application status	Pinellas County CAV Field Equipment	Pinellas County Traffic Management Center	Planned
intersection safety application info	Pinellas County Traffic Management Center	Pinellas County CAV Field Equipment	Planned
intersection safety application status	Pinellas County CAV Field Equipment	Pinellas County Traffic Management Center	Planned
intersection safety warning	Pinellas County CAV Field Equipment	Private Travelers Personal Computing Devices	Planned
intersection safety warning	Pinellas County CAV Field Equipment	Vehicles	Planned
intersection status	Pinellas County CAV Field Equipment	County Fire EMS/Rescue Vehicles	Planned
intersection status	Pinellas County CAV Field Equipment	Private Travelers Personal Computing Devices	Planned
intersection status	Pinellas County CAV Field Equipment	PSTA Transit Vehicles	Planned
intersection status	Pinellas County CAV Field Equipment	Vehicles	Planned
intersection status	Pinellas County Field Equipment	Vehicles	Planned
intersection status	Pinellas County Traffic Management Center	County Fire EMS/Rescue Vehicles	Planned
intersection status	Pinellas County Traffic Management Center	FHP Vehicles	Planned
intersection status	Pinellas County Traffic Management Center	PSTA Transit Management Center	Planned
intersection status	Pinellas County Traffic Management Center	PSTA Transit Vehicles	Planned
intersection status	Pinellas County Traffic Management Center	Vehicles	Planned
intersection status	PSTA Transit Management Center	PSTA Transit Vehicles	Planned
intersection status monitoring	Pinellas County CAV Field Equipment	Pinellas County Field Equipment	Planned
local signal preemption request	County Fire EMS/Rescue Vehicles	Pinellas County CAV Field Equipment	Planned
local signal preemption request	County Fire EMS/Rescue Vehicles	Pinellas County Field Equipment	Planned
local signal priority request	PSTA Transit Vehicles	Pinellas County CAV Field Equipment	Planned
local signal priority request	PSTA Transit Vehicles	Pinellas County Field Equipment	Planned
local traveler information	Pinellas County CAV Field Equipment	Pinellas County Maintenance Vehicles	Planned
local traveler information	Pinellas County CAV Field Equipment	Private Travelers Personal Computing Devices	Planned
local traveler information	Pinellas County CAV Field Equipment	Vehicles	Planned
maint and constr archive data	Pinellas County Traffic Management Center	Pinellas County Connected Mobility Platform(CMP)	Planned
maint and constr vehicle location data	Pinellas County Maintenance Vehicles	Pinellas County Traffic Management Center	Planned
maint and constr vehicle operational data	Pinellas County Maintenance Vehicles	Pinellas County Traffic Management Center	Planned
maint and constr vehicle system control	Pinellas County Traffic Management Center	Pinellas County Maintenance Vehicles	Planned
map update notification	City of Clearwater Traffic Control Center	CAV-ITS Map Update System	Planned
map update notification	City of St. Petersburg Traffic Control Center	CAV-ITS Map Update System	Planned
map update notification	FDOT District 7 Tampa Bay SunGuide Center	CAV-ITS Map Update System	Planned
map update notification	Pinellas County Traffic Management Center	CAV-ITS Map Update System	Planned
map updates	CAV-ITS Map Update System	City of Clearwater Traffic Control Center	Planned
map updates	CAV-ITS Map Update System	City of St. Petersburg Traffic Control Center	Planned
map updates	CAV-ITS Map Update System	FDOT District 7 Tampa Bay SunGuide Center	Planned
map updates	CAV-ITS Map Update System	Pinellas County CAV Field Equipment	Planned
map updates	CAV-ITS Map Update System	Pinellas County Traffic Management Center	Planned
map updates	Pinellas County CAV Field Equipment	Pinellas County Maintenance Vehicles	Planned
misbehavior report	City of Clearwater Traffic Control Center	FDOT SCMS	Planned
misbehavior report	City of St. Petersburg Traffic Control Center	FDOT SCMS	Planned
misbehavior report	County Fire EMS/Rescue Vehicles	FDOT SCMS	Planned
misbehavior report	FDOT District 7 Tampa Bay SunGuide Center	FDOT SCMS	Planned
misbehavior report	Personnel Device	FDOT SCMS	Planned
misbehavior report	Pinellas County CAV Field Equipment	FDOT SCMS	Planned
misbehavior report	Pinellas County Maintenance Vehicles	FDOT SCMS	Planned
misbehavior report	Pinellas County Traffic Management Center	FDOT SCMS	Planned
misbehavior report	Private Travelers Personal Computing Devices	FDOT SCMS	Planned
misbehavior report	PSTA Transit Management Center	FDOT SCMS	Planned
misbehavior report	PSTA Transit Vehicles	FDOT SCMS	Planned
misbehavior report	Vehicles	FDOT SCMS	Planned
mixed use crossing status	Pinellas County Field Equipment	Pinellas County CAV Field Equipment	Planned
personal crossing safety information	Pinellas County CAV Field Equipment	Private Travelers Personal Computing Devices	Planned
personal location	Private Travelers Personal Computing Devices	Pinellas County CAV Field Equipment	Planned
personal location	Private Travelers Personal Computing Devices	Vehicles	Planned
personal location information	Pinellas County CAV Field Equipment	Pinellas County Field Equipment	Planned
personal signal service request	Private Travelers Personal Computing Devices	Pinellas County CAV Field Equipment	Planned
personnel location	Personnel Device	Pinellas County Field Equipment	Planned
personnel safety warning	Pinellas County Field Equipment	Personnel Device	Planned
proxied personal location	Pinellas County CAV Field Equipment	Vehicles	Planned
remote vehicle control commands	Personnel Device	Pinellas County Maintenance Vehicles	Planned
right-of-way request notification	Pinellas County Field Equipment	Pinellas County Traffic Management Center	Planned
road network conditions	City of Clearwater Traffic Control Center	Pinellas County Traffic Management Center	Planned
road network conditions	City of St. Petersburg Traffic Control Center	Pinellas County Traffic Management Center	Planned
road network conditions	FDOT District 7 Tampa Bay SunGuide Center	Pinellas County Traffic Management Center	Planned
road network conditions	Pinellas County Traffic Management Center	City of Clearwater Traffic Control Center	Planned
road network conditions	Pinellas County Traffic Management Center	City of St. Petersburg Traffic Control Center	Planned
road network conditions	Pinellas County Traffic Management Center	FDOT District 7 Tampa Bay SunGuide Center	Planned
road weather information	Pinellas County Traffic Management Center	National Weather Service	Planned
road weather information	Pinellas County Traffic Management Center	Private Weather Information Providers	Planned
roadway dynamic signage data	Pinellas County Traffic Management Center	Pinellas County Field Equipment	Planned
roadway dynamic signage status	Pinellas County Field Equipment	Pinellas County Traffic Management Center	Planned
roadway geometry	CAV-ITS Map Update System	Pinellas County CAV Field Equipment	Planned
roadway geometry	Pinellas County CAV Field Equipment	Pinellas County Maintenance Vehicles	Planned
roadway geometry	Pinellas County CAV Field Equipment	Vehicles	Planned
RSE application information	CAV Authorizing Center	Pinellas County CAV Field Equipment	Planned
RSE application information	Pinellas County Traffic Management Center	Pinellas County CAV Field Equipment	Planned
RSE application install/upgrade	CAV Authorizing Center	Pinellas County CAV Field Equipment	Planned
RSE application install/upgrade	Pinellas County Traffic Management Center	Pinellas County CAV Field Equipment	Planned
RSE application status	Pinellas County CAV Field Equipment	CAV Authorizing Center	Planned
RSE application status	Pinellas County CAV Field Equipment	Pinellas County Traffic Management Center	Planned
security credential revocations	FDOT SCMS	City of Clearwater Traffic Control Center	Planned
security credential revocations	FDOT SCMS	City of St. Petersburg Traffic Control Center	Planned
security credential revocations	FDOT SCMS	County Fire EMS/Rescue Vehicles	Planned
security credential revocations	FDOT SCMS	FDOT District 7 Tampa Bay SunGuide Center	Planned
security credential revocations	FDOT SCMS	Personnel Device	Planned
security credential revocations	FDOT SCMS	Pinellas County CAV Field Equipment	Planned
security credential revocations	FDOT SCMS	Pinellas County Maintenance Vehicles	Planned
security credential revocations	FDOT SCMS	Pinellas County Traffic Management Center	Planned
security credential revocations	FDOT SCMS	Private Travelers Personal Computing Devices	Planned
security credential revocations	FDOT SCMS	PSTA Transit Management Center	Planned
security credential revocations	FDOT SCMS	PSTA Transit Vehicles	Planned
security credential revocations	FDOT SCMS	Vehicles	Planned
security credentials	FDOT SCMS	City of Clearwater Traffic Control Center	Planned
security credentials	FDOT SCMS	City of St. Petersburg Traffic Control Center	Planned
security credentials	FDOT SCMS	County Fire EMS/Rescue Vehicles	Planned
security credentials	FDOT SCMS	FDOT District 7 Tampa Bay SunGuide Center	Planned
security credentials	FDOT SCMS	Personnel Device	Planned
security credentials	FDOT SCMS	Pinellas County CAV Field Equipment	Planned
security credentials	FDOT SCMS	Pinellas County Maintenance Vehicles	Planned
security credentials	FDOT SCMS	Pinellas County Traffic Management Center	Planned
security credentials	FDOT SCMS	Private Travelers Personal Computing Devices	Planned
security credentials	FDOT SCMS	PSTA Transit Management Center	Planned
security credentials	FDOT SCMS	PSTA Transit Vehicles	Planned
security credentials	FDOT SCMS	Vehicles	Planned
security policy and networking information	FDOT SCMS	City of Clearwater Traffic Control Center	Planned
security policy and networking information	FDOT SCMS	City of St. Petersburg Traffic Control Center	Planned
security policy and networking information	FDOT SCMS	County Fire EMS/Rescue Vehicles	Planned
security policy and networking information	FDOT SCMS	FDOT District 7 Tampa Bay SunGuide Center	Planned
security policy and networking information	FDOT SCMS	Personnel Device	Planned
security policy and networking information	FDOT SCMS	Pinellas County CAV Field Equipment	Planned
security policy and networking information	FDOT SCMS	Pinellas County Maintenance Vehicles	Planned
security policy and networking information	FDOT SCMS	Pinellas County Traffic Management Center	Planned
security policy and networking information	FDOT SCMS	Private Travelers Personal Computing Devices	Planned
security policy and networking information	FDOT SCMS	PSTA Transit Management Center	Planned
security policy and networking information	FDOT SCMS	PSTA Transit Vehicles	Planned
security policy and networking information	FDOT SCMS	Vehicles	Planned
signal control commands	Pinellas County Traffic Management Center	Pinellas County Field Equipment	Planned
signal control plans	Pinellas County Traffic Management Center	Pinellas County Field Equipment	Planned
signal control status	Pinellas County Field Equipment	Pinellas County Traffic Management Center	Planned
signal fault data	Pinellas County Field Equipment	Pinellas County Traffic Management Center	Planned
signal preemption request	Pinellas County CAV Field Equipment	Pinellas County Field Equipment	Planned
signal priority service request	Pinellas County CAV Field Equipment	Pinellas County Field Equipment	Planned
signal priority status	Pinellas County CAV Field Equipment	County Fire EMS/Rescue Vehicles	Planned
signal priority status	Pinellas County CAV Field Equipment	PSTA Transit Vehicles	Planned
signal priority status	Pinellas County Field Equipment	County Fire EMS/Rescue Vehicles	Planned
signal priority status	Pinellas County Field Equipment	PSTA Transit Vehicles	Planned
signal service request	Pinellas County CAV Field Equipment	Pinellas County Field Equipment	Planned
signal system configuration	Pinellas County Traffic Management Center	Pinellas County Field Equipment	Planned
situation data collection parameters	Pinellas County Traffic Management Center	Pinellas County CAV Field Equipment	Planned
traffic archive data	City of Clearwater Traffic Control Center	Pinellas County Connected Mobility Platform(CMP)	Planned
traffic archive data	City of St. Petersburg Traffic Control Center	Pinellas County Connected Mobility Platform(CMP)	Planned
traffic archive data	FDOT District 7 Tampa Bay SunGuide Center	Pinellas County Connected Mobility Platform(CMP)	Planned
traffic archive data	Pinellas County Traffic Management Center	Pinellas County Connected Mobility Platform(CMP)	Planned
traffic archive data	Private Traveler Information Services	Pinellas County Connected Mobility Platform(CMP)	Planned
traffic control priority status	Pinellas County Traffic Management Center	PSTA Transit Management Center	Planned
traffic detector control	Pinellas County Traffic Management Center	Pinellas County Field Equipment	Planned
traffic detector data	Pinellas County Field Equipment	Pinellas County Traffic Management Center	Planned
traffic images	City of Clearwater Traffic Control Center	Pinellas County Traffic Management Center	Planned
traffic images	City of St. Petersburg Traffic Control Center	Pinellas County Traffic Management Center	Planned
traffic images	FDOT District 7 Tampa Bay SunGuide Center	Pinellas County Traffic Management Center	Planned
traffic images	Pinellas County Field Equipment	Pinellas County Traffic Management Center	Planned
traffic images	Pinellas County Traffic Management Center	City of Clearwater Traffic Control Center	Planned
traffic images	Pinellas County Traffic Management Center	City of St. Petersburg Traffic Control Center	Planned
traffic images	Pinellas County Traffic Management Center	FDOT District 7 Tampa Bay SunGuide Center	Planned
traffic monitoring application info	Pinellas County Traffic Management Center	Pinellas County CAV Field Equipment	Planned
traffic monitoring application status	Pinellas County CAV Field Equipment	Pinellas County Traffic Management Center	Planned
traffic situation data	Pinellas County CAV Field Equipment	Pinellas County Field Equipment	Planned
traffic situation data	Pinellas County CAV Field Equipment	Pinellas County Traffic Management Center	Planned
transit archive data	PSTA Transit Management Center	Pinellas County Connected Mobility Platform(CMP)	Planned
transit schedule information	PSTA Transit Management Center	PSTA Transit Vehicles	Planned
transit vehicle schedule performance	PSTA Transit Vehicles	PSTA Transit Management Center	Planned
transportation operational strategies	Pinellas County Smart City Data Platform(SCDP)	Pinellas County Traffic Management Center	Planned
transportation weather information	Private Weather Information Providers	Pinellas County Traffic Management Center	Planned
traveler archive data	City of Clearwater Traffic Control Center	Pinellas County Connected Mobility Platform(CMP)	Planned
traveler archive data	FDOT District 7 Tampa Bay SunGuide Center	Pinellas County Connected Mobility Platform(CMP)	Planned
traveler archive data	Pinellas County Traffic Management Center	Pinellas County Connected Mobility Platform(CMP)	Planned
traveler archive data	Private Traveler Information Services	Pinellas County Connected Mobility Platform(CMP)	Planned
traveler archive data	PSTA Transit Management Center	Pinellas County Connected Mobility Platform(CMP)	Planned
vehicle location and motion	County Fire EMS/Rescue Vehicles	Pinellas County CAV Field Equipment	Planned
vehicle location and motion	PSTA Transit Vehicles	Pinellas County CAV Field Equipment	Planned
vehicle location and motion	Vehicles	Pinellas County CAV Field Equipment	Planned
vehicle location and motion	Vehicles	Private Travelers Personal Computing Devices	Planned
vehicle location and motion for surveillance	Pinellas County Maintenance Vehicles	Pinellas County CAV Field Equipment	Planned
vehicle location and motion for surveillance	Vehicles	Pinellas County CAV Field Equipment	Planned
vehicle location data for mapping	Pinellas County CAV Field Equipment	CAV-ITS Map Update System	Planned
vehicle signage application info	Pinellas County Traffic Management Center	Pinellas County CAV Field Equipment	Planned
vehicle signage application status	Pinellas County CAV Field Equipment	Pinellas County Traffic Management Center	Planned
vehicle signage data	Pinellas County CAV Field Equipment	Pinellas County Maintenance Vehicles	Planned
vehicle signage data	Pinellas County CAV Field Equipment	Vehicles	Planned
vehicle situation data	County Fire EMS/Rescue Vehicles	Pinellas County Traffic Management Center	Planned
vehicle situation data	FHP Vehicles	Pinellas County Traffic Management Center	Planned
vehicle situation data	Pinellas County Maintenance Vehicles	Pinellas County Traffic Management Center	Planned
vehicle situation data	PSTA Transit Vehicles	Pinellas County Traffic Management Center	Planned
vehicle situation data	Vehicles	Pinellas County CAV Field Equipment	Planned
vehicle situation data parameters	Pinellas County Traffic Management Center	Vehicles	Planned
video surveillance control	Pinellas County Traffic Management Center	Pinellas County Field Equipment	Planned
weather information	National Weather Service	Pinellas County Traffic Management Center	Planned

Project Functional Requirements (Element - Functional Object):

911 Emergency Call Centers - Emergency Data Collection

1: The center shall collect emergency service data, emergency vehicle management data, emergency vehicle data, sensor and surveillance data, threat data, and incident data.
2: The emergency management center shall assign quality control metrics and meta-data to be stored along with the data. Meta-data may include attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.
3: The center shall receive and respond to requests from ITS Archives for either a catalog of the emergency management data or for the data itself.
4: The emergency management center shall produce sample products of the data available.

911 Emergency Call Centers - Emergency Incident Command

1: The center shall provide tactical decision support, resource coordination, and communications integration for first responders to support local management of an incident.
2: The center shall provide incident command communications with public safety, emergency management, transportation, and other allied response agency centers.
3: The center shall track and maintain resource information and action plans pertaining to the incident command.
6: The center shall provide other agencies real-time information on the current conditions at the incident scene.

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 Authorizing Center - 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.

CAV Authorizing Center - 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.

CAV Authorizing Center - 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.

CAV-ITS Map Update System - 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.

CAV-ITS Map Update System - 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.

CAV-ITS Map Update System - 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.

CAV-ITS Map Update System - Map Management

1: The Center shall collect Vehicle location information from Vehicles.
10: The Center shall use vehicle location information to refine roadway geometry.
11: The Center shall use vehicle location information to refine basemaps.
12: The Center shall use vehicle location information to refine intersection geometry.
13: The Center shall provide intersection geometry updates to other Centers.
18: The Center shall provide intersection geometry updates to Connected Vehicle Roadside Equipment.
19: The Center shall provide roadway geometry updates to Connected Vehicle Roadside Equipment.
2: The Center shall collect updates to roadway geometry from other Centers.
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.
25: The Center shall provide roadway geometry updates to Vehicles.
27: The Center shall provide basemap updates to Connected Vehicle Roadside Equipment.
4: The Center shall collect updates to intersection geometry from other Centers.
5: The Center shall provide basemap updates to other Centers.
7: The Center shall collect vehicle location information from the Connected Vehicle Roadside Equipment.
8: The Center shall coordinate the contents of map data for distribution with other Centers.

City of Clearwater Traffic Control Center - 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 Clearwater Traffic Control Center - 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 Clearwater Traffic Control Center - 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 Clearwater Traffic Control Center - TIC Operations Data Collection

1: The center shall collect traveler information data, such as parking lot data, rideshare data, road network use data, vehicle probe data, and other data from traveler information system operations.
4: The center shall receive and respond to requests from ITS Archives for either a catalog of the traveler information data or for the data itself.

City of Clearwater Traffic Control Center - TMC Data Collection

1: The center shall collect traffic management data such as operational data, event logs, etc.
3: The traffic management center shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data itself.
4: The traffic management center shall produce sample products of the data available.

City of Clearwater Traffic Control Center - TMC Regional Traffic Management

1: The center shall exchange traffic information with other traffic management centers including incident information, congestion data, traffic data, signal timing plans, and real-time signal control information.

City of St. Petersburg Traffic Control Center - 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 St. Petersburg Traffic Control Center - 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 St. Petersburg Traffic Control Center - 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 St. Petersburg Traffic Control Center - TMC Data Collection

1: The center shall collect traffic management data such as operational data, event logs, etc.
3: The traffic management center shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data itself.
4: The traffic management center shall produce sample products of the data available.

City of St. Petersburg Traffic Control Center - TMC Regional Traffic Management

1: The center shall exchange traffic information with other traffic management centers including incident information, congestion data, traffic data, signal timing plans, and real-time signal control information.

County Fire EMS/Rescue Vehicles - EV On-Board En Route Support

1: The emergency vehicle, including roadway service patrols, shall track its current location.
2: The emergency vehicle, including roadway service patrols, shall send the vehicle's location and operational data to the center for emergency management and dispatch.
5: The emergency vehicle shall send requests to traffic signal control equipment at the roadside to preempt the signal.
9: The emergency vehicle shall send the vehicle�s location, speed and direction to other vehicles in the area.

County Fire EMS/Rescue Vehicles - EV On-Board Incident Management Communication

1: The emergency vehicle shall receive dispatch instructions sufficient to enable emergency personnel in the field to implement an effective incident response. It includes local traffic, road, and weather conditions, hazardous material information, and the current status of resources that have been allocated to an incident.
2: The emergency vehicle shall provide an interface to the center for emergency personnel to transmit information about the incident site such as the extent of injuries, identification of vehicles and people involved, hazardous material, etc.

County Fire EMS/Rescue Vehicles - 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.

County Fire EMS/Rescue 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.
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.

County Fire EMS/Rescue Vehicles - Vehicle Basic Safety Communication

1: The vehicle shall collect location and motion data from the vehicle platform.
12: The vehicle shall analyze its own applications' performance and enter fail-safe mode (a mode such that the application cannot provide information or perform actions that affect its host) when critical components fail.
13: The vehicle shall notify the driver when onboard components or safety applications are offline.
2: The vehicle shall provide its location with lane-level accuracy to on-board applications.
3: The vehicle shall provide its location with road-level accuracy to on-board applications.

County Fire EMS/Rescue Vehicles - Vehicle Situation Data Monitoring

1: The Vehicle shall obtain data collection parameters from Connected Vehicle Roadside Equipment.
2: The Vehicle shall collect data collection parameters from Centers.
3: The vehicle shall collect location and motion data from the vehicle platform.
5: The Vehicle shall provide data to Centers in accordance with data collection parameters provided by Centers/Connected Vehicle Roadside Equipment.

FDOT District 7 Tampa Bay SunGuide Center - Archive Data Repository

1: The center shall collect data from centers.
11: The center shall respond to requests for archive data from archive data users (centers, field devices).
13: The center shall associate meta-data with archived data, including catalog data, statistical products determined from method execution and data longevity.
2: The center shall collect data catalogs from one or more data sources. A catalog describes the data contained in the collection of archived data and may include descriptions of the schema or structure of the data, a description of the contents of the data; e.g., time range of entries, number of entries; or a sample of the data (e. g. a thumbnail).
3: The center shall store collected data in an information repository.
4: The center shall perform quality checks on collected data.
6: The center shall include capabilities for archive to archive coordination.
7: The center shall provide the capability to execute methods on the incoming data such as cleansing, summarizations, aggregations, or transformations applied to the data before it is stored in the archive.
8: The center shall collect data from data distribution systems and other data sources.

FDOT District 7 Tampa Bay SunGuide Center - Archive Situation Data Archival

1: The center shall collect data from roadside devices.
4: The center shall collect vehicle traffic probe data for performance monitoring and analysis.
5: The center shall be capable of archiving vehicle traffic probe data.

FDOT District 7 Tampa Bay SunGuide Center - 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.

FDOT District 7 Tampa Bay SunGuide Center - Emergency Data Collection

1: The center shall collect emergency service data, emergency vehicle management data, emergency vehicle data, sensor and surveillance data, threat data, and incident data.
2: The emergency management center shall assign quality control metrics and meta-data to be stored along with the data. Meta-data may include attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.
3: The center shall receive and respond to requests from ITS Archives for either a catalog of the emergency management data or for the data itself.

FDOT District 7 Tampa Bay SunGuide Center - Emergency Incident Command

2: The center shall provide incident command communications with public safety, emergency management, transportation, and other allied response agency centers.
3: The center shall track and maintain resource information and action plans pertaining to the incident command.

FDOT District 7 Tampa Bay SunGuide Center - 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.

FDOT District 7 Tampa Bay SunGuide Center - 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.

FDOT District 7 Tampa Bay SunGuide Center - MCM Data Collection

1: The center shall collect maintenance and construction data (such as field equipment status, infrastructure status, maintenance and construction activity data) gathered from roadway, traffic, and other maintenance and construction sources.
2: The maintenance and construction management center shall assign quality control metrics and meta-data to be stored along with the data. Meta-data may include attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.
3: The center shall receive and respond to requests from ITS Archives for either a catalog of the maintenance and construction data or for the data itself.

FDOT District 7 Tampa Bay SunGuide Center - MCM Work Activity Coordination

1: The center shall provide work zone activities affecting the road network including the nature of the maintenance or construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays, alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual indication of current work zone status and traffic impacts.
3: The center shall collect and respond to feedback concerning scheduled maintenance and construction activities with other management centers such as traffic, emergency, transit, and rail operations.

FDOT District 7 Tampa Bay SunGuide Center - PAC Data Collection

1: The center shall collect toll operational data and roadway pricing data.

FDOT District 7 Tampa Bay SunGuide Center - TIC Operations Data Collection

1: The center shall collect traveler information data, such as parking lot data, rideshare data, road network use data, vehicle probe data, and other data from traveler information system operations.
4: The center shall receive and respond to requests from ITS Archives for either a catalog of the traveler information data or for the data itself.

FDOT District 7 Tampa Bay SunGuide Center - TMC Data Collection

1: The center shall collect traffic management data such as operational data, event logs, etc.
3: The traffic management center shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data itself.
4: The traffic management center shall produce sample products of the data available.

FDOT District 7 Tampa Bay SunGuide Center - TMC Regional Traffic Management

1: The center shall exchange traffic information with other traffic management centers including incident information, congestion data, traffic data, signal timing plans, and real-time signal control information.

FDOT SCMS - CCMS Authorization

1: The Center shall generate credential identifiers using facilities that are independently owned and operated from one another.
10: The Center shall accept user permission information from Centers authorized to provide that information.
11: The Center shall acquire identifiers relevant to ITS services from the relevant registry of such identifiers
2: The Center shall assign two or more non-unique identifiers, that when combined are unique, to each credential it distributes.
3: The Center shall verify information received in pseudonym requests.
4: The Center shall coordinate the distribution of credentials with other Centers.
5: The Center shall store credential identifiers using facilities that are independently owned and operated from one another.
6: The Center shall provide Vehicle pseudonymous credentials in response to valid Vehicle pseudonym requests.
7: The Center shall provide Personal Device pseudonymous credentials in response to valid Personal Device pseudonym requests.
8: The Center shall provide Center pseudonymous credentials in response to valid Center pseudonym requests.
9: The Center shall provide Connected Vehicle Roadside Equipment pseudonymous credentials in response to valid Connected Vehicle Roadside Equipment pseudonym requests.

FDOT SCMS - CCMS Misbehavior Reporting and Action

1: The Center shall accept misbehavior reports from ITS Objects.
2: The Center shall analyze misbehavior reports.
3: The Center shall coordinate misbehavior analysis with other Centers.

FDOT SCMS - CCMS Provisioning

1: The Center shall provide security and regulatory policy information to ITS Objects.
2: The Center shall provide its credentials information to ITS Objects.
3: The Center shall provide the operator with mechanisms for monitoring the status of all credential-granting activities without compromising any other requirement.

FDOT SCMS - CCMS Revocation

1: The Center shall place certificates on the revocation list of those certificates that are associated with misbehavior.
2: The Center shall provide to ITS Objects a list of credentials whose trust as been revoked.

FDOT SCMS - 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.

FDOT SCMS - 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.

FHP Vehicles - EV On-Board Incident Management Communication

1: The emergency vehicle shall receive dispatch instructions sufficient to enable emergency personnel in the field to implement an effective incident response. It includes local traffic, road, and weather conditions, hazardous material information, and the current status of resources that have been allocated to an incident.
2: The emergency vehicle shall provide an interface to the center for emergency personnel to transmit information about the incident site such as the extent of injuries, identification of vehicles and people involved, hazardous material, etc.
3: The emergency vehicle shall provide an interface to the center for emergency personnel to transmit information about the current incident response status such as the identification of the resources on site, site management strategies in effect, and current clearance status.
7: The emergency vehicle shall exchange information with other emergency vehicles to support the decision making and overall incident response.
8: The emergency vehicle shall provide nearby vehicles with information related to active incident management activities that require cooperation from surrounding traffic.

FHP Vehicles - Vehicle Basic Safety Communication

1: The vehicle shall collect location and motion data from the vehicle platform.
2: The vehicle shall provide its location with lane-level accuracy to on-board applications.
6: The vehicle shall exchange location and motion information with roadside equipment and nearby vehicles.

FHP Vehicles - Vehicle Situation Data Monitoring

1: The Vehicle shall obtain data collection parameters from Connected Vehicle Roadside Equipment.
2: The Vehicle shall collect data collection parameters from Centers.
3: The vehicle shall collect location and motion data from the vehicle platform.
5: The Vehicle shall provide data to Centers in accordance with data collection parameters provided by Centers/Connected Vehicle Roadside Equipment.

Personnel Device - 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.
5: The ITS Object shall provide its configuration and operational status information to the Service Monitor

Personnel Device - 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.

Personnel Device - Personnel Field Asset Locating

1: The field device operated by field personnel shall scan MC assets and record their location relative to the scanning device.
2: The personnel device shall accept inputs from the user to manipulate field asset location activities.
3: The personnel device shall provide status information related to field asset locations to the user.

Pinellas County 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.

Pinellas County 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.

Pinellas County CAV Field Equipment - RSE Device Management

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.

Pinellas County 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.
2: The field element shall send the request for emergency vehicle preemption to a traffic signal controller that results in preemption of the current control plan and grants right-of-way to the requesting vehicle.
5: The field element shall receive transit signal priority requests from transit vehicles and forward to the traffic signal controller
6: The field element shall receive emergency vehicle preemption requests from emergency vehicles and forward to the traffic signal controller.
7: The field element shall determine when special vehicles requesting preemption or priority at a signal are authorized to do so based on their digital credentials.
8: The field element shall send a signal service request to the traffic signal controller when its application status determines the need for a signal change.
9: The field element shall collect current signal phase and timing data from the traffic signal controller.

Pinellas County CAV Field Equipment - RSE Intersection Safety

1: The roadway equipment shall collect the current location (latitude, longitude, and elevation) from personal information devices.
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.
4: The roadway equipment shall provide current crossing status including permission to cross, crossing time remaining.
5: The roadway equipment shall send to Connected Vehicles intersection signal timing information in order for the vehicle to determine if it will safely cross the intersection given its current speed and location.
6: The roadway equipment shall send to connected vehicles a warning if an intersection violation appears to be imminent.

Pinellas County 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.
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.
6: The field element shall provide basemap 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.

Pinellas County 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.
3: The field element shall provide data collection parameters to vehicles.
5: The field element shall provide collected vehicle situation and local sensor data to data distribution centers.

Pinellas County 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.

Pinellas County CAV Field Equipment - RSE Traveler Information Communications

1: The field element shall distribute traveler information including traffic and road conditions or upcoming work zones to passing vehicles using short range communications, under center control.
11: The field element shall provide real-time driving advice to connected vehicles so that they can adjust their driving behavior to save fuel and reduce emissions.
4: The field element shall return system operational status to the controlling center.
5: The field element shall return system fault data to the maintenance center for repair.

Pinellas County Connected Mobility Platform(CMP) - Archive Data Repository

1: The center shall collect data from centers.
10: The center shall respond to requests from the administrator interface function to manage the archive data.
3: The center shall store collected data in an information repository.
4: The center shall perform quality checks on collected data.
7: The center shall provide the capability to execute methods on the incoming data such as cleansing, summarizations, aggregations, or transformations applied to the data before it is stored in the archive.

Pinellas County Connected Mobility Platform(CMP) - Archive Situation Data Archival

1: The center shall collect data from roadside devices.
2: The center shall respond to requests from the administrator interface function to manage field-sourced data collection.
3: The center shall provide the capability to adjust the collection of field-sourced data based on the statistical measures.
4: The center shall collect vehicle traffic probe data for performance monitoring and analysis.
5: The center shall be capable of archiving vehicle traffic probe data.
6: The center shall provide the capability to execute methods on the incoming field data such as aggregation and statistical measures before the data is stored in the archive.
7: The center shall respond to requests from the administrator interface function to select and manage data stored in the archive.

Pinellas County Connected Mobility Platform(CMP) - Center Data Collection

5: The Center shall collect operational data from other Centers.

Pinellas County Connected Mobility Platform(CMP) - Center Data Subscription Management

2: The center shall allow users to sign up for a data subscription service to access data held by the center.
3: The center shall send data to users based upon a set of rules governing the data subscription service.
4: The center shall allow center personnel to manage the subscription service.
5: The center shall be capable of collecting data from other centers to be used as part of the data subscription service.
8: The center shall support a data subscription service that manages the necessary user information and rules that govern the data subscriptions.

Pinellas County Connected Mobility Platform(CMP) - DDS Data Access Management

2: The data support center shall distribute to Vehicles data which has been validated, aggregated, integrated, and sanitized.
3: The data support center shall distribute to other Centers data which has been validated, aggregated, integrated, and sanitized.
6: The data support center shall provide metadata parameters (geographic area, data content type, time) as filters for subscription.
8: The data support center shall provide data consumers with a mechanism for subscribing to data received by the Center.
9: The data support center shall provide a mechanism for the operator to modify data subscriptions.

Pinellas County Connected Mobility Platform(CMP) - DDS Data Collection and Aggregation

5: The data support center shall collect data from other Centers.
7: The data support center shall perform 'VISA' functions on incoming data (VISA = Validation, Integration, Sanitization, Aggregation).
8: The data support center shall provide a mechanism for the operator to control data collection parameters.
9: The data support center shall provide a mechanism for the operator to modify VISA functions.

Pinellas County Field Equipment - Field Asset Identification

1: The field device shall provide a unique identification number that is used for identification and tracking of assets.

Pinellas County 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.
2: The field element shall collect, process, and send traffic images to the center for further analysis and distribution.
5: The field element shall return sensor and CCTV system fault data to the controlling center for repair.

Pinellas County Field Equipment - Roadway Field Management Station Operation

1: The field element shall accept configuration information from the center.
2: The field element shall pass data provided by the center to local field devices and report data from the field devices back to the center.

Pinellas County Field Equipment - Roadway Mixed Use Crossing Safety

1: The field element shall collect images or sensor data for pedestrians or bicyclists and respond to pedestrian or bicyclist crossing requests via display, audio signal, or other manner.
2: The field element shall respond to pedestrian or bicyclist crossing requests via display, audio signal, or other manner.
3: The field element shall inform pedestrians and bicyclists of the status of the intersection including the amount of time left for crossing the intersection.

Pinellas County Field Equipment - Roadway Passive Monitoring

1: The field element shall collect, process, and send data to the center to uniquely identify passing vehicles in order to support travel time measurement

Pinellas County 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.
13: The field element shall provide to roadside equipment the intersection geometry and signal phase movement information including phase and timing information, alarm status, and priority/preempt status.
15: The field element shall receive requests for emergency vehicle signal preemption.
2: The field element shall respond to pedestrian crossing requests by accommodating the pedestrian crossing.
3: The field element shall provide the capability to notify the traffic management center of pedestrian calls and pedestrian accommodations.
4: The field element shall report the current signal control information to the center.
5: The field element shall report current preemption status to the center.
6: The field element shall return traffic signal controller operational status to the center.
7: The field element shall return traffic signal controller fault data to the center.
8: The field element shall report current transit priority status to the center.
9: The field element shall report current intersection signal timing information to roadside equipment for transmission to connected vehicles.

Pinellas County Field Equipment - Roadway Signal Preemption

1: The field element shall respond to signal preemption requests from emergency vehicles.
3: The field element shall send the preemption request to the signal controller to immediately preempt the signal for the requested direction.

Pinellas County Field Equipment - Roadway Traffic Information Dissemination

1: The field element shall include dynamic message signs for dissemination of traffic and other information to drivers, under center control; the DMS may be either those that display variable text messages, or those that have fixed format display(s) (e.g. vehicle restrictions, or lane open/close).
4: The field element shall provide fault data for the driver information systems equipment (DMS, HAR, etc.) to the center for repair.
5: The field element shall provide dynamic message sign information to roadside equipment for transmission to connected vehicles to support in-vehicle signing.

Pinellas County Field Equipment - RSE Field Asset Locating

1: The field device shall scan MC assets and record their location relative to the scanning device.

Pinellas County 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.
2: The field element shall send the request for emergency vehicle preemption to a traffic signal controller that results in preemption of the current control plan and grants right-of-way to the requesting vehicle.
3: The field element shall send the infrastructure application status to the operations center.
5: The field element shall receive transit signal priority requests from transit vehicles and forward to the traffic signal controller
6: The field element shall receive emergency vehicle preemption requests from emergency vehicles and forward to the traffic signal controller.
7: The field element shall determine when special vehicles requesting preemption or priority at a signal are authorized to do so based on their digital credentials.
8: The field element shall send a signal service request to the traffic signal controller when its application status determines the need for a signal change.
9: The field element shall collect current signal phase and timing data from the traffic signal controller.

Pinellas County Field Equipment - RSE Intersection Safety

1: The roadway equipment shall collect the current location (latitude, longitude, and elevation) from personal information devices.
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.
4: The roadway equipment shall provide current crossing status including permission to cross, crossing time remaining.
5: The roadway equipment shall send to Connected Vehicles intersection signal timing information in order for the vehicle to determine if it will safely cross the intersection given its current speed and location.
6: The roadway equipment shall send to connected vehicles a warning if an intersection violation appears to be imminent.
7: The field element shall collect current conflict monitor and intersection control data from the traffic signal controller.

Pinellas County 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.
5: The field element shall provide collected vehicle situation and local sensor data to data distribution centers.

Pinellas County 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.

Pinellas County Field Equipment - RSE Traveler Information Communications

1: The field element shall distribute traveler information including traffic and road conditions or upcoming work zones to passing vehicles using short range communications, under center control.
2: The field element shall distribute advisory information, such as evacuation information, wide-area alerts, incident information, work zone intrusion information, recommended speed limit and other special information to passing vehicles using short range communications, under center control.
3: The field element shall distribute indicator and fixed sign information, including static sign information (e.g., stop, curve warning, guide signs, service signs, and directional signs) and dynamic information (e.g., current signal states and local conditions warnings identified by local environmental sensors) to equipment on-board vehicles under center control.
4: The field element shall return system operational status to the controlling center.
5: The field element shall return system fault data to the maintenance center for repair.

Pinellas County Maintenance Vehicles - 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.

Pinellas County Maintenance 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.
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.

Pinellas County Maintenance Vehicles - MCV Field Asset Locating

1: The field device housed in a vehicle shall scan MC assets and record their location relative to the scanning device.

Pinellas County Maintenance Vehicles - MCV Vehicle Location Tracking

1: The maintenance and construction vehicle shall track its current location.
2: The maintenance and construction vehicle shall send the time stamped vehicle location to the controlling center.
9: The maintenance/construction vehicle shall provide vehicle location and motion information to local connected vehicle equipment near signalized intersections.

Pinellas County Maintenance Vehicles - MCV Work Zone Support

2: The maintenance and construction vehicle shall provide an interface for field personnel to input status of their work zone activities.
3: The maintenance and construction vehicle shall collect inputs from field personnel and from work zone devices on-board the maintenance and construction vehicle and send them to the controlling center.

Pinellas County Maintenance Vehicles - Vehicle Basic Safety Communication

1: The vehicle shall collect location and motion data from the vehicle platform.
12: The vehicle shall analyze its own applications' performance and enter fail-safe mode (a mode such that the application cannot provide information or perform actions that affect its host) when critical components fail.
2: The vehicle shall provide its location with lane-level accuracy to on-board applications.
3: The vehicle shall provide its location with road-level accuracy to on-board applications.
4: The vehicle shall collect road condition data from other vehicles.

Pinellas County Maintenance 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.
10: The vehicle shall present vehicle control information to the driver in audible or visual forms without impairing the driver's ability to control the vehicle in a safe manner.
11: The vehicle shall perform control actions based on information received from other vehicles regarding potentially hazardous road conditions or road hazards.
12: The vehicle shall perform pre-crash actions, including seatbelt tightening, brake assist, airbag pre-arming, bumper raising/extension.
13: The vehicle shall be capable of performing control actions based upon warnings received from nearby special vehicles.
14: The vehicle shall be capable of performing control actions based upon warnings received regarding pedestrians, cyclists, and other non-motorized users that are sharing the roadway with the vehicle
15: The vehicle shall be capable of performing control actions based upon information received from the infrastructure regarding the status of the intersection the vehicle is approaching.
16: The vehicle shall be capable of performing control actions based upon information received from other vehicles regarding their status approaching the intersection the vehicle is approaching.
17: The vehicle shall send appropriate control actions to the vehicle's speed control systems (e.g., throttle, brakes).
2: The vehicle shall monitor the area to the sides of the vehicle to determine the proximity of other objects to the vehicle to determine if a control adjustment is needed.
3: The vehicle shall evaluate the likelihood of a collision between two vehicles or a vehicle and a stationary object, based on the proximity of other objects to the vehicle and the current speed and direction of the vehicle.
4: The vehicle shall collect location and motion data from the vehicle platform.
8: The vehicle shall provide an interface through which a vehicle driver can initiate, monitor and terminate automatic control of the vehicle.
9: The vehicle shall send appropriate control actions to the vehicle's steering actuators.

Pinellas County Maintenance Vehicles - 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.
2: The vehicle shall evaluate the likelihood of a collision between two vehicles or a vehicle and a stationary object to warn the driver, based on the proximity of other objects to the vehicle, roadway characteristics, and the current speed and direction of the vehicle.
3: The vehicle shall provide position warnings to the driver when an object gets close enough to the vehicle to become a hazard if no action is taken by the driver.
4: The vehicle shall present vehicle control warnings information to the driver in audible or visual forms without impairing the driver's ability to control the vehicle in a safe manner.
5: The vehicle shall provide warnings to the driver based on information received from other vehicles regarding potentially hazardous road conditions or road hazards.
9: The vehicle shall collect location and motion data from the vehicle platform.

Pinellas County Maintenance 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.
2: Vehicle shall provide data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size.
3: The vehicle shall receive intersection signal timing information in order for the vehicle to determine if it will safely cross the intersection given its current location and speed.

Pinellas County Maintenance 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.
2: The Vehicle shall obtain parking facility geometry information from proximate Connected Vehicle Roadside Equipment.
3: The Vehicle shall obtain roadway geometry update information from proximate Connected Vehicle Roadside Equipment.
4: The Vehicle shall obtain intersection geometry update information from proximate Connected Vehicle Roadside Equipment.
5: The Vehicle shall provide its location to Centers.

Pinellas County Maintenance Vehicles - Vehicle Roadside Information Reception

1: The vehicle shall receive traveler information including traffic and road conditions, incident information, maintenance and construction information, event information, transit information, parking information, and weather information.
10: The vehicle shall receive customized real-time driving advice so that the vehicle or the driver can adjust their driving behavior to save fuel and reduce emissions.
3: The vehicle shall receive indicator and fixed sign information including static sign information (e.g., stop, curve warning, guide signs, service signs, and directional signs) and dynamic information (e.g., current signal and traffic meter states and local conditions warnings identified by local environmental sensors).

Pinellas County Maintenance Vehicles - Vehicle Situation Data Monitoring

1: The Vehicle shall obtain data collection parameters from Connected Vehicle Roadside Equipment.
2: The Vehicle shall collect data collection parameters from Centers.
5: The Vehicle shall provide data to Centers in accordance with data collection parameters provided by Centers/Connected Vehicle Roadside Equipment.

Pinellas County Maintenance Vehicles - Vehicle Traveler Information Reception

1: The vehicle shall receive formatted traffic information from a center and present it to the driver.
12: The Vehicle shall receive traveler information from Connected Vehicle Roadside Equipment.
15: The vehicle shall receive roadway safety information of infrastructure issues such as objects in or near travel lanes.
2: The vehicle shall receive transit information from a center and present it to the driver.
6: The vehicle shall provide data from the vehicle itself to the driver. This vehicle data may include vehicle conditions, environmental conditions, safety or position warnings.

Pinellas County Smart City Data Platform(SCDP) - Center Data Collection

5: The Center shall collect operational data from other Centers.

Pinellas County Smart City Data Platform(SCDP) - Center Data Subscription Management

3: The center shall send data to users based upon a set of rules governing the data subscription service.

Pinellas County Smart City Data Platform(SCDP) - MCM Data Collection

1: The center shall collect maintenance and construction data (such as field equipment status, infrastructure status, maintenance and construction activity data) gathered from roadway, traffic, and other maintenance and construction sources.
2: The maintenance and construction management center shall assign quality control metrics and meta-data to be stored along with the data. Meta-data may include attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.

Pinellas County Smart City Data Platform(SCDP) - MCM Work Activity Coordination

1: The center shall provide work zone activities affecting the road network including the nature of the maintenance or construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays, alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual indication of current work zone status and traffic impacts.
2: The center shall provide status information about scheduled maintenance and construction activities including anticipated closures and impact to the roadway, alternate routes, anticipated delays, closure times, and durations. The information is provided to other management centers such as traffic, emergency, transit, traveler information providers, other maintenance centers, multimodal transportation providers, rail operations, and the media.
3: The center shall collect and respond to feedback concerning scheduled maintenance and construction activities with other management centers such as traffic, emergency, transit, and rail operations.

Pinellas County Smart City Data Platform(SCDP) - MCM Work Zone Management

1: The center shall generate new work zone activity schedules for use by maintenance and construction vehicles, maintenance and construction operators, and for information coordination purposes.
2: The center shall control the collection of work zone status information including video images from cameras located in or near the work zone.
3: The center shall disseminate work zone information to other agencies and centers including traffic, transit, emergency management centers, other maintenance centers, traveler information centers, and the media.

Pinellas County Smart City Data Platform(SCDP) - TIC Data Collection

1: The center shall collect, process, and store traffic and highway condition information, including incident information, detours and road closures, event information, recommended routes, and current speeds on specific routes.
2: The transportation information center shall select real-time information on the state of the regional transportation system including current traffic and road conditions, weather conditions, transit information, parking information, special event and incident information.

Pinellas County Smart City Data Platform(SCDP) - TIC Operations Data Collection

1: The center shall collect traveler information data, such as parking lot data, rideshare data, road network use data, vehicle probe data, and other data from traveler information system operations.

Pinellas County Smart City Data Platform(SCDP) - TIC Trip Planning

1: The center shall provide the capability to provide specific pre-trip and en route directions to travelers (and drivers), including costs, arrival times, and transfer points.
3: The center shall support on-line route guidance for travelers using personal devices (such as PDAs).
4: The center shall support on-line route guidance for drivers in vehicles.
6: The center shall generate route plans based on current and/or predicted conditions of the road network, scheduled maintenance and construction work activities, and work zone activities.

Pinellas County Smart City Data Platform(SCDP) - TMC Data Collection

1: The center shall collect traffic management data such as operational data, event logs, etc.

Pinellas County Smart City Data Platform(SCDP) - TMC Demand Management Coordination

1: The center shall collect and store toll pricing data from payment administration centers, including the price for each road segment to which a toll applies, with the time and date for when it applies.
3: The center shall collect and store transit fare and schedule information from transit management centers.
4: The center shall collect and store current transit, parking, and toll fee schedule information provided by regional traveler information centers.

Pinellas County Smart City Data Platform(SCDP) - TMC Regional Traffic Management

1: The center shall exchange traffic information with other traffic management centers including incident information, congestion data, traffic data, signal timing plans, and real-time signal control information.

Pinellas County Smart City Data Platform(SCDP) - TMC Traffic Management Decision Support

1: The center shall provide center personnel with an integrated regional view of current and forecast road and traffic conditions including traffic incidents, special events, maintenance activities and other events or conditions that impact capacity or demand.
2: The center shall identify network imbalances and potential courses of action.
4: The recommended actions shall include predefined incident response plans, signal timing plan changes, DMS/HAR messages, lane control strategies and freeway control strategies including ramp metering, interchange metering, and mainline metering.
5: The recommended actions shall include multimodal strategies that include suggested transit strategies and suggested route and mode choices for travelers.
6: The center shall provide an interface to center personnel to input control parameters for the decision support process and receive recommended actions and supporting information presentation.
7: The center shall provide transportation operational strategies to other centers.

Pinellas County Smart City Data Platform(SCDP) - TMC Traffic Network Performance Evaluation

3: The center shall collect and store anticipated route information from traveler information centers to support overall network performance evaluations and predictions.
7: This center shall use the collected information to measure overall current and forecast network performance and predict travel demand patterns.

Pinellas County Traffic Management 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.
4: The Center shall be capable of modifying the operational status of Connected Vehicle Roadside Equipment.

Pinellas County Traffic Management Center - 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.

Pinellas County Traffic Management Center - Emergency Data Collection

1: The center shall collect emergency service data, emergency vehicle management data, emergency vehicle data, sensor and surveillance data, threat data, and incident data.
2: The emergency management center shall assign quality control metrics and meta-data to be stored along with the data. Meta-data may include attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.

Pinellas County Traffic Management Center - Emergency Incident Command

2: The center shall provide incident command communications with public safety, emergency management, transportation, and other allied response agency centers.

Pinellas County Traffic Management Center - Emergency Routing

1: The center shall collect current traffic and road condition information for emergency vehicle route calculation.
2: The center shall receive information on the location and status of traffic control equipment and work zones along potential emergency routes.

Pinellas County Traffic Management Center - 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.

Pinellas County Traffic Management Center - 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.

Pinellas County Traffic Management Center - MCM Data Collection

1: The center shall collect maintenance and construction data (such as field equipment status, infrastructure status, maintenance and construction activity data) gathered from roadway, traffic, and other maintenance and construction sources.

Pinellas County Traffic Management Center - MCM Field Equipment Maintenance

1: The center shall collect the status and fault data from the centers that operate the equipment, including data for traffic, infrastructure, and environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems, barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, short range communications equipment, security sensors and surveillance equipment, etc..
2: The center shall collect the status and fault data from field equipment, such as traffic, infrastructure, and environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems, barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, short range communications equipment, security sensors and surveillance equipment, etc.

Pinellas County Traffic Management Center - MCM Work Activity Coordination

1: The center shall provide work zone activities affecting the road network including the nature of the maintenance or construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays, alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual indication of current work zone status and traffic impacts.

Pinellas County Traffic Management Center - MCM Work Zone Management

2: The center shall control the collection of work zone status information including video images from cameras located in or near the work zone.

Pinellas County Traffic Management Center - TIC Connected Vehicle Traveler Info Distribution

1: The center shall collect traveler information for distribution including traffic and road conditions, incident information, maintenance and construction information, event information, transit information, parking information, and weather information.

Pinellas County Traffic Management Center - TIC Data Collection

1: The center shall collect, process, and store traffic and highway condition information, including incident information, detours and road closures, event information, recommended routes, and current speeds on specific routes.

Pinellas County Traffic Management Center - TIC Operations Data Collection

1: The center shall collect traveler information data, such as parking lot data, rideshare data, road network use data, vehicle probe data, and other data from traveler information system operations.

Pinellas County Traffic Management Center - TIC Situation Data Management

1: The center shall collect traffic probe data (speeds, travel times, etc.) from appropriately equipped vehicles and short range communications equipment.
2: The center shall collect environmental probe data (air temperature, exterior light status, wiper status, traction control status, etc.) from appropriately equipped vehicles and short range communications equipment.
5: The center shall aggregate collected traffic probe data, calculate route segment travel times, route segment speeds, route usage, and road weather information for dissemination to other centers.

Pinellas County Traffic Management Center - TIC Traffic Control Dissemination

3: The center shall provide real time signal phase and timing information for all lanes at a signalized intersection to vehicle.

Pinellas County Traffic Management Center - TIC Traveler Information Broadcast

1: The center shall disseminate traffic and highway condition information to travelers, including incident information, detours and road closures, event information, recommended routes, and current speeds on specific routes.

Pinellas County Traffic Management Center - TIC Trip Planning

1: The center shall provide the capability to provide specific pre-trip and en route directions to travelers (and drivers), including costs, arrival times, and transfer points.
3: The center shall support on-line route guidance for travelers using personal devices (such as PDAs).
4: The center shall support on-line route guidance for drivers in vehicles.

Pinellas County Traffic Management Center - 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.
2: The center shall monitor, analyze, and distribute traffic images from CCTV systems under remote control of the center.
4: The center shall distribute road network conditions data (raw or processed) based on collected and analyzed traffic sensor and surveillance data to other centers.

Pinellas County Traffic Management Center - TMC Data Collection

1: The center shall collect traffic management data such as operational data, event logs, etc.
3: The traffic management center shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data itself.

Pinellas County Traffic Management Center - TMC Demand Management Coordination

1: The center shall collect and store toll pricing data from payment administration centers, including the price for each road segment to which a toll applies, with the time and date for when it applies.
2: The center shall collect and store parking information from parking management providers including lot locations, features (e.g. ability to handle oversized vehicles), capacity, type, hours of operation and rates.

Pinellas County Traffic Management Center - TMC Intersection Safety

1: The center shall provide current intersection safety status information.
2: The center shall provide warnings to drivers when non-motorized users are occupying a cross walk or other mixed use path crossing.
3: The center shall provide warnings to pedestrians or bicyclists when vehicles are infringing on a cross walk or other mixed use path crossing.
5: The field element shall be capable of configuring roadside equipment to perform the collection and transmission of information to support intersection safety.

Pinellas County Traffic Management Center - 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.
4: The center shall receive system operational status from field equipment that supports in-vehicle signage communications.
5: The center shall receive system fault data from field equipment that supports in-vehicle signage communications.

Pinellas County Traffic Management Center - TMC Multi-Modal Coordination

2: The center shall exchange information with transit management centers including details current transit routes, the level of service on each route, and the progress of individual vehicles along their routes.

Pinellas County Traffic Management Center - TMC Passive Surveillance

1: The center shall collect time stamped vehicle identities from field equipment.
2: The center shall correlate the time stamped vehicle identities in order to calculate link travel times and derive other traffic measures.

Pinellas County Traffic Management Center - TMC Regional Traffic Management

1: The center shall exchange traffic information with other traffic management centers including incident information, congestion data, traffic data, signal timing plans, and real-time signal control information.

Pinellas County Traffic Management Center - TMC Roadway Equipment Monitoring

1: The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) operational status.
2: The center shall collect and store CCTV surveillance system (traffic, pedestrian) operational status.
3: The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) fault data and send to the maintenance center for repair.
4: The center shall collect and store CCTV surveillance system (traffic, pedestrian) fault data send to the maintenance center for repair.

Pinellas County Traffic Management Center - 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.
4: The center shall collect traffic signal controller fault data from the field.
6: The center shall implement control plans to coordinate signalized intersections based on data from sensors.

Pinellas County Traffic Management Center - TMC Traffic Information Dissemination

1: The center shall remotely control dynamic messages signs for dissemination of traffic and other information to drivers.
5: The center shall retrieve locally stored traffic information, including current and forecasted traffic information, road and weather conditions, traffic incident information, information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements), and the definition of the road network itself.

Pinellas County Traffic Management Center - TMC Traffic Management Decision Support

1: The center shall provide center personnel with an integrated regional view of current and forecast road and traffic conditions including traffic incidents, special events, maintenance activities and other events or conditions that impact capacity or demand.

Pinellas County Traffic Management Center - TMC Traffic Network Performance Evaluation

1: The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements under remote control of the center to support overall network performance evaluations.
5: The center shall exchange traffic information with other traffic management centers, including incidents, congestion data, traffic data, signal timing plans, and real-time signal control information to support overall network performance evaluations.

Private Traveler Information Services - TIC Connected Vehicle Traveler Info Distribution

1: The center shall collect traveler information for distribution including traffic and road conditions, incident information, maintenance and construction information, event information, transit information, parking information, and weather information.
2: The center shall distribute location relevant traveler information to short range communications equipment at the roadside.

Private Traveler Information Services - TIC Data Collection

1: The center shall collect, process, and store traffic and highway condition information, including incident information, detours and road closures, event information, recommended routes, and current speeds on specific routes.
2: The transportation information center shall select real-time information on the state of the regional transportation system including current traffic and road conditions, weather conditions, transit information, parking information, special event and incident information.

Private Traveler Information Services - TIC Operations Data Collection

1: The center shall collect traveler information data, such as parking lot data, rideshare data, road network use data, vehicle probe data, and other data from traveler information system operations.
4: The center shall receive and respond to requests from ITS Archives for either a catalog of the traveler information data or for the data itself.

Private Traveler Information Services - TIC Traveler Information Broadcast

1: The center shall disseminate traffic and highway condition information to travelers, including incident information, detours and road closures, event information, recommended routes, and current speeds on specific routes.

Private Traveler Information Services - TMC Data Collection

1: The center shall collect traffic management data such as operational data, event logs, etc.

Private Travelers Personal Computing Devices - 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.

Private Travelers Personal Computing Devices - 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.

Private Travelers Personal Computing Devices - Personal Pedestrian Safety

1: The personal information device shall provide the current location (latitude, longitude, and elevation) of the non-motorized travelers.
5: The personal traveler interface shall provide the traveler with warnings about approaching vehicles.

Private Travelers Personal Computing Devices - Personal Traveler Information Reception

1: The personal traveler interface shall receive traffic information from a center and present it to the traveler.
2: The personal traveler interface shall receive transit information from a center and present it to the traveler.
3: The personal traveler interface shall receive event information from a center and present it to the traveler.

PSTA Transit Management Center - Emergency Data Collection

1: The center shall collect emergency service data, emergency vehicle management data, emergency vehicle data, sensor and surveillance data, threat data, and incident data.

PSTA Transit Management Center - 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.

PSTA Transit Management Center - 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.

PSTA Transit Management Center - TIC Operations Data Collection

1: The center shall collect traveler information data, such as parking lot data, rideshare data, road network use data, vehicle probe data, and other data from traveler information system operations.
2: The center shall collect traveler requests, confirmations, and payment transaction data for traveler services provided.

PSTA Transit Management Center - TIC Traffic Control Dissemination

1: The center shall provide intersection status, lane control information, and other real time traffic control related information to vehicles.
2: The center shall collect traffic control information from Traffic Management Center.
3: The center shall provide real time signal phase and timing information for all lanes at a signalized intersection to vehicle.

PSTA Transit Management Center - Transit Center Data Collection

1: The center shall collect transit management data such as transit fares and passenger use, transit services, paratransit operations, transit vehicle maintenance data, etc.
4: The transit management center shall produce sample products of the data available.

PSTA Transit Management Center - 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.
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.

PSTA Transit Vehicles - 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.

PSTA Transit 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.
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.

PSTA Transit 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.
2: The transit vehicle shall provide the capability for the transit vehicle operator to monitor and control the operation of the short range communication system.

PSTA 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.

PSTA Transit Vehicles - Vehicle Basic Safety Communication

1: The vehicle shall collect location and motion data from the vehicle platform.
2: The vehicle shall provide its location with lane-level accuracy to on-board applications.
3: The vehicle shall provide its location with road-level accuracy to on-board applications.
4: The vehicle shall collect road condition data from other vehicles.

PSTA Transit Vehicles - Vehicle Roadside Information Reception

1: The vehicle shall receive traveler information including traffic and road conditions, incident information, maintenance and construction information, event information, transit information, parking information, and weather information.
2: The vehicle shall receive advisory information, such as evacuation information, proximity to a maintenance and construction vehicle, wide-area alerts, work zone intrusion information, variable speed limits, tunnel entrance restrictions, and other special information.

PSTA Transit Vehicles - Vehicle Situation Data Monitoring

1: The Vehicle shall obtain data collection parameters from Connected Vehicle Roadside Equipment.
2: The Vehicle shall collect data collection parameters from Centers.
5: The Vehicle shall provide data to Centers in accordance with data collection parameters provided by Centers/Connected Vehicle Roadside Equipment.

Vehicles - 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

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.
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.

Vehicles - Vehicle Basic Safety Communication

2: The vehicle shall provide its location with lane-level accuracy to on-board applications.
3: The vehicle shall provide its location with road-level accuracy to on-board applications.
5: The vehicle shall calculate vehicle paths in order to determine if an impending collision is detected.
6: The vehicle shall exchange location and motion information with roadside equipment and nearby vehicles.

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.
3: The vehicle shall evaluate the likelihood of a collision between two vehicles or a vehicle and a stationary object, based on the proximity of other objects to the vehicle and the current speed and direction of the vehicle.
7: The vehicle shall provide position control adjustments and warnings to the driver when an object gets close enough to the vehicle to become a hazard if no action is taken by the driver.

Vehicles - Vehicle Control Warning

10: The Vehicle shall provide its location with lane-level accuracy to on-board warning applications.
11: The vehicle shall determine the trajectory of the host vehicle.
12: The vehicle shall determine if a crash between the host vehicle and a remote vehicle is imminent.
15: The vehicle shall acquire the current location and motion of remote vehicles to determine any slow moving vehicles which the host vehicle is approaching.
2: The vehicle shall evaluate the likelihood of a collision between two vehicles or a vehicle and a stationary object to warn the driver, based on the proximity of other objects to the vehicle, roadway characteristics, and the current speed and direction of the vehicle.
3: The vehicle shall provide position warnings to the driver when an object gets close enough to the vehicle to become a hazard if no action is taken by the driver.
6: The vehicle shall receive emergency vehicle location information.
7: The vehicle shall notify the Driver of the presence of emergency vehicles nearby that may affect the host vehicle.
8: The vehicle shall provide warnings to the driver based upon warnings received from nearby special vehicles.

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.
2: Vehicle shall provide data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size.
3: The vehicle shall receive intersection signal timing information in order for the vehicle to determine if it will safely cross the intersection given its current location and speed.
4: The vehicle shall be capable of providing warnings to the driver based upon information received regarding pedestrians, cyclists, and other non-motorized users that are sharing the roadway with the vehicle.
5: The vehicle shall receive warning from the infrastructure if an intersection violation appears to be imminent.
6: The vehicle shall provide to the driver a warning if it looks like the vehicle will go through the intersection after the signal has turned red.

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.
10: The Vehicle shall obtain intersection geometry information from Centers.
2: The Vehicle shall obtain parking facility geometry information from proximate Connected Vehicle Roadside Equipment.
3: The Vehicle shall obtain roadway geometry update information from proximate Connected Vehicle Roadside Equipment.
4: The Vehicle shall obtain intersection geometry update information from proximate Connected Vehicle Roadside Equipment.
5: The Vehicle shall provide its location to Centers.
6: The Vehicle shall obtain basemap updates from Centers.
7: The Vehicle shall obtain basemap update information from proximate Connected Vehicle Roadside Equipment.
8: The Vehicle shall obtain roadway geometry information from Centers.
9: The Vehicle shall obtain parking facility geometry information from Centers.

Vehicles - Vehicle Roadside Information Reception

1: The vehicle shall receive traveler information including traffic and road conditions, incident information, maintenance and construction information, event information, transit information, parking information, and weather information.
10: The vehicle shall receive customized real-time driving advice so that the vehicle or the driver can adjust their driving behavior to save fuel and reduce emissions.
6: The vehicle shall present to the driver a visual display of static sign information or dynamic roadway conditions information
7: The vehicle shall be capable of providing to the driver an audible presentation of static sign information or dynamic roadway conditions information

Vehicles - Vehicle Situation Data Monitoring

1: The Vehicle shall obtain data collection parameters from Connected Vehicle Roadside Equipment.
2: The Vehicle shall collect data collection parameters from Centers.
4: The vehicle shall provide traffic-related data including snapshots of measured speed and heading and events including starts and stops, speed changes, and other vehicle control from vehicle.
5: The Vehicle shall provide data to Centers in accordance with data collection parameters provided by Centers/Connected Vehicle Roadside Equipment.
6: The Vehicle shall provide data to Connected Vehicle Roadside Equipment. in accordance with data collection parameters provided by Centers/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.
12: The Vehicle shall receive traveler information from Connected Vehicle Roadside Equipment.
2: The vehicle shall receive transit information from a center and present it to the driver.
3: The vehicle shall receive event information from a center and present it to the driver.
9: The vehicle shall present information to the driver in audible or visual forms without impairing the driver's ability to control the vehicle in a safe manner.

Standards:

Project Operational Concepts:

Roles and Responsibilities

Florida Highway Patrol

Coordinate emergency response with county EOCs, local police, and county sheriffs.
Coordinate incident response with county and municipal public safety agencies; traffic management agencies; and the FDOT, as appropriate.
Dispatch FHP vehicles to incidents in the jurisdiction.
Provide incident information to traffic management and public safety agencies.

Private ISPs

Provide road network coditions data for archiving.

Travelers

Load pedestrian safety application on mobile device.
Operate vehicle.
Provide vehicle communication of collision warning, and location.

NOAA

Provide weather information to traffic management systems.
Provides daily weather forecasts, severe storm warnings and other weather related information that are used in surface transportation weather codition prediction.

Regional Public Safety Agencies

Receive emergency calls for incidents in the jurisdiction of 911 centers. Coordinate incident response with local public safety agencies, including police/fire/EMS agencies, county sheriffs, and the FHP.

County Public Safety Agencies

Install and maintain signal preemption equipment.
Participate in incident response, coordination, and reporting for the regional incident and mutual aid network.

FDOT District 7

Coordinate emergency plans, incident responses, and resources with the county EOC/warning points.
Coordinate regional traffic operations through controlling and accessing data of local agencies' ITS devices.
Coordinate regional traffic operations through sharing of FDOT ITS devices' control and data.
Coordinate traffic information with county and local TMCs.
Obtain traffic images and traffic flow data through CCTVs and field sensors, and maintain operational control of its own field equipment.

Pinellas County

Develop and maintain the Pinellas County Smart City Data Platform (SCDP).
Manage the data exchanges with the state and county transportation systems.

Pinellas Suncoast Transit Authority

Coordinate with the Pinellas County TMC, and the cities of Clearwater and St. Petersburg for traffic signal priority.
Receive road network conditions from Pinellas County Traffic Management Center.

City of Clearwater Traffic Operations Division

Coordinate traffic information and traffic control with Pinellas County.
Obtain traffic images and traffic flow data City of Clearwater CCTVs and field sensors, and maintain operational control of all field equipment.
Operate traffic signal systems on municipal-owned arterials.

City of St. Petersburg

Coordinate traffic information and traffic control with Pinellas County.
Obtain traffic images and traffic flow data from City of St. Petersburg CCTVs and field sensors, and maintain operational control of all field equipment.
Operate traffic signal systems on municipal-owned arterials.

Pinellas County PWD

Collect traffic and incident information, and provide it to the media and private travelers.
Coordinate emergency plans, incident responses, and resources with the county EOC/warning points.
Coordinate traffic information and traffic control with the City of Clearwater, City of St. Petersburg and FDOT District 7.
Obtain traffic images and traffic flow data from Pinellas County CCTVs and field sensors, and maintain operational control of all field equipment.
Operate traffic signal systems on county-owned arterials.
Provide emergency signal preemption for local and county fire vehicles.
Provide incident information to other traffic management and public safety agencies.
Provide traffic and road network information to local transit agencies.
Provide traffic information to travelers using county-owned DMS devices.
Provide traffic information to travelers using the county public information system, private companies, FL511, and the media.
Provide transit signal priority with roadside devices for Pinellas Suncoast Transit Authority (PSTA) transit vehicles.

Private Weather Information Providers

Provide weather information to traffic management systems.

FDOT CO

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

Region Personnel (Emergency and Maintenance)

Provide personnel location to field equipment.
Provide road inventory, work zone and video analytic data to Pinellas County Traffic Management Center.

Last Updated 8/15/2023