< < MC10 : MC11 : MC12 > >

MC11: Maintenance and Construction Signal Priority

The Maintenance and Construction Signal Priority service package uses maintenance and construction vehicle to infrastructure communications to allow a maintenance and construction vehicle (e.g., a snow plow or a lane striping vehicle) to request priority at one or a series of intersections. The service package provides feedback to the driver indicating whether the signal priority has been granted or not. This service package can contribute to improved operating performance of snow plows and other mission-critical maintenance and construction vehicles by reducing the time spent stopped at a red light.

Relevant Regions: Australia, Canada, European Union, and United States

Enterprise

Development Stage Roles and Relationships

Installation Stage Roles and Relationships

Operations and Maintenance Stage Roles and Relationships
(hide)

Source Destination Role/Relationship
Connected Vehicle Roadside Equipment MaintainerConnected Vehicle Roadside Equipment Maintains
Connected Vehicle Roadside Equipment ManagerConnected Vehicle Roadside Equipment Manages
Connected Vehicle Roadside Equipment ManagerConnected Vehicle Roadside Equipment Operator System Usage Agreement
Connected Vehicle Roadside Equipment OperatorConnected Vehicle Roadside Equipment Operates
Connected Vehicle Roadside Equipment OwnerConnected Vehicle Roadside Equipment Maintainer System Maintenance Agreement
Connected Vehicle Roadside Equipment OwnerConnected Vehicle Roadside Equipment Manager Operations Agreement
Connected Vehicle Roadside Equipment OwnerITS Roadway Equipment Maintainer Maintenance Data Exchange Agreement
Connected Vehicle Roadside Equipment OwnerITS Roadway Equipment Owner Information Exchange and Action Agreement
Connected Vehicle Roadside Equipment OwnerITS Roadway Equipment User Service Usage Agreement
Connected Vehicle Roadside Equipment OwnerMaint and Constr Field Personnel Application Usage Agreement
Connected Vehicle Roadside Equipment OwnerMaint and Constr Vehicle OBE Maintainer Maintenance Data Exchange Agreement
Connected Vehicle Roadside Equipment OwnerMaint and Constr Vehicle OBE Owner Expectation of Information Provision
Connected Vehicle Roadside Equipment OwnerMaint and Constr Vehicle OBE User Service Usage Agreement
Connected Vehicle Roadside Equipment OwnerMaint and Constr Vehicle Operator Application Usage Agreement
Connected Vehicle Roadside Equipment OwnerTraffic Management Center Maintainer Maintenance Data Exchange Agreement
Connected Vehicle Roadside Equipment OwnerTraffic Management Center Owner Information Exchange Agreement
Connected Vehicle Roadside Equipment OwnerTraffic Management Center User Service Usage Agreement
Connected Vehicle Roadside Equipment OwnerTraffic Operations Personnel Application Usage Agreement
Connected Vehicle Roadside Equipment SupplierConnected Vehicle Roadside Equipment Owner Warranty
ITS Roadway Equipment MaintainerITS Roadway Equipment Maintains
ITS Roadway Equipment ManagerITS Roadway Equipment Manages
ITS Roadway Equipment ManagerMaint and Constr Field Personnel System Usage Agreement
ITS Roadway Equipment OwnerConnected Vehicle Roadside Equipment Maintainer Maintenance Data Exchange Agreement
ITS Roadway Equipment OwnerConnected Vehicle Roadside Equipment Operator Application Usage Agreement
ITS Roadway Equipment OwnerConnected Vehicle Roadside Equipment Owner Information Exchange and Action Agreement
ITS Roadway Equipment OwnerConnected Vehicle Roadside Equipment User Service Usage Agreement
ITS Roadway Equipment OwnerITS Roadway Equipment Maintainer System Maintenance Agreement
ITS Roadway Equipment OwnerITS Roadway Equipment Manager Operations Agreement
ITS Roadway Equipment OwnerMulti-Access Edge Computing Maintainer Maintenance Data Exchange Agreement
ITS Roadway Equipment OwnerMulti-Access Edge Computing Operator Application Usage Agreement
ITS Roadway Equipment OwnerMulti-Access Edge Computing Owner Information Exchange and Action Agreement
ITS Roadway Equipment OwnerMulti-Access Edge Computing User Service Usage Agreement
ITS Roadway Equipment OwnerTraffic Management Center Maintainer Maintenance Data Exchange Agreement
ITS Roadway Equipment OwnerTraffic Management Center Owner Information Exchange Agreement
ITS Roadway Equipment OwnerTraffic Management Center User Service Usage Agreement
ITS Roadway Equipment OwnerTraffic Operations Personnel Application Usage Agreement
ITS Roadway Equipment SupplierITS Roadway Equipment Owner Warranty
Maint and Constr Center PersonnelMaint and Constr Management Center Operates
Maint and Constr Field PersonnelITS Roadway Equipment Operates
Maint and Constr Management Center MaintainerMaint and Constr Management Center Maintains
Maint and Constr Management Center ManagerMaint and Constr Center Personnel System Usage Agreement
Maint and Constr Management Center ManagerMaint and Constr Management Center Manages
Maint and Constr Management Center OwnerMaint and Constr Management Center Maintainer System Maintenance Agreement
Maint and Constr Management Center OwnerMaint and Constr Management Center Manager Operations Agreement
Maint and Constr Management Center OwnerMaint and Constr Vehicle OBE Maintainer Maintenance Data Exchange Agreement
Maint and Constr Management Center OwnerMaint and Constr Vehicle OBE Owner Information Exchange Agreement
Maint and Constr Management Center OwnerMaint and Constr Vehicle OBE User Service Usage Agreement
Maint and Constr Management Center OwnerMaint and Constr Vehicle Operator Application Usage Agreement
Maint and Constr Management Center OwnerTraffic Management Center Maintainer Maintenance Data Exchange Agreement
Maint and Constr Management Center OwnerTraffic Management Center Owner Information Exchange Agreement
Maint and Constr Management Center OwnerTraffic Management Center User Service Usage Agreement
Maint and Constr Management Center OwnerTraffic Operations Personnel Application Usage Agreement
Maint and Constr Management Center SupplierMaint and Constr Management Center Owner Warranty
Maint and Constr Vehicle OBE MaintainerMaint and Constr Vehicle OBE Maintains
Maint and Constr Vehicle OBE ManagerMaint and Constr Vehicle OBE Manages
Maint and Constr Vehicle OBE ManagerMaint and Constr Vehicle Operator System Usage Agreement
Maint and Constr Vehicle OBE OwnerConnected Vehicle Roadside Equipment Maintainer Maintenance Data Exchange Agreement
Maint and Constr Vehicle OBE OwnerConnected Vehicle Roadside Equipment Operator Application Usage Agreement
Maint and Constr Vehicle OBE OwnerConnected Vehicle Roadside Equipment Owner Expectation of Data Provision
Maint and Constr Vehicle OBE OwnerConnected Vehicle Roadside Equipment User Service Usage Agreement
Maint and Constr Vehicle OBE OwnerITS Roadway Equipment Maintainer Maintenance Data Exchange Agreement
Maint and Constr Vehicle OBE OwnerITS Roadway Equipment Owner Expectation of Data Provision
Maint and Constr Vehicle OBE OwnerITS Roadway Equipment User Service Usage Agreement
Maint and Constr Vehicle OBE OwnerMaint and Constr Center Personnel Application Usage Agreement
Maint and Constr Vehicle OBE OwnerMaint and Constr Center Personnel Vehicle Operating Agreement
Maint and Constr Vehicle OBE OwnerMaint and Constr Field Personnel Application Usage Agreement
Maint and Constr Vehicle OBE OwnerMaint and Constr Management Center Maintainer Maintenance Data Exchange Agreement
Maint and Constr Vehicle OBE OwnerMaint and Constr Management Center Owner Expectation of Data Provision
Maint and Constr Vehicle OBE OwnerMaint and Constr Management Center Owner Information Exchange Agreement
Maint and Constr Vehicle OBE OwnerMaint and Constr Management Center User Service Usage Agreement
Maint and Constr Vehicle OBE OwnerMaint and Constr Vehicle OBE Maintainer System Maintenance Agreement
Maint and Constr Vehicle OBE OwnerMaint and Constr Vehicle OBE Manager Operations Agreement
Maint and Constr Vehicle OBE OwnerMulti-Access Edge Computing Maintainer Maintenance Data Exchange Agreement
Maint and Constr Vehicle OBE OwnerMulti-Access Edge Computing Operator Application Usage Agreement
Maint and Constr Vehicle OBE OwnerMulti-Access Edge Computing Owner Expectation of Data Provision
Maint and Constr Vehicle OBE OwnerMulti-Access Edge Computing User Service Usage Agreement
Maint and Constr Vehicle OBE OwnerTIC Operator Application Usage Agreement
Maint and Constr Vehicle OBE OwnerTransportation Information Center Maintainer Maintenance Data Exchange Agreement
Maint and Constr Vehicle OBE OwnerTransportation Information Center Owner Information Exchange Agreement
Maint and Constr Vehicle OBE OwnerTransportation Information Center User Service Usage Agreement
Maint and Constr Vehicle OBE SupplierMaint and Constr Vehicle OBE Owner Warranty
Maint and Constr Vehicle OperatorMaint and Constr Vehicle OBE Operates
Multi-Access Edge Computing MaintainerMulti-Access Edge Computing Maintains
Multi-Access Edge Computing ManagerMulti-Access Edge Computing Manages
Multi-Access Edge Computing ManagerMulti-Access Edge Computing Operator System Usage Agreement
Multi-Access Edge Computing OperatorMulti-Access Edge Computing Operates
Multi-Access Edge Computing OwnerITS Roadway Equipment Maintainer Maintenance Data Exchange Agreement
Multi-Access Edge Computing OwnerITS Roadway Equipment Owner Information Exchange and Action Agreement
Multi-Access Edge Computing OwnerITS Roadway Equipment User Service Usage Agreement
Multi-Access Edge Computing OwnerMaint and Constr Field Personnel Application Usage Agreement
Multi-Access Edge Computing OwnerMaint and Constr Vehicle OBE Maintainer Maintenance Data Exchange Agreement
Multi-Access Edge Computing OwnerMaint and Constr Vehicle OBE Owner Expectation of Information Provision
Multi-Access Edge Computing OwnerMaint and Constr Vehicle OBE User Service Usage Agreement
Multi-Access Edge Computing OwnerMaint and Constr Vehicle Operator Application Usage Agreement
Multi-Access Edge Computing OwnerMulti-Access Edge Computing Maintainer System Maintenance Agreement
Multi-Access Edge Computing OwnerMulti-Access Edge Computing Manager Operations Agreement
Multi-Access Edge Computing OwnerTraffic Management Center Maintainer Maintenance Data Exchange Agreement
Multi-Access Edge Computing OwnerTraffic Management Center Owner Information Exchange Agreement
Multi-Access Edge Computing OwnerTraffic Management Center User Service Usage Agreement
Multi-Access Edge Computing OwnerTraffic Operations Personnel Application Usage Agreement
Multi-Access Edge Computing SupplierMulti-Access Edge Computing Owner Warranty
TIC OperatorTransportation Information Center Operates
Traffic Management Center MaintainerTraffic Management Center Maintains
Traffic Management Center ManagerTraffic Management Center Manages
Traffic Management Center ManagerTraffic Operations Personnel System Usage Agreement
Traffic Management Center OwnerConnected Vehicle Roadside Equipment Maintainer Maintenance Data Exchange Agreement
Traffic Management Center OwnerConnected Vehicle Roadside Equipment Operator Application Usage Agreement
Traffic Management Center OwnerConnected Vehicle Roadside Equipment Owner Information Exchange Agreement
Traffic Management Center OwnerConnected Vehicle Roadside Equipment User Service Usage Agreement
Traffic Management Center OwnerITS Roadway Equipment Maintainer Maintenance Data Exchange Agreement
Traffic Management Center OwnerITS Roadway Equipment Owner Information Exchange Agreement
Traffic Management Center OwnerITS Roadway Equipment User Service Usage Agreement
Traffic Management Center OwnerMaint and Constr Center Personnel Application Usage Agreement
Traffic Management Center OwnerMaint and Constr Field Personnel Application Usage Agreement
Traffic Management Center OwnerMaint and Constr Management Center Maintainer Maintenance Data Exchange Agreement
Traffic Management Center OwnerMaint and Constr Management Center Owner Information Exchange Agreement
Traffic Management Center OwnerMaint and Constr Management Center User Service Usage Agreement
Traffic Management Center OwnerMulti-Access Edge Computing Maintainer Maintenance Data Exchange Agreement
Traffic Management Center OwnerMulti-Access Edge Computing Operator Application Usage Agreement
Traffic Management Center OwnerMulti-Access Edge Computing Owner Information Exchange Agreement
Traffic Management Center OwnerMulti-Access Edge Computing User Service Usage Agreement
Traffic Management Center OwnerTIC Operator Application Usage Agreement
Traffic Management Center OwnerTraffic Management Center Maintainer System Maintenance Agreement
Traffic Management Center OwnerTraffic Management Center Manager Operations Agreement
Traffic Management Center OwnerTransportation Information Center Maintainer Maintenance Data Exchange Agreement
Traffic Management Center OwnerTransportation Information Center Owner Information Exchange Agreement
Traffic Management Center OwnerTransportation Information Center User Service Usage Agreement
Traffic Management Center SupplierTraffic Management Center Owner Warranty
Traffic Operations PersonnelTraffic Management Center Operates
Transportation Information Center MaintainerTransportation Information Center Maintains
Transportation Information Center ManagerTIC Operator System Usage Agreement
Transportation Information Center ManagerTransportation Information Center Manages
Transportation Information Center OwnerMaint and Constr Vehicle OBE Maintainer Maintenance Data Exchange Agreement
Transportation Information Center OwnerMaint and Constr Vehicle OBE Owner Information Exchange Agreement
Transportation Information Center OwnerMaint and Constr Vehicle OBE User Service Usage Agreement
Transportation Information Center OwnerMaint and Constr Vehicle Operator Application Usage Agreement
Transportation Information Center OwnerTraffic Management Center Maintainer Maintenance Data Exchange Agreement
Transportation Information Center OwnerTraffic Management Center Owner Information Exchange Agreement
Transportation Information Center OwnerTraffic Management Center User Service Usage Agreement
Transportation Information Center OwnerTraffic Operations Personnel Application Usage Agreement
Transportation Information Center OwnerTransportation Information Center Maintainer System Maintenance Agreement
Transportation Information Center OwnerTransportation Information Center Manager Operations Agreement
Transportation Information Center SupplierTransportation Information Center Owner Warranty

