How to implement ERP in a plastics and injection molding company

ERP projects in moulding plants rarely stall because of the software. They stall because cycle times and cavities were never written down, the resin stock was never counted by lot, or the night shift was never trained. The approach below keeps the scope to a few machines at a time and the training at the machine itself.

Before you start: decide what the system must do first

Write down the questions the plant cannot answer quickly today. For most moulders the list is short: what each machine made against its target last shift, how long mould changes really take, which resin and masterbatch lots went into a batch, scrap by cause and mould, and where parts sent to vendors are. Those define the first scope. The rest can follow.

• Name an owner from the plant, usually the production manager or plant head, not IT alone.
• Choose the first group of machines: real volume, a willing shift supervisor, and parts customers ask about.
• Agree what will stop when they go live, such as the shift register for those machines or the loading sheet.
• Make sure the night shift is in the plan from the start, not added later.

What data do you need to prepare?

Cycle times do not need to be perfect on day one. Use the figure the mould was approved at, or a recent observed one. The counts logged at the machine will show the real figure within a few weeks.

The stages of an implementation

1. Configure the plant as it runs

Machines, shifts, parts, moulds, BOMs, routings with mould changes, reason codes and inspection plans are set up in the plant's own words. Regrind is set up as its own item. Opening resin and masterbatch stock is loaded by lot, and the accounting sync is connected. By the end of this stage, a test job should run from material issue to dispatch on screen.

2. Run the first machines on real jobs

Operators, setters, supervisors and QC on the first machines are trained at the machine, a short session each, on every shift, and record real jobs while the rest of the plant carries on as before. Gaps show quickly: a mould with the wrong cavity count, a missing downtime reason, a secondary operation not on the routing. Fix them the same day.

3. Switch the first machines over

The first machines now run on the system alone, and their register stops. Planning, material and cost read what is recorded at the machine.

4. Extend group by group

The remaining machines, the secondary operations and the vendors follow the same pattern. Each group goes faster than the last, because the masters and the training approach are already proven.

How long does an ERP implementation take in a moulding plant?

That turns on how much is in scope, how clean the mould and resin data is, and which system you choose. A broad enterprise ERP covering finance, purchasing and several plants is a much larger project than putting production, inventory and quality live on one group of machines. 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 and cycle times that need rework first, will take longer.

Common ERP implementation mistakes in plastics manufacturing

1. Configuring software before understanding the process

Setting up screens before anyone has stood at the machines gives a system that fits a template. Walk one part through first: where resin is issued, how regrind is handled, who approves first-off, what goes to vendors, how the night shift records. Configure to that, then run it as set up for a few weeks before asking for changes.

2. Poor master-data preparation

Wrong cavity counts, cycle times nobody agrees on, BOMs without the runner weight, opening stock without lots: each one breaks the first targets, traces and costs. Clean the masters for the parts and moulds you start with. Do not try to load every past transaction either. Open orders, current stock by lot and active masters are usually enough, and history can stay where it is for reference.

3. Ignoring shop-floor users

Operators and setters make most of the records, yet they are often trained last, in a meeting room, on the day shift only. Train them at the machine on real jobs, on every shift, and keep their entries to what they need: counter reading, scrap by cause, downtime with a reason, mould change time. FleekERP's shop floor apps run on ordinary Android phones kept at the machine. Show supervisors their machines against target from the first day, so the entries are used. If shift counts reach the office today as WhatsApp photos of the register, the piece on why WhatsApp ends up running the production floor is worth reading before training starts.

4. Trying to digitise everything at once

Every machine, the stores, quality, secondary operations, vendors and costing on the same day spreads the team too thin to fix problems as they show. A few machines fully live are worth more than the whole floor half set up.

5. Unclear BOM and routing ownership

If nobody owns the BOM and the routing, they drift: the customer approves a new grade, the BOM still shows the old one, a mould is modified and the cavity count on record is wrong. Name an owner for each, often production or engineering for the BOM and production or the tool room for moulds and cycle times, and agree how a change is released.

6. No pilot, or a pilot with no end

Going live on every machine without a pilot means every gap appears everywhere at once. A few pilot machines bring them out while they are still easy to fix. Set the date its register stops, though. A pilot that runs alongside the old register for months becomes a second copy nobody trusts.

7. Measuring software usage instead of operational outcomes

Logins and entry counts show whether people use the system, not whether the plant runs better. Track whether machines, moulds and resin are better controlled than before.

After go-live: what to measure

• Output against target rate per machine and shift, and how quickly a slow machine is noticed.
• Actual mould change time against planned, by mould.
• Scrap by cause and mould, reviewed weekly, and whether the top causes are falling.
• The time taken to trace a complaint back to its resin and masterbatch lots.
• Resin and masterbatch stock in stores compared with the system, by lot, at month end.
• Short returns from vendors caught on the order rather than at packing.

In the first weeks it is still worth watching how much of the output is recorded at the machine during the shift, as an early sign that the outcomes will follow. The guide to OEE monitoring covers how availability, performance and quality are worked out from these records.

For how the full flow runs once the plant is live, see FleekERP for plastics and moulding plants.