Last business day of January 2026 · Target: Jan 30, 2026
✗ SLA Missed
Active: 5 biz days
Paused: 86 biz days
🕐 Clock stopped: Completed (May 16, 2026)
▶ Clock Running
Status: Created
Jan 6 → Jan 7, 2026
1 business day (counted)
Running total: 1 of ? biz days used
⏸86d
⏸ Clock Paused
Status: Ready for Release
Jan 7 → May 11, 2026
86 business days (not counted)
▶ Clock Running
Status: Assigned
May 11 → May 11, 2026
0 business days (counted)
Running total: 1 of ? biz days used
▶ Clock Running
Status: Scheduled
May 11 → May 15, 2026
4 business days (counted)
Running total: 5 of ? biz days used
▶ Clock Running
Status: Tech On Site
May 15 → May 16, 2026
0 business days (counted)
Running total: 5 of ? biz days used
Created: Jan 6, 2026Completed: May 16, 2026
Show SLA Clock Detail (5 periods)
Period
Status
Clock
Biz Days
Running Total
Jan 6 → Jan 7
Created
▶ Running
1
1
Jan 7 → May 11
Ready for Release
⏸ Paused
86
—
May 11 → May 11
Assigned
▶ Running
0
1
May 11 → May 15
Scheduled
▶ Running
4
5
May 15 → May 16
Tech On Site
▶ Running
0
5
Holding88.6d (excluded)
Coordinators5.0d
Field Work1.0d
Billing0.2d
✗ SLA Missed
Holding(excluded from total)
88.6 days
Coordinators
5.0 days
Over SLA
Field Work
1.0 days
Billing
0.2 days
Created: Jan 6, 2026
Due: Dec 31, 2026
Completed: May 16, 2026 (229 days early)
📅
91.6 daysTotal Age
⏱️
87.0d in Ready for ReleaseLongest Stage
🔄
8 transitionsStatus Changes
⚠️
3.0d 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 minor delays
Invoiced • 220 days old
🚨
Primary Delay87.0 days stuck in "Ready for Release"
⏱️
Total Delay3.0 business days over SLA thresholds
SLA vs Actual Time by Status
Actual (within SLA)
Actual (over SLA)
SLA Target
On Hold
1.6d
Ready for Release
87.0d
Assigned
0.0d / 0.5d SLA
Scheduled
5.0d / 2.0d SLA
Tech On Site
1.0d / 1.0d SLA
Completed
0.0d / 1.0d SLA
Closed
1.0d / 1.0d SLA
Ready to Bill
0.2d / 1.0d SLA
💬 Activities, Notes & Communications
🔧Work Performed
Performed PM on higi kiosk called L2 to document kiosk is not plugged directly into outlet. I spoke with Andrew from higi support and was told to leave as is.
🔍Technician Findings
Higi was on and running upon arrival, also I found the kiosk plugged into an extension cord due to location of higi.
⚠️Problem Description
Please Perform a PM on this Kiosk and attach all required photos from Checklist Regardless if a PM was completed or not a Checklist and photos are required as well as a signed field service report for every work order If a follow up is needed: Confirm with Tech support, select New issue, enter in the troubleshooting performed and part needed for the follow up in the follow up notes field Trunk stock work order: email dispatch@emsar.com with current work order # and the description of the repair that is required to be performed prior to PM completion (Example LED lights, bamboo seat replacement, Leveler replacement etc. all parts that can be found in your trunk stock ) Link to Work Instructions & Checklist on last page: SZZT (Higi Green) https://emsar-portal1.sharepoint.com/SOPs%20and%20Work%20Instructions/Higi%20&%20Legacy%20Kiosk%20Group/Higi%20Green/WI-ST-310%20Higi%20Green%20Preventative%20Maintenance%20009%20DCR652.pdf
📄Description
Merge KMY Kiosk
📞
Call
Completed May 15, 2026
Field Technician Max reported Higi connected to extension cord. Advise putting out of order sign and to contact Higi.
May 15, 2026 11:13am
@Nicole Floyd @Phillip Castillo Field Technician reported Higi connected to extension cord. Advise putting out of order sign and to contact Higi.