FDOT District 5 I-4 FRAME

Project Description: Interstate 4 (I–4) Florida's Regional Advanced Mobility Elements (FRAME) is a regional, intercity integrated corridor management (ICM) project running from the Central Business District in Tampa to the southwest side of Orlando at the Florida Turnpike. I–4 and the other ICM routes cross four (4) counties: Hillsborough, Polk, Osceola, and Orange. This District 5 project covers the sections in Osceola and Orange Counties.

Project Status: Planned

Project Stakeholders:

• City of Orlando
• Counties and Cities
• FDOT CO
• FDOT District 5
• LYNX
• Orange County
• Osceola County
• Private Commercial Vehicle and Fleet Operators
• Private Weather Information Providers
• Travelers

Project Service Packages:

• SU02: Core Authorization (FDOT District 5 I-4 FRAME Project)
• SU04: Map Management (FDOT District 5 I-4 FRAME Project)
• SU08: Security and Credentials Management (FDOT District 5 I-4 FRAME Project)
• TM03: Traffic Signal Control (FDOT District 5 I-4 FRAME Project)
• TM04: Connected Vehicle Traffic Signal System (FDOT District 5 I-4 FRAME Project)
• TM06: Traffic Information Dissemination (FDOT District 5 I-4 FRAME Project)
• TM08: Traffic Incident Management System (FDOT District 5 I-4 FRAME Project)
• TI01: Broadcast Traveler Information (FDOT District 5 I-4 FRAME Project)
• SU09: Device Certification and Enrollment (FDOT District 5 I-4 FRAME Project)
• SU01: Connected Vehicle System Monitoring and Management (FDOT District 5 I-4 FRAME)
• CVO06: Freight Signal Priority (FDOT District 5 I-4 FRAME)
• TM12: Dynamic Roadway Warning (FDOT District 5 I-4 FRAME)
• TM17: Speed Warning and Enforcement (FDOT District 5 I-4 FRAME)
• MC06: Work Zone Management (FDOT District 5 I-4 FRAME )
• TM25: Wrong Way Vehicle Detection and Warning (FDOT District 5 I-4 FRAME)
• TI03: En-Route Guidance (FDOT District 5 I-4 FRAME)
• VS08: Queue Warning (FDOT District 5 I-4 FRAME)
• VS09: Reduced Speed Zone Warning / Lane Closure (FDOT District 5 I-4 FRAME)
• PS07: Incident Scene Safety Monitoring (FDOT District 5 I-4 FRAME)
• TM14: Advanced Railroad Grade Crossing (FDOT District 5 I-4 FRAME)
• PT09: Transit Signal Priority (FDOT District 5 I-4 FRAME)
• VS12: Vulnerable Road User Safety (FDOT District 5 I-4 FRAME)
• VS13: Intersection Safety Warning and Collision Avoidance (FDOT District 5 I-4 FRAME)
• TM01: Infrastructure-Based Traffic Surveillance (FDOT District 5 I-4 FRAME)

Project Information Flows:

Information Flow	Source Element	Destination Element	Status
communications signature	Commercial Vehicle	FDOT District 5 Field Equipment	Planned
communications signature	Commercial Vehicle	Orange County Field Equipment	Planned
communications signature	Commercial Vehicle	Osceola County Field Equipment	Planned
communications signature	Vehicle	Osceola County Field Equipment	Planned
equipment control commands	CAV Authorizing Center	City of Orlando CAV Field Equipment	Planned
equipment control commands	CAV Authorizing Center	FDOT District 5 CAV Field Equipment	Planned
equipment control commands	CAV Authorizing Center	Orange County CAV Field Equipment	Planned
equipment control commands	CAV Authorizing Center	Osceola County CAV Field Equipment	Planned
high resolution signal controller data_ud	FDOT District 5 Field Equipment	FDOT District 5 RTMC	Planned
high resolution signal controller data_ud	Orange County Field Equipment	Orange County TMC	Planned
high resolution signal controller data_ud	Osceola County Field Equipment	Osceola County Traffic Operations Center	Planned
incident information for public	City of Orlando TMC	FL511	Planned
incident information for public	FDOT District 5 RTMC	FL511	Planned
incident information for public	Orange County TMC	FL511	Planned
incident information for public	Osceola County Traffic Operations Center	FL511	Planned
incident scene safety application info	FDOT District 5 RTMC	FDOT District 5 CAV Field Equipment	Planned
incident scene safety application status	FDOT District 5 CAV Field Equipment	FDOT District 5 RTMC	Planned
interactive traveler information	FL511	Private Travelers Personal Computing Devices	Planned
intersection geometry	CAV-ITS Map Update System	City of Orlando CAV Field Equipment	Planned
intersection geometry	CAV-ITS Map Update System	City of Orlando TMC	Planned
intersection geometry	CAV-ITS Map Update System	FDOT District 5 CAV Field Equipment	Planned
intersection geometry	CAV-ITS Map Update System	FDOT District 5 RTMC	Planned
intersection geometry	CAV-ITS Map Update System	Orange County CAV Field Equipment	Planned
intersection geometry	CAV-ITS Map Update System	Orange County TMC	Planned
intersection geometry	CAV-ITS Map Update System	Osceola County CAV Field Equipment	Planned
intersection geometry	CAV-ITS Map Update System	Osceola County Traffic Operations Center	Planned
intersection geometry	City of Orlando CAV Field Equipment	Commercial Vehicle	Planned
intersection geometry	City of Orlando CAV Field Equipment	Private Travelers Personal Computing Devices	Planned
intersection geometry	FDOT District 5 CAV Field Equipment	Commercial Vehicle	Planned
intersection geometry	Orange County CAV Field Equipment	Commercial Vehicle	Planned
intersection geometry	Orange County CAV Field Equipment	Private Travelers Personal Computing Devices	Planned
intersection geometry	Osceola County CAV Field Equipment	Commercial Vehicle	Planned
intersection geometry	Osceola County CAV Field Equipment	Private Travelers Personal Computing Devices	Planned
intersection infringement info	City of Orlando Field Equipment	City of Orlando CAV Field Equipment	Planned
intersection management application info	City of Orlando TMC	City of Orlando CAV Field Equipment	Planned
intersection management application info	FDOT District 5 RTMC	FDOT District 5 CAV Field Equipment	Planned
intersection management application info	Orange County TMC	Orange County CAV Field Equipment	Planned
intersection management application info	Osceola County Traffic Operations Center	Osceola County CAV Field Equipment	Planned
intersection management application status	City of Orlando CAV Field Equipment	City of Orlando TMC	Planned
intersection management application status	FDOT District 5 CAV Field Equipment	FDOT District 5 RTMC	Planned
intersection management application status	Orange County CAV Field Equipment	Orange County TMC	Planned
intersection management application status	Osceola County CAV Field Equipment	Osceola County Traffic Operations Center	Planned
intersection safety application info	City of Orlando TMC	City of Orlando CAV Field Equipment	Planned
intersection safety application info	Orange County TMC	Orange County CAV Field Equipment	Planned
intersection safety application info	Osceola County Traffic Operations Center	Osceola County CAV Field Equipment	Planned
intersection safety application status	City of Orlando CAV Field Equipment	City of Orlando TMC	Planned
intersection safety application status	Orange County CAV Field Equipment	Orange County TMC	Planned
intersection safety application status	Osceola County CAV Field Equipment	Osceola County Traffic Operations Center	Planned
intersection safety warning	Osceola County CAV Field Equipment	Private Travelers Personal Computing Devices	Planned
intersection status	City of Orlando CAV Field Equipment	Commercial Vehicle	Planned
intersection status	City of Orlando CAV Field Equipment	Private Travelers Personal Computing Devices	Planned
intersection status	FDOT District 5 CAV Field Equipment	Commercial Vehicle	Planned
intersection status	Orange County CAV Field Equipment	Commercial Vehicle	Planned
intersection status	Orange County CAV Field Equipment	LYNX Transit Vehicles	Planned
intersection status	Orange County CAV Field Equipment	Private Travelers Personal Computing Devices	Planned
intersection status	Orange County Field Equipment	LYNX Transit Vehicles	Planned
intersection status	Osceola County CAV Field Equipment	Commercial Vehicle	Planned
intersection status	Osceola County CAV Field Equipment	LYNX Transit Vehicles	Planned
intersection status	Osceola County CAV Field Equipment	Private Travelers Personal Computing Devices	Planned
local signal preemption request	Orange County Fire Vehicles	Orange County CAV Field Equipment	Planned
local signal preemption request	Orange County Fire Vehicles	Orange County Field Equipment	Planned
local signal priority request	Commercial Vehicle	City of Orlando CAV Field Equipment	Planned
local signal priority request	Commercial Vehicle	FDOT District 5 CAV Field Equipment	Planned
local signal priority request	Commercial Vehicle	FDOT District 5 Field Equipment	Planned
local signal priority request	Commercial Vehicle	Orange County CAV Field Equipment	Planned
local signal priority request	Commercial Vehicle	Orange County Field Equipment	Planned
local signal priority request	Commercial Vehicle	Osceola County CAV Field Equipment	Planned
local signal priority request	Commercial Vehicle	Osceola County Field Equipment	Planned
local signal priority request	LYNX Transit Vehicles	City of Orlando CAV Field Equipment	Planned
local signal priority request	LYNX Transit Vehicles	City of Orlando Field Equipment	Planned
local signal priority request	LYNX Transit Vehicles	Orange County CAV Field Equipment	Planned
local signal priority request	LYNX Transit Vehicles	Orange County Field Equipment	Planned
local signal priority request	LYNX Transit Vehicles	Osceola County CAV Field Equipment	Planned
local signal priority request	LYNX Transit Vehicles	Osceola County Field Equipment	Planned
map update notification	City of Orlando TMC	CAV-ITS Map Update System	Planned
map update notification	FDOT District 5 RTMC	CAV-ITS Map Update System	Planned
map update notification	Orange County TMC	CAV-ITS Map Update System	Planned
map update notification	Osceola County Traffic Operations Center	CAV-ITS Map Update System	Planned
map updates	CAV-ITS Map Update System	City of Orlando CAV Field Equipment	Planned
map updates	CAV-ITS Map Update System	City of Orlando TMC	Planned
map updates	CAV-ITS Map Update System	FDOT District 5 CAV Field Equipment	Planned
map updates	CAV-ITS Map Update System	FDOT District 5 RTMC	Planned
map updates	CAV-ITS Map Update System	Orange County CAV Field Equipment	Planned
map updates	CAV-ITS Map Update System	Orange County TMC	Planned
map updates	CAV-ITS Map Update System	Osceola County CAV Field Equipment	Planned
map updates	CAV-ITS Map Update System	Osceola County Traffic Operations Center	Planned
misbehavior report	City of Orlando CAV Field Equipment	FDOT SCMS	Planned
misbehavior report	City of Orlando TMC	FDOT SCMS	Planned
misbehavior report	Commercial Vehicle	FDOT SCMS	Planned
misbehavior report	FDOT District 5 CAV Field Equipment	FDOT SCMS	Planned
misbehavior report	FDOT District 5 RTMC	FDOT SCMS	Planned
misbehavior report	Orange County CAV Field Equipment	FDOT SCMS	Planned
misbehavior report	Orange County TMC	FDOT SCMS	Planned
misbehavior report	Osceola County CAV Field Equipment	FDOT SCMS	Planned
misbehavior report	Osceola County Traffic Operations Center	FDOT SCMS	Planned
passive vehicle monitoring control	FDOT District 5 RTMC	FDOT District 5 Field Equipment	Planned
passive vehicle monitoring control	Orange County TMC	Orange County Field Equipment	Planned
passive vehicle monitoring control	Osceola County Traffic Operations Center	Osceola County Field Equipment	Planned
passive vehicle monitoring data	Orange County Field Equipment	Orange County TMC	Planned
passive vehicle monitoring data	Osceola County Field Equipment	Osceola County Traffic Operations Center	Planned
personal crossing safety information	City of Orlando CAV Field Equipment	Private Travelers Personal Computing Devices	Planned
personal crossing safety information	Orange County CAV Field Equipment	Private Travelers Personal Computing Devices	Planned
personal crossing safety information	Osceola County CAV Field Equipment	Private Travelers Personal Computing Devices	Planned
personal location	Private Travelers Personal Computing Devices	City of Orlando CAV Field Equipment	Planned
personal location	Private Travelers Personal Computing Devices	FDOT District 5 CAV Field Equipment	Planned
personal location	Private Travelers Personal Computing Devices	Orange County CAV Field Equipment	Planned
personal location	Private Travelers Personal Computing Devices	Osceola County CAV Field Equipment	Planned
personal signal service request	Private Travelers Personal Computing Devices	City of Orlando CAV Field Equipment	Planned
personal signal service request	Private Travelers Personal Computing Devices	Orange County CAV Field Equipment	Planned
personal signal service request	Private Travelers Personal Computing Devices	Osceola County CAV Field Equipment	Planned
queue warning application information	City of Orlando TMC	City of Orlando CAV Field Equipment	Planned
queue warning application information	FDOT District 5 RTMC	FDOT District 5 CAV Field Equipment	Planned
queue warning application information	Orange County TMC	Orange County CAV Field Equipment	Planned
queue warning application information	Osceola County Traffic Operations Center	Osceola County CAV Field Equipment	Planned
queue warning application status	FDOT District 5 CAV Field Equipment	FDOT District 5 RTMC	Planned
queue warning application status	Orange County CAV Field Equipment	Orange County TMC	Planned
rail crossing application info	City of Orlando TMC	City of Orlando CAV Field Equipment	Planned
rail crossing application info	FDOT District 5 RTMC	FDOT District 5 CAV Field Equipment	Planned
rail crossing application info	Orange County TMC	Orange County CAV Field Equipment	Planned
rail crossing application info	Osceola County Traffic Operations Center	Osceola County CAV Field Equipment	Planned
rail crossing application status	City of Orlando CAV Field Equipment	City of Orlando TMC	Planned
rail crossing application status	FDOT District 5 CAV Field Equipment	FDOT District 5 RTMC	Planned
rail crossing application status	Orange County CAV Field Equipment	Orange County TMC	Planned
rail crossing application status	Osceola County CAV Field Equipment	Osceola County Traffic Operations Center	Planned
road network conditions	City of Orlando TMC	FL511	Planned
road network conditions	FDOT District 5 RTMC	FL511	Planned
road network conditions	Orange County TMC	FL511	Planned
road network conditions	Osceola County Traffic Operations Center	FL511	Planned
road network traffic situation data	FL511	City of Orlando TMC	Planned
road network traffic situation data	FL511	FDOT District 5 RTMC	Planned
road network traffic situation data	FL511	Orange County TMC	Planned
road network traffic situation data	FL511	Osceola County Traffic Operations Center	Planned
road weather information	FDOT District 5 RTMC	FL511	Planned
road weather information	FDOT District 5 RTMC	Weather Information Providers	Planned
roadway advisory radio data	FDOT District 5 RTMC	FDOT District 5 Field Equipment	Planned
roadway advisory radio status	FDOT District 5 Field Equipment	FDOT District 5 RTMC	Planned
roadway dynamic signage data	City of Orlando TMC	City of Orlando Field Equipment	Planned
roadway dynamic signage data	FDOT District 5 RTMC	FDOT District 5 Field Equipment	Planned
roadway dynamic signage data	Orange County TMC	Orange County Field Equipment	Planned
roadway dynamic signage data	Osceola County Traffic Operations Center	Osceola County Field Equipment	Planned
roadway dynamic signage status	City of Orlando Field Equipment	City of Orlando TMC	Planned
roadway dynamic signage status	FDOT District 5 Field Equipment	FDOT District 5 RTMC	Planned
roadway dynamic signage status	Orange County Field Equipment	Orange County TMC	Planned
roadway dynamic signage status	Osceola County Field Equipment	Osceola County Traffic Operations Center	Planned
roadway geometry	CAV-ITS Map Update System	City of Orlando CAV Field Equipment	Planned
roadway geometry	CAV-ITS Map Update System	FDOT District 5 CAV Field Equipment	Planned
roadway geometry	CAV-ITS Map Update System	Orange County CAV Field Equipment	Planned
roadway geometry	CAV-ITS Map Update System	Osceola County CAV Field Equipment	Planned
roadway warning system control	City of Orlando TMC	City of Orlando CAV Field Equipment	Planned
RSE application information	CAV Authorizing Center	City of Orlando CAV Field Equipment	Planned
RSE application information	CAV Authorizing Center	FDOT District 5 CAV Field Equipment	Planned
RSE application information	CAV Authorizing Center	Orange County CAV Field Equipment	Planned
RSE application information	CAV Authorizing Center	Osceola County CAV Field Equipment	Planned
RSE application install/upgrade	CAV Authorizing Center	City of Orlando CAV Field Equipment	Planned
RSE application install/upgrade	CAV Authorizing Center	FDOT District 5 CAV Field Equipment	Planned
RSE application install/upgrade	CAV Authorizing Center	Orange County CAV Field Equipment	Planned
RSE application install/upgrade	CAV Authorizing Center	Osceola County CAV Field Equipment	Planned
RSE application status	City of Orlando CAV Field Equipment	CAV Authorizing Center	Planned
RSE application status	City of Orlando CAV Field Equipment	City of Orlando TMC	Planned
RSE application status	FDOT District 5 CAV Field Equipment	CAV Authorizing Center	Planned
RSE application status	FDOT District 5 CAV Field Equipment	FDOT District 5 RTMC	Planned
RSE application status	Orange County CAV Field Equipment	CAV Authorizing Center	Planned
RSE application status	Orange County CAV Field Equipment	Orange County TMC	Planned
RSE application status	Osceola County CAV Field Equipment	CAV Authorizing Center	Planned
RSE application status	Osceola County CAV Field Equipment	Osceola County Traffic Operations Center	Planned
security credential revocations	FDOT SCMS	City of Orlando CAV Field Equipment	Planned
security credential revocations	FDOT SCMS	City of Orlando TMC	Planned
security credential revocations	FDOT SCMS	Commercial Vehicle	Planned
security credential revocations	FDOT SCMS	FDOT District 5 CAV Field Equipment	Planned
security credential revocations	FDOT SCMS	FDOT District 5 RTMC	Planned
security credential revocations	FDOT SCMS	Orange County CAV Field Equipment	Planned
security credential revocations	FDOT SCMS	Orange County TMC	Planned
security credential revocations	FDOT SCMS	Osceola County CAV Field Equipment	Planned
security credential revocations	FDOT SCMS	Osceola County Traffic Operations Center	Planned
security credentials	FDOT SCMS	City of Orlando CAV Field Equipment	Planned
security credentials	FDOT SCMS	City of Orlando TMC	Planned
security credentials	FDOT SCMS	Commercial Vehicle	Planned
security credentials	FDOT SCMS	FDOT District 5 CAV Field Equipment	Planned
security credentials	FDOT SCMS	FDOT District 5 RTMC	Planned
security credentials	FDOT SCMS	Orange County CAV Field Equipment	Planned
security credentials	FDOT SCMS	Orange County TMC	Planned
security credentials	FDOT SCMS	Osceola County CAV Field Equipment	Planned
security credentials	FDOT SCMS	Osceola County Traffic Operations Center	Planned
security policy and networking information	FDOT SCMS	City of Orlando CAV Field Equipment	Planned
security policy and networking information	FDOT SCMS	City of Orlando TMC	Planned
security policy and networking information	FDOT SCMS	Commercial Vehicle	Planned
security policy and networking information	FDOT SCMS	FDOT District 5 CAV Field Equipment	Planned
security policy and networking information	FDOT SCMS	FDOT District 5 RTMC	Planned
security policy and networking information	FDOT SCMS	Orange County CAV Field Equipment	Planned
security policy and networking information	FDOT SCMS	Orange County TMC	Planned
security policy and networking information	FDOT SCMS	Osceola County CAV Field Equipment	Planned
security policy and networking information	FDOT SCMS	Osceola County Traffic Operations Center	Planned
signal control commands	City of Orlando TMC	City of Orlando Field Equipment	Planned
signal control commands	FDOT District 5 RTMC	FDOT District 5 Field Equipment	Planned
signal control commands	Orange County TMC	Orange County Field Equipment	Planned
signal control commands	Osceola County Traffic Operations Center	Osceola County Field Equipment	Planned
signal control device configuration	City of Orlando TMC	City of Orlando Field Equipment	Planned
signal control device configuration	FDOT District 5 RTMC	FDOT District 5 Field Equipment	Planned
signal control device configuration	Orange County TMC	Orange County Field Equipment	Planned
signal control device configuration	Osceola County Traffic Operations Center	Osceola County Field Equipment	Planned
signal control plans	City of Orlando TMC	City of Orlando Field Equipment	Planned
signal control plans	FDOT District 5 RTMC	FDOT District 5 Field Equipment	Planned
signal control plans	Orange County TMC	Orange County Field Equipment	Planned
signal control plans	Osceola County Traffic Operations Center	Osceola County Field Equipment	Planned
signal control status	City of Orlando Field Equipment	City of Orlando TMC	Planned
signal control status	FDOT District 5 Field Equipment	FDOT District 5 RTMC	Planned
signal control status	Orange County Field Equipment	Orange County TMC	Planned
signal control status	Osceola County Field Equipment	Osceola County Traffic Operations Center	Planned
signal fault data	City of Orlando Field Equipment	City of Orlando TMC	Planned
signal fault data	FDOT District 5 Field Equipment	FDOT District 5 RTMC	Planned
signal fault data	Orange County Field Equipment	Orange County TMC	Planned
signal fault data	Osceola County Field Equipment	Osceola County Traffic Operations Center	Planned
signal preemption request	City of Orlando CAV Field Equipment	City of Orlando Field Equipment	Planned
signal preemption request	City of Orlando Field Equipment	City of Orlando CAV Field Equipment	Planned
signal preemption request	FDOT District 5 CAV Field Equipment	FDOT District 5 Field Equipment	Planned
signal preemption request	Orange County CAV Field Equipment	Orange County Field Equipment	Planned
signal preemption request	Osceola County CAV Field Equipment	Osceola County Field Equipment	Planned
signal priority service request	City of Orlando CAV Field Equipment	City of Orlando Field Equipment	Planned
signal priority service request	City of Orlando Field Equipment	City of Orlando CAV Field Equipment	Planned
signal priority service request	FDOT District 5 CAV Field Equipment	FDOT District 5 Field Equipment	Planned
signal priority service request	Orange County CAV Field Equipment	Orange County Field Equipment	Planned
signal priority service request	Osceola County CAV Field Equipment	Osceola County Field Equipment	Planned
signal priority status	City of Orlando CAV Field Equipment	LYNX Transit Vehicles	Planned
signal priority status	City of Orlando Field Equipment	LYNX Transit Vehicles	Planned
signal priority status	FDOT District 5 CAV Field Equipment	Commercial Vehicle	Planned
signal priority status	Orange County CAV Field Equipment	Commercial Vehicle	Planned
signal priority status	Orange County CAV Field Equipment	LYNX Transit Vehicles	Planned
signal priority status	Orange County Field Equipment	LYNX Transit Vehicles	Planned
signal priority status	Osceola County CAV Field Equipment	Commercial Vehicle	Planned
signal priority status	Osceola County CAV Field Equipment	LYNX Transit Vehicles	Planned
signal priority status	Osceola County Field Equipment	LYNX Transit Vehicles	Planned
signal system configuration	City of Orlando TMC	City of Orlando Field Equipment	Planned
signal system configuration	Orange County TMC	Orange County Field Equipment	Planned
signal system configuration	Osceola County Traffic Operations Center	Osceola County Field Equipment	Planned
speed warning application info	City of Orlando TMC	City of Orlando CAV Field Equipment	Planned
speed warning application info	County and City Roadway Maintenance and Construction Systems	City of Orlando CAV Field Equipment	Planned
speed warning application info	County and City Roadway Maintenance and Construction Systems	FDOT District 5 CAV Field Equipment	Planned
speed warning application info	FDOT District 5 RTMC	FDOT District 5 CAV Field Equipment	Planned
speed warning application info	Orange County TMC	Orange County CAV Field Equipment	Planned
speed warning application status	FDOT District 5 CAV Field Equipment	County and City Roadway Maintenance and Construction Systems	Planned
speed warning application status	FDOT District 5 CAV Field Equipment	FDOT District 5 RTMC	Planned
speed warning application status	Orange County CAV Field Equipment	Orange County TMC	Planned
traffic control information	City of Orlando TMC	FL511	Planned
traffic control information	FDOT District 5 RTMC	FL511	Planned
traffic control information	Orange County TMC	FL511	Planned
traffic control information	Osceola County Traffic Operations Center	FL511	Planned
traffic detector control	City of Orlando TMC	City of Orlando Field Equipment	Planned
traffic detector control	FDOT District 5 RTMC	FDOT District 5 Field Equipment	Planned
traffic detector control	Orange County TMC	Orange County Field Equipment	Planned
traffic detector control	Osceola County Traffic Operations Center	Osceola County Field Equipment	Planned
traffic detector data	City of Orlando Field Equipment	City of Orlando TMC	Planned
traffic detector data	FDOT District 5 Field Equipment	FDOT District 5 RTMC	Planned
traffic detector data	Orange County Field Equipment	Orange County TMC	Planned
traffic detector data	Osceola County Field Equipment	Osceola County Traffic Operations Center	Planned
traffic images	City of Orlando Field Equipment	City of Orlando TMC	Planned
traffic images	City of Orlando TMC	FL511	Planned
traffic images	FDOT District 5 Field Equipment	FDOT District 5 RTMC	Planned
traffic images	FDOT District 5 RTMC	FL511	Planned
traffic images	Orange County Field Equipment	Orange County TMC	Planned
traffic images	Orange County TMC	FL511	Planned
traffic images	Osceola County Field Equipment	Osceola County Traffic Operations Center	Planned
traffic images	Osceola County Traffic Operations Center	FL511	Planned
traffic situation data	City of Orlando CAV Field Equipment	City of Orlando Field Equipment	Planned
traffic situation data	City of Orlando CAV Field Equipment	City of Orlando TMC	Planned
traffic situation data	City of Orlando Field Equipment	City of Orlando TMC	Planned
traffic situation data	FDOT District 5 CAV Field Equipment	FDOT District 5 Field Equipment	Planned
traffic situation data	FDOT District 5 CAV Field Equipment	FDOT District 5 RTMC	Planned
traffic situation data	Orange County CAV Field Equipment	Orange County Field Equipment	Planned
traffic situation data	Orange County CAV Field Equipment	Orange County TMC	Planned
traffic situation data	Osceola County CAV Field Equipment	Osceola County Field Equipment	Planned
traffic situation data	Osceola County CAV Field Equipment	Osceola County Traffic Operations Center	Planned
traffic situation data	Osceola County Field Equipment	Osceola County Traffic Operations Center	Planned
transportation system status	FDOT District 5 RTMC	FL511	Planned
traveler alerts	FL511	Vehicle	Planned
traveler information application status	FDOT District 5 CAV Field Equipment	FDOT District 5 RTMC	Planned
traveler request	Private Travelers Personal Computing Devices	FL511	Planned
vehicle location and motion	Commercial Vehicle	City of Orlando CAV Field Equipment	Planned
vehicle location and motion	Commercial Vehicle	FDOT District 5 CAV Field Equipment	Planned
vehicle location and motion	Commercial Vehicle	Orange County CAV Field Equipment	Planned
vehicle location and motion	Commercial Vehicle	Osceola County CAV Field Equipment	Planned
vehicle location and motion	LYNX Transit Vehicles	City of Orlando CAV Field Equipment	Planned
vehicle location and motion	LYNX Transit Vehicles	Orange County CAV Field Equipment	Planned
vehicle location and motion	Orange County Fire Vehicles	Orange County Field Equipment	Planned
vehicle location and motion	Vehicle	City of Orlando CAV Field Equipment	Planned
vehicle location and motion	Vehicle	FDOT District 5 CAV Field Equipment	Planned
vehicle location and motion	Vehicle	Orange County CAV Field Equipment	Planned
vehicle location and motion	Vehicle	Orange County Field Equipment	Planned
vehicle location and motion	Vehicle	Osceola County CAV Field Equipment	Planned
vehicle location and motion for surveillance	Vehicle	FDOT District 5 Field Equipment	Planned
vehicle location data for mapping	City of Orlando CAV Field Equipment	CAV-ITS Map Update System	Planned
vehicle location data for mapping	FDOT District 5 CAV Field Equipment	CAV-ITS Map Update System	Planned
vehicle location data for mapping	Orange County CAV Field Equipment	CAV-ITS Map Update System	Planned
vehicle location data for mapping	Osceola County CAV Field Equipment	CAV-ITS Map Update System	Planned
vehicle signage application info	City of Orlando TMC	City of Orlando CAV Field Equipment	Planned
vehicle signage application info	County and City Roadway Maintenance and Construction Systems	FDOT District 5 CAV Field Equipment	Planned
vehicle signage application info	County and City Roadway Maintenance and Construction Systems	Orange County CAV Field Equipment	Planned
vehicle signage application info	County and City Roadway Maintenance and Construction Systems	Osceola County CAV Field Equipment	Planned
vehicle signage application info	FDOT District 5 RTMC	FDOT District 5 CAV Field Equipment	Planned
vehicle signage application info	Orange County TMC	Orange County CAV Field Equipment	Planned
vehicle signage application info	Osceola County Traffic Operations Center	Osceola County CAV Field Equipment	Planned
vehicle signage application status	City of Orlando CAV Field Equipment	City of Orlando TMC	Planned
vehicle signage application status	City of Orlando CAV Field Equipment	County and City Roadway Maintenance and Construction Systems	Planned
vehicle signage application status	FDOT District 5 CAV Field Equipment	County and City Roadway Maintenance and Construction Systems	Planned
vehicle signage application status	FDOT District 5 CAV Field Equipment	FDOT District 5 RTMC	Planned
vehicle signage application status	Orange County CAV Field Equipment	County and City Roadway Maintenance and Construction Systems	Planned
vehicle signage application status	Orange County CAV Field Equipment	Orange County TMC	Planned
vehicle signage application status	Osceola County CAV Field Equipment	County and City Roadway Maintenance and Construction Systems	Planned
vehicle signage application status	Osceola County CAV Field Equipment	Osceola County Traffic Operations Center	Planned
vehicle signage data	City of Orlando CAV Field Equipment	Vehicle	Planned
vehicle signage data	FDOT District 5 CAV Field Equipment	Vehicle	Planned
vehicle signage data	Orange County CAV Field Equipment	Vehicle	Planned
vehicle signage data	Osceola County CAV Field Equipment	Vehicle	Planned
vehicle signage local data	City of Orlando Field Equipment	City of Orlando CAV Field Equipment	Planned
vehicle signage local data	FDOT District 5 Field Equipment	FDOT District 5 CAV Field Equipment	Planned
vehicle signage local data	Orange County Field Equipment	Orange County CAV Field Equipment	Planned
vehicle signage local data	Osceola County Field Equipment	Osceola County CAV Field Equipment	Planned
video surveillance control	City of Orlando TMC	City of Orlando Field Equipment	Planned
video surveillance control	FDOT District 5 RTMC	FDOT District 5 Field Equipment	Planned
video surveillance control	Orange County TMC	Orange County Field Equipment	Planned
video surveillance control	Osceola County Traffic Operations Center	Osceola County Field Equipment	Planned
weather information	Weather Information Providers	FDOT District 5 RTMC	Planned
weather information	Weather Information Providers	FL511	Planned
work zone warning device control	County and City Roadway Maintenance and Construction Systems	FDOT District 5 Field Equipment	Planned
work zone warning device control	County and City Roadway Maintenance and Construction Systems	Orange County Field Equipment	Planned
work zone warning device control	County and City Roadway Maintenance and Construction Systems	Osceola County Field Equipment	Planned
work zone warning status	City of Orlando Field Equipment	County and City Roadway Maintenance and Construction Systems	Planned
work zone warning status	FDOT District 5 Field Equipment	County and City Roadway Maintenance and Construction Systems	Planned
work zone warning status	Orange County Field Equipment	County and City Roadway Maintenance and Construction Systems	Planned
work zone warning status	Osceola County Field Equipment	County and City Roadway Maintenance and Construction Systems	Planned
wrong way vehicle detected	FDOT District 5 CAV Field Equipment	FDOT District 5 Field Equipment	Planned
wrong way vehicle detected	FDOT District 5 Field Equipment	FDOT District 5 CAV Field Equipment	Planned

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


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


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


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


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


