EUROMAP 77 is the OPC-UA companion specification that standardises data exchange between plastic injection moulding machines and MES systems. It defines a shared information model (machine state, per-shot cycle data, counters, alarms and job data) so an MES reads the same nodes on machines from different manufacturers.
Where EUROMAP 77 shows up on the plant floor
EUROMAP released the first version in May 2018 and, after the joint working group with the OPC Foundation was set up, the specification is also published under the latter’s neutral umbrella: EUROMAP 77 release 1.01 is identical to OPC 40077. It belongs to a family: EUROMAP 83 holds the general type definitions for plastics and rubber machinery, and EUROMAP 82 covers peripheral devices, starting with temperature control units. On the plant floor it appears on recently acquired moulding machines, where the OPC-UA server with the EUROMAP 77 model ships from the factory, often as a licensed option, and in installations where new machines coexist with older ones that speak only EUROMAP 63. For the Valencian plastics sector that coexistence is the normal situation, not the exception.
EUROMAP 77 versus EUROMAP 63 and versus generic OPC-UA
Against EUROMAP 63 the change is a shift of paradigm: from file exchange polled in a shared directory to typed nodes in an address space, with subscriptions that notify as each cycle closes, with certificates and encryption, and with a defined vocabulary instead of a parameter table extended by every manufacturer. The second comparison is subtler and matters more in practice: a machine simply "having OPC-UA" is not enough. An OPC-UA server without a companion specification exposes nodes named after the vendor’s internal conventions, and the mapping work is still ahead of you. What EUROMAP 77 adds is exactly the missing layer: which node is the switchover pressure, which one the good-parts counter, how an alarm is represented. The MES can then read two moulding machines from different brands with the same configuration.
Getting EUROMAP 77 data into a data layer
Ingestion works by subscription: the client creates monitored items on the nodes of interest and the server notifies on change, instead of the collector asking continuously. Per-shot data arrives as the cycle closes, which is the natural production unit in injection moulding, so the stream is discrete and its volume depends on cycle time rather than on a polling interval.
Two parameters are worth telling apart, because they are routinely conflated. The sampling interval is how often the server looks at the underlying variable; the publishing interval is how often it delivers queued notifications. Asking for a 50 ms publishing interval speeds nothing up if the server refreshes that variable every 200 ms: the real limit is the control’s internal cycle, not the client. In any case, OPC-UA over TCP on a conventional plant network is not a deterministic channel: it serves per-cycle data, state and alarms, while machine regulation stays inside the control itself.
Two practical issues decide whether the rollout lands. The first is certificate management: client and server must trust each other, and that trust expires; planning renewal before go-live prevents connections dropping months later with no apparent cause. The second is verifying the actual implementation before designing the MES on top of it. EUROMAP 77 availability is often a purchase option and its coverage varies between manufacturers, so the node set has to be walked on the machine, not on the datasheet. Enabling the server needs no line stop, although some controls require an HMI restart, which is scheduled between jobs. For a mixed fleet, the usual route is translating the older machines into the same model through an intermediate device, so the data layer sees one interface. Designing that bridge between plant and business systems is the subject of OT/IT integration.
Related terms
EUROMAP 77 is a companion specification of OPC-UA and the natural successor to EUROMAP 63. Its typical consumer is the MES, and its deployment is part of the OT/IT bridge. Where the fleet is mixed, an industrial gateway unifies the model before handing it northbound.