How to implement ERP in an industrial machinery manufacturing company

ERP projects at machine builders seldom fail on the software. They stall because the BOMs are not ready, because half-built machines make the switch confusing, or because the fitters were never shown why they should record anything. This guide sets out an approach that keeps the first stage small and close enough to the assembly bay to be used.

Before you start: decide what the system must answer on day one

Write down the questions your customers and your own management ask most often about builds. For most machine builders the list is short: where each build stands, what is short and when it will arrive, what is at vendors, and what the machine has cost so far. Those define the first scope.

• Name an owner from operations, usually the plant head or production manager, not IT alone.
• Choose the first product family: one with steady orders and a BOM that engineering is confident in.
• Decide which builds go on the system. New builds start on it; machines close to dispatch usually finish on the current method.
• Agree what stops when the first builds go live, such as the progress sheet or the per-build purchase tracker.

What data do you need to prepare?

Operation times do not need to be exact at the start. A rough figure is enough, and the times recorded on the first few builds will show the real ones.

The stages of an implementation

1. Configure the plant as it runs

Work centres, shifts, items, BOMs, routings, vendor steps, reason codes and check plans are set up in the plant's own terms. Opening stock is loaded by lot and the accounting sync is connected. By the end of this stage, a test build should run from release through sub-assemblies, a vendor step and assembly to dispatch on the screens.

2. Run the first builds on real orders

New builds of the first product family are released on the system. Operators, fitters, supervisors and QC working on them are trained at their stations, one short session each, and record real work while other builds carry on as before. Gaps show quickly: a sub-assembly that should be its own work order, a missing vendor step, a check that sits at the wrong stage. Fix them as they appear.

3. Switch the first product family over

Builds of that family now run on the system alone. The progress sheet and purchase tracker for them stop, and planning, material and cost read what the floor records.

4. Extend family by family

Other product families and departments follow the same pattern. Each goes faster, because the BOM structure, the routings and the training approach are already proven.

How long does a machinery ERP implementation take?

It depends on the scope, the state of the BOMs and the system chosen. A broad enterprise ERP with project accounting across several plants is a much larger undertaking than putting builds, stock and quality live for one product family. FleekERP's implementation plan is built to put the first production line live in 18 days. A plant migrating years of history from another ERP, or with BOMs that need restructuring first, will take longer.

Common ERP implementation mistakes in machinery manufacturing

1. Configuring software before understanding the process

Screens set up before anyone has followed a build through the plant will match a template, not the way machines are made. Walk one recent machine first: where material was issued, which sub-assemblies were made in-house, what went to vendors, where checks were done. Configure to that, and run it for a few builds before asking for changes.

2. Poor master-data preparation

A BOM with missing levels, bought-out items with no lead time, opening stock with no lots: each one makes the first shortage list and the first build cost wrong, and the floor stops trusting the system. Clean the masters for the first product family before go-live. Do not try to migrate every old build either. Current stock, open orders and active BOMs are enough to start, and history can stay where it is.

3. Ignoring shop-floor users

Fitters, operators and QC make most of the records, and are often the last to be trained. Train them at their station on the build they are working on, and keep their entries short: operation done, downtime with a reason, check result. FleekERP takes these entries through shop floor apps on ordinary Android phones, so a fitter logs a step from the bay. Show supervisors their builds' progress from the first day, so the entries are used. The article on why WhatsApp ends up running the production floor covers the habits that need to change.

4. Trying to digitise everything at once

Every product family, every department and every build in progress on the same day spreads the team too thin to fix problems as they appear. One product family running properly is worth more than the whole plant half set up.

5. Unclear BOM and routing ownership

In a machinery plant BOMs change during builds, and without an owner they drift: design revises a part, purchase buys the old one, and the shop machines a third version. Name an owner for the BOM, usually engineering, and for the routing, usually production, and agree how a change to a released build is approved and passed on. For a builder this matters more than almost anything else in the project.

6. No pilot, or a pilot with no end

Going live on every build at once means every gap appears everywhere. A pilot on one product family finds them on a small scale. But set the date when the old tracker stops for that family: a pilot that runs beside the spreadsheet for months becomes a second record nobody trusts.

7. Measuring software usage instead of operational outcomes

Logins and entry counts show whether people are using the system, not whether builds run better. Track whether machines ship on the promised date and close near the quoted cost, which is what the project was for.

After go-live: what to measure

• Builds delivered on the promised date.
• Shortages found at assembly, compared with shortages flagged before the build reached the bay.
• Late vendor returns seen on the build before they held up work.
• Rework by stage and reason, and whether the same fault repeats on the next machine.
• The gap between quoted cost and actual cost per build, and how early it is seen.

The share of build progress recorded at the station is worth watching in the first weeks, as an early sign that the outcomes will follow.

For how the full flow runs once the plant is live, see FleekERP for industrial equipment makers.