Last business day of January 2025 · Target: Jan 31, 2025
✗ SLA Missed (219 biz days late)
Active: 240 biz days
Paused: 46 biz days
🕐 Clock stopped: Completed (Feb 26, 2026)
236d
▶ Clock Running
Status: Created
Jan 2 → Dec 12, 2025
236 business days (counted)
Running total: 236 of ? biz days used
⏸46d
⏸ Clock Paused
Status: Ready for Release
Dec 12 → Feb 20, 2026
46 business days (not counted)
▶ Clock Running
Status: Assigned
Feb 20 → Feb 20, 2026
0 business days (counted)
Running total: 236 of ? biz days used
▶ Clock Running
Status: Scheduled
Feb 20 → Feb 26, 2026
4 business days (counted)
Running total: 240 of ? biz days used
▶ Clock Running
Status: Tech On Site
Feb 26 → Feb 26, 2026
0 business days (counted)
Running total: 240 of ? biz days used
Created: Jan 2, 2025Completed: Feb 26, 2026
Show SLA Clock Detail (5 periods)
Period
Status
Clock
Biz Days
Running Total
Jan 2 → Dec 12
Created
▶ Running
236
236
Dec 12 → Feb 20
Ready for Release
⏸ Paused
46
—
Feb 20 → Feb 20
Assigned
▶ Running
0
236
Feb 20 → Feb 26
Scheduled
▶ Running
4
240
Feb 26 → Feb 26
Tech On Site
▶ Running
0
240
Holding283.2d (excluded)
Coordinators4.5d
Field Work0.7d
Billing2.0d
✗ SLA Missed
Holding(excluded from total)
283.2 days
Coordinators
4.5 days
Over SLA
Field Work
0.7 days
Billing
2.0 days
Over SLA
Created: Jan 2, 2025
Due: Dec 31, 2026
Completed: Feb 26, 2026 (308 days early)
📅
286.5 daysTotal Age
⏱️
236.5d in On HoldLongest Stage
🔄
8 transitionsStatus Changes
⚠️
3.8d overTotal Delay
📦
0 orders, 0 quotesParts & Quotes
📝
6 linesWork Details
🏠
1 visitOn-Site Trips
👤
Self-ScheduledScheduling
AI Analysis
Powered by OpenAI
Generating AI analysis...
Completed with minor delays
Invoiced • 426 days old
🚨
Primary Delay236.5 days stuck in "On Hold"
⏱️
Total Delay3.8 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
46.7d
Scheduled
4.5d / 2.0d SLA
Tech On Site
0.1d / 1.0d SLA
Completed
0.6d / 1.0d SLA
Closed
1.3d / 1.0d SLA
Ready to Bill
2.0d / 1.0d SLA
Invoice Pending
0.0d / 2.0d SLA
💬 Activities, Notes & Communications
🔧Work Performed
2/26/26
Traveled to site
Found unit had been tossed out. Not available to PM.
Contacted L2 to give them the updated information about device.
Traveled from location
Closed WO as trip charge
🔍Technician Findings
The unit was tossed by the store prior to arrival.
I searched the back storage area. The pharmacist said she saw it off the floor but didn’t know it had recently been tossed out.
The store manager, Ms. Currie, said it happened during a previous manager’s term.
⚠️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.