Last business day of January 2025 · Target: Jan 31, 2025
✗ SLA Missed (44 biz days late)
Active: 65 biz days
Paused: 129 biz days
🕐 Clock stopped: Completed (Oct 9, 2025)
61d
▶ Clock Running
Status: Created
Jan 2 → Apr 1, 2025
61 business days (counted)
Running total: 61 of ? biz days used
⏸37d
⏸ Clock Paused
Status: Ready for Release
Apr 1 → May 22, 2025
37 business days (not counted)
▶ Clock Running
Status: Scheduled
May 22 → May 22, 2025
0 business days (counted)
Running total: 61 of ? biz days used
▶ Clock Running
Status: Entered
May 22 → May 22, 2025
0 business days (counted)
Running total: 61 of ? biz days used
⏸92d
⏸ Clock Paused
Status: Ready for Release
May 22 → Oct 3, 2025
92 business days (not counted)
▶ Clock Running
Status: Assigned
Oct 3 → Oct 3, 2025
0 business days (counted)
Running total: 61 of ? biz days used
▶ Clock Running
Status: Scheduled
Oct 3 → Oct 8, 2025
3 business days (counted)
Running total: 64 of ? biz days used
▶ Clock Running
Status: Tech On Site
Oct 8 → Oct 9, 2025
1 business day (counted)
Running total: 65 of ? biz days used
Created: Jan 2, 2025Completed: Oct 9, 2025
Show SLA Clock Detail (8 periods)
Period
Status
Clock
Biz Days
Running Total
Jan 2 → Apr 1
Created
▶ Running
61
61
Apr 1 → May 22
Ready for Release
⏸ Paused
37
—
May 22 → May 22
Scheduled
▶ Running
0
61
May 22 → May 22
Entered
▶ Running
0
61
May 22 → Oct 3
Ready for Release
⏸ Paused
92
—
Oct 3 → Oct 3
Assigned
▶ Running
0
61
Oct 3 → Oct 8
Scheduled
▶ Running
3
64
Oct 8 → Oct 9
Tech On Site
▶ Running
1
65
Holding192.1d (excluded)
Coordinators4.2d
Field Work0.5d
Billing17.0d
✗ SLA Missed
Holding(excluded from total)
192.1 days
Coordinators
4.2 days
Over SLA
Field Work
0.5 days
Billing
17.0 days
Over SLA
Created: Jan 2, 2025
Due: Dec 31, 2025
Completed: Oct 9, 2025 (83 days early)
📅
193.8 daysTotal Age
⏱️
92.7d in Ready for ReleaseLongest Stage
🔄
11 transitionsStatus Changes
⚠️
18.0d 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 Delay92.7 days stuck in "Ready for Release"
⏱️
Total Delay18.0 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
130.7d
Scheduled
4.1d / 2.0d SLA
Assigned
0.0d / 0.5d SLA
Tech On Site
0.1d / 1.0d SLA
Completed
0.3d / 1.0d SLA
Closed
1.0d / 1.0d SLA
Ready to Bill
17.0d / 1.0d SLA
Invoice Pending
0.0d / 2.0d SLA
💬 Activities, Notes & Communications
🔧Work Performed
PM Service
🔍Technician Findings
Working Health station
⚠️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.