< < VS16 : VS17 : VS18 > >

VS17: Management of Electronic Transport Regulations (METR)

The Management of Electronic Transport Regulations (METR) service package provides vehicles and other participants in the transportation environment with trustworthy, timely, authoritative, machine-interpretable, transport-related rules as established by relevant jurisdictional entities. METR defines means by which rules are securely translated into a standard electronic format and electronically signed, collected from various translators for a specific scope, and disseminated to vehicles and other users as necessary. As users become aware of the authenticated rules, they may provide feedback to help identify discrepancies.

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
Driver Vehicle OBE Operates
Map Update System Maintainer Map Update System Maintains
Map Update System Manager Map Update System Manages
Map Update System Owner Map Update System Maintainer System Maintenance Agreement
Map Update System Owner Map Update System Manager Operations Agreement
Map Update System Owner Personal Information Device Owner Information Provision Agreement
Map Update System Owner Vehicle OBE Owner Information Provision Agreement
Map Update System Supplier Map Update System Owner Warranty
Other Transportation Information Centers Maintainer Other Transportation Information Centers Maintains
Other Transportation Information Centers Manager Other Transportation Information Centers Manages
Other Transportation Information Centers Owner Other Transportation Information Centers Maintainer System Maintenance Agreement
Other Transportation Information Centers Owner Other Transportation Information Centers Manager Operations Agreement
Other Transportation Information Centers Owner Transportation Information Center Owner Information Exchange Agreement
Other Transportation Information Centers Supplier Other Transportation Information Centers Owner Warranty
Personal Information Device Maintainer Personal Information Device Maintains
Personal Information Device Manager Personal Information Device Manages
Personal Information Device Manager Traveler System Usage Agreement
Personal Information Device Owner Personal Information Device Maintainer System Maintenance Agreement
Personal Information Device Owner Personal Information Device Manager Operations Agreement
Personal Information Device Supplier Personal Information Device Owner Warranty
Traffic Management Center Maintainer Traffic Management Center Maintains
Traffic Management Center Manager Traffic Management Center Manages
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 Owner Information Provision Agreement
Traffic Management Center Supplier Traffic Management Center Owner Warranty
Traffic Regulatory Authority Center Maintainer Traffic Regulatory Authority Center Maintains
Traffic Regulatory Authority Center Manager Traffic Regulatory Authority Center Manages
Traffic Regulatory Authority Center Owner Map Update System Owner Information Provision Agreement
Traffic Regulatory Authority Center Owner Traffic Management Center Owner Information Provision Agreement
Traffic Regulatory Authority Center Owner Traffic Regulatory Authority Center Maintainer System Maintenance Agreement
Traffic Regulatory Authority Center Owner Traffic Regulatory Authority Center Manager Operations Agreement
Traffic Regulatory Authority Center Owner Transportation Information Center Owner Information Provision Agreement
Traffic Regulatory Authority Center Supplier Traffic Regulatory Authority Center Owner Warranty
Transportation Information Center Maintainer Transportation Information Center Maintains
Transportation Information Center Manager Transportation Information Center Manages
Transportation Information Center Owner Other Transportation Information Centers Owner Information Exchange Agreement
Transportation Information Center Owner Personal Information Device Owner Information Provision Agreement
Transportation Information Center Owner Transportation Information Center Maintainer System Maintenance Agreement
Transportation Information Center Owner Transportation Information Center Manager Operations Agreement
Transportation Information Center Owner Vehicle OBE Owner Information Provision Agreement
Transportation Information Center Supplier Transportation Information Center Owner Warranty
Traveler Personal Information Device Operates
Vehicle OBE Maintainer Vehicle OBE Maintains
Vehicle OBE Manager Driver System Usage Agreement
Vehicle OBE Manager Vehicle OBE Manages
Vehicle OBE Owner Vehicle OBE Maintainer System Maintenance Agreement
Vehicle OBE Owner Vehicle OBE Manager Operations Agreement
Vehicle OBE Supplier Vehicle OBE Owner Warranty

Functional

This service package includes the following Functional View PSpecs:

Physical Object Functional Object PSpec Number PSpec Name
ITS Roadway Equipment Roadway Field Device Support 9.2.3.6 Collect Field Equipment Status for Repair

Physical

The physical diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagrams: Part 1 Part 2 Part 3
PNG Diagrams: Part 1 Part 2 Part 3


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 that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. 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.
Driver Vehicle The 'Driver' represents the person that operates a vehicle on the roadway. Included are operators of private, transit, commercial, and emergency vehicles where the interactions are not particular to the type of vehicle (e.g., interactions supporting vehicle safety applications). The Driver originates driver requests and receives driver information that reflects the interactions which might be useful to all drivers, regardless of vehicle classification. Information and interactions which are unique to drivers of a specific vehicle type (e.g., fleet interactions with transit, commercial, or emergency vehicle drivers) are covered by separate objects.
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.
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 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.
METR Discrepancy Contact System Support The 'METR Discrepancy Contact System' represents any external system that a METR Regulation System might need to notify about the existence of a discrepancy report. For example, the original equipment manufacturer (OEM) for a vehicle model that repeatedly incorrectly reports discrepancies should be notified of the problem in its discrepancy reporting logic.
The MDCS may register its availability as a service, and its associated cyber location information, with the Object Registration and Discovery Service (ORDS).
METR Discrepancy Handling System Support The 'METR Discrepancy Handling System' receives reports of discrepancies in rules from METR User Systems. It will perform a numerical analysis of discrepancy count vs. time for any given rule, and when warranted, report to the METR Regulation Center those rules with sufficient discrepancy reports to justify further investigation. It is identified as a separate center to provide a level of anonymity for the user that reports the issue. The METR Discrepancy Handling Center may register its availability as a service, and its associated cyber location information, with the Object Registration and Discovery System (ORDS).
METR Distribution Center Center The 'METR Distribution Center' manages the collection and dissemination of rules received from one or more METR Regulation Centers and will verify that, holistically, the collective information is trustworthy for subsequent distribution to METR Users. It will accept and respond to requests for METR information from METR Consumer Systems using the provided request criteria.
The METR Distribution Center can be distinct from the METR Regulation Center because it will frequently need to collect rules from multiple METR Regulation Centers representing various rule-makers with different jurisdictional authority (e.g., traffic agency vs. environmental agency), in different areas (e.g., neighboring jurisdictional areas), and different levels of government (e.g., federal, state, and local). Likewise, there might be different METR Distribution Centers for different purposes (e.g., one that focuses on mainstream vehicles and another for commercial vehicles). The METR Distribution Center may register its availability as a service, and its associated cyber location information, with the Object Registration and Discovery System (ORDS).
METR Regulation System Support The 'METR Regulation System' creates and maintains electronic versions of transport rules for eventual consumption by traveler systems and other interested parties. Once approved, each rule is signed and traceable to a specific Rule-Maker. Depending on local policies and division of labor, the METR Regulation Center might need to coordinate with a METR Verification Center, a Maintenance and Construction Management System, and METR Discrepancy Handling Centers.
METR Rule Translator Agent Support The 'METR Rule Translator Agent' represents the person that enters the electronic version of the transport rule into the METR Regulation System. This role might be fulfilled by the Rule-Maker, but this will often be a different individual. The rule translator agent may enter this rule from scratch or may base the rule on information provided by discrepancy reports (e.g., especially rule discovery from authorized vehicles).
METR Rule-Maker Support The 'METR Rule-Maker' is the entity that has the legal authority to establish (i.e., sign) a rule and has the responsibility to digitally sign the approved METR rule. The digital signature provides traceability back to the specific individual with authority (i.e., if a jurisdictional entity has multiple rule-makers, they will each have a different signature). For laws (e.g., within the vehicle code), this might be a mayor, chairman of a city council, etc. For regulations, this might be the city traffic engineer. For an emergent rule in response to an incident, this might be a police officer or maintenance and construction personnel.
METR Verification System Support The 'METR Verification System' is responsible for providing independent verification of the rules defined by a METR Regulation System. It is represented as a distinct physical object since the verification is intended to be independently performed.
Non-METR Distribution System Support A 'Non-METR Distribution System' will accept METR information from a METR Regulation Center but will disseminate the received information to its users using a non-conformant interface.
Other METR Discrepancy Handling Systems Support Depending on deployments scenarios, a discrepancy report might be passed among multiple levels of Discrepancy Handling Systems. For example, a vehicle might be configured to report all its detected discrepancies to an OEM-operated Discrepancy Handling Center. This allows the OEM to become aware of potential problems with its discrepancy detection logic.
Once established thresholds are met, the OEM-operated Discrepancy Handling System might notify a Discrepancy Handling Center operated by a jurisdictional entity. The jurisdictional Discrepancy Handling System can then determine when the METR Regulation System is notified of the reported discrepancies.
Other METR Distribution Centers Center
Other METR Regulation Systems Support 'Other METR Regulation Systems' supports information exchange between METR Regulation Systems. A METR Regulation System may exchange METR information with other METR regulation systems to enhance the trustworthiness, both in terms of accuracy and completeness.
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.
Traveler Personal The 'Traveler' represents any individual who uses transportation services. The interfaces to the traveler provide general pre-trip and en-route information supporting trip planning, personal guidance, and requests for assistance in an emergency that are relevant to all transportation system users. It also represents users of a public transportation system and addresses interfaces these users have within a transit vehicle or at transit facilities such as roadside stops and transit centers.
Vehicle Vehicle This 'Vehicle' physical object is used to model core capabilities that are common to more than one type of Vehicle. It provides the vehicle-based general sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. Many of these capabilities (e.g., see the Vehicle Safety service packages) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle includes the common interfaces and functions that apply to all motorized vehicles. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Advanced sensors, processors, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. This physical object supports all six levels of driving automation as defined in SAE J3016. Initial collision avoidance functions provide 'vigilant co-pilot' driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain lane position and safe headways. In the most advanced implementations, this Physical Object supports full automation of all aspects of the driving task, aided by communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems.

