← Full case study Score one-pager

This sheet is the companion page to the Plant Score one-pager: what the current reporting pipeline costs, priced the same way the plant is scored.

Blue Star Pipeline Cost Sheet
Ridgeline Instruments · fictional demo plant
Timed at the Jun 2 walkthrough · companion to the Plant Score one-pager
$55,500
per year — the Friday report
18.5
engineer-hours
every week
925
hours a year —
call it half an engineer
$1,110
every week, whether
anyone trusts it or not

Printed assumptions — change either and every number on this page recomputes by hand: $60/hr fully-loaded engineer time · 50 working weeks. Line math: hrs/week × 50 × $60.

Where the hours go  — five lines, each tagged with how we know it

TOTAL — 18.5 hrs/week · 925 hrs/yr$55,500
Not priced —
on purpose

$ —

The exit  — fixed prices, and every move has a do-it-yourself path

Shop Data Snapshot — run this same timing worksheet on your pipeline: measured hours, not guessed ones, plus where they go. DIY: the timing worksheet is in the report appendix — hold your own stopwatch $1,500 fixed
Kill the Friday Report — values keyed once into a flat entry sheet, one clean table, and the same report assembles itself every week. Built inside your own tenant. DIY: values-only entry sheet + one shared workbook per line — template included $3,000 fixed
Two Systems, One Truth — when Ops and Quality stop reconciling because the contested numbers have one signed definition and one system of record. DIY: definitions worksheet + a 1-hour cross-shift review $5,000 fixed

On this plant's numbers: $3,000 ÷ $1,110/week → the Friday-report fix pays for itself in week 3 — counting only the hours above, and none of the unpriced line. Keep-It-Running retainer afterward: $250–500/mo.

What Friday looks like after

Values keyed once — or reported by the machines. One table feeds the same report every week, and the number a customer asks about traces to its source in one click. The Monday meeting argues about what to do, not whose number is right.

How this connects to the score

Build & Check → SEE (number integrity) · Defend → TRACE (find the source) · Fix → ADOPT (one standard) · Change → RETAIN (survives a template, survives a retirement).

In lean terms this page prices overprocessing and waiting — in payroll, not in slogans. The score tells you whether the system that produced it can see itself.

Every line is tagged with how we know it (measured · assessed · self-reported) — and self-reported never outranks measured. What we didn't measure stays out of the total: unmeasured leaves the math. Findings indict the process, never the people. Your data never leaves your building. Ridgeline Instruments is fictional; every number on this sheet is synthetic and recomputes by hand.

plant.bluestarscore.comjohn@bluestarcentral.com · Blue Star Labs