Excel vs ERP for automotive manufacturing: where spreadsheets stop coping

Most automotive component plants did not choose spreadsheets. They grew into them. A planner built a schedule sheet, stores added a stock sheet, quality kept an inspection workbook, and over a few years the plant came to run on a set of files that only their owners fully understand.

That is not a failure. Excel is flexible, everyone knows it, and it costs nothing extra. The question is not whether Excel is good or bad, but at what point the plant's needs go past what a set of separate files can reliably hold.

Where Excel works well in a component plant

• Quotations and cost estimates, where one person builds a model and nobody else edits it.
• One-off analysis: a rejection Pareto, a capacity check, a price comparison.
• A small plant with one planner, a few part numbers and customers who rarely ask for records.
• Reports built from data that already lives in a system.

Where do spreadsheets become difficult?

Several people, several copies

Planning, stores and quality each keep their own file. When the planner updates the schedule, the stores sheet still shows last week's requirements. Shared workbooks help, but it is still easy to work on a copy saved yesterday.

Schedules that change every week

Each OEM release means re-entering quantities, re-checking material and re-sequencing machines by hand. The more customers and part numbers, the longer this takes, and the floor works to the old plan until it is done.

Production status is always behind

A spreadsheet only knows what someone typed into it. Counts from the floor arrive at the end of the shift, from a register or a WhatsApp message, so the office is looking at yesterday's position.

Material availability

Whether an order can start depends on stock, allocations to other orders and open purchase orders. Working that out across sheets is slow, so shortages are usually found when the line is already waiting.

Traceability and QC records

An OEM trace needs the supplier lot, the heat number, the operations, the operators and the inspection results for one batch. In spreadsheets those sit in different files, and some may be on paper. SMX Enterprises, a wiring harness maker in Bengaluru supplying OEM customers, kept its traceability in Excel sheets that ran a day or two behind production, and a trace took hours. With lot records made at each operation, the same trace now takes under three minutes.

Rework and audit history

When a batch is reworked, the record should show the original failure, the rework and the re-inspection. An overwritten cell does not show what it said before, or who changed it.

Reporting across departments

Rejection by operation, cost per order and on-time delivery by customer each need data from several sheets. They are built monthly, by hand, and are already out of date when someone reads them.

Spreadsheets and ERP compared, task by task

An ERP is an operational system, not a bigger spreadsheet

The main difference is where the data comes from. A spreadsheet is filled in after the work. A manufacturing ERP with shop-floor recording is filled in as the work happens: stores issues a lot to an order, the operator logs the count and scrap at the station, QC records the measured value before the batch moves on. Reports are read from those records, not compiled.

That is why replacing Excel with an ERP that only covers the office often disappoints. The sheets that cause the most trouble in an automotive plant are the ones about the floor, and an ERP without floor recording leaves them in place.

When should an automotive manufacturer move from Excel to ERP?

There is no size at which a plant must stop using spreadsheets. The useful test is operational: how often the files fail to give a current, trustworthy answer. These are the triggers plants most often point to.

• Several people edit the plan. When planning, stores and quality each keep a copy, someone is always working from an old one.
• More than one line runs at once. One sheet can follow one line; with several running in parallel, nobody has the whole picture.
• BOMs change often. If revisions arrive every month or two, keeping every sheet on the right revision becomes a job in itself.
• Material is hard to track. Stock the sheets show is not on the rack, or a line waits for material that was marked available.
• Production updates arrive late. Counts reach the office at the end of the shift or the next morning, so decisions are made on yesterday's position.
• QC records are kept by hand. Inspection values sit on paper or in a separate workbook that is not linked to the batch.
• A trace takes more than an hour. Answering a customer complaint means opening several files and registers.
• Rework cannot be seen. Nobody can say how many parts were reworked last week, at which operation, or what it cost.
• Customer requirements are growing. A new OEM asks for lot traceability, inspection records or delivery performance that cannot be produced quickly.
• Current WIP is unknown. Finding out how many parts sit at each operation, or at the plating vendor, needs a walk round the floor.

None of these means Excel has failed. They mean the plant has grown past what separate files can reliably hold. Two or three together usually mean the files are costing more time than a system would. The guide to implementing ERP in an automotive plant covers what the move involves.

Keeping what works

Moving to an ERP does not mean giving up Excel. Exports for analysis, quotation models and one-off studies stay in spreadsheets. What moves is the operational record: orders, stock by lot, production, inspection and dispatch. In FleekERP that record is kept on the work order, with inventory and lot traceability and quality control on the same lot, while the books stay in Tally or Zoho.

For how schedules, inspection and lot genealogy run on one record in a component plant, see FleekERP for automotive component makers.