Pair the identified non-LSR dosing or blending system with its material-component map, IMM cyclic or batch relationship, physical feed point, selected OPC 40082-4 scope, responsibility split and configured acceptance evidence.
Release each material component and each machine-to-doser relationship as a controlled evidence row. Keep every unconfirmed supplier implementation, compatible option, recipe and operating value open until the responsible parties provide project records.
Build the fixed dosing-interface briefEach row assigns one buyer decision and rejects the adjacent inference.
| Decision | Owns | Keep separate |
|---|---|---|
| Identified dosing-system interface | The proposed non-LSR dosing or blending system, material components, dosing mode, IMM cycle or batch relationship, physical feed point, selected functional/data scope, responsibility split and configured evidence. | This page selects no dosing architecture, device, recipe, percentage, throughput, timing, mounting hardware, setting or operating method. |
| Resin, screw and barrel review | The controlled resin grade, additives or regrind context and the injection-unit hardware questions raised by wear, corrosion, residence, feeding and processing behaviour. | A resin-to-hardware review does not identify the dosing components, feed topology, recipe owner or machine-to-doser exchange. |
| Cell utilities and installation | Site supply points, available capacity, utility quality, connection ownership, layout, drainage and installed-cell evidence. | A utility schedule does not define which material component is dosed, where it enters the process or how the cycle and recipe are coordinated. |
| General machine-interface register | Every physical, utility, electrical, functional, data, safety and access endpoint across the IMM, mold, robot, auxiliaries and site systems. | The dosing route narrows one material-delivery subsystem and its components. It does not replace the complete cell endpoint register. |
| IMM-to-MES data contract | The identified IMM and MES endpoints, EUROMAP 77 / OPC 40077 release, job, cycle and dataset semantics, write boundary and reconciliation evidence. | A dosing value in a production record does not prove dosing-system identity, component mapping, recipe ownership, cyclic relationship or writable function. |
| Central material supply, drying and conveying | The wider source-to-machine material route, storage, order management, drying, conveying, line clearing, tracing and multi-machine ownership. | This page records only the identified dosing-system boundary; it does not design or release the upstream material-supply network. |
| Changeover, startup and production release | Approved site procedures, recipe release, material verification, first-off checks, deviations and the authority to start normal production. | The interface register supplies controlled identities and evidence inputs, not a loading, cleaning, calibration, purging or startup procedure. |
| FAT/SAT programme | The full configured-machine and installed-cell methods, conditions, witnesses, observations, deviations, retest and closure. | This route names evidence rows to request. Qualified project parties still define and approve the test and safe operating methods. |
Complete every field for the identified project; keep assumptions visible.
| Register field | Record for the proposed interface | Evidence to request |
|---|---|---|
| Project and dosing-interface boundary | Intended material-delivery function, included dosing or blending equipment, IMM integration work, upstream/downstream systems, site work, supplier work and explicit exclusions | Approved scope diagram and responsibility matrix naming machine, dosing-system, material-supply, integrator and site owners |
| Injection molding machine identity | Exact proposed machine, injection-unit and controller configuration, software/option baseline, feed-zone endpoint and responsible machine party | Configuration-specific machine record without implying a NEW ORIENTAL IMM dosing option or implementation |
| Dosing-system identity and revision | Proposed manufacturer, model/configuration, serial identity when assigned, controller/software revision, device mapping and responsible supplier | Controlled supplier configuration; a generic product family, photograph or interface title is insufficient |
| Material-component register | Buyer-approved identity and role for every main material, additive, color, regrind or other included component, plus every excluded material stream | Controlled component list tied to recipe aliases, supplier/grade records and the proposed project without publishing a formulation |
| Material state and handling basis | Relevant physical form, flow questions, moisture/temperature history questions, contamination sensitivity and assumptions requiring material-supplier review | Project material basis and supplier disposition; this checklist prescribes no material preparation or handling condition |
| Dosing architecture and mode | Supplier-defined batch, continuous or combined topology; gravimetric, volumetric or conveying-only component roles; weighing/mixing stages; and unsupported alternatives | Configuration drawing and functional description for the proposed system rather than a generic method ranking |
| Mounting and feed-point boundary | Direct machine-throat, machine-adjacent, floor, mezzanine, day-bin or other proposed relationship, final material discharge point, support owner and access boundary | Controlled arrangement drawing and load/access disposition; no adapter, frame or installation dimension is selected here |
| Upstream and downstream material path | Where each material enters the included subsystem, any loader/dryer/conveyor/day-bin handoff, discharge destination, isolation boundary and owner | Reconciled material-flow diagram that keeps the wider material-supply network on its separate release path |
| Component and delivery-device mapping | Which hopper, valve, screw, feeder, weigh chamber, mixer or other identified element handles each material component and which elements are optional or absent | Configuration-specific component map; model vocabulary does not prove installed hardware or suitability |
| Cyclic, batch or continuous relationship | Whether material delivery is shot-synchronous, independently batched, continuous or supplier-defined otherwise, including the initiating/receiving owners and open timing questions | Approved functional narrative and configured observations without prescribing a trigger, duration or sequence |
| Recipe and dataset ownership | Recipe/dataset identity, revision, component aliases, source of truth, edit/release authority, destination, retention owner and change approval | Controlled recipe/dataset lifecycle record with no formulation or universal transfer workflow published |
| Quantity and value semantics | Meaning, source, unit family and basis for every required component share, shot-related value, batch value, rate, total, scrap or status record | Field dictionary that distinguishes target, actual, total, reset state, validity and missing value without setting a project number |
| Functional handshake boundary | Every proposed enable, cycle/dose request, ready, active, complete, inhibit, fault or other function; physical/data path; initiator; receiver; and exclusion | Allowlisted functional matrix and configured observation without publishing a pinout, command order or operating sequence |
| Companion specification and release | Selected EUROMAP 82.4 / OPC 40082-4 release, namespace/model version, related common-type release, profile/facet scope and any controlled extension | Dated applicability record distinguishing official scope, optional elements, vendor extensions and project assumptions |
| Endpoint, read, write and method scope | Identified endpoint owner; proposed read/write/method families; business purpose; authorization owner; unsupported functions; and separate hardwired/proprietary paths | Configuration-specific support and test matrix; no node list, address, port, credential, certificate or network design is published |
| Alarm, fault and disposition ownership | Required state/error meaning, source component, display/record owner, acknowledgement/reset authority, product-disposition owner and escalation boundary | Approved semantic matrix and configured observations; this page sets no alarm value, reset action or fault-recovery method |
| Utilities, loads and physical responsibility | Configuration-specific services and loads for the included package, site connection points, structural/access ownership and dependencies carried to installation planning | Supplier schedules and approved drawings without a fixed capacity, connection, mounting or utility instruction |
| Material change and contamination evidence | Which component identities, retained-material locations, segregation risks, inspection records, supplier cleaning references and release owners apply after a material/configuration change | Project-approved evidence index and disposition record; no cleaning, purging, filling or calibration procedure is supplied here |
| Configured FAT and SAT evidence | Which identities, mappings, material/recipe records, functional states, displayed/recorded values, deviations and as-installed relationships require factory and site observation | Approved FAT/SAT references, dated observations, witnesses, deviations and closure under the separate acceptance programme |
| As-built handover and release decision | Final equipment/component identities, drawings, software/specification releases, mappings, accepted deviations, open assumptions, owners and recheck triggers | Signed handover index and action register; unanswered compatibility, capability, value or evidence items remain open |
Retain evidence for the exact materials, components, endpoints and revisions.
| Evidence gate | Record to retain | Boundary |
|---|---|---|
| Identity and material gate | Exact IMM, dosing-system, component, material/alias, recipe/dataset and responsible-party identities with controlled revisions. | A generic blender class, recipe name, product page or interface title does not prove the proposed configuration or material relationship. |
| Physical path and mounting gate | Approved material-flow path, mounting/feed-point relationship, upstream/downstream handoffs, support/access ownership and as-installed identification. | Qualified suppliers and site parties select and approve the hardware; this page supplies no frame, adapter, hopper, routing or installation design. |
| Dosing and cycle-basis gate | Supplier-defined architecture, component roles, cyclic/batch/continuous relationship, value semantics and configured functional observations. | Method labels do not establish suitability, accuracy, throughput, timing, recipe integrity, part quality or process equivalence. |
| OPC UA and functional-scope gate | Selected OPC 40082-4 release/model, proposed profile/facet, supported elements, endpoint ownership, read/write/method scope and controlled extensions. | A namespace, profile or companion-specification name does not prove endpoint support, interoperability, conformance or certification. |
| Change and contamination gate | Material/component change identity, retained-material locations, approved supplier references, inspection/disposition evidence and release owner. | The evidence index is not a loading, cleaning, purging, calibration, startup or fault-recovery procedure. |
| Acceptance and handover gate | Project-approved FAT/SAT references, observations, witnesses, deviations, closure, as-built records and recheck triggers. | The register names evidence to request; it is not a test method, risk assessment, commissioning plan, operating instruction or safety validation. |
Reviewed 1 August 2026. EUROMAP and the OPC Foundation publish OPC 40082-4 / EUROMAP 82.4 for non-LSR dosing-system data exchange; the current OPC record is Release 1.0 dated 1 July 2026. EUROMAP 86 is a separate, broader release-candidate material-supply scope. motan articles are named-manufacturer examples only. None proves a NEW ORIENTAL IMM dosing system, interface, compatibility, accuracy, performance, certification or case.
The official page defines data exchange between production machines and non-LSR dosing systems, identifies EUROMAP 83 as the common-types basis and publishes version 1.0.0.
Boundary: The title and download do not prove that an identified machine or dosing system implements, supports or interoperates through the specification.
The official record lists Release 1.0, published 2026-07-01, as current and identifies namespace model version 1.0.0.
Boundary: A release or namespace identity is not endpoint implementation, compatibility, interoperability, conformance or certification evidence.
The official scope covers directly or separately mounted non-LSR dosing systems, material/components, configuration/status, process information and cell exchange, while excluding safety-related signals such as emergency stop.
Boundary: The information model is not a universal node list, recipe, command sequence, safety design or proof of configured endpoint support.
The official section distinguishes an inline dosing device on a cyclic IMM from continuous processing and separately describes a batch blender's relationship to shot synchronization.
Boundary: Those semantics do not select a topology, feed arrangement, trigger, duration, quantity or setting for the identified project.
The official profile list separates the Basic Server Profile from the Alarms Server Facet.
Boundary: A profile or facet name requires configuration-specific support and verification. It is not an implementation, certification or interoperability result.
The official page places loaders, silos, pipes, dryers, mixers and dosing units inside a broader material-supply-system model and identifies Part 1 order management as a Release Candidate.
Boundary: That broader release-candidate scope is kept separate. It does not establish a central system design, final implementation or NEW ORIENTAL IMM capability.
This attributed article illustrates one batch weighing/mixing topology, alternative feed destinations and an IMM shot-information/trigger relationship, exposing fields that a buyer must identify.
Boundary: The topology, devices, functions and results belong to the motan discussion. None transfers to NEW ORIENTAL IMM or becomes a universal design or performance claim.
This attributed article says device choice depends on material properties, dosing method, required amount per cycle or time and surrounding conditions, then gives named device examples.
Boundary: The examples do not rank a method universally, select a device for the buyer or prove NEW ORIENTAL IMM supply, integration, accuracy or performance.
The answers separate material components, physical feeding, cyclic coordination, data scope and configured evidence.
No. Identify the exact machine and dosing-system configurations, selected release/model, endpoint and functional scope, component/material mappings, physical feed relationship and configuration-specific FAT/SAT evidence.
No. Its official scope refers liquid silicone and rubber dosing systems to OPC 40082-3. Keep LSR equipment, material, process and interface requirements on their own qualified project path.
No universal ranking follows from a method label. Compare the actual materials, component roles, amount basis, cyclic or continuous relationship, feed topology, environment, supplier evidence and project acceptance method.
Not without its meaning and ownership. Record the source, unit family, material basis, target/actual distinction, revision, validity, receiving system and reconciliation evidence for every exchanged value.
No. Configuration hardware and approved procedures remain with qualified machine, dosing-system, material, integrator and site parties. This page records identities, responsibilities and evidence to request.
Include machine and dosing-system identities; all material components; architecture and feed-point map; cyclic/batch relationship; recipe and value semantics; selected OPC 40082-4 scope; functional and fault ownership; utilities; material-change evidence; FAT/SAT records; and open deviations.
Attach the controlled machine and dosing-system identities; material/component and recipe maps; dosing architecture and feed-point relationship; cyclic/batch basis; quantity/value semantics; selected OPC 40082-4 release and profile/facet; endpoint and functional scope; fault ownership; utilities; material-change evidence; FAT/SAT records; and open deviations. Keep every unconfirmed supplier implementation, compatibility, setting, accuracy, certification and result open.
Build the machine brief