Last business day of January 2026 · Target: Jan 30, 2026
✗ SLA Missed (6 biz days late)
Active: 24 biz days
Paused: 72 biz days
🕐 Clock stopped: Completed (May 22, 2026)
▶ Clock Running
Status: Created
Jan 6 → Jan 7, 2026
1 business day (counted)
Running total: 1 of ? biz days used
⏸ Clock Paused
Status: Ready for Release
Jan 7 → Jan 14, 2026
5 business days (not counted)
▶ Clock Running
Status: Assigned
Jan 14 → Jan 23, 2026
6 business days (counted)
Running total: 7 of ? biz days used
▶ Clock Running
Status: Scheduled
Jan 23 → Jan 30, 2026
5 business days (counted)
Running total: 12 of ? biz days used
▶ Clock Running
Status: Reschedule
Jan 30 → Feb 4, 2026
3 business days (counted)
Running total: 15 of ? biz days used
▶ Clock Running
Status: Entered
Feb 4 → Feb 4, 2026
0 business days (counted)
Running total: 15 of ? biz days used
⏸59d
⏸ Clock Paused
Status: Ready for Release
Feb 4 → Apr 29, 2026
59 business days (not counted)
▶ Clock Running
Status: Assigned
Apr 29 → May 1, 2026
2 business days (counted)
Running total: 17 of ? biz days used
▶ Clock Running
Status: Entered
May 1 → May 1, 2026
0 business days (counted)
Running total: 17 of ? biz days used
⏸ Clock Paused
Status: Ready for Release
May 1 → May 6, 2026
3 business days (not counted)
▶ Clock Running
Status: Assigned
May 6 → May 6, 2026
0 business days (counted)
Running total: 17 of ? biz days used
▶ Clock Running
Status: Scheduled
May 6 → May 6, 2026
0 business days (counted)
Running total: 17 of ? biz days used
▶ Clock Running
Status: Entered
May 6 → May 6, 2026
0 business days (counted)
Running total: 17 of ? biz days used
⏸ Clock Paused
Status: Ready for Release
May 6 → May 13, 2026
5 business days (not counted)
▶ Clock Running
Status: Assigned
May 13 → May 13, 2026
0 business days (counted)
Running total: 17 of ? biz days used
▶ Clock Running
Status: Scheduled
May 13 → May 22, 2026
7 business days (counted)
Running total: 24 of ? biz days used
Created: Jan 6, 2026Completed: May 22, 2026
Show SLA Clock Detail (16 periods)
Period
Status
Clock
Biz Days
Running Total
Jan 6 → Jan 7
Created
▶ Running
1
1
Jan 7 → Jan 14
Ready for Release
⏸ Paused
5
—
Jan 14 → Jan 23
Assigned
▶ Running
6
7
Jan 23 → Jan 30
Scheduled
▶ Running
5
12
Jan 30 → Feb 4
Reschedule
▶ Running
3
15
Feb 4 → Feb 4
Entered
▶ Running
0
15
Feb 4 → Apr 29
Ready for Release
⏸ Paused
59
—
Apr 29 → May 1
Assigned
▶ Running
2
17
May 1 → May 1
Entered
▶ Running
0
17
May 1 → May 6
Ready for Release
⏸ Paused
3
—
May 6 → May 6
Assigned
▶ Running
0
17
May 6 → May 6
Scheduled
▶ Running
0
17
May 6 → May 6
Entered
▶ Running
0
17
May 6 → May 13
Ready for Release
⏸ Paused
5
—
May 13 → May 13
Assigned
▶ Running
0
17
May 13 → May 22
Scheduled
▶ Running
7
24
Holding76.5d (excluded)
Coordinators28.2d
Field Work1.0d
Billing0.0d
✗ SLA Missed
Holding(excluded from total)
76.5 days
Coordinators
28.2 days
Over SLA
Field Work
1.0 days
Billing
0.0 days
Created: Jan 6, 2026
Due: Dec 31, 2026
Completed: May 25, 2026 (220 days early)
📅
96.6 daysTotal Age
⏱️
59.3d in Ready for ReleaseLongest Stage
🔄
16 transitionsStatus Changes
⚠️
20.7d overTotal Delay
📦
0 orders, 0 quotesParts & Quotes
📝
5 linesWork Details
🏠
1 visitOn-Site Trips
📋
CoordinatorScheduling
AI Analysis
Powered by OpenAI
Generating AI analysis...
Completed with significant delays
Invoiced • 220 days old
🚨
Primary Delay59.3 days stuck in "Ready for Release"
⏱️
Total Delay20.7 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
74.9d
Assigned
10.0d / 0.5d SLA
Scheduled
14.2d / 2.0d SLA
Reschedule
4.0d / 2.0d SLA
Completed
1.0d / 1.0d SLA
Closed
1.0d / 1.0d SLA
Ready to Bill
0.0d / 1.0d SLA
💬 Activities, Notes & Communications
🔒Internal CSA Notes
1/30/26 CDempsey- Tech couldn't get here in time. Will need to reschedule.
🔧Work Performed
5/21 CLacy- PM Service completed to manufacture specs. Functional testing passed. This unit is ready to return to service
🔍Technician Findings
PM Service is due, kiosk was fully operational
⚠️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