Functional

This service package includes the following Functional View PSpecs:

Physical Object Functional Object PSpec Number PSpec Name
Connected Vehicle Roadside Equipment RSE Intersection Management 1.1.1.6 Collect Vehicle Roadside Safety Data
1.1.2.6 Process Collected Vehicle Safety Data
1.1.6 Collect Vehicle Traffic Surveillance Data
1.2.7.14 Manage Connected Signal Priority and Preemption Requests
1.2.7.15 Process Intersection Safety Data
1.2.7.4 Process In-vehicle Signage Data
1.2.7.7 Process Vehicle Safety and Environmental Data for Output
1.5.10 Collect Vehicle Emissions Messages
ITS Roadway Equipment Roadway Signal Control 1.1.1.1 Process Traffic Sensor Data
1.2.7.1 Process Indicator Output Data for Roads
1.2.7.13 Provide Device Interface for Field Management Stations
1.2.7.16 Process Signal Control Conflict Monitoring
1.2.7.2 Monitor Roadside Equipment Operation
1.2.7.8 Provide Device Interface to Other Roadway Devices
Maint and Constr Management Center MCM Priority Management 9.1.3 Track M&C Vehicles and Equipment
9.1.4 Manage M&C Vehicle Fleet
9.1.7 Process Road Network Information
9.2.1 Schedule M&C Activities
9.2.5 Provide M&C Center Personnel Interface for Maint
Maint and Constr Vehicle OBE MCV Signal Priority 9.1.1 Manage M&C Systems On-Board
9.1.2 Collect M&C Vehicle Data On-Board
9.1.6 Provide M&C Vehicle Operator Interface for Maint
Traffic Management Center TMC Multi-Modal Coordination 1.1.2.2 Process Traffic Data
1.2.2.1 Determine Indicator State for Freeway Management
1.2.2.2 Determine Indicator State for Road Management
1.2.3 Determine Ramp State
1.3.2.2 Review and Classify Possible Incidents
1.4.2 Collect Demand Forecast Data
TMC Signal Control 1.1.2.2 Process Traffic Data
1.1.2.5 Process Vehicle Situation Data
1.1.4.1 Retrieve Traffic Data
1.1.4.4 Manage Traffic Archive Data
1.1.5 Exchange Data with Other Traffic Centers
1.2.1 Select Strategy
1.2.2.2 Determine Indicator State for Road Management
1.2.4.1 Output Control Data for Roads
1.2.6.1 Maintain Traffic and Sensor Static Data
1.2.8 Collect Traffic Field Equipment Fault Data
Transportation Information Center TIC Traffic Control Dissemination 6.2.2 Collect Traffic Data
6.5.1 Provide Broadcast Data Interface

