Resin Moulding Production Management Systems: A Buyer’s Guide

When a Thai factory searches for a resin moulding production management system, it quickly finds products offering planning, inventory, production reporting, quality and machine connectivity. Feature screens do not answer the most important buying question: can the system explain a shipped lot after the event? It should connect that shipment to base resin, colourant, additives and permitted regrind; the released recipe version and actual conditions; the machine, mould, insert and cavity; inspection results; and every good, scrap, purge and recovery transaction. It should also trace forward from a suspect input lot to work in progress, finished lots and customers.

This guide covers injection, extrusion, blow, compression and transfer moulding where relevant. It is not an operating manual for one process. It explains how to design the evidence chain, decide what belongs in the package, configuration, add-on or custom-development layer, and translate the boundary into an RFP, acceptance tests and an exit plan. For an injection-specific overview, see our injection-moulding production management article. Here, the focus is procurement architecture across processes.

Start resin moulding production management with evidence, not screens

In many plastics plants, each department holds a valid fragment of the truth. Purchasing and stores know supplier lots. Engineering owns material specifications and standard settings. Machines hold actual parameters. Tooling maintains repair records. Quality stores measurements. Daily reports contain good output and defects. Without shared identifiers and immutable versions, these fragments cannot be reconstructed as one manufacturing history.

Before selecting software, define the evidence required to explain one shipment. At minimum, preserve links among:

the customer requirement and released product/specification revision;
the production order, operation, location and time interval;
input lots for base resin, colourant/masterbatch, additives and permitted regrind;
the machine or line, mould/tool, insert, cavity, die or head as applicable;
the released recipe revision and evidence of the conditions actually used;
quantity events for good product, scrap, purge, recovery, return and work in progress;
the inspection-specification revision, result, disposition and release approval; and
packing, finished-goods and shipment lots plus customer evidence.

The public introduction to ISO 20457:2026 explains that dimensional control of plastics moulded parts is affected by the material, part design and tool layout, and processing conditions. The standard does not prescribe a production database. It does reinforce the practical reason to join material, tooling and conditions to the resulting part rather than storing only the final inspection value.

Resin Moulding Production Management Systems: A Buyer's Guide - figure 1

Do not force injection, extrusion, blow and compression into one generic report

Standardisation should create common evidence principles and relationship keys, not erase process differences.

Injection moulding

Join machine, mould, cavity, material lots, recipe revision, cycle or production interval and inspection. With multi-cavity tooling, a mould ID alone is insufficient. The system must retain cavity status, defects, stops and repairs. EUROMAP 77 addresses data exchange between injection moulding machines and MES, but a compliance statement does not prove that a particular machine exposes every business field or that material genealogy and approvals are implemented. Require sample data from the actual machine population.

Extrusion

Extrusion is continuous. The design must convert time, length, weight, coil or reel and changeover points into controlled lot boundaries. A material or colour change creates a transition interval. The plant must define when the new lot begins, how transition product is segregated, and how mixed states are recorded. EUROMAP 84 provides OPC UA information models for extrusion, while the business rule that creates a customer lot remains the factory’s responsibility.

Blow moulding

Link preform or parison, material, machine, mould, cavity and checks such as leak, appearance and weight. If an intermediate preform is produced elsewhere, record a transformation event from that intermediate lot to the final container. A high-speed reject signal has little evidential value unless the product unit or time window it applies to is unambiguous.

Compression, transfer and other moulding

Connect compound batch, preform, charge, tooling, pressure/heat conditions, curing time and subsequent operations. ISO 20457:2026 publicly lists injection, injection-compression, transfer, compression and rotational moulding among its covered processes for applicable non-porous moulded parts. Applicability to the plant’s specific material and customer requirement still needs technical review.

The shared model can be simple: material is issued, transformed by authorised resources and conditions, inspected, dispositioned and released as a lot. Shot, continuous interval, reel, batch and cavity then become process-specific extensions. This preserves enterprise reporting without discarding shop-floor evidence.

Raw material lot control is more than scanning a barcode

Scanning at receipt and issue is useful, but genealogy breaks unless the system records the state transitions around the scan:

mapping between supplier and internal lots;
receipt, quarantine, inspection, release, conditional use and rejection;
movement through bag, box, silo, dryer, hopper and intermediate container;
weighing and issue of resin, colourant and additives with explicit units;
return of unused material, repacking and relabelling;
creation, grinding, storage, approval and reuse of regrind;
the prior value, new value, reason and approval for inventory corrections.

