Center --> Support Maintenance Equipment:
service maintenance request
Definitions
service maintenance request (Information Flow): Identification of central system service requiring repair and known information about the associated faults.
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:
Relationship | Source | Destination | Flow |
---|---|---|---|
Interactive | Support Maintenance Equipment | Center | service maintenance status |
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 | Device operational status information should be known only by those entities that need to know for operations and maintenance. Allowing others to read this information may enable abuse of those systems, 3rd party monitoring of system status when that may not be desireable, and reverse engineering of this and similar information flows. | If this data is incorrect or unavailable then maintenance assets may not be appropriately assigned, systems may not be repaired on time, resulting in inefficient use of maintenance assets and higher overall downtime. | If this data is incorrect or unavailable then maintenance assets may not be appropriately assigned, systems may not be repaired on time, resulting in inefficient use of maintenance assets and higher overall downtime. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |