Pair the controlled mold-circuit map with the identified temperature-control device, machine endpoint, physical and utility responsibilities, selected OPC 40082-1 scope and configuration-specific FAT/SAT evidence.
Release the physical circuit, external services, measurement and data relationship as separate evidence rows. Keep every unknown supplier implementation, compatible option and operating value open until the responsible parties provide project records.
Build the fixed thermal-interface briefEach row assigns one buyer decision and rejects the adjacent inference.
| Decision | Owns | Keep separate |
|---|---|---|
| Identified mold-temperature interface | The controlled mold-circuit map, temperature-control device and zone identities, machine/display endpoint, selected data scope, responsibility split and configuration-specific FAT/SAT evidence. | This page publishes no hose or coupling selection, connection drawing, setpoint, flow, pressure, temperature, pump, alarm or operating instruction. |
| Cell utilities and installation | Site supply points, utility quality, available capacity, connection ownership, isolation boundary, layout, drainage and installation evidence for the complete cell. | A site water or power entry does not define the mold-circuit map, the selected temperature-control device or its machine/data relationship. |
| General machine-interface register | Every physical, electrical, utility, functional, data, safety and access endpoint across the IMM, mold, robot, auxiliaries and site systems. | The temperature-control route narrows one peripheral and its mold circuits. It does not replace the complete endpoint register. |
| Hot-runner controller interface | Mold heating zones, thermocouples, electrical demand, controller, plugs, valve-gate scope, hot-runner data exchange and acceptance evidence. | A hot-runner temperature zone is not automatically a circulating mold-temperature-control circuit or an OPC 40082-1 TCD zone. |
| IMM-to-MES data contract | The identified machine/MES endpoints, EUROMAP 77 / OPC 40077 scope, job, cycle and dataset semantics, write boundary and reconciliation evidence. | Peripheral process values appearing in a machine or MES record do not prove a TCD endpoint, zone mapping, writable function or physical circuit. |
| FAT/SAT programme | The full configured-machine and installed-cell test plan, approved methods, conditions, witnesses, observations, deviations, retest and closure. | This route identifies evidence rows to request. Qualified project parties still define the test and safe operating method. |
Complete every field for the identified project; keep assumptions visible.
| Register field | Record for the proposed interface | Evidence to request |
|---|---|---|
| Project and thermal-interface boundary | Mold-temperature-control purpose, included mold circuits, proposed equipment and integration work, site work, supplier work and every explicit exclusion | Approved scope diagram and responsibility matrix naming mold, machine, TCD, manifold, integrator and site owners |
| Mold identity and controlled revision | Exact mold, fixed and moving halves, insert or auxiliary thermal loads where relevant, drawing revision and responsible mold party | Controlled mold record tied to the proposed project rather than a generic mold family or photograph |
| Mold-circuit identity and mapping | Buyer-approved names for every included supply/return pair, mold half or zone, circuit relationship and current drawing status | Controlled circuit diagram and cross-reference that can be reconciled at the mold, manifold and TCD |
| Temperature-control device identity | Proposed manufacturer, model/configuration, serial identity when assigned, software revision, device-zone identity and responsible supplier | Configuration-specific supplier record; a device class, catalogue family or interface title is insufficient |
| IMM and controller endpoint identity | Exact proposed machine/controller identity, installed software and option baseline, display or integration endpoint and owner | Configuration record tied to the proposed machine without implying any NEW ORIENTAL IMM implementation |
| Heat-transfer medium and process basis | Buyer-approved medium, process purpose, material compatibility questions, external cooling/heating relationship and assumptions requiring supplier review | Project basis and supplier disposition; this checklist selects no medium or operating condition |
| TCD-to-manifold circuit relationship | Which TCD/device zone feeds which manifold or distribution point and which mold circuits it serves, including shared or separate returns | Configuration drawing with identities and revision, not an inferred one-to-one relationship |
| Physical connection responsibility | Connection endpoints, hose/coupling and distribution ownership, routing and access responsibilities, leak-containment boundary and exclusions | Supplier-approved interface schedule and installed identification; no connection dimension or assembly instruction is published here |
| External service and load boundary | Site services required by the identified TCD/manifold package, supplied connection points, site connection points and declared dependencies | Configuration-specific utility schedule carried into the separate installation checklist |
| Sensor and measurement-point map | Which device or circuit supplies each required temperature, flow, pressure or status observation and where the measurement point belongs | Controlled instrument and signal map with responsible owner; a screen label alone is not a measurement definition |
| Value semantics, units and status | Meaning, unit family, source, actual/set/limit distinction, validity/status meaning and missing-value treatment for each required record | Field dictionary and configured observations without prescribing a target, tolerance or sampling interval |
| Companion specification and release | Selected EUROMAP 82.1 / OPC 40082-1 release, related OPC 40083 release, document status and any controlled project extension | Dated applicability record distinguishing official scope, optional elements, vendor extensions and project assumptions |
| Profile and facet scope | Basic server scope and any proposed alarms or maintenance facets for the identified endpoint, with unsupported or excluded functions | Configuration-specific support declaration and testable matrix; profile names are not an implementation or certification result |
| Data endpoint and ownership boundary | Which identified endpoint provides or consumes the required TCD/device-zone information, who owns mapping and which path remains separate | Approved endpoint and responsibility record without publishing a network design, address, port, credential or certificate plan |
| Read, write and method boundary | Every proposed read, write or method family, its business purpose, initiating owner, receiving owner, prerequisite approval and exclusion | Allowlisted functional matrix and configured observation; no universal node map, command order or operating sequence is supplied |
| Alarm, fault and responsibility boundary | Required status or alarm meaning, source, display/record owner, acknowledgement responsibility and project response owner | Approved semantic matrix and observed configured behavior; this page sets no alarm value, reset method or safe response |
| FAT evidence package | Which circuit identities, endpoint mappings, displayed/recorded values, proposed functions and open deviations must be observed at factory review | Approved FAT references, dated observations and deviation ownership under the separate acceptance programme |
| SAT evidence package | Which as-installed identities, site services, routing, circuit mapping, data path and handover records require site confirmation | Approved SAT references tied to the installed cell without prescribing commissioning or operating steps |
| As-built handover and change control | Final identities, drawings, software and specification releases, mappings, accepted deviations, owners and recheck triggers | Signed handover index and later change log covering mold, TCD, manifold, hose/coupling, sensor, software or endpoint changes |
| Open assumptions and release decision | Every unknown compatibility, capability, option, value, responsibility or evidence item, its owner, due record and current release status | Controlled action register; unanswered items remain open instead of becoming supplier or performance claims |
Retain evidence for the exact circuits, endpoints and revisions.
| Evidence gate | Record to retain | Boundary |
|---|---|---|
| Identity and circuit gate | Exact mold, circuit, TCD/device zone, manifold, machine/controller and responsible-party identities with controlled revisions. | A generic diagram, catalogue page or TCD class does not prove the proposed physical circuit or equipment configuration. |
| Physical and utility gate | Approved endpoints, routing and connection ownership, external services, distribution relationship and as-installed identification. | Qualified suppliers and site parties select and approve the hardware; this page supplies no dimensions, materials or connection instructions. |
| Measurement and semantics gate | Required values, sources, measurement points, units, state meanings and configured observations for each included circuit or device zone. | A displayed number does not establish sensor location, accuracy, acceptable process range or product quality. |
| OPC UA scope gate | Selected OPC 40082-1 and OPC 40083 releases, proposed profiles/facets, supported elements, controlled extensions and functional evidence. | A namespace or companion-specification name does not prove endpoint support, interoperability, conformance or certification. |
| Acceptance gate | Project-approved FAT/SAT references, observations, witnesses, deviations, retest and closure for the configured interface. | The register names evidence to request; it is not a test procedure, risk assessment, commissioning plan or operating instruction. |
| Handover and change gate | As-built circuit and endpoint records, software/specification revisions, accepted deviations, owners and recheck triggers. | A later mold, TCD, circuit, sensor, manifold, connection, software or interface change reopens the affected evidence rows. |
Reviewed 1 August 2026. EUROMAP and the OPC Foundation identify Release 1.01 for temperature-control-device data exchange; the OPC reference separates its basic, alarms and maintenance facets and excludes safety-related signals. ENGEL and HB-Therm sources are named-manufacturer examples only. None proves a NEW ORIENTAL IMM device, interface, compatibility, performance, conformity, certification or case.
The official series page identifies EUROMAP 82.1 for temperature-control devices and says the series standardizes data exchange from peripherals to production machines and higher-level systems. It lists Release 1.01 for part 82.1.
Boundary: The series page is a scope and release record. It does not prove that an identified machine, TCD or project endpoint implements or supports the specification.
The official reference lists Release 1.01, published 2020-06-01, as current for temperature-control-device data exchange and identifies the primary namespace model version.
Boundary: A release or namespace identity is not an endpoint implementation, interoperability, conformance, certification or supplier-capability record.
The official scope covers general device information, status and process data and excludes safety-related signals such as emergency stop. The model distinguishes device zones, process values and optional elements.
Boundary: The published model does not prove that every optional element or method is present, writable, correctly mapped or fit for the identified project.
The official profile chapter separates the basic server profile from alarms and maintenance server facets.
Boundary: Profile and facet names require configuration-specific support and verification evidence. They are not interchangeable with certification or interoperability results.
This named OEM example shows circuit-level monitoring, machine-display integration and retained records for an ENGEL eco-flomo configuration, illustrating why circuit identity, measurement source and record ownership belong in an RFQ.
Boundary: The functions, limits, integration and results belong only to the named ENGEL configuration. None transfers to NEW ORIENTAL IMM or establishes a universal design or performance claim.
This named TCD-manufacturer example describes OPC UA communication and translation between EUROMAP 82.1 and listed proprietary protocols, showing why exact endpoint, protocol and ownership records are required.
Boundary: The HB-Therm functions apply only to the named products and configurations. They do not prove a machine-side option, compatibility, cybersecurity result or NEW ORIENTAL IMM capability.
The answers separate physical circuits, utilities, data scope, supplier capability and configured evidence.
No. Identify the exact mold circuits, TCD/device zones, machine endpoint, physical and utility responsibilities, selected interface release, proposed functions and configuration-specific FAT/SAT evidence.
No. It is a temperature-control-device data-exchange model. Physical connections, circuit distribution, materials, routing and site services remain project-specific supplier and site responsibilities.
No. Its official scope expressly excludes safety-related signals such as emergency stop. Keep the applicable machine, peripheral and site safety boundaries in the qualified project risk and validation work.
No. Record the source device, measurement point, circuit or device-zone mapping, value meaning, unit, validity/status and configured acceptance evidence. A displayed value alone does not prove process suitability or part quality.
No. They are named-manufacturer examples used only to expose procurement fields. Their devices, functions, limits, integration, results and interfaces do not transfer to NEW ORIENTAL IMM.
Include the mold and circuit identities; TCD, device-zone, manifold and machine endpoint identities; medium and utility basis; connection ownership; sensor/value semantics; selected OPC 40082-1 scope; read/write boundary; fault ownership; FAT/SAT evidence; handover revisions; and open deviations.
Attach the controlled mold and circuit map; identified TCD/device zones, manifold and machine endpoint; medium and site-service basis; connection and measurement ownership; selected OPC 40082-1 and OPC 40083 releases; proposed profiles/facets and read/write boundary; fault responsibilities; FAT/SAT evidence; handover revisions; and open deviations. Keep every unconfirmed supplier implementation, compatibility, operating value, certification and result open.
Build the machine brief