FDOT District 5 I-75 FRAME Ocala

Project Description: This I–75 Florida's Regional Advanced Mobility Elements (FRAME) project will deploy emerging technologies to better manage, operate, and maintain the multi–modal transportation system and create an Integrated Corridor Management solution on I–75 and state highway systems in the Cities of Gainesville and Ocala. This project focuses on the City of Ocala. The emerging technologies in this project are Automated Traffic Signal Performance Measures (ATSPM) and Connected Vehicle technologies such as Roadside Units (RSU) and On Board Units (OBU) for effective traffic operations; Transit Signal Priority (TSP) and Freight Signal Priority. The goal of the project is to disseminate real–time information to the motorists during freeway incidents.

Project Status: Planned

Project Stakeholders:

• City of Ocala
• Counties and Cities
• County and City Public Safety Agencies
• FDOT CO
• FDOT District 5
• Private Commercial Vehicle and Fleet Operators
• Rail Operator
• SUNTRAN
• Travelers

Project Service Packages:

• CVO06: Freight Signal Priority (FDOT I-75 FRAME Ocala Project)
• PT09: Transit Signal Priority (FDOT I-75 FRAME Ocala Project)
• TM06: Traffic Information Dissemination (FDOT I-75 FRAME Ocala Project)
• TM04: Connected Vehicle Traffic Signal System (FDOT I-75 FRAME Ocala)
• VS12: Vulnerable Road User Safety (FDOT I-75 FRAME Ocala Project)
• TM14: Advanced Railroad Grade Crossing (FDOT I-75 FRAME Ocala Project)
• SU04: Map Management (FDOT District 5 I-75 FRAME Ocala Project)
• SU02: Core Authorization (FDOT District 5 I-75 FRAME Ocala Project)
• SU08: Security and Credentials Management (FDOT District 5 I-75 FRAME Ocala Project)
• SU09: Device Certification and Enrollment (FDOT District 5 I-75 FRAME Ocala Project)

Project Information Flows:

