Moulding machines already generate the data. The problem is that it stays inside the machine while production counting still runs on paper and spreadsheets. Pulling the machine signal straight through to results, mould history and defect causes is where an injection plant starts.
The shot count on the machine does not match the quantity in the logbook.
02
Mould history lives in memory
How many shots a mould has run and when it was last repaired sits in a supervisor's notebook.
03
You cannot reconstruct the conditions behind a defect
Mould temperature, holding pressure and cycle time vary slightly between operators, and none of it is recorded.
Where injection molding plants get stuck
Problems that come up repeatedly in implementation discussions.
Field issue
Shot counts and reported output disagree
The shot count on the machine does not match the quantity in the logbook. Handover gaps, trial shots and scrap shots get mixed in. When the counting rule lives in someone's head, reconciling at month-end becomes routine.
Field issue
Mould history lives in memory
How many shots a mould has run and when it was last repaired sits in a supervisor's notebook. When that person changes, the state of every mould has to be rediscovered — and the maintenance window gets missed.
Field issue
You cannot reconstruct the conditions behind a defect
Mould temperature, holding pressure and cycle time vary slightly between operators, and none of it is recorded. Without the conditions for a defective lot you cannot separate a process cause from a material cause.
Field issue
Machines come from different vendors
Even within one plant, moulding machines differ in make and vintage, so protocols and data formats differ. Building per machine does not scale to maintain.
What gets connected
Machine signals and floor entry combined into history.
What is connected
How it is collected
What it produces
Shot signal
Machine dry contact or PLC register
Live production count, cycle time
Mould temperature
Temperature controller, PLC or sensor
Condition-drift alerting, per-lot condition history
Injection and holding pressure
Machine PLC
Backtracking conditions for a defective lot
Alarm and stop codes
Machine PLC or dry contact
Downtime classification, per-machine stop history
Mould identity
Barcode or work order linkage
Cumulative shots per mould, maintenance timing
Build sequence
Nothing is converted all at once. High-impact areas are built and verified first.
STEP 01
Survey machine communications
Establish vendor, vintage and communication capability (PLC protocol, dry-contact availability) per machine. This is where it is decided which machines connect directly and which need a gateway.
STEP 02
Collect and normalise signals
Take the differing signals into an industrial gateway and Resource Lake and bring them to one shape. From then on upstream systems do not need to know the machines differ.
STEP 03
Automate production counting
Bind the shot signal to the work order so quantities accumulate on their own. Decide here how trial and scrap shots are treated.
STEP 04
Attach mould and condition history
Store mould identity and moulding conditions against the lot, so a defect can be traced back to the conditions that produced it.
Applied solutions
Scope is composed after reviewing equipment and workflow.
Questions that come up on injection molding floors.
Can we get data from older moulding machines?
Usually yes. Even machines without a communication port normally expose something — a shot contact or a temperature controller signal — that a gateway can read. Conditions vary per machine, so the communication survey comes first and the collection scope follows from it.
We have machines from several vendors. Do we build for each?
No. The differences are absorbed in the collection layer. Resource Lake converts each format into a standard shape, so MES and dashboards never distinguish vendors.
Can we start with mould shot counting alone?
Yes, and many do. One shot signal is enough to give cumulative shots per mould and a maintenance trigger. Condition history and quality linkage come after.
What if production results disagree with our ERP?
Align the counting rule first. Trial shots, scrap and rework are usually the source of the gap. Once the rule is fixed, passing MES results to ERP removes the double entry.
What can we do with cycle time data?
Compare standard against actual cycle per machine and mould to locate where time is lost, and check whether lengthening cycles coincide with mould condition or setting changes.
Sources and standards
Terms and procedures on this page follow the public standards and official sources below. Figures are as of each source's publication date.