Last business day of December 2024 · Target: Dec 31, 2024
✗ SLA Missed (73 biz days late)
Active: 75 biz days
Paused: 99 biz days
🕐 Clock stopped: Completed (Sep 9, 2025)
48d
▶ Clock Running
Status: Created
Dec 30 → Mar 11, 2025
48 business days (counted)
Running total: 48 of ? biz days used
▶ Clock Running
Status: Scheduled
Mar 11 → Mar 17, 2025
4 business days (counted)
Running total: 52 of ? biz days used
▶ Clock Running
Status: Entered
Mar 17 → Mar 17, 2025
0 business days (counted)
Running total: 52 of ? biz days used
▶ Clock Running
Status: On Hold
Mar 17 → Mar 27, 2025
8 business days (counted)
Running total: 60 of ? biz days used
▶ Clock Running
Status: Scheduled
Mar 27 → Apr 2, 2025
4 business days (counted)
Running total: 64 of ? biz days used
▶ Clock Running
Status: Entered
Apr 2 → Apr 2, 2025
0 business days (counted)
Running total: 64 of ? biz days used
⏸38d
⏸ Clock Paused
Status: Ready for Release
Apr 2 → May 27, 2025
38 business days (not counted)
▶ Clock Running
Status: Assigned
May 27 → May 27, 2025
0 business days (counted)
Running total: 64 of ? biz days used
▶ Clock Running
Status: Scheduled
May 27 → Jun 5, 2025
7 business days (counted)
Running total: 71 of ? biz days used
▶ Clock Running
Status: Entered
Jun 5 → Jun 5, 2025
0 business days (counted)
Running total: 71 of ? biz days used
⏸61d
⏸ Clock Paused
Status: Ready for Release
Jun 5 → Sep 3, 2025
61 business days (not counted)
▶ Clock Running
Status: Assigned
Sep 3 → Sep 3, 2025
0 business days (counted)
Running total: 71 of ? biz days used
▶ Clock Running
Status: Scheduled
Sep 3 → Sep 9, 2025
4 business days (counted)
Running total: 75 of ? biz days used
▶ Clock Running
Status: Tech On Site
Sep 9 → Sep 9, 2025
0 business days (counted)
Running total: 75 of ? biz days used
▶ Clock Running
Status: Scheduled
Sep 9 → Sep 9, 2025
0 business days (counted)
Running total: 75 of ? biz days used
▶ Clock Running
Status: Tech On Site
Sep 9 → Sep 9, 2025
0 business days (counted)
Running total: 75 of ? biz days used
Created: Dec 30, 2024Completed: Sep 9, 2025
Show SLA Clock Detail (16 periods)
Period
Status
Clock
Biz Days
Running Total
Dec 30 → Mar 11
Created
▶ Running
48
48
Mar 11 → Mar 17
Scheduled
▶ Running
4
52
Mar 17 → Mar 17
Entered
▶ Running
0
52
Mar 17 → Mar 27
On Hold
▶ Running
8
60
Mar 27 → Apr 2
Scheduled
▶ Running
4
64
Apr 2 → Apr 2
Entered
▶ Running
0
64
Apr 2 → May 27
Ready for Release
⏸ Paused
38
—
May 27 → May 27
Assigned
▶ Running
0
64
May 27 → Jun 5
Scheduled
▶ Running
7
71
Jun 5 → Jun 5
Entered
▶ Running
0
71
Jun 5 → Sep 3
Ready for Release
⏸ Paused
61
—
Sep 3 → Sep 3
Assigned
▶ Running
0
71
Sep 3 → Sep 9
Scheduled
▶ Running
4
75
Sep 9 → Sep 9
Tech On Site
▶ Running
0
75
Sep 9 → Sep 9
Scheduled
▶ Running
0
75
Sep 9 → Sep 9
Tech On Site
▶ Running
0
75
Holding157.4d (excluded)
Coordinators22.0d
Field Work0.1d
Billing0.3d
✗ SLA Missed
Holding(excluded from total)
157.4 days
Coordinators
22.0 days
Over SLA
Field Work
0.1 days
Billing
0.3 days
Created: Dec 30, 2024
Due: Dec 31, 2025
Completed: Sep 9, 2025 (113 days early)
📅
174.3 daysTotal Age
⏱️
61.6d in Ready for ReleaseLongest Stage
🔄
14 transitionsStatus Changes
⚠️
14.4d overTotal Delay
📦
0 orders, 0 quotesParts & Quotes
📝
5 linesWork Details
🏠
2 visitsOn-Site Trips
👤
Self-ScheduledScheduling
🔄
2 On-Site Visits
2 on-site visits — follow-up trip required
👤 Self-scheduled by Ronnie Salone — scheduling delays attributed to technician, not coordinators
Visit 1Sep 9, 2025
AI Analysis
Powered by OpenAI
Generating AI analysis...
Completed with significant delays
Invoiced • 429 days old
🚨
Primary Delay61.6 days stuck in "Ready for Release"
⏱️
Total Delay14.4 business days over SLA thresholds
SLA vs Actual Time by Status
Actual (within SLA)
Actual (over SLA)
SLA Target
On Hold
57.1d
Scheduled
22.0d / 2.0d SLA
Ready for Release
100.3d
Assigned
0.0d / 0.5d SLA
Tech On Site
0.0d / 1.0d SLA
Completed
0.1d / 1.0d SLA
Closed
1.4d / 1.0d SLA
Ready to Bill
0.3d / 1.0d SLA
💬 Activities, Notes & Communications
🔒Internal CSA Notes
4/2 Lbasharat placing on ready for release due to repairs
🔧Work Performed
9/9/25
Traveled to site
Completed PM
Unit did not hold pressure for 60 seconds
Follow up needed for pressure cuff
🔍Technician Findings
Unit needed PM
Unit did not hold pressure for 60 seconds
⚠️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