• City of Orlando CAV Field Equipment - RSE Intersection Management
• 1: The field element shall communicate with passing vehicles to provide the current signal phase and timing information for all lanes and approaches at a signalized intersection.
• 2: The field element shall send the request for emergency vehicle preemption to a traffic signal controller that results in preemption of the current control plan and grants right-of-way to the requesting vehicle.
• 5: The field element shall receive transit signal priority requests from transit vehicles and forward to the traffic signal controller.
• 6: The field element shall receive emergency vehicle preemption requests from emergency vehicles and forward to the traffic signal controller.
• 9: The field element shall collect current signal phase and timing data from the traffic signal controller.


• City of Orlando CAV Field Equipment - RSE Intersection Safety
• 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.


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


• City of Orlando CAV Field Equipment - RSE Queue Warning
• 1: The field equipment shall communicate with the connected vehicles to gather real-time vehicle-collected data including vehicle speed, location and localized weather condition from the vehicle network.
• 2: The field equipment shall communicate queue response strategies (speed reduction, lane change, diversion recommendations) to the vehicle.


• City of Orlando CAV Field Equipment - RSE Speed Warning
• 2: The field element shall provide a warning to a vehicle whose speed has been detected to be over the posted speed limit.


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


• City of Orlando 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 Orlando Field Equipment - Roadway Advanced Rail Crossing
• 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 Orlando 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.


