Purpose
This procedure provides information for IT or System Admins to maintain servers to support proper function of AVL system. The procedure provides steps for non-hosted and Avail hosted solutions.
Operational Impact and Metrics
Operational Impact: This procedure should be administered to ensure the health of the IT infrastructure stays up to date. Failure to conduct this procedure could lead to system performance issues, system down time, and the inability for the Avail Customer Support team to provide remote troubleshooting.
Metrics: Microsoft Windows Updates Log, PRTG Sensors
Definitions
| ITS | Intelligent Transportation Systems |
| CAD/AVL | Computer-Aided Dispatch and Automatic Vehicle Location |
| RAM | Random Access Memory |
| OS | Operating System |
| PRTG | Paessler Router Traffic Grapher |
Frequency
Monthly. See other details in section VI.
Roles and Responsibilities
Implementation of these procedures is the responsibility of transit agency staff involved in system administration and/or information technology.
Procedure
Non-Hosted Solutions:
- Ensure Avail Support has remote access to locally installed Avail Servers
- Microsoft Windows updates to be completed by Transit Agency staff (quarterly)
- Ensure all Avail ITS Servers are behind a firewall (continuously)
- Review critical hardware manufacturers’ warranty and support contracts
- Monitor hardware for potential failures (i.e. Raid hard drives)
- Ensure server technical capabilities are adequate to support the Avail load and meet Avail standards (annually, and any time hardware is updated)
Hosted Solutions:
- Servers are monitored and all maintenance is conducted by Avail
Supporting Documents
- Hardware Technical Specifications
- Related SOPs