The GS1 Global Traceability Standard offers a useful pattern through Critical Tracking Events and Key Data Elements, describing the who, what, where, when and why of important events such as receiving, transforming, packing and shipping. It is not a plastics recipe specification. The plant still has to decide which events change genealogy in its own process.

Separate physical genealogy, quantity accounting and claims for regrind

Regrind and recycled content require three separate ledgers.

First, physical genealogy identifies where recovered material came from, how it was segregated, and which output lot received it. Second, material accounting reconciles generation, movement, storage, reuse, disposal and external transfer. Third, a customer or sustainability claim follows a defined chain-of-custody model and may not be identical to physical tracing.

ISO 22095:2020 supplies a generic chain-of-custody framework and warns that having such a system alone does not substantiate a product characteristic or claim. ISO 22095-2:2026 addresses mass balance, including boundaries, attribution rules, conversion factors and communication principles, and ISO identifies plastics as a relevant sector. Consequently, an RFP should not ask only for a “recycled material” flag. It should ask for the adopted model, boundary, accounting period, conversion and attribution rules, duplicate-claim prevention and supporting documents.

Do not silently net material differences

If production reporting captures only good and reject quantities, purge, start-up scrap, samples, transport residue, recoverable material and unrecoverable disposal disappear. Acceptance testing should recalculate inputs and every disposition from events. A remaining difference should stay visible as unexplained until an authorised correction is recorded. The tolerance must come from the factory’s material, weighing method, equipment and product risk; this article asserts no universal percentage.

For broader design principles, see our lot-management system guide. This article concentrates on resin blends, regrind and their connection to moulding resources.

Moulding parameter management is version and deviation control

Saving a table of nominal conditions is not enough. The system must answer which revision was approved, when and by whom; which product, material, mould and machine combination it applied to; what actually ran; and how deviations were authorised.

Do not flatten a recipe into one value sheet

A recipe needs an identifier, revision, lifecycle status, effective and retirement dates, applicability, change reason and maker/checker/approver roles. If machine capability requires local conversion, relate the enterprise recipe to a machine-specific recipe. Version the conversion rules for names, units, precision and ranges.

Do not overwrite setpoint, machine-reported value, observed sensor value and operator entry into one field. They have different sources and times. Specify which source supports acceptance for each parameter. Test what happens when connectivity fails: blank, stale value or manual entry must be explicit, not accidental.

Make deviation a controlled event

Material condition, ambient conditions, tooling state or an approved customer trial may require a temporary change. A useful system records authority, reason, scope, validity, approval and return to standard. It should prevent unauthorised change without pushing legitimate exceptions into hidden notes or private spreadsheets.

Acceptance tests should prove that an unreleased recipe cannot be selected, an expired deviation does not continue, a historical run remains tied to its original revision, and planned and actual values can be exported side by side.

A mould management system belongs in manufacturing history

When mould management is isolated inside maintenance, production and quality lose causality. Keep mould/tool ID, revision, inserts, cavities, die/head where applicable, availability, location, storage condition, use evidence, cleaning, repair, component replacement, inspection/calibration and restrictions.

A repair may preserve the mould ID while changing its state revision. If the replacement time for an insert or cavity is not linked to the production interval, pre- and post-repair trends cannot be separated. A temporarily disabled cavity must also change the active cavity configuration and its output evidence, not just the total counter.

An RFP should test scenarios, not merely ask whether a mould register exists:

validate status and compatibility when assigning a mould to an order;
warn or block overdue, stopped or missing tooling;
record setup start/end, trial shots and mass-production approval;
split actual history across an insert or cavity change;
compare defects and dimensions by mould, cavity and repair revision; and
export the complete tooling relationships outside the vendor UI.

If a specialist maintenance system remains the master, contract the shared ID, status, history link, downtime reason and ownership at the interface.

Quality evidence must retain what the result was judged against

A measurement cannot be reproduced without the inspection-specification revision, method, unit, sampling rule, instrument status and decision logic. Version the quality master with the product specification and bind each result to the revision effective at production time.

ISO 20457:2026 covers geometric and dimensional tolerances and acceptance conditions for plastics moulded parts. Its public explanation discusses shrinkage, warpage and non-uniform cooling and why metal-part tolerance logic cannot simply be copied. The applicable tolerance and measurement method for a real product must still come from design, material, process capability and the customer agreement. Displaying a standard number is not evidence of conformity.

Store measurement, specification revision and decision-rule revision separately. If the specification later changes, retain the decision made under the original rule; where useful, show a separate re-evaluation under the new rule. Quarantine, concession, reinspection, rework, disposal and release should be authorised state transitions. Customer certificates should link source data, generation time, template revision and approver to the shipment lot.

