Last business day of January 2026 · Target: Jan 30, 2026
⚠ 78 biz days overdue
Active: 94 biz days
Paused: 58 biz days
▶ Clock Running
Status: Created
Jan 7 → Jan 7, 2026
0 business days (counted)
Running total: 0 of ? biz days used
▶ Clock Running
Status: Ready for Scheduling
Jan 7 → Jan 7, 2026
0 business days (counted)
Running total: 0 of ? biz days used
⏸58d
⏸ Clock Paused
Status: Ready for Release
Jan 7 → Apr 1, 2026
58 business days (not counted)
▶ Clock Running
Status: Entered
Apr 1 → Apr 1, 2026
0 business days (counted)
Running total: 0 of ? biz days used
47d
▶ Clock Running
Status: On Hold
Apr 1 → Jun 8, 2026
47 business days (counted)
Running total: 47 of ? biz days used
▶ Clock Running
Status: Ready for Scheduling
Jun 8 → Jun 12, 2026
4 business days (counted)
Running total: 51 of ? biz days used
▶ Clock Running
Status: Entered
Jun 12 → Jun 12, 2026
0 business days (counted)
Running total: 51 of ? biz days used
▶ Clock Running
Status: On Hold
Jun 12 → Jun 19, 2026
4 business days (counted)
Running total: 55 of ? biz days used
▶ Clock Running
Status: Ready for Scheduling
Jun 19 → Jun 22, 2026
1 business day (counted)
Running total: 56 of ? biz days used
▶ Clock Running
Status: Assigned
Jun 22 → Jun 22, 2026
0 business days (counted)
Running total: 56 of ? biz days used
▶ Clock Running
Status: Ready for Scheduling
Jun 22 → Jul 8, 2026
11 business days (counted)
Running total: 67 of ? biz days used
27d
▶ Clock Running
Status: Assigned
Jul 8 → Aug 16, 2026
27 business days (counted)
Running total: 94 of ? biz days used
Created: Jan 7, 2026Today
Show SLA Clock Detail (12 periods)
Period
Status
Clock
Biz Days
Running Total
Jan 7 → Jan 7
Created
▶ Running
0
0
Jan 7 → Jan 7
Ready for Scheduling
▶ Running
0
0
Jan 7 → Apr 1
Ready for Release
⏸ Paused
58
—
Apr 1 → Apr 1
Entered
▶ Running
0
0
Apr 1 → Jun 8
On Hold
▶ Running
47
47
Jun 8 → Jun 12
Ready for Scheduling
▶ Running
4
51
Jun 12 → Jun 12
Entered
▶ Running
0
51
Jun 12 → Jun 19
On Hold
▶ Running
4
55
Jun 19 → Jun 22
Ready for Scheduling
▶ Running
1
56
Jun 22 → Jun 22
Assigned
▶ Running
0
56
Jun 22 → Jul 8
Ready for Scheduling
▶ Running
11
67
Jul 8 → Aug 16
Assigned
▶ Running
27
94
Dispatch0.3d
Holding110.7d (excluded)
Coordinators18.3d
⚠ Overdue
Dispatch
0.3 days
Holding(excluded from total)
110.7 days
Coordinators
18.3 days
Over SLA
Created: Jan 7, 2026
Due: May 31, 2026 (77 days overdue)
📅
153.0 daysTotal Age
⏱️
58.3d in Ready for ReleaseLongest Stage
🔄
9 transitionsStatus Changes
⚠️
14.9d overTotal Delay
📦
0 orders, 0 quotesParts & Quotes
📝
0 linesWork Details
📋
CoordinatorScheduling
AI Analysis
Powered by OpenAI
Generating AI analysis...
Behind Schedule - Needs Attention
Assigned • 221 days old
🚨
Primary Delay58.3 days stuck in "Ready for Release"
⏱️
Total Delay14.9 business days over SLA thresholds
SLA vs Actual Time by Status
Actual (within SLA)
Actual (over SLA)
SLA Target
Entered
0.3d / 0.5d SLA
Ready for Scheduling
18.3d / 1.0d SLA
Ready for Release
58.3d
On Hold
52.4d
Assigned
0.1d / 0.5d SLA
💬 Activities, Notes & Communications
🔒Internal CSA Notes
7/13/26 RBerry- Emailed Alex Buban to schedule for 7/14/26 with an arrival time between 11AM-1PM. Waiting for confirmation. See logged email.
7/13/26 RBerry- Lm with Alex Buban to schedule for 7/14/26 with an arrival time between 11AM-1PM. Could not log call in RC. Logged call manually.
7/10/26 Rberry- Emailed Alex Buban to schedule for 7/14/26 with an arrival time between 11AM-1PM. Waiting for confirmation. See logged email.
7/10/26 RBerry- Lm with Alex Buban to schedule for 7/14/26 with an arrival time between 11AM-1PM.
6/29/26 RBerry-Sent email to tech sup/FOD to discuss how this WO will be covered.
6/23/2026 CRamen talked about in scheduling meeting with LYoder in that we have all techs booked for weeks out and dont have a current resolution on scheduling a tech to cover kiosk in past due status and upcoming for due end of this month.
6/12/2026 CRamen called and none of the promts get me to a person to schedule this 763-514-5000 800-633-8766 as well.
6/12/2026 CRamen 303-530-2300 is no longer in service.
06/08 Updated POC please schedule
4/1/2026 CRamen called the listed #515-599-4950 and message says this number is not in use. Good Bye! Returning to dispatch and placing On Hold and escalating to AM.
🔧Work Performed
6/12/2026 CRamen called and none of the promts get me to a person to schedule this 763-514-5000 800-633-8766 as well.
6/12/2026 CRamen 303-530-2300 is no longer in service.
⚠️Problem Description
Please Perform the PM for this Kiosk based on the product listed in the work order: 90550, LC300, LC500.
***IMPORTANT CHANGE****
Please Log/notate in the technician findings the number of times the kiosk was used and double check the SN. If the SN is different than in the work order please also notate the correct SN. Regardless if the SN matches continue to perform the PM service.
If location is a non-retail location a call ahead to schedule is required
PM Checklist Tips:
If Checklist is not populating, make sure the order type contains 'PM' and the product must contain an 90550, LC300 or LC500. Update the order status to 'tech onsite' and the workflow will look for the parameters in which a PM checklist is required and will auto attach.
Common missed step: After you Finalize the checklist you must select 'Print checklist' for the checklist to attach to the work order for the billing reviewer to review.
**IMPORTANT** This is a non-retail location and an appointment must be coordinated in advance. If the technician or scheduler is unable to make contact with the onsite point of contact, they must notify Texas Medical Screening before departing the site. TMS may be able to provide an alternate contact or additional site access information.
Primary TMS Contact: James Williams Phone: 726-202-3465. All contact attempts must be logged on the work order, including who was contacted, the date and time of the attempt, the phone number called, and the outcome of the communication attempt.
📄Description
90550,BP MONITOR, NO AD DISPLAY
📧
Email:Fw: EMSAR Request for service at MEDTRONIC (Email to schedule service)
Completed Jul 13, 2026
From: rhea.berry@emsar.com
To: alex.t.buban@medtronic.com
Cc: cramen@emsar.com
Hi ALEX BUBAN,I hope you’re doing well. I’m reaching out to schedule a service appointment for the preventative maintenance on your blood pressure machine.Here’s the location information we have on file:Location:MEDTRONIC4600 NATHAN LANEPLYMOUTH, MN 55442Contact:ALEX BUBAN262-705-6601We currently have availability on 7/14/26 with an arrival window between 11AM-1PM. Please let us know if this works for you, or if
📞
Call
Completed Jul 13, 2026
7/13/26 RBerry- Lm with Alex Buban to schedule for 7/14/26 with an arrival time between 11AM-1PM. Could not log call in RC. Logged call manually.
📧
Email: EMSAR Request for service at MEDTRONIC (Email to schedule service)
Completed Jul 10, 2026
To: alex.t.buban@medtronic.com
CC: cramen@emsar.com
BCC: rhea.berry@emsar.com
Attachment: --none--
Subject: EMSAR Request for service at MEDTRONIC (Email to schedule service)
Body:
Hi ALEX BUBAN,
I hope you’re doing well. I’m reaching out to schedule a service appointment for the preventative maintenance on your blood pressure machine.
Here’s the location information we have on file:
Location:
MEDTRONIC
4600 NATHAN LANE
PLYMOUTH, MN 55442
Contact:
ALEX BUBAN
262-705-6601
We currently h
📋
Outbound to +12627056601
Completed Jul 10, 2026
7/10/26 RBerry- Lm with Alex Buban to schedule for 7/14/26 with an arrival time between 11AM-1PM.
📋
Outbound to +13035302300
Completed Jun 12, 2026
6/12/2026 CRamen called and none of the promts get me to a person to schedule this 763-514-5000
6/12/2026 CRamen 303-530-2300 is no longer in service.
Timeline
📋
Work Order Created Jan 7, 11:09 AM
Work Order:WO-01333996
Type:Preventive Maintenance
Priority:PSM
📅
Status: Ready for Scheduling by Jessica FoleyJan 7, 1:43 PM
From:Entered
To:Ready for Scheduling
Duration in Previous:2h 33m
✅
Status: Ready for Release by Allison BelyeaJan 7, 4:36 PM
From:Ready for Scheduling
To:Ready for Release
Duration in Previous:2h 52m
🚨58.9 business days
🆕
Status: Entered by Charles RamenApr 1, 4:15 PM
From:Ready for Release, Entered
To:Entered, On Hold
Duration in Previous:83d 22h, 0m
🚨48.0 business days
📅
Status: Ready for Scheduling by Chris BakkemoJun 8, 12:17 PM
From:On Hold
To:Ready for Scheduling
Duration in Previous:67d 20h
⚠️5.0 business days
🆕
Status: Entered by Charles RamenJun 12, 12:09 PM
From:Ready for Scheduling, Entered
To:Entered, On Hold
Duration in Previous:3d 23h, 0m
⚠️5.0 business days
📅
Status: Ready for Scheduling by Chris BakkemoJun 19, 2:55 PM
From:On Hold
To:Ready for Scheduling
Duration in Previous:7d 2h
⏳1.0 business days
👷
▶
2
Technician Assigned Jun 22, 11:51 AM
Technician Assigned → Status: Assigned
👷
Status: Assigned by Kaitlyn Kelch
From:Ready for Scheduling
To:Assigned
Duration in Previous:2d 20h
📅
Status: Ready for Scheduling by Rhea BerryJun 22, 12:31 PM
From:Assigned
To:Ready for Scheduling
Duration in Previous:40m
🚨12.0 business days
👷
▶
2
Technician Assigned Jul 8, 4:19 PM
Technician Assigned → Status: Assigned
👷
Status: Assigned by Rhea Berry
From:Ready for Scheduling
To:Assigned
Duration in Previous:16d 3h
Bottlenecks
Ready for Scheduling
Duration: 5.0 business days (threshold: 1.0 business days)
Exceeded by 4.0 business days
Ready for Scheduling
Duration: 11.9 business days (threshold: 1.0 business days)