Physical

The physical diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagram
PNG Diagram


Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object Class Description
Connected Vehicle Roadside Equipment Field 'Connected Vehicle Roadside Equipment' (CV RSE) represents the Connected Vehicle roadside devices (i.e., Roadside Units (RSUs)) equipped with short range wireless (SRW) communications technology, as well as any other supporting equipment that leverage the RSU and are not described by other objects (e.g., a local roadside processor). CVRSE are used to send messages to, and receive messages from, nearby vehicles and personal devices equipped with compatible communications technology. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers.
ITS Roadway Equipment Field 'ITS Roadway Equipment' represents the ITS equipment that is distributed on and along the roadway that monitors and controls traffic and monitors and manages the roadway. This physical object includes traffic detectors, environmental sensors, traffic signals, highway advisory radios, dynamic message signs, CCTV cameras and video image processing systems, grade crossing warning systems, and ramp metering systems. Lane management systems and barrier systems that control access to transportation infrastructure such as roadways, bridges and tunnels are also included. This object also provides environmental monitoring including sensors that measure road conditions, surface weather, and vehicle emissions. Work zone systems including work zone surveillance, traffic control, driver warning, and work crew safety systems are also included.
Maint and Constr Center Personnel Center The people that directly interface with a Maintenance and Construction Management Center. These personnel interact with fleet dispatch and management systems, road maintenance systems, incident management systems, work plan scheduling systems, and work zone management systems. They provide operator data and command inputs to direct system operations to varying degrees depending on the type of system and the deployment scenario.
Maint and Constr Management Center Center The 'Maint and Constr Management Center' monitors and manages roadway infrastructure construction and maintenance activities. Representing both public agencies and private contractors that provide these functions, this physical object manages fleets of maintenance, construction, or special service vehicles (e.g., snow and ice control equipment). The physical object receives a wide range of status information from these vehicles and performs vehicle dispatch, routing, and resource management for the vehicle fleets and associated equipment. The physical object participates in incident response by deploying maintenance and construction resources to an incident scene, in coordination with other center physical objects. The physical object manages equipment at the roadside, including environmental sensors and automated systems that monitor and mitigate adverse road and surface weather conditions. It manages the repair and maintenance of both non-ITS and ITS equipment including the traffic controllers, detectors, dynamic message signs, signals, and other equipment associated with the roadway infrastructure. Weather information is collected and fused with other data sources and used to support advanced decision support systems. The physical object remotely monitors and manages ITS capabilities in work zones, gathering, storing, and disseminating work zone information to other systems. It manages traffic in the vicinity of the work zone and advises drivers of work zone status (either directly at the roadside or through an interface with the Transportation Information Center or Traffic Management Center physical objects.) Construction and maintenance activities are tracked and coordinated with other systems, improving the quality and accuracy of information available regarding closures and other roadway construction and maintenance activities.
Maint and Constr Vehicle OBE Vehicle The 'Maint and Constr Vehicle OBE' resides in a maintenance, construction, or other specialized service vehicle or equipment and provides the processing, storage, and communications functions necessary to support highway maintenance and construction. All types of maintenance and construction vehicles are covered, including heavy equipment, supervisory vehicles, unmanned remote controlled field maintenance robots, and sensory platforms that may be wheeled or low altitude aerial vehicles (e.g. drones, balloons). The MCV OBE provides two-way communications between drivers/operators and dispatchers and maintains and communicates current location and status information. A wide range of operational status is monitored, measured, and made available, depending on the specific type of vehicle or equipment. A snow plow for example, would monitor whether the plow is up or down and material usage information. The Maint and Constr Vehicle OBE may also contain capabilities to monitor vehicle systems to support maintenance of the vehicle itself. A separate 'Vehicle OBE' physical object supports the general vehicle safety and driver information capabilities that apply to all vehicles, including maintenance and construction vehicles. The Maint and Constr Vehicle OBE supplements these general capabilities with capabilities that are specific to maintenance and construction vehicles.
Maint and Constr Vehicle Operator Vehicle The operator of maintenance, construction, or other specialized service vehicles or equipment. Represents the maintenance and construction vehicle operators. The operator provides input specific to maintenance and construction vehicle operations, including the status of maintenance actions. Information provided to the operator includes dispatch requests and maintenance and construction actions to be performed.
Multi-Access Edge Computing Field 'Multi-Access Edge Computing' ((MEC) previously known as mobile edge computing) represents computing devices that operate and are managed like a cloud server, but are deployed at the edge of a network (typically a cellular network, but it could be any network). While not in strict proximity to the transportation network, these systems do benefit from vastly decreased distances to the roadway compared to central systems, and so can provide lower latency than strictly backoffice systems
Traffic Management Center Center The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters.
Transportation Information Center Center The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service.