Includes Functional Objects:

Functional Object Description Physical Object
EV METR Emergent Information Dissemination 'EV METR Emergent Information Dissemination' receives emergent rule information directly from collection function(s) and is responsible for notifying any nearby METR Consumer Systems (e.g., vehicles and PIDs) and the relevant Management Center (TMC/EMC/M&CMC) of the emergent rule status. Emergency Vehicle OBE
MCM METR Rule Installation 'MCMC Rule Installation' informs external entities of the installation and maintenance status of the traffic control devices that are associated with each transport rule. Maint and Constr Management Center
MCV METR Emergent Information Dissemination 'MCV METR Emergent Information Dissemination' receives emergent rule information directly from collection function(s) and is responsible for notifying any nearby METR Consumer Systems (e.g., vehicles and PIDs) and the relevant Management Center (TMC/EMC/M&CMC) of the emergent rule status. Maint and Constr Vehicle OBE
MDC METR Collection 'MDC METR Collection' receives METR information directly from METR translation function(s) and performs completeness and consistency checks to ensure each rule is fully defined and to identify any conflicts or discrepancies among the received rules. Any errors or warnings that are generated are sent to the provider of that content. The METR Collection function maintains and manages the consolidated information and provides the approved and signed content to METR dissemination functions. METR Distribution Center
MDC METR Discrepancy Management 'MDC METR Discrepancy Management' receives consolidated discrepancy reports from METR Discrepancy Handling Centers and respectively processes each constituent discrepancy. It also handles sending requests for discrepancy details on behalf of the Rule Translator Agent. METR Distribution Center
MDC METR Dissemination 'MDC METR Dissemination' receives rule information directly from collection function(s) and is responsible for notifying all requesting receivers (e.g., Vehicle OBEs, PIDs) of all rules that meet their relevancy criteria. METR Distribution Center
MDHS METR Collection 'MDHS METR Collection' receives METR information directly from METR translation function(s) and performs completeness and consistency checks to ensure each rule is fully defined and to identify any conflicts or discrepancies among the received rules. Any errors or warnings that are generated are sent to the provider of that content. The METR Collection function maintains and manages the consolidated information and provides the approved and signed content to METR dissemination functions. METR Discrepancy Handling System
MDHS METR Discrepancy Handling 'MDHS METR Discrepancy Handling' receives discrepancy reports from individuals (e.g., Vehicle OBE), anonymizes the information, tracks the number of reports received for each reported discrepancy, and provides the consolidated information to the appropriate METR Regulation Center for verification. As directed by the METR Regulation Center, the METR Discrepancy Handling function suppresses the delivery of consolidated discrepancy reports. METR Discrepancy Handling System
MRS METR Collection 'MRS METR Collection' receives METR information directly from METR translation function(s) and performs completeness and consistency checks to ensure each rule is fully defined and to identify any conflicts or discrepancies among the received rules. Any errors or warnings that are generated are sent to the provider of that content. The METR Collection function maintains and manages the consolidated information and provides the approved and signed content to METR dissemination functions. METR Regulation System
MRS METR Discovered Rule Management 'MRS METR Discovered Rule Management' is responsible for handling consolidated discrepancy reports from authorized vehicles. While similar to METR Discrepancy Management, the discovered rules focus on reporting existing traffic control devices without corresponding METR rules and are known to be from authorized vehicles with more trustworthy sensors (e.g., which should provide greater accuracy in positioning of rules). METR Regulation System
MRS METR Discrepancy Management 'MRS METR Discrepancy Management' receives consolidated discrepancy reports from METR Discrepancy Handling Centers and respectively processes each constituent discrepancy. It also handles sending requests for discrepancy details on behalf of the Rule Translator Agent. METR Regulation System
MRS METR Information Approval 'MRS METR Information Approval presents all METR information to the Rule-Maker for approval and digital signing before being made available for distribution. Optionally, based on jurisdictional policy, it will send the METR rules to the METR Verification Centre for independent verification prior to seeking the Rule-Maker's approval. METR Regulation System
MRS METR Translation 'MRS METR Translation' accepts inputs from Rule Translator Agents regarding pre-announced or emergent rules and converts the information into the structured, electronic METR format for provision to the METR Information Approval function. 'METR Translation' also accepts inputs from the METR Discrepancy Management and METR Discovered Rule Management functions to assist in the creation of the structured, electronic METR format. It also performs completeness and consistency checks to ensure the METR information is fully defined with no known conflicts or discrepancies with other known METR information. METR Regulation System
MVS Independent METR Verification 'MVS Independent METR Verification' receives electronic rules from external translation functions and verifies that they properly reflect the associated legal rule. If the rules agree, this function signs and returns the rule; otherwise, the function coordinates with the submitting center to resolve the interpretation issue. METR Verification System
Personal METR Discrepancy Reporting 'Personal METR Discrepancy Reporting' receives notifications of discrepancies from the interpretation function, formats the information into a METR discrepancy report, and manages the logging of the report and delivery of the report to the METR Discrepancy Handling Center. Personal Information Device
Personal METR Interpretation 'Personal METR Interpretation' combines the currently relevant rules from METR with supporting data (e.g., from on-board sensors, from V2X exchanges) to develop a complete picture of the rules that are currently active. The function also performs completeness and consistency checks to ensure each rule is fully defined and to identify any conflicts or discrepancies among the received rules Any discrepancies detected in this process (e.g., physical sign different from electronic rule) are forwarded to the discrepancy reporter function. Personal Information Device
Personal METR Reception 'Personal METR Reception' requests and obtains METR information from dissemination function(s) and provides access to this information in a local data store. The information requested is based on criteria provided by the interpretation function. The consolidated METR information is made available to the interpretation function. Personal Information Device
Roadway Field Device Support 'Roadway Field Device Support' monitors the operational status of field devices and detects and reports fault conditions. Consolidated operational status (device status, configuration, and fault information) are reported for resolution and repair. A local interface is provided to field personnel for local monitoring and diagnostics, supporting field maintenance, upgrade, repair, and replacement of field devices. ITS Roadway Equipment
RSE METR Emergent Information Dissemination 'RSE METR Emergent Information Dissemination' receives emergent rule information directly from collection function(s) and is responsible for notifying any nearby METR Consumer Systems (e.g., vehicles and PIDs) and the relevant Management Center (TMC/EMC/M&CMC) of the emergent rule status. Connected Vehicle Roadside Equipment
Vehicle METR Discrepancy Reporting 'Vehicle METR Discrepancy Reporting' receives notifications of discrepancies from the interpretation function, formats the information into a METR discrepancy report, and manages the logging of the report and delivery of the report to the METR Discrepancy Handling Center. Vehicle
Vehicle METR Interpretation 'Vehicle METR Interpretation' combines the currently relevant rules from METR with supporting data (e.g., from on-board sensors, from V2X exchanges) to develop a complete picture of the rules that are currently active. The function also performs completeness and consistency checks to ensure each rule is fully defined and to identify any conflicts or discrepancies among the received rules Any discrepancies detected in this process (e.g., physical sign different from electronic rule) are forwarded to the discrepancy reporter function. Vehicle
Vehicle METR Reception 'Vehicle METR Reception' requests and obtains METR information from dissemination function(s) and provides access to this information in a local data store. The information requested is based on criteria provided by the interpretation function. The consolidated METR information is made available to the interpretation function. Vehicle

