Last business day of January 2025 · Target: Jan 31, 2025
✗ SLA Missed (227 biz days late)
Active: 248 biz days
Paused: 27 biz days
🕐 Clock stopped: Completed (Feb 10, 2026)
236d
▶ Clock Running
Status: Created
Jan 2 → Dec 12, 2025
236 business days (counted)
Running total: 236 of ? biz days used
⏸27d
⏸ Clock Paused
Status: Ready for Release
Dec 12 → Jan 23, 2026
27 business days (not counted)
▶ Clock Running
Status: Assigned
Jan 23 → Jan 23, 2026
0 business days (counted)
Running total: 236 of ? biz days used
▶ Clock Running
Status: Scheduled
Jan 23 → Feb 10, 2026
12 business days (counted)
Running total: 248 of ? biz days used
▶ Clock Running
Status: Tech On Site
Feb 10 → Feb 10, 2026
0 business days (counted)
Running total: 248 of ? biz days used
Created: Jan 2, 2025Completed: Feb 10, 2026
Show SLA Clock Detail (5 periods)
Period
Status
Clock
Biz Days
Running Total
Jan 2 → Dec 12
Created
▶ Running
236
236
Dec 12 → Jan 23
Ready for Release
⏸ Paused
27
—
Jan 23 → Jan 23
Assigned
▶ Running
0
236
Jan 23 → Feb 10
Scheduled
▶ Running
12
248
Feb 10 → Feb 10
Tech On Site
▶ Running
0
248
Holding264.2d (excluded)
Coordinators12.9d
Field Work0.8d
Billing13.0d
✗ SLA Missed
Holding(excluded from total)
264.2 days
Coordinators
12.9 days
Over SLA
Field Work
0.8 days
Billing
13.0 days
Over SLA
Created: Jan 2, 2025
Due: Dec 31, 2026
Completed: Feb 11, 2026 (323 days early)
📅
275.8 daysTotal Age
⏱️
236.5d in On HoldLongest Stage
🔄
9 transitionsStatus Changes
⚠️
23.1d overTotal Delay
📦
0 orders, 0 quotesParts & Quotes
📝
3 linesWork Details
🏠
1 visitOn-Site Trips
👤
Self-ScheduledScheduling
AI Analysis
Powered by OpenAI
Generating AI analysis...
Completed with significant delays
Invoiced • 588 days old
🚨
Primary Delay236.5 days stuck in "On Hold"
⏱️
Total Delay23.1 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
27.7d
Assigned
0.0d / 0.5d SLA
Scheduled
12.9d / 2.0d SLA
Tech On Site
0.0d / 1.0d SLA
Completed
0.7d / 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
2/10/2026 PC- PC
Technician Findings upon arrival: Unit not on-site.
Actions Taken/Work Performed: No unit in pharmacy area. Spoke to store manager and was able to check back of store to see if there was a unit on site. No unit found.
Final Resolution: No unit on-site.
🔍Technician Findings
2/10/2026 PC- PC
Technician Findings upon arrival: Unit not on-site.
Actions Taken/Work Performed: No unit in pharmacy area. Spoke to store manager and was able to check back of store to see if there was a unit on site. No unit found.
Final Resolution: No unit on-site.
⚠️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.