Includes Functional Objects:

Functional Object Description Physical Object
MCM Priority Management 'MCM Priority Management' monitors maintenance schedule performance and generates requests for priority on routes and at certain intersections to facilitate time-critical maintenance operations like winter maintenance. It may coordinate with the Traffic Management Center to provide priority along the selected route. It also coordinates with the Maintenance and Construction Vehicle OBE to monitor and manage local priority requests at individual intersections. Maint and Constr Management Center
MCV Signal Priority 'MCV Signal Priority' provides the capability for maintenance and construction vehicles to determine eligibility for priority and request signal priority at signalized intersections, ramps, and interchanges through short range communication with traffic control equipment at the roadside. Maint and Constr Vehicle OBE
MEC Intersection Management 'MEC Intersection Management' uses cellular communications to support connected vehicle applications that manage signalized intersections. It communicates with nearby vehicles and ITS infrastructure (e.g., the traffic signal controller) to enhance traffic signal operations. There may be constraints related to performance related to communications with participants using network operators foreign to the MEC. Multi-Access Edge Computing
Roadway Signal Control 'Roadway Signal Control' includes the field elements that monitor and control signalized intersections. It includes the traffic signal controllers, detectors, conflict monitors, signal heads, and other ancillary equipment that supports traffic signal control. It also includes field masters, and equipment that supports communications with a central monitoring and/or control system, as applicable. The communications link supports upload and download of signal timings and other parameters and reporting of current intersection status. It represents the field equipment used in all levels of traffic signal control from basic actuated systems that operate on fixed timing plans through adaptive systems. It also supports all signalized intersection configurations, including those that accommodate pedestrians. In advanced, future implementations, environmental data may be monitored and used to support dilemma zone processing and other aspects of signal control that are sensitive to local environmental conditions. ITS Roadway Equipment
RSE Intersection Management 'RSE Intersection Management' uses short range communications to support connected vehicle applications that manage signalized intersections. It communicates with approaching vehicles and ITS infrastructure (e.g., the traffic signal controller) to enhance traffic signal operations. Coordination with the ITS infrastructure also supports conflict monitoring to ensure the RSE output and traffic signal control output are consistent and degrade in a fail safe manner. This object also has the required functionalities for optimizing Signal Phase and Timing (SPaT), sending necessary commands to traffic signal controller to execute the optimized SPaT, and updating SPaT in real-time. Connected Vehicle Roadside Equipment
TIC Traffic Control Dissemination 'TIC Traffic Control Dissemination' serves as intermediary between transportation operations centers (e.g., TMC, Transit MC) and transportation users (e.g., vehicles, personal devices). It collects and disseminates intersection status, lane control information, special vehicle alerts, and other traffic control related information that is real-time or near real-time in nature and relevant to vehicles in a relatively local area on the road network. It collects traffic control information from Traffic Management and other Center(s) and disseminates the relevant information to vehicles and other mobile devices. Transportation Information Center
TMC Multi-Modal Coordination 'TMC Multi-Modal Coordination' supports center-to-center coordination between the Traffic Management and Transit Management Centers. It monitors transit operations and provides traffic signal priority for transit vehicles on request from the Transit Management Center. Traffic Management Center
TMC Signal Control 'TMC Signal Control' provides the capability for traffic managers to monitor and manage the traffic flow at signalized intersections. This capability includes analyzing and reducing the collected data from traffic surveillance equipment and developing and implementing control plans for signalized intersections. Control plans may be developed and implemented that coordinate signals at many intersections under the domain of a single Traffic Management Center and are responsive to traffic conditions and adapt to support incidents, preemption and priority requests, pedestrian crossing calls, etc. Traffic Management Center
Vehicle Basic Safety Communication 'Vehicle Basic Safety Communication' exchanges current vehicle characteristics, location, and motion (including past and intended maneuver) information with other vehicles in the vicinity and the infrastructure, uses that information to calculate vehicle paths, and warns the driver when the potential for an impending collision is detected. If available, map data is used to filter and interpret the relative location and motion of vehicles in the vicinity. Information from on-board sensors (e.g., radars and image processing) are also used, if available, in combination with the V2V communications to detect non-equipped vehicles and corroborate connected vehicle data. This object represents a broad range of implementations ranging from basic Vehicle Awareness Devices that only broadcast vehicle location and motion and provide no driver warnings to advanced integrated safety systems that coordinate maneuvers and may, in addition to warning the driver, provide collision warning information to support automated control functions that can support control intervention. This object can also support broadcasting other vehicle information required for passing through a specific roadway segment such as variables that describe vehicle's characteristics and parameters, driver's preferences in terms of vehicle motion and behavior, etc. Vehicle
Vehicle Intersection Movement 'Vehicle Intersection Movement' uses short-range wireless communications to monitor other connected vehicles at intersections and support the safe movement of the vehicle through the intersection by receiving and processing signal phase and timing messages from the intersection. Driver warnings are provided and the application may also optionally take control of the vehicle to avoid collisions, in coordination with Vehicle Control Automation. The application will also notify the infrastructure and other vehicles if it detects an unsafe infringement on the intersection. Vehicle

Includes Information Flows:

