Last business day of January 2025 · Target: Jan 31, 2025
✗ SLA Missed (233 biz days late)
Active: 254 biz days
Paused: 150 biz days
🕐 Clock stopped: Completed (Aug 14, 2026)
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 9, 2026
18 business days (not counted)
▶ Clock Running
Status: Assigned
Jan 9 → Jan 9, 2026
0 business days (counted)
Running total: 236 of ? biz days used
▶ Clock Running
Status: Scheduled
Jan 9 → Jan 14, 2026
3 business days (counted)
Running total: 239 of ? biz days used
▶ Clock Running
Status: Reschedule
Jan 14 → Feb 4, 2026
14 business days (counted)
Running total: 253 of ? biz days used
▶ Clock Running
Status: Entered
Feb 4 → Feb 4, 2026
0 business days (counted)
Running total: 253 of ? biz days used
⏸132d
⏸ Clock Paused
Status: Ready for Release
Feb 4 → Aug 13, 2026
132 business days (not counted)
▶ Clock Running
Status: Assigned
Aug 13 → Aug 13, 2026
0 business days (counted)
Running total: 253 of ? biz days used
▶ Clock Running
Status: Scheduled
Aug 13 → Aug 14, 2026
1 business day (counted)
Running total: 254 of ? biz days used
▶ Clock Running
Status: Tech On Site
Aug 14 → Aug 14, 2026
0 business days (counted)
Running total: 254 of ? biz days used
Created: Jan 2, 2025Completed: Aug 14, 2026
Show SLA Clock Detail (10 periods)
Period
Status
Clock
Biz Days
Running Total
Jan 2 → Dec 12
Created
▶ Running
236
236
Dec 12 → Jan 9
Ready for Release
⏸ Paused
18
—
Jan 9 → Jan 9
Assigned
▶ Running
0
236
Jan 9 → Jan 14
Scheduled
▶ Running
3
239
Jan 14 → Feb 4
Reschedule
▶ Running
14
253
Feb 4 → Feb 4
Entered
▶ Running
0
253
Feb 4 → Aug 13
Ready for Release
⏸ Paused
132
—
Aug 13 → Aug 13
Assigned
▶ Running
0
253
Aug 13 → Aug 14
Scheduled
▶ Running
1
254
Aug 14 → Aug 14
Tech On Site
▶ Running
0
254
Holding387.5d (excluded)
Coordinators20.4d
Field Work0.4d
Billing13.0d
✗ SLA Missed
Holding(excluded from total)
387.5 days
Coordinators
20.4 days
Over SLA
Field Work
0.4 days
Billing
13.0 days
Over SLA
Created: Jan 2, 2025
Due: Dec 31, 2026
Completed: Aug 14, 2026 (139 days early)
📅
404.5 daysTotal Age
⏱️
236.5d in On HoldLongest Stage
🔄
10 transitionsStatus Changes
⚠️
27.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 • 657 days old
🚨
Primary Delay236.5 days stuck in "On Hold"
⏱️
Total Delay27.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
151.0d
Scheduled
5.4d / 2.0d SLA
Reschedule
15.0d / 2.0d SLA
Tech On Site
0.4d / 1.0d SLA
Closed
1.2d / 1.0d SLA
Ready to Bill
13.0d / 1.0d SLA
Invoice Pending
0.0d / 2.0d SLA
💬 Activities, Notes & Communications
🔧Work Performed
08/14/2026 Mike Huffman. Completed the PM and checklist. Completed the Field Service Report and obtained customer signature.
🔍Technician Findings
Kiosk is fully operational.
⚠️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.