Last business day of January 2025 · Target: Jan 31, 2025
✗ SLA Missed (53 biz days late)
Active: 74 biz days
Paused: 100 biz days
🕐 Clock stopped: Completed (Sep 11, 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 11, 2025
13 business days (counted)
Running total: 74 of ? biz days used
▶ Clock Running
Status: Tech On Site
Sep 11 → Sep 11, 2025
0 business days (counted)
Running total: 74 of ? biz days used
Created: Jan 2, 2025Completed: Sep 11, 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 11
Scheduled
▶ Running
13
74
Sep 11 → Sep 11
Tech On Site
▶ Running
0
74
Holding162.5d (excluded)
Coordinators14.0d
Field Work1.0d
Billing13.4d
✗ SLA Missed
Holding(excluded from total)
162.5 days
Coordinators
14.0 days
Over SLA
Field Work
1.0 days
Billing
13.4 days
Over SLA
Created: Jan 2, 2025
Due: Dec 31, 2025
Completed: Sep 11, 2025 (111 days early)
📅
174.5 daysTotal Age
⏱️
101.0d in Ready for ReleaseLongest Stage
🔄
8 transitionsStatus Changes
⚠️
24.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 • 426 days old
🚨
Primary Delay101.0 days stuck in "Ready for Release"
⏱️
Total Delay24.5 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
Assigned
0.0d / 0.5d SLA
Scheduled
14.0d / 2.0d SLA
Tech On Site
1.0d / 1.0d SLA
Closed
1.1d / 1.0d SLA
Ready to Bill
13.4d / 1.0d SLA
Invoice Pending
0.0d / 2.0d SLA
💬 Activities, Notes & Communications
🔧Work Performed
On arrival. Unit was up and running, LEDs functioning. Cabinetry in good shape.
while performing maintenance, I noticed that if the cabinet was lightly bumped the unit would turn on and start a user testing cycle. Inspected for loose connections internally. Unable to find a loose connection.
Will create follow-up.
🔍Technician Findings
On arrival. Unit was up and running, LEDs functioning. Cabinetry in good shape.
while performing maintenance, I noticed that if the cabinet was lightly bumped the unit would turn on and start a user testing cycle. Inspected for loose connections internally. Unable to find a loose connection.
Will create follow-up.
⚠️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
Model 300 with Backboard
Sep 15, 2025 5:26pm
@David Trost I saw your note we are sending a pod and cuff there is not a controller box