Maint and Constr Vehicle OBE --> Maint and Constr Management Center:
maint and constr vehicle location data
Definitions
maint and constr vehicle location data (Information Flow): The current location and related status (e.g., direction and speed) of the maintenance/construction vehicle.
Maint and Constr Vehicle OBE (Source Physical Object): The 'Maint and Constr Vehicle OBE' resides in a maintenance, construction, or other specialized service vehicle or equipment and provides the processing, storage, and communications functions necessary to support highway maintenance and construction. All types of maintenance and construction vehicles are covered, including heavy equipment, supervisory vehicles, unmanned remote controlled field maintenance robots, and sensory platforms that may be wheeled or low altitude aerial vehicles (e.g. drones, balloons). The MCV OBE provides two-way communications between drivers/operators and dispatchers and maintains and communicates current location and status information. A wide range of operational status is monitored, measured, and made available, depending on the specific type of vehicle or equipment. A snow plow for example, would monitor whether the plow is up or down and material usage information. The Maint and Constr Vehicle OBE may also contain capabilities to monitor vehicle systems to support maintenance of the vehicle itself. A separate 'Vehicle OBE' physical object supports the general vehicle safety and driver information capabilities that apply to all vehicles, including maintenance and construction vehicles. The Maint and Constr Vehicle OBE supplements these general capabilities with capabilities that are specific to maintenance and construction vehicles.
Maint and Constr Management Center (Destination 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.
Included In
This Triple is in the following Service Packages:
- MC01: Maintenance and Construction Vehicle and Equipment Tracking
- MC10: Asset Tracking
- MC11: Maintenance and Construction Signal Priority
This triple is associated with the following Functional Objects:
- MCM Priority Management
- MCM Remote Vehicle Control
- MCM Vehicle Tracking
- MCV Signal Priority
- MCV Vehicle Location Tracking
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
Relationship | Source | Destination | Flow |
---|---|---|---|
Depends On | Location and Time Data Source | Maint and Constr Vehicle OBE | location and time |
Communication Solutions
- (None-Data) - Secure Wireless Internet (EU) (32)
- (None-Data) - Secure Wireless Internet (ITS) (32)
- (None-Data) - Apache Kafka over Wireless (36)
- (None-Data) - OMG DDS over Wireless (36)
- (None-Data) - OASIS MQTT over Wireless (42)
- (None-Data) - OASIS AMQP over Wireless (45)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
OASIS MQTT DMP |
Facilities
Development needed OASIS MQTT |
Security
|
|
TransNet
|
|||
Access
|
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 | True |
Interoperability | Description |
---|---|
National | This triple should be implemented consistently within the geopolitical region through which movement is essentially free (e.g., the United States, the European Union). |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Rating | Moderate | Moderate | Moderate | |
Basis | This is effectively a tracking flow, which if intercepted would provide a third party with the ability to track maintenance and construction vehicles, which could enable nefarious and illegal activities. | Corruption, unavailability or unauthorized manipulation of this data could lead to a lack of understanding of maintenance vehilce locations. This could negatively effect coordinated actions such as roadway treatment and snow removal, compromising mobility. It could also negatively impact the safety of the vehicle operator. | Corruption, unavailability or unauthorized manipulation of this data could lead to a lack of understanding of maintenance vehilce locations. This could negatively effect coordinated actions such as roadway treatment and snow removal, compromising mobility. It could also negatively impact the safety of the vehicle operator. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |