Summary
Pitt Information Technology partners with outside vendors to provide reliable, secure computing experiences at the University. These vendors can require regular maintenance periods to ensure the strength of their infrastructure, security, and data. This maintenance can occasionally mean downtime and unavailability for brief time spans.
Body
Overview
Pitt Information Technology partners with outside vendors to provide reliable, secure computing experiences at the University. As part of vendor-recommended best practices to ensure the continued security, stability, and reliability of our systems, the University denotes a regularly scheduled downtime period or window for outages that takes place weekly – usually from ~11 p.m. on a Friday or Saturday night until ~7 a.m. on the next one to two days. During these downtime periods, the University services and systems scheduled for maintenance may be inaccessible.
Detail
2025 Tentative Schedule of Planned Outages
These planned maintenance periods are subject to change.
| Service |
Start Date |
Start Time |
End Date |
End Time |
Outage Type |
| Pitt Worx |
Fri., Jan. 17 |
10 p.m. |
Sun., Jan 19 |
7 a.m. |
Payroll Legislative Patches, 2 Year End, Year Begin |
| Student Information System (PeopleSoft) |
Sat., Jan. 18 |
11 p.m. |
Sun., Jan.19 |
7 a.m. |
Routine |
| Student Information System (PeopleSoft) |
Sat., Feb. 8 |
11 p.m. |
Sun., Feb.9 |
7a.m. |
Routine |
| Pitt Worx |
Fri., Feb. 21 |
10 p.m. |
Sun., Feb. 23 |
7 p.m. |
Releases, 25A |
| Student Information System (PeopleSoft) |
Sat., Mar. 8 |
11 p.m. |
Sun., Mar. 9 |
7 a.m. |
Routine |
| Pitt Worx |
Fri., Mar. 21 |
10 p.m. |
Sun., Mar 23 |
7 a.m. |
Payroll Legislative Patches, 3 Quarter End |
| Student Information System (PeopleSoft) |
Sat., Apr. 5 |
11 p.m. |
Sun., Apr. 6 |
7 a.m. |
Routine |
| Student Information System (PeopleSoft) |
Sat., May 10 |
11 p.m. |
Sun., May 11 |
7 a.m. |
Routine |
| Pitt Worx |
Fri., May 16 |
10 p.m. |
Sun., May 18 |
7p.m. |
Releases, 25B |
| Student Information System (PeopleSoft) |
Sat., June 14 |
11 p.m. |
Sun., June 15 |
7 a.m. |
Routine |
| Pitt Worx |
Fri., June 20 |
10 p.m. |
Sun. June 22 |
7 a.m. |
Payroll Legislative Patches, 3 Quarter End |
| Student Information System (PeopleSoft) |
Fri., June 20 |
12:00 a.m. |
Sun., June 22 |
11:59 p.m. |
PeopleTools Upgrade/Update Image |
| Student Information System (PeopleSoft) |
Sat., July 12 |
11 p.m. |
Sun., July 13 |
7 a.m. |
Routine |
| Student Information System (PeopleSoft) |
Sat., August 9 |
11 p.m. |
Sun., Aug. 10 |
7 a.m. |
Routine |
| Pitt Worx |
Fri., Aug. 15 |
10 p.m. |
Sun., Aug. 17 |
7 p.m. |
Releases, 25C |
| Student Information System (PeopleSoft) |
Sat., Sept. 13 |
11 p.m. |
Sun., Sept. 14 |
7 a.m. |
Routine |
| Pitt Worx |
Fri., Sept. 19 |
10 p,m. |
Sun., Sept. 21 |
7 a.m. |
Payroll Legislative Patches, 3 Quarter End |
| Student Information System (PeopleSoft) |
Sat., Sept. 20 |
11 p.m. |
Sun., Sept. 21 |
7 a.m. |
Update Image |
| Student Information System (PeopleSoft) |
Sat., Oct. 11 |
11 p.m. |
Sun., Oct. 12 |
7 a.m. |
Routine |
| Student Information System (PeopleSoft) |
Sat., Nov. 15 |
11 p.m. |
Sun., Nov. 16 |
7 a.m. |
Routine |
| Pitt Worx |
Fri., Nov. 21 |
10 p.m. |
Sun., Nov. 23 |
7 p.m. |
Releases, 25D and Payroll Legislative Patches, 2 Year End, Year Begin |
| Student Information System (PeopleSoft) |
Sat., Nov. 22 |
11 p.m. |
Sun., Nov. 23 |
7 a.m. |
Update Image |
| Pitt Worx |
Fri., Dec. 19 |
10 p.m. |
Sun., Dec. 21 |
7 a.m. |
Payroll Legislative Patches, 1 Year End |
| Student Information System (PeopleSoft) |
Sat., Dec. 20 |
11 p.m. |
Sun., Dec. 21 |
7 a.m. |
Routine |
Types of Scheduled Maintenance
Routine/Quarterly
These pro-active maintenance periods are performed monthly and/or quarterly to proactively address the security, stability, and reliability of the service or system.
Image Update
Usually a quarterly maintenance, Image Updates are application-specific, and address bug-fixes, financial aid regulatory updates, and enhancements to a service or system.
Non-Routine
Non-Routine maintenance is scheduled as needed, with as much advance notice as possible. It may include time-sensitive critical patches, database enhancements, or necessary upgrades.