Chapter 1
Meet Ridgeline Instruments
An electronics manufacturer. Two SMT lines, four assembly cells, three shifts. Their flagship is the Horizon industrial printer line — the boards, assemblies, and finished print engines that go into it, shipping to logistics and healthcare customers. Like almost every plant we've walked, their quality system runs on two things: good engineers and Excel.
Every shift, a QA engineer pulls finished boards and units off the lines and runs the daily product audit: inspect each unit, mark any defects, disposition it PASS or REJECT. The record of that audit is an Excel workbook. One template, used by everyone. That template is where this story starts.
Chapter 2
The template everyone uses
It's a good template. Somebody put real thought into it. You type your name, the date, and your shift into the header block once — then the sheet does the rest for you: it carries your info down every row and computes the disposition automatically. Looks solid, right? Now flip Show formulas in the green bar above the sheet.
Now you see it.
The "data" just disappeared. The engineer's name, the disposition, the defect count — they're not typed-in values, they're formulas pointing at the header block and at other cells. Excel evaluates them at save time, so what any downstream tool actually gets is whatever was cached at the last save, hanging off a layout no table parser can read. Change B3 and every row silently changes with it. Save with calculation off and the file lies.
Keep that in mind. It's about to matter.
Chapter 3
Now multiply by every engineer, every day
Eight QA engineers. Six production days a week. Each one does the right thing: fills out the template and hits Save As. Five months later, the audit folder on SharePoint looks like this.
None of this is anyone's fault. Every engineer did their job — the audits are done, and done well. But nobody's job was to make nine hundred–plus workbooks act like one dataset. So nobody did.
Chapter 4
The Monday it hit the wall
Ridgeline's quality manager gets a reasonable request from a customer: "Show us your defect trends for the last quarter." Easy — the data exists. He points Power BI at the audit folder.
- ERROR Column 'Result' contains mixed types — 41 workbooks saved with calculation off, cached values stale
- ERROR Header block A3:B5 breaks table detection — expected column headers on row 1, found "RIDGELINE INSTRUMENTS — DAILY PRODUCT AUDIT"
- WARN 'Date' parsed as text in 5 distinct formats — "6/29/26", "June 29, 2026", "2026-06-29", "29-Jun", "March 14"
- WARN Column count mismatch — 3 workbooks contain user-added columns ("Notes for Hayes")
And the worst failure never shows up in any log at all: one engineer marks defects with an "x" instead of a 1. The template's =SUM() sees zero, his rejects import as PASS, and the refresh reports success. Loud failures cost you an afternoon. The silent ones cost you a customer.
So the quality manager does what every quality manager in America does. He opens each workbook, selects the data, copies, and pastes-as-values into a master sheet. File by file.
And here's the part that stings: the master sheet is a snapshot. Next Monday there are 44 new workbooks, and the whole exercise starts over. The audits keep getting done. The learning keeps not happening.
Chapter 5
Run the fix yourself
This is the part we build. A pipeline that lives in Ridgeline's own Microsoft tenant, watches the audit folder, and turns every workbook — past and future — into one clean, analysis-ready table. Press the button. This is a simulation of the real run, at about 400× speed.
One clean table. Every audit ever done.
Values, not formulas. One row per unit inspected. Canonical names, ISO dates, explicit zeros. Exactly what Power BI, JMP, or a database wants to eat — and it refreshes itself on schedule. Note the pipeline doesn't silently "fix" everything: rows it can't resolve with confidence get flagged for your team to rule on, not guessed at.
Chapter 6
What the data was hiding
Five months of audits, visible for the first time as one dataset. Within an hour of the first refresh, three findings surfaced that nobody could see one workbook at a time. Every chart below is drawn live from the synthetic data.
Finding 1 — the plant is slipping, and you can put a week on it
Weekly audit pass rate, all products — the sampled proxy for first-pass yield. Each daily audit looked normal. Put 900+ files on one line and you can see the plant drop below its own baseline and stay there — and even catch the one-day incident everyone had already forgotten.
Finding 2a — two defects are most of the problem
Defect Pareto, full period. Misplaced components and solder bridges together account for half of all defects logged. Focus follows.
Finding 2b — the bridging is a night shift problem
HZ-340 print engine, solder-bridge rate by shift in two-week windows. Shifts 1 and 2 hold their baseline; shift 3 jumps the week of June 8 and stays up — the same week a new solder-paste lot started running nights. Now it's a paste-lot conversation, not a hunch.
Finding 3 — a machine asking for maintenance, in writing
p-chart: PS-208 power supply board, weekly reject proportion, provisional control limits set from the Feb–Mar baseline. This is component misplacement from a wearing pick-and-place nozzle — no single day's audit ever looked alarming, but the weekly proportion walks straight through the ceiling. The chart flags it weeks before misplacement becomes scrap and unplanned downtime: you schedule the nozzle change instead of eating the line stop.
Where to walk first — June reject rate, product × shift
The whole plant, one glance. Hover any cell. This is the view a quality manager opens with coffee on Monday.
The point isn't the charts.
Power BI drew these. JMP could take the same clean table and run capability studies and control charts, join it to line and test data for regression — and tell you exactly where a DOE is worth running. The point is that every one of these signals was already sitting in the daily audits — paid for, inspected, recorded — and structurally invisible. The expensive part wasn't collecting the data. It was the last inch: making it usable.
Chapter 7
What the manual version costs
Put your own numbers in. These sliders start at Ridgeline's; adjust them to your plant and watch what copy-paste-as-values actually costs per year.
Straight time only, figured on 250 working days and 50 manager-weeks a year. Doesn't count the decisions made late, the customer report that took two weeks, or the bridging running all month on nights because nobody could see it.
Chapter 8
How this works in your plant
Everything above ran on synthetic data in your browser. The real version is built around one principle that matters to any plant with proprietary product data:
Where your files already live
SharePoint · Teams · network drives · ERP/MES exports
The pipeline — runs in your tenant
Power Automate / Office Scripts / Fabric dataflow, or a small tool we deploy inside your network. Materializes formulas, normalizes, validates, flags exceptions.
Where your team already works
Power BI dashboards · JMP-ready extracts · Teams alerts when a control limit trips
"We already have Copilot."
Keep it — it gets better with what we build. Copilot answers questions about a document. It doesn't crawl 900+ workbooks, materialize formulas into values, enforce a schema, maintain a refreshable Power BI model, or run SPC. That's data engineering, and it's the layer Copilot sits on top of. Clean data in, smarter Copilot out.
"Our data is proprietary."
Good — ours is too. That's why the architecture is tenant-native: the pipeline runs on your Microsoft 365 subscription or on a box inside your firewall, under your access controls and your audit logs. Nothing to breach on our side, nothing to trust but your own tenant.
"We're an Excel shop, not a software shop."
Stay one. Your engineers keep the template they know — or we tighten it up with validation so the "x vs. 1" problem dies at the source. The pipeline meets your data where it is. No new software to learn on the floor, no six-month ERP project.
Who's behind this
Two manufacturing engineers with 30+ combined years on plant floors — daily audits, PPAPs, SPC, JMP, Power BI — who also build software. We've lived the Friday copy-paste. That's why this demo exists.
Take the files with you
The synthetic workbooks from this case study — open them in Excel and see the formula trap yourself, then see what the clean extract looks like.
Chapter 9
The audit problem has cousins
Same disease, different spreadsheet. If any of these live in your plant, the treatment is the same: clean data, in your tenant, visible as a trend.
Bring us one ugly spreadsheet.
Thirty minutes, screen share, no deck. Show us the workbook your team fights with every week and we'll map out — live — what it would take to turn it into the kind of picture you just scrolled through. If it's not a fit, we'll tell you that too.
Book the 30 minutesOr just email john@bluestarcentral.com — subject line: "our ugly spreadsheet." And forward this page to the person who does your Friday copy-paste. They'll know exactly what it's about.