Last business day of January 2025 · Target: Jan 31, 2025
✗ SLA Missed (70 biz days late)
Active: 91 biz days
Paused: 105 biz days
🕐 Clock stopped: Completed (Oct 14, 2025)
61d
▶ Clock Running
Status: Created
Jan 2 → Apr 1, 2025
61 business days (counted)
Running total: 61 of ? biz days used
⏸30d
⏸ Clock Paused
Status: Ready for Release
Apr 1 → May 13, 2025
30 business days (not counted)
▶ Clock Running
Status: Scheduled
May 13 → May 27, 2025
9 business days (counted)
Running total: 70 of ? biz days used
▶ Clock Running
Status: Reschedule
May 27 → Jun 4, 2025
6 business days (counted)
Running total: 76 of ? biz days used
▶ Clock Running
Status: Entered
Jun 4 → Jun 4, 2025
0 business days (counted)
Running total: 76 of ? biz days used
⏸75d
⏸ Clock Paused
Status: Ready for Release
Jun 4 → Sep 22, 2025
75 business days (not counted)
▶ Clock Running
Status: Assigned
Sep 22 → Sep 22, 2025
0 business days (counted)
Running total: 76 of ? biz days used
▶ Clock Running
Status: Scheduled
Sep 22 → Oct 14, 2025
15 business days (counted)
Running total: 91 of ? biz days used
▶ Clock Running
Status: Tech On Site
Oct 14 → Oct 14, 2025
0 business days (counted)
Running total: 91 of ? biz days used
Created: Jan 2, 2025Completed: Oct 14, 2025
Show SLA Clock Detail (9 periods)
Period
Status
Clock
Biz Days
Running Total
Jan 2 → Apr 1
Created
▶ Running
61
61
Apr 1 → May 13
Ready for Release
⏸ Paused
30
—
May 13 → May 27
Scheduled
▶ Running
9
70
May 27 → Jun 4
Reschedule
▶ Running
6
76
Jun 4 → Jun 4
Entered
▶ Running
0
76
Jun 4 → Sep 22
Ready for Release
⏸ Paused
75
—
Sep 22 → Sep 22
Assigned
▶ Running
0
76
Sep 22 → Oct 14
Scheduled
▶ Running
15
91
Oct 14 → Oct 14
Tech On Site
▶ Running
0
91
Holding168.3d (excluded)
Coordinators30.9d
Field Work0.1d
Billing15.0d
✗ SLA Missed
Holding(excluded from total)
168.3 days
Coordinators
30.9 days
Over SLA
Field Work
0.1 days
Billing
15.0 days
Over SLA
Created: Jan 2, 2025
Due: Dec 31, 2025
Completed: Oct 14, 2025 (78 days early)
📅
195.8 daysTotal Age
⏱️
75.9d in Ready for ReleaseLongest Stage
🔄
10 transitionsStatus Changes
⚠️
38.9d overTotal Delay
📦
0 orders, 0 quotesParts & Quotes
📝
5 linesWork Details
🏠
1 visitOn-Site Trips
👤
Self-ScheduledScheduling
AI Analysis
Powered by OpenAI
Generating AI analysis...
Completed with significant delays
Invoiced • 426 days old
🚨
Primary Delay75.9 days stuck in "Ready for Release"
⏱️
Total Delay38.9 business days over SLA thresholds
SLA vs Actual Time by Status
Actual (within SLA)
Actual (over SLA)
SLA Target
On Hold
61.5d
Ready for Release
106.9d
Scheduled
24.6d / 2.0d SLA
Reschedule
6.3d / 2.0d SLA
Tech On Site
0.1d / 1.0d SLA
Closed
1.0d / 1.0d SLA
Ready to Bill
15.0d / 1.0d SLA
Invoice Pending
0.0d / 2.0d SLA
💬 Activities, Notes & Communications
🔒Internal CSA Notes
6/4/25 RCook- Placing WO into RFR until WO is ready to be scheduled.
5/27 Cwassam rescheduled due to incoming repairs
🔧Work Performed
KIOSK HAS BEEN REMOVED FOR OVER A YEAR
🔍Technician Findings
KIOSK HAS BEEN REMOVED FOR OVER A YEAR
⚠️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.