Center --> Support Maintenance Equipment:
center equipment status
Definitions
center equipment status (Information Flow): Reports from center equipment (computers, networks, video walls, etc.) which indicate current operational status.
Center (Source Physical Object): This general physical object is used to model core capabilities that are common to any center.
Support Maintenance Equipment (Destination Physical Object): 'Support Maintenance Equipment' represents the equipment used by IT personnel and technicians to locally or remotely troubleshoot, initialize, reprogram, and test IT assets that support ITS operations. It also manages service activities for IT assets, accepting service requests and providing service status as maintenance activities and repairs are scheduled and performed. It may include a workstation, laptop, trouble-ticket or other maintenance tracking software, specialized diagnostics tools, or any other general purpose or specialized equipment that is interfaced remotely or locally to support maintenance, repair, and upgrade.
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
No communications solutions identified.Characteristics
Characteristic | Value |
---|---|
Time Context | Recent |
Spatial Context | Regional |
Acknowledgement | True |
Cardinality | Unicast |
Initiator | Source |
Authenticable | True |
Encrypt | True |
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 | Moderate | Moderate | Moderate | |
Basis | The operational state of center systems, if known to an attacker or individual with criminal intent, could be used to facilitate the commission of a crime. Individual centers may be more or less important in this context; for example knowing whether a traffic management center is operating is probably more relevant to the criminal than knowing if a weather information center 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 | True |