PS08: Roadway Service Patrols
This service package supports roadway service patrol vehicles that monitor roads and aid motorists, offering rapid response to minor incidents (flat tire, accidents, out of gas) to minimize disruption to the traffic stream. If problems are detected, the roadway service patrol vehicles will provide assistance to the motorist (e.g., push a vehicle to the shoulder or median). The service package monitors service patrol vehicle locations and supports vehicle dispatch to identified incident locations. Incident information collected by the service patrol is shared with traffic, maintenance and construction, and traveler information systems.
Relevant Regions: Australia, Canada, European Union, and United States
- Enterprise
- Functional
- Physical
- Goals and Objectives
- Needs and Requirements
- Sources
- Security
- Standards
- System Requirements
Enterprise
Development Stage Roles and Relationships
Installation Stage Roles and Relationships
Operations and Maintenance Stage Roles and Relationships
(hide)
Source | Destination | Role/Relationship |
---|---|---|
Emergency Management Center Maintainer | Emergency Management Center | Maintains |
Emergency Management Center Manager | Emergency Management Center | Manages |
Emergency Management Center Owner | Emergency Management Center Maintainer | System Maintenance Agreement |
Emergency Management Center Owner | Emergency Management Center Manager | Operations Agreement |
Emergency Management Center Supplier | Emergency Management Center Owner | Warranty |
Emergency Personnel | Emergency Vehicle OBE | Operates |
Emergency Vehicle OBE Maintainer | Emergency Vehicle OBE | Maintains |
Emergency Vehicle OBE Manager | Emergency Personnel | System Usage Agreement |
Emergency Vehicle OBE Manager | Emergency Vehicle OBE | Manages |
Emergency Vehicle OBE Owner | Emergency Vehicle OBE Maintainer | System Maintenance Agreement |
Emergency Vehicle OBE Owner | Emergency Vehicle OBE Manager | Operations Agreement |
Emergency Vehicle OBE Owner | Traffic Management Center Maintainer | Maintenance Data Exchange Agreement |
Emergency Vehicle OBE Owner | Traffic Management Center Owner | Expectation of Data Provision |
Emergency Vehicle OBE Owner | Traffic Management Center User | Service Usage Agreement |
Emergency Vehicle OBE Owner | Traffic Operations Personnel | Application Usage Agreement |
Emergency Vehicle OBE Owner | Traffic Operations Personnel | Vehicle Operating Agreement |
Emergency Vehicle OBE Supplier | Emergency Vehicle OBE Owner | Warranty |
Maint and Constr Management Center Maintainer | Maint and Constr Management Center | Maintains |
Maint and Constr Management Center Manager | Maint and Constr Management Center | Manages |
Maint and Constr Management Center Owner | Maint and Constr Management Center Maintainer | System Maintenance Agreement |
Maint and Constr Management Center Owner | Maint and Constr Management Center Manager | Operations Agreement |
Maint and Constr Management Center Supplier | Maint and Constr Management Center Owner | Warranty |
Traffic Management Center Maintainer | Traffic Management Center | Maintains |
Traffic Management Center Manager | Traffic Management Center | Manages |
Traffic Management Center Manager | Traffic Operations Personnel | System Usage Agreement |
Traffic Management Center Owner | Emergency Management Center Maintainer | Maintenance Data Exchange Agreement |
Traffic Management Center Owner | Emergency Management Center Owner | Information Provision Agreement |
Traffic Management Center Owner | Emergency Management Center User | Service Usage Agreement |
Traffic Management Center Owner | Emergency Personnel | Application Usage Agreement |
Traffic Management Center Owner | Emergency Vehicle OBE Maintainer | Maintenance Data Exchange Agreement |
Traffic Management Center Owner | Emergency Vehicle OBE Owner | Information Provision Agreement |
Traffic Management Center Owner | Emergency Vehicle OBE User | Service Usage Agreement |
Traffic Management Center Owner | Maint and Constr Management Center Maintainer | Maintenance Data Exchange Agreement |
Traffic Management Center Owner | Maint and Constr Management Center Owner | Information Provision Agreement |
Traffic Management Center Owner | Maint and Constr Management Center User | Service Usage Agreement |
Traffic Management Center Owner | Traffic Management Center Maintainer | System Maintenance Agreement |
Traffic Management Center Owner | Traffic Management Center Manager | Operations Agreement |
Traffic Management Center Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
Traffic Management Center Owner | Transportation Information Center Owner | Information Provision Agreement |
Traffic Management Center Owner | Transportation Information Center User | Service Usage Agreement |
Traffic Management Center Supplier | Traffic Management Center Owner | Warranty |
Traffic Operations Personnel | Traffic Management Center | Operates |
Transportation Information Center Maintainer | Transportation Information Center | Maintains |
Transportation Information Center Manager | Transportation Information Center | Manages |
Transportation Information Center Owner | Transportation Information Center Maintainer | System Maintenance Agreement |
Transportation Information Center Owner | Transportation Information Center Manager | Operations Agreement |
Transportation Information Center Supplier | Transportation Information Center Owner | Warranty |
Functional
This service package includes the following Functional View PSpecs:
Physical
The physical diagram can be viewed in SVG or PNG format and the current format is SVG.SVG Diagram
PNG Diagram
Includes Physical Objects:
Physical Object | Class | Description |
---|---|---|
Emergency Management Center | Center | The 'Emergency Management Center' represents systems that support incident management, disaster response and evacuation, security monitoring, and other security and public safety-oriented ITS applications. It includes the functions associated with fixed and mobile public safety communications centers including public safety call taker and dispatch centers operated by police (including transit police), fire, and emergency medical services. It includes the functions associated with Emergency Operations Centers that are activated at local, regional, state, and federal levels for emergencies and the portable and transportable systems that support Incident Command System operations at an incident. This Center also represents systems associated with towing and recovery, freeway service patrols, HAZMAT response teams, and mayday service providers. It manages sensor and surveillance equipment used to enhance transportation security of the roadway infrastructure (including bridges, tunnels, interchanges, and other key roadway segments) and the public transportation system (including transit vehicles, public areas such as transit stops and stations, facilities such as transit yards, and transit infrastructure such as rail, bridges, tunnels, or bus guideways). It provides security/surveillance services to improve traveler security in public areas not a part of the public transportation system. It monitors alerts, advisories, and other threat information and prepares for and responds to identified emergencies. It coordinates emergency response involving multiple agencies with peer centers. It stores, coordinates, and utilizes emergency response and evacuation plans to facilitate this coordinated response. Emergency situation information including damage assessments, response status, evacuation information, and resource information are shared The Emergency Management Center also provides a focal point for coordination of the emergency and evacuation information that is provided to the traveling public, including wide-area alerts when immediate public notification is warranted. It tracks and manages emergency vehicle fleets using real-time road network status and routing information from the other centers to aid in selecting the emergency vehicle(s) and routes, and works with other relevant centers to tailor traffic control to support emergency vehicle ingress and egress, implementation of special traffic restrictions and closures, evacuation traffic control plans, and other special strategies that adapt the transportation system to better meet the unique demands of an emergency. |
Emergency Personnel | Vehicle | 'Emergency Personnel' represents personnel that are responsible for police, fire, emergency medical services, towing, service patrols, and other special response team (e.g., hazardous material clean-up) activities at an incident site. These personnel are associated with the Emergency Vehicle during dispatch to the incident site, but often work independently of the Emergency Vehicle while providing their incident response services. |
Emergency Vehicle OBE | Vehicle | The 'Emergency Vehicle On-Board Equipment' (OBE) resides in an emergency vehicle and provides the processing, storage, and communications functions that support public safety-related connected vehicle applications. It represents a range of vehicles including those operated by police, fire, and emergency medical services. In addition, it represents other incident response vehicles including towing and recovery vehicles and freeway service patrols. It includes two-way communications to support coordinated response to emergencies. A separate 'Vehicle OBE' physical object supports the general vehicle safety and driver information capabilities that apply to all vehicles, including emergency vehicles. The Emergency Vehicle OBE supplements these general capabilities with capabilities that are specific to emergency vehicles. |
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. |
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. |
Traffic Operations Personnel | Center | 'Traffic Operations Personnel' represents the people that operate a traffic management center. These personnel interact with traffic control systems, traffic surveillance systems, incident management systems, work zone management systems, and travel demand 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. |
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 |
---|---|---|
EV Service Patrol Vehicle Operations | 'EV Service Patrol Vehicle Operations' provides on-board processing and communications to service patrol vehicles that reduce response times and improve safety of responding personnel. It supports service patrol vehicle dispatch and provides incident information back to the dispatching center. | Emergency Vehicle OBE |
TMC Service Patrol Management | 'TMC Service Patrol Management' supports dispatch and communication with service patrol vehicles that monitor roads to aid motorists, offering rapid response to minor incidents. | Traffic Management Center |
Includes Information Flows:
Information Flow | Description |
---|---|
emergency personnel information presentation | Presentation of information to emergency personnel in the field including dispatch information, incident information, current road network conditions, device status, and other supporting information. |
emergency personnel input | User input from emergency personnel in the field including dispatch coordination, incident status information, and remote device control requests. |
emergency vehicle tracking data | The current location and operating status of the emergency vehicle. |
incident information | Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system. |
incident information for public | Report of current desensitized incident information prepared for public dissemination. |
service patrol dispatch request | Service patrol dispatch instructions including incident location and available information concerning the incident. |
service patrol dispatch response | Request for additional dispatch information and provision of en route status. |
service patrol incident status | Information gathered at the incident site by a service patrol vehicle that more completely characterizes the incident, the services provided, and clearance status. |
traffic operator data | Presentation of traffic operations data to the operator including traffic conditions, current operating status of field equipment, maintenance activity status, incident status, video images, security alerts, emergency response plan updates and other information. This data keeps the operator appraised of current road network status, provides feedback to the operator as traffic control actions are implemented, provides transportation security inputs, and supports review of historical data and preparation for future traffic operations activities. |
traffic operator input | User input from traffic operations personnel including requests for information, configuration changes, commands to adjust current traffic control strategies (e.g., adjust signal timing plans, change DMS messages), and other traffic operations data entry. |
Goals and Objectives
Associated Planning Factors and Goals
Planning Factor | Goal |
---|---|
A. Support the economic vitality of the metropolitan area, especially by enabling global competitiveness, productivity, and efficiency; | Improve freight network |
B. Increase the safety of the transportation system for motorized and nonmotorized users; | Reduce fatalities and injuries |
C. Increase the security of the transportation system for motorized and nonmotorized users; | Improve security |
D. Increase the accessibility and mobility of people and for freight; | Reduce congestion |
F. Enhance the integration and connectivity of the transportation system, across and between modes, for people and freight; | Enhance integration and connectivity |
G. Promote efficient system management and operation; | Improve efficiency |
I. Improve the resiliency and reliability of the transportation system and reduce or mitigate stormwater impacts of surface transportation; | Improve resiliency and reliability |
Associated Objective Categories
Associated Objectives and Performance Measures
Needs and Requirements
Need | Functional Object | Requirement | ||
---|---|---|---|---|
01 | Roadway Service Patrol Operations need to be able to monitor service patrol vehicle locations and dispatch service patrol vehicles to identified incident locations. | EV Service Patrol Vehicle Operations | 01 | The service patrol vehicle shall track its current location. |
02 | The service patrol vehicle shall send the vehicle's location and operational data to the center for dispatch. | |||
03 | The service patrol vehicle shall receive incident details and a suggested route when dispatched to a scene. | |||
TMC Service Patrol Management | 01 | The center shall dispatch roadway service patrol vehicles to identified incident locations. | ||
02 | The center shall store the current status of all service patrol vehicles available for dispatch and those that have been dispatched. | |||
04 | The center shall track the location and status of service patrol vehicles. | |||
02 | Roadway Service Patrol Operations need to be able to monitor roads and aid motorists, offering rapid response to minor incidents (flat tire, accidents, out of gas) in order to minimize disruption to the traffic stream. | EV Service Patrol Vehicle Operations | 04 | The service patrol vehicle shall send the current en route status (including estimated time of arrival) and requests for emergency dispatch updates. |
05 | The service patrol vehicle shall provide the personnel on-board with dispatch information, including incident type and location, and forward an acknowledgment from personnel to the center that the vehicle is on its way to the incident scene. | |||
07 | The roadway service patrols vehicle shall monitor roads and aid motorists, offering rapid response to minor incidents (flat tire, accidents, out of gas). | |||
03 | Roadway Service Patrol Operations need to be able to share incident information collected by the service patrol with traffic, maintenance and construction, and traveler information systems. | EV Service Patrol Vehicle Operations | 06 | The service patrol vehicle shall update the center with status of an incident response including the nature of the incident, e.g. flat tire, gas, minor accident. |
TMC Service Patrol Management | 03 | The center shall share incident information collected by the service patrol with traffic, maintenance and construction, and traveler information centers for incident management, incident notification to travelers, and incident cleanup. |
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 |
Emergency Management Center | High | High | Moderate | Class 4 |
Emergency Vehicle OBE | Moderate | Moderate | Moderate | Class 2 |
Maint and Constr Management Center | High | High | Moderate | Class 4 |
Traffic Management Center | High | Moderate | Moderate | Class 4 |
Transportation Information Center | Low | 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 | |||
Emergency Personnel | Emergency Vehicle OBE | emergency personnel input | Moderate | Moderate | Moderate |
Some of the information, such as incident status information, is sensitive, and should be protected. | The system must know that these requests came from actual Emergency Personal. Additionally, incorrect information here may lead to the system responding incorrectly to the incident | These messages are important for the system to operate properly. Additionally, the system must know if messages are not received so that it can act accordingly. | |||
Emergency Vehicle OBE | Emergency Personnel | emergency personnel information presentation | Moderate | Moderate | Moderate |
Some of this information, such as incident information, is sensitive and should be protected. | This information could affect how the Emergency Personnel respond to the event, and should be as accurate as possible. | This information needs to be available for the Emergency Personnel in order for them to respond accurately to the system. If they do not acknowledge this information, dispatch needs to know, so they can attempt to contact the Emergency Personnel via another channel, such as radio. | |||
Emergency Vehicle OBE | Traffic Management Center | emergency vehicle tracking data | Moderate | Moderate | Moderate |
Emergency Vehicles give obvious visual and audio indicators about their location and operating status. Knowing the location of every single emergency vehicle within a city could be extremely useful information to a criminal. Additionally, although this is observable data, it is transmitted on a regional level, which means that someone who is able to intercept it would be able to read the location of all emergency vehicles, not just the ones they could directly observed. A sufficiently motivated criminal can however get this information by other means. | Incorrect data here could lead to incorrect decisions being made about the closure of lanes, or incorrect information being shared with the emergency vehicles. There should be other indicators that would contradict incorrect information transmitted here. | This information may be used to determine which emergency vehicle is dispatched, and having this information available could lead to a quicker response from the emergency vehicle. However, the system would still be able to operate properly if only most messages make it through. | |||
Emergency Vehicle OBE | Traffic Management Center | service patrol dispatch response | Moderate | Moderate | Moderate |
Suggests routing of the receiving emergency vehicle and severity of the incident, which could be used by an attacker who wished to harm that vehicle or harm something/someone in an area the vehicle vacates. | Inaccurate or corrupted information here could lead to an inappropriate response, compromising the purpose of the request. | Unavailability of this flow will negatively affect the response to the incident, locally compromising mobility and possibly safety. | |||
Emergency Vehicle OBE | Traffic Management Center | service patrol incident status | Moderate | Moderate | Moderate |
Specifically describes the conditions of an incident, which may include PII-related information, or at least information of a sensitive nature for severe incidents, which should be protected from viewing to protect the privacy of those involved. | Inaccurate or corrupted or unavailable information here could lead to an inappropriate incident management action, which while not likely to impact safety-related actions (which would be carried out by Emergency-related actors), but which could impact mobility. | Inaccurate or corrupted or unavailable information here could lead to an inappropriate incident management action, which while not likely to impact safety-related actions (which would be carried out by Emergency-related actors), but which could impact mobility. | |||
Traffic Management Center | Emergency Management Center | incident information | High | Moderate | Moderate |
This data contains all of the information regarding the incident. This could include personal information regarding persons involved in the incident. It could also include sensitive information regarding special events or closures. | Minor discrepancies in this data should not have a catastrophic effect, but it should be reasonably controlled and accurate. | A few missed messages should not have a significant effect. However, most messages should make it through and the TMC should be able to know if the EMC has received a message. | |||
Traffic Management Center | Emergency Vehicle OBE | service patrol dispatch request | Moderate | Moderate | Moderate |
Suggests routing of the receiving emergency vehicle and severity of the incident, which could be used by an attacker who wished to harm that vehicle or harm something/someone in an area the vehicle vacates. | Inaccurate or corrupted information here could lead to an inappropriate response, compromising the purpose of the request. | Unavailability of this flow will negatively affect the response to the incident, locally compromising mobility and possibly safety. | |||
Traffic Management Center | Maint and Constr Management Center | incident information | High | Moderate | Moderate |
This data contains all of the information regarding the incident. This could include personal information regarding persons involved in the incident. It could also include sensitive information regarding special events or closures. | Minor discrepancies in this data should not have a catastrophic effect, but it should be reasonably controlled and accurate. | A few missed messages should not have a significant effect. However, most messages should make it through and the TMC should be able to know if the EMC has received a message. | |||
Traffic Management Center | Traffic Operations Personnel | traffic operator data | Moderate | Moderate | Moderate |
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. | 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. | |||
Traffic Management Center | Transportation Information Center | incident information for public | Low | Moderate | Moderate |
Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. | Incident information will be used to make routing and other travel decisions. Corrupted information may have a significant impac t on travel plans and/or road network conditions. | Significant numbers of travelers serve as end users for the information in this flow; lack of availability has a significant effect on their travel decisions. | |||
Traffic Operations Personnel | Traffic Management Center | traffic operator input | Moderate | High | High |
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. | 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. |
Standards
Currently, there are no standards associated with the physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages.
System Requirements
System Requirement | Need | ||
---|---|---|---|
001 | The system shall dispatch roadway service patrol vehicles to identified incident locations. | 01 | Roadway Service Patrol Operations need to be able to monitor service patrol vehicle locations and dispatch service patrol vehicles to identified incident locations. |
002 | The system shall store the current status of all service patrol vehicles available for dispatch and those that have been dispatched. | 01 | Roadway Service Patrol Operations need to be able to monitor service patrol vehicle locations and dispatch service patrol vehicles to identified incident locations. |
003 | The system shall share incident information collected by the service patrol with traffic, maintenance and construction, and traveler information centers for incident management, incident notification to travelers, and incident cleanup. | 03 | Roadway Service Patrol Operations need to be able to share incident information collected by the service patrol with traffic, maintenance and construction, and traveler information systems. |
004 | The system shall track the location and status of service patrol vehicles. | 01 | Roadway Service Patrol Operations need to be able to monitor service patrol vehicle locations and dispatch service patrol vehicles to identified incident locations. |
005 | The system shall track its current location. | 01 | Roadway Service Patrol Operations need to be able to monitor service patrol vehicle locations and dispatch service patrol vehicles to identified incident locations. |
006 | The system shall send the vehicle's location and operational data to the center for dispatch. | 01 | Roadway Service Patrol Operations need to be able to monitor service patrol vehicle locations and dispatch service patrol vehicles to identified incident locations. |
007 | The system shall update the center with status of an incident response including the nature of the incident, e.g. flat tire, gas, minor accident. | 03 | Roadway Service Patrol Operations need to be able to share incident information collected by the service patrol with traffic, maintenance and construction, and traveler information systems. |
008 | The system shall monitor roads and aid motorists, offering rapid response to minor incidents (flat tire, accidents, out of gas). | 02 | Roadway Service Patrol Operations need to be able to monitor roads and aid motorists, offering rapid response to minor incidents (flat tire, accidents, out of gas) in order to minimize disruption to the traffic stream. |