Last business day of January 2025 · Target: Jan 31, 2025
✗ SLA Missed (254 biz days late)
Active: 275 biz days
Paused: 101 biz days
🕐 Clock stopped: Completed (Jul 7, 2026)
236d
▶ Clock Running
Status: Created
Jan 2 → Dec 12, 2025
236 business days (counted)
Running total: 236 of ? biz days used
⏸54d
⏸ Clock Paused
Status: Ready for Release
Dec 12 → Mar 4, 2026
54 business days (not counted)
▶ Clock Running
Status: Assigned
Mar 4 → Mar 4, 2026
0 business days (counted)
Running total: 236 of ? biz days used
▶ Clock Running
Status: Scheduled
Mar 4 → Mar 16, 2026
8 business days (counted)
Running total: 244 of ? biz days used
▶ Clock Running
Status: Reschedule
Mar 16 → Mar 31, 2026
11 business days (counted)
Running total: 255 of ? biz days used
▶ Clock Running
Status: Entered
Mar 31 → Mar 31, 2026
0 business days (counted)
Running total: 255 of ? biz days used
⏸ Clock Paused
Status: Ready for Release
Mar 31 → Apr 8, 2026
6 business days (not counted)
▶ Clock Running
Status: Assigned
Apr 8 → Apr 8, 2026
0 business days (counted)
Running total: 255 of ? biz days used
▶ Clock Running
Status: Scheduled
Apr 8 → Apr 15, 2026
5 business days (counted)
Running total: 260 of ? biz days used
▶ Clock Running
Status: Entered
Apr 15 → Apr 15, 2026
0 business days (counted)
Running total: 260 of ? biz days used
⏸ Clock Paused
Status: Ready for Release
Apr 15 → Apr 29, 2026
10 business days (not counted)
▶ Clock Running
Status: Assigned
Apr 29 → May 1, 2026
2 business days (counted)
Running total: 262 of ? biz days used
▶ Clock Running
Status: Entered
May 1 → May 1, 2026
0 business days (counted)
Running total: 262 of ? biz days used
⏸ Clock Paused
Status: Ready for Release
May 1 → May 1, 2026
0 business days (not counted)
▶ Clock Running
Status: Entered
May 1 → May 1, 2026
0 business days (counted)
Running total: 262 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: 262 of ? biz days used
▶ Clock Running
Status: Scheduled
May 6 → May 6, 2026
0 business days (counted)
Running total: 262 of ? biz days used
▶ Clock Running
Status: Entered
May 6 → May 6, 2026
0 business days (counted)
Running total: 262 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: 262 of ? biz days used
▶ Clock Running
Status: Scheduled
May 13 → May 18, 2026
3 business days (counted)
Running total: 265 of ? biz days used
▶ Clock Running
Status: Entered
May 18 → May 18, 2026
0 business days (counted)
Running total: 265 of ? biz days used
⏸ Clock Paused
Status: Ready for Release
May 18 → May 21, 2026
3 business days (not counted)
▶ Clock Running
Status: Assigned
May 21 → May 21, 2026
0 business days (counted)
Running total: 265 of ? biz days used
▶ Clock Running
Status: Entered
May 21 → May 21, 2026
0 business days (counted)
Running total: 265 of ? biz days used
⏸ Clock Paused
Status: Ready for Release
May 21 → May 27, 2026
3 business days (not counted)
▶ Clock Running
Status: Assigned
May 27 → May 27, 2026
0 business days (counted)
Running total: 265 of ? biz days used
▶ Clock Running
Status: Scheduled
May 27 → May 28, 2026
1 business day (counted)
Running total: 266 of ? biz days used
▶ Clock Running
Status: Entered
May 28 → May 28, 2026
0 business days (counted)
Running total: 266 of ? biz days used
⏸ Clock Paused
Status: Ready for Release
May 28 → Jun 23, 2026
17 business days (not counted)
▶ Clock Running
Status: Assigned
Jun 23 → Jun 23, 2026
0 business days (counted)
Running total: 266 of ? biz days used
▶ Clock Running
Status: Scheduled
Jun 23 → Jun 30, 2026
5 business days (counted)
Running total: 271 of ? biz days used
▶ Clock Running
Status: Entered
Jun 30 → Jun 30, 2026
0 business days (counted)
Running total: 271 of ? biz days used
▶ Clock Running
Status: Ready for Scheduling
Jun 30 → Jul 3, 2026
2 business days (counted)
Running total: 273 of ? biz days used
▶ Clock Running
Status: Assigned
Jul 3 → Jul 3, 2026
0 business days (counted)
Running total: 273 of ? biz days used
▶ Clock Running
Status: Scheduled
Jul 3 → Jul 7, 2026
2 business days (counted)
Running total: 275 of ? biz days used
Created: Jan 2, 2025Completed: Jul 7, 2026
Show SLA Clock Detail (37 periods)
Period
Status
Clock
Biz Days
Running Total
Jan 2 → Dec 12
Created
▶ Running
236
236
Dec 12 → Mar 4
Ready for Release
⏸ Paused
54
—
Mar 4 → Mar 4
Assigned
▶ Running
0
236
Mar 4 → Mar 16
Scheduled
▶ Running
8
244
Mar 16 → Mar 31
Reschedule
▶ Running
11
255
Mar 31 → Mar 31
Entered
▶ Running
0
255
Mar 31 → Apr 8
Ready for Release
⏸ Paused
6
—
Apr 8 → Apr 8
Assigned
▶ Running
0
255
Apr 8 → Apr 15
Scheduled
▶ Running
5
260
Apr 15 → Apr 15
Entered
▶ Running
0
260
Apr 15 → Apr 29
Ready for Release
⏸ Paused
10
—
Apr 29 → May 1
Assigned
▶ Running
2
262
May 1 → May 1
Entered
▶ Running
0
262
May 1 → May 1
Ready for Release
⏸ Paused
0
—
May 1 → May 1
Entered
▶ Running
0
262
May 1 → May 6
Ready for Release
⏸ Paused
3
—
May 6 → May 6
Assigned
▶ Running
0
262
May 6 → May 6
Scheduled
▶ Running
0
262
May 6 → May 6
Entered
▶ Running
0
262
May 6 → May 13
Ready for Release
⏸ Paused
5
—
May 13 → May 13
Assigned
▶ Running
0
262
May 13 → May 18
Scheduled
▶ Running
3
265
May 18 → May 18
Entered
▶ Running
0
265
May 18 → May 21
Ready for Release
⏸ Paused
3
—
May 21 → May 21
Assigned
▶ Running
0
265
May 21 → May 21
Entered
▶ Running
0
265
May 21 → May 27
Ready for Release
⏸ Paused
3
—
May 27 → May 27
Assigned
▶ Running
0
265
May 27 → May 28
Scheduled
▶ Running
1
266
May 28 → May 28
Entered
▶ Running
0
266
May 28 → Jun 23
Ready for Release
⏸ Paused
17
—
Jun 23 → Jun 23
Assigned
▶ Running
0
266
Jun 23 → Jun 30
Scheduled
▶ Running
5
271
Jun 30 → Jun 30
Entered
▶ Running
0
271
Jun 30 → Jul 3
Ready for Scheduling
▶ Running
2
273
Jul 3 → Jul 3
Assigned
▶ Running
0
273
Jul 3 → Jul 7
Scheduled
▶ Running
2
275
Holding344.3d (excluded)
Coordinators45.6d
Field Work0.0d
Billing19.6d
✗ SLA Missed
Holding(excluded from total)
344.3 days
Coordinators
45.6 days
Over SLA
Field Work
0.0 days
Billing
19.6 days
Over SLA
Created: Jan 2, 2025
Due: Dec 31, 2026
Completed: Jul 7, 2026 (177 days early)
📅
375.7 daysTotal Age
⏱️
236.5d in On HoldLongest Stage
🔄
30 transitionsStatus Changes
⚠️
48.9d 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 • 588 days old
🚨
Primary Delay236.5 days stuck in "On Hold"
⏱️
Total Delay48.9 business days over SLA thresholds
SLA vs Actual Time by Status
Actual (within SLA)
Actual (over SLA)
SLA Target
On Hold
236.5d
Ready for Release
107.8d
Scheduled
28.3d / 2.0d SLA
Reschedule
11.2d / 2.0d SLA
Assigned
3.1d / 0.5d SLA
Ready for Scheduling
3.0d / 1.0d SLA
Completed
0.0d / 1.0d SLA
Closed
1.0d / 1.0d SLA
Ready to Bill
19.6d / 1.0d SLA
Invoice Pending
0.0d / 2.0d SLA
💬 Activities, Notes & Communications
🔒Internal CSA Notes
6/30/26 Rberry- Placed back into RFR due to repair.
🔧Work Performed
7/6 CLacy- PM Service completed to manufacture specs. Functional testing passed. This unit is in proper working condition and is ready to return to service
🔍Technician Findings
PM Service is due
⚠️Problem Description
Please Perform PM: PM Checklist can be found as a link in the work order under WO actions
If Kiosk is not on the Sales floor request to speak to a manager to find out if kiosk is being stored in the back room or if it was disposed. Offer to help bring the kiosk to the salesfloor or advise that EMSAR can replace a disposed kiosk. If store does not want to bring the kiosk out of storage or if kiosk was disposed, close out work order with Repair code '37 Store intervention required' and document who you spoke with and outcome of conversation. Labor line shall be a trip charge.
***Important: Please make sure to document if kiosk is disposed or in storage***
If kiosk fails a PM, checklist is still required to be completed. Please use Code 35 - Follow up needed and detail in the Tech Findings, Work Performed and Final condition the result and cause for a follow up. Close out the work order. Dispatch will create a follow up repair work order to send parts.