• City of Orlando Field Equipment - Roadway Passive Monitoring
• 1: The field element shall collect, process, and send data to the center to uniquely identify passing vehicles in order to support travel time measurement


• City of Orlando 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 Orlando Field Equipment - Roadway Signal Preemption
• 1: The field element shall respond to signal preemption requests from emergency vehicles.


• City of Orlando 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 Orlando Field Equipment - Roadway Work Zone Traffic Control
• 3: Under the control of field personnel within maintenance vehicles, the field element shall include driver information systems (such as dynamic messages signs and highway advisory radios) that advise drivers of activity around a work zone through which they are currently passing.


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


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


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


• City of Orlando 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 Orlando TMC - Center Connected Vehicle Infrastructure Management
• 1: The Center shall be capable of monitoring the operational status of Connected Vehicle Roadside Equipment applications.
• 2: The Center shall be capable of modifying the operational status of Connected Vehicle Roadside Equipment applications.
• 4: The Center shall be capable of modifying the operational status of Connected Vehicle Roadside Equipment.


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


• City of Orlando 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 Orlando 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 Orlando 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 Orlando TMC - MCM Incident Management
• 7: The maintenance center shall provide work zone activities affecting the road network during traffic incidents 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.


• City of Orlando TMC - MCM Work Zone Management
• 4: The center shall control traffic in work zones by providing remote control of dynamic message signs, highway advisory radio systems, gates, and barriers located in or near the work zone.


