Explicitly Track Maintenance (vs OFF)

[slominskir]

Each NPES schedule supplementary memo provides an allowance for non-physics accelerator activities including beam studies, tuning, and maintenance. We don't currently track maintenance explicitly, leading to confusion and a complicated calculation of performance in the Joule report requiring manual intervention and out-of-band maintenance tracking. We also don't fullly/completely track tuning, but that's in #33.

We currently track both scheduled maintenance and OFF together as a single metric named Scheduled Accelerator Maintenance (SAM) in BTM. This isn't quite right. When we're OFF because we simply aren't on the NPES schedule to run isn't the same as OFF because we're doing scheduled maintenance per the NPES allowance.

Often (but not always) we have a weekly Wednesday maintenance day cadence. This is often where our allowance goes, and in this case it's recorded on the Crew Chief timesheet as SAM. However, since the accelerator division has the flexibility to schedule maintenance at any time, without advanced warning, and even retroactively (and even bankable), it follows that maintenance time can also be used to subtract downtime. The Joule report (Choose... option) allows dynamic input of maintenance hours to accomplish this. BTM doesn't track how much maintenance we have used up in maintenance days though, so this enhancement is to add a new dedicated column for it, and make a distinction with OFF / Not Scheduled.

A few nuances:

1. The SAM Calendar doesn't make a distinction between OFF because we're not scheduled by NPES and OFF because we're scheduled for maintenance by NPES. In some sense the accelerator is always in maintenance mode when not scheduled to run, but there is a distinction made by NPES and therefore in the Joule report. We may need to rename the calendar app since it often covers both time periods (any form of OFF, scheduled maintenance or not).

2. We'd need to update the SAM definition to indicate that if we're OFF because of NPES schedule (not for maintenance), then that's just the OFF metric. SAM currently is defined to allow for both.

3. We may want to allow configurating the total banked allowances for beam studies, tuning, and maintenance per run directly in BTM. We could do this in the setup tab and expose this in the Joule report. This would allow us to simplify the Joule report by fully automating the allowance calculations. Could even report how much we went over the allowance and add downtime. Might fold this into the runs configuration Runs cache is not automated #3.