Last business day of January 2026 · Target: Jan 30, 2026
✗ SLA Missed
Active: 1 biz days
Paused: 74 biz days
🕐 Clock stopped: Completed (Apr 25, 2026)
▶ Clock Running
Status: Created
Jan 7 → Jan 7, 2026
0 business days (counted)
Running total: 0 of ? biz days used
▶ Clock Running
Status: Ready for Scheduling
Jan 7 → Jan 7, 2026
0 business days (counted)
Running total: 0 of ? biz days used
⏸74d
⏸ Clock Paused
Status: Ready for Release
Jan 7 → Apr 23, 2026
74 business days (not counted)
▶ Clock Running
Status: Ready for Scheduling
Apr 23 → Apr 23, 2026
0 business days (counted)
Running total: 0 of ? biz days used
▶ Clock Running
Status: Assigned
Apr 23 → Apr 23, 2026
0 business days (counted)
Running total: 0 of ? biz days used
▶ Clock Running
Status: Scheduled
Apr 23 → Apr 24, 2026
1 business day (counted)
Running total: 1 of ? biz days used
▶ Clock Running
Status: Tech On Site
Apr 24 → Apr 25, 2026
0 business days (counted)
Running total: 1 of ? biz days used
Created: Jan 7, 2026Completed: Apr 25, 2026
Show SLA Clock Detail (7 periods)
Period
Status
Clock
Biz Days
Running Total
Jan 7 → Jan 7
Created
▶ Running
0
0
Jan 7 → Jan 7
Ready for Scheduling
▶ Running
0
0
Jan 7 → Apr 23
Ready for Release
⏸ Paused
74
—
Apr 23 → Apr 23
Ready for Scheduling
▶ Running
0
0
Apr 23 → Apr 23
Assigned
▶ Running
0
0
Apr 23 → Apr 24
Scheduled
▶ Running
1
1
Apr 24 → Apr 25
Tech On Site
▶ Running
0
1
Dispatch0.3d
Holding74.3d (excluded)
Coordinators2.2d
Field Work0.9d
Billing0.1d
✗ SLA Missed
Dispatch
0.3 days
Holding(excluded from total)
74.3 days
Coordinators
2.2 days
Field Work
0.9 days
Billing
0.1 days
Created: Jan 7, 2026
Due: Apr 30, 2026
Completed: Apr 25, 2026 (5 days early)
📅
76.0 daysTotal Age
⏱️
74.3d in Ready for ReleaseLongest Stage
🔄
10 transitionsStatus Changes
✅
On timeTotal Delay
📦
0 orders, 0 quotesParts & Quotes
📝
3 linesWork Details
🏠
1 visitOn-Site Trips
👤
Self-ScheduledScheduling
AI Analysis
Powered by OpenAI
Generating AI analysis...
Completed on schedule
Invoiced • 221 days old
🚨
Primary Delay74.3 days stuck in "Ready for Release"
SLA vs Actual Time by Status
Actual (within SLA)
Actual (over SLA)
SLA Target
Entered
0.3d / 0.5d SLA
Ready for Scheduling
0.7d / 1.0d SLA
Ready for Release
74.3d
Scheduled
1.5d / 2.0d SLA
Tech On Site
0.9d / 1.0d SLA
Completed
0.0d / 1.0d SLA
Closed
1.0d / 1.0d SLA
Ready to Bill
0.0d / 1.0d SLA
Invoice Pending
0.0d / 2.0d SLA
💬 Activities, Notes & Communications
🔧Work Performed
24apr2026 fjackson pm performed
🔍Technician Findings
Counter# 109,549.
PM due
⚠️Problem Description
Please Perform the PM for this Kiosk based on the product listed in the work order: 90550, LC300, LC500.
***IMPORTANT CHANGE****
Please Log/notate in the technician findings the number of times the kiosk was used and double check the SN. If the SN is different than in the work order please also notate the correct SN. Regardless if the SN matches continue to perform the PM service.
If location is a non-retail location a call ahead to schedule is required
PM Checklist Tips:
If Checklist is not populating, make sure the order type contains 'PM' and the product must contain an 90550, LC300 or LC500. Update the order status to 'tech onsite' and the workflow will look for the parameters in which a PM checklist is required and will auto attach.
Common missed step: After you Finalize the checklist you must select 'Print checklist' for the checklist to attach to the work order for the billing reviewer to review.
**IMPORTANT** This is a Non Retail location and a scheduled appointment must be made in advance to ensure the machine will be made available prior to tech arrival on site. If a work market technician has to be used SDL must obtain approval from Higi prior to scheduling work. If the technician is unable to make contact on the first attempt, email EMSAR at higisupport@emsar.com so HIGI can be notified to provide us with an alternate contact name and number. Any calls made MUST be logged on the work order under Activity History with who you spoke to and date/time of call