Field --> Personnel Device:
asset ID
Definitions
asset ID (Information Flow): A unique identification number and optional additional information. This flow represents the output of an RFID tag that is used for identification and tracking of assets, including both passive and active RFID tag technology options. For active tags, additional stored information that conveys additional information about the asset (e.g., lot number, production date, service data) may be provided along with the unique ID.
Field (Source Physical Object): This general physical object is used to model core capabilities that are common to any piece of field equipment.
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:
None |
Communication Solutions
- Proprietary Data - Proprietary Comm (16)
- (None-Data) - BTP/GeoNetworking/G5 (42)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
ETSI 302 890-1 Addressed Elsewhere |
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 | Static |
Spatial Context | Adjacent |
Acknowledgement | False |
Cardinality | Broadcast |
Initiator | Destination |
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 | Unlikely that the ID of a particular asset, or even a group of assets would be useful to an attacker. Slight possibility, which is why Low vs. N/A. | Infrastructure information should be correct or maintenance assets may be inappropriately assigned, located or otherwise referenced. | 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 | False |