Information Flow	Source Element	Destination Element	Status
arriving train information	FDOT District 5 Field Equipment	Private Travelers Personal Computing Devices	Planned
arriving train information	Railroad Operators Wayside Equipment	City of Ocala Field Equipment	Planned
arriving train information	Railroad Operators Wayside Equipment	FDOT District 5 Field Equipment	Planned
connection protection instructions	SUNTRAN Transit Dispatch Center	SUNTRAN Transit Vehicles	Planned
device enrollment information	CAV Authorizing Center	FDOT SCMS	Planned
device enrollment information	CAV-ITS Map Update System	FDOT SCMS	Planned
device enrollment information	City of Ocala Field Equipment	FDOT SCMS	Planned
device enrollment information	Commercial Vehicle	FDOT SCMS	Planned
device enrollment information	County Fire EMS/Rescue Vehicles	FDOT SCMS	Planned
device enrollment information	FDOT District 5 Field Equipment	FDOT SCMS	Planned
device enrollment information	Private Travelers Personal Computing Devices	FDOT SCMS	Planned
device enrollment information	SUNTRAN Transit Vehicles	FDOT SCMS	Planned
device identification	CAV Authorizing Center	City of Ocala TMC	Planned
device identification	CAV Authorizing Center	County Fire EMS/Rescue Dispatch	Planned
device identification	CAV Authorizing Center	FDOT District 5 RTMC	Planned
device identification	CAV Authorizing Center	SUNTRAN Transit Dispatch Center	Planned
device identification	CAV-ITS Map Update System	CAV Authorizing Center	Planned
device identification	City of Ocala Field Equipment	CAV Authorizing Center	Planned
device identification	City of Ocala TMC	CAV Authorizing Center	Planned
device identification	Commercial Vehicle	CAV Authorizing Center	Planned
device identification	Commercial Vehicle	City of Ocala TMC	Planned
device identification	County Fire EMS/Rescue Dispatch	CAV Authorizing Center	Planned
device identification	County Fire EMS/Rescue Vehicles	CAV Authorizing Center	Planned
device identification	FDOT District 5 Field Equipment	CAV Authorizing Center	Planned
device identification	FDOT District 5 RTMC	CAV Authorizing Center	Planned
device identification	FDOT SCMS	CAV Authorizing Center	Planned
device identification	Private Fleet Vehicle Dispatch Systems	CAV Authorizing Center	Planned
device identification	Private Travelers Personal Computing Devices	CAV Authorizing Center	Planned
device identification	SUNTRAN Transit Dispatch Center	CAV Authorizing Center	Planned
device identification	SUNTRAN Transit Vehicles	CAV Authorizing Center	Planned
enrollment credentials	FDOT SCMS	CAV Authorizing Center	Planned
enrollment credentials	FDOT SCMS	CAV-ITS Map Update System	Planned
enrollment credentials	FDOT SCMS	City of Ocala Field Equipment	Planned
enrollment credentials	FDOT SCMS	Commercial Vehicle	Planned
enrollment credentials	FDOT SCMS	County Fire EMS/Rescue Vehicles	Planned
enrollment credentials	FDOT SCMS	FDOT District 5 Field Equipment	Planned
enrollment credentials	FDOT SCMS	Private Travelers Personal Computing Devices	Planned
enrollment credentials	FDOT SCMS	SUNTRAN Transit Vehicles	Planned
equipment control commands	CAV Authorizing Center	FDOT District 5 Field Equipment	Planned
equipment maintenance request	CAV Authorizing Center	FDOT District 5 RTMC	Planned
high resolution signal controller data_ud	City of Ocala Field Equipment	City of Ocala TMC	Planned
high resolution signal controller data_ud	FDOT District 5 Field Equipment	FDOT District 5 RTMC	Planned
incident information	FDOT District 5 RTMC	Rail Operations Centers	Planned
incident information	Rail Operations Centers	FDOT District 5 RTMC	Planned
incident response status	FDOT District 5 RTMC	Rail Operations Centers	Planned
interactive traveler information	FL511	Private Travelers Personal Computing Devices	Planned
intersection geometry	CAV-ITS Map Update System	CAV Authorizing Center	Planned
intersection geometry	CAV-ITS Map Update System	County and City Field Equipment	Planned
intersection geometry	CAV-ITS Map Update System	County Fire EMS/Rescue Dispatch	Planned
intersection geometry	CAV-ITS Map Update System	FDOT District 5 Field Equipment	Planned
intersection geometry	CAV-ITS Map Update System	FDOT District 5 RTMC	Planned
intersection geometry	FDOT District 5 Field Equipment	Private Travelers Personal Computing Devices	Planned
intersection geometry	FDOT District 5 Field Equipment	SUNTRAN Transit Vehicles	Planned
intersection status	FDOT District 5 Field Equipment	Private Travelers Personal Computing Devices	Planned
intersection status	FDOT District 5 Field Equipment	SUNTRAN Transit Vehicles	Planned
local signal preemption request	County Fire EMS/Rescue Vehicles	City of Ocala Field Equipment	Planned
local signal preemption request	County Fire EMS/Rescue Vehicles	FDOT District 5 Field Equipment	Planned
local signal preemption request	County Fire Vehicles	City of Ocala Field Equipment	Planned
local signal preemption request	County Fire Vehicles	FDOT District 5 Field Equipment	Planned
local signal priority request	Commercial Vehicle	FDOT District 5 Field Equipment	Planned
local signal priority request	SUNTRAN Transit Vehicles	City of Ocala Field Equipment	Planned
local signal priority request	SUNTRAN Transit Vehicles	FDOT District 5 Field Equipment	Planned
local traveler information	FDOT District 5 Field Equipment	Private Travelers Personal Computing Devices	Planned
map update notification	City of Ocala TMC	CAV-ITS Map Update System	Planned
map update notification	FDOT District 5 RTMC	CAV-ITS Map Update System	Planned
map updates	CAV-ITS Map Update System	CAV Authorizing Center	Planned
map updates	CAV-ITS Map Update System	County and City Field Equipment	Planned
map updates	CAV-ITS Map Update System	County Fire EMS/Rescue Dispatch	Planned
map updates	CAV-ITS Map Update System	FDOT District 5 Field Equipment	Planned
map updates	CAV-ITS Map Update System	FDOT District 5 RTMC	Planned
map updates	CAV-ITS Map Update System	Private Fleet Vehicle Dispatch Systems	Planned
map updates	CAV-ITS Map Update System	SUNTRAN Transit Dispatch Center	Planned
misbehavior report	CAV Authorizing Center	FDOT SCMS	Planned
misbehavior report	City of Ocala Field Equipment	FDOT SCMS	Planned
misbehavior report	Commercial Vehicle	FDOT SCMS	Planned
misbehavior report	FDOT District 5 Field Equipment	FDOT SCMS	Planned
misbehavior report	Private Travelers Personal Computing Devices	FDOT SCMS	Planned
misbehavior report	SUNTRAN Transit Vehicles	FDOT SCMS	Planned
multimodal information_ud	Rail Operations Centers	City of Ocala TMC	Planned
multimodal information_ud	Rail Operations Centers	FDOT District 5 RTMC	Planned
on-board vehicle data	Commercial Vehicle	Private Fleet Vehicle Dispatch Systems	Planned
permission application	CAV Authorizing Center	City of Ocala TMC	Planned
permission application	CAV Authorizing Center	County Fire EMS/Rescue Dispatch	Planned
permission application	CAV Authorizing Center	FDOT District 5 RTMC	Planned
permission application	CAV Authorizing Center	SUNTRAN Transit Dispatch Center	Planned
permission application	CAV-ITS Map Update System	CAV Authorizing Center	Planned
permission application	City of Ocala Field Equipment	CAV Authorizing Center	Planned
permission application	City of Ocala TMC	CAV Authorizing Center	Planned
permission application	Commercial Vehicle	CAV Authorizing Center	Planned
permission application	Commercial Vehicle	City of Ocala TMC	Planned
permission application	County Fire EMS/Rescue Dispatch	CAV Authorizing Center	Planned
permission application	County Fire EMS/Rescue Vehicles	CAV Authorizing Center	Planned
permission application	FDOT District 5 Field Equipment	CAV Authorizing Center	Planned
permission application	FDOT District 5 RTMC	CAV Authorizing Center	Planned
permission application	FDOT SCMS	CAV Authorizing Center	Planned
permission application	Private Fleet Vehicle Dispatch Systems	CAV Authorizing Center	Planned
permission application	Private Travelers Personal Computing Devices	CAV Authorizing Center	Planned
permission application	SUNTRAN Transit Dispatch Center	CAV Authorizing Center	Planned
permission application	SUNTRAN Transit Vehicles	CAV Authorizing Center	Planned
permission application receipt	CAV Authorizing Center	City of Ocala Field Equipment	Planned
permission application receipt	CAV Authorizing Center	City of Ocala TMC	Planned
permission application receipt	CAV Authorizing Center	County Fire EMS/Rescue Dispatch	Planned
permission application receipt	CAV Authorizing Center	County Fire EMS/Rescue Vehicles	Planned
permission application receipt	CAV Authorizing Center	FDOT District 5 Field Equipment	Planned
permission application receipt	CAV Authorizing Center	FDOT District 5 RTMC	Planned
permission application receipt	CAV Authorizing Center	FDOT SCMS	Planned
permission application receipt	CAV Authorizing Center	Private Travelers Personal Computing Devices	Planned
permission application receipt	CAV Authorizing Center	SUNTRAN Transit Dispatch Center	Planned
permission application receipt	CAV Authorizing Center	SUNTRAN Transit Vehicles	Planned
permission application receipt	City of Ocala TMC	CAV Authorizing Center	Planned
permission application receipt	City of Ocala TMC	Commercial Vehicle	Planned
permission application receipt	County Fire EMS/Rescue Dispatch	CAV Authorizing Center	Planned
permission application receipt	FDOT District 5 RTMC	CAV Authorizing Center	Planned
permission application receipt	Private Fleet Vehicle Dispatch Systems	CAV Authorizing Center	Planned
permission application receipt	SUNTRAN Transit Dispatch Center	CAV Authorizing Center	Planned
permission request	City of Ocala TMC	CAV Authorizing Center	Planned
permission request	County Fire EMS/Rescue Dispatch	CAV Authorizing Center	Planned
permission request	FDOT District 5 RTMC	CAV Authorizing Center	Planned
permission request	Private Fleet Vehicle Dispatch Systems	CAV Authorizing Center	Planned
permission request	SUNTRAN Transit Dispatch Center	CAV Authorizing Center	Planned
permission request received	CAV Authorizing Center	City of Ocala TMC	Planned
permission request received	CAV Authorizing Center	County Fire EMS/Rescue Dispatch	Planned
permission request received	CAV Authorizing Center	FDOT District 5 RTMC	Planned
permission request received	CAV Authorizing Center	SUNTRAN Transit Dispatch Center	Planned
permission update request	City of Ocala TMC	CAV Authorizing Center	Planned
permission update request	County Fire EMS/Rescue Dispatch	CAV Authorizing Center	Planned
permission update request	FDOT District 5 RTMC	CAV Authorizing Center	Planned
permission update request	Private Fleet Vehicle Dispatch Systems	CAV Authorizing Center	Planned
permission update request	SUNTRAN Transit Dispatch Center	CAV Authorizing Center	Planned
personal crossing safety information	FDOT District 5 Field Equipment	Private Travelers Personal Computing Devices	Planned
personal location	Private Travelers Personal Computing Devices	FDOT District 5 Field Equipment	Planned
personal signal service request	Private Travelers Personal Computing Devices	FDOT District 5 Field Equipment	Planned
personal transit information	SUNTRAN Transit Dispatch Center	Private Travelers Personal Computing Devices	Planned
rail crossing advisories	City of Ocala TMC	Rail Operations Centers	Planned
rail crossing advisories	FDOT District 5 RTMC	Rail Operations Centers	Planned
rail crossing blockage notification	City of Ocala Field Equipment	Railroad Operators Wayside Equipment	Planned
rail crossing blockage notification	FDOT District 5 Field Equipment	Railroad Operators Wayside Equipment	Planned
rail crossing control data	City of Ocala TMC	City of Ocala Field Equipment	Planned
rail crossing operational status	City of Ocala Field Equipment	Railroad Operators Wayside Equipment	Planned
rail crossing operational status	FDOT District 5 Field Equipment	Railroad Operators Wayside Equipment	Planned
rail crossing request	City of Ocala TMC	City of Ocala Field Equipment	Planned
rail crossing status	City of Ocala Field Equipment	City of Ocala TMC	Planned
rail crossing warning	FDOT District 5 Field Equipment	Private Travelers Personal Computing Devices	Planned
rail incident response status	Rail Operations Centers	FDOT District 5 RTMC	Planned
rail system status assessment	Rail Operations Centers	FDOT District 5 RTMC	Planned
railroad advisories	Rail Operations Centers	City of Ocala TMC	Planned
railroad advisories	Rail Operations Centers	FDOT District 5 RTMC	Planned
railroad schedules	Rail Operations Centers	City of Ocala TMC	Planned
railroad schedules	Rail Operations Centers	FDOT District 5 RTMC	Planned
right-of-way request notification	City of Ocala Field Equipment	City of Ocala TMC	Planned
right-of-way request notification	FDOT District 5 Field Equipment	FDOT District 5 RTMC	Planned
roadway dynamic signage data	City of Ocala TMC	City of Ocala Field Equipment	Planned
roadway dynamic signage data	FDOT District 5 RTMC	FDOT District 5 Field Equipment	Planned
roadway dynamic signage status	City of Ocala Field Equipment	City of Ocala TMC	Planned
roadway dynamic signage status	FDOT District 5 Field Equipment	FDOT District 5 RTMC	Planned
roadway geometry	CAV-ITS Map Update System	County and City Field Equipment	Planned
roadway geometry	CAV-ITS Map Update System	FDOT District 5 Field Equipment	Planned
RSE application information	CAV Authorizing Center	FDOT District 5 Field Equipment	Planned
RSE application install/upgrade	CAV Authorizing Center	FDOT District 5 Field Equipment	Planned
RSE application status	FDOT District 5 Field Equipment	CAV Authorizing Center	Planned
security credential revocations	FDOT SCMS	CAV Authorizing Center	Planned
security credential revocations	FDOT SCMS	CAV-ITS Map Update System	Planned
security credential revocations	FDOT SCMS	City of Ocala Field Equipment	Planned
security credential revocations	FDOT SCMS	Commercial Vehicle	Planned
security credential revocations	FDOT SCMS	FDOT District 5 Field Equipment	Planned
security credential revocations	FDOT SCMS	Private Travelers Personal Computing Devices	Planned
security credential revocations	FDOT SCMS	SUNTRAN Transit Vehicles	Planned
security credentials	FDOT SCMS	CAV Authorizing Center	Planned
security credentials	FDOT SCMS	CAV-ITS Map Update System	Planned
security credentials	FDOT SCMS	City of Ocala Field Equipment	Planned
security credentials	FDOT SCMS	Commercial Vehicle	Planned
security credentials	FDOT SCMS	FDOT District 5 Field Equipment	Planned
security credentials	FDOT SCMS	Private Travelers Personal Computing Devices	Planned
security credentials	FDOT SCMS	SUNTRAN Transit Vehicles	Planned
security policy and networking information	FDOT SCMS	CAV Authorizing Center	Planned
security policy and networking information	FDOT SCMS	CAV-ITS Map Update System	Planned
security policy and networking information	FDOT SCMS	City of Ocala Field Equipment	Planned
security policy and networking information	FDOT SCMS	Commercial Vehicle	Planned
security policy and networking information	FDOT SCMS	County Fire EMS/Rescue Vehicles	Planned
security policy and networking information	FDOT SCMS	FDOT District 5 Field Equipment	Planned
security policy and networking information	FDOT SCMS	Private Travelers Personal Computing Devices	Planned
security policy and networking information	FDOT SCMS	SUNTRAN Transit Vehicles	Planned
signal control commands	City of Ocala TMC	City of Ocala Field Equipment	Planned
signal control commands	FDOT District 5 RTMC	FDOT District 5 Field Equipment	Planned
signal control device configuration	City of Ocala TMC	City of Ocala Field Equipment	Planned
signal control device configuration	FDOT District 5 RTMC	FDOT District 5 Field Equipment	Planned
signal control plans	City of Ocala TMC	City of Ocala Field Equipment	Planned
signal control plans	FDOT District 5 RTMC	FDOT District 5 Field Equipment	Planned
signal control status	City of Ocala Field Equipment	City of Ocala TMC	Planned
signal control status	FDOT District 5 Field Equipment	FDOT District 5 RTMC	Planned
signal fault data	City of Ocala Field Equipment	City of Ocala TMC	Planned
signal fault data	FDOT District 5 Field Equipment	FDOT District 5 RTMC	Planned
signal priority status	FDOT District 5 Field Equipment	Commercial Vehicle	Planned
signal priority status	FDOT District 5 Field Equipment	County Fire EMS/Rescue Vehicles	Planned
signal priority status	FDOT District 5 Field Equipment	County Fire Vehicles	Planned
signal priority status	FDOT District 5 Field Equipment	SUNTRAN Transit Vehicles	Planned
signal system configuration	FDOT District 5 RTMC	FDOT District 5 Field Equipment	Planned
track status	Railroad Operators Wayside Equipment	City of Ocala Field Equipment	Planned
track status	Railroad Operators Wayside Equipment	FDOT District 5 Field Equipment	Planned
traffic situation data	FDOT District 5 Field Equipment	FDOT District 5 RTMC	Planned
transfer request	Private Travelers Personal Computing Devices	SUNTRAN Transit Dispatch Center	Planned
transfer request	SUNTRAN Transit Vehicles	SUNTRAN Transit Dispatch Center	Planned
transfer status	SUNTRAN Transit Dispatch Center	Private Travelers Personal Computing Devices	Planned
transfer status	SUNTRAN Transit Dispatch Center	SUNTRAN Transit Vehicles	Planned
transit information user request	Private Travelers Personal Computing Devices	SUNTRAN Transit Dispatch Center	Planned
transit schedule information	SUNTRAN Transit Dispatch Center	SUNTRAN Transit Vehicles	Planned
transit traveler information	SUNTRAN Transit Dispatch Center	SUNTRAN Transit Vehicles	Planned
transit traveler request	SUNTRAN Transit Vehicles	SUNTRAN Transit Dispatch Center	Planned
transit user information	SUNTRAN Transit Vehicles	SUNTRAN Transit Dispatch Center	Planned
transit vehicle location data	SUNTRAN Transit Vehicles	SUNTRAN Transit Dispatch Center	Planned
transit vehicle schedule performance	SUNTRAN Transit Vehicles	SUNTRAN Transit Dispatch Center	Planned
transportation system status	FDOT District 5 RTMC	Rail Operations Centers	Planned
traveler alerts	FL511	Private Travelers Personal Computing Devices	Planned
traveler request	Private Travelers Personal Computing Devices	FL511	Planned
trip confirmation	Private Travelers Personal Computing Devices	FL511	Planned
trip confirmation	Private Travelers Personal Computing Devices	SUNTRAN Transit Dispatch Center	Planned
trip plan	FL511	Private Travelers Personal Computing Devices	Planned
trip plan	SUNTRAN Transit Dispatch Center	Private Travelers Personal Computing Devices	Planned
trip request	Private Travelers Personal Computing Devices	FL511	Planned
user permission sets	CAV Authorizing Center	FDOT SCMS	Planned
user profile	Private Travelers Personal Computing Devices	FL511	Planned
vehicle control	Vehicle	Commercial Vehicle	Planned
vehicle location and motion	Commercial Vehicle	FDOT District 5 Field Equipment	Planned
vehicle location and motion	SUNTRAN Transit Vehicles	FDOT District 5 Field Equipment	Planned
vehicle location and motion	Vehicle	FDOT District 5 Field Equipment	Planned
vehicle profile	Vehicle	FDOT District 5 Field Equipment	Planned
vehicle signage data	FDOT District 5 Field Equipment	Vehicle	On-going