• City of Orlando TMC - TMC Advanced Rail Crossing Management
• 1: The center shall remotely control highway-rail intersection (HRI) equipment located in the field.
• 6: The center shall support 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 Orlando 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 Orlando TMC - TMC Incident Detection
• 1: The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.
• 2: The center shall collect and store traffic flow and image data from the field equipment to detect and verify incidents.
• 4: The center shall exchange incident and threat information with emergency management centers as well as maintenance and construction centers; including notification of existence of incident and expected severity, location, time and nature of incident.


• City of Orlando TMC - TMC Incident Dispatch Coordination
• 1: The center shall exchange alert information and status with emergency management centers. The information includes notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction for distribution to the public. The information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency, the effective time period, and information and instructions necessary for the public to respond to the alert. This may also identify specific information that should not be released to the public.
• 2: The center shall coordinate planning for incidents with emergency management centers - including pre-planning activities for disaster response, evacuation, and recovery operations.
• 5: The center shall share resources with allied agency centers to implement special traffic control measures, assist in clean up, verify an incident, etc. This may also involve coordination with maintenance centers.


• City of Orlando TMC - TMC Intersection Safety
• 1: The center shall provide current intersection safety status information.
• 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 Orlando TMC - TMC In-Vehicle Signing Management
• 4: The center shall receive system operational status from field equipment that supports in-vehicle signage communications.


• City of Orlando TMC - TMC Multi-Modal Coordination
• 2: The center shall exchange information with transit management centers including details current transit routes, the level of service on each route, and the progress of individual vehicles along their routes.


• City of Orlando TMC - TMC Passive Surveillance
• 1: The center shall collect time stamped vehicle identities from field equipment.
• 2: The center shall correlate the time stamped vehicle identities in order to calculate link travel times and derive other traffic measures.


• City of Orlando 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 Orlando TMC - TMC Roadway Warning
• 7: The center shall have the capability to receive real-time traffic (including location and speed), road conditions (e.g. ice, wet, etc.), and weather data (clear, rainy and snowy) from connected vehicles.
• 8: The center shall generate appropriate queue response strategies that include speed reduction, lane change, or diversion recommendations based on local traffic, weather, and roadway conditions.
• 9: The center shall use collected data to detect the location, duration, and length of queue propagation, as a result of significant downstream speed reductions or stopped traffic.


• City of Orlando TMC - TMC Signal Control
• 1: The center shall remotely control traffic signal controllers.
• 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 Orlando TMC - TMC Speed Warning
• 2: The center shall province the capability to control automated speed monitoring and speed warning systems.
• 3: The center shall monitor reduced speed zone warning field equipment.


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


• City of Orlando TMC - TMC Work Zone Traffic Management
• 3: The center shall remotely control driver information systems (such as dynamic messages signs, highway advisory radios) to advise drivers of activity around a work zone.


• 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 - Vehicle Basic Safety Communication
• 2: The vehicle shall provide its location with lane-level accuracy to on-board applications.


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


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


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


• Commercial Vehicle - Vehicle Queue Warning
• 1: The vehicle shall disseminate a queued status alert to other connected vehicles.
• 2: The vehicle shall receive queue warning messages from infrastructure systems.
• 3: The vehicle shall receive queue warning messages from other vehicles.


• 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 Speed Management Assist
• 1: Vehicle shall monitor current vehicle speed and communicates with the infrastructure to receive current speed limits or speed recommendations.
• 2: The vehicle shall receive speed warnings from the roadside field equipment.


• Commercial Vehicle - Vehicle Traveler Information Reception
• 1: The vehicle shall receive traveler information including traffic and road conditions, incident information, maintenance and construction information, event information, transit information, parking information, border crossing information, and weather information.
• 19: The vehicle shall receive notification that a vehicle has been detected traveling in the wrong direction.
• 20: The vehicle shall receive notification that vehicle is traveling in the wrong direction.


• County and City Roadway Maintenance and Construction Systems - MCM Data Collection
• 1: The center shall collect maintenance and construction data (such as field equipment status, infrastructure status, maintenance and construction activity data) gathered from roadway, traffic, and other maintenance and construction sources.


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


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


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


• FDOT District 5 CAV Field Equipment - RSE Intersection Management
• 1: The field element shall communicate with passing vehicles to provide the current signal phase and timing information for all lanes and approaches at a signalized intersection.
• 2: The field element shall send the request for emergency vehicle preemption to a traffic signal controller that results in preemption of the current control plan and grants right-of-way to the requesting vehicle.
• 5: The field element shall receive transit signal priority requests from transit vehicles and forward to the traffic signal controller.
• 6: The field element shall receive emergency vehicle preemption requests from emergency vehicles and forward to the traffic signal controller.
• 7: The field element shall determine when special vehicles requesting preemption or priority at a signal are authorized to do so based on their digital credentials.
• 9: The field element shall collect current signal phase and timing data from the traffic signal controller.


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


• FDOT District 5 CAV Field Equipment - RSE Queue Warning
• 1: The field equipment shall communicate with the connected vehicles to gather real-time vehicle-collected data including vehicle speed, location and localized weather condition from the vehicle network.
• 2: The field equipment shall communicate queue response strategies (speed reduction, lane change, diversion recommendations) to the vehicle.


• FDOT District 5 CAV Field Equipment - RSE Speed Warning
• 2: The field element shall provide a warning to a vehicle whose speed has been detected to be over the posted speed limit.


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


• FDOT District 5 CAV Field Equipment - RSE Wrong Way Vehicle Warning
• 1: The field equipment shall warn wrong way vehicles using V2I communications.


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


• 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 Environmental Monitoring
• 1: The field element shall include surface and sub-surface environmental sensors that measure road surface temperature, moisture, icing, salinity, and other measures.
• 3: The field element's environmental sensors shall be remotely controlled by a maintenance center.


• FDOT District 5 Field Equipment - Roadway Incident Detection
• 1: The field element shall collect, process, and send traffic images to the center for incident detection and further analysis.


• FDOT District 5 Field Equipment - Roadway Incident Scene Safety
• 1: The field device shall detect vehicle intrusions at an incident scene and warns public safety responders and drivers of imminent encroachment.


• FDOT District 5 Field Equipment - Roadway Passive Monitoring
• 1: The field element shall collect, process, and send data to the center to uniquely identify passing vehicles in order to support travel time measurement


• 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.
• 15: The field element shall provide to roadside equipment the intersection geometry and signal phase movement information including phase and timing information, alarm status, and priority/preempt status.
• 17: The field element shall receive requests for signal preemption.
• 2: The field element shall respond to pedestrian crossing requests by accommodating the pedestrian crossing.
• 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.


• FDOT District 5 Field Equipment - Roadway Signal Preemption
• 1: The field element shall respond to signal preemption requests from emergency vehicles.


• FDOT District 5 Field Equipment - Roadway Speed Monitoring and Warning
• 1: The field element shall include sensors to detect vehicle speeds, under traffic or maintenance center control.


• 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.
• 5: The field element shall provide dynamic message sign information to roadside equipment for transmission to connected vehicles to support in-vehicle signing.
• 8: The field element shall include dynamic message signs for dissemination of wrong way entry to drivers.


• FDOT District 5 Field Equipment - Roadway Warning
• 7: The field element shall receive commands from the controlling center that activate warning signs to approaching motorists.


• FDOT District 5 Field Equipment - Roadway Work Zone Traffic Control
• 1: The field element shall collect, process, and send work zone images to the center for further analysis and distribution, under center control.


• FDOT District 5 Field Equipment - Roadway Wrong Way Vehicle Detection
• 1: The field element shall detect wrong way vehicle entry using traffic detectors and surveillance equipment.
• 3: The field equipment shall provide potential wrong way vehicle detection data and images to the center for processing.


• 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.
• 9: The field element shall collect current signal phase and timing 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.
• 5: The field element shall provide intersection geometry update information to proximate Vehicles.


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


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


• 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 - 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 Incident Management
• 1: The maintenance center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.
• 2: The maintenance center shall exchange alert information and status with emergency management centers. The information includes notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction. The information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency, the effective time period, etc.


• 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 - TIC Connected Vehicle Traveler Info Distribution
• 1: The center shall collect traveler information for distribution including traffic and road conditions, incident information, maintenance and construction information, event information, transit information, parking information, and weather information.
• 2: The center shall distribute location relevant traveler information to short range communications equipment at the roadside.


