Last business day of January 2025 · Target: Jan 31, 2025
✗ SLA Missed (215 biz days late)
Active: 236 biz days
Paused: 49 biz days
🕐 Clock stopped: Completed (Feb 25, 2026)
236d
▶ Clock Running
Status: Created
Jan 2 → Dec 12, 2025
236 business days (counted)
Running total: 236 of ? biz days used
⏸24d
⏸ Clock Paused
Status: Ready for Release
Dec 12 → Jan 20, 2026
24 business days (not counted)
▶ Clock Running
Status: Assigned
Jan 20 → Jan 20, 2026
0 business days (counted)
Running total: 236 of ? biz days used
⏸24d
⏸ Clock Paused
Status: Ready for Release
Jan 20 → Feb 24, 2026
24 business days (not counted)
▶ Clock Running
Status: Assigned
Feb 24 → Feb 24, 2026
0 business days (counted)
Running total: 236 of ? biz days used
▶ Clock Running
Status: Scheduled
Feb 24 → Feb 24, 2026
0 business days (counted)
Running total: 236 of ? biz days used
⏸ Clock Paused
Status: Ready for Release
Feb 24 → Feb 25, 2026
1 business day (not counted)
▶ Clock Running
Status: Assigned
Feb 25 → Feb 25, 2026
0 business days (counted)
Running total: 236 of ? biz days used
▶ Clock Running
Status: Scheduled
Feb 25 → Feb 25, 2026
0 business days (counted)
Running total: 236 of ? biz days used
▶ Clock Running
Status: Tech On Site
Feb 25 → Feb 25, 2026
0 business days (counted)
Running total: 236 of ? biz days used
Created: Jan 2, 2025Completed: Feb 25, 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 20
Ready for Release
⏸ Paused
24
—
Jan 20 → Jan 20
Assigned
▶ Running
0
236
Jan 20 → Feb 24
Ready for Release
⏸ Paused
24
—
Feb 24 → Feb 24
Assigned
▶ Running
0
236
Feb 24 → Feb 24
Scheduled
▶ Running
0
236
Feb 24 → Feb 25
Ready for Release
⏸ Paused
1
—
Feb 25 → Feb 25
Assigned
▶ Running
0
236
Feb 25 → Feb 25
Scheduled
▶ Running
0
236
Feb 25 → Feb 25
Tech On Site
▶ Running
0
236
Holding287.5d (excluded)
Coordinators0.4d
Field Work0.3d
Billing2.0d
✗ SLA Missed
Holding(excluded from total)
287.5 days
Coordinators
0.4 days
Field Work
0.3 days
Billing
2.0 days
Over SLA
Created: Jan 2, 2025
Due: Dec 31, 2026
Completed: Feb 25, 2026 (309 days early)
📅
285.5 daysTotal Age
⏱️
236.5d in On HoldLongest Stage
🔄
13 transitionsStatus Changes
⚠️
2.5d 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 minor delays
Invoiced • 588 days old
🚨
Primary Delay236.5 days stuck in "On Hold"
⏱️
Total Delay2.5 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
51.0d
Assigned
0.0d / 0.5d SLA
Scheduled
0.4d / 2.0d SLA
Tech On Site
0.3d / 1.0d SLA
Completed
0.0d / 1.0d SLA
Closed
2.5d / 1.0d SLA
Ready to Bill
2.0d / 1.0d SLA
Invoice Pending
0.0d / 2.0d SLA
💬 Activities, Notes & Communications
🔧Work Performed
I completed the PM on the unit. I function tested the unit and unit failed. Unit was not returned to service.
🔍Technician Findings
Pm/ unit is out of calibration and is not holding pressure.
⚠️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.