Maint and Constr Management Center --> METR Regulation System:
METR TCD discrepancy status
Definitions
METR TCD discrepancy status (Information Flow): This flow supports reporting of status regarding the maintenance activities related to the response of a reported discrepancy that requires traffic control device maintenance (e.g., replacing a missing sign).
Maint and Constr Management Center (Source Physical Object): The 'Maint and Constr Management Center' monitors and manages roadway infrastructure construction and maintenance activities. Representing both public agencies and private contractors that provide these functions, this physical object manages fleets of maintenance, construction, or special service vehicles (e.g., snow and ice control equipment). The physical object receives a wide range of status information from these vehicles and performs vehicle dispatch, routing, and resource management for the vehicle fleets and associated equipment. The physical object participates in incident response by deploying maintenance and construction resources to an incident scene, in coordination with other center physical objects. The physical object manages equipment at the roadside, including environmental sensors and automated systems that monitor and mitigate adverse road and surface weather conditions. It manages the repair and maintenance of both non-ITS and ITS equipment including the traffic controllers, detectors, dynamic message signs, signals, and other equipment associated with the roadway infrastructure. Weather information is collected and fused with other data sources and used to support advanced decision support systems.
The physical object remotely monitors and manages ITS capabilities in work zones, gathering, storing, and disseminating work zone information to other systems. It manages traffic in the vicinity of the work zone and advises drivers of work zone status (either directly at the roadside or through an interface with the Transportation Information Center or Traffic Management Center physical objects.)
Construction and maintenance activities are tracked and coordinated with other systems, improving the quality and accuracy of information available regarding closures and other roadway construction and maintenance activities.
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:
None |
Communication Solutions
- METR: Regulation Requirements - Secure Internet (ITS) (22)
- METR: Regulation Requirements - Apache Kafka (23)
- METR: Regulation Requirements - OMG DDS (23)
- METR: Regulation Requirements - OASIS MQTT (29)
- METR: Regulation Requirements - OASIS AMQP (40)
- (None-Data) - Secure Internet (ITS) (43)
Selected Solution
Solution Description
ITS Application Entity
ISO 24315-4 ISO 24315-8 |
Click gap icons for more info.
|
||
Mgmt
OASIS MQTT DMP |
Facilities
(None) OASIS MQTT |
Security
|
|
TransNet
|
|||
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
Characteristic | Value |
---|---|
Time Context | Recent |
Spatial Context | Regional |
Acknowledgement | True |
Cardinality | Unicast |
Initiator | Source |
Authenticable | True |
Encrypt | False |
Interoperability | Description |
---|---|
Regional | Interoperability throughout the geopolitical region is highly desirable, but if implemented differently in different transportation management jurisdictions, significant benefits will still accrue in each jurisdiction. Regardless, this Information Flow Triple should be implemented consistently within a transportation jurisdiction (i.e., the scope of a regional architecture). |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Rating | Low | Moderate | Moderate | |
Basis | Related data is generally widely distributed, so it is difficult to justify concealment. Related discrepancy flows are typically MODERATE though, so this could be elevated to homogenize requirements. | Road maintenance data needs to be accurate and available so that travelers can make appropriate decisions. Inappropriate decisions may significantly affect traffic and individual travel experiences. | Road maintenance data needs to be accurate and available so that other maintenance centers can make appropriate decisions. Inappropriate decisions may significantly affect traffic and individual travel experiences. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | False |