Automatic non-prod time for outages would be a layup for morale and getting a concrete KPI for IT systems.
Seriously IT fuckery is probably one of the biggest drags on production and sources of examiner stress. Career upper management at the office have gone to such great lengths to avoid measuring the actual impact (hiding behind "just flex around it") that it can only be called an active cover-up at this point
If Squires wants a way to both goose morale and get insight into how things are actually running at the office, putting in a time code for IT systems downtime and making it policy that outside of extraordinary situations it gets used when certain IT systems have trouble would be an easy easy win.
You could assign certain categories for outages based on their impact. Maybe for DAV/Search/OC 25% of affected time for degraded performance, 50% time if one is down, and 100% if two are down. VPN should be 100%, as should be any workstation hardware failure.
Waiting on hold should be a separate code because nobody can focus on anything else while that godawful hold loop is playing, at least until IT can implement an automatic "call me back when I am next in the queue" feature like many customer service lines have.