SU10: Center Maintenance
This service package supports maintenance of the computers, networks, video walls, and other information technology assets that are installed in a center to support center operations. Like other support service packages, this SP is drawn at a high level of abstraction so the basic interfaces and functionality associated with maintaining center IT assets can be applied to any center.
Relevant Regions: Australia, Canada, European Union, and United States
- Enterprise
- Functional
- Physical
- Goals and Objectives
- Needs and Requirements
- Sources
- Security
- Standards
- System Requirements
Enterprise
Development Stage Roles and Relationships
Installation Stage Roles and Relationships
Operations and Maintenance Stage Roles and Relationships
(hide)
Source | Destination | Role/Relationship |
---|---|---|
Center Maintainer | Center | Maintains |
Center Manager | Center | Manages |
Center Manager | Center Personnel | System Usage Agreement |
Center Owner | Center Maintainer | System Maintenance Agreement |
Center Owner | Center Manager | Operations Agreement |
Center Owner | Service Monitor System Maintainer | Maintenance Data Exchange Agreement |
Center Owner | Service Monitor System Owner | Information Provision Agreement |
Center Owner | Service Monitor System User | Service Usage Agreement |
Center Owner | Support Maintenance Equipment Maintainer | Maintenance Data Exchange Agreement |
Center Owner | Support Maintenance Equipment Owner | Information Provision Agreement |
Center Owner | Support Maintenance Equipment User | Service Usage Agreement |
Center Owner | Support Maintenance Personnel | Application Usage Agreement |
Center Personnel | Center | Operates |
Center Supplier | Center Owner | Warranty |
Service Monitor System Maintainer | Service Monitor System | Maintains |
Service Monitor System Manager | Service Monitor System | Manages |
Service Monitor System Owner | Center Maintainer | Maintenance Data Exchange Agreement |
Service Monitor System Owner | Center Owner | Information Provision Agreement |
Service Monitor System Owner | Center Personnel | Application Usage Agreement |
Service Monitor System Owner | Center User | Service Usage Agreement |
Service Monitor System Owner | Service Monitor System Maintainer | System Maintenance Agreement |
Service Monitor System Owner | Service Monitor System Manager | Operations Agreement |
Service Monitor System Supplier | Service Monitor System Owner | Warranty |
Support Maintenance Equipment Maintainer | Support Maintenance Equipment | Maintains |
Support Maintenance Equipment Manager | Support Maintenance Equipment | Manages |
Support Maintenance Equipment Manager | Support Maintenance Personnel | System Usage Agreement |
Support Maintenance Equipment Owner | Center Maintainer | Maintenance Data Exchange Agreement |
Support Maintenance Equipment Owner | Center Owner | Information Provision Agreement |
Support Maintenance Equipment Owner | Center Personnel | Application Usage Agreement |
Support Maintenance Equipment Owner | Center User | Service Usage Agreement |
Support Maintenance Equipment Owner | Support Maintenance Equipment Maintainer | System Maintenance Agreement |
Support Maintenance Equipment Owner | Support Maintenance Equipment Manager | Operations Agreement |
Support Maintenance Equipment Supplier | Support Maintenance Equipment Owner | Warranty |
Support Maintenance Personnel | Support Maintenance Equipment | Operates |
Functional
This service package includes the following Functional View PSpecs:
Physical
The physical diagram can be viewed in SVG or PNG format and the current format is SVG.SVG Diagram
PNG Diagram
Includes Physical Objects:
Physical Object | Class | Description |
---|---|---|
Center | Center | This general physical object is used to model core capabilities that are common to any center. |
Center Personnel | Center | 'Center Personnel' represent system operators and other personnel that work within a transportation center. This interface supports modeling of general human interactions that are common to any center. |
Service Monitor System | Support | The 'Service Monitor System' represents one or more center-based systems that provide monitoring, management and control services necessary to other applications and/or devices operating within the Connected Vehicle Environment. These support services enable other applications to provide transportation services. |
Support Maintenance Equipment | Support | '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. |
Support Maintenance Personnel | Support | 'Support Maintenance Personnel' represents technicians and IT personnel that support maintenance of information technology assets that support ITS. |
Includes Functional Objects:
Functional Object | Description | Physical Object |
---|---|---|
Center System Executive | 'Center System Executive' provides the operating system and executive functions that manage computer resources, user accounts, and installed applications. It provides security features and manages software installation and upgrade. | Center |
Center System Monitoring and Diagnostics | 'Center System Monitoring and Diagnostics' includes background self-tests, diagnostics, watchdog timers, and other hardware and software that monitors the operating condition of the center. The status of the center equipment and diagnostic information is provided to center operations personnel and maintenance personnel that may be operating remotely from the center. | Center |
SM Device Management | 'SM Device Management' provides the functions necessary to manage devices, including network management, operational status monitoring, and application performance monitoring. | Service Monitor System |
SME IT Maintenance | 'SME IT Maintenance' provides maintenance, diagnostics, and troubleshooting capabilities for information technology equipment that supports back office operations for intelligent transportation systems. It provides the capability to control and configure this equipment to support on-site installation, repair, and maintenance and remote software configuration and upgrade. It also provides service desk capabilities for IT assets, receiving service requests and providing service status updates as the requests are addressed and issues are resolved. | Support Maintenance Equipment |
Includes Information Flows:
Information Flow | Description |
---|---|
center equipment commands | System-level control commands issued to center equipment such as reset and remote diagnostics. |
center equipment configuration settings | Control settings and parameters that are used to configure center equipment. |
center equipment software install/upgrade | This flow supports installation and update of software residing in centers. It supports download and installation of center software, including executable code and associated support files. |
center equipment status | Reports from center equipment (computers, networks, video walls, etc.) which indicate current operational status. |
center fault data | Fault information that can be used to identify centers that require initialization, reconfiguration, or repair. This flow identifies the center, the nature of the fault, and associated error codes and diagnostic data. |
center operator data | Data presented to a center operator. This flow represents general status output and other data that broadly applies to transportation centers. |
center operator input | Input from a center operator. This flow represents operator input that broadly applies to transportation centers. |
center status | Represents the interactive monitoring of system operations by the Service Monitor. It includes device housekeeping/heartbeat monitoring and network monitoring information, the status of installed applications, and the configuration of managed devices. |
service maintenance request | Identification of central system service requiring repair and known information about the associated faults. |
service maintenance status | Current status of central system maintenance actions. |
support equipment status presentation | Presentation of operational status of support system equipment (computers, networks, etc.) to maintenance personnel. |
support personnel equipment input | User input from support system maintenance personnel that supports querying, controlling, and configuring support system equipment. |
Goals and Objectives
Associated Planning Factors and Goals
Planning Factor | Goal |
---|---|
H. Emphasize the preservation of the existing transportation system; | Maintain infrastructure asset system |
Associated Objective Categories
Objective Category |
---|
Preservation: Preserve Existing Infrastructure |
Associated Objectives and Performance Measures
Needs and Requirements
Need | Functional Object | Requirement | ||
---|---|---|---|---|
01 | Operating agencies need to be able to maintain the hardware and software assets installed in the center so that the assets continue to operate as designed. | Center System Monitoring and Diagnostics | 03 | The center shall allow center personnel to monitor the center status either locally or remotely. |
SME IT Maintenance | 02 | The support element shall provide an interface for support personnel to view outputs or provide inputs. | ||
02 | Operating agencies need to be able to monitor the status of center hardware assets in order to diagnose problems that may occur during operations. | Center System Monitoring and Diagnostics | 01 | The center shall have the capability to monitor the operating conditions of hardware in the center. |
03 | The center shall allow center personnel to monitor the center status either locally or remotely. | |||
SM Device Management | 08 | The service monitor system shall monitor the status of transportation centers. | ||
09 | The service monitor system shall notify transportation centers of any faults detected in the operational status of those transportation centers. | |||
SME IT Maintenance | 01 | The support element shall obtain diagnostic information from the center in order to diagnose problems identified in the center. | ||
03 | Operating agencies need to be able to reconfigure center assets as well as perform installation or upgrade of software used to support operations. | Center System Executive | 01 | The center shall include software operating systems and executive functions that manage computer resources, user accounts, and installed applications. |
02 | The center shall have the capability to install or upgrade software or hardware of the center. | |||
03 | The center shall provide the capability for center personnel to install or update software in the center. | |||
Center System Monitoring and Diagnostics | 02 | The center shall have the capability to monitor the operating conditions of software in the center | ||
04 | The center shall allow center personnel to control center hardware and software in order to install, repair, or upgrade center assets. | |||
SME IT Maintenance | 03 | The support element shall control and configure center equipment to support remote software installation, repair, and maintenance. |
Security
In order to participate in this service package, each physical object should meet or exceed the following security levels.
Physical Object Security | ||||
---|---|---|---|---|
Physical Object | Confidentiality | Integrity | Availability | Security Class |
Center | High | High | High | Class 5 |
Service Monitor System | High | High | High | Class 5 |
Support Maintenance Equipment | Moderate | High | High | Class 5 |
In order to participate in this service package, each information flow triple should meet or exceed the following security levels.
Information Flow Security | |||||
---|---|---|---|---|---|
Source | Destination | Information Flow | Confidentiality | Integrity | Availability |
Basis | Basis | Basis | |||
Center | Center Personnel | center operator data | High | High | High |
Direct interactions between personnel and systems in a backoffice environment are effectively protected by physical means, so long as the interaction is in a dedicated facility. If this interaction is virtual (i.e. ,the center is not directly in front of the Center Personnel, like in a cloud-based system) then the user's input requires some degree of obfuscation depending on sensitivity of information. Given that this could include information about compromised or ineffectual systems, including security systems, the potential for damage is high. Thus, HIGH. | Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. | Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. | |||
Center | Service Monitor System | center status | High | High | High |
System operational status information could be used to either initiate or confirm attacks, leading to significant downtime of related C-ITS systems. | System status information needs the greatest possible correctness, as if it is incorrect then inappropriate actions may be triggered that, for large backoffice and core systems, have widespread repurcussions. | Monitoring of system operational status has the highest possible needs for availability, as without an understanding of system state it is difficult to impossible to manage the system. | |||
Center | Support Maintenance Equipment | center equipment status | Moderate | Moderate | Moderate |
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. | |||
Center | Support Maintenance Equipment | service maintenance request | Moderate | Moderate | Moderate |
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. | |||
Center Personnel | Center | center operator input | High | High | High |
Direct interactions between personnel and systems in a backoffice environment are effectively protected by physical means, so long as the interaction is in a dedicated facility. If this interaction is virtual (i.e. ,the center is not directly in front of the Center Personnel, like in a cloud-based system) then the user's input requires some degree of obfuscation depending on sensitivity of information. Given that this could include information about compromised or ineffectual systems, including security systems, the potential for damage is high. Thus, HIGH. | Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. | Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. | |||
Service Monitor System | Center | center fault data | Moderate | Moderate | Moderate |
Device status information should not be viewable by third parties, as those with criminal intent may use this information toward their own ends. | If incorrect or changed, could lead to inappropriate maintenance activity, which has a significant cost in itself and contributes negatively to system operational status. Scope is small, but impact significant if this occurs with many instances. | A delay in reporting this may cause a delay in necessary maintenance. Considered higher availability requirement than the source flow (RSE status) because this information aggregates many instances of the source. | |||
Support Maintenance Equipment | Center | center equipment commands | Moderate | High | High |
Commands could be sensitive and should include authentication data, thus should be MODERATE. | Commands to Centers must be authenticated as having come from a source entitled to issue that command, or roadway equipment may be comprimised. Similarly, commands and configuration must be guaranteed to be correct; not manipulated midstream or corrupted, or the center may be mis-configured or compromised. Considered HIGH as opposed to MODERATE because the operational scope of a Center is typically quite large compared to a Field device. | Without the ability to locally diagnose, operate, update and configure Center Equipment, the equipment is effectively out of control and would have to be taken out of service. | |||
Support Maintenance Equipment | Center | center equipment configuration settings | Moderate | High | High |
Commands could be sensitive and should include authentication data, thus should be MODERATE. | Center system control, configuration and update need to be correct or the center may be misconfigured, which for some applications could have severe safety impacts. If the center has no safety-related functions, or little impact on regional mobility, this could be MODERATE. | Without the ability to locally diagnose, operate, update and configure Center system Equipment, the Center is effectively out of control and would have to be taken out of service. | |||
Support Maintenance Equipment | Center | center equipment software install/upgrade | Moderate | High | Moderate |
Equipment software is sensitive and should include authentication data, thus should be MODERATE. | Software updates to Center components must be authenticated as having come from a source entitled to provide that software, or roadway equipment may be comprimised. Similarly, such software must be guaranteed to being the intent of the originator; not manipulated midstream or corrupted, or the roadway equipment may be mis-configured or compromised. | The ability to remotely update and configure software is inherent to their successful operation. If this link is down it either suggests or will prompt field maintenance activity, which has a non-trivial cost and resource impact. | |||
Support Maintenance Equipment | Center | service maintenance status | Moderate | Moderate | Moderate |
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. | |||
Support Maintenance Equipment | Support Maintenance Personnel | support equipment status presentation | Moderate | Moderate | High |
System maintenance flows should have some protection from casual viewing, as otherwise imposters could gain illicit control over field equipment | 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. | |||
Support Maintenance Personnel | Support Maintenance Equipment | support personnel equipment input | Moderate | Moderate | High |
System support flows should have some protection from casual viewing, as otherwise imposters could gain illicit control over support equipment or the equipment managed by the support equipment. | System support flows are the primary interface between support personnel and support equipment, and must present accurate data or inappropriate support actions may be taken. | System support flows are the primary interface between support personnel and support equipment, and must present accurate data or inappropriate support actions may be taken. |
Standards
Currently, there are no standards associated with the physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages.
System Requirements
System Requirement | Need | ||
---|---|---|---|
001 | The system shall include software operating systems and executive functions that manage computer resources, user accounts, and installed applications. | 03 | Operating agencies need to be able to reconfigure center assets as well as perform installation or upgrade of software used to support operations. |
002 | The system shall have the capability to install or upgrade software or hardware of the center. | 03 | Operating agencies need to be able to reconfigure center assets as well as perform installation or upgrade of software used to support operations. |
003 | The system shall provide the capability for center personnel to install or update software in the center. | 03 | Operating agencies need to be able to reconfigure center assets as well as perform installation or upgrade of software used to support operations. |
004 | The system shall have the capability to monitor the operating conditions of hardware in the center. | 02 | Operating agencies need to be able to monitor the status of center hardware assets in order to diagnose problems that may occur during operations. |
005 | The system shall have the capability to monitor the operating conditions of software in the center | 03 | Operating agencies need to be able to reconfigure center assets as well as perform installation or upgrade of software used to support operations. |
006 | The system shall allow center personnel to monitor the center status either locally or remotely. | 01 | Operating agencies need to be able to maintain the hardware and software assets installed in the center so that the assets continue to operate as designed. |
02 | Operating agencies need to be able to monitor the status of center hardware assets in order to diagnose problems that may occur during operations. | ||
007 | The system shall allow center personnel to control center hardware and software in order to install, repair, or upgrade center assets. | 03 | Operating agencies need to be able to reconfigure center assets as well as perform installation or upgrade of software used to support operations. |
008 | The system shall monitor the status of transportation centers. | 02 | Operating agencies need to be able to monitor the status of center hardware assets in order to diagnose problems that may occur during operations. |
009 | The system shall notify transportation centers of any faults detected in the operational status of those transportation centers. | 02 | Operating agencies need to be able to monitor the status of center hardware assets in order to diagnose problems that may occur during operations. |
010 | The system shall obtain diagnostic information from the center in order to diagnose problems identified in the center. | 02 | Operating agencies need to be able to monitor the status of center hardware assets in order to diagnose problems that may occur during operations. |
011 | The system shall provide an interface for support personnel to view outputs or provide inputs. | 01 | Operating agencies need to be able to maintain the hardware and software assets installed in the center so that the assets continue to operate as designed. |
012 | The system shall control and configure center equipment to support remote software installation, repair, and maintenance. | 03 | Operating agencies need to be able to reconfigure center assets as well as perform installation or upgrade of software used to support operations. |