Injection Moulding Machine Monitoring and OEE

Start with the relationship between shots and parts

A shot counter establishes how many observed cycles occurred. To turn it into a production quantity, the system also needs the number of relevant parts per cycle and the conditions under which that relationship holds. Trial shots, incomplete cycles, disabled cavities and family moulds can change the interpretation. The first task is to define which event is counted and how that event becomes a quantity for the intended production report.

Ask the production and process teams to select representative operating conditions. One may be stable production using a familiar mould; another may involve a cavity change, trial run or product transition. The quality team identifies how accepted and rejected quantities are recorded. Finance or planning may need a separate output view by order. These perspectives establish the data model before sensors or dashboards are specified.

Survey the machine interface and the working procedure

Send machine manufacturer, controller model and version, available outputs, mould examples and an existing shift record. The survey establishes what can be obtained through an approved interface and what needs an external observation or operator entry. A cycle contact may support reliable event timing while providing no mould identity. A richer controller interface may expose additional fields, but access, configuration and licensing must be checked on the actual machine.

EUROMAP's published description of EUROMAP 77 concerns data exchange between injection moulding machines and manufacturing execution systems. It is a useful interface reference when reviewing equipment documentation. Its existence does not establish that a particular installed controller has the required option or field available. We scope the supported connection and its point list with the machine owner, then verify the interpretation through representative operating events.

Keep configuration history with the production record

The system needs to know when a mould, product, active-cavity count or approved cycle reference changes. Store the effective time of that change with the job history. An operator may enter a change at the machine, or it may come from an existing job or production system. Either way, define who owns the value and how a correction is reviewed. Updating the current configuration should not silently rewrite an earlier shift.

An illustrative run shows why this matters. Sixty cycles with eight producing cavities yield an expected 480 parts. After a configuration change, forty cycles with six producing cavities yield an expected 240 parts. The combined expected quantity is 720. Applying eight cavities to all 100 cycles would instead report 800. This example is hypothetical and assumes one part per active cavity; the acceptance test must verify the actual mould and output arrangement.

Preserve the distinction between actual configuration and capacity reference

Recording six active cavities is necessary to reconstruct actual output. It does not automatically justify lowering the capacity benchmark from an approved eight-cavity arrangement. If a cavity was disabled because of a recurring tooling problem, changing the reference without explanation could hide the resulting capacity loss. Keep the effective production configuration separate from the reference against which the plant evaluates performance.

The process owner should approve reference changes and state why they were made. A deliberate product or mould revision may warrant a new benchmark; a temporary fault may warrant a visible loss against the existing benchmark. The report can show both the observed configuration and the approved reference. This supports a tooling or maintenance decision while keeping the production quantity internally consistent.

Match cycle time to the exact reporting unit

Cycle time may refer to a machine shot, while the order report is expressed in individual parts. Establish the conversion and retain its version. If a performance calculation uses seconds per part, the numerator must use the corresponding part count. For a family mould that makes different components in one shot, define whether the output is a set, an individual component or a separate quantity for each part number.

Actual cycle-time trends should be reviewed with mould and product context. A shift that includes a different mould or a lengthy trial should not be compared against stable production without that distinction. The OEE production environment guide introduces these differences across manufacturing; this service turns the moulding-specific definitions into a scoped collection and reporting project.

Record trials, changeovers and the start of accepted production

Agree the milestones that describe a mould change: the previous production run ending, setup work, first trial cycle, required checks and release for the new job. Some events may be available automatically; others need a brief operator or supervisor input. The classification should reflect the plant's agreed production-time policy. A changeover within planned production remains visible according to that policy rather than disappearing because someone changed the schedule afterwards.

Trial output also needs a clear disposition. It may consume cycles and material while being unavailable for customer delivery. Retain that context when deriving good count and performance. A practical report should let the supervisor explain why the machine was active but accepted output was low, using the actual milestones and quality decisions. The instrumented record supports this conversation without assigning a cause merely from the duration of a stop.

Link quality information without assuming every cycle is good

Quality records may arrive from an operator count, a batch disposition or an existing inspection system. Define the part or batch identifier, the unit used and the treatment of results arriving after shift end. Until the agreed result is available, an affected quantity can be shown as pending. When a decision changes the good count, preserve the original report version or an auditable adjustment so the difference can be explained.

If 720 parts were produced in the illustrative run and 20 were rejected, the first-pass good count would be 700 under that simplified assumption. An unrecorded quality decision cannot be replaced with a default zero-reject value. Separately agreed quality interfaces supply disposition data; machine-vision inspection projects can be discussed through the group's specialist addaScan service. The monitoring scope remains centred on the production records supplied to it.

Design collection and recovery around the actual cycle events

A local counter or approved controller source must capture the required events before the communications layer can transport them. The survey defines the relevant event timing and retained data. LoRaWAN and 4G may form part of the site monitoring architecture, with buffering and reporting intervals selected for the application. A periodic wireless report can carry accumulated counts when configured appropriately; it should not be assumed to represent every individual cycle timestamp.

The acceptance plan specifies what happens when the data connection is interrupted, a device restarts or a job crosses a shift boundary. Recovered records need their original timing and configuration context. A fresh cumulative counter after restart requires an explicit reset event. The operator should be able to distinguish a genuine period without production from a period whose data have not yet arrived.

Accept two representative conditions before extending the hall

Numerical tolerances, observation duration and acceptance authority belong in the project agreement. The OEE pilot acceptance worksheet provides a starting format; add mould and cavity fields for this application. A failed test becomes a named defect with retest evidence. A wider rollout should use the approved mapping and field procedures, while still checking the interfaces and handling conditions of each additional machine.

Define the cost and ownership of each part of the project

Initial scope includes interface assessment, required sensing or edge equipment, installation, configuration, operator inputs, report design and commissioning. Existing systems may already own job and mould data; connecting those systems requires a defined export or interface and an owner who can approve the mapping. A quote should state which production and quality fields are included and how the team will enter anything not supplied automatically.

Ongoing responsibilities include keeping mould references current, reviewing unresolved quality records, maintaining instruments and approving configuration changes after controller or tooling work. Separate platform and connectivity charges from support, site service and integration maintenance. Choose the first machines for their representative conditions and available reference data. The parent OEE management service explains how the accepted records can support a wider production view.

For adjacent production processes and plant responsibilities, use the manufacturing overview to identify the other records that need to connect with the moulding report.

Frequently asked questions

Technical references

EUROMAP 77: injection moulding machine to MES interface describes the interface's intended role. Vorne's OEE calculation guide explains the factor relationships. Sources checked 5 November 2026; interface availability, production conventions and acceptance values are confirmed for the actual installation.