Draw the boundary among package, configuration, add-on and custom development

A package-versus-scratch binary is too coarse. Use four layers.

Package standard

Identity, items, orders, inventory, basic production, basic quality, access and audit are mature cross-industry capabilities. If the factory adopts the standard, document which process changes it accepts and what stays supportable through upgrades.

Configuration and workflow

Statuses, approvals, fields, screens, reports and alerts can often be configured. Configuration is still a deliverable. Require a register, history, deployment and rollback method, backup and test evidence. “No code” must not mean “no specification.”

Controlled add-ons and interfaces

Machine, scale, label, inspection, ERP, warehouse and tooling integration, plus resin-specific blending or continuous-lot logic, belong here. Prefer documented APIs and messages. Specify retry, duplicate, ordering, unit, time, master mismatch and recovery behaviour. ISA-95 and EUROMAP can provide shared vocabulary, but the contract must name implementation scope and responsibility.

Custom development

Reserve custom code for differentiating requirements that cannot be met by standard, configuration or safe extensions. Custom work needs source/build access, dependency records, tests, vulnerability handling, maintenance, IP terms and handover. NIST SSDF provides a common vocabulary that acquirers can use with suppliers; ask for evidence of development, review, release and remediation practices rather than relying on a badge.

Resin Moulding Production Management Systems: A Buyer's Guide - figure 2

For each requirement, compare differentiating value, customer/regulatory risk, change frequency, standard fit, upgrade impact, data ownership, replaceability and acceptance evidence. Departure from the standard creates not only build cost but also future-change and exit obligations. Our production management system comparison for Thai factories provides the wider comparison process.

Turn the RFP from a feature list into scenarios, evidence and responsibility

Terms such as “traceability,” “mould management” or “parameter monitoring” allow incompatible interpretations. Write every major requirement as:

Business situation: who handles what at which process.

Preconditions: valid master revision, material/tool state and role.

Action/event: scan, issue, start, change, inspect, quarantine or release.

Expected outcome: block, warn, record, link, notify or recalculate.

Evidence: screen, API response, event log, audit record and export.

Responsibility: plant, package supplier, machine supplier, SI or inspection supplier.

Exception: outage, damaged label, wrong issue, retry, reversal, correction or night shift.

Instead of “the system shall trace material lots,” write an acceptance-ready statement:

Only released base resin, colourant, additive and approved regrind lots may be issued to the order. The issue event retains lot, container, quantity and unit, equipment/location, order, actor, event time and data source. Reversal or correction must not delete the original event and must retain prior value, new value, reason and approval. Users can trace from shipment to all inputs and forward from an input lot to affected work in progress, finished lots and shipments, then export the relationship in a machine-readable form.

Ask each vendor to classify the answer as standard, configuration, add-on, custom or out of scope, and disclose assumptions, third-party products and licences.

Accept by replaying history, not watching a happy-path demo

Acceptance confirms that critical facts survive without omission, duplication or substitution. Use production-like data and reconstruct genealogy in both directions.

Split one resin lot over two orders and create two packing lots from one order.
Issue base resin, colourant, additive and approved regrind with unit conversion and rounding.
Block an unreleased recipe, then use an approved time-bounded deviation.
Change an insert or cavity state during production and split history correctly.
Disconnect and restore a machine interface; verify gaps, retry, duplicates and order.
Record good, scrap, purge, sample, recoverable and disposed quantities separately.
Revise an inspection specification while historical results remain bound to the prior version.
Quarantine a lot and execute a segregated concession or release with evidence.
Trace a shipment backward and a suspect material lot forward.
Export masters, transactions, attachments, audit and relationship keys and reconstruct them elsewhere.

Resin Moulding Production Management Systems: A Buyer's Guide - figure 3

Attach input data, steps, expected outcomes, evidence files, approver, defect severity and retest conditions to each case. Performance tests should include concurrent use, burst label printing, large genealogy queries, history export and outage recovery. Set thresholds from measured plant loads and operational deadlines, not a generic benchmark.

Contract the deliverables and failure boundaries

The contract should list more than a requirements document:

scenarios, data dictionary, identifiers, units and time rules;
master ownership, approval, transport and rollback;
interface schema, error codes, retry, deduplication and monitoring;
configuration register, add-on design, source/escrow and build method;
tests, evidence, defect register and acceptance record;
role matrix, audit, backup, recovery and security response;
operating procedures, training, language scope and support hours;
retention, deletion, personal-data and cross-border review items;
licence, volume metrics, third-party dependency and end-of-support terms; and
exit export, migration assistance and knowledge transfer.