Project Functional Requirements (Element - Functional Object):

• 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 - Center Permission Management
• 1: The Center shall manage the device permission request process on behalf of the devices it manages.
• 2: The Center shall acquire device identification information from ITS Objects it manages.
• 3: The Center shall request permissions for ITS Objects it manages from a center authorized to manage those permissions.
• 4: The Center shall request permissions for itself from a center authorized to manage those permissions.
• 5: The Center shall maintain the status of ITS Object permission requests.
• 6: The Center shall notify the ITS Object of the status of its permission request.
• 7: The Center shall accept permissions requests from ITS Object.


• CAV Authorizing Center - Core Authorization
• 1: The Center shall provide valid user permission information to the CCMS
• 2: The Center shall provide a response to the requesting Center identifying the validity and status of the permission request.
• 3: The Center shall determine if a permission request is valid.
• 4: The Center shall coordinate user permission information with other centers authorized to provide that information.
• 5: The Center shall accept permissions requests from Centers.


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


• CAV-ITS Map Update System - Map Management
• 1: The Center shall collect Vehicle location information from Vehicles.
• 2: The Center shall collect updates to roadway geometry from other Centers.
• 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 Ocala Field Equipment - ITS Security Support
• 1: The ITS Object shall obtain security policy information from the Cooperative Intelligent Transportation System Credentials Management System (CCMS).
• 2: The ITS Object shall request enrollment credentials from the CCMS.
• 3: The ITS Object shall obtain the CCMS' trust credentials.
• 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.


