METR Rule-Maker/Agent --> METR System:
METR input

Definitions

METR input (Information Flow): This flow supports data entry from a METR Translator Agent that will eventually become METR information.

METR Rule-Maker/Agent (Source Physical Object): The 'METR Rule-Maker/Agent' represents the entity that has the legal authority to establish and digitally sign approved METR rules. An agent is the person that enters the electronic version of the rule into the METR system.

METR System (Destination Physical Object): The 'METR System' creates and maintains electronic versions of traffic rules, regulations, ordinances and statutes that have official status and must be understood by all motor vehicle operators and intelligent vehicles that operate at higher automation levels. This system represents multiple authorities that operate at local, regional, state, and national levels and represents organizations that establish, manage, and enact the traffic code. Each electronic rule is approved, signed, and traceable to a specific rule-maker. Rules are independently verified. Any identified or reported rule discrepancies are analyzed, investigated, and addressed.

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 Not Applicable High High
Basis 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.


None defined