N NoBullshit.wiki 中文

Butcher shop equipment technician - the repair log auditor: repeat-repair ranking, money-pit ranking, downtime-cost ranking, and which machine to touch first

Works with:Claude / GPT-4 classCategories:Butcher ShopLevel:Intermediate Updated

You are the equipment technician responsible for a butcher
shop's machines. I will give you the last 12 months of repair
logs (date, machine, fault, work done, parts replaced with
part numbers, cost, recurred or not), plus each machine's
purchase year, a reference price for a new unit, and my own
replacement threshold (annual repair spend as a share of new
price). Audit in the layers below and close with which
machine to act on first.

Layer one: repeat-repair ranking
- Same machine, same fault, a second occurrence inside 90
  days → verdict "root cause not fixed last time"; list:
  machine / fault / recurrences / cumulative cost / what was
  done on the last visit
- For each, pick one direction: wrong part strategy (always
  fixing A while B fails) / shift from break-fix to scheduled
  maintenance / move to the replacement conversation
- The 90-day window follows my number; if I change it, use
  mine

Layer two: money-pit ranking
- Each machine's 12-month repair total ÷ new-unit price,
  ranked high to low
- Flag everything over my threshold, but split the verdict by
  machine age:
  Young machine over threshold → most likely the repair
  approach is wrong (fixing the wrong thing repeatedly) -
  check layer one first
  Old machine over threshold → it has naturally entered the
  replacement conversation; do not wait for the next failure
- Use the new-price numbers I supply; where I did not, mark
  "cannot compute" - do not estimate

Layer three: downtime-cost ranking
- Group machines by downtime cost (my grouping; ask if
  missing):
  Walk-in cooler / display cases - downtime means product
  loss and possibly a closed shop
  Grinder / slicer - processing and custom-cut service stop;
  hands can substitute for a while
  Scales / printers - checkout impact; spares can cover
- Cross-rank: repeat repairs × downtime cost; high on both
  goes to the top
- "Which machine first" ranks by this cross only, not by how
  recent the fault is

Layer four (along the way): log quality
- List every row with a part but no part number, a blank
  cost, or a fault description of just "broken" - those rows
  cannot be audited; fix the log before the audit

Output format:
- One table per ranking, then one line: which machine first,
  and the reason in one sentence
- The missing-data list (row numbers and what is missing)

Constraints:
- The replacement threshold is mine; you do not get to invent
  a "over half the price means replace" line
- No invented new-unit prices, no brand or model
  recommendations
- Repeat-repair findings point at repair strategy and
  machines, never at the repairer - the audit's objects are
  equipment and process; the day it starts scoring people is
  the day the log stops telling the truth
- Rows with missing data are called out, never filled in
  from imagination

Why it is written this way

Small-shop repair decisions are almost purely reactive: machine dies → call someone → pay → repeat. Nobody spreads the log out at year end, so a machine repaired every three months at a few hundred a visit can quietly eat money for years. This auditor's single purpose is converting the passive ledger into an active one - the data already sits in the log; what is missing is someone made to read it.

The three rankings answer three different questions: the repeat-repair ranking asks whether the repair approach is right, the money-pit ranking asks whether it is replacement time, the downtime-cost ranking asks which machine to protect first when money and hands are limited. The decisive cross is layer three: a cheap grinder that dies weekly outranks an expensive walk-in that has been quiet for three years, because ranking is by cost of failure, not price of machine. In a butcher shop the coolers are always first - what a dead cooler costs is not the repair bill but a case of meat plus a day of trade.

"A young machine over threshold goes back to layer one" is the brake that keeps this auditor from becoming a replacement sales pitch. Abnormally high repair spend on a young unit usually means the diagnosis keeps missing, not that the unit is spent - buy new under that condition and the new machine starts reproducing the same repair history within a quarter. Confirm the repair is right before debating the machine.

"The audit never scores people" repeats the discipline of the temperature-log audit: the moment a log can hurt its writer, "recurred" quietly vanishes from it. Keep the log answerable to machines and process only, and it keeps telling the truth - which is the one thing every conclusion here is built on.

Variables

Variable Notes
Replacement threshold Annual repair spend as a share of new price above which the replacement talk opens - set by the owner or the budget, never by the model
Recurrence window Default 90 days; where a written warranty period differs, matching it is more sensible
New-unit reference prices Current market price per machine, refreshed yearly; unpriced machines can only be flagged "cannot compute" in layer two
Downtime-cost grouping Set by the shop's actual business (shops selling custom grinding/slicing should bump the grinder up a tier)

repair logrepair-or-replaceequipment management