• FDOT District 5 RTMC - TIC Data Collection
• 1: The center shall collect, process, and store traffic and highway condition information, including incident information, detours and road closures, event information, recommended routes, and current speeds on specific routes.
• 2: The 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.
• 3: The center shall collect, process, and store maintenance and construction information, including scheduled maintenance and construction work activities and work zone activities.


• FDOT District 5 RTMC - 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.
• 9: The center shall provide traffic and incident data to the media.


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


• FDOT District 5 RTMC - TMC Environmental Monitoring
• 1: The traffic center shall remotely control environmental sensors that measure road surface conditions including temperature, moisture, icing, salinity, and other measures.
• 2: The traffic center shall remotely control environmental sensors that measure weather conditions including temperature, wind, humidity, precipitation, and visibility.
• 4: The traffic center shall receive road condition information from weather service providers.


• FDOT District 5 RTMC - TMC Incident Detection
• 1: The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.


• FDOT District 5 RTMC - TMC Incident Dispatch Coordination
• 1: The center shall exchange alert information and status with emergency management centers. The information includes notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction for distribution to the public. The information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency, the effective time period, and information and instructions necessary for the public to respond to the alert. This may also identify specific information that should not be released to the public.
• 10: The center shall coordinate information and controls with other traffic management centers.
• 2: The center shall coordinate planning for incidents with emergency management centers - including pre-planning activities for disaster response, evacuation, and recovery operations.
• 6: The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters, traveler information service providers, media, border crossings, and rail operations centers.
• 7: The center shall provide road network conditions and traffic images to emergency management centers, maintenance and construction centers, and traveler information service providers.
• 8: The center shall monitor incident response performance and calculate incident response and clearance times.
• 9: The center shall exchange road network status assessment information with emergency management and maintenance centers including an assessment of damage sustained by the road network including location and extent of the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and recovery.


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


• FDOT SCMS - CCMS Enrollment
• 1: The Center shall provide enrollment credentials in response to valid enrollment requests.
• 2: The Center shall coordinate the distribution of enrollment credentials with other Centers.
• 3: The Center shall verify information received in enrollment 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).
• 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.


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


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


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


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


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


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


• Orange County CAV Field Equipment - RSE Environmental Monitoring
• 1: The field element shall communicate with passing vehicles to collect environmental monitoring data, including ambient air quality, emissions, temperature, precipitation, and other road weather information.
• 2: The field element shall aggregate and forward collected environmental probe information to the center.
• 3: The field element shall collect environmental monitoring data from sensors, including ambient air quality, emissions, temperature, precipitation, and other road weather information.
• 4: The field element shall provide application status to the center for monitoring.
• 5: The field element shall aggregate and filter the collected environmental data based on configuration parameters received from the controlling center.
• 6: The field element shall process the collected data locally and issue short-term road weather advisories for the road segment using short range communication.
• 7: The field element shall provide environmental data to other field elements.


• Orange County CAV Field Equipment - RSE Intersection Management
• 1: The field element shall communicate with passing vehicles to provide the current signal phase and timing information for all lanes and approaches at a signalized intersection.
• 2: The field element shall send the request for emergency vehicle preemption to a traffic signal controller that results in preemption of the current control plan and grants right-of-way to the requesting vehicle.
• 3: The field element shall send the infrastructure application status to the operations center.
• 4: The field element shall receive signal priority 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.
• 7: The field element shall determine when special vehicles requesting preemption or priority at a signal are authorized to do so based on their digital credentials.
• 8: The field element shall send a signal service request to the traffic signal controller when its application status determines the need for a signal change.
• 9: The field element shall collect current signal phase and timing data from the traffic signal controller.


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


• Orange County CAV Field Equipment - RSE Queue Warning
• 1: The field equipment shall communicate with the connected vehicles to gather real-time vehicle-collected data including vehicle speed, location and localized weather condition from the vehicle network.
• 2: The field equipment shall communicate queue response strategies (speed reduction, lane change, diversion recommendations) to the vehicle.


• Orange County CAV Field Equipment - RSE Speed Warning
• 1: The field element shall provide the reduced speed zone current posted speed limit as established by the controlling center and any roadway configuration changes associated with the reduced speed zone (e.g., lane closures, lane shifts).
• 2: The field element shall provide a warning to a vehicle whose speed has been detected to be over the posted speed limit.
• 3: The field element shall provide vehicles with about speed reductions, lane closures or roadway configuration changes.


• Orange County CAV Field Equipment - RSE Traffic Monitoring
• 1: The field element shall communicate with on-board equipment on passing vehicles to collect current vehicle position, speed, and heading and a record of previous events (e.g., starts and stops, link travel times) that can be used to determine current traffic conditions.
• 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.


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


• Orange County 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.
• 8: The ITS Object shall obtain a list of revoked credentials from the CCMS.


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


• Orange County Field Equipment - Roadway Basic Surveillance
• 1: The field element shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the center for further analysis and storage, under center control.
• 2: The field element shall collect, process, and send traffic images to the center for further analysis and distribution.
• 3: The field element shall collect, digitize, and send multimodal crossing and high occupancy vehicle (HOV), and high occupancy toll (HOT) lane sensor data to the center for further analysis and storage.
• 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.


• Orange County Field Equipment - Roadway Environmental Monitoring
• 1: The field element shall include surface and sub-surface environmental sensors that measure road surface temperature, moisture, icing, salinity, and other measures.
• 3: The field element's environmental sensors shall be remotely controlled by a maintenance center.


• Orange County Field Equipment - Roadway Incident Detection
• 1: The field element shall collect, process, and send traffic images to the center for incident detection and further analysis.


• Orange County Field Equipment - Roadway Passive Monitoring
• 1: The field element shall collect, process, and send data to the center to uniquely identify passing vehicles in order to support travel time measurement


• Orange County Field Equipment - Roadway Signal Control
• 1: The field element shall control traffic signals under center control.
• 10: The field element shall receive request for transit vehicle signal priority.
• 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.


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


• Orange County Field Equipment - Roadway Speed Monitoring and Warning
• 1: The field element shall include sensors to detect vehicle speeds, under traffic or maintenance center control.


• Orange County Field Equipment - Roadway Traffic Information Dissemination
• 1: The field element shall include dynamic message signs for dissemination of traffic and other information to drivers, under center control; the DMS may be either those that display variable text messages, or those that have fixed format display(s) (e.g. vehicle restrictions, or lane open/close).
• 3: The field element shall provide operational status for the driver information systems equipment (DMS, HAR, etc.) to the center.
• 8: The field element shall include dynamic message signs for dissemination of wrong way entry to drivers.


• Orange County Field Equipment - Roadway Warning
• 7: The field element shall receive commands from the controlling center that activate warning signs to approaching motorists.


• Orange County Field Equipment - Roadway Work Zone Traffic Control
• 1: The field element shall collect, process, and send work zone images to the center for further analysis and distribution, under center control.
• 2: Under traffic and maintenance center control, the field element shall include driver information systems (such as dynamic messages signs and highway advisory radios) that advise drivers of activity around the work zone through which they are currently passing.
• 3: Under the control of field personnel within maintenance vehicles, the field element shall include driver information systems (such as dynamic messages signs and highway advisory radios) that advise drivers of activity around a work zone through which they are currently passing.


• Orange County Field Equipment - RSE Intersection Management
• 1: The field element shall communicate with passing vehicles to provide the current signal phase and timing information for all lanes and approaches at a signalized intersection.
• 2: The field element shall send the request for emergency vehicle preemption to a traffic signal controller that results in preemption of the current control plan and grants right-of-way to the requesting vehicle.
• 9: The field element shall collect current signal phase and timing data from the traffic signal controller.


• Orange County 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.
• 5: The field element shall provide intersection geometry update information to proximate Vehicles.


• Orange County Field Equipment - RSE Situation Monitoring
• 1: The field element shall collect traffic-related data including snapshots of measured speed and heading and events including starts and stops, speed changes, and other vehicle control from vehicles.


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


• Orange County Fire Vehicles - EV On-Board En Route Support
• 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.


• Orange County TMC - Center Connected Vehicle Infrastructure Management
• 1: The Center shall be capable of monitoring the operational status of Connected Vehicle Roadside Equipment applications.
• 2: The Center shall be capable of modifying the operational status of Connected Vehicle Roadside Equipment applications.
• 4: The Center shall be capable of modifying the operational status of Connected Vehicle Roadside Equipment.


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


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


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


• Orange County TMC - 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.


• Orange County TMC - TMC Advanced Rail Crossing Management
• 1: The center shall remotely control highway-rail intersection (HRI) equipment located in the field.
• 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 support 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.


• Orange County 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.
• 5: The center shall respond to control data from center personnel regarding sensor and surveillance data collection, analysis, storage, and distribution.
• 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.