Information Flow Description
driver information Regulatory, warning, guidance, and other information provided to the driver to support safe and efficient vehicle operation.
intersection control status Status data provided by the traffic signal controller including phase information, alarm status, and priority/preempt status.
intersection geometry The physical geometry of an intersection covering the location and width of each approaching lane, egress lane, and valid paths between approaches and egresses. This flow also defines the location of stop lines, cross walks, specific traffic law restrictions for the intersection (e.g., turning movement restrictions), and other elements that support calculation of a safe and legal vehicle path through the intersection.
intersection management application info Intersection and device configuration data, including intersection geometry, and warning parameters and thresholds. This flow also supports remote control of the application so the application can be taken offline, reset, or restarted.
intersection management application status Infrastructure application status including current operational state and status of the field device and a log of operations.
intersection status Current signal phase and timing information for all lanes at a signalized intersection. This flow identifies active lanes and lanes that are being stopped and specifies the length of time that the current state will persist for each lane. It also identifies signal priority and preemption status and pedestrian crossing status information where applicable. It may also include future signal phase and timing information.
local signal priority request Request from a vehicle to a signalized intersection for priority/preemption at that intersection.
maint and constr center personnel input User input from maintenance and construction center personnel including routing information, scheduling data, dispatch instructions, device configuration and control, resource allocations, alerts, incident and emergency response plan coordination.
maint and constr dispatch information Information used to dispatch maintenance and construction vehicles, equipment, and crews and information used to keep work zone crews informed. This information includes routing information, traffic information, road restrictions, incident information, environmental information, decision support information, maintenance schedule data, dispatch instructions, personnel assignments, alert notifications, and corrective actions.
maint and constr operations information presentation Presentation of maintenance and construction operations information to center personnel. This information includes maintenance resource status (vehicles, equipment, and personnel), work schedule information, work status, road and weather conditions, traffic information, incident information and associated resource requests, security alerts, emergency response plans and a range of other information that supports efficient maintenance and construction operations and planning.
maint and constr vehicle location data The current location and related status (e.g., direction and speed) of the maintenance/construction vehicle.
maint and constr vehicle operational data Data that describes the maintenance and construction activity performed by the vehicle. Operational data includes materials usage (amount stored and current application rate), operational state of the maintenance equipment (e.g., blade up/down, spreader pattern), vehicle safety status, and other measures associated with the operation of a maintenance, construction, or other special purpose vehicle. Operational data may include basic operational status of the vehicle equipment or a more precise record of the work performed (e.g., application of crack sealant with precise locations and application characteristics).
maint and constr vehicle operator input User input from field personnel including current maintenance and construction status information as well as on-board device control.
maint and constr vehicle operator presentation Information presented to maintenance and construction field personnel including vehicle routing and traffic information, road restrictions, environmental information, decision support information, maintenance schedules, dispatch instructions, maintenance personnel assignments, vehicle maintenance information, work zone status information, and corrective actions.
right-of-way request notification Notice that a request has occurred for signal prioritization, signal preemption, pedestrian call, multi-modal crossing activation, or other source for right-of-way.
signal control commands Control of traffic signal controllers or field masters including clock synchronization.
signal control status Operational and status data of traffic signal control equipment including operating condition and current indications.
signal priority request Request from a vehicle for priority at an intersection. The request may include the priority level (preemption is the highest possible priority), the desired time and duration of service, and the intended travel path through the intersection. This flow may also allow the originator to cancel a previously issued request for priority.
signal priority service request A service request for vehicle priority issued to a traffic signal controller. The request includes the priority level (preemption is the highest possible priority), and may include other parameters such as the desired time and duration of service, and the intended travel path through the intersection. This flow also allows the originator to cancel a previously issued request for priority.
signal priority status In response to a request for signal priority, this flow indicates the status of the priority or preemption request.
traffic control priority request Request for signal priority at one or more intersections along a particular route.
traffic control priority status Status of signal priority request functions at the roadside (e.g., enabled or disabled).
vehicle location and motion Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor Goal
E. Protect and enhance the environment, promote energy conservation, improve the quality of life, and promote consistency between transportation improvements and State and local planned growth and economic development patterns; Protect/Enhance the Environment

Associated Objective Categories

Objective Category
System Efficiency: Energy Consumption

Associated Objectives and Performance Measures

Objective Performance Measure
Reduce excess fuel consumed due to congestion by X percent by year Y. Excess fuel consumed (total or per capita).

 
Since the mapping between objectives and service packages is not always straight-forward and often situation-dependent, these mappings should only be used as a starting point. Users should do their own analysis to identify the best service packages for their region.

Needs and Requirements

Need Functional Object Requirement
01 Traffic Management needs to collect data from maintenance management in order to support traffic signal system optimization for maintenance and construction vehicles. MCM Priority Management 01 The maintenance/construction vehicle shall provide maintenance vehicle operational data to the center.
02 The center shall make signal priority requests to the signal control center.
03 The center shall accept vehicle location data from maintenance/construction vehicles.
07 The center shall accept signal priority status information from the signal control center.
TMC Multi-Modal Coordination 04 The center shall respond to requests from maintenance and construction management centers for signal priority at one or more intersections along a particular route.
02 Traffic Management needs to process traffic and maintenance and construction vehicle data in order to provide maintenance and construction vehicle signal priority for the efficient movement of maintenance and construction vehicles. MCM Priority Management 06 The center shall accept input from center personnel related to dispatch and instruction of maintenance/construction vehicles.
TIC Traffic Control Dissemination 01 The center shall provide intersection status, lane control information, and other real time traffic control related information to vehicles.
03 Traffic Management needs to communicate with field equipment to provide maintenance and construction vehicle signal priority commands to the intersection. Roadway Signal Control 09 The field element shall report current intersection signal timing information to roadside equipment for transmission to connected vehicles.
RSE Intersection Management 07 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.
09 The field element shall collect current signal phase and timing data from the traffic signal controller.
TMC Signal Control 01 The center shall remotely control traffic signal controllers.
10 The center shall adjust signal timing in response to a signal prioritization, signal preemption, pedestrian call, multi-modal crossing activation, or other requests for right-of-way.
04 The Maintenance and Construction Vehicle Operator needs to progress through his arterial route safely and efficiently. MCM Priority Management 01 The maintenance/construction vehicle shall provide maintenance vehicle operational data to the center.
02 The center shall make signal priority requests to the signal control center.
05 The center shall provide dispatch instructions to maintenance/construction vehicles.
06 The center shall accept input from center personnel related to dispatch and instruction of maintenance/construction vehicles.
07 The center shall accept signal priority status information from the signal control center.
MCV Signal Priority 01 The maintenance/construction vehicle shall provide operational information to the vehicle operator, including routing and traffic information and maintenance/construction-specific information relevant to ongoing or upcoming taskings.
02 The maintenance/construction vehicle shall accept signalized intersection status information from roadside controllers.
03 The maintenance/construction vehicle shall roadway geometry information from roadside controllers.
04 The maintenance/construction 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 the vehicle to
05 The maintenance/construction vehicle shall accept dispatch information from maintenance centers.
06 The maintenance/construction vehicle shall send schedule deviation data and status of priority requests to the vehicle operator and provide the capability for the vehicle operator to control the priority system.
07 The maintenance/construction vehicle shall accept input from field equipment describing the status of signal priority requests.
08 The maintenance/construction vehicle shall accept input from the vehicle operator, regarding operational status and device control.
Roadway Signal Control 13 The field element shall receive requests for maintenance and construction vehicle signal priority.
14 The field element shall report current maintenance and construction vehicle priority status to the center.
RSE Intersection Management 01 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.
07 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.
10 The field element shall receive signal priority requests from maintenance and construction vehicles and forward to the traffic signal controller.
TIC Traffic Control Dissemination 02 The center shall collect traffic control information from Traffic Management Center.
03 The center shall provide real time signal phase and timing information for all lanes at a signalized intersection to vehicle.
Vehicle Basic Safety Communication 06 The vehicle shall exchange location and motion information with roadside equipment and nearby vehicles.
Vehicle Intersection Movement 03 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.
05 Maintenance and Construction management needs to be able to be able to monitor the schedule performance of maintenance/construction vehicles so that it might request signal priority when needed. MCM Priority Management 03 The center shall accept vehicle location data from maintenance/construction vehicles.
04 The center shall provide information to the center personnel indicating maintenance/construction vehicle operating conditions and status.
05 The center shall provide dispatch instructions to maintenance/construction vehicles.
06 The center shall accept input from center personnel related to dispatch and instruction of maintenance/construction vehicles.

