METR Regulation System --> METR Rule Translator Agent:
METR feedback

Definitions

METR feedback (Information Flow): This flow supports the presentation of issues requiring corrective actions necessary before information entered into a METR Regulation Center, can be approved. This flow can also be used to alert the rule translation agent that the METR Regulation Center has become aware of either a user-identified or system-identified discrepancy with previously distributed METR information which may require corrective actions. METR feedback can also be used to inform the rule translator agent of a newly discovered physical rule for further analysis and approval.

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

Included In

This Triple is in the following Service Packages:

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

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

  • None

This Triple has the following triple relationships:

None

Communication Solutions

No communications solutions identified.

Characteristics

None defined


Interoperability Description
Not Applicable Interoperability ratings don't apply per se to some types of interfaces like human interfaces. These interfaces may still benefit from associated standards (e.g., ergonomic and human factors standards for human interfaces), but the primary motive for these standards is not interoperability.

Security

Information Flow Security
  Confidentiality Integrity Availability
Rating Moderate High Low
Basis 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.


None defined