METR Discrepancy Handling System --> Other METR Discrepancy Handling Systems:
consolidated discrepancy report

Definitions

consolidated discrepancy report (Information Flow): This flow allows the METR Discrepancy Handling Center to send consolidated discrepancy reports to the intended destination. The consolidated reports are sent when conditions, as defined by local policies, are met (e.g., a sufficient number of reports have been received). The destination might be another METR Discrepancy Handing Center (e.g., an OEM sending data to a governmental handling system) but eventually, the consolidated reports are sent to the relevant METR Regulation Center.

METR Discrepancy Handling System (Source Physical Object): 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).

Other METR Discrepancy Handling Systems (Destination Physical Object): 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.

Included In

This Triple is in the following Service Packages:

• VS17: Management of Electronic Transport Regulations (METR)

This Triple is described by the following Functional View Functional Objects:

• MDHS METR Discrepancy Handling

This Triple is described by the following Functional View Data Flows:

• None

This Triple has the following triple relationships:

Communication Solutions

• METR: Discrepancy Reporting Requirements - Secure Internet (ITS) (19)
• METR: Discrepancy Reporting Requirements - Apache Kafka (23)
• METR: Discrepancy Reporting Requirements - OMG DDS (23)
• METR: Discrepancy Reporting Requirements - OASIS MQTT (29)
• (None-Data) - Secure Internet (ITS) (32)
• METR: Discrepancy Reporting Requirements - OASIS AMQP (32)
• (None-Data) - OASIS MQTT (42)
• (None-Data) - OASIS AMQP (45)

Selected Solution

METR: Discrepancy Reporting Requirements - Secure Internet (ITS)

Solution Description

ITS Application Entity ISO 24315-7 ISO 24315-8			Click gap icons for more info.
Mgmt Bundle: SNMPv3 MIB	Facilities (None)	Security Secure Session Alternatives
	TransNet IP Alternatives Internet Transport Alternatives
	Access Internet Subnet Alternatives

Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.

Characteristics

Security