Last business day of January 2025 · Target: Jan 31, 2025
✗ SLA Missed (223 biz days late)
Active: 244 biz days
Paused: 179 biz days
🕐 Clock stopped: Completed (Sep 11, 2026)
236d
▶ Clock Running
Status: Created
Jan 2 → Dec 12, 2025
236 business days (counted)
Running total: 236 of ? biz days used
⏸162d
⏸ Clock Paused
Status: Ready for Release
Dec 12 → Aug 6, 2026
162 business days (not counted)
▶ Clock Running
Status: Scheduled
Aug 6 → Aug 10, 2026
2 business days (counted)
Running total: 238 of ? biz days used
▶ Clock Running
Status: Entered
Aug 10 → Aug 10, 2026
0 business days (counted)
Running total: 238 of ? biz days used
⏸ Clock Paused
Status: Ready for Release
Aug 10 → Sep 2, 2026
17 business days (not counted)
▶ Clock Running
Status: Ready for Scheduling
Sep 2 → Sep 10, 2026
5 business days (counted)
Running total: 243 of ? biz days used
▶ Clock Running
Status: Assigned
Sep 10 → Sep 10, 2026
0 business days (counted)
Running total: 243 of ? biz days used
▶ Clock Running
Status: Scheduled
Sep 10 → Sep 10, 2026
0 business days (counted)
Running total: 243 of ? biz days used
▶ Clock Running
Status: Tech On Site
Sep 10 → Sep 11, 2026
1 business day (counted)
Running total: 244 of ? biz days used
Created: Jan 2, 2025Completed: Sep 11, 2026
Show SLA Clock Detail (9 periods)
Period
Status
Clock
Biz Days
Running Total
Jan 2 → Dec 12
Created
▶ Running
236
236
Dec 12 → Aug 6
Ready for Release
⏸ Paused
162
—
Aug 6 → Aug 10
Scheduled
▶ Running
2
238
Aug 10 → Aug 10
Entered
▶ Running
0
238
Aug 10 → Sep 2
Ready for Release
⏸ Paused
17
—
Sep 2 → Sep 10
Ready for Scheduling
▶ Running
5
243
Sep 10 → Sep 10
Assigned
▶ Running
0
243
Sep 10 → Sep 10
Scheduled
▶ Running
0
243
Sep 10 → Sep 11
Tech On Site
▶ Running
1
244
Holding416.7d (excluded)
Coordinators8.9d
Field Work0.4d
Billing16.0d
✗ SLA Missed
Holding(excluded from total)
416.7 days
Coordinators
8.9 days
Over SLA
Field Work
0.4 days
Billing
16.0 days
Over SLA
Created: Jan 2, 2025
Due: Dec 31, 2026
Completed: Sep 11, 2026 (111 days early)
📅
422.8 daysTotal Age
⏱️
236.5d in On HoldLongest Stage
🔄
11 transitionsStatus Changes
⚠️
20.9d overTotal Delay
📦
0 orders, 0 quotesParts & Quotes
📝
7 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 Delay20.9 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
180.3d
Scheduled
3.4d / 2.0d SLA
Ready for Scheduling
5.5d / 1.0d SLA
Tech On Site
0.4d / 1.0d SLA
Completed
0.0d / 1.0d SLA
Closed
2.0d / 1.0d SLA
Ready to Bill
16.0d / 1.0d SLA
Invoice Pending
0.0d / 2.0d SLA
💬 Activities, Notes & Communications
🔒Internal CSA Notes
8/10/26- BBaggett- clearing tech name and placing back into RFR.
🔧Work Performed
Completed the CVS PM.
🔍Technician Findings
The kiosk was functioning normally.
⚠️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.