Release one identified mold-to-machine data relationship through controlled asset identity, engineering-record sources, configuration and cavity state, runtime scope, permissions and as-built evidence—not through a digital-mold or OPC UA label.
Put the buyer-controlled mold and article records beside the exact proposed endpoint, supported data scope, authority and configured observations. Preserve source status, assumptions, exclusions and conflicts from RFQ through as-built handover.
Build the fixed mold-data interface briefEach row assigns ownership and rejects what the data record cannot release.
| Decision | Owns | Keep separate |
|---|---|---|
| Identified mold data relationship | One mold's controlled asset identity, article and engineering-record references, runtime endpoint scope, configuration/cavity state, permissions, evidence and as-built handover for one identified machine/cell. | It does not prove a digital-mold function, standard implementation, physical fit, safe operation, process capability, part quality or production release. |
| Mold envelope and injection-unit fit | Mold dimensions, mass, opening/ejection demand, shot-volume and plasticizing questions used to shortlist the machine. | An asset record or data endpoint cannot prove that the mold fits the clamping and injection units. |
| Mold mounting and platen interface | Mounting-face drawings, centering, patterns, support, permitted mounting method and configured platen-fit evidence. | Identity, article and engineering-data fields do not release the mechanical mounting interface. |
| Automatic mold-change package | Clamping, transfer, ejector, service couplings, functional and safety-related boundaries for the configured mold-changing system. | A mold identifier may be an input, but it does not release the changing device, sequence or safety validation. |
| Hot-runner controller interface | Mold-specific zones, heaters, thermocouples, plugs, valve-gate functions, controller scope and configured evidence. | A hot-runner reference inside engineering data is not a supplied controller, wiring map or runtime implementation. |
| Mold temperature-control interface | Controlled mold circuits, TCD/device zones, physical and utility responsibilities, value semantics and configured evidence. | A mold-data record cannot release circuit layout, couplings, medium, utility capacity or thermal performance. |
| General machine-interface register | Every physical, electrical, utility, functional, data, safety and access endpoint across the complete cell. | This route narrows only the identified mold-data relationship and cannot replace the complete endpoint inventory. |
| IMM-to-MES data contract | Identified IMM and MES endpoints, jobs, cycles, datasets, write authority and reconciliation under the selected OPC 40077 release. | A job or dataset carrying a mold ID does not prove a mold AAS record, direct mold endpoint or OPC 40082-5 implementation. |
| Mold protection and pressure evidence | Mold-close protection windows and the separately defined injection, hydraulic-drive and in-cavity pressure meanings and evidence. | A pressure or digital value category in a data model does not define a sensor chain, limit, reaction, protection setting or acceptance result. |
| FAT, SAT and production startup | The complete test programme, conditions, methods, witnesses, deviations, retest, first-off checks and production-release authority. | This page names evidence rows to request; it supplies no test procedure, operating setting or authority to start production. |
The source title and status guide questions; only configured project evidence releases an implementation.
| Layer | Source and status | May inform | Cannot release |
|---|---|---|---|
| Mold identification | EUROMAP 101.1 / IDTA 02038-1 Release 1.0, July 2025; official history records publication on 2025-07-22 | Questions about mold/article identity, owner or affiliation, asset ID, component name and location. | Physical fit, runtime behavior, a controller, an interface implementation or a supplier capability. |
| Design-time engineering record | EUROMAP 101.2 / IDTA 02038-2 Draft 1.0, January 2026; review period started on 2026-01-13 | Questions about article, material, assumed machine data, peripheral and injection-unit context, hot-runner data and mold description. | A final standard, mandatory buyer template, verified machine fit, runtime values or supplier conformity. |
| Runtime mold data exchange | EUROMAP 82.5 / OPC 40082-5 / VDMA 40082-5 Release Candidate 1.0.0; series page says published 2024-07-30 while the PDF cover is dated 2024-09-01 | Questions about identification, configuration, user, operation, process-value categories, cycle information and maintenance scope. | An endpoint, node map, read/write function, security design, safety signal, interoperability, conformance or delivered implementation. |
| Configured project release | Buyer, mold owner, machine supplier, integrator and site records Project-specific controlled evidence; not supplied by a standard title | The exact endpoints, revisions, supported items, permissions, observed results, deviations, owners and as-built files. | Any unobserved function, another configuration, another mold, another site or a universal result. |
Complete every row for the identified project; preserve unsupported and disputed items.
| Register field | Record for the proposed relationship | Evidence to request |
|---|---|---|
| Project and mold-data boundary | Business decision supported, identified mold/machine/cell relationship, included work, integration work, site work and explicit exclusions | Approved scope diagram and responsibility matrix naming the mold owner, toolmaker, machine supplier, integrator, MES/PLM parties and site owners |
| Mold identity and ownership | Owner or affiliation, toolmaker, model/type designation, serial or unique identifier, buyer asset ID, component name and current location scheme | Controlled nameplate/identity record with source, revision, owner and conflicts left open |
| Article identity and revision | Every intended article/part ID and name, product owner, drawing or specification revision and multi-article relationship | Approved article register linked to the released product and mold documentation |
| Mold document and drawing index | Current mold assembly, cavity, electrical, hydraulic/pneumatic, hot-runner, thermal-circuit and handover-document references with revision status | Controlled document index showing supplied, approved, superseded and missing records |
| Intended IMM and cell baseline | Exact machine identity when assigned, controller/application revision, injection unit and installed option baseline, cell identity and responsible owners | Configuration record tied to the proposed project rather than a generic series or controller name |
| Identity source and system of record | Digital nameplate, EUROMAP 101.1/AAS or other record proposed; authoritative owner; storage location; update path; offline availability and conflict rule | Source declaration and representative controlled record without credentials or confidential infrastructure details |
| Engineering-data source and status | EUROMAP 101.2 Draft or other handover structure proposed, document revision, data owner, assumptions, engineered results and unsupported fields | Field-level applicability matrix that preserves Draft status and links each populated item to its project source |
| Mold configuration variants | Possible configuration identities, distinguishing features, allowed relationships, current active configuration and authority to approve a change | Controlled configuration register plus approved observation or document for the delivered arrangement |
| Cavity topology and active state | Cavity count and identities, layout reference, active/disabled state meaning, change ownership and relationship to article and production records | Cavity map and configured comparison; no cavity state is inferred from a total count alone |
| Mold-side controller or endpoint identity | Exact mold device/controller, software and application revision, endpoint owner, installation location and relationship to the machine or higher-level system | Configuration-specific implementation declaration; leave the field open when no direct endpoint is proposed |
| Runtime specification and release | EUROMAP 82.5 / OPC 40082-5 / VDMA 40082-5 release and status, related common-types release and controlled project extensions | Dated applicability record distinguishing Release Candidate scope from actual implementation and vendor-specific additions |
| Supported runtime data categories | Proposed identification, configuration, user, operation, process-value, cycle-information and maintenance categories with included and excluded scope | Configuration-specific support matrix and planned evidence; a specification title alone is insufficient |
| Process-value semantics | Required temperature, pressure, flow, distance, force or digital-value meaning, source/measurement location, unit, timestamp, status/quality and validity boundary | Field dictionary tied to the proposed sensors/devices and configured observations, without universal values or thresholds |
| Cycle, cavity and quality semantics | Cycle identity, mold and cavity count meanings, active job relationship, quality-state owner, actual/average-time meaning and missing or disputed record treatment | Approved semantic matrix and traceable project observations; no data field is treated as proof of part quality by itself |
| Counters and reset/change ownership | Mold-lifetime, job and cavity counter source, initial state, increment meaning, persistence, reconciliation, reset/change authority and audit requirement | Baseline and controlled change record with owner, reason and affected downstream records |
| Maintenance information boundary | Required maintenance identities, source documents, status or alarm meaning, remaining-interval semantics, acknowledgement/reset ownership and explicit exclusions | Project maintenance-information matrix and document references; no interval or procedure is prescribed here |
| Read, write, method and event authority | Every proposed data direction, event, write or method family, business purpose, initiating/receiving owner, approval prerequisite and denied function | Allowlisted authority matrix and configured observation under the approved acceptance plan, without publishing a node map or action sequence |
| User, access and cybersecurity ownership | User/login relationship, account and role owner, network/security responsibilities, certificate lifecycle, logging, backup/update boundary and hardwired/safety separation | Buyer-approved responsibility record; no account, credential, certificate, port or security architecture is published |
| FAT/SAT evidence and deviations | Selected identity, configuration, read/write, process-value, event, disconnect/reconnect and handover observations; conditions, witnesses, deviations and retest owner | Signed configuration-specific record linked to the complete FAT/SAT programme rather than a universal test procedure |
| As-built handover and revalidation | Final identities, mappings, document revisions, supported/unsupported scope, backups, deviations, approval owner and triggers after mold, controller, machine, software or interface change | Released as-built index and change-control record retaining superseded versions and open actions |
Reviewed 1 August 2026. EUROMAP 101.1 is identified as Release 1.0, EUROMAP 101.2 as Draft 1.0 and EUROMAP 82.5 as Release Candidate 1.0.0. Official publication dates and running labels are retained where they disagree. None proves a NEW ORIENTAL IMM digital mold, AAS, OPC UA endpoint, RFID system, data collection, integration, interoperability, certification, result or case.
The official series page lists EUROMAP 82.5 Moulds as a Release Candidate, says its RC was published on 30 July 2024 and describes identification/configuration, user login and process-value monitoring/control as series-level categories.
Boundary: A series page does not prove an endpoint, installed function, data item, interoperability, conformance, safety function or NEW ORIENTAL IMM implementation.
The official PDF identifies Release Candidate 1.0.0, dated 2024-09-01, for mold data exchange during operation and exposes identification, configuration, user, operation, process-value, cycle and maintenance categories. It excludes safety-related signals such as emergency stop.
Boundary: Only high-level categories become RFQ questions. No node map, method signature, write right, sequence, value, security design or implementation claim is transferred.
The official page identifies EUROMAP 101.1 Identification as Release 1.0 published 22 July 2025 and EUROMAP 101.2 Engineering Data as Draft 1.0 published 13 January 2026; it states that the broader series remains under development.
Boundary: Do not present all planned submodels as released or infer an AAS, digital twin, implementation, compatibility, certification or supplier capability.
The official cover and history identify Release 1.0, July 2025, while the running footer still says Version Draft 1.0. The public model exposes mold/article identity, owner/affiliation, asset ID, component name and location questions.
Boundary: The publication-status inconsistency stays visible. Identity fields do not prove physical fit, runtime behavior, an interface, an AAS deployment or a NEW ORIENTAL IMM implementation.
The January 2026 draft describes design handover and pre-production equipment-selection use cases and organizes engineering information around articles/materials, assumed machine/peripheral data, hot runners and the mold description. It distinguishes static/lifecycle AAS information from dynamic OPC UA process data.
Boundary: Draft 1.0 is not a final standard, mandatory project template, validated design, fit result, runtime implementation, supplier conformity or delivered case.
The answers keep identity, engineering records, runtime data and project acceptance inside their separate evidence boundaries.
No. Identify the exact mold/controller and machine endpoints, software revisions, selected specification release, supported categories, read/write/event authority and configuration-specific observations. Keep every unsupported item visible.
No. EUROMAP 101.1 Release 1.0 covers mold identification; EUROMAP 101.2 Draft 1.0 covers design-time engineering data; EUROMAP 82.5 Release Candidate covers runtime mold data exchange. A project still needs its own implementation and acceptance record.
The EUROMAP 82 series page says the 82.5 RC was published on 30 July 2024, while the PDF cover is dated 1 September 2024. The EUROMAP 101.1 cover and history say Release 1.0, but its running footer still says Draft. Preserve both source records rather than silently normalizing them.
No. Use the separate mold-envelope and mold-mounting records for dimensions, mass, tie bars, platens, centering, patterns, support and mounting method. The identity record only links the controlled asset and documents.
No. Record the actual sensor/device, measurement location, unit, timestamp, status/quality semantics and acceptance evidence. A data category or value alone does not establish measurement validity, a limit, a reaction or molded-part quality.
No. It names the responsible records and keeps ordinary data exchange separate from safety functions. Buyer IT/OT, machine, mold, integrator and site safety owners define and approve the architecture, validation and procedures.
Include the controlled mold, article, document and target-machine identities; engineering-data source; configurations and cavities; endpoint and release; supported data categories; value/counter/maintenance semantics; permissions; access ownership; FAT/SAT evidence; deviations; and as-built change control.
Attach the mold, article, document and target-machine identities; engineering-data source and status; configurations and cavity map; proposed endpoint and selected release; supported runtime categories; value, counter and maintenance semantics; permissions and access ownership; configured FAT/SAT evidence; deviations; and as-built change controls. Keep every unconfirmed digital-mold, AAS, OPC UA, RFID, data, integration, interoperability, certification and result claim open.
Build the machine brief