Related Sources

Document Name Version Publication Date
None


Security

In order to participate in this service package, each physical object should meet or exceed the following security levels.

Physical Object Security
Physical Object Confidentiality Integrity Availability Security Class
Connected Vehicle Roadside Equipment Moderate Moderate Moderate Class 2
ITS Roadway Equipment Moderate High Moderate Class 3
Maint and Constr Management Center Moderate Moderate Moderate Class 2
Maint and Constr Vehicle OBE Moderate Moderate Moderate Class 2
Multi-Access Edge Computing  
Traffic Management Center Moderate High Moderate Class 3
Transportation Information Center Not Applicable Low Moderate Class 1



In order to participate in this service package, each information flow triple should meet or exceed the following security levels.

Information Flow Security
Source Destination Information Flow Confidentiality Integrity Availability
Basis Basis Basis
Connected Vehicle Roadside Equipment ITS Roadway Equipment signal priority service request Not Applicable Moderate Low
There is no sensitive or confidential information within this messages. Additionally, it could be inferred by observing either the presence of a transit vehicle near an intersection, or the effect on the timing of the intersection. This is also transmitted as a result of broadcast data. The RSE is transmitting a request to the ITS RE on behalf of a transit vehicle. It should only be making requests on behalf of an approved vehicle. A corrupted request may lead to a transit vehicle not receiving a green light after requesting it. In this case, this may lead to traffic delays. If an unapproved vehicle is able to forge these requests, they may cause larger scale traffic delays. If the ITS RE does not receive any requests, the vehicle may not receive the priority it requested. In the worst case scenario the transit vehicle would be forced to wait at some lights until they turned green. It would be more useful for a device to support this application, and only have some messages received, than to not support this application at all.
Connected Vehicle Roadside Equipment Maint and Constr Vehicle OBE signal priority status Low Moderate Low
Not much could be learned by observing this flow, just the state of the priority request and the identity of the requester. Both of those are information that can be gleaned by physical observation, and give little advantage to an observer. Signal priority status information enables the receiving vehicle to proceed with more surety toward's its next stop; while there are obvious redundancies, a degree of confidence in the state of the message is required for user acceptance if nothing else. The most important aspect of this flow is the initiating request and hopefull success of that priority message; if that succeeds then the signal will turn in the vehicle's favor, making this flow a 'nice-to-have' that should be correct if it arrives, but is not necessary for the priority application to function.
Connected Vehicle Roadside Equipment Traffic Management Center intersection management application status Moderate Moderate Low
This information could be of interest to a malicious individual who is attempting to determine the best way to accomplish a crime. As such it would be best to not make it easily accessible. May be LOW in some cases. If this is compromised, it could send unnecessary maintenance workers, or worse report plausible data that is erroneous. From THEA: should be able to cope with some bad information on the status and record of alerts/warnings; aggregate info; however could cause appearance of excessive traffic violations or unnecessary maintenance caused if data is compromised (operational state, status, log); should not affect the application functionality Incident status information should be presented in timely fashion as large scale mobility and safety issues are related. There are other mechanisms for reporting this information however, thus MODERATE. From THEA: Only limited adverse effect of info is not timely/readily available
ITS Roadway Equipment Connected Vehicle Roadside Equipment intersection control status Low High Moderate
This data is intentionally transmitted to everyone via a broadcast. It can also be determined via other visual indicators. If this is compromised, the Roadway Equipment and Roadside Equipment will be sending messages that are inconsistent with each other, leading to confusion and possible accidents. If this is down, the RSE doesn’t get the information it needs to stay in synch with the actual signal state, reducing or eliminating the value add from having this application. The RSE must detect a lack of availability and choose not to send out-of-date information, so a failure of availability could be interpreted as having the same value as Integrity. However, this data is semi-predictable and there are other indicators (such as the lights themselves) of the intersection status. From NYC, who believe this should be HIGH for some applications: If this is down, the RSE doesn’t get the information it needs to stay in synch with the actual signal state, reducing or eliminating the value add from having this application. The RSE must detect a lack of availability and choose not to send out-of-date information, so a failure of availability cannot have worse consequences than a failure of integrity which we have previously assessed at HIGH.
ITS Roadway Equipment Maint and Constr Vehicle Operator driver information Not Applicable High Moderate
This data is sent to all drivers and is also directly observable, by design. This is the primary signal trusted by the driver to decide whether to go through the intersection and what speed to go through the intersection at; if it’s wrong, accidents will happen. If the lights are out you have to get a policeman to direct traffic – expensive and inefficient and may cause a knock-on effect due to lack of coordination with other intersections.
ITS Roadway Equipment Traffic Management Center right-of-way request notification Low Moderate Moderate
This can be reasonably guessed based on observing the ITS RE’s environment. It is obvious when a bus approaches an intersection. Invalid messages could lead to an unauthorized user gaining signal priority at an intersection. This could also be used to delay traffic, which could lead to a financial impact on the community. However, the traffic signal will have controls in place to ensure that it does not display an illegal configuration (such as green in every direction). Even if all of the Right-of-way Requests are not passed along from an ITS RE, the intersection will still operate as normal. There are other existing methods to assist a right-of-way requesting vehicle safely traveling through an intersection, such as lights and sirens, which prevent this from being a HIGH. DISC: THEA and NYC believe this to be LOW: "not necessary for the app to work; can cope with not having immediately available data"
ITS Roadway Equipment Traffic Management Center signal control status Low High Moderate
The current conditions of an ITS RE are completely observable, by design. This influences the TMC response to a right-of-way request. It should be as accurate as the right-of-way request themselves. For some applications (ISIG) this need only be moderate. Per THEA: info needs to be accurate and should not be tampered to enable effective monitoring and control by the TMC. DISC: THEA believes this to be MODERATE: "info needs to be accurate and should not be tampered to enable effective monitoring and control by the TMC; should be as accurate as the right of way request". NYC:TMC doesn’t play an active role in this application, i.e. even if the information contained in this flow were incorrect, it is unlikely to affect the outcome of this application one way or the other. On some applications NYC has this MODERATE though. RES: This value can obviously change a lot depending on the application context. The TMC will need the current status of the ITS RE in order to make an educated decision. If it is unavailable, the system is unable to operate. However, a few missed messages will not have a catastrophic impact. From NYC: TMC doesn’t play an active role in this application, i.e. even if it is unavailable, it is unlikely to affect the outcome of this application one way or the other. RES: This value can change a lot depending on the application context.
Maint and Constr Center Personnel Maint and Constr Management Center maint and constr center personnel input High High High
Direct interactions between personnel and systems in a backoffice environment are effectively protected by physical means, so long as the interaction is in a dedicated facility. If this interaction is virtual (i.e. ,the MCMC is not directly in front of the MCMC Personnel, like in a cloud-based system) then the user's input requires some degree of obfuscation depending on sensitivity of information. Given that this could include information about compromised or ineffectual systems, including security systems, the potential for damage is high. Thus, HIGH. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Maint and Constr Management Center Maint and Constr Center Personnel maint and constr operations information presentation Not Applicable Moderate Moderate
System maintenance flows should have some protection from casual viewing, as otherwise imposters could gain illicit control over field equipment Information presented to backoffice system operators must be consistent or the operator may perform actions that are not appropriate to the real situation. The backoffice system operator should have access to system operation. If this interface is down then control is effectively lost, as without feedback from the system the operator has no way of knowing what is the correct action to take.
Maint and Constr Management Center Maint and Constr Vehicle OBE maint and constr dispatch information Moderate Moderate Moderate
Maintenance vehicle dispatch and routing information is predictive of maintenance vehicle location, and should be protected from hostile actors, as they may use this information for target acquisition or selection or damage assessment, for example. Maintenance vehicle dispatch instructions need to be correct and timely so that road maintenance activities are performed when and where they should be. Corruption of this information would cost time and money and may impact mobility. Maintenance vehicle dispatch instructions need to be correct and timely so that road maintenance activities are performed when and where they should be. Corruption of this information would cost time and money and may impact mobility.
Maint and Constr Management Center Traffic Management Center traffic control priority request Low Moderate Moderate
The result of this will be directly observable. Invalid messages could lead to an unauthorized user gaining transit signal priority at an intersection. This could also be used to delay traffic, which could lead to a financial impact on the community. However, the traffic signal will have controls in place to ensure that it does not display an illegal configuration (such as green in every direction). These messages are important to help with the transit signal priority application. Without them, it will not work. However, if these signals are not received, the ITS RE will continue to function using its default configuration. The Transit Management Center should have an acknowledgement of the receipt of a message.
Maint and Constr Vehicle OBE ITS Roadway Equipment local signal priority request Not Applicable Moderate Low
This information can be observed. nly approved vehicles should be allowed to make these requests to the RSE. A corrupted request may lead to a transit vehicle not receiving a green light after requesting it. In this case, this may lead to traffic delays. If an unapproved vehicle is able to forge these requests, they may cause larger scale traffic delays. If the RSE does not receive any requests, the vehicle may not receive the priority it requested. In the worst case scenario the transit vehicle would be forced to wait at some lights until they turned green. It would be more useful for a device to support this application, and only have some messages received, than to not support this application at all.
Maint and Constr Vehicle OBE Maint and Constr Management Center maint and constr vehicle location data Moderate Moderate Moderate
This is effectively a tracking flow, which if intercepted would provide a third party with the ability to track maintenance and construction vehicles, which could enable nefarious and illegal activities. Corruption, unavailability or unauthorized manipulation of this data could lead to a lack of understanding of maintenance vehilce locations. This could negatively effect coordinated actions such as roadway treatment and snow removal, compromising mobility. It could also negatively impact the safety of the vehicle operator. Corruption, unavailability or unauthorized manipulation of this data could lead to a lack of understanding of maintenance vehilce locations. This could negatively effect coordinated actions such as roadway treatment and snow removal, compromising mobility. It could also negatively impact the safety of the vehicle operator.
Maint and Constr Vehicle OBE Maint and Constr Management Center maint and constr vehicle operational data Moderate Moderate Moderate
Contains information indicating the activity of the maintenance vehicle, which if public could be used against the vehicle or the infrastructure, depending on the hostile party's intent. Status information needs to be timely and correct or the dispatcher may issue additional instructions, costing time and money. Status information needs to be timely and correct or the dispatcher may issue additional instructions, costing time and money.
Maint and Constr Vehicle OBE Maint and Constr Vehicle Operator maint and constr vehicle operator presentation Moderate High High
System maintenance flows should have some protection from casual viewing, as otherwise imposters could gain illicit control over the MCV. System maintenance flows are the primary interface between field personnel and field equipment, and must present accurate data or inappropriate maintenance actions may be taken. System maintenance flows are the primary interface between field personnel and field equipment, and must present accurate data or inappropriate maintenance actions may be taken.
Maint and Constr Vehicle Operator Maint and Constr Vehicle OBE maint and constr vehicle operator input Not Applicable Moderate High
Observation of control or status information is unlikely to have any value to a third party; actions of field personnel should be observable anyway. Any driver/operator interaction with vehicle systems needs some assurance of correctness; corruption of this information could lead to unexpected vehicle behavior which poses a limited safety risk. Without direct local control of vehicle systems the vehicle is essentially uncontrolled.
Traffic Management Center Connected Vehicle Roadside Equipment intersection management application info Moderate High Low
proprietary configuration data with warning parameters and thresholds should be accurate and not be tampered with; could enable outside control of application should be timely and readily available or may not be able to restart/reset; however, should be able to operate on a default configuration and/or stop sending messages
Traffic Management Center ITS Roadway Equipment signal control commands Moderate High Moderate
Control flows, even for seemingly innocent devices, should be kept confidential to minimize attack vectors. While an individual installation may not be particularly impacted by a cyberattack of its sensor network, another installation might be severely impacted, and different installations are likely to use similar methods, so compromising one leads to compromising all. DISC: NYC believes this to be LOW: "The result of this will be directly observable." Invalid messages could lead to an unauthorized user gaining control of an intersection. This could also be used to bring traffic to a standstill, which could lead to a large financial impact on the community. DISC: NYC believes this to be MODERATE: The signal timing is critical to the intersection operation; incorrect signal timing can lead to significant congestion and unreliable operation; while unsafe operation is controlled by the cabinet monitoring system, attackers could “freeze” the signal or call a preemption. RES: This will vary depending on the application and implementation. These messages are important to help with preemption and signal priority applications. Without them, these applications mayl not work. However, if these signals are not received, the ITS RE will continue to function using its default configuration. The TMC should have an acknowledgement of the receipt of a message. DISC: NYC blieves this to be LOW: TMC doesn’t play an active role in this application, i.e. even if it is unavailable, it is unlikely to affect the outcome of this application one way or the other. RES: This will vary depending on the application and implementation.
Traffic Management Center Maint and Constr Management Center traffic control priority status Low Moderate Moderate
This information is not sensitive. There are other indicators when an intersection supports transit signal priority. This information is important for the system to function correctly. If it is incorrect, it could lead to the transit system designing routes that do not take advantage of the optimizations. This information is necessary for the system to operate properly. There should be an acknowledgement of the message being received.
Traffic Management Center Transportation Information Center intersection status Not Applicable Moderate Moderate
This data is distributed using a variety of mechanisms, some of which are localized broadcast; it is desireable that all potential users get this information. If this flow is not accurate or delivered in a timely fashion then a large variety of mobility and safety services that depend on it will not work properly. If this flow is not accurate or delivered in a timely fashion then a large variety of mobility and safety services that depend on it will not work properly.