• City of Ocala Field Equipment - Roadway Advanced Rail Crossing
• 1: The field element shall collect and process, traffic sensor data in the vicinity of an advanced highway-rail intersection (HRI).
• 2: The field element shall determine whether the highway-rail intersection (HRI) is blocked by traffic in the roadway or some other obstruction.
• 3: The field element shall notify the traffic management center and the rail wayside equipment of any intersection blockages, including trapped vehicles or other obstructions.
• 4: The field element shall monitor the status of the advanced highway-rail intersection (HRI) equipment, including both the current state and mode of operation and the current equipment condition, to be forwarded on to the traffic management center.


• City of Ocala 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.
• 4: The field element shall return sensor and CCTV system operational status to the controlling center.
• 6: The field element shall collect, process, and send traffic images to the center for further wrong way vehicle entries analysis and detection.


• City of Ocala 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.


• City of Ocala 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.
• 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.


• City of Ocala Field Equipment - Roadway Signal Preemption
• 1: The field element shall respond to signal preemption requests from emergency vehicles.


• City of Ocala 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).
• 3: The field element shall provide operational status for the driver information systems equipment (DMS, HAR, etc.) to the center.


• City of Ocala 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.
• 4: The field element shall receive signal prioity requests from commercial vehicles and forward to the traffic signal controller.
• 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.
• 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.


• City of Ocala 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.
• 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.


• City of Ocala Field Equipment - RSE Map Management
• 1: The field element shall collect broadcasted vehicle location and motion information.
• 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.


• City of Ocala Field Equipment - RSE Rail Crossing Warning
• 1: The field element shall identify a train approaching or already in a highway rail intersection and activate warning signs to approaching motorists.
• 10: The field element shall acquire railroad crossing intersection geometry information.
• 11: The field element shall warn the driver of a potential crash at a railroad grade crossing.
• 12: The field element shall calculate whether the vehicle may approach the railroad intersection while a train is present in the intersection.
• 2: The field element shall autonomously identify a train is approaching or already in the highway rail intersection and activate warning signs to approaching motorists.
• 3: The field element shall provide collected vehicle location information to the controlling center.
• 4: The field element shall provide train arrival information to approaching vehicles.
• 5: The field element shall monitor connected vehicles that may intrude on the crossing.
• 6: The field element shall provide collected pedestrians and other non motorist location information to the controlling center.
• 7: The field element shall collect the current status of the wayside equipment and notification of an arriving train.
• 8: The field element shall receive commands from the controlling center that activate warning signs to approaching vehicles, pedestrians and non motorist vehicles.
• 9: The field element shall warn drivers of crossing closures due to oncoming trains.


• City of Ocala 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 provide vehicle situation data to a center for archival.
• 3: The field element shall provide data collection parameters to vehicles.


• City of Ocala 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.


• City of Ocala TMC - Center Map Management
• 1: The Center shall collect updates to basemaps from Map Update Systems .


• City of Ocala TMC - Center Permission Management
• 1: The Center shall manage the device permission request process on behalf of the devices it manages.
• 2: The Center shall acquire device identification information from ITS Objects it manages.
• 3: The Center shall request permissions for ITS Objects it manages from a center authorized to manage those permissions.
• 4: The Center shall request permissions for itself from a center authorized to manage those permissions.
• 5: The Center shall maintain the status of ITS Object permission requests.
• 6: The Center shall notify the ITS Object of the status of its permission request.
• 7: The Center shall accept permissions requests from ITS Object.


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


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


