In this guide 6 sections
A rubber moulding shop should expect software that follows a compound lot from the mixer to the cured part. It keeps mould history, press cure records and reject reasons against each work order, and prices quotes from the same figures. General ERP packages usually miss the cure and mould detail.
Compound lots come before everything else
Every part you ship began as a mixed batch. That batch carries a compound code, a mixing date, a rheometer result and a shelf life, and software should hold all four against one lot number.
A stale or scorchy batch shows up later as blisters at the press, long after anyone remembers which drop of the internal mixer it came from. Operators should book the lot to the press when they load the preform.
Skip that step. Nothing downstream can be trusted. Ask each vendor to show on screen how a lot travels from the mixer log to the press sheet.
- Compound code and the customer specification it meets
- Mixing date, mixer and shift
- Rheometer or Mooney result with a pass or fail
- Expiry date for each lot
- Quantity issued to each press and balance returned
Mould history should live with the mould
A mould has a life of its own: it is built, cleaned, repaired, coated and re-cut, and the cavity count or shot weight can drift along the way. Most shops keep this in a ledger beside the tool store, where nobody reads it before a run.
Software should show that history the moment a work order is raised. How many cycles since the last clean? Is a cavity blocked off? Which press suits this tool best? Short answers save a bad first hour.
Ownership matters too. A customer-owned mould needs a different record from your own, including where it is stored, who signs for repairs and who pays when a cavity must be re-cut.
- Cycle count since the last cleaning
- Repair and re-cut log with dates
- Blocked or damaged cavities
- Owner of the tool, yours or the customer’s
- Approved presses and platen sizes
Press cure records and reject reasons
Cure time, platen temperature and pressure decide whether a part is sound, so these settings belong on the work order with the actual values the operator ran. A setpoint copied from last year’s sheet is not a record.
Rejects need the same care. Scrap is not one thing, because flash, short shots, blisters, backrinding and tears have different causes, and a single scrap count hides every one of them from the supervisor.
Pick a short code list. Make the operator choose one at the bench. Over a month the codes show which mould, cavity or lot keeps failing, and that is where the fix begins.
- Platen temperature, pressure and cure time as run
- Operator and shift for each batch
- Reject code per defect, with quantity
- Post-cure or deflashing step completed
Quotes should use the numbers production records
A quote needs compound weight, cavity count, cure time, trimming and inspection, while the shop floor records the same figures later. When they sit in separate files, the estimate and the real cost drift apart without anyone noticing.
Good software lets you set what a job was quoted at beside what it consumed, so press hours and scrap show the gap quickly. Repeat orders are then priced from fact, not memory. Margin stops leaking quietly.
Where a general ERP usually falls short
A general ERP handles stock, purchase orders, invoices and accounts well, but it rarely understands a mould, a cavity or a cure. Those fields end up in free text, or in a side spreadsheet that only one person updates.
Bring three real jobs to every demo and ask the vendor to trace a lot, open a mould history and cost a quote on screen. Whatever cannot be shown live, you will be doing in Excel a year from now.
Write your three jobs down this week. Send them to each vendor ahead of the call.
Moulding shop software demo sheet
A single demo sheet in four columns: the need, what the vendor showed, whether the demo ran on screen or on slides, and the gap. Rows cover compound lot booking, mould history, cure record, reject codes and quote against actual. Fill it in during every demo, so vendors are compared on identical rows.
Open a blank worksheet to printQuestions owners ask
Does a rubber moulding shop need its own software or can a general ERP work?
A general ERP can work if it allows custom fields for moulds, cavities and cure settings, so test that with a real job. If those details land in free text, nobody can search them later.
How many reject codes should we use?
Start with eight to twelve codes. Flash, short shot, blister, backrinding, tear, porosity, contamination and dimension cover most plants. Add more only when the data asks for them.
Who should enter press data, operators or supervisors?
Operators, at the press, on a tablet or a fixed screen. A supervisor filling sheets at shift end produces a poorer record and burns time chasing clipboards across the shop floor.
Can old mould records be loaded into new software?
Usually yes, from a spreadsheet. Load the active tools first with cavity count and owner, then add the repair history as moulds come back for service.