Standards

The following table lists the standards associated with physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages. These pages can be accessed directly from the SVG diagram(s) located on the Physical tab, by clicking on each information flow line on the diagram.

NameTitlePhysical Object
CTI 4001 RSU Roadside Unit (RSU) Standard Connected Vehicle Roadside Equipment
ITE 5201 ATC Advanced Transportation Controller ITS Roadway Equipment
ITE 5202 ATC Model 2070 Model 2070 Controller Standard ITS Roadway Equipment
ITE 5301 ATC ITS Cabinet Intelligent Transportation System Standard Specification for Roadside Cabinets ITS Roadway Equipment
ITE 5401 ATC API Application Programming Interface Standard for the Advanced Transportation Controller ITS Roadway Equipment
NEMA TS 8 Cyber and Physical Security Cyber and Physical Security for Intelligent Transportation Systems ITS Roadway Equipment
Traffic Management Center
NEMA TS2 Traffic Controller Assemblies Traffic Controller Assemblies with NTCIP Requirements ITS Roadway Equipment




System Requirements

System Requirement Need
001 The system shall provide dispatch instructions to maintenance/construction vehicles. 04 The Maintenance and Construction Vehicle Operator needs to progress through his arterial route safely and efficiently.
05 Maintenance and Construction management needs to be able to be able to monitor the schedule performance of maintenance/construction vehicles so that it might request signal priority when needed.
002 The system shall accept input from center personnel related to dispatch and instruction of maintenance/construction vehicles. 02 Traffic Management needs to process traffic and maintenance and construction vehicle data in order to provide maintenance and construction vehicle signal priority for the efficient movement of maintenance and construction vehicles.
04 The Maintenance and Construction Vehicle Operator needs to progress through his arterial route safely and efficiently.
05 Maintenance and Construction management needs to be able to be able to monitor the schedule performance of maintenance/construction vehicles so that it might request signal priority when needed.
003 The system shall provide information to the center personnel indicating maintenance/construction vehicle operating conditions and status. 05 Maintenance and Construction management needs to be able to be able to monitor the schedule performance of maintenance/construction vehicles so that it might request signal priority when needed.
004 The system shall accept vehicle location data from maintenance/construction vehicles. 01 Traffic Management needs to collect data from maintenance management in order to support traffic signal system optimization for maintenance and construction vehicles.
05 Maintenance and Construction management needs to be able to be able to monitor the schedule performance of maintenance/construction vehicles so that it might request signal priority when needed.
005 The system shall make signal priority requests to the signal control center. 01 Traffic Management needs to collect data from maintenance management in order to support traffic signal system optimization for maintenance and construction vehicles.
04 The Maintenance and Construction Vehicle Operator needs to progress through his arterial route safely and efficiently.
006 The system shall accept signal priority status information from the signal control center. 01 Traffic Management needs to collect data from maintenance management in order to support traffic signal system optimization for maintenance and construction vehicles.
04 The Maintenance and Construction Vehicle Operator needs to progress through his arterial route safely and efficiently.
007 The system shall remotely control traffic signal controllers. 03 Traffic Management needs to communicate with field equipment to provide maintenance and construction vehicle signal priority commands to the intersection.
008 The system shall provide intersection status, lane control information, and other real time traffic control related information to vehicles. 02 Traffic Management needs to process traffic and maintenance and construction vehicle data in order to provide maintenance and construction vehicle signal priority for the efficient movement of maintenance and construction vehicles.
009 The system shall adjust signal timing in respond to a signal prioritization, signal preemption, pedestrian call, multi-modal crossing activation, or other requests for right-of-way. 03 Traffic Management needs to communicate with field equipment to provide maintenance and construction vehicle signal priority commands to the intersection.
010 The system shall collect traffic control information from Traffic Management Center. 04 The Maintenance and Construction Vehicle Operator needs to progress through his arterial route safely and efficiently.
011 The system shall accept input from field equipment describing the status of signal priority requests. 04 The Maintenance and Construction Vehicle Operator needs to progress through his arterial route safely and efficiently.
012 The system shall provide real time signal phase and timing information for all lanes at a signalized intersection to vehicle. 04 The Maintenance and Construction Vehicle Operator needs to progress through his arterial route safely and efficiently.
013 The system shall respond to requests from maintenance and construction management centers for signal priority at one or more intersections along a particular route. 01 Traffic Management needs to collect data from maintenance management in order to support traffic signal system optimization for maintenance and construction vehicles.
014 The system shall accept input from the vehicle operator, regarding operational status and device control. 04 The Maintenance and Construction Vehicle Operator needs to progress through his arterial route safely and efficiently.
015 The system shall provide operational information to the vehicle operator, including routing and traffic information and maintenance/construction-specific information relevant to ongoing or upcoming taskings. 04 The Maintenance and Construction Vehicle Operator needs to progress through his arterial route safely and efficiently.
016 The system shall accept signalized intersection status information from roadside controllers. 04 The Maintenance and Construction Vehicle Operator needs to progress through his arterial route safely and efficiently.
017 The system shall report current intersection signal timing information to roadside equipment for transmission to connected vehicles. 03 Traffic Management needs to communicate with field equipment to provide maintenance and construction vehicle signal priority commands to the intersection.
018 The system shall roadway geometry information from roadside controllers. 04 The Maintenance and Construction Vehicle Operator needs to progress through his arterial route safely and efficiently.
019 The system 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 the vehicle to 04 The Maintenance and Construction Vehicle Operator needs to progress through his arterial route safely and efficiently.
020 The system shall report current maintenance and construction vehicle priority status to the center. 04 The Maintenance and Construction Vehicle Operator needs to progress through his arterial route safely and efficiently.
021 The system shall accept dispatch information from maintenance centers. 04 The Maintenance and Construction Vehicle Operator needs to progress through his arterial route safely and efficiently.
022 The system shall receive requests for maintenance and construction vehicle signal priority. 04 The Maintenance and Construction Vehicle Operator needs to progress through his arterial route safely and efficiently.
023 The system shall communicate with passing vehicles to provide the current signal phase and timing information for all lanes and approaches at a signalized intersection. 04 The Maintenance and Construction Vehicle Operator needs to progress through his arterial route safely and efficiently.
024 The system shall send schedule deviation data and status of priority requests to the vehicle operator and provide the capability for the vehicle operator to control the priority system. 04 The Maintenance and Construction Vehicle Operator needs to progress through his arterial route safely and efficiently.
025 The system shall determine when special vehicles requesting preemption or priority at a signal are authorized to do so based on their digital credentials. 03 Traffic Management needs to communicate with field equipment to provide maintenance and construction vehicle signal priority commands to the intersection.
04 The Maintenance and Construction Vehicle Operator needs to progress through his arterial route safely and efficiently.
026 The system shall collect current signal phase and timing data from the traffic signal controller. 03 Traffic Management needs to communicate with field equipment to provide maintenance and construction vehicle signal priority commands to the intersection.
027 The system shall receive signal priority requests from maintenance and construction vehicles and forward to the traffic signal controller. 04 The Maintenance and Construction Vehicle Operator needs to progress through his arterial route safely and efficiently.
028 The system shall exchange location and motion information with roadside equipment and nearby vehicles. 04 The Maintenance and Construction Vehicle Operator needs to progress through his arterial route safely and efficiently.
029 The system 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. 04 The Maintenance and Construction Vehicle Operator needs to progress through his arterial route safely and efficiently.