• City of Ocala TMC - TMC Advanced Rail Crossing Management
• 1: The center shall remotely control highway-rail intersection (HRI) equipment located in the field.
• 2: The center shall accept collect highway-rail intersection (HRI) advisory or alert data from rail operations centers.
• 4: The center shall provide the highway-rail intersection (HRI) equipment operational status to rail operations centers.
• 6: The center shall implement control plans to coordinate signalized intersections around highway-rail intersections (HRI), under control of center personnel, based on data from sensors and surveillance monitoring traffic conditions, incidents, equipment faults, pedestrian crossings, etc.
• 7: The center shall accept train schedules, maintenance schedules, and any other forecast events that will result in highway-rail intersection (HRI) closures data from rail operations centers.


• City of Ocala TMC - TMC Basic Surveillance
• 1: The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements under remote control of the center.
• 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.
• 6: The center shall maintain a database of surveillance equipment and sensors and associated data (including the roadway on which they are located, the type of data collected, and the ownership of each).
• 7: The center shall remotely control devices to detect traffic.


• City of Ocala TMC - 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.
• 5: The field element shall be capable of configuring roadside equipment to perform the collection and transmission of information to support intersection safety.


• City of Ocala TMC - TMC Multi-Modal Coordination
• 1: The center shall respond to requests from transit management centers for signal priority at one or more intersections along a particular transit route.
• 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.


• City of Ocala TMC - 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.
• 4: The center shall collect and store CCTV surveillance system (traffic, pedestrian) fault data send to the maintenance center for repair.


• City of Ocala TMC - TMC Signal Control
• 1: The center shall remotely control traffic signal controllers.
• 10: The center shall adjust signal timing in respond to a signal prioritization, signal preemption, pedestrian call, multi-modal crossing activation, or other requests for right-of-way.
• 11: The center shall collect commercial vehicle data (e.g., characteristics, route, schedule) for intermodal freight events.
• 3: The center shall collect traffic signal controller operational status and compare against the control information sent by the center.
• 4: The center shall collect traffic signal controller fault data from the field.
• 5: The center shall manage (define, store and modify) control plans to coordinate signalized intersections, to be engaged at the direction of center personnel or according to a daily schedule.
• 6: The center shall implement control plans to coordinate signalized intersections based on data from sensors.
• 7: The center shall manage boundaries of the control sections used within the signal system.
• 8: The center shall maintain traffic signal coordination including synchronizing clocks throughout the system.


• City of Ocala TMC - TMC Traffic Information Dissemination
• 1: The center shall remotely control dynamic messages signs for dissemination of traffic and other information to drivers.
• 3: The center shall collect operational status for the driver information systems equipment (DMS, HAR, etc.).


• Commercial Vehicle - CV On-Board Signal Priority
• 1: The commercial vehicle shall request priority at a signalized intersection, including signals at the entrance to or exit from an intermodal shipping facility.
• 2: The commercial vehicle shall provide vehicle location and motion information to local connected vehicle equipment near signalized intersections.


• Commercial Vehicle - 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.


• Commercial Vehicle - ITS Security Support
• 1: The ITS Object shall obtain security policy information from the Cooperative Intelligent Transportation System Credentials Management System (CCMS).
• 2: The ITS Object shall request enrollment credentials from the CCMS.
• 3: The ITS Object shall obtain the CCMS' trust credentials.
• 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.


• Commercial Vehicle - 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.
• 7: The vehicle shall receive warnings, informational road signs, traffic meters, and signals provided by infrastructure devices.


• Commercial Vehicle - Vehicle Control Automation
• 1: The vehicle shall monitor the area behind and in front of the vehicle to determine the proximity of other objects to the vehicle.
• 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.
• 5: The Vehicle shall provide its location with lane-level accuracy to on-board control automation applications.
• 6: 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, roadway characteristics, and the current speed and direction of the vehicle.


• Commercial Vehicle - Vehicle Intersection Warning
• 1: Vehicle shall provide vehicle path information to identify if vehicle is performing an unpermitted movement at an intersection such as a stop sign violation or running a red light.
• 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.


• Commercial Vehicle - Vehicle Map Management
• 1: The Vehicle shall make basemap, roadway geometry, intersection geometry and parking facility geometry information available to other onboard vehicle applications.
• 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.


• Commercial Vehicle - Vehicle Rail Crossing Warning
• 1: Vehicle shall receive alerts of trains entering HRIs and provide warnings to drivers regarding the trains.


• Commercial Vehicle - 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.


• County and City 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.


• County Fire EMS/Rescue Dispatch - Emergency Call-Taking
• 1: The emergency call-taking center shall support the interface to the Emergency Telecommunications System (e.g. 911 or 7-digit call routing) to receive emergency notification information and provide it to the emergency system operator.
• 2: The emergency call-taking center shall receive emergency call information from 911 services and present the possible incident information to the emergency system operator.
• 3: The emergency call-taking center shall receive emergency call information from vehicles and present the possible incident information to the emergency system operator.


• 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.
• 3: The emergency vehicle, including roadway service patrols, shall receive incident details and a suggested route when dispatched to a scene.
• 4: The emergency vehicle shall send the current en route status (including estimated time of arrival) and requests for emergency dispatch updates.
• 5: The emergency vehicle shall send requests to traffic signal control equipment at the roadside to preempt the signal.
• 6: The emergency vehicle shall provide the personnel on-board with dispatch information, including incident type and location, and forward an acknowledgment from personnel to the center that the vehicle is on its way to the incident scene.


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


• County Fire Vehicles - EV On-Board En Route Support
• 1: The emergency vehicle, including roadway service patrols, shall track its current location.
• 4: The emergency vehicle shall send the current en route status (including estimated time of arrival) and requests for emergency dispatch updates.
• 5: The emergency vehicle shall send requests to traffic signal control equipment at the roadside to preempt the signal.
• 6: The emergency vehicle shall provide the personnel on-board with dispatch information, including incident type and location, and forward an acknowledgment from personnel to the center that the vehicle is on its way to the incident scene.


• FDOT District 5 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.


• FDOT District 5 Field Equipment - ITS Security Support
• 1: The ITS Object shall obtain security policy information from the Cooperative Intelligent Transportation System Credentials Management System (CCMS).
• 2: The ITS Object shall request enrollment credentials from the CCMS.
• 3: The ITS Object shall obtain the CCMS' trust credentials.
• 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.


