Last business day of January 2025 · Target: Jan 31, 2025
✗ SLA Missed (52 biz days late)
Active: 73 biz days
Paused: 100 biz days
🕐 Clock stopped: Completed (Sep 10, 2025)
61d
▶ Clock Running
Status: Created
Jan 2 → Apr 1, 2025
61 business days (counted)
Running total: 61 of ? biz days used
⏸100d
⏸ Clock Paused
Status: Ready for Release
Apr 1 → Aug 22, 2025
100 business days (not counted)
▶ Clock Running
Status: Assigned
Aug 22 → Aug 22, 2025
0 business days (counted)
Running total: 61 of ? biz days used
▶ Clock Running
Status: Scheduled
Aug 22 → Sep 9, 2025
11 business days (counted)
Running total: 72 of ? biz days used
▶ Clock Running
Status: Tech On Site
Sep 9 → Sep 10, 2025
1 business day (counted)
Running total: 73 of ? biz days used
Created: Jan 2, 2025Completed: Sep 10, 2025
Show SLA Clock Detail (5 periods)
Period
Status
Clock
Biz Days
Running Total
Jan 2 → Apr 1
Created
▶ Running
61
61
Apr 1 → Aug 22
Ready for Release
⏸ Paused
100
—
Aug 22 → Aug 22
Assigned
▶ Running
0
61
Aug 22 → Sep 9
Scheduled
▶ Running
11
72
Sep 9 → Sep 10
Tech On Site
▶ Running
1
73
Holding162.5d (excluded)
Coordinators12.0d
Field Work0.7d
Billing16.0d
✗ SLA Missed
Holding(excluded from total)
162.5 days
Coordinators
12.0 days
Over SLA
Field Work
0.7 days
Billing
16.0 days
Over SLA
Created: Jan 2, 2025
Due: Dec 31, 2025
Completed: Sep 10, 2025 (112 days early)
📅
172.5 daysTotal Age
⏱️
101.0d in Ready for ReleaseLongest Stage
🔄
8 transitionsStatus Changes
⚠️
25.0d 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 • 426 days old
🚨
Primary Delay101.0 days stuck in "Ready for Release"
⏱️
Total Delay25.0 business days over SLA thresholds
SLA vs Actual Time by Status
Actual (within SLA)
Actual (over SLA)
SLA Target
On Hold
61.5d
Ready for Release
101.0d
Scheduled
12.0d / 2.0d SLA
Tech On Site
0.7d / 1.0d SLA
Completed
0.0d / 1.0d SLA
Closed
1.0d / 1.0d SLA
Ready to Bill
16.0d / 1.0d SLA
Invoice Pending
0.0d / 2.0d SLA
💬 Activities, Notes & Communications
🔒Internal CSA Notes
9/15/25 lcoonrod
This is not a follow up (35). it is a store issue(37). Location wants the unit removed. marking as resolved and sending chatter to Allison.
🔧Work Performed
On arrival. I was unable to locate the blood pressure kiosk. Pharmacist said it was disconnected and in the break room.
Store manager Gabriel Cudmire mentioned it was disconnected since covid. She also mentioned that she would like the unit removed from the store. Creating follow-up regarding this issue.
Unable to proceed.
🔍Technician Findings
On arrival. I was unable to locate the blood pressure kiosk. Pharmacist said it was disconnected and in the break room.
Store manager Gabriel Cudmire mentioned it was disconnected since covid. She also mentioned that she would like the unit removed from the store. Creating follow-up regarding this issue.
Unable to proceed.
⚠️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.
📄Description
LC300 w/wheelchair accessible cabinet
Sep 15, 2025 4:49pm
@Allison Belyea Hi Allison, This is on our follow up report, but is marked as a 37 (store issue). Notes state location wants it removed.