Freeze endpoints
Name the exact equipment and configured options on both sides; a family-level interface label is not enough.
G15
CELL / INTERFACES
An injection molding machine interface needs a register—not a “ready” label.
Define the exact endpoints, connector, edition, functional signals, safety signals, data set, fault behavior and acceptance evidence for robots, peripherals, molds and MES.
ANSWER FIRST
Split one interface claim into five verifiable layers.
A named EUROMAP or OPC UA interface does not show which connector, optional signal, node, safety path or software release is installed. The register makes both endpoints and every testable function visible.
Place interfaces inside the complete cell planInterface release gate
- Endpoints and intended function
- Specification number, edition and status
- Connector, signals, nodes and units
- Separate safety design and validation
- FAT, SAT and as-built evidence
FIVE LAYERS
Physical, functional, safety, data and access checks need different owners.
An interface is accepted only when its intended function and failure behavior are proven on the configured endpoints.
| Layer | Register | Owners | Acceptance evidence |
|---|---|---|---|
| Physical connection | Connector, mating side, cable, pinout, voltage/current where applicable, location and environmental constraint | Machine, robot/peripheral and cell electrical owners | Continuity, pinout, labeling, strain relief and as-built record |
| Functional signals | Signal name, direction, state logic, timing, optional/required status, sequence and fault behavior | Machine and integrated-equipment controls owners | Normal sequence, denied state, timeout, restart and recovery |
| Safety signals | Designated safety contacts or safety-only interface, device/category or performance basis, reset behavior and risk-assessment owner | Machine/cell safety and destination conformity owners | Approved validation plan; never assume ordinary data exchange carries safety-related functions |
| Data exchange | Protocol/specification, release/status, namespace/profile, node/data list, units, access and timestamps | Machine, equipment, MES and site IT/OT owners | Identification, read/write permissions, values, events, time, disconnect and reconnect |
| Cybersecurity and access | Network zone, accounts/roles, certificates, remote-access approval, update/backup ownership and logging | Buyer IT/OT, machine supplier and integrator | Approved access, credential handover, restore path and unauthorized-access response |
INTERFACE WORKSHEET
Use one row per endpoint pair and intended function.
Duplicate an endpoint pair when different safety, control and data functions need separate evidence or owners.
| Register field | Required entry |
|---|---|
| Interface ID | Unique cell reference linked to the electrical and network drawings |
| Equipment endpoints | Exact machine and robot, peripheral, mold device or MES endpoint |
| Purpose | What the interface must enable; avoid a generic 'connected' status |
| Specification | EUROMAP/OPC/other document number, edition or release-candidate status |
| Connector and media | Plug/socket, cable, network medium, port and physical location |
| Signals/data | Required, optional and unused items; direction, logic, unit and permitted write access |
| Safety path | Safety-related functions, designated contacts/interface and validation responsibility |
| Configuration | Software/firmware, namespace, mapping, option license and controlled revision |
| Fault behavior | Loss of signal/data, timeout, safe state, alarms, reset and restart sequence |
| Evidence | Drawing, mapping, test step, result, issue owner and final as-built file |
ACCEPTANCE SEQUENCE
Test the declared interface from quotation to as-built handover.
This checklist structures procurement evidence; it is not a cell safety design or validation procedure.
Control the edition
Record the recommendation/specification number, release, publication status and any vendor implementation note.
Map every item
Separate connector/pin, functional signal, safety signal, data node, unit, direction and optional status.
Define failure
Agree timeout, loss-of-communication, denied motion, alarm, safe-state, reset and restart behavior.
Test both stages
Use FAT for available endpoint simulation or integration and SAT for the final installed network, safety chain and equipment.
Handover as built
Deliver final drawings, mappings, versions, credentials/access rules, backups, test evidence and unresolved deviations.
PRIMARY SOURCES / BOUNDARY
Use the exact official interface document and publication status.
The sources define interface families and boundaries. They do not prove that any NEW ORIENTAL IMM machine, robot or peripheral implements them.
EUROMAP 67 — Electrical interface between injection moulding machine and handling device / robot
Version 1.11 defines a wired connector with required/optional coordination signals and designated two-channel safety contacts.
Boundary: Confirm the exact implementation, connector, signals and test result; do not describe all EUROMAP machine/robot interfaces as data-only.
EUROMAP 79 — OPC UA interface between injection moulding machines and robots
The official page lists Release Candidate 1.00.06 (updated March 2024) for machine/robot OPC UA data and non-safety coordination.
Boundary: It is a release candidate, not a final Release; the page explicitly keeps safety signals outside OPC UA and points to EUROMAP 81.
EUROMAP 81 — Electrical Interface for Safety Signals
The official library lists EUROMAP 81.1 and 81.2 Version 1.0 (May 2024) for one- or two-safety-device hardware arrangements.
Boundary: Select the correct part and connector; publication does not replace the configured cell risk assessment, destination requirements or validation.
EUROMAP 82 — OPC UA interfaces for peripheral devices
The official page lists Releases for 82.1–82.4 and Release Candidates for 82.5–82.6 at the 2026-07-28 review.
Boundary: Status is part-specific and can change; verify device support, the current part/version and implemented nodes at procurement.
BUYER QUESTIONS
Machine interface FAQ
These answers turn broad compatibility wording into specific endpoints, functions and evidence.
01Is “EUROMAP ready” enough for an RFQ?+
No. Record the exact recommendation or specification, edition/release status, connector/media, required and optional signals or nodes, safety separation, endpoint configurations and acceptance test.
02Can OPC UA carry the machine-to-robot safety signals?+
Do not assume that it does. EUROMAP 79's official page states that safety signals are not exchanged via its OPC UA interface and points to EUROMAP 81. The cell safety design and validation still require responsible-party review.
03Are EUROMAP 67 and EUROMAP 79 interchangeable?+
No. EUROMAP 67 Version 1.11 is a wired connector/signals recommendation that includes designated safety contacts. EUROMAP 79 is currently a release candidate for OPC UA data and non-safety coordination; its official page directs safety signals to EUROMAP 81. Record the exact architecture and part instead of treating the numbers as interchangeable.
04What should an interface FAT test?+
Test available physical connections, mappings, normal and denied sequences, optional signals, data values/units, permissions, alarms, disconnects, timeouts, reset/restart and controlled evidence. SAT must cover the final installed endpoints and site network.
05Who owns the final interface register?+
The purchase scope should assign one integration owner while naming contributors and approvers for machine controls, robot/peripheral controls, safety, MES and IT/OT. The buyer should receive the final as-built register.
INTERFACES / NEXT STEP
Send the endpoints and required functions—not only a standard number.
Attach the robot, peripheral, mold-device and MES list with connector, edition, signals, safety boundary, nodes, fault behavior and planned FAT/SAT evidence.
Build the machine brief