Personnel Device --> Maint and Constr Management Center:
asset locations
Definitions
asset locations (Information Flow): Aggregate collected data including identified assets and their locations.
Personnel Device (Source 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.
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:
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:
Relationship | Source | Destination | Flow |
---|---|---|---|
Depends On | Field | Personnel Device | asset ID |
Depends On | Maint and Constr Vehicle OBE | Personnel Device | asset locations |
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
Development needed |
Facilities
Development needed OASIS AMQP |
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 | 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 |