Print Farm Production Metrics: What to Track and Why
Most print farm operators have a feel for how their farm is performing. Fewer have actual numbers. The gap matters: a farm that feels productive but has a 15% failure rate and 55% utilization is significantly underperforming what the hardware is capable of — and without measurement, you can't tell the difference between "running well" and "running below potential."
These are the metrics worth tracking, what they tell you, and what to do with them.
Utilization rate
Definition: billable print hours ÷ available print hours, expressed as a percentage.
How to calculate: total hours your printers were actively printing on paying jobs in a given period, divided by total hours they could have been printing (printer count × hours per day × days). A 10-printer farm running 18 hours/day for 7 days has 1,260 available hours per week.
What it tells you: the gap between what you could produce and what you're actually producing. Every percentage point of utilization is real revenue on the table.
Benchmarks:
- Below 50%: demand problem or queue management problem
- 50–65%: reasonable but improvable — look at idle gaps and queue depth
- 65–80%: good production efficiency for a running farm
- Above 80%: strong — focus on failure rate and quality, not throughput
Why it moves: utilization drops from idle gaps between jobs (queue management), unexpected downtime (maintenance, failures), and genuine demand gaps. Diagnosing which is which tells you whether the fix is operational or commercial.
Failure rate
Definition: failed jobs ÷ total jobs attempted, expressed as a percentage.
How to calculate: count of prints that didn't complete successfully (spaghetti, adhesion failure, mid-print clog, dimensional failure on inspection) divided by total prints started in the period.
What it tells you: the overhead tax on your capacity. Every failed print consumes machine time and material that could have gone to a successful job. At 10% failure rate, you're effectively running at 90% of your printed-unit output versus capacity.
Benchmarks by material:
- PLA, standard geometry: 2–4% is achievable
- PETG, moderate geometry: 4–7%
- ABS/ASA, enclosed: 6–10%
- Above 12% on any material consistently: systemic problem worth investigating
Track failure by printer: if printer 4 has a 14% failure rate and the fleet average is 5%, printer 4 has a problem. Hardware wear, calibration drift, or a bad batch of material are the usual culprits. You won't find this without per-printer data.
Material cost per successful unit
Definition: total filament cost (including waste and failed prints) ÷ successful units produced.
How to calculate: track filament consumed per job (slicer estimates, adjusted by actual spool weight change for precision). Divide total filament cost by successful completed units in the period.
What it tells you: actual material cost per unit, which is almost always higher than the slicer's model-weight estimate because it excludes purge, support, and failure waste. This is the number that belongs in your cost model for pricing.
Common finding: operators discover their actual material cost per unit is 20–40% higher than they estimated, because failure waste and purge weren't accounted for. This has direct margin implications.
Average revenue per print hour
Definition: total revenue from print jobs ÷ total billable print hours in the period.
How to calculate: sum of all job revenue divided by sum of all job print times (excluding failed runs that didn't bill).
What it tells you: the revenue density of your job mix. A farm doing high-volume low-margin jobs generates less per print hour than one doing specialized high-margin work. Tracking this over time shows whether your mix is improving.
How to use it: when revenue per print hour is low, look at whether job pricing is appropriate or whether you're taking on too many low-margin jobs. When it's high, understand what job types are driving it and sell more of them.
Queue depth and idle gap time
Definition: average number of jobs waiting per printer at any given time; average idle time between job completion and next job start.
What it tells you: whether your queue management is keeping printers fed. An idle gap of 30+ minutes between jobs on average represents significant lost utilization — at 10 printers running 18-hour days, 30-minute average idle gaps lose 1.25 hours of capacity per printer per day, or 12.5 hours across the fleet daily.
What causes idle gaps: manual job assignment (someone has to notice the printer finished and assign the next job), small queue depth (not enough jobs buffered to auto-assign), and printer capability mismatches (the next job requires a material or profile that printer doesn't have loaded).
Automated job routing that assigns the next job immediately when a printer finishes eliminates idle gaps caused by the first two factors. This is one of the highest-leverage operational improvements available to a farm running manual queue management.
Revenue per printer per day
Definition: total revenue ÷ printer count ÷ days in period.
What it tells you: the blended productivity of each printer on your farm. A simple number that captures utilization, failure rate, and job mix in a single metric.
How to use it: as a farm health indicator. If revenue per printer per day is trending down over a month while printer count is stable, something is wrong — demand has dropped, failure rate has risen, or utilization has fallen. Spot the trend; investigate the cause.
Benchmark: for a farm running $6–8/hour gross margin at 70% utilization on an 18-hour day, revenue per printer per day works out to $75–100. This varies widely by pricing model and market.
How to actually capture this data
Without tooling, tracking these metrics requires manually logging job starts, completions, failures, and material weights — significant overhead at scale.
With Print Hive, print hours, failure events, job completion times, and material tracking are recorded automatically per printer. The metrics above are derivable from the underlying data without manual logging. At 5+ printers, the overhead of manual tracking becomes significant enough that automated data collection pays for itself in the time it saves.
The minimum viable approach without dedicated software: a simple spreadsheet with one row per job (printer, start time, end time, material weight, result: pass/fail, revenue). Takes 2 minutes per job to maintain; gives you the raw data to calculate everything above weekly.
Track consistently. The value of metrics is in the trend, not the snapshot.
Print Hive automatically tracks print hours, failure events, material consumption, and job history per printer — the data foundation for calculating and improving your farm's key production metrics. Start free →