Injection moulding units can use AI to build custom moulding management software for machine and mould scheduling, changeover recording, tool life in shots, cavity status, cycle time against standard, material and masterbatch consumption, regrind control, rejection analysis by defect, secondary operations and customer schedule adherence. Pentoggle is an AI platform that generates production-ready software from a plain English description, which means a moulding unit can build an application around its own machines, moulds and customers instead of adapting to a system built for a different kind of factory.
Most moulding units in India already run Tally for accounting, some run Busy or Marg, and larger businesses may run SAP Business One. Those systems handle purchase, sales, GST and accounting well. This is not a proposal to replace them. Pentoggle builds the shop-floor application around them, covering the workflows they were never designed for.
A moulding unit earns differently from a machine shop. A machine shop sells time and skill against a drawing. A moulder sells a repeating part at a rate fixed for the year, so the price is settled before the work starts and cannot be improved. Everything after that is cost. The margin is made in cycle time held to standard, material consumed to shot weight, rejection kept low and machines producing rather than being changed over.
Key takeaways
- Moulding software is built around the machine and the mould together, because a mould that fits three machines and a machine that runs forty moulds is a scheduling problem no order list can express.
- Changeover time is the largest recoverable loss in most units, and it is rarely recorded as a number.
- The mould is often the customer's asset sitting on your floor, so its shot count, maintenance history and cavity status are your responsibility to track.
- Material consumption can be checked against arithmetic, because shot weight multiplied by shots is a theoretical figure that actual issue should be close to.
- The number that runs a moulding unit is OEE with availability broken out, because moulders lose far more to stopped machines than to slow ones.
Why moulding units are badly served by existing software
Tally records that you bought twelve tonnes of polypropylene and sold a hundred and forty thousand parts. It does not know that machine four ran nine hours yesterday and was being changed over for three, that the mould for a part is due for maintenance in eleven thousand shots, or that one cavity has been blocked since March and every shot from that mould has been producing three parts instead of four.
Packaged manufacturing ERP handles the order and the dispatch and struggles with the middle. Its planning logic works on items and quantities, while a moulder plans on the pairing of mould to machine, tonnage compatibility and how many changeovers a sequence will cost. Two orders that look identical in an ERP can differ by six hours of production depending on which mould is already in the machine.
Machine monitoring systems solve the data capture problem by reading the machine directly, and they are excellent at it. They are also priced for plants with many machines, and they tell you about the machine rather than about the mould, the material or the customer schedule.
Most units are running some combination of the first two columns below.
What moulding units use today, and what they can build instead
| Register and Excel | Packaged manufacturing ERP | Application built with Pentoggle | |
|---|---|---|---|
| Machine and mould scheduling | Planned in a supervisor's head | Order list without mould logic | Mould to machine mapping, tonnage and sequence aware |
| Changeover | Not recorded | Rarely captured as a distinct event | Start and stop recorded, reported per mould and per machine |
| Tool life | Shot count estimated, or not kept | Asset record without shot counting | Shots since last maintenance, alerts before the interval |
| Cavity status | Known to the toolroom only | Not modelled at all | Cavities blocked and active, output adjusted accordingly |
| Cycle time | Standard on a sheet, actual unknown | Standard time in the routing | Standard against actual, per shift and per mould |
| Material and regrind | Reconciled at stock take | Consumption booked at standard | Theoretical against actual, regrind percentage per job |
| Rejection | Counted, rarely classified | Scrap quantity | By defect type, machine, mould and shift |
What a moulding unit can build
Each of these can be built separately or combined. Most units start with the production log and changeover recording.
Mould register
Every mould with its owner, cavities, tonnage requirement, compatible machines, current location, shot count and maintenance history.
Machine and mould schedule
What is running on each machine now, what is planned next, and which changeovers that sequence implies.
Shift production log
Shots produced, parts accepted, parts rejected by defect, downtime with reason, and cycle time against standard, entered at the machine.
Changeover record
Time from last good part on the outgoing mould to first good part on the incoming one, with who did it and what held it up.
Tool life and mould maintenance
Shots since last service against the interval, with an alert before the mould is due, and a record of what the toolroom did.
Material and regrind reconciliation
Virgin material, masterbatch and regrind issued against theoretical consumption from shot weight, with regrind percentage tracked against what the customer has approved.
Rejection analysis
Defects classified as short shot, flash, sink, black spot, warpage or dimensional, with the machine, mould, shift and material lot attached.
Secondary operations
Assembly, printing, ultrasonic welding, deflashing and packing tracked after moulding, since the part is not saleable until these are done.
Customer schedule tracking
Weekly or monthly schedules against dispatch, with returnable crates and bins tracked back from the customer.
Changeover is the capacity you already own
A unit running twenty moulds across eight machines changes over constantly. Each change stops a machine while the mould is pulled, the next one craned in, clamped, connected for water and hydraulics, heated, and set until the first acceptable part comes out. The supervisor knows it takes about ninety minutes. Almost nobody knows what it actually took last Tuesday.
The reason this matters is arithmetic rather than theory. Thirty minutes saved on a changeover done four hundred times a year is two hundred hours, which is roughly a month of single-shift production on one machine, obtained without buying anything. That is why moulders who measure changeover tend to find capacity before they find a supplier for a ninth machine.
Recording it needs two entries, last good part out and first good part in, and a reason field for whatever held it up. Within a few weeks the pattern is visible, and it is usually the same three causes: the mould was not preheated, the water fittings did not match, or the setting sheet from the last run was not kept. All three are fixable, and none of them are fixable while the number is a feeling.
The mould is your customer's asset, sitting on your floor
In many Indian moulding businesses the tool belongs to the customer. They paid for it, it lives with you, and you are expected to maintain it, report on it and return it if the business moves. That is a custody relationship, and it is closer to job work than to owning your own equipment.
Three things follow. The shot count matters, because maintenance intervals are defined in shots and a mould serviced late damages a customer's asset. Cavity status matters, because a four cavity mould running with one blocked is producing at seventy five percent while your costing still assumes four, and that silently reprices the job. Location matters, because a mould can be in a machine, in the store, at the toolroom or at another vendor, and a customer asking where their tool is expects an answer in minutes.
A mould register with owner, shot count, cavity status, maintenance history and location turns all of that into a screen. It also makes a difficult conversation easier, since a customer told that their tool needs refurbishment responds better to a shot history than to an opinion.
Material can be checked with arithmetic
Moulding is one of the few manufacturing processes where theoretical consumption is genuinely computable. Shot weight multiplied by shots gives the material that should have been used, including runners where they are not automatically reground. Compare that to what was actually issued from stores, and the difference is real information.
A persistent gap points somewhere specific. It may be shot weight recorded from the drawing rather than weighed. It may be purging between colour changes that nobody counts. It may be regrind being used above the approved percentage, which is a quality exposure rather than a costing one, since many customers specify a maximum and some specify none. Or it may be material leaving the premises.
None of that is visible in a monthly stock reconciliation, where everything nets off into one variance figure. Running the comparison per job, per shift, makes the cause findable while anyone still remembers the shift.
Why building this is now practical
A unit with eight machines has never been able to justify custom software. A development team, a specification document and a six month build were never going to be recovered on parts priced by the piece at rates agreed annually.
That has changed. With Pentoggle you describe how your unit runs, including your machines and their tonnages, your moulds and which machines they fit, your customers and their schedules, and get a working application. When a customer sends a new tool, or you add a machine, or you start tracking regrind against an approved limit, you describe the change and the application updates. Most units start with the shift production log and changeover recording, because those two produce the data every other decision depends on.
Why moulding units choose Pentoggle
Built around moulds and machines together
Tonnage compatibility, cavity counts and changeover sequence, which generic order-based systems do not model.
Works alongside Tally
Pentoggle handles the floor, the moulds and the production data. Your accounting stays where your CA already works.
Built for Indian documentation
GST invoicing with HSN codes, delivery challans and e-way bill workflows.
Usable at the machine
Shot counts, downtime reasons and changeover times entered on a phone or tablet by the operator.
Changes in days
A new customer schedule format does not become a three month project.
The one number that runs a moulding unit
OEE, with availability broken out separately from performance and quality.
OEE reported as a single percentage is close to useless for a moulder, because the three components behave differently and only one of them is usually the problem. Performance is largely fixed by the mould and the material, since the cycle is what the cycle is. Quality is visible and gets attention because rejected parts are physically in front of you. Availability is where the losses hide, and it is the only one nobody sees, because a machine standing idle during a changeover looks like normal work rather than lost production.
Track availability per machine per shift with the downtime reason attached. In most units the biggest single line in that report is changeover, followed by material or mould waiting, and both are recoverable without capital expenditure.
Ready to build moulding software?
Every extra minute of changeover is invisible until you multiply it by four hundred mould changes a year.