Last business day of January 2025 · Target: Jan 31, 2025
⚠ 277 biz days overdue
Active: 297 biz days
Paused: 107 biz days
236d
▶ Clock Running
Status: Created
Jan 2 → Dec 12, 2025
236 business days (counted)
Running total: 236 of ? biz days used
⏸ Clock Paused
Status: Ready for Release
Dec 12 → Jan 14, 2026
21 business days (not counted)
▶ Clock Running
Status: Assigned
Jan 14 → Jan 23, 2026
6 business days (counted)
Running total: 242 of ? biz days used
▶ Clock Running
Status: Scheduled
Jan 23 → Mar 4, 2026
27 business days (counted)
Running total: 269 of ? biz days used
▶ Clock Running
Status: Reschedule
Mar 4 → Mar 31, 2026
19 business days (counted)
Running total: 288 of ? biz days used
▶ Clock Running
Status: Entered
Mar 31 → Mar 31, 2026
0 business days (counted)
Running total: 288 of ? biz days used
⏸ Clock Paused
Status: Ready for Release
Mar 31 → Apr 29, 2026
21 business days (not counted)
▶ Clock Running
Status: Assigned
Apr 29 → May 1, 2026
2 business days (counted)
Running total: 290 of ? biz days used
▶ Clock Running
Status: Entered
May 1 → May 1, 2026
0 business days (counted)
Running total: 290 of ? biz days used
⏸ Clock Paused
Status: Ready for Release
May 1 → May 6, 2026
3 business days (not counted)
▶ Clock Running
Status: Assigned
May 6 → May 6, 2026
0 business days (counted)
Running total: 290 of ? biz days used
▶ Clock Running
Status: Scheduled
May 6 → May 6, 2026
0 business days (counted)
Running total: 290 of ? biz days used
▶ Clock Running
Status: Entered
May 6 → May 6, 2026
0 business days (counted)
Running total: 290 of ? biz days used
⏸ Clock Paused
Status: Ready for Release
May 6 → May 13, 2026
5 business days (not counted)
▶ Clock Running
Status: Assigned
May 13 → May 13, 2026
0 business days (counted)
Running total: 290 of ? biz days used
▶ Clock Running
Status: Entered
May 13 → May 13, 2026
0 business days (counted)
Running total: 290 of ? biz days used
⏸ Clock Paused
Status: Ready for Release
May 13 → May 21, 2026
6 business days (not counted)
▶ Clock Running
Status: Assigned
May 21 → May 21, 2026
0 business days (counted)
Running total: 290 of ? biz days used
▶ Clock Running
Status: Entered
May 21 → May 21, 2026
0 business days (counted)
Running total: 290 of ? biz days used
⏸ Clock Paused
Status: Ready for Release
May 21 → May 27, 2026
3 business days (not counted)
▶ Clock Running
Status: Assigned
May 27 → May 27, 2026
0 business days (counted)
Running total: 290 of ? biz days used
▶ Clock Running
Status: Scheduled
May 27 → May 28, 2026
1 business day (counted)
Running total: 291 of ? biz days used
▶ Clock Running
Status: Entered
May 28 → May 28, 2026
0 business days (counted)
Running total: 291 of ? biz days used
⏸ Clock Paused
Status: Ready for Release
May 28 → Jun 23, 2026
17 business days (not counted)
▶ Clock Running
Status: Assigned
Jun 23 → Jun 23, 2026
0 business days (counted)
Running total: 291 of ? biz days used
▶ Clock Running
Status: Scheduled
Jun 23 → Jun 30, 2026
5 business days (counted)
Running total: 296 of ? biz days used
▶ Clock Running
Status: Entered
Jun 30 → Jun 30, 2026
0 business days (counted)
Running total: 296 of ? biz days used
⏸ Clock Paused
Status: Ready for Release
Jun 30 → Jul 31, 2026
22 business days (not counted)
▶ Clock Running
Status: Assigned
Jul 31 → Jul 31, 2026
0 business days (counted)
Running total: 296 of ? biz days used
▶ Clock Running
Status: Scheduled
Jul 31 → Aug 3, 2026
1 business day (counted)
Running total: 297 of ? biz days used
▶ Clock Running
Status: Entered
Aug 3 → Aug 3, 2026
0 business days (counted)
Running total: 297 of ? biz days used
⏸ Clock Paused
Status: Ready for Release
Aug 3 → Aug 14, 2026
9 business days (not counted)
Created: Jan 2, 2025Today
Show SLA Clock Detail (32 periods)
Period
Status
Clock
Biz Days
Running Total
Jan 2 → Dec 12
Created
▶ Running
236
236
Dec 12 → Jan 14
Ready for Release
⏸ Paused
21
—
Jan 14 → Jan 23
Assigned
▶ Running
6
242
Jan 23 → Mar 4
Scheduled
▶ Running
27
269
Mar 4 → Mar 31
Reschedule
▶ Running
19
288
Mar 31 → Mar 31
Entered
▶ Running
0
288
Mar 31 → Apr 29
Ready for Release
⏸ Paused
21
—
Apr 29 → May 1
Assigned
▶ Running
2
290
May 1 → May 1
Entered
▶ Running
0
290
May 1 → May 6
Ready for Release
⏸ Paused
3
—
May 6 → May 6
Assigned
▶ Running
0
290
May 6 → May 6
Scheduled
▶ Running
0
290
May 6 → May 6
Entered
▶ Running
0
290
May 6 → May 13
Ready for Release
⏸ Paused
5
—
May 13 → May 13
Assigned
▶ Running
0
290
May 13 → May 13
Entered
▶ Running
0
290
May 13 → May 21
Ready for Release
⏸ Paused
6
—
May 21 → May 21
Assigned
▶ Running
0
290
May 21 → May 21
Entered
▶ Running
0
290
May 21 → May 27
Ready for Release
⏸ Paused
3
—
May 27 → May 27
Assigned
▶ Running
0
290
May 27 → May 28
Scheduled
▶ Running
1
291
May 28 → May 28
Entered
▶ Running
0
291
May 28 → Jun 23
Ready for Release
⏸ Paused
17
—
Jun 23 → Jun 23
Assigned
▶ Running
0
291
Jun 23 → Jun 30
Scheduled
▶ Running
5
296
Jun 30 → Jun 30
Entered
▶ Running
0
296
Jun 30 → Jul 31
Ready for Release
⏸ Paused
22
—
Jul 31 → Jul 31
Assigned
▶ Running
0
296
Jul 31 → Aug 3
Scheduled
▶ Running
1
297
Aug 3 → Aug 3
Entered
▶ Running
0
297
Aug 3 → Aug 14
Ready for Release
⏸ Paused
9
—
Holding341.0d (excluded)
Coordinators66.4d
⚠ Overdue
Holding(excluded from total)
341.0 days
Coordinators
66.4 days
Over SLA
Created: Jan 2, 2025
Due: Dec 31, 2026 (139 days left)
📅
404.5 daysTotal Age
⏱️
236.5d in On HoldLongest Stage
🔄
22 transitionsStatus Changes
⚠️
54.8d overTotal Delay
📦
0 orders, 0 quotesParts & Quotes
📝
0 linesWork Details
AI Analysis
Powered by OpenAI
Generating AI analysis...
Behind Schedule - Needs Attention
Ready for Release • 588 days old
🚨
Primary Delay236.5 days stuck in "On Hold"
⏱️
Total Delay54.8 business days over SLA thresholds
SLA vs Actual Time by Status
Actual (within SLA)
Actual (over SLA)
SLA Target
On Hold
236.5d
Ready for Release
104.5d
Assigned
10.1d / 0.5d SLA
Scheduled
37.8d / 2.0d SLA
Reschedule
18.5d / 2.0d SLA
💬 Activities, Notes & Communications
🔒Internal CSA Notes
6/30/26 RBerry- Placed WO back into RFR due to repairs.
⚠️Problem Description
Please Perform PM: PM Checklist can be found as a link in the work order under WO actions
If Kiosk is not on the Sales floor request to speak to a manager to find out if kiosk is being stored in the back room or if it was disposed. Offer to help bring the kiosk to the salesfloor or advise that EMSAR can replace a disposed kiosk. If store does not want to bring the kiosk out of storage or if kiosk was disposed, close out work order with Repair code '37 Store intervention required' and document who you spoke with and outcome of conversation. Labor line shall be a trip charge.
***Important: Please make sure to document if kiosk is disposed or in storage***
If kiosk fails a PM, checklist is still required to be completed. Please use Code 35 - Follow up needed and detail in the Tech Findings, Work Performed and Final condition the result and cause for a follow up. Close out the work order. Dispatch will create a follow up repair work order to send parts.
📄Description
Model 300 with Backboard
Timeline
📋
Work Order Created Jan 2, 3:16 PM
Work Order:WO-01233571
Type:Preventive Maintenance
Priority:PSM
🚨237.0 business days
✅
Status: Ready for Release by Stephanie RamenDec 12, 1:08 PM