• FDOT District 5 Field Equipment - Roadway Advanced Rail Crossing
• 1: The field element shall collect and process, traffic sensor data in the vicinity of an advanced highway-rail intersection (HRI).
• 2: The field element shall determine whether the highway-rail intersection (HRI) is blocked by traffic in the roadway or some other obstruction.
• 3: The field element shall notify the traffic management center and the rail wayside equipment of any intersection blockages, including trapped vehicles or other obstructions.
• 4: The field element shall monitor the status of the advanced highway-rail intersection (HRI) equipment, including both the current state and mode of operation and the current equipment condition, to be forwarded on to the traffic management center.
• 5: The field element shall monitor the status of the advanced highway-rail intersection (HRI) equipment, including both the current state and mode of operation and the current equipment condition, to be forwarded on to the rail wayside equipment.
• 8: The field element shall control the dynamic message signs (DMS) in the vicinity of an advanced highway-rail intersection (HRI) to advise drivers, cyclists, and pedestrians of approaching trains.
• 9: The field element shall close the highway-rail intersection (HRI) when a train is approaching with enough time for traffic to safely clear the crossing using gates, lights/signs, barriers, and traffic control signals.


• FDOT District 5 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.
• 4: The field element shall return sensor and CCTV system operational status to the controlling center.
• 5: The field element shall return sensor and CCTV system fault data to the controlling center for repair.
• 6: The field element shall collect, process, and send traffic images to the center for further wrong way vehicle entries analysis and detection.


• FDOT District 5 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.


• FDOT District 5 Field Equipment - Roadway Signal Control
• 1: The field element shall control traffic signals under center control.
• 10: The field element shall receive request for transit vehicle signal priority.
• 11: The field element shall receive request for commercial vehicle signal priority.
• 12: The field element shall report current commercial vehicle priority status to the center.
• 14: The field element shall provide data to the Connected Vehicle Roadside Equipment.
• 15: The field element shall receive requests for emergency vehicle signal preemption.
• 16: The field element shall receive request for signal change from an emissions/environmental field device.
• 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.


• FDOT District 5 Field Equipment - Roadway Signal Preemption
• 1: The field element shall respond to signal preemption requests from emergency vehicles.
• 2: The field element shall inform the controlling center when preemption requests have been received.
• 3: The field element shall send the preemption request to the signal controller to immediately preempt the signal for the requested direction.


• FDOT District 5 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).
• 3: The field element shall provide operational status for the driver information systems equipment (DMS, HAR, etc.) to the center.
• 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.


• FDOT District 5 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.
• 4: The field element shall receive signal prioity requests from commercial vehicles and forward to the traffic signal controller.
• 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.
• 9: The field element shall collect current signal phase and timing data from the traffic signal controller.


• FDOT District 5 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.


• FDOT District 5 Field Equipment - RSE Map Management
• 1: The field element shall collect broadcasted vehicle location and motion information.
• 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.


• FDOT District 5 Field Equipment - RSE Rail Crossing Warning
• 1: The field element shall identify a train approaching or already in a highway rail intersection and activate warning signs to approaching motorists.
• 10: The field element shall acquire railroad crossing intersection geometry information.
• 11: The field element shall warn the driver of a potential crash at a railroad grade crossing.
• 12: The field element shall calculate whether the vehicle may approach the railroad intersection while a train is present in the intersection.
• 2: The field element shall autonomously identify a train is approaching or already in the highway rail intersection and activate warning signs to approaching motorists.
• 3: The field element shall provide collected vehicle location information to the controlling center.
• 4: The field element shall provide train arrival information to approaching vehicles.
• 5: The field element shall monitor connected vehicles that may intrude on the crossing.
• 6: The field element shall provide collected pedestrians and other non motorist location information to the controlling center.
• 7: The field element shall collect the current status of the wayside equipment and notification of an arriving train.
• 8: The field element shall receive commands from the controlling center that activate warning signs to approaching vehicles, pedestrians and non motorist vehicles.
• 9: The field element shall warn drivers of crossing closures due to oncoming trains.


• FDOT District 5 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 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.


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


• FDOT District 5 RTMC - 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 5 RTMC - Center Permission Management
• 1: The Center shall manage the device permission request process on behalf of the devices it manages.
• 2: The Center shall acquire device identification information from ITS Objects it manages.
• 3: The Center shall request permissions for ITS Objects it manages from a center authorized to manage those permissions.
• 4: The Center shall request permissions for itself from a center authorized to manage those permissions.
• 5: The Center shall maintain the status of ITS Object permission requests.
• 6: The Center shall notify the ITS Object of the status of its permission request.
• 7: The Center shall accept permissions requests from ITS Object.


• FDOT District 5 RTMC - 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.
• 6: The center shall track current emergency vehicle location and status along with other emergency vehicle characteristics.
• 7: The center shall calculate emergency vehicle routes, under center personnel control, based on the collected traffic and road conditions information.


• FDOT District 5 RTMC - 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 5 RTMC - ITS Security Support
• 1: The ITS Object shall obtain security policy information from the Cooperative Intelligent Transportation System Credentials Management System (CCMS).
• 2: The ITS Object shall request enrollment credentials from the CCMS.
• 3: The ITS Object shall obtain the CCMS' trust credentials.
• 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.


• FDOT District 5 RTMC - 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.


• FDOT District 5 RTMC - TMC Advanced Rail Crossing Management
• 1: The center shall remotely control highway-rail intersection (HRI) equipment located in the field.
• 2: The center shall accept collect highway-rail intersection (HRI) advisory or alert data from rail operations centers.
• 3: The center shall collect highway-rail intersection (HRI) equipment operational status and compare against the control information sent by the center.
• 4: The center shall provide the highway-rail intersection (HRI) equipment operational status to rail operations centers.
• 5: The center shall collect incident information related to a highway-rail intersection (HRI), such as intersection blockages or crashes or equipment malfunctions.
• 6: The center shall implement control plans to coordinate signalized intersections around highway-rail intersections (HRI), under control of center personnel, based on data from sensors and surveillance monitoring traffic conditions, incidents, equipment faults, pedestrian crossings, etc.
• 7: The center shall accept train schedules, maintenance schedules, and any other forecast events that will result in highway-rail intersection (HRI) closures data from rail operations centers.


• FDOT District 5 RTMC - 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.


• FDOT District 5 RTMC - 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.
• 4: The field element shall be capable of providing intersection priority for pedestrians or bicyclists based upon requests from the pedestrians or bicyclists
• 5: The field element shall be capable of configuring roadside equipment to perform the collection and transmission of information to support intersection safety.


• FDOT District 5 RTMC - TMC Multi-Modal Coordination
• 1: The center shall respond to requests from transit management centers for signal priority at one or more intersections along a particular transit route.
• 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.
• 3: The center shall provide an integrated operations strategy for the parking facilities in the area. These strategies can include dynamic adjustments to parking fees and restrictions, and other active demand management strategies.


• FDOT District 5 RTMC - 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.


