Last business day of January 2026 · Target: Jan 30, 2026
✗ SLA Missed (19 biz days late)
Active: 37 biz days
Paused: 54 biz days
🕐 Clock stopped: Completed (May 15, 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 8, 2026
1 business day (not counted)
▶ Clock Running
Status: Assigned
Jan 8 → Jan 8, 2026
0 business days (counted)
Running total: 1 of ? biz days used
13d
▶ Clock Running
Status: Scheduled
Jan 8 → Jan 28, 2026
13 business days (counted)
Running total: 14 of ? biz days used
▶ Clock Running
Status: Reschedule
Jan 28 → Jan 28, 2026
0 business days (counted)
Running total: 14 of ? biz days used
16d
▶ Clock Running
Status: Scheduled
Jan 28 → Feb 20, 2026
16 business days (counted)
Running total: 30 of ? biz days used
▶ Clock Running
Status: Reschedule
Feb 20 → Feb 22, 2026
0 business days (counted)
Running total: 30 of ? biz days used
▶ Clock Running
Status: Entered
Feb 22 → Feb 22, 2026
0 business days (counted)
Running total: 30 of ? biz days used
⏸36d
⏸ Clock Paused
Status: Ready for Release
Feb 22 → Apr 13, 2026
36 business days (not counted)
▶ Clock Running
Status: Assigned
Apr 13 → Apr 13, 2026
0 business days (counted)
Running total: 30 of ? biz days used
▶ Clock Running
Status: Scheduled
Apr 13 → Apr 14, 2026
1 business day (counted)
Running total: 31 of ? biz days used
▶ Clock Running
Status: Entered
Apr 14 → Apr 14, 2026
0 business days (counted)
Running total: 31 of ? biz days used
⏸ Clock Paused
Status: Ready for Release
Apr 14 → Apr 22, 2026
6 business days (not counted)
▶ Clock Running
Status: Assigned
Apr 22 → Apr 22, 2026
0 business days (counted)
Running total: 31 of ? biz days used
▶ Clock Running
Status: Scheduled
Apr 22 → Apr 23, 2026
1 business day (counted)
Running total: 32 of ? biz days used
▶ Clock Running
Status: Entered
Apr 23 → Apr 23, 2026
0 business days (counted)
Running total: 32 of ? biz days used
⏸ Clock Paused
Status: Ready for Release
Apr 23 → Apr 29, 2026
4 business days (not counted)
▶ Clock Running
Status: Assigned
Apr 29 → Apr 29, 2026
0 business days (counted)
Running total: 32 of ? biz days used
▶ Clock Running
Status: Scheduled
Apr 29 → Apr 29, 2026
0 business days (counted)
Running total: 32 of ? biz days used
▶ Clock Running
Status: Entered
Apr 29 → Apr 29, 2026
0 business days (counted)
Running total: 32 of ? biz days used
⏸ Clock Paused
Status: Ready for Release
Apr 29 → May 6, 2026
5 business days (not counted)
▶ Clock Running
Status: Assigned
May 6 → May 6, 2026
0 business days (counted)
Running total: 32 of ? biz days used
▶ Clock Running
Status: Scheduled
May 6 → May 11, 2026
3 business days (counted)
Running total: 35 of ? biz days used
▶ Clock Running
Status: Entered
May 11 → May 11, 2026
0 business days (counted)
Running total: 35 of ? biz days used
⏸ Clock Paused
Status: Ready for Release
May 11 → May 13, 2026
2 business days (not counted)
▶ Clock Running
Status: Assigned
May 13 → May 13, 2026
0 business days (counted)
Running total: 35 of ? biz days used
▶ Clock Running
Status: Scheduled
May 13 → May 15, 2026
2 business days (counted)
Running total: 37 of ? biz days used
▶ Clock Running
Status: Tech On Site
May 15 → May 15, 2026
0 business days (counted)
Running total: 37 of ? biz days used
Created: Jan 6, 2026Completed: May 15, 2026
Show SLA Clock Detail (28 periods)
Period
Status
Clock
Biz Days
Running Total
Jan 6 → Jan 7
Created
▶ Running
1
1
Jan 7 → Jan 8
Ready for Release
⏸ Paused
1
—
Jan 8 → Jan 8
Assigned
▶ Running
0
1
Jan 8 → Jan 28
Scheduled
▶ Running
13
14
Jan 28 → Jan 28
Reschedule
▶ Running
0
14
Jan 28 → Feb 20
Scheduled
▶ Running
16
30
Feb 20 → Feb 22
Reschedule
▶ Running
0
30
Feb 22 → Feb 22
Entered
▶ Running
0
30
Feb 22 → Apr 13
Ready for Release
⏸ Paused
36
—
Apr 13 → Apr 13
Assigned
▶ Running
0
30
Apr 13 → Apr 14
Scheduled
▶ Running
1
31
Apr 14 → Apr 14
Entered
▶ Running
0
31
Apr 14 → Apr 22
Ready for Release
⏸ Paused
6
—
Apr 22 → Apr 22
Assigned
▶ Running
0
31
Apr 22 → Apr 23
Scheduled
▶ Running
1
32
Apr 23 → Apr 23
Entered
▶ Running
0
32
Apr 23 → Apr 29
Ready for Release
⏸ Paused
4
—
Apr 29 → Apr 29
Assigned
▶ Running
0
32
Apr 29 → Apr 29
Scheduled
▶ Running
0
32
Apr 29 → Apr 29
Entered
▶ Running
0
32
Apr 29 → May 6
Ready for Release
⏸ Paused
5
—
May 6 → May 6
Assigned
▶ Running
0
32
May 6 → May 11
Scheduled
▶ Running
3
35
May 11 → May 11
Entered
▶ Running
0
35
May 11 → May 13
Ready for Release
⏸ Paused
2
—
May 13 → May 13
Assigned
▶ Running
0
35
May 13 → May 15
Scheduled
▶ Running
2
37
May 15 → May 15
Tech On Site
▶ Running
0
37
Holding60.2d (excluded)
Coordinators43.4d
Field Work1.0d
Billing3.3d
✗ SLA Missed
Holding(excluded from total)
60.2 days
Coordinators
43.4 days
Over SLA
Field Work
1.0 days
Billing
3.3 days
Created: Jan 6, 2026
Due: Dec 31, 2026
Completed: May 16, 2026 (229 days early)
📅
91.6 daysTotal Age
⏱️
36.0d in Ready for ReleaseLongest Stage
🔄
24 transitionsStatus Changes
⚠️
29.5d 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 significant delays
Invoiced • 220 days old
🚨
Primary Delay36.0 days stuck in "Ready for Release"
⏱️
Total Delay29.5 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
58.6d
Scheduled
42.0d / 2.0d SLA
Reschedule
1.4d / 2.0d SLA
Assigned
0.0d / 0.5d SLA
Tech On Site
0.1d / 1.0d SLA
Completed
1.0d / 1.0d SLA
Closed
2.0d / 1.0d SLA
WO Correction Needed
3.3d
Ready to Bill
0.1d / 1.0d SLA
💬 Activities, Notes & Communications
🔒Internal CSA Notes
5.18.26 hshaw - missing mileage
2/21/26 RBerry- Found WO in reschedule status. Cleared tech and placed WO back into RFR. Removed delay code.
🔧Work Performed
Pm completed
🔍Technician Findings
No issue found
⚠️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