# A tibble: 15 × 4
scanner prev_time scan_complete_time gap_hours
<chr> <dttm> <dttm> <dbl>
1 SS7834 2025-10-04 16:20:37 2025-10-23 17:28:54 457.
2 SS7834 2025-11-15 13:08:00 2025-11-30 07:17:30 354.
3 SS7833 2025-08-04 22:00:55 2025-08-16 14:21:02 280.
4 SS7834 2025-08-23 11:06:45 2025-09-03 17:42:13 271.
5 SS7834 2025-10-28 13:04:23 2025-11-07 00:28:33 227.
6 SS7834 2025-07-29 10:49:05 2025-08-07 12:49:41 218.
7 SS7834 2025-09-17 00:40:53 2025-09-25 18:35:35 210.
8 SS7834 2025-06-17 23:24:45 2025-06-25 17:36:52 186.
9 SS7833 2025-11-08 04:30:51 2025-11-15 05:21:34 169.
10 SS7834 2025-06-28 19:00:41 2025-07-05 19:09:53 168.
11 SS7833 2025-11-16 06:02:52 2025-11-23 06:03:15 168.
12 SS7834 2025-07-10 19:50:06 2025-07-17 17:36:58 166.
13 SS7834 2025-06-03 23:56:42 2025-06-10 19:48:17 164.
14 SS7834 2025-09-26 10:12:51 2025-10-02 10:23:09 144.
15 SS7833 2025-06-05 20:47:42 2025-06-11 18:15:49 141.22 Downtime Detection
22.1 Why this matters
Long gaps between scans hint at downtime or operational pauses. Detecting and timestamping them supports maintenance planning and staffing adjustments.
22.2 Gap Detection (>4 hours)
22.3 Gap Distribution by Scanner
22.4 Interpretation Guide
- Large gaps clustered on one scanner point to hardware or workflow issues on that device; cross-check with maintenance logs.
- Gaps at predictable times (overnight) reflect planned idle periods; unexpected daytime gaps deserve review of staffing or loading.
- Track the count and total hours of downtime per week to see if interventions reduce unplanned idle time.
22.5 Transfer Error Downtimes
We also detect downtimes specifically caused by “No space left on device” errors in the scanner logs. These errors indicate a failure to transfer files to PACS, effectively stopping the workflow.
# A tibble: 6 × 7
scanner_name event_id start_time end_time error_count
<chr> <dbl> <dttm> <dttm> <int>
1 SS45134 3 2025-09-13 18:14:10 2025-09-15 10:02:06 46741
2 SS45328 3 2025-09-13 18:15:24 2025-09-15 10:02:04 46606
3 SS7833 2 2025-09-13 18:16:19 2025-09-15 09:28:49 14097
4 SS7834 2 2025-09-13 18:21:37 2025-09-15 09:28:49 28051
5 SS45134 7 2025-09-22 18:50:22 2025-09-23 09:42:04 16385
6 SS7834 6 2025-09-22 18:49:22 2025-09-23 08:57:56 16115
# ℹ 2 more variables: duration_hours <dbl>, reason <chr>22.5.1 Visualizing Transfer Error Downtimes
22.5.2 Timeline of Transfer Errors