• FDOT District 5 RTMC - TMC Signal Control
• 1: The center shall remotely control traffic signal controllers.
• 11: The center shall collect commercial vehicle data (e.g., characteristics, route, schedule) for intermodal freight events.
• 14: The center shall support requests from emergency management centers to provide responding emergency vehicles with signal preemption.
• 15: The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements at or near signalized intersections.
• 3: The center shall collect traffic signal controller operational status and compare against the control information sent by the center.
• 4: The center shall collect traffic signal controller fault data from the field.
• 5: The center shall manage (define, store and modify) control plans to coordinate signalized intersections, to be engaged at the direction of center personnel or according to a daily schedule.
• 6: The center shall implement control plans to coordinate signalized intersections based on data from sensors.
• 7: The center shall manage boundaries of the control sections used within the signal system.
• 8: The center shall maintain traffic signal coordination including synchronizing clocks throughout the system.


• FDOT District 5 RTMC - TMC Traffic Information Dissemination
• 1: The center shall remotely control dynamic messages signs for dissemination of traffic and other information to drivers.
• 2: The center shall remotely control driver information systems that communicate directly from a center to the vehicle radio (such as Highway Advisory Radios) for dissemination of traffic and other information to drivers.
• 3: The center shall collect operational status for the driver information systems equipment (DMS, HAR, etc.).


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


• FL511 - TIC Data Collection
• 2: The 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.


• FL511 - TIC Interactive Traveler Information
• 1: The center shall disseminate customized traffic and highway condition information to travelers, including incident information, detours and road closures, recommended routes, and current speeds on specific routes upon request.
• 3: The center shall disseminate customized transit routes and schedules, transit transfer options, transit fares, and real-time schedule adherence information to travelers upon request.


• FL511 - 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.
• 2: The center shall disseminate maintenance and construction information to travelers, including scheduled maintenance and construction work activities and work zone activities.
• 6: The center shall disseminate weather information to travelers.
• 7: The center shall disseminate event information to travelers.


• Private Fleet Vehicle Dispatch Systems - Center Map Management
• 1: The Center shall collect updates to basemaps from Map Update Systems .


• Private Fleet Vehicle Dispatch Systems - Center Permission Management
• 1: The Center shall manage the device permission request process on behalf of the devices it manages.
• 2: The Center shall acquire device identification information from ITS Objects it manages.
• 3: The Center shall request permissions for ITS Objects it manages from a center authorized to manage those permissions.
• 4: The Center shall request permissions for itself from a center authorized to manage those permissions.
• 5: The Center shall maintain the status of ITS Object permission requests.
• 6: The Center shall notify the ITS Object of the status of its permission request.
• 7: The Center shall accept permissions requests from ITS Object.


• Private Fleet Vehicle Dispatch Systems - Freight Administration and Management
• 1: The center shall collect data from the commercial vehicles carrying freight or from the freight equipment itself. Data includes container, trailer, or chassis information regarding identity, type, location, brake wear data, mileage, seal number/type, door open/close status, chassis bare/covered status, tethered/untethered status, bill of lading, and sensor status.
• 2: The center shall provide the interface with intermodal freight shippers to setup transportation for freight equipment. Inputs to this include information about the shipper, consignee, commodities, pick-up and drop-off locations for freight equipment. Outputs include information about the driver and commercial vehicle that will be transporting the freight.


• Private Fleet Vehicle Dispatch Systems - 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 Fleet Vehicle Dispatch Systems - ITS Security Support
• 1: The ITS Object shall obtain security policy information from the Cooperative Intelligent Transportation System Credentials Management System (CCMS).
• 2: The ITS Object shall request enrollment credentials from the CCMS.
• 3: The ITS Object shall obtain the CCMS' trust credentials.
• 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.


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


• Private Travelers Personal Computing Devices - Personal Map Management
• 1: The Personal Device shall obtain basemap updates from Centers.


• 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.
• 2: The personal information device shall receive rail crossing warning information.
• 3: The personal traveler interface shall provide traveler location information to transit vehicles.
• 5: The personal traveler interface shall provide the traveler with warnings about approaching vehicles.
• 6: The personal traveler interface shall provide the traveler with an indication that an approaching transit vehicle is the one they want to board based on their input trip itinerary.


• Rail Operations Centers - Center Map Management
• 1: The Center shall collect updates to basemaps from Map Update Systems .


• Rail Operations Centers - Center Permission Management
• 1: The Center shall manage the device permission request process on behalf of the devices it manages.
• 2: The Center shall acquire device identification information from ITS Objects it manages.
• 3: The Center shall request permissions for ITS Objects it manages from a center authorized to manage those permissions.
• 4: The Center shall request permissions for itself from a center authorized to manage those permissions.
• 5: The Center shall maintain the status of ITS Object permission requests.
• 6: The Center shall notify the ITS Object of the status of its permission request.
• 7: The Center shall accept permissions requests from ITS Object.


• Rail Operations Centers - 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.


• Rail Operations Centers - ITS Security Support
• 1: The ITS Object shall obtain security policy information from the Cooperative Intelligent Transportation System Credentials Management System (CCMS).
• 2: The ITS Object shall request enrollment credentials from the CCMS.
• 3: The ITS Object shall obtain the CCMS' trust credentials.
• 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.


• Railroad Operators Wayside Equipment - ITS Communications Support
• 3: The ITS Object shall include a mechanism for relaying messages received using one physical communications medium to other ITS Objects using that same medium.


• Railroad Operators Wayside 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


• Railroad Operators Wayside Equipment - ITS Security Support
• 1: The ITS Object shall obtain security policy information from the Cooperative Intelligent Transportation System Credentials Management System (CCMS).
• 2: The ITS Object shall request enrollment credentials from the CCMS.
• 3: The ITS Object shall obtain the CCMS' trust credentials.
• 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.


• SUNTRAN Transit Dispatch Center - Center Map Management
• 1: The Center shall collect updates to basemaps from Map Update Systems .


• SUNTRAN Transit Dispatch Center - Center Permission Management
• 1: The Center shall manage the device permission request process on behalf of the devices it manages.
• 2: The Center shall acquire device identification information from ITS Objects it manages.
• 3: The Center shall request permissions for ITS Objects it manages from a center authorized to manage those permissions.
• 4: The Center shall request permissions for itself from a center authorized to manage those permissions.
• 5: The Center shall maintain the status of ITS Object permission requests.
• 6: The Center shall notify the ITS Object of the status of its permission request.
• 7: The Center shall accept permissions requests from ITS Object.


• SUNTRAN Transit Dispatch 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.


• SUNTRAN Transit Dispatch Center - ITS Security Support
• 1: The ITS Object shall obtain security policy information from the Cooperative Intelligent Transportation System Credentials Management System (CCMS).
• 2: The ITS Object shall request enrollment credentials from the CCMS.
• 3: The ITS Object shall obtain the CCMS' trust credentials.
• 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.


• SUNTRAN Transit Dispatch 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.
• 2: The center shall send requests for priority along routes or at intersections to traffic management.


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


