Excel vs ERP for machine shops and fabrication units: where spreadsheets stop coping

Most job shops run on a job register in Excel, a whiteboard by the machines and a phone that never stops. It works better than outsiders expect, because the people running it know every job personally. The trouble starts when the shop grows past what those people can keep in their heads.

Excel is not the problem. It is flexible, it is free, and every estimator in the country can build a costing sheet in it. The question is when the shop's day-to-day running needs more than a set of separate files can give.

Where Excel works well in a job shop

• Estimating and quoting, where one person builds the cost from cycle times, material and vendor rates.
• A short job list in a small shop, with one planner and a few machines.
• One-off analysis: which customers bring the most rework, which machine is busiest.
• Reports and charts built from data exported from another system.

Where do spreadsheets become difficult?

Machine load in a sheet

Loading jobs onto machines by hours is possible in Excel, but every change ripples. A rush job, a breakdown or a long setup means re-working the sheet by hand, so it is usually done once a week and is wrong by Wednesday.

Job status lives on the whiteboard

The sheet knows a job was released. Where it is now, at which operation, and how many parts are good, is on the whiteboard or with the supervisor. When a customer calls, someone walks the floor.

Drawing revisions

A column for the revision number does not stop an old print being used at the machine. When revisions arrive often, keeping the job sheet, the drawing folder and the floor in step becomes a job in itself.

Heat numbers and offcuts

A bar is cut for two jobs, and the offcut goes back to the rack. Recording which heat went to which job, and which heat the offcut belongs to, is easy to skip in a sheet and hard to reconstruct later.

Parts at vendors

Challans are written in a book or a separate sheet. Matching what came back against what went out, across hardening, plating and grinding vendors, is done at month end when the bills arrive. Short returns are found when the next operation runs out of parts.

Job cost

A costing sheet needs actual machine hours, setup time, scrap and the vendor charge for each job. In most shops those numbers are scattered or never recorded, so the job cost is the quotation with the material price updated.

Several people, several versions

Sales, the planner, stores and QC each keep their own file or tab. Someone is always working from a copy saved yesterday, and an overwritten cell does not say who changed it or what it said before.

Spreadsheets and ERP compared, task by task

An ERP is an operational system, not a bigger spreadsheet

The difference is when the record is made. A spreadsheet is filled in after the work, by someone in the office. A manufacturing ERP with floor recording is filled in during the work: stores issues the heat to the job, the operator logs the setup and the count at the machine, QC records the first-off value before the batch runs. The load board, the job status and the job cost are read from those entries.

That is why an ERP that covers only purchase, stock and billing often disappoints a job shop. The spreadsheets that cause the most trouble are the ones about the floor, and those stay in place.

When should a machine shop move from Excel to ERP?

Headcount is a poor guide. The better test is how often the files fail to give a current answer. These are the signs shops most often point to.

• More than one person updates the job list, and the copies no longer agree.
• Several machines run several jobs at once, and nobody has the full load picture without asking.
• Customers revise drawings often, and parts have been made to an old revision.
• Bar and plate are hard to track: a job waits for material the sheet said was on the rack.
• Job progress reaches the office at the end of the shift or the next morning.
• First-off and inspection results are on paper, and the customer's report is typed up from them.
• A customer asks which heat a part came from, and it takes hours to find out.
• Rework is done but not recorded, so nobody knows what it costs.
• Customers start asking for inspection reports, material traceability or delivery performance.
• Nobody can say how many parts are at each vendor right now, or since when.

Any one of these can be managed. Three or four together usually mean the files take more time than a system would. The guide to implementing ERP in a fabrication or machining shop covers what the move involves.

Keeping what works

Estimating sheets, one-off analysis and the owner's favourite reports can stay in Excel, built from exports. What moves into the system is the running record: jobs, routings, material by heat, floor entries, vendor challans, inspection and dispatch. In FleekERP that record sits on the work order, with shop floor apps for the entries at the machine and production planning for the load board, while the books stay in Tally or Zoho.

For how a job runs on one record in FleekERP, see FleekERP for engineering and machining units.