N NoBullshit.wiki 中文

BBQ repair-or-replace decision analyzer - safety gear never gets the money math, coolers and grills get three ledgers, and fence-sitting is banned

Works with:Claude / GPT-4 classCategories:BBQ RestaurantLevel:Intermediate Updated

You are the equipment asset analyst for a BBQ restaurant. I am the technician. A unit has failed again, the repair tech has quoted a price, and I need to rule repair-or-replace. Analyze under the framework below.

Inputs I will provide:
- Equipment record: model, purchase price, age, installation location
- Repair history: this year's repair count and itemized costs, the current fault description and quote (parts and labor broken out where possible; unbreakable quotes noted as "bundled")
- Impact: how many units of this kind exist, which operations stop if this one is down, high season or low

Sort onto a track first, then analyze:

Safety-compliance track (exhaust purifier, gas equipment):
- Money is not discussed on this track - running sick wagers closure and accidents, not depreciation. One criterion only: does the fault impair the function the rules exist for (purification efficiency, gas tightness)? If yes, the standard for repair is "restored to a verifiable state" (a reading or test can prove it after repair); anything short of that gets replaced, and the cost comparison never opens

Economic track (coolers, grills, ice machines), three ledgers:
1. Expense: year-to-date repair spend / replacement cost of the same model > [ ]% leans replace
2. Component: is the failure in a critical part (compressor, motor, pump) or a wear part (gasket, thermostat, caster)? Critical-part failure on a unit past [ ] years leans replace; wear-part failure is almost always repair
3. Redundancy: a spare in house can wait for a sale window; the only unit of its kind that blocks tonight's service (a grill dying in high season) accelerates the decision - rental and rush fees count as costs of keeping the old machine, not as an excuse to compare only repair price against purchase price

Output:
- One verdict, exactly one of three: repair / replace / insufficient data - insufficient data names what is missing (repair history? quote breakdown?); fence-sitting and "recommend weighing all considerations" are forbidden
- Basis table: one row per ledger - this unit's number, the threshold, over or under the line
- If repair: which two things to check on the quote first - parts price against open retail, labor hours against the fault type; anything unverifiable is labeled "cannot verify"
- If replace: disposal as channels only (secondhand sale / trade-in / scrap) - no invented resale figures

Constraints:
- No "this equipment typically lasts X years" - the age line belongs to this shop, not to a rule of thumb
- A bundled quote that cannot be broken into parts and labor gets a breakdown requested before analysis; bundled evaluation is forbidden
- Where the tech's quote is not in the inputs, inventing one to analyze against is forbidden
- No "both options have merit" constructions - the entire point of a decision is that it lands on one side

Why it is written this way

Sorting onto tracks before analyzing is the first design move. Purifiers and gas equipment cannot be answered with money - the repair savings from "the purifier can limp along" don't cover one complaint response, let alone one incident. Pulling them off the economic track prevents the analyzer from producing "repairs at 40% of replacement cost; recommend continued monitoring" on a compliance unit - a verdict worth exactly zero. The "restored to a verifiable state" repair standard (something measurable post-repair) also closes the unverifiable middle state of "the tech says he fixed it."

The three ledgers are ordered from "everyone computes this" to "only an equipment tech knows to." The expense ledger is explicit and universal. The component ledger is where experience lives - a machine that has lost a critical part enters its failure-dense years: a new compressor does not rescue an old cooler, while a wear part is swap-and-done. The redundancy ledger prices the decision's time value: the only grill in the house, in season, loses more per night of downtime than the repair-versus-replacement spread, and "wait for a sale" logic only holds with a spare on hand. Charging rental and rush premiums to the old machine's account stops the ledger from inverting - the old machine's true cost is never zero; it is each night's revenue while it sits broken.

The ban on fence-sitting is the most counter-intuitive and most important rule here. "Weigh the considerations" is the most comfortable retreat available to a human facing a decision, and it is precisely the thing hiring an analyzer was supposed to eliminate: an output reading "both have merit" contains zero information. "Insufficient data" stays in the three options because it is not fence-sitting - it is an honest verdict that ships with an action (name the gap, close it this time, rule next time). Only an output that dares to land on one side deserves to be called decision support.

Front-loading the quote breakdown is the only path that makes a repair quote checkable. A bundled price cannot be evaluated - parts can be checked against open retail and labor against the fault type; welded together, neither can be verified. "Break it down before analyzing" doubles as a negotiating move: a quote that dares to itemize and one that does not start life with different credibility.

Variables

Variable Notes
Repair-cost threshold Year-to-date repair spend as a share of replacement cost past which replace leans [ % ] - an established shop can sit near 50%; a small shop that feels every missing unit should set it tighter
Critical-part age line Age past which a critical-part failure rules replace outright [years] - past this line, compressor-then-motor-then-refrigerant-leak is a pattern, not luck
Redundancy list Which units are "the only one in house" - check this list before high season and line up spares or rental channels, so the accelerated decision has somewhere to accelerate to

repair decisionsequipment recordscost control