Release one defined plant relationship through controlled material, source, destination, route, equipment, order, exception and reconciliation evidence. Preserve EUROMAP 86.1 as a Release Candidate/Draft and keep every actual implementation claim project-specific.
A material or order identifier is useful only after the responsible parties agree which source, route, destination, lot, quantity state and exception it represents. Start with identities and ownership; then record the proposed data scope and configured observations.
Build the fixed material-supply briefNo NEW ORIENTAL IMM central material-supply system, conveying, silo, bin, loader, pipework, dryer, mixer, dosing system, OPC UA, EUROMAP 86, MES/ERP integration, material tracing, traceability, compatibility, interoperability, conformance, certification, performance or delivered case is claimed.
No route, quantity, endpoint, credential, node, write right, threshold, timing, alarm, cleaning method, sequence, setting or result is supplied. Keep every unconfirmed item open for the identified project parties and controlled evidence.
The same material or equipment identity may appear in several records, but each route owns a different procurement and acceptance question.
| Decision owner | Owns | Must stay separate |
|---|---|---|
| Central material-supply order and trace record | The controlled relationship between identified material sources, routes, intermediate equipment, consuming machines, supply orders or jobs, material lots, exceptions, reconciliation and as-built evidence across the defined plant boundary. | It selects no equipment, route, setting, quantity, cleaning method or operating sequence and proves no traceability, interface implementation, compatibility or production result. |
| Resin dryer and machine-feed interface | The exact thermoplastic grade and supplier document, dryer/bin configuration, material-conditioning evidence, residual-moisture method and identified dryer-to-feed-throat handoff. | A dryer record does not release plant-wide source selection, multi-machine routing, supply orders, lot reconciliation or the complete material-trace record. |
| Non-LSR dosing-system interface | Material-component identities, dosing or blending topology, physical feed point, cyclic or batch relationship and selected OPC 40082-4 evidence. | A component or recipe relationship does not release upstream storage, central routing, source reservation, line status or plant-wide material reconciliation. |
| Resin, screw and barrel fit | The identified material grade and injection-unit questions involving feeding, residence, wear, corrosion, contamination and process fit. | Material-to-hardware review does not establish the source container, transport route, order identity, lot movement or central-supply implementation. |
| General machine-interface register | Every physical, electrical, utility, functional, data, safety and access endpoint across the complete configured cell. | This route narrows only the material-order, routing and trace-evidence relationship and cannot release the complete machine, peripheral, mold, robot or safety package. |
| IMM-to-MES data contract | The identified IMM and MES endpoints, jobs, cycles, datasets, writes, failure handling and reconciliation under the selected OPC 40077 release. | A machine job or material field does not prove a plant material-supply order, physical route, source lot, ERP relationship or OPC 40086 implementation. |
| Cell utilities and installation | Site supply points, available capacity, utility quality, loads, layout, access, connection ownership and installed-cell evidence. | A site schedule does not establish material identity, source-to-destination routing, lot movement, order state or trace-record semantics. |
| Mold change and production startup | Approved site procedures, material and recipe release, line disposition, first-off checks, deviations and authority to start production. | This register supplies controlled inputs only; it publishes no loading, unloading, routing, line-clearing, cleaning, restart or recovery instruction. |
| FAT, SAT and production acceptance | Approved methods, conditions, instruments, witnesses, observations, deviations, retest and production-release authority for the configured project. | A standards title or RFQ row cannot become a test method, observed result, safety validation, traceability proof or production release. |
The EUROMAP and VDMA labels describe related source records, but only controlled project evidence can establish what was actually proposed, supported and observed.
| Record | Identity | Public status | May inform | Cannot prove |
|---|---|---|---|---|
| EUROMAP 86 landing page | EUROMAP 86 / OPC 40086 — Material Supply Systems | Release Candidate published 19 October 2022; Part 1 is described as order management, jobs and material tracing | Use the public scope to ask which plant boundary, materials, equipment relationships, orders and tracing evidence are relevant. | A final release, supported data item, endpoint, interoperability, conformance or supplier implementation. |
| EUROMAP download register | EUROMAP 86.1 RC 1.00.01 | Official recommendations register labels the package Release Candidate 1.00.01 dated 19 October 2022 | Record the exact RC identity and a field-level applicability, support and exclusion matrix for the proposed project. | That every concept in the package is required, implemented, final or available from the machine supplier. |
| VDMA publication record | Draft VDMA 40086-1:2023-01 | January 2023 Draft; issue date 25 November 2022; comments requested by 1 March 2023; stated identical to OPC 40086-1 and EUROMAP 86.1 RC 1.00.01 | Preserve the Draft/RC relationship and obtain written agreement on the exact version and project extensions proposed. | A final specification. The source warns that application of the draft is subject to special agreement. |
| Configured project record | Buyer, material-system parties, machine supplier, integrator, MES/ERP parties and site evidence | Project-specific controlled evidence; not supplied by a standard name or a source-page date | Release actual identities, supported items, permissions, route observations, reconciliation, deviations and as-built records. | Any unobserved function, another configuration, another material, another site or a universal result. |
Record unknowns as open items. Do not populate them with a generic plant diagram, a standard title, another supplier's values or an assumed system function.
| RFQ field | Record | Evidence to request |
|---|---|---|
| Project and material-supply boundary | Business decision supported, included plant area and shifts, storage-to-consumption boundary, supplier and site work, integration work and explicit exclusions | Approved scope diagram and responsibility matrix naming material owners, material-system parties, machine supplier, integrator, MES/ERP parties and site owners |
| Consuming IMM and production-cell identities | Every intended injection molding machine and cell identity, controller/application revision when known, feed-point relationship and responsible owner | Controlled machine/cell register tied to the proposed project rather than a generic machine family or unverified endpoint |
| Material, grade, lot and unit identities | Material producer, exact grade, color/additive state, approved secondary-material relationship, lot/batch identity and the units used by each record | Controlled material dictionary with source, owner, revision, alias handling and unresolved conflicts left open |
| Source silo, bin, container and bag identities | Every included source type and unique asset or location identity, current material assignment, ownership and status meaning | Approved source register and arrangement reference without implying that NEW ORIENTAL IMM supplies or controls the source equipment |
| Destination and machine feed-point identities | Every intended destination, receiver, machine feed point and intermediate handoff with its asset/location identity and responsible owner | Controlled destination register reconciled with the material-flow and cell-interface drawings |
| Loader, pipe, valve and route identities | Proposed transport elements and route segments, asset or location references, source/destination relationships and unsupported alternatives | Configuration-specific route map supplied by the responsible system party; no route is inferred from a generic topology example |
| Dryer, mixer and dosing-system relationships | Identified intermediate equipment, controller/application revisions when known, upstream/downstream relationships and separate decision-record references | Controlled equipment relationship map linking to the dedicated dryer and dosing registers without merging their settings or acceptance scope |
| Supply order and job identity/status | Required order/job identifiers, source and owner, relationship to production demand, status meanings, timestamps and missing or disputed record treatment | Approved semantic matrix and representative configured observations rather than a copied standard object model |
| Material request, reservation and availability state | Requesting and fulfilling parties, intended material/source/destination relationship, reservation and availability meanings, authority and exception ownership | Buyer-approved state and authority record with observations under the configured project; no operating sequence is supplied here |
| Planned, issued, returned and consumed quantity semantics | Which quantity states are required, source system, unit, estimate/measurement status, timestamp, rounding or uncertainty treatment and record owner | Controlled quantity dictionary and reconciliation record without a fixed quantity, tolerance, loss allowance or performance promise |
| Active route and material-path confirmation | How the current source-to-destination relationship is identified, its data or physical evidence source, status/validity semantics and confirmation owner | Configured route observation tied to the exact material, equipment identities and project conditions; no route-selection instruction is published |
| Changeover, line-clear and carryover evidence reference | Approved procedure/document references, retained-material locations, prior/current material identities, evidence owner, disposition and release status | Controlled evidence index only; the site and qualified project parties own every cleaning, line-clear, purge and changeover procedure |
| Substitution, quarantine and exception authority | Allowed and prohibited substitutions, quarantine/hold meanings, initiating and approving parties, deviation linkage and downstream notification boundary | Approved authority matrix and representative exception record without publishing automatic actions or production-release instructions |
| EUROMAP 86.1 RC applicability and extensions | Selected EUROMAP 86.1 / OPC 40086-1 / VDMA 40086-1 identity and status, related common-types basis, proposed support, exclusions and controlled extensions | Dated applicability matrix preserving Release Candidate/Draft status and separating specification concepts from actual implementation |
| Endpoint, role, access and write authority | Every proposed endpoint relationship, data direction, role, read/write/event authority, business purpose, approval prerequisite and denied function | Allowlisted responsibility and authority matrix plus configured observations; no endpoint address, credential, node map or write sequence is published |
| MES, ERP and IMM reconciliation boundary | Systems of record for material, order and machine relationships; identifiers and status mappings; ownership of conflicts, late/missing records and corrections | Approved reconciliation matrix linked to the separate IMM-to-MES contract without implying MES/ERP integration or automated traceability |
| Configured FAT/SAT evidence and deviations | Selected identity, order/status, material-path, exception, disconnect/reconnect and reconciliation observations; conditions, witnesses, deviations and retest owner | Signed configuration-specific record linked to the complete acceptance programme rather than a universal test method or procedure |
| As-built mapping, retention and revalidation | Final identities, route/equipment relationships, document and software revisions, supported/unsupported scope, retention ownership, open deviations and recheck triggers | Released as-built index and change-control record retaining superseded versions and unresolved actions |
Qualified project parties define methods, settings, operating sequences and safe conditions for the actual plant.
Controlled project, material, source, destination, route, equipment, order/job and system-of-record identities with owners and missing fields visible.
Identity evidence does not select a system, prove an interface or authorize production.Exact Release Candidate/Draft references, supplier-declared support and exclusions, extensions, responsibilities and conflicts with buyer requirements.
A standard title or support declaration is not an interoperability, conformance or traceability result.Approved conditions and observations for selected identities, order states, routes, material records, exceptions, reconciliation and failure cases.
The responsible project parties define methods and safe conditions; this page supplies no operating or test sequence.Final mapping, supported and unsupported scope, revisions, deviations, retention ownership, approval and revalidation triggers.
Configured evidence applies only to the recorded project and cannot become a universal supplier claim.Reviewed 1 August 2026. EUROMAP identifies 86.1 as Release Candidate 1.00.01 dated 19 October 2022; VDMA publishes the identical work as a January 2023 Draft with issue date 25 November 2022 and a special-agreement warning. The OPC Foundation still lists the work area, but none of these records proves a final release or a NEW ORIENTAL IMM implementation.
The official landing page covers material-supply systems handling granules, powder and liquids, from bagged goods and loaders to complex systems involving silos, pipes, dryers, mixers and dosing units. It says Part 1 covers order management, jobs and material tracing and identifies publication as a Release Candidate on 19 October 2022.
Boundary: The scope becomes buyer questions only. It does not prove a final release, an implemented endpoint, a configured route, interoperability, traceability or NEW ORIENTAL IMM capability.
The current public register lists Material Supply Systems — Order Management as Release Candidate 1.00.01 dated 19 October 2022 and links the official package.
Boundary: A download listing does not make the RC final, mandatory, supported or implemented for the proposed plant, machine or material system.
The official draft is dated January 2023, carries issue date 25 November 2022 and comments-by date 1 March 2023, and states identity with OPC 40086-1 and EUROMAP 86.1 Release Candidate 1.00.01.
Boundary: The warning says application of the draft is subject to special agreement because a final VDMA specification may differ. No protected object model or implementation detail is reproduced here.
The current working-group page still lists OPC 40086 Material Supply Systems and describes the same material-handling, order, job and tracing scope in the wider plastics and rubber information-model programme.
Boundary: A working-group listing does not establish a later final release, certification, conformance, compatibility, implementation or supplier offering.
The answers keep source status, physical routing, data semantics, procedures and supplier capability inside their separate evidence boundaries.
No. It provides a Release Candidate information-model scope. The project still has to identify the materials, sources, destinations, routes, orders, lots, endpoints, permissions, reconciliation rules and configured evidence. A standard title is not a traceability result.
The official EUROMAP pages label version 1.00.01 a Release Candidate dated 19 October 2022. The identical VDMA publication is labeled a January 2023 Draft, with issue date 25 November 2022, and warns that application is subject to special agreement. Preserve both labels.
No. It records identified assets, relationships, responsibilities and evidence needed for a buyer decision. Qualified system parties still select, size, design and validate equipment and routes for the actual materials, plant and operating conditions.
No. The dryer route owns one identified grade, conditioning document, dryer/bin configuration, moisture evidence and dryer-to-feed-throat handoff. This route owns the wider source, route, order, lot, exception and reconciliation relationship across the defined plant boundary.
No. Keep the IMM-to-MES job and cycle contract separate. The project record must reconcile the material and order identities with the observed source-to-destination relationship, responsible system parties, exceptions and as-built evidence.
No. It requests controlled procedure references, evidence and responsible owners only. Site and qualified project parties define, approve and execute every operating, cleaning, line-clear, recovery and safety procedure.
Include the project boundary; consuming machines; materials, lots and units; sources, destinations and route identities; intermediate equipment relationships; order, request and quantity semantics; route and exception evidence; exact RC/Draft applicability; authority and reconciliation; configured FAT/SAT evidence; and as-built change control.
Attach the project boundary; consuming machines; material, lot and unit identities; source and destination register; route and intermediate-equipment relationships; supply-order, request and quantity semantics; active-route, line-clear and exception evidence references; exact EUROMAP 86.1 Release Candidate/Draft applicability; endpoint authority; MES/ERP/IMM reconciliation; configured FAT/SAT observations; deviations; as-built retention and recheck triggers. Keep every unconfirmed system, interface, traceability, compatibility, setting, procedure and result open.
Build the machine brief