Last business day of January 2025 · Target: Jan 31, 2025
⚠ 254 biz days overdue
Active: 274 biz days
Paused: 177 biz days
236d
▶ Clock Running
Status: Created
Jan 2 → Dec 12, 2025
236 business days (counted)
Running total: 236 of ? biz days used
⏸163d
⏸ Clock Paused
Status: Ready for Release
Dec 12 → Aug 7, 2026
163 business days (not counted)
▶ Clock Running
Status: Scheduled
Aug 7 → Aug 13, 2026
4 business days (counted)
Running total: 240 of ? biz days used
▶ Clock Running
Status: Entered
Aug 13 → Aug 13, 2026
0 business days (counted)
Running total: 240 of ? biz days used
⏸ Clock Paused
Status: Ready for Release
Aug 13 → Sep 2, 2026
14 business days (not counted)
▶ Clock Running
Status: Ready for Scheduling
Sep 2 → Oct 22, 2026
34 business days (counted)
Running total: 274 of ? biz days used
Created: Jan 2, 2025Today
Show SLA Clock Detail (6 periods)
Period
Status
Clock
Biz Days
Running Total
Jan 2 → Dec 12
Created
▶ Running
236
236
Dec 12 → Aug 7
Ready for Release
⏸ Paused
163
—
Aug 7 → Aug 13
Scheduled
▶ Running
4
240
Aug 13 → Aug 13
Entered
▶ Running
0
240
Aug 13 → Sep 2
Ready for Release
⏸ Paused
14
—
Sep 2 → Oct 22
Ready for Scheduling
▶ Running
34
274
Holding415.1d (excluded)
Coordinators5.0d
⚠ Overdue
Holding(excluded from total)
415.1 days
Coordinators
5.0 days
Over SLA
Created: Jan 2, 2025
Due: Dec 31, 2026 (70 days left)
📅
451.3 daysTotal Age
⏱️
236.5d in On HoldLongest Stage
🔄
4 transitionsStatus Changes
⚠️
3.0d overTotal Delay
📦
0 orders, 0 quotesParts & Quotes
📝
0 linesWork Details
AI Analysis
Powered by OpenAI
Generating AI analysis...
On Track
Ready for Scheduling • 657 days old
🚨
Primary Delay236.5 days stuck in "On Hold"
⏱️
Total Delay3.0 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
178.7d
Scheduled
5.0d / 2.0d SLA
💬 Activities, Notes & Communications
🔒Internal CSA Notes
10/19 KKelch called Ashlie to schedule for 10/27 due to tech availability with arrival between 8 and 10 am. Left VM. Call logged on WO-01435501
10/19/2026jsells
left a voicemail with the work order number and I let the customer know that someone would be calling to schedule the visit
⚠️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:14 PM
Work Order:WO-01232495
Type:Preventive Maintenance
Priority:PSM
🚨237.0 business days
✅
Status: Ready for Release by Stephanie RamenDec 12, 1:08 PM