Maint and Constr Vehicle OBE --> Personnel Device:
asset locations

Definitions

asset locations (Information Flow): Aggregate collected data including identified assets and their locations.

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.

Personnel Device (Destination Physical Object): 'Personnel Device' represents devices used by emergency personnel or maintenance and construction personnel in the field. In the case of emergency personnel, the devices would include body cameras or smartphones (and their peripherals) that can be used by emergency personnel to provide images or video as well as send or receive data regarding the incident. The devices could also be used for incident scene safety messages to the personnel. In the case of maintenance and construction field personnel, the devices could be cellular phones or specialized safety devices that would be used for work zone safety messages to the personnel.

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:

RelationshipSourceDestinationFlow
Depends On Field Maint and Constr Vehicle OBE asset ID

Communication Solutions

Solutions are sorted in ascending Gap Severity order. The Gap Severity is the parenthetical number at the end of the solution.

Selected Solution

(None-Data) - Local Unicast Wireless (1609.2)

Solution Description

This solution is used within the U.S.. It combines standards associated with (None-Data) with those for V-X: Local Unicast Wireless (1609.2). The (None-Data) standards include an unspecified set of standards at the upper layers. The V-X: Local Unicast Wireless (1609.2) standards include lower-layer standards that support local-area unicast wireless solutions applicable to North America, such as WAVE DSRC, LTE-V2X, LTE, Wi-Fi, etc.

ITS Application Entity
Mind the gap

Development needed
Click gap icons for more info.
Mgmt

Addressed Elsewhere
Facilities

Development needed
Security
Mind the gap
TransNet

IEEE 1609.3
Access
Mind the gapMind the gapMind the gapMind the gap
TransNet TransNet

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Access Access

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

ITS Application ITS Application

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Mgmt Mgmt

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Facility Facility

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Security Security

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

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 Local
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 All observable information, and not easy to observe given that one end of the flow is moving around a construction site. However, observation at the non-moving end of the flow creates the "one stop shop", so should be protected from the nefarious for person looking for intrastructure targets. Infrastructure information should be correct or maintenance assets may be inappropriately located, jeopardizing further uses, some of which involve safety. Without this flow, asset location based safety applications may not function properly. The availability rating should mirror the importance of that service to the deployer. Generally if an operator goes to the trouble to track assets in the field this way, they consider this important and so the flow should be satisfied. Note that if an operator has multiple methods for tracking assets in the field, one instance of this flow could probably be reduced to LOW with minimal effect on service performance.


Security Characteristics Value
Authenticable True
Encrypt True