Excel vs ERP for medical device manufacturing: when spreadsheets stop coping

A lot of precision and device plants run on a familiar set of records: a paper traveller that goes with each batch, an inspection workbook kept by QC, a stores register for material lots, and a calibration list on the quality manager's computer. Many of them pass customer and certification audits that way, because the people keeping the records are careful.

That is not a weakness to be ashamed of. Spreadsheets are flexible and everyone can use them. The question is when the effort of keeping separate files complete and in agreement grows past what the team can do reliably, and the batch record starts to depend on people remembering to fill gaps.

Where Excel works well in a device plant

• Quotations and cost models, built and owned by one person.
• One-off analysis: a capability study on a dimension, a scrap Pareto, a supplier comparison.
• A small plant with a few part numbers, one shift and one person who owns every record.
• Trend charts and reports drawn from data that already sits in a system.

Where do spreadsheets become difficult?

The batch record is assembled afterwards

With travellers and separate sheets, the batch record exists only once QA collects the pieces. Missing initials, a blank inspection line or an issue slip without a lot number are found at review, sometimes days later, when the person who did the work cannot be sure what they did.

Inspection results do not name the instrument

The inspection sheet has a column for the value, and the calibration list has a column for the due date, but they are different files. When a gauge fails calibration, finding every batch it measured since its last good check means reading through old sheets, if the instrument was written down at all.

Several people, several copies

Planning, stores and QC each keep their own workbook. A revised drawing reaches one file and not the others, and someone works to the old revision. Shared drives help, but it is still easy to open a copy saved last week.

Nonconforming parts on loose sheets

A held batch, a rework and a use as is decision should be one connected record. In spreadsheets they are often separate lines, or a note on the traveller, and the re-inspection is not clearly linked to the rework it followed.

Change history and corrections

An auditor will ask what an entry said before it was corrected, who corrected it and when. An edited cell keeps none of that unless the workbook was built to, and keeping such a workbook locked and controlled is itself work. Spreadsheets used for quality records are software in an auditor's eyes, and are treated that way.

Traces for complaints

A complaint arrives with a batch number. Answering which material lots went into it, who machined it, what the critical dimensions measured and where the rest of the batch went means opening several files and registers. It can be done; it just takes a day that the quality team does not have.

Material and batch status

Whether a lot is quarantined, accepted or held, and whether a finished batch is released, is often a label on the bin and a note in a sheet. When the two disagree, material that should not be used can be.

Spreadsheets and ERP compared, task by task

An ERP is an operational system, not a bigger spreadsheet

What changes is the moment the batch record gets written. A spreadsheet is filled in after the work, from paper or memory. A manufacturing ERP with floor recording is filled in during the work: stores issues a lot to the batch, the operator logs the count at the operation, QC enters the measured value with the instrument before the batch moves on. The batch record is read from those entries rather than written up.

That is why an ERP that covers only the office often disappoints a device plant. The files that cause the audit findings are the floor files: the traveller, the inspection sheet, the nonconformance log. A system that leaves those on paper leaves the problem where it was.

When should a medical device manufacturer move from Excel to ERP?

There is no plant size at which spreadsheets stop being allowed. The practical test is how often the files fail to give a complete, current answer. These are the triggers plants most often name.

• Several people edit the same records. Planning, stores and QC each keep a copy, and they do not always agree.
• More than one line or cell runs at once. A machining cell, a cleaning line and a cleanroom packing station each produce records, and nobody sees them together.
• Drawings and revisions change often. Keeping every traveller and inspection sheet on the right revision has become a job in itself.
• Material lots are hard to follow. A heat number on the receipt does not reliably reach the batch it was used in.
• Production updates arrive late. Counts and scrap reach the office the next day, so planning works on yesterday's position.
• QC records are kept by hand. Measured values are on paper or in a workbook with no link to the batch or the instrument.
• A trace takes more than an hour. A complaint or a supplier notice means opening several files to find the affected batches.
• Rework and nonconformance cannot be seen. Nobody can say how many parts were reworked last month, at which operation, or who approved them.
• Customer requirements are growing. A device maker's audit or a new market asks for records that take days to put together.
• Current WIP is unknown. Finding out how many parts are at each operation, at the anodiser or at the steriliser needs a walk round the plant and a phone call.

None of these means the spreadsheets have failed. They mean the plant has grown past what separate files can hold reliably. When two or three show up in the same quarter, QA is usually spending more hours keeping files in agreement than a system would take to run. The guide to implementing ERP in a medical device plant covers what the move involves, including your own validation.

Keeping what works

QC will still open Excel after go-live. Capability studies, quotation models and trend analysis stay in spreadsheets, fed by exports. What moves is the operational record: orders, material by lot, counts, inspections, dispositions and dispatch. In FleekERP that record sits on the work order, with quality control and inventory and lot traceability on the same batch, while the books stay in Tally or Zoho.

One caution: FleekERP is not validated for ISO 13485 or 21 CFR Part 11. Moving records into any system means validating it for your use, as you would a controlled spreadsheet. For how lot-to-unit trace and instrument-linked inspection run on one record, see FleekERP for medical device makers.