Field --> Field Maintenance Equipment:
field equipment status

Definitions

field equipment status (Information Flow): Reports from field equipment (sensors, signals, signs, controllers, etc.) which indicate current operational status.

Field (Source Physical Object): This general physical object is used to model core capabilities that are common to any piece of field equipment.

Field Maintenance Equipment (Destination Physical Object): 'Field Maintenance Equipment' represents the portable equipment used by field personnel to locally troubleshoot, initialize, reprogram, and test infrastructure equipment. It may include a laptop, specialized diagnostics tools, or any other general purpose or specialized equipment that is interfaced locally to infrastructure equipment to support maintenance and repair.

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

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

Selected Solution

US: NTCIP Generic Device - SNMPv3/TLS

Solution Description

This solution is used within Canada and the U.S.. It combines standards associated with US: NTCIP Generic Device with those for I-F: SNMPv3/TLS. The US: NTCIP Generic Device standards include upper-layer standards required to implement center-to-field communications for any device functionality. The I-F: SNMPv3/TLS standards include lower-layer standards that support secure center-to-field and field-to-field communications using simple network management protocol (SNMPv3); implementations are strongly encouraged to use the TLS for SNMP security option for this solution to ensure adequate security.

ITS Application Entity
Click gap icons for more info.
Mgmt

NTCIP 1201
Bundle: SNMPv3 MIB
Facilities
Mind the gap
Security
Mind the gapMind the gap

IETF RFC 6353
IETF RFC 9456
TransNet
Access
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 Regional
Acknowledgement True
Cardinality Unicast
Initiator Destination
Authenticable True
Encrypt False


Interoperability Description
Local In cases where an interface is normally encapsulated by a single stakeholder, interoperability is still desirable, but the motive is vendor independence and the efficiencies and choices that an open standards-based interface provides.

Security

Information Flow Security
  Confidentiality Integrity Availability
Rating Low Moderate High
Basis The operational state of field devices, if known to an attacker or individual with criminal intent, could be used to facilitate the commission of a crime. Individual devices may be more or less important in this context; for example knowing whether a security camera is operating is probably more relevant to the criminal than knowing if the DMS is operating, though the latter could still be useful info. Instances of this flow that are local minimize this risk however, so for these local flows Confidentiality is considered LOW. If incorrect or changed, could lead to inappropriate maintenance activity, which has a significant cost in itself and contributes negatively to system operational status. This must be timely to support operational uptime requirements. Lack of monitoring will lead to less uptime, which will impact security, mobility and in some cases, safety.


Security Characteristics Value
Authenticable True
Encrypt False