• Orange County TMC - TMC Incident Detection
• 1: The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.
• 3: The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters and traveler information service providers.


• Orange County TMC - TMC Incident Dispatch Coordination
• 1: The center shall exchange alert information and status with emergency management centers. The information includes notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction for distribution to the public. The information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency, the effective time period, and information and instructions necessary for the public to respond to the alert. This may also identify specific information that should not be released to the public.
• 2: The center shall coordinate planning for incidents with emergency management centers - including pre-planning activities for disaster response, evacuation, and recovery operations.


• Orange County TMC - TMC Intersection Safety
• 1: The center shall provide current intersection safety status information.
• 5: The field element shall be capable of configuring roadside equipment to perform the collection and transmission of information to support intersection safety.


• Orange County TMC - TMC In-Vehicle Signing Management
• 4: The center shall receive system operational status from field equipment that supports in-vehicle signage communications.


• Orange County TMC - TMC Multi-Modal Coordination
• 2: The center shall exchange information with transit management centers including details current transit routes, the level of service on each route, and the progress of individual vehicles along their routes.


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


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


• Orange County TMC - TMC Roadway Warning
• 7: The center shall have the capability to receive real-time traffic (including location and speed), road conditions (e.g. ice, wet, etc.), and weather data (clear, rainy and snowy) from connected vehicles.
• 8: The center shall generate appropriate queue response strategies that include speed reduction, lane change, or diversion recommendations based on local traffic, weather, and roadway conditions.
• 9: The center shall use collected data to detect the location, duration, and length of queue propagation, as a result of significant downstream speed reductions or stopped traffic.


• Orange County TMC - TMC Signal Control
• 1: The center shall remotely control traffic signal controllers.
• 2: The center shall accept notifications of pedestrian calls.
• 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.


• Orange County TMC - TMC Speed Warning
• 1: The center shall provide the capability to notify an enforcement agency when vehicle speeds in the work zone are in excess of the posted speed limit or are creating an unsafe condition based upon the current environmental or traffic conditions.
• 3: The center shall monitor reduced speed zone warning field equipment.


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


• Orange County TMC - TMC Work Zone Traffic Management
• 3: The center shall remotely control driver information systems (such as dynamic messages signs, highway advisory radios) to advise drivers of activity around a work zone.


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


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


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


• Osceola County CAV Field Equipment - RSE Environmental Monitoring
• 1: The field element shall communicate with passing vehicles to collect environmental monitoring data, including ambient air quality, emissions, temperature, precipitation, and other road weather information.
• 2: The field element shall aggregate and forward collected environmental probe information to the center.
• 3: The field element shall collect environmental monitoring data from sensors, including ambient air quality, emissions, temperature, precipitation, and other road weather information.
• 4: The field element shall provide application status to the center for monitoring.
• 5: The field element shall aggregate and filter the collected environmental data based on configuration parameters received from the controlling center.
• 6: The field element shall process the collected data locally and issue short-term road weather advisories for the road segment using short range communication.
• 7: The field element shall provide environmental data to other field elements.


• Osceola County CAV Field Equipment - RSE Intersection Management
• 1: The field element shall communicate with passing vehicles to provide the current signal phase and timing information for all lanes and approaches at a signalized intersection.
• 2: The field element shall send the request for emergency vehicle preemption to a traffic signal controller that results in preemption of the current control plan and grants right-of-way to the requesting vehicle.
• 5: The field element shall receive transit signal priority requests from transit vehicles and forward to the traffic signal controller.
• 6: The field element shall receive emergency vehicle preemption requests from emergency vehicles and forward to the traffic signal controller.


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


• Osceola County CAV Field Equipment - RSE Queue Warning
• 1: The field equipment shall communicate with the connected vehicles to gather real-time vehicle-collected data including vehicle speed, location and localized weather condition from the vehicle network.
• 2: The field equipment shall communicate queue response strategies (speed reduction, lane change, diversion recommendations) to the vehicle.


• Osceola County CAV Field Equipment - RSE Speed Warning
• 1: The field element shall provide the reduced speed zone current posted speed limit as established by the controlling center and any roadway configuration changes associated with the reduced speed zone (e.g., lane closures, lane shifts).
• 2: The field element shall provide a warning to a vehicle whose speed has been detected to be over the posted speed limit.
• 3: The field element shall provide vehicles with about speed reductions, lane closures or roadway configuration changes.


• Osceola County CAV Field Equipment - RSE Traffic Monitoring
• 1: The field element shall communicate with on-board equipment on passing vehicles to collect current vehicle position, speed, and heading and a record of previous events (e.g., starts and stops, link travel times) that can be used to determine current traffic conditions.
• 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.


• Osceola County 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


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


• Osceola County Field Equipment - Roadway Advanced Rail Crossing
• 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.


• Osceola County Field Equipment - Roadway Basic Surveillance
• 1: The field element shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the center for further analysis and storage, under center control.
• 2: The field element shall collect, process, and send traffic images to the center for further analysis and distribution.
• 4: The field element shall return sensor and CCTV system operational status to the controlling center.


• Osceola County Field Equipment - Roadway Incident Detection
• 1: The field element shall collect, process, and send traffic images to the center for incident detection and further analysis.
• 3: The field element's video devices shall be remotely controlled by a traffic management center.


• Osceola County Field Equipment - Roadway Passive Monitoring
• 1: The field element shall collect, process, and send data to the center to uniquely identify passing vehicles in order to support travel time measurement


• Osceola County Field Equipment - Roadway Signal Control
• 1: The field element shall control traffic signals under center control.
• 10: The field element shall receive request for transit vehicle signal priority.
• 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.


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


• Osceola County Field Equipment - Roadway Traffic Information Dissemination
• 1: The field element shall include dynamic message signs for dissemination of traffic and other information to drivers, under center control; the DMS may be either those that display variable text messages, or those that have fixed format display(s) (e.g. vehicle restrictions, or lane open/close).
• 3: The field element shall provide operational status for the driver information systems equipment (DMS, HAR, etc.) to the center.


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


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


• Osceola County Field Equipment - RSE Situation Monitoring
• 1: The field element shall collect traffic-related data including snapshots of measured speed and heading and events including starts and stops, speed changes, and other vehicle control from vehicles.


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


• Osceola County Traffic Operations Center - Center Connected Vehicle Infrastructure Management
• 1: The Center shall be capable of monitoring the operational status of Connected Vehicle Roadside Equipment applications.
• 2: The Center shall be capable of modifying the operational status of Connected Vehicle Roadside Equipment applications.
• 4: The Center shall be capable of modifying the operational status of Connected Vehicle Roadside Equipment.


• Osceola County Traffic Operations 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.


• Osceola County Traffic Operations 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.


• Osceola County Traffic Operations 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.


• Osceola County Traffic Operations 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.


• Osceola County Traffic Operations Center - TMC Advanced Rail Crossing Management
• 1: The center shall remotely control highway-rail intersection (HRI) equipment located in the field.
• 6: The center shall support 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.


• Osceola County Traffic Operations Center - TMC Basic Surveillance
• 1: The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements under remote control of the center.
• 2: The center shall monitor, analyze, and distribute traffic images from CCTV systems under remote control of the center.
• 3: The center shall monitor, analyze, and store multimodal crossing, high occupancy vehicle (HOV) and high occupancy toll (HOT) lane sensor data 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.


• Osceola County Traffic Operations Center - TMC Incident Detection
• 1: The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.
• 4: The center shall exchange incident and threat information with emergency management centers as well as maintenance and construction centers; including notification of existence of incident and expected severity, location, time and nature of incident.


• Osceola County Traffic Operations Center - TMC Incident Dispatch Coordination
• 1: The center shall exchange alert information and status with emergency management centers. The information includes notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction for distribution to the public. The information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency, the effective time period, and information and instructions necessary for the public to respond to the alert. This may also identify specific information that should not be released to the public.
• 2: The center shall coordinate planning for incidents with emergency management centers - including pre-planning activities for disaster response, evacuation, and recovery operations.


• Osceola County Traffic Operations Center - TMC Intersection Safety
• 1: The center shall provide current intersection safety status information.
• 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.


• Osceola County Traffic Operations Center - TMC In-Vehicle Signing Management
• 4: The center shall receive system operational status from field equipment that supports in-vehicle signage communications.


• Osceola County Traffic Operations Center - TMC Multi-Modal Coordination
• 2: The center shall exchange information with transit management centers including details current transit routes, the level of service on each route, and the progress of individual vehicles along their routes.


• Osceola County Traffic Operations Center - TMC Passive Surveillance
• 1: The center shall collect time stamped vehicle identities from field equipment.
• 2: The center shall correlate the time stamped vehicle identities in order to calculate link travel times and derive other traffic measures.


