METR Regulation System --> METR Rule-Maker:
METR information approval request

Definitions

METR information approval request (Information Flow): This flow requests the approval of verified METR information prior to provision to METR users.

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-Maker (Destination Physical Object): 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.

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:

This Triple has the following triple relationships:

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 Moderate
Basis 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.


None defined