MC12: One-Way Convoy Driving
This service package enables convoys through areas restricted to one-way travel by maintenance and construction, heavy snowfalls, or other obstructions. Typically these are long stretches of roadway that require escort due to excessive speed concerns, crossroads, lane changes, equipment crossings, or adverse conditions. Maintenance vehicles assemble groups of vehicles and serve as pilot vehicles (lead and optional chase vehicles) for the convoy. Notification of convoy operations occurs through traditional traveler information methods.
Origin: European Union
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 |
---|
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 |
---|---|---|
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. |
Light Vehicle Driver | Vehicle | The 'Light Vehicle Driver' represents the person that operates a light vehicle on the roadway. This physical object covers the interactions that are specific to light, passenger vehicles. See also the 'Driver' physical object that covers interactions that are shared by operators of light, transit, commercial, and emergency vehicles where the interactions are not particular to the type of vehicle. |
Light Vehicle OBE | Vehicle | The 'Light Vehicle OBE' includes traveler-oriented capabilities that apply to passenger cars, trucks, and motorcycles that are used for personal travel. The rules vary by jurisdiction, but generally light vehicles are restricted in their weight and the maximum number of passengers they can carry. In ARC-IT, the Light Vehicle OBE represents vehicles that are operated as personal vehicles that are not part of a vehicle fleet and are not used commercially; thus, the choice between the various vehicle subsystems should be based more on how the vehicle is used than how much the vehicle weighs. See also the 'Vehicle' subsystem that includes the general safety and information services that apply to all types of vehicles, including light 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. |
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. |
Other MCV OBEs | Vehicle | This represents on-board equipment on other maintenance and construction vehicles. It provides a source and destination for ITS information transfers between maintenance and construction vehicles. These information transfers allow vehicle operational status, environmental information, and work zone intrusion warnings or alarms to be shared between vehicles. |
Personal Information Device | Personal | The 'Personal Information Device' provides the capability for travelers to receive formatted traveler information wherever they are. Capabilities include traveler information, trip planning, and route guidance. Frequently a smart phone, the Personal Information Device provides travelers with the capability to receive route planning and other personally focused transportation services from the infrastructure in the field, at home, at work, or while en-route. Personal Information Devices may operate independently or may be linked with vehicle on-board equipment. This subsystem also supports safety related services with the capability to broadcast safety messages and initiate a distress signal or request for help. |
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 |
---|---|---|
Light Vehicle Interactive Traveler Information | 'Light Vehicle Interactive Traveler Information' provides drivers with personalized traveler information including traffic and road conditions, transit information, maintenance and construction information, multimodal information, event information, and weather information. The provided information is tailored based on driver requests. Both one-time requests for information and on-going information streams based on a submitted traveler profile and preferences are supported. | Light Vehicle OBE |
Light Vehicle Traveler Information Reception | 'Light Vehicle Traveler Information Reception' provides the capability for drivers to receive general transportation information including traffic and road conditions, traffic regulations, incident information, maintenance and construction information, event information, transit information, parking information, weather information, and broadcast alerts. | Light Vehicle OBE |
MCM Reduced Speed Zone Warning | 'MCM Reduced Speed Zone Warning' supports remote control and monitoring of reduced speed zone warning roadside equipment. It provides posted speed limits and associated schedules and information about associated road configuration changes including lane merges and shifts. It monitors field equipment operation and reports current status to the operator. | Maint and Constr Management Center |
MCV Convoy Support | 'MCV Convoy Support' supports communications between a lead and a trailing maintenance vehicle when leading vehicle convoys through maintenance and construction areas or areas impacted by weather where travel is restricted to a single travel lane. Communications with a center are also available to allow the center to provide updates and monitor the convoy operations. | Maint and Constr Vehicle OBE |
Personal Interactive Traveler Information | 'Personal Interactive Traveler Information' provides traffic information, road conditions, transit information, yellow pages (traveler services) information, special event information, and other traveler information that is specifically tailored based on the traveler's request and/or previously submitted traveler profile information. It also supports interactive services that support enrollment, account management, and payments for transportation services. The interactive traveler information capability is provided by personal devices including personal computers and personal portable devices such as smart phones. | Personal Information Device |
Personal Traveler Information Reception | 'Personal Traveler Information Reception' receives formatted traffic advisories, road conditions, traffic regulations, transit information, broadcast alerts, and other general traveler information broadcasts and presents the information to the traveler. The traveler information broadcasts are received by personal devices including personal computers and personal portable devices such as smart phones. | Personal Information Device |
Roadway Reversible Lanes | 'Roadway Reversible Lanes' includes field elements that monitor and control reversible lane facilities. It includes the traffic sensors, surveillance equipment, lane control signals, physical lane access controls, and other field elements that manage traffic on these facilities. It provides current reversible lane facility status information and accepts requests and control commands from the controlling center. | ITS Roadway Equipment |
Roadway Speed Monitoring and Warning | 'Roadway Speed Monitoring and Warning' includes the field elements that monitor vehicle speeds. If the speed is determined to be excessive, an advisory or warning is displayed. Current environmental conditions and other factors that may reduce safe operating speeds may also be taken into account. The operational status (state of the device, configuration, and fault data) is provided to the center. This application can also provide an enforcement function, reporting speed violations to an enforcement agency. | ITS Roadway Equipment |
TIC Interactive Traveler Information | 'TIC Interactive Traveler Information' disseminates personalized traveler information including traffic and road conditions, transit information, parking information, maintenance and construction information, multimodal information, event information, and weather information. Tailored information is provided based on the traveler's request in this interactive service. | Transportation Information Center |
TIC Traffic Control Dissemination | 'TIC Traffic Control Dissemination' disseminates intersection status, lane control information, 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 Center(s) and disseminates the relevant information to vehicles and other mobile devices. | Transportation Information Center |
TMC Reversible Lane Management | 'TMC Reversible Lane Management' remotely monitors and controls reversible lanes. It provides an interface to reversible lane field equipment (traffic sensors, surveillance equipment, lane control signals, physical lane access controls, etc.) and to traffic operations personnel to support central monitoring and control of these facilities. | Traffic Management Center |
TMC Speed Warning | 'TMC Speed Warning' supports remote control and monitoring of reduced speed zone warning roadside equipment. It provides the location and extent of the reduced speed zone, the posted speed limit(s) with information about the applicability of the speed limit(s) (e.g., time of day, day of week, seasonality, relevant vehicle types) and information about associated road configuration changes including lane merges and shifts. It monitors field equipment operation and reports current status to the operator. | Traffic Management Center |
Includes Information Flows:
Information Flow | Description |
---|
Goals and Objectives
Associated Planning Factors and Goals
Planning Factor | Goal |
---|
Associated Objective Categories
Objective Category |
---|
Associated Objectives and Performance Measures
Objective | Performance Measure |
---|
Needs and Requirements
Need | Functional Object | Requirement |
---|
Related Sources
- 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 |
ITS Roadway Equipment | Moderate | Moderate | Moderate | Class 2 |
Light Vehicle OBE | Moderate | Moderate | Moderate | Class 2 |
Maint and Constr Management Center | Moderate | Moderate | Moderate | Class 2 |
Maint and Constr Vehicle OBE | Moderate | Moderate | Moderate | Class 2 |
Other MCV OBEs | Low | Moderate | Low | Class 1 |
Personal Information Device | Moderate | Moderate | Moderate | Class 2 |
Traffic Management Center | Moderate | High | Moderate | Class 3 |
Transportation Information Center | Moderate | Moderate | Moderate | Class 2 |
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 | |||
ITS Roadway Equipment | Light Vehicle Driver | 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 | Maint and Constr Management Center | roadway dynamic signage status | Moderate | Moderate | Moderate |
Device status information should not be available, as those with criminal intent may use this information toward their own ends. | Data is intended to feed dissemination channels, either C-ITS messages or DMS or other channels, so it should generally be correct as it is distributed widely and any forgery or corrupted data will have widespread impact. | Failure of this flow affects traveler information dissemination, the importance of which varies with the data contained in the flow and the scenario. Could be LOW in many instances. | |||
ITS Roadway Equipment | Traffic Management Center | reversible lane status | Moderate | Moderate | Moderate |
May contain surveillance data; if that data includes license plates or other imagery, observation by a third party should be discouraged at this point (public camera data may be republished under other flows, but as chosen by the operator). Without such personally-focused surveillance data, this may be LOW. | Since this reports the status of reversible controls, any corruption or modification could have a catastrophic impact (if the center though the lanes were open in the opposite direction and allowed head-on traffic into the lanes). However, any such reversing should be accompanied by verification, either by camera or direct visual inspection, justifying lowering this to MODERATE. | Reversible lane controls should always be accessible, however this status flow will be supported by another, generally visual confirmation. | |||
ITS Roadway Equipment | Traffic Management Center | roadway dynamic signage status | Moderate | Moderate | Moderate |
Device status information should not be available, as those with criminal intent may use this information toward their own ends. | Data is intended to feed dissemination channels, either C-ITS messages or DMS or other channels, so it should generally be correct as it is distributed widely and any forgery or corrupted data will have widespread impact. | Failure of this flow affects traveler information dissemination, the importance of which varies with the data contained in the flow and the scenario. Could be LOW in many instances. | |||
Light Vehicle Driver | Light Vehicle OBE | light vehicle driver input | Moderate | High | High |
Data included in this flow may include origin and destination information, which should be protected from other's viewing as it may compromise the driver's privacy. | Commands from from the driver to the vehicle must be correct or the vehicle may behave in an unpredictable and possibly unsafe manner | Commands must always be able to be given or the driver has no control. | |||
Light Vehicle OBE | Light Vehicle Driver | light vehicle driver updates | Not Applicable | Moderate | Moderate |
This data is informing the driver about the safety of a nearby area. It should not contain anything sensitive, and does not matter if another person can observe it. | This is the information that is presented to the driver. If they receive incorrect information, they may act in an unsafe manner. However, there are other indicators that would alert them to any hazards, such as an oncoming vehicle or crossing safety lights. | If this information is not made available to the driver, then the system has not operated correctly. | |||
Light Vehicle OBE | Transportation Information Center | traveler request | Moderate | Moderate | Moderate |
This is likely to include the traveler location and may include traveler identity as well. This PII could be used by an attacker to the detriment of the traveler. | Request needs to be correct, or the wrong data may be sent. | Interface needs to be available or users will find other sources that are reliable. | |||
Maint and Constr Management Center | ITS Roadway Equipment | roadway dynamic signage data | Moderate | Moderate | Moderate |
Device control information should not be available, as those with criminal intent may use this information toward their own ends. | Data is intended to feed dissemination channels, either C-ITS messages or DMS or other channels, so it should generally be correct as it is distributed widely and any forgery or corrupted data will have widespread impact. | Occasional outages of this flow will delay dissemination of the data to travelers (the eventual end user) which could have significant impacts on travel, both safety and mobility impacts. | |||
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 | field device coordination | Low | Moderate | Moderate |
There should be little harm to come from knowing who controls what field device in most instances. For security monitoring objects such as security cameras this might be MODERATE, but the flow is marked as low since it is unlikely that those kinds of objects have shared control. | If this flow is incorrect or manipulated then an unauthorized party may be able to gain control of a device, which can have significant effects. This is not a control flow however, so actual control is unlikely, thus MODERATE. | Depends on the sharing arrangement, but generally interfaces between centers should provide timely response to enable proper decision making and action. | |||
Maint and Constr Management Center | Transportation Information Center | lane closure information | Low | Moderate | Low |
Lane closure information is intended for broadcast and public consumption. | Data should be consistent with observed reality, so it should be protected appropriately, otherwisee users may lose confidence in and ignore this flow in the future. | While useful, this information is available through a variety of means. | |||
Maint and Constr Vehicle OBE | Maint and Constr Management Center | maint and constr dispatch status | 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 hostil 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 OBE | Other MCV OBEs | maint and constr vehicle status coordination | Low | Moderate | Low |
Unlikely that this includes any information that could be used against the originator. | Status information should be correct, but modification will cause only minor inconvenience. | Probably little impact if this flow is not operational. | |||
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. | |||
Other MCV OBEs | Maint and Constr Vehicle OBE | maint and constr vehicle status coordination | Low | Moderate | Low |
Unlikely that this includes any information that could be used against the originator. | Status information should be correct, but modification will cause only minor inconvenience. | Probably little impact if this flow is not operational. | |||
Personal Information Device | Transportation Information Center | traveler request | Moderate | Moderate | Moderate |
This is likely to include the traveler location and may include traveler identity as well. This PII could be used by an attacker to the detriment of the traveler. | Request needs to be correct, or the wrong data may be sent. | Interface needs to be available or users will find other sources that are reliable. | |||
Traffic Management Center | ITS Roadway Equipment | reversible lane control | 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. | Control flows, even for seemingly innocent devices, should have MODERATE integrity at minimum, just to guarantee that intended control messages are received. Incorrect, corrupted, intercepted and modified control messages can or will result in target field devices not behaving according to operator intent. The severity of this depends on the type of device, which is why some devices are set MODERATE and some HIGH. | Control flow availability is related to the criticality of being able to remotely control the device. For most devices, this is MODERATE. For purely passive devices with no incident relationship, this will be LOW. All devices should have default modes that enable them to operate without backhaul connectivity, so no device warrants a HIGH. | |||
Traffic Management Center | ITS Roadway Equipment | roadway dynamic signage data | Moderate | Moderate | Moderate |
Device control information should not be available, as those with criminal intent may use this information toward their own ends. | Data is intended to feed dissemination channels, either C-ITS messages or DMS or other channels, so it should generally be correct as it is distributed widely and any forgery or corrupted data will have widespread impact. | Occasional outages of this flow will delay dissemination of the data to travelers (the eventual end user) which could have significant impacts on travel, both safety and mobility impacts. | |||
Traffic Management Center | Maint and Constr Management Center | field device coordination | Low | Moderate | Moderate |
There should be little harm to come from knowing who controls what field device in most instances. For security monitoring objects such as security cameras this might be MODERATE, but the flow is marked as low since it is unlikely that those kinds of objects have shared control. | If this flow is incorrect or manipulated then an unauthorized party may be able to gain control of a device, which can have significant effects. This is not a control flow however, so actual control is unlikely, thus MODERATE. | Depends on the sharing arrangement, but generally interfaces between centers should provide timely response to enable proper decision making and action. | |||
Traffic Management Center | Transportation Information Center | lane closure information | Low | Moderate | Low |
Lane closure information is intended for broadcast and public consumption. | Data should be consistent with observed reality, so it should be protected appropriately, otherwisee users may lose confidence in and ignore this flow in the future. | While useful, this information is available through a variety of means. | |||
Transportation Information Center | Light Vehicle OBE | interactive traveler information | Moderate | Moderate | Low |
Personalized traveler information implies location, intent and/or future location, which if compromised could enable an attacker with leverage over the traveler. | Traveler information needs to be correct, as the traveler is using this to make transport-related decisions. | Travelers will rely on this data for transportation-related decisions. Depending on the number of options, possible choices and impacts, this may be MODERATE. | |||
Transportation Information Center | Light Vehicle OBE | lane closure information | Low | Moderate | Low |
Lane closure information is intended for broadcast and public consumption. | Data should be consistent with observed reality, so it should be protected appropriately, otherwisee users may lose confidence in and ignore this flow in the future. | While useful, this information is available through a variety of means. | |||
Transportation Information Center | Light Vehicle OBE | traveler alerts | Moderate | Moderate | Low |
May be personalized, and personalized traveler information implies location, intent and/or future location, which if compromised could enable an attacker with leverage over the traveler. | Traveler information needs to be correct, as the traveler is using this to make transport-related decisions. | Travelers will rely on this data for transportation-related decisions. Depending on the number of options, possible choices and impacts, this may be MODERATE. | |||
Transportation Information Center | Personal Information Device | interactive traveler information | Moderate | Moderate | Low |
Personalized traveler information implies location, intent and/or future location, which if compromised could enable an attacker with leverage over the traveler. | Traveler information needs to be correct, as the traveler is using this to make transport-related decisions. | Travelers will rely on this data for transportation-related decisions. Depending on the number of options, possible choices and impacts, this may be MODERATE. | |||
Transportation Information Center | Personal Information Device | lane closure information | Low | Moderate | Low |
Lane closure information is intended for broadcast and public consumption. | Data should be consistent with observed reality, so it should be protected appropriately, otherwisee users may lose confidence in and ignore this flow in the future. | While useful, this information is available through a variety of means. | |||
Transportation Information Center | Personal Information Device | traveler alerts | Moderate | Moderate | Low |
May be personalized, and personalized traveler information implies location, intent and/or future location, which if compromised could enable an attacker with leverage over the traveler. | Traveler information needs to be correct, as the traveler is using this to make transport-related decisions. | Travelers will rely on this data for transportation-related decisions. Depending on the number of options, possible choices and impacts, this may be MODERATE. |
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.
Name | Title | Physical Object |
---|---|---|
ITE ATC | Advanced Transportation Controller | ITS Roadway Equipment |
ITE ATC API | Application Programming Interface Standard for the Advanced Transportation Controller | ITS Roadway Equipment |
ITE ATC ITS Cabinet | Intelligent Transportation System Standard Specification for Roadside Cabinets | ITS Roadway Equipment |
ITE ATC Model 2070 | Model 2070 Controller Standard | ITS Roadway Equipment |
NEMA TS 8 Cyber and Physical Security | Cyber and Physical Security for Intelligent Transportation Systems | ITS Roadway Equipment |
Maint and Constr Management Center | ||
Traffic Management Center | ||
NEMA TS2 Traffic Controller Assemblies | Traffic Controller Assemblies with NTCIP Requirements | ITS Roadway Equipment |
NEMA TS4 Hardware Standards for DMS | Hardware Standards for Dynamic Message Signs (DMS) With NTCIP Requirements | ITS Roadway Equipment |
System Requirements
No System Requirements |