• SUNTRAN Transit Vehicles - ITS Security Support
• 1: The ITS Object shall obtain security policy information from the Cooperative Intelligent Transportation System Credentials Management System (CCMS).
• 2: The ITS Object shall request enrollment credentials from the CCMS.
• 3: The ITS Object shall obtain the CCMS' trust credentials.
• 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.


• SUNTRAN 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.
• 3: The transit vehicle shall send the schedule deviation data and status of priority requests to the transit vehicle operator and provide the capability for the transit vehicle operator to control the priority system.
• 4: The transit vehicle shall prevent a priority request from being sent when the transit vehicle cannot use the priority (e.g., when the transit vehicle makes a passenger stop on the approach to an intersection).


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


• Vehicle - ITS Security Support
• 1: The ITS Object shall obtain security policy information from the Cooperative Intelligent Transportation System Credentials Management System (CCMS).
• 2: The ITS Object shall request enrollment credentials from the CCMS.
• 3: The ITS Object shall obtain the CCMS' trust credentials.
• 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.


• Vehicle - 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.
• 7: The vehicle shall receive warnings, informational road signs, traffic meters, and signals provided by infrastructure devices.


• Vehicle - Vehicle Control Automation
• 1: The vehicle shall monitor the area behind and in front of the vehicle to determine the proximity of other objects to the vehicle.
• 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.
• 5: The Vehicle shall provide its location with lane-level accuracy to on-board control automation applications.
• 6: 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, roadway characteristics, 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.
• 8: The vehicle shall provide an interface through which a vehicle driver can initiate, monitor and terminate automatic control of the vehicle.


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


• Vehicle - Vehicle Map Management
• 1: The Vehicle shall make basemap, roadway geometry, intersection geometry and parking facility geometry information available to other onboard vehicle applications.
• 10: The Vehicle shall obtain intersection geometry information from Centers.
• 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.


• Vehicle - Vehicle Rail Crossing Warning
• 1: Vehicle shall receive alerts of trains entering HRIs and provide warnings to drivers regarding the trains.


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

Standards:

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

Project Operational Concepts:

Roles and Responsibilities

• Private Commercial Vehicle and Fleet Operators
• Provide commercial vehicles with the ability to communicate with infrastructure for freight signal priority.
• Provide fleet capability for freight signal priority.


• FDOT CO
• Provide security services for I-75 FRAME.


• FDOT District 5
• Collect vehicle probe information using roadside equipment and calculate travel times.
• Control and coordinate highway traffic, including reversible lanes, with lane control signals on FDOT freeways.
• Coordinate emergency plans, incident responses, and resources with the county EOC/warning points.
• Coordinate emergency traffic signal control with the county EOC/warning points.
• Coordinate evacuation and reentry plans with the county EOC/warning points.
• Coordinate incident response and incident reports with the county sheriff, county fire/EMS agencies, county EOC, local police/fire/EMS agencies, the FHP, and other public safety agencies.
• Coordinate maintenance resources for incident response with the FDOT District 7 maintenance system, and county and city public works departments (PWDs).
• Coordinate the Vehicle Infrastructure Integration (VII) initiative with private vehicles using FDOT District 5 field equipment.
• Coordinate threat information, such as surveillance or sensor data, with local traffic and emergency management agencies.
• Coordinate traffic information and traffic control with CFX, Brevard, Orange, Osceola, and Volusia counties; and the cities of Daytona Beach and Orlando.
• Coordinate traffic information and traffic control with other FDOT District TMCs.
• Coordinate traffic information with the Seminole County Traffic Action Center (SEMTAC); Volusia County transportation management center (TMC); the City of Orlando; Orange and Brevard counties; and other FDOT District TMCs.
• Develop and coordinate regional emergency plans; evacuation and reentry plans; and disaster management plans with FDOT District 5 and other Districts.
• Dispatch FDOT District 5 and CFX Road Ranger Service Patrols.
• Monitor secure area sensors and report alert notifications to regional ISPs, FDOT maintenance systems, and regional emergency management agencies.
• Monitor secure area sensors and report alert notifications to the FDOT District 5 PIO, FDOT maintenance systems, and regional emergency management agencies.
• Obtain traffic images and traffic flow data from closed-circuit televisions (CCTVs) and field sensors, and maintain operational control of its own field equipment.
• Operate select traffic signal systems in the FDOT District 5 region.
• Operate signalization and control of reversible lanes in coordination with FDOT District 7 and the Florida Highway Patrol (FHP) for evacuation purposes.
• Participate in incident response, coordination, and reporting for the regional incident and mutual aid network.
• Perform network surveillance for detection and verification of incidents on freeways, and send traffic/incident information and traffic images to county fire/EMS/sheriff agencies, the FHP, the county EOC, and local fire/EMS/police.
• Provide camera coverage for FDOT District 5 roadways.
• Provide incident information to travelers using traffic information devices on freeways, such as DMS devices and highway advisory radio (HAR) broadcasts, and through local information service providers (ISPs) and Web sites.
• Provide parking demand information to private/public parking facilities to determine parking capacity and traffic implications at the facility.
• Provide traffic information and road network conditions to local emergency management providers, including local fire/EMS/police agencies, the FHP, and the county sheriff.
• Provide traffic information and road network conditions to LYNX transit operations.
• Provide traffic information in a coordination effort to the FDOT statewide center-to-center (C2C) information network and the central Florida TMC information network.
• Provide traffic information reports to other agencies, including other FDOT District TMCs.
• Provide traffic information to travelers using CFX DMS devices.
• Provide traffic information to travelers using FDOT DMS devices.
• Provide traffic information to travelers using Florida 511, private companies, and the media.
• Receive America’s Missing: Broadcast Emergency Response (AMBER) Alerts and other wide area alert information from the FDLE.
• Receive incident information, incident response status, and resource requests from the county EOC/warning points and from the FDOT District 5 EOC.


• City of Ocala
• Coordinate emergency plans, incident responses, and resources with the county EOC/warning points.
• Coordinate emergency traffic signal control with the county EOC/warning points.
• Coordinate evacuation and reentry plans with the county EOC/warning points.
• Coordinate HRI signal adjustments, and provide track status information (e.g., blockage) to rail operators and local traffic operations.
• Obtain traffic images and traffic flow data from CCTVs and field sensors, and maintain operational control of its own field equipment.
• Operate traffic signal systems, including CCTVs, signals, and sensors, for the City of Ocala.
• Provide camera coverage for Ocala city streets.
• Provide emergency signal preemption for county and local fire/EMS agencies.
• Provide parking demand information to private/public parking facilities to determine parking capacity and traffic implications at the facility.
• Provide traffic information in a coordination effort to Florida 511
• Provide traffic information to travelers using City of Ocala DMS devices.
• Provide traffic information to travelers using private companies; county and city public information systems; and the media.
• Receive AMBER Alerts and other wide area alert information from FDLE.


• SUNTRAN
• Provide transit signal priority.
• Provide transit vehicle tracking to support TSP.