Maint and Constr Vehicle OBE --> Equipment Repair Facility:
maint and constr vehicle conditions
Definitions
maint and constr vehicle conditions (Information Flow): Vehicle diagnostics information that is collected, filtered, and selectively reported by a maintenance and construction vehicle. The information includes engine temperature, mileage, tire wear, brake wear, belt wear, and any warnings or alarms concerning the operational condition of the vehicle and ancillary equipment.
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.
Equipment Repair Facility (Destination Physical Object): 'Equipment Repair Facility' represents the facilities that configure, service, and repair vehicles and other support equipment used in roadway infrastructure construction and maintenance. The equipment repair facility receives preventative and corrective maintenance schedules and vehicle configuration requirements, performs the necessary configuration and maintenance work on the vehicles and equipment, and provides vehicle and equipment status back to the architecture.
Included In
This Triple is in the following Service Packages:
This triple is associated with the following Functional Objects:
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
None |
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
|
Facilities
Development needed |
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 | Basic diagnostic information might not be sensitive, but any warnings or alarms could be, particularly if they are related to an incident or hostile event related to the vehicle. Such information could be used as part of damage assessment or target identification. | This needs to be accurate to properly schedule maintenance activities (for the basic maintenance data items) and to properly respond to warning indicators. If corrupted or unavailable, there could be a significant repurcussion for the vehicle and by extension, the vehicle operator. | This needs to be accurate to properly schedule maintenance activities (for the basic maintenance data items) and to properly respond to warning indicators. If corrupted or unavailable, there could be a significant repurcussion for the vehicle and by extension, the vehicle operator. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |