DC3-AI Performance Optimisation

Home / Examples / Repair workshop

Example · live production dashboard

The workshop, live

The dashboard behind the morning report. Each technician signs in with their help-desk account and sees their own scoreboard; managers see the whole team, the honest date for any customer’s unit, and every open order with whose move it is.

Workshop · production dashboardTue 6 Oct, 09:04
Help desk · timesheets · books
refreshed every few minutes

Jobs finished, warranty repairs and activities closed, for everyone on the bench. Week of 5 Oct, to date: weekday 2 of 5.

Jobs finished
41
33 invoiced · 8 awaiting invoice
Warranty repairs
4
extra work, not in jobs
Activities closed
25
72% after due date
Open bench work, assigned
258
124 activities overdue
TechnicianJobs finishedtarget 20 a week · 8 expected by nowWarrantyActivities closedOpen · mineReopenedcustomer replied
Sam Okafor
945%ahead by 1
042912
Lena Park
735%behind by 1
13249
Marco Ruiz
630%behind by 2
023114
Priya Shah
525%behind by 3 · 2 warranty repairs
26174
Tom Becker
525%behind by 3
013617
Ava Lindqvist
420%behind by 4
13258
Jonah Reid
315%behind by 5
023011
Mia Torres
210%behind by 6
04266
Owen Hart
00%no hours and no leave on Monday: confirm
00227
Kai Morgan
0leaveon leave Mon–Tue: target lowered
00185
Team · 10 technicians4133 invoiced · 8 awaiting42525893

Targets are fixed: leave and company holidays lower them, nothing else does. A week’s share is spread evenly over its weekdays, so “expected by now” is fair on a Tuesday. A ticket reopened because the customer replied is its own column and never counted inside open work.

What is waiting on the team

Pre-work122unit here, bench work not started
On the bench106being tested or repaired
On hold27waiting on the customer or parts
Not started3created and never touched

Example from client work. Products renamed Alpha to Iota, technicians renamed, and every figure changed, so the business cannot be identified.