Standard 7: Change Management
| Revision Number: | 1 |
|
| Effective Date: | 2/24/2020 | |
| Revised Date: | 2/24/2020 | |
| Review Date: | 2/24/2020 | |
|
Responsible Division/Department:
Office of the CIO / Information Technology Services |
||
- The university's infrastructure is constantly changing and evolving to support the mission of the university. Computer networks, systems, and applications require planned outages for upgrades, maintenance, and fine-tuning.
- UNF ITS has a defined maintenance window every Sunday morning from 5 AM - 9 AM in which normal maintenance occurs.
- All changes to technology are to be tracked in the UNF ITS ticketing system. Changes should use change templates where applicable to ensure all UNF parties are at least aware of changes. Examples include: Changes to group policy or client computer settings, changes to AD groups, changes to networks, changes to firewall rules, server decommissioning, employee termination, etc.
- Significant changes to systems are to be documented in the UNF ITS Change Management system. Significant changes include but are not limited to changes that: are not routine, could impact dependent services or systems managed by other teams, or impact large user audiences such as all students or employees.
- All changes should be added to the system at least 1 week before the scheduled change.
- ITS management should review the changes at least weekly and document their review of the change.
- Any outstanding questions should be resolved before moving forward with the change.