• Osceola County Traffic Operations Center - TMC Roadway Equipment Monitoring
• 1: The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) operational status.
• 2: The center shall collect and store CCTV surveillance system (traffic, pedestrian) operational status.
• 4: The center shall collect and store CCTV surveillance system (traffic, pedestrian) fault data send to the maintenance center for repair.


• Osceola County Traffic Operations Center - TMC Roadway Warning
• 7: The center shall have the capability to receive real-time traffic (including location and speed), road conditions (e.g. ice, wet, etc.), and weather data (clear, rainy and snowy) from connected vehicles.
• 8: The center shall generate appropriate queue response strategies that include speed reduction, lane change, or diversion recommendations based on local traffic, weather, and roadway conditions.
• 9: The center shall use collected data to detect the location, duration, and length of queue propagation, as a result of significant downstream speed reductions or stopped traffic.


• Osceola County Traffic Operations Center - TMC Signal Control
• 1: The center shall remotely control traffic signal controllers.
• 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.


• Osceola County Traffic Operations Center - TMC Speed Warning
• 2: The center shall province the capability to control automated speed monitoring and speed warning systems.
• 3: The center shall monitor reduced speed zone warning field equipment.


• Osceola County Traffic Operations Center - TMC Traffic Information Dissemination
• 1: The center shall remotely control dynamic messages signs for dissemination of traffic and other information to drivers.
• 10: The center shall distribute traffic information to information service providers for dissemination to the public.
• 3: The center shall collect operational status for the driver information systems equipment (DMS, HAR, etc.).


• Osceola County Traffic Operations Center - TMC Work Zone Traffic Management
• 3: The center shall remotely control driver information systems (such as dynamic messages signs, highway advisory radios) to advise drivers of activity around a work zone.


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


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


• Private Travelers Personal Computing Devices - Personal Traveler Information Reception
• 1: The personal traveler interface shall receive traffic information from a center and present it to the traveler.
• 3: The personal traveler interface shall receive event information from a center and present it to the traveler.
• 7: The personal traveler interface shall present information to the traveler in audible or visual forms, consistent with a personal device.


• 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


• 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.
• 8: The ITS Object shall obtain a list of revoked credentials from the CCMS.


• 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.
• 4: The vehicle shall collect road condition data from other vehicles.
• 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.


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


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


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


• Vehicle - Vehicle Queue Warning
• 1: The vehicle shall disseminate a queued status alert to other connected vehicles.
• 2: The vehicle shall receive queue warning messages from infrastructure systems.
• 3: The vehicle shall receive queue warning messages from other vehicles.


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


• Vehicle - Vehicle Speed Management Assist
• 1: Vehicle shall monitor current vehicle speed and communicates with the infrastructure to receive current speed limits or speed recommendations.
• 2: The vehicle shall receive speed warnings from the roadside field equipment.


• Vehicle - Vehicle Traveler Information Reception
• 1: The vehicle shall receive traveler information including traffic and road conditions, incident information, maintenance and construction information, event information, transit information, parking information, border crossing information, and weather information.
• 2: The vehicle shall receive advisory information, such as evacuation information, proximity to a maintenance and construction vehicle, wide-area alerts, work zone intrusion information, variable speed limits, tunnel entrance restrictions, border crossing advisories, and other special information.
• 21: The vehicle shall receive the infrastructure size and weight restrictions warning messages.
• 3: The vehicle shall receive indicator and fixed sign information including static sign information (e.g., stop, curve warning, guide signs, service signs, and directional signs) and dynamic information (e.g., current signal and traffic meter states and local conditions warnings identified by local environmental sensors).

Standards:

• (Data Not Needed) - Bluetooth
• (None-Data) - Secure Internet (ITS)
• (None-Data) - WAVE WSMP
• TPEG2 - Wide Area Broadcast
• TUF - Secure Internet (ITS)
• US: ATIS - Secure Wireless Internet (ITS)
• US: ATIS - Wide Area Broadcast
• US: Misbehavior reporting - Secure Internet (ITS)
• US: NTCIP Message Sign - SNMPv3/TLS
• US: NTCIP Roadside Unit - SNMPv3/TLS
• US: NTCIP Signal Priority - SNMPv3/TLS
• US: NTCIP Signal System Masters - SNMPv3/TLS
• US: NTCIP Traffic Signal - SNMPv3/TLS
• US: NTCIP Transportation Sensors - SNMPv3/TLS
• US: NTCIP Video Switches - SNMPv3/TLS
• US: NTCIP Warning Device - SNMPv3/TLS
• US: SAE Basic Safety Messages - WAVE WSMP
• US: SAE Lane-Level Mapping - Secure Internet (ITS)
• US: SAE Other J2735 - Local Unicast Wireless (1609.2)
• US: SAE Other J2735 - Secure Internet (ITS)
• US: SAE Other J2735 - WAVE TCP
• US: SAE Other J2735 - WAVE WSMP
• US: SAE Signal Control Messages - WAVE WSMP
• US: SAE Signal Preemption - WAVE TCP
• US: SAE Traveler Info - WAVE WSMP
• US: SAE VRU Messages - WAVE WSMP
• US: Security Credentials - Secure Internet (ITS)
• US: TMDD - NTCIP Messaging

Project Operational Concepts:

Roles and Responsibilities

• Travelers
• Enable bluetooth device.
• Load intersection safety application on mobile device.


• 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 Authorization, SCMS and Map services to Cities and Counties in the FDOT District 5 region.
• Provide CAV secure infrastructure for vehicle safety.


• Counties and Cities
• Manage work zones for all county and city maintenance and construction activities, and monitor work zone safety with county and city field equipment and vehicles.
• Provide maintenance and construction information to regional traffic operations and the traveling public using portable DMS devices.
• Provide maintenance and construction information to the traveling public using portable DMS devices.


• FDOT District 5
• Collect environmental information from its own field equipment, and from public and private weather service providers.
• Collect vehicle probe information using roadside equipment and calculate travel times.
• Coordinate a maintenance or construction request from the FDOT District 5 RTMC.
• Coordinate with city and county maintenance and construction systems, as well as other FDOT District maintenance and construction sections.
• Manage work zones on all FDOT maintenance and construction activities, and monitor work zone safety with FDOT field devices and vehicles.
• 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.
• 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 incident information to travelers via traffic information devices on freeways, such as DMS devices and HAR broadcasts, and through local ISPs and Web sites.
• Provide maintenance and construction information to the FDOT District 5 RTMC; regional maintenance and construction operations; and the traveling public using portable DMS devices.
• Provide maintenance and construction information to the traveling public using FDOT District 5 portable DMS devices.
• Provide traffic information to travelers using FDOT DMS devices.
• Provide traffic information to travelers using Florida 511, private companies, and the media.


• Orange County
• Collect vehicle probe data using roadside equipment and calculate travel times.
• Coordinate maintenance resources for incident response with county and city maintenance and construction systems.
• Coordinate traffic information and traffic control with the FDOT District 5 RTMC.
• 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 Orange County.
• Provide emergency signal preemption for county and local fire/EMS agencies.
• Provide incident information to travelers via traffic information devices on county roads and through local ISPs, Web sites, and the local media.
• Provide traffic information to travelers using Orange County DMS devices.
• Provide transit signal priority for regional transit providers using roadside devices.


• Osceola County
• Collect traffic probe data from vehicles using roadside equipment
• Coordinate maintenance resources for incident response with county and city maintenance and construction systems.
• Coordinate traffic information and traffic control with the FDOT District 5 RTMC.
• 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, planned sensors, and existing signals, for Osceola County.
• Provide emergency signal preemption for county and local fire/EMS agencies.
• Provide incident information to travelers using traffic information devices on county roads, and through local ISPs, Web sites, and the local media.
• Provide traffic information to travelers using Osceola County DMS devices.
• Provide transit signal priority for regional transit providers using roadside devices.


• LYNX
• Coordinate with FDOT District 5 for traffic signal priority.
• Coordinate with Orange County for traffic signal priority.
• Coordinate with Osceola County for traffic signal priority.
• Provide awareness of surrounding connected and autonomous vehicles.
• Provide transit signal priority services.


• City of Orlando
• Collect vehicle probe data using roadside equipment, and calculate travel times.
• Coordinate HRI signal adjustments, and provide track status information (e.g., blockage) to rail operators and local traffic operations.
• Coordinate maintenance resources for incident response with county and city maintenance and construction systems.
• Coordinate traffic information and traffic control with the FDOT District 5 RTMC.
• 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 Orlando.
• Provide emergency signal preemption for county and local fire/EMS agencies.
• Provide incident information to travelers via traffic information devices on city streets and through local information service providers, websites, and the local media.
• Provide traffic information in a coordination effort to the Florida 511
• Provide traffic information to travelers using City of Orlando DMS devices.
• Provide transit signal priority for regional transit providers using roadside devices.


• Private Weather Information Providers
• Provides weather forecasts and real-time weather information.