Includes Information Flows:

Information Flow Description
driver input Driver input to the vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands.
driver updates Information provided to the driver including visual displays, audible information and warnings, and haptic feedback. The updates inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment.
traveler input User input from a traveler to summon assistance, request travel information, make a reservation, or request any other traveler service.
traveler interface updates Visual or audio information (e.g., routes, messages, guidance, emergency information) that is provided to the traveler.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor Goal
B. Increase the safety of the transportation system for motorized and nonmotorized users; Reduce fatalities and injuries

Associated Objective Categories

Objective Category
Safety: Vehicle Crashes and Fatalities

Associated Objectives and Performance Measures

Objective Performance Measure
Reduce crashes at intersections Number of crashes and fatalities at signalized intersections
Reduce crashes at intersections Number of crashes and fatalities at unsignalized intersections
Reduce crashes at intersections Number of crashes and fatalities related to red-light running
Reduce crashes at railroad crossings Number of crashes and fatalities at railroad crossings
Reduce crashes due to driver errors and limitations Number of crashes and fatalities related to driver inattention and distraction
Reduce crashes due to driver errors and limitations Number of crashes and fatalities related to driving while intoxicated
Reduce crashes due to red-light running Number of crashes and fatalities related to red-light running
Reduce crashes due to road weather conditions Number of crashes and fatalities related to weather conditions
Reduce crashes due to unexpected congestion Number of crashes and fatalities related to unexpected congestion
Reduce crashes due to unsafe drivers, vehicles and cargo on the transportation system Number of crashes and fatalities due to commercial vehicle safety violations
Reduce lane departure crashes Number of crashes and fatalities related to inappropriate lane departure, crossing or merging
Reduce secondary crashes Number of secondary crashes
Reduce speed differential Number of crashes and fatalities related to excessive speeding
Reduce speed differential Number of speed violations
Reduce the number of fatalities in crashes involving a driver or motorcycle operator with a BAC of.08 and above by X percent by Y year. Number of fatalities in crashes involving a driver or motorcycle operator with a BAC of.08 and above
Reduce the number of motorcyclist fatalities by X percent by year Y. Number of motorcyclist fatalities
Reduce the number of pedestrian fatalities by X percent by year Y. Number of pedestrian fatalities
Reduce the number of speeding-related fatalities by X percent by year Y. Number of speeding-related fatalities
Reduce the rate fatalities in the region by X percent by year Y. Rate of fatalities (rate per vehicle miles travelled (VMT))
Reduce the rate of severe injuries in the region by X percent by year Y. Rate of serious injuries (rate per VMT)
Reduce the total number of crashes in the region by X percent by year Y. Total crashes per X VMT.
Reduce the total number of crashes involving bicyclists and pedestrians in the region by X percent by year Y. Total crashes involving bicycles.
Reduce the total number of crashes involving bicyclists and pedestrians in the region by X percent by year Y. Total crashes involving pedestrians.
Reduce the total number of fatalities and severe injuries in the region by X percent by year Y. Total fatalities per X VMT.
Reduce the total number of fatalities and severe injuries in the region by X percent by year Y. Total severe injuries per X VMT.
Reduce the total number of fatalities in the region by X percent by year Y. Number of fatalities
Reduce the total number of severe injuries in the region by X percent by year Y. Number of serious injuries

 
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

Related Sources

