Last business day of January 2026 · Target: Jan 30, 2026
✗ SLA Missed
Active: 4 biz days
Paused: 32 biz days
🕐 Clock stopped: Completed (Feb 27, 2026)
▶ Clock Running
Status: Created
Jan 6 → Jan 7, 2026
1 business day (counted)
Running total: 1 of ? biz days used
⏸32d
⏸ Clock Paused
Status: Ready for Release
Jan 7 → Feb 24, 2026
32 business days (not counted)
▶ Clock Running
Status: Assigned
Feb 24 → Feb 24, 2026
0 business days (counted)
Running total: 1 of ? biz days used
▶ Clock Running
Status: Scheduled
Feb 24 → Feb 27, 2026
3 business days (counted)
Running total: 4 of ? biz days used
▶ Clock Running
Status: Tech On Site
Feb 27 → Feb 27, 2026
0 business days (counted)
Running total: 4 of ? biz days used
Created: Jan 6, 2026Completed: Feb 27, 2026
Show SLA Clock Detail (5 periods)
Period
Status
Clock
Biz Days
Running Total
Jan 6 → Jan 7
Created
▶ Running
1
1
Jan 7 → Feb 24
Ready for Release
⏸ Paused
32
—
Feb 24 → Feb 24
Assigned
▶ Running
0
1
Feb 24 → Feb 27
Scheduled
▶ Running
3
4
Feb 27 → Feb 27
Tech On Site
▶ Running
0
4
Holding34.6d (excluded)
Coordinators3.1d
Field Work0.2d
Billing0.1d
✗ SLA Missed
Holding(excluded from total)
34.6 days
Coordinators
3.1 days
Over SLA
Field Work
0.2 days
Billing
0.1 days
Created: Jan 6, 2026
Due: Dec 31, 2026
Completed: Feb 27, 2026 (307 days early)
📅
36.6 daysTotal Age
⏱️
33.0d in Ready for ReleaseLongest Stage
🔄
8 transitionsStatus Changes
⚠️
4.0d 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 • 57 days old
🚨
Primary Delay33.0 days stuck in "Ready for Release"
⏱️
Total Delay4.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
33.0d
Scheduled
3.1d / 2.0d SLA
Tech On Site
0.1d / 1.0d SLA
Completed
0.1d / 1.0d SLA
Closed
3.9d / 1.0d SLA
Ready to Bill
0.1d / 1.0d SLA
Invoice Pending
0.0d / 2.0d SLA
💬 Activities, Notes & Communications
🔧Work Performed
Tech performed a PM on the kiosk. After performing a PM on kiosk, tech function tested the unit and everything was found to be in working order. Tech let the pharmacist know that the kiosk was ready for use again.
🔍Technician Findings
Tech arrived on site and was told to perform a PM on the kiosk. Tech checked in the the pharmacist. Kiosk was found to be on and in working order and tech saw that all the lights were working on the seat and on the side. Both screens were on and working also.
⚠️Problem Description
Please Perform a PM on this Kiosk and attach all required photos from the PM Checklist
Note this is a Non-retail account and requires a call to schedule. Please navigate to the location page for contact details
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.pdf
Work Order: WO-01330895
Account: HIGI LLC
Customer Case Number:
Location: CVS 788
Address: 344 West Hubbard, Chicago, IL 60610
Manufacturer: Merge SH Holdings, Inc.
Model #: KMY8202F
Serial #: KMY-120328650-513
Contact Name:
Contact Phone:
Contact Email:
Due Date: 12/31/2026
Scheduled Date/Time