Define responsibility through failures as well as RACI. If machine values do not arrive, who diagnoses tags, gateway, network, time, message, MES ingestion and master mapping? Which logs are shared? Who authorises temporary operation?

Thailand ETDA publishes the Electronic Transactions Act and related electronic-contract guidance. Projects using electronic approvals and evidence should obtain Thai legal advice on the contract form, signatures, personal data and retention. This guide is not legal advice.

Accept the exit before signing the implementation

“CSV on termination” is not an exit plan. Relationships must survive. Export revisions with items; issue, transformation and return events with material lots; cavity and repair history with moulds; specification revisions and decisions with measurements; relationship keys with attachments; and stable audit identities even for departed employees.

The joint Secure by Demand guidance for OT owners recommends asking about open interoperable standards and migration to reduce lock-in. It is not a private-factory legal mandate, but it is a strong procurement question.

Run a small exit test during the PoC. Export vendor data and let the plant reconstruct one shipment in another tool. If the promise is an API, test limits, paging, deleted data, attachments, audit, cost and post-termination availability. Add keys, service accounts, cloud stores, machine-connection settings, labels, reports, source and dependencies to an exit register.

A staged implementation for Thai plastics plants

Stage 1: inventory current evidence

Select a representative product and trace it back from shipment. Record where Excel, paper, machines, inspection systems, ERP and tooling records hold the facts, where IDs fail to join and where corrections erase history. Include Thai and other operating-language terminology.

Stage 2: design one minimum evidence chain

Limit the pilot to selected products, machines, moulds and materials. Define identifiers, events, versions, states and owners. Select barcode and machine connectivity as means to create that chain accurately.

Stage 3: scenario PoC

Demonstrate material return, recipe deviation, network outage, cavity stop and quarantine/release—not only a normal day. The plant team validates exported evidence, not the vendor narrative.

Stage 4: FAT, SAT and operational acceptance

FAT validates configuration, interfaces, reports and roles in a controlled environment. SAT uses the actual machine, label, network and operators. After go-live, monitor closing, inventory differences, unlinked events, manual corrections and interface gaps, then make final acceptance against a contracted operating-evidence period.

Stage 5: scale by common evidence and process extensions

When moving from injection to extrusion or blow, retain the common material, revision, quality and shipment model and add process-specific lot boundaries and resources. Do not merely clone the first screens.

FAQ: selecting a resin moulding production management system

What makes a resin moulding system different from a generic production system?

It must join blend components, regrind, recipe revisions, mould/cavity, continuous-process boundaries and quality-specification revisions into manufacturing history. Validate that capability with the plant’s scenarios rather than a product label.

Should one system cover only injection moulding?

Not necessarily. A common material/version/quality/shipment model can support injection shots and cavities, extrusion intervals and reels, blow-moulded intermediates and compression batches through process extensions.

What is the minimum for raw material lot control?

Supplier/internal lots, state, movement, weighing/issue, return/repack, regrind, correction history and bidirectional product relationships. A barcode is an input method; event and exception design is the core.

Must every machine parameter be stored?

Define the parameters needed for quality, traceability and diagnosis, along with source, unit, frequency, revision and missing-data behaviour. Keep setpoint, machine response and observed value distinct.

Can mould management remain in a maintenance system?

Yes, if shared IDs connect mould/cavity state, repair revision, location and usage interval to production and quality, and the interface has clear ownership and failure rules.

How should package and custom development be divided?

Use standard capabilities for mature common work, configuration for plant workflow, controlled interfaces/add-ons for equipment and process differences, and custom code only for unmet differentiating needs. Give every layer acceptance and exit evidence.

What RFP wording should be avoided most?

Avoid noun-only requirements such as “has traceability,” “supports mould management” or “monitors parameters.” Each requirement should define the scenario, precondition, event, expected result, exception, evidence, owner and response.

Conclusion: buy explainable manufacturing

A resin moulding production management system should deliver more than screens. It should preserve an evidence chain among released specification, material lots and regrind, recipe revision, machine, mould/cavity, actual production, inspection, scrap/recovery and shipment. Respect process differences, divide the solution among standard, configuration, add-on and custom layers, write scenario-based RFP requirements, replay failures during acceptance and prove that relationship-rich data can leave the platform.

TOMAS TECH can support current-state evidence mapping, solution boundaries, RFP, PoC/FAT/SAT and integration among machines, ERP, quality and tooling. You can contact us even while deciding what evidence the project should preserve, before selecting a product.

Primary sources

The proposed record set, RFP structure and acceptance scenarios are implementation recommendations. They do not mean that any cited standard mandates the exact same fields for every factory.