Document Name Version Publication Date
Management of Electronic Surface Transport Regulations (METR) Vision Final 7/12/2021
ITS User Services Document 1/1/2005


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 High Moderate Class 3
Emergency Vehicle OBE Moderate High Moderate Class 3
ITS Roadway Equipment Moderate High Moderate Class 3
Maint and Constr Management Center Moderate High Moderate Class 3
Maint and Constr Vehicle OBE Moderate High Moderate Class 3
METR Discrepancy Contact System Moderate High Moderate Class 3
METR Discrepancy Handling System Moderate High Moderate Class 3
METR Distribution Center Moderate High Moderate Class 3
METR Regulation System Moderate High Moderate Class 3
METR Verification System Moderate High Moderate Class 3
Non-METR Distribution System Moderate Moderate Moderate Class 2
Other METR Discrepancy Handling Systems Moderate Moderate Moderate Class 2
Other METR Distribution Centers Moderate High Moderate Class 3
Other METR Regulation Systems Moderate High Moderate Class 3
Personal Information Device Moderate Moderate Moderate Class 2
Vehicle 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
Connected Vehicle Roadside Equipment METR Regulation System METR 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. If this is compromised, it could send unnecessary maintenance workers, or cause the appearance of excessive traffic violations, leading to further unnecessary investigation. A delay in reporting this may cause a delay in necessary maintenance, but (a) this is not time-critical and (b) there are other channels for reporting malfunctioning. Additionally, there is a message received notification, which means that RSE can ensure that all intersection safety issues are delivered.
Connected Vehicle Roadside Equipment Personal Information Device local METR information for users Not Applicable High Moderate
This information is intended to be widely distributed and effectively public. This information may be used to guide driver and AV behavior; incorrect or manipulated information could result in a vehicle performing a traffic movement that is not permitted, which in some cases (e.g., right turn on red) could be quite dangerous. While it would be ideal if this information is always available, every user should have a safe fallback approach so the impact of a flow outage could degrade vehicle performance but should not result in significant material loss or safety impact.
Connected Vehicle Roadside Equipment Vehicle local METR information for users Not Applicable High Moderate
This information is intended to be widely distributed and effectively public. This information may be used to guide driver and AV behavior; incorrect or manipulated information could result in a vehicle performing a traffic movement that is not permitted, which in some cases (e.g., right turn on red) could be quite dangerous. While it would be ideal if this information is always available, every user should have a safe fallback approach so the impact of a flow outage could degrade vehicle performance but should not result in significant material loss or safety impact.
Driver 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.
Emergency Vehicle OBE Personal Information Device local METR information for users Not Applicable High Moderate
This information is intended to be widely distributed and effectively public. This information may be used to guide driver and AV behavior; incorrect or manipulated information could result in a vehicle performing a traffic movement that is not permitted, which in some cases (e.g., right turn on red) could be quite dangerous. While it would be ideal if this information is always available, every user should have a safe fallback approach so the impact of a flow outage could degrade vehicle performance but should not result in significant material loss or safety impact.
Emergency Vehicle OBE Vehicle local METR information for users Not Applicable High Moderate
This information is intended to be widely distributed and effectively public. This information may be used to guide driver and AV behavior; incorrect or manipulated information could result in a vehicle performing a traffic movement that is not permitted, which in some cases (e.g., right turn on red) could be quite dangerous. While it would be ideal if this information is always available, every user should have a safe fallback approach so the impact of a flow outage could degrade vehicle performance but should not result in significant material loss or safety impact.
ITS Roadway Equipment Connected Vehicle Roadside Equipment field equipment status for METR Moderate High Moderate
The operational state of field devices, if known to an attacker or individual with criminal intent, could be used to facilitate the commission of a crime. Individual devices may be more or less important in this context; for example knowing whether a security camera is operating is probably more relevant to the criminal than knowing if the DMS is operating, though the latter could still be useful info. Instances of this flow that are local minimize this risk however, so for these local flows Confidentiality is considered LOW. If incorrect or changed, could lead to in incorrect rule distribution which in turn could lead to incorrect behavior by vehicles receiving the incorrect information. Might be MODERATE in some instances, but rated HIGH because the simplest use cases (e.g. higher speed limits) can lead to dangerous behavior. Must be timely and available for most use cases, but receiving devices must have safe fallbacks anyway and the impact of not having this information is likely not catastrophic.
Maint and Constr Management Center METR Regulation System METR coordination Moderate High Moderate
The scope of coordination could expose some of the inner workings that imply policy or technical workings that could be used negatively against METR subsystems. While it would be ideal if METR operations were completely transparent, at least in early phases it is likely that coordination activies are in flux and could be taken out of context. There is no legitimate reason to observe this information regardless. This information may eventually (once it is reconciled throughout the METR system) be used to guide driver and AV behavior; incorrect or manipulated information could result in a vehicle performing a traffic movement that is not permitted, which in some cases (e.g., right turn on red) could be quite dangerous. Discrepancy management should ideally always be functioning, but especially early on as METR deployments evolve, it is unreasonable to expect, and would have minimal impact, if discrepancy related flows were reasonably available. HIGH may be viable in the future, and may be necessary if automated vehicles depend on METR information to be consistently correct at all times.
Maint and Constr Management Center METR Regulation System METR TCD discrepancy status Low Moderate Moderate
Related data is generally widely distributed, so it is difficult to justify concealment. Related discrepancy flows are typically MODERATE though, so this could be elevated to homogenize requirements. Road maintenance data needs to be accurate and available so that travelers can make appropriate decisions. Inappropriate decisions may significantly affect traffic and individual travel experiences. Road maintenance data needs to be accurate and available so that other maintenance centers can make appropriate decisions. Inappropriate decisions may significantly affect traffic and individual travel experiences.
Maint and Constr Vehicle OBE Personal Information Device local METR information for users Not Applicable High Moderate
This information is intended to be widely distributed and effectively public. This information may be used to guide driver and AV behavior; incorrect or manipulated information could result in a vehicle performing a traffic movement that is not permitted, which in some cases (e.g., right turn on red) could be quite dangerous. While it would be ideal if this information is always available, every user should have a safe fallback approach so the impact of a flow outage could degrade vehicle performance but should not result in significant material loss or safety impact.
Maint and Constr Vehicle OBE Vehicle local METR information for users Not Applicable High Moderate
This information is intended to be widely distributed and effectively public. This information may be used to guide driver and AV behavior; incorrect or manipulated information could result in a vehicle performing a traffic movement that is not permitted, which in some cases (e.g., right turn on red) could be quite dangerous. While it would be ideal if this information is always available, every user should have a safe fallback approach so the impact of a flow outage could degrade vehicle performance but should not result in significant material loss or safety impact.
METR Discrepancy Contact System METR Regulation System METR coordination Moderate High Moderate
The scope of coordination could expose some of the inner workings that imply policy or technical workings that could be used negatively against METR subsystems. While it would be ideal if METR operations were completely transparent, at least in early phases it is likely that coordination activies are in flux and could be taken out of context. There is no legitimate reason to observe this information regardless. This information may eventually (once it is reconciled throughout the METR system) be used to guide driver and AV behavior; incorrect or manipulated information could result in a vehicle performing a traffic movement that is not permitted, which in some cases (e.g., right turn on red) could be quite dangerous. Discrepancy management should ideally always be functioning, but especially early on as METR deployments evolve, it is unreasonable to expect, and would have minimal impact, if discrepancy related flows were reasonably available. HIGH may be viable in the future, and may be necessary if automated vehicles depend on METR information to be consistently correct at all times.
METR Discrepancy Handling System METR Regulation System consolidated discrepancy report Moderate Moderate Moderate
Discrepancy-handling flows may contain a significant amount of discrepancy reporting information, which could imply behavior in the field, actions of rules-agents and other activities that could be leveraged by bad actors. Information contained in this flow will be used to assess the accuracy of existing rules; this will require some process that strips out incorrect reports, but the number of incorrect reports should be minimized to reduce undue processing. Backoffice discrepancy handling flows should be basically reliable, else the discrepancy handling system will have difficulty functioning, which in turn could lead to negative safety or other impacts in the field.
METR Discrepancy Handling System METR Regulation System discrepancy report details Moderate Moderate Moderate
Discrepancy-handling flows may contain a significant amount of discrepancy reporting information, which could imply behavior in the field, actions of rules-agents and other activities that could be leveraged by bad actors. Information contained in this flow will be used to assess the accuracy of existing rules; this will require some process that strips out incorrect reports, but the number of incorrect reports should be minimized to reduce undue processing. Backoffice discrepancy handling flows should be basically reliable, else the discrepancy handling system will have difficulty functioning, which in turn could lead to negative safety or other impacts in the field.
METR Discrepancy Handling System METR Regulation System METR information Low High Moderate
Since all rules are intended for public/machine consumption, there is little reason to obfuscate the information. Only in the case of an instance of the flow that is targeted to a specific vehicle or class of vehicles might encryption be warranted, as that distribution may imply the behavior or desired action of the target vehicles. Rules could be used to guide vehicle behavior, and if incorrect could lead to vehicles breaking actual rules with potentially highly damaging consequences. Updates are probably infrequent so often this flow can be a less than HIGH availability. In cases of high update (e.g., work zones, incidents), it could be HIGH.
METR Discrepancy Handling System Other METR Discrepancy Handling Systems consolidated discrepancy report Moderate Moderate Moderate
Discrepancy-handling flows may contain a significant amount of discrepancy reporting information, which could imply behavior in the field, actions of rules-agents and other activities that could be leveraged by bad actors. Information contained in this flow will be used to assess the accuracy of existing rules; this will require some process that strips out incorrect reports, but the number of incorrect reports should be minimized to reduce undue processing. Backoffice discrepancy handling flows should be basically reliable, else the discrepancy handling system will have difficulty functioning, which in turn could lead to negative safety or other impacts in the field.
METR Discrepancy Handling System Other METR Discrepancy Handling Systems discrepancy report details Moderate Moderate Moderate
Discrepancy-handling flows may contain a significant amount of discrepancy reporting information, which could imply behavior in the field, actions of rules-agents and other activities that could be leveraged by bad actors. Information contained in this flow will be used to assess the accuracy of existing rules; this will require some process that strips out incorrect reports, but the number of incorrect reports should be minimized to reduce undue processing. Backoffice discrepancy handling flows should be basically reliable, else the discrepancy handling system will have difficulty functioning, which in turn could lead to negative safety or other impacts in the field.
METR Discrepancy Handling System Other METR Discrepancy Handling Systems discrepancy suppression information Moderate Moderate Moderate
Discrepancy-handling flows may contain a significant amount of discrepancy reporting information, which could imply behavior in the field, actions of rules-agents and other activities that could be leveraged by bad actors. Information contained in this flow will be used to assess the accuracy of existing rules; this will require some process that strips out incorrect reports, but the number of incorrect reports should be minimized to reduce undue processing. Backoffice discrepancy handling flows should be basically reliable, else the discrepancy handling system will have difficulty functioning, which in turn could lead to negative safety or other impacts in the field.
METR Distribution Center METR Discrepancy Handling System METR information Low High Moderate
Since all rules are intended for public/machine consumption, there is little reason to obfuscate the information. Only in the case of an instance of the flow that is targeted to a specific vehicle or class of vehicles might encryption be warranted, as that distribution may imply the behavior or desired action of the target vehicles. Rules could be used to guide vehicle behavior, and if incorrect could lead to vehicles breaking actual rules with potentially highly damaging consequences. Updates are probably infrequent so often this flow can be a less than HIGH availability. In cases of high update (e.g., work zones, incidents), it could be HIGH.
METR Distribution Center METR Regulation System system-generated discrepancy report Moderate Moderate Moderate
Discrepancy-handling flows may contain a significant amount of discrepancy reporting information, which could imply behavior in the field, actions of rules-agents and other activities that could be leveraged by bad actors. Information contained in this flow will be used to assess the accuracy of existing rules; this will require some process that strips out incorrect reports, but the number of incorrect reports should be minimized to reduce undue processing. Backoffice discrepancy handling flows should be basically reliable, else the discrepancy handling system will have difficulty functioning, which in turn could lead to negative safety or other impacts in the field.
METR Distribution Center Other METR Distribution Centers METR information Low High Moderate
Since all rules are intended for public/machine consumption, there is little reason to obfuscate the information. Only in the case of an instance of the flow that is targeted to a specific vehicle or class of vehicles might encryption be warranted, as that distribution may imply the behavior or desired action of the target vehicles. Rules could be used to guide vehicle behavior, and if incorrect could lead to vehicles breaking actual rules with potentially highly damaging consequences. Updates are probably infrequent so often this flow can be a less than HIGH availability. In cases of high update (e.g., work zones, incidents), it could be HIGH.
METR Distribution Center Other METR Distribution Centers system-generated discrepancy report Moderate Moderate Moderate
Discrepancy-handling flows may contain a significant amount of discrepancy reporting information, which could imply behavior in the field, actions of rules-agents and other activities that could be leveraged by bad actors. Information contained in this flow will be used to assess the accuracy of existing rules; this will require some process that strips out incorrect reports, but the number of incorrect reports should be minimized to reduce undue processing.` Backoffice discrepancy handling flows should be basically reliable, else the discrepancy handling system will have difficulty functioning, which in turn could lead to negative safety or other impacts in the field.
METR Distribution Center Personal Information Device METR information for users Low High Moderate
Since all rules are intended for public/machine consumption, there is little reason to obfuscate the information. Only in the case of an instance of the flow that is targeted to a specific vehicle or class of vehicles might encryption be warranted, as that distribution may imply the behavior or desired action of the target vehicles. Rules could be used to guide vehicle behavior, and if incorrect could lead to vehicles breaking actual rules with potentially highly damaging consequences. Updates are probably infrequent so often this flow can be a less than HIGH availability. In cases of high update (e.g., work zones, incidents), it could be HIGH.
METR Distribution Center Vehicle METR information for users Low High Moderate
Since all rules are intended for public/machine consumption, there is little reason to obfuscate the information. Only in the case of an instance of the flow that is targeted to a specific vehicle or class of vehicles might encryption be warranted, as that distribution may imply the behavior or desired action of the target vehicles. Rules could be used to guide vehicle behavior, and if incorrect could lead to vehicles breaking actual rules with potentially highly damaging consequences. Updates are probably infrequent so often this flow can be a less than HIGH availability. In cases of high update (e.g., work zones, incidents), it could be HIGH.
METR Regulation System Connected Vehicle Roadside Equipment METR application information 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. If this is compromised, it could send unnecessary maintenance workers, or cause the appearance of excessive traffic violations, leading to further unnecessary investigation. A delay in reporting this may cause a delay in necessary maintenance, but (a) this is not time-critical and (b) there are other channels for reporting malfunctioning. Additionally, there is a message received notification, which means that RSE can ensure that all intersection safety issues are delivered.
METR Regulation System Emergency Vehicle OBE METR management information Moderate High Moderate
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. If this is compromised, it could result in incorrect rule-related information distribution, which could in turn cause a safety or other serious issue. Occasional outages will be inconvenient but in all cases, safe fallbacks should exist.
METR Regulation System Maint and Constr Management Center METR coordination Moderate High Moderate
The scope of coordination could expose some of the inner workings that imply policy or technical workings that could be used negatively against METR subsystems. While it would be ideal if METR operations were completely transparent, at least in early phases it is likely that coordination activies are in flux and could be taken out of context. There is no legitimate reason to observe this information regardless. This information may eventually (once it is reconciled throughout the METR system) be used to guide driver and AV behavior; incorrect or manipulated information could result in a vehicle performing a traffic movement that is not permitted, which in some cases (e.g., right turn on red) could be quite dangerous. Discrepancy management should ideally always be functioning, but especially early on as METR deployments evolve, it is unreasonable to expect, and would have minimal impact, if discrepancy related flows were reasonably available. HIGH may be viable in the future, and may be necessary if automated vehicles depend on METR information to be consistently correct at all times.
METR Regulation System Maint and Constr Management Center METR information Low High Moderate
Since all rules are intended for public/machine consumption, there is little reason to obfuscate the information. Only in the case of an instance of the flow that is targeted to a specific vehicle or class of vehicles might encryption be warranted, as that distribution may imply the behavior or desired action of the target vehicles. Rules could be used to guide vehicle behavior, and if incorrect could lead to vehicles breaking actual rules with potentially highly damaging consequences. Updates are probably infrequent so often this flow can be a less than HIGH availability. In cases of high update (e.g., work zones, incidents), it could be HIGH.
METR Regulation System Maint and Constr Vehicle OBE METR management information Moderate High Moderate
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. If this is compromised, it could result in incorrect rule-related information distribution, which could in turn cause a safety or other serious issue. Occasional outages will be inconvenient but in all cases, safe fallbacks should exist.
METR Regulation System METR Discrepancy Contact System METR coordination Moderate High Moderate
The scope of coordination could expose some of the inner workings that imply policy or technical workings that could be used negatively against METR subsystems. While it would be ideal if METR operations were completely transparent, at least in early phases it is likely that coordination activies are in flux and could be taken out of context. There is no legitimate reason to observe this information regardless. This information may eventually (once it is reconciled throughout the METR system) be used to guide driver and AV behavior; incorrect or manipulated information could result in a vehicle performing a traffic movement that is not permitted, which in some cases (e.g., right turn on red) could be quite dangerous. Discrepancy management should ideally always be functioning, but especially early on as METR deployments evolve, it is unreasonable to expect, and would have minimal impact, if discrepancy related flows were reasonably available. HIGH may be viable in the future, and may be necessary if automated vehicles depend on METR information to be consistently correct at all times.
METR Regulation System METR Discrepancy Handling System discrepancy suppression information Moderate Moderate Moderate
Discrepancy-handling flows may contain a significant amount of discrepancy reporting information, which could imply behavior in the field, actions of rules-agents and other activities that could be leveraged by bad actors. Information contained in this flow will be used to assess the accuracy of existing rules; this will require some process that strips out incorrect reports, but the number of incorrect reports should be minimized to reduce undue processing. Backoffice discrepancy handling flows should be basically reliable, else the discrepancy handling system will have difficulty functioning, which in turn could lead to negative safety or other impacts in the field.
METR Regulation System METR Discrepancy Handling System METR information Low High Moderate
Since all rules are intended for public/machine consumption, there is little reason to obfuscate the information. Only in the case of an instance of the flow that is targeted to a specific vehicle or class of vehicles might encryption be warranted, as that distribution may imply the behavior or desired action of the target vehicles. Rules could be used to guide vehicle behavior, and if incorrect could lead to vehicles breaking actual rules with potentially highly damaging consequences. Updates are probably infrequent so often this flow can be a less than HIGH availability. In cases of high update (e.g., work zones, incidents), it could be HIGH.
METR Regulation System METR Distribution Center METR device status Moderate Moderate Moderate
Device status information should be concealed, as an unauthorized observer could use this to reverse engineer device control systems. Device status information needs to be available and correct, or the controlling system may take inappropriate maintenance action, costing time and money. Device status information needs to be available and correct, or the controlling system may take inappropriate maintenance action, costing time and money.
METR Regulation System METR Distribution Center METR information Low High Moderate
Since all rules are intended for public/machine consumption, there is little reason to obfuscate the information. Only in the case of an instance of the flow that is targeted to a specific vehicle or class of vehicles might encryption be warranted, as that distribution may imply the behavior or desired action of the target vehicles. Rules could be used to guide vehicle behavior, and if incorrect could lead to vehicles breaking actual rules with potentially highly damaging consequences. Updates are probably infrequent so often this flow can be a less than HIGH availability. In cases of high update (e.g., work zones, incidents), it could be HIGH.
METR Regulation System METR Rule Translator Agent METR feedback Moderate High Low
Changes to rules and the information exchanged as part of that process should be held in context; observation by third parties may enable an attack on the rules themselves, and so should be avoided. Changes to rules must be correct as they could have impacts on vehicles and others in the field. While some rules could lower this requirement based on the severity of impact of an alteration in that rule type, in practice this information is likely distributed the same way for every rule type, so default to the most severe requirement. There should be many opportunities to provide this feedback, though as this is a C2C flow there is no practical reason this flow should not be able to easily attain a high availability.
METR Regulation System METR Rule-Maker METR feedback Moderate High Low
Changes to rules and the information exchanged as part of that process should be held in context; observation by third parties may enable an attack on the rules themselves, and so should be avoided. Changes to rules must be correct as they could have impacts on vehicles and others in the field. While some rules could lower this requirement based on the severity of impact of an alteration in that rule type, in practice this information is likely distributed the same way for every rule type, so default to the most severe requirement. There should be many opportunities to provide this feedback, though as this is a C2C flow there is no practical reason this flow should not be able to easily attain a high availability.
METR Regulation System METR Rule-Maker METR information approval request Moderate High Moderate
May have some PII for internal actors in the METR system, which should not be observed as they could be used as part of phishing or related attacks. Rules could be used to guide vehicle behavior, and if incorrect could lead to vehicles breaking actual rules with potentially highly damaging consequences. Updates are probably infrequent so often this flow can be a less than HIGH availability. In cases of high update (e.g., work zones, incidents), it could be HIGH.
METR Regulation System METR Verification System METR coordination Moderate High Moderate
The scope of coordination could expose some of the inner workings that imply policy or technical workings that could be used negatively against METR subsystems. While it would be ideal if METR operations were completely transparent, at least in early phases it is likely that coordination activies are in flux and could be taken out of context. There is no legitimate reason to observe this information regardless. This information may eventually (once it is reconciled throughout the METR system) be used to guide driver and AV behavior; incorrect or manipulated information could result in a vehicle performing a traffic movement that is not permitted, which in some cases (e.g., right turn on red) could be quite dangerous. Discrepancy management should ideally always be functioning, but especially early on as METR deployments evolve, it is unreasonable to expect, and would have minimal impact, if discrepancy related flows were reasonably available. HIGH may be viable in the future, and may be necessary if automated vehicles depend on METR information to be consistently correct at all times.
METR Regulation System METR Verification System METR information Low High Moderate
Since all rules are intended for public/machine consumption, there is little reason to obfuscate the information. Only in the case of an instance of the flow that is targeted to a specific vehicle or class of vehicles might encryption be warranted, as that distribution may imply the behavior or desired action of the target vehicles. Rules could be used to guide vehicle behavior, and if incorrect could lead to vehicles breaking actual rules with potentially highly damaging consequences. Updates are probably infrequent so often this flow can be a less than HIGH availability. In cases of high update (e.g., work zones, incidents), it could be HIGH.
METR Regulation System METR Verification System unverified METR information Moderate High Moderate
May have some PII for internal actors in the METR system, which should not be observed as they could be used as part of phishing or related attacks. Rules could be used to guide vehicle behavior, and if incorrect could lead to vehicles breaking actual rules with potentially highly damaging consequences. Updates are probably infrequent so often this flow can be a less than HIGH availability. In cases of high update (e.g., work zones, incidents), it could be HIGH.
METR Regulation System Non-METR Distribution System METR information Low High Moderate
Since all rules are intended for public/machine consumption, there is little reason to obfuscate the information. Only in the case of an instance of the flow that is targeted to a specific vehicle or class of vehicles might encryption be warranted, as that distribution may imply the behavior or desired action of the target vehicles. Rules could be used to guide vehicle behavior, and if incorrect could lead to vehicles breaking actual rules with potentially highly damaging consequences. Updates are probably infrequent so often this flow can be a less than HIGH availability. In cases of high update (e.g., work zones, incidents), it could be HIGH.
METR Regulation System Other METR Regulation Systems METR coordination Moderate High Moderate
The scope of coordination could expose some of the inner workings that imply policy or technical workings that could be used negatively against METR subsystems. While it would be ideal if METR operations were completely transparent, at least in early phases it is likely that coordination activies are in flux and could be taken out of context. There is no legitimate reason to observe this information regardless. This information may eventually (once it is reconciled throughout the METR system) be used to guide driver and AV behavior; incorrect or manipulated information could result in a vehicle performing a traffic movement that is not permitted, which in some cases (e.g., right turn on red) could be quite dangerous. Discrepancy management should ideally always be functioning, but especially early on as METR deployments evolve, it is unreasonable to expect, and would have minimal impact, if discrepancy related flows were reasonably available. HIGH may be viable in the future, and may be necessary if automated vehicles depend on METR information to be consistently correct at all times.
METR Regulation System Other METR Regulation Systems METR information Low High Moderate
Since all rules are intended for public/machine consumption, there is little reason to obfuscate the information. Only in the case of an instance of the flow that is targeted to a specific vehicle or class of vehicles might encryption be warranted, as that distribution may imply the behavior or desired action of the target vehicles. Rules could be used to guide vehicle behavior, and if incorrect could lead to vehicles breaking actual rules with potentially highly damaging consequences. Updates are probably infrequent so often this flow can be a less than HIGH availability. In cases of high update (e.g., work zones, incidents), it could be HIGH.
METR Regulation System Other METR Regulation Systems system-generated discrepancy report Moderate Moderate Moderate
Discrepancy-handling flows may contain a significant amount of discrepancy reporting information, which could imply behavior in the field, actions of rules-agents and other activities that could be leveraged by bad actors. Information contained in this flow will be used to assess the accuracy of existing rules; this will require some process that strips out incorrect reports, but the number of incorrect reports should be minimized to reduce undue processing.` Backoffice discrepancy handling flows should be basically reliable, else the discrepancy handling system will have difficulty functioning, which in turn could lead to negative safety or other impacts in the field.
METR Rule Translator Agent METR Regulation System METR input Not Applicable High High
System core flows should have some protection from casual viewing, as otherwise imposters could gain illicit control over core equipment. 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.
METR Rule-Maker METR Regulation System METR information approval Moderate High Moderate
May have some PII for internal actors in the METR system, which should not be observed as they could be used as part of phishing or related attacks. Rules could be used to guide vehicle behavior, and if incorrect could lead to vehicles breaking actual rules with potentially highly damaging consequences. Updates are probably infrequent so often this flow can be a less than HIGH availability. In cases of high update (e.g., work zones, incidents), it could be HIGH.
METR Rule-Maker METR Regulation System METR input Not Applicable High High
System core flows should have some protection from casual viewing, as otherwise imposters could gain illicit control over core equipment. 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.
METR Verification System METR Regulation System METR coordination Moderate High Moderate
The scope of coordination could expose some of the inner workings that imply policy or technical workings that could be used negatively against METR subsystems. While it would be ideal if METR operations were completely transparent, at least in early phases it is likely that coordination activies are in flux and could be taken out of context. There is no legitimate reason to observe this information regardless. This information may eventually (once it is reconciled throughout the METR system) be used to guide driver and AV behavior; incorrect or manipulated information could result in a vehicle performing a traffic movement that is not permitted, which in some cases (e.g., right turn on red) could be quite dangerous. Discrepancy management should ideally always be functioning, but especially early on as METR deployments evolve, it is unreasonable to expect, and would have minimal impact, if discrepancy related flows were reasonably available. HIGH may be viable in the future, and may be necessary if automated vehicles depend on METR information to be consistently correct at all times.
METR Verification System METR Regulation System verified METR information Moderate High Moderate
May have some PII for internal actors in the METR system, which should not be observed as they could be used as part of phishing or related attacks. Rules could be used to guide vehicle behavior, and if incorrect could lead to vehicles breaking actual rules with potentially highly damaging consequences. Updates are probably infrequent so often this flow can be a less than HIGH availability. In cases of high update (e.g., work zones, incidents), it could be HIGH.
Non-METR Distribution System METR Regulation System system-generated discrepancy report Moderate Moderate Moderate
Discrepancy-handling flows may contain a significant amount of discrepancy reporting information, which could imply behavior in the field, actions of rules-agents and other activities that could be leveraged by bad actors. Information contained in this flow will be used to assess the accuracy of existing rules; this will require some process that strips out incorrect reports, but the number of incorrect reports should be minimized to reduce undue processing. Backoffice discrepancy handling flows should be basically reliable, else the discrepancy handling system will have difficulty functioning, which in turn could lead to negative safety or other impacts in the field.
Other METR Discrepancy Handling Systems METR Discrepancy Handling System consolidated discrepancy report Moderate Moderate Moderate
Discrepancy-handling flows may contain a significant amount of discrepancy reporting information, which could imply behavior in the field, actions of rules-agents and other activities that could be leveraged by bad actors. Information contained in this flow will be used to assess the accuracy of existing rules; this will require some process that strips out incorrect reports, but the number of incorrect reports should be minimized to reduce undue processing. Backoffice discrepancy handling flows should be basically reliable, else the discrepancy handling system will have difficulty functioning, which in turn could lead to negative safety or other impacts in the field.
Other METR Discrepancy Handling Systems METR Discrepancy Handling System discrepancy report details Moderate Moderate Moderate
Discrepancy-handling flows may contain a significant amount of discrepancy reporting information, which could imply behavior in the field, actions of rules-agents and other activities that could be leveraged by bad actors. Information contained in this flow will be used to assess the accuracy of existing rules; this will require some process that strips out incorrect reports, but the number of incorrect reports should be minimized to reduce undue processing. Backoffice discrepancy handling flows should be basically reliable, else the discrepancy handling system will have difficulty functioning, which in turn could lead to negative safety or other impacts in the field.
Other METR Discrepancy Handling Systems METR Discrepancy Handling System discrepancy suppression information Moderate Moderate Moderate
Discrepancy-handling flows may contain a significant amount of discrepancy reporting information, which could imply behavior in the field, actions of rules-agents and other activities that could be leveraged by bad actors. Information contained in this flow will be used to assess the accuracy of existing rules; this will require some process that strips out incorrect reports, but the number of incorrect reports should be minimized to reduce undue processing. Backoffice discrepancy handling flows should be basically reliable, else the discrepancy handling system will have difficulty functioning, which in turn could lead to negative safety or other impacts in the field.
Other METR Distribution Centers METR Distribution Center METR information Low High Moderate
Since all rules are intended for public/machine consumption, there is little reason to obfuscate the information. Only in the case of an instance of the flow that is targeted to a specific vehicle or class of vehicles might encryption be warranted, as that distribution may imply the behavior or desired action of the target vehicles. Rules could be used to guide vehicle behavior, and if incorrect could lead to vehicles breaking actual rules with potentially highly damaging consequences. Updates are probably infrequent so often this flow can be a less than HIGH availability. In cases of high update (e.g., work zones, incidents), it could be HIGH.
Other METR Distribution Centers METR Distribution Center system-generated discrepancy report Moderate Moderate Moderate
Discrepancy-handling flows may contain a significant amount of discrepancy reporting information, which could imply behavior in the field, actions of rules-agents and other activities that could be leveraged by bad actors. Information contained in this flow will be used to assess the accuracy of existing rules; this will require some process that strips out incorrect reports, but the number of incorrect reports should be minimized to reduce undue processing. Backoffice discrepancy handling flows should be basically reliable, else the discrepancy handling system will have difficulty functioning, which in turn could lead to negative safety or other impacts in the field.
Other METR Regulation Systems METR Regulation System METR coordination Moderate High Moderate
The scope of coordination could expose some of the inner workings that imply policy or technical workings that could be used negatively against METR subsystems. While it would be ideal if METR operations were completely transparent, at least in early phases it is likely that coordination activies are in flux and could be taken out of context. There is no legitimate reason to observe this information regardless. This information may eventually (once it is reconciled throughout the METR system) be used to guide driver and AV behavior; incorrect or manipulated information could result in a vehicle performing a traffic movement that is not permitted, which in some cases (e.g., right turn on red) could be quite dangerous. Discrepancy management should ideally always be functioning, but especially early on as METR deployments evolve, it is unreasonable to expect, and would have minimal impact, if discrepancy related flows were reasonably available. HIGH may be viable in the future, and may be necessary if automated vehicles depend on METR information to be consistently correct at all times.
Other METR Regulation Systems METR Regulation System METR information Low High Moderate
Since all rules are intended for public/machine consumption, there is little reason to obfuscate the information. Only in the case of an instance of the flow that is targeted to a specific vehicle or class of vehicles might encryption be warranted, as that distribution may imply the behavior or desired action of the target vehicles. Rules could be used to guide vehicle behavior, and if incorrect could lead to vehicles breaking actual rules with potentially highly damaging consequences. Updates are probably infrequent so often this flow can be a less than HIGH availability. In cases of high update (e.g., work zones, incidents), it could be HIGH.
Other METR Regulation Systems METR Regulation System system-generated discrepancy report Moderate Moderate Moderate
Discrepancy-handling flows may contain a significant amount of discrepancy reporting information, which could imply behavior in the field, actions of rules-agents and other activities that could be leveraged by bad actors. Information contained in this flow will be used to assess the accuracy of existing rules; this will require some process that strips out incorrect reports, but the number of incorrect reports should be minimized to reduce undue processing. Backoffice discrepancy handling flows should be basically reliable, else the discrepancy handling system will have difficulty functioning, which in turn could lead to negative safety or other impacts in the field.
Personal Information Device METR Discrepancy Handling System METR discrepancy report Moderate Moderate Low
Will include some artifact indicating the identity of the reporter; while this could be a pseudonym, it could eventually be associated with the reporter. There is no good reason for discrepancy reporters to be observed by anyone outside the METR system. Information contained in this flow will be used to assess the accuracy of existing rules; this will require some process that strips out incorrect reports, but the number of incorrect reports should be minimized to reduce undue processing. There should be many opportunities to provide discrepancy reports, so there is no pressing need for a requirement above LOW.
Personal Information Device Traveler traveler interface updates Not Applicable Moderate Moderate
Personalized data that includes directions and guidance for an individual, but eventually evident anyway. Should be accurate as the Traveler will be relying on this information for routing and related choices. Lack of accuracy will result in lack of confidence from the traveler as well as an unsatisfactory trip, leading to a negative feedback spiral. Users expect their devices to work. If information is not presented to the operator, the relevant applications simply won't be used.
Traveler Personal Information Device traveler input Not Applicable Moderate Low
This data is informing the vehicle of operational information that is relevant to the operation of the vehicle. It should not contain anything sensitive, and does not matter if another person can observe it. While public, information must be correct or travelers may make incorrect decisions with regard to their travel plans. Information is available through other means, though depending on the location this might not always be the case, in which case this would be MODERATE.
Vehicle Driver 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.
Vehicle METR Discrepancy Handling System METR discrepancy report Moderate Moderate Low
Will include some artifact indicating the identity of the reporter; while this could be a pseudonym, it could eventually be associated with the reporter. There is no good reason for discrepancy reporters to be observed by anyone outside the METR system. Information contained in this flow will be used to assess the accuracy of existing rules; this will require some process that strips out incorrect reports, but the number of incorrect reports should be minimized to reduce undue processing. There should be many opportunities to provide discrepancy reports, so there is no pressing need for a requirement above LOW.

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
CTI 4001 RSU Dedicated Short-Range Communications Roadside Unit Specifications (FHWA-JPO-17-589) Connected Vehicle Roadside Equipment
ITE ATC ITS Cabinet Intelligent Transportation System Standard Specification for Roadside Cabinets ITS Roadway Equipment
NEMA TS 8 Cyber and Physical Security Cyber and Physical Security for Intelligent Transportation Systems ITS Roadway Equipment




System Requirements

System Requirement Need
001 The system shall collect, store and exchange transportation-related regulations with other transportation centers. 01 Traveler Information needs to be able to disseminate to connected vehicles current local statutes, regulations, ordinances, and rules.
02 Traveler Information needs to be able to disseminate to personal device applications the current local statutes, regulations, ordinances, and rules.
002 The system shall disseminate rules, regulations, and statutes that govern motor vehicle operation to vehicles and other mobile devices. 01 Traveler Information needs to be able to disseminate to connected vehicles current local statutes, regulations, ordinances, and rules.
02 Traveler Information needs to be able to disseminate to personal device applications the current local statutes, regulations, ordinances, and rules.
003 The system shall receive rules, regulations, and status updates from traffic regulatory agencies or other traffic agencies. 03 Traffic regulatory agencies need to be able to provide current local statutes, regulations, ordinances, and rules to both traffic agencies and to traveler information.
004 The system shall aggregate updates to rules, regulations, and statutes in order to define updates to be sent to vehicles and other mobile devices. 03 Traffic regulatory agencies need to be able to provide current local statutes, regulations, ordinances, and rules to both traffic agencies and to traveler information.
005 The system shall control reduced speed zone warning roadside equipment, providing 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, 03 Traffic regulatory agencies need to be able to provide current local statutes, regulations, ordinances, and rules to both traffic agencies and to traveler information.
006 The system shall provide basemap updates to other Centers. 04 Vehicle and Personal device operators need to be able to validate and use traffic codes.
007 The system shall coordinate the contents of map data for distribution with other Centers. 04 Vehicle and Personal device operators need to be able to validate and use traffic codes.
008 The system shall provide basemap updates to Personal devices. 04 Vehicle and Personal device operators need to be able to validate and use traffic codes.
009 The system shall provide intersection geometry updates to Vehicles. 04 Vehicle and Personal device operators need to be able to validate and use traffic codes.
010 The system shall provide basemap updates to Vehicles. 04 Vehicle and Personal device operators need to be able to validate and use traffic codes.
011 The system shall provide intersection geometry updates to Personal Devices. 04 Vehicle and Personal device operators need to be able to validate and use traffic codes.
012 The system shall provide roadway geometry updates to Vehicles. 04 Vehicle and Personal device operators need to be able to validate and use traffic codes.
013 The system shall associate traffic regulations with map features. 04 Vehicle and Personal device operators need to be able to validate and use traffic codes.
014 The system shall distribute traffic regulatory data with its mapping products. 04 Vehicle and Personal device operators need to be able to validate and use traffic codes.
015 The system shall present traffic regulation information to the traveler when the traveler is in a condition where the regulation is relevant. 04 Vehicle and Personal device operators need to be able to validate and use traffic codes.
016 The system shall receive traffic regulation information from the center and validate that the information originated with the traffic regulatory entity with authority over the region the regulation applies. 04 Vehicle and Personal device operators need to be able to validate and use traffic codes.
017 The system shall present traffic regulation information to the driver when the driver is in a condition where the regulation is relevant. 04 Vehicle and Personal device operators need to be able to validate and use traffic codes.