METR Discrepancy Handling System --> METR Regulation System:
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).

METR Regulation System (Destination Physical Object): The 'METR Regulation System' creates and maintains electronic versions of traffic regulations 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.

Included In

This Triple is in the following Service Packages:

• None

This triple is associated with the following Functional Objects:

• None

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 - OMG DDS

Solution Description

ITS Application Entity ISO 24315-7 ISO 24315-8			Click gap icons for more info.
Mgmt OMG DDS	Facilities (None) OMG DDS OMG DDS-RPC OMG DDSI-RTPS	Security OMG DDS-Security
	TransNet IETF RFC 768 IP 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