1 Scope

OPC 40077 describes the interface between injection moulding machines (IMM) and manufacturing execution systems (MES) for data exchange. MES are used for collecting the information generated by IMM at a central point for easier quality assurance and job and dataset management. The target of OPC 40077 is to provide a unique interface for IMM and MES from different manufacturers to ensure compatibility.

The following functionalities are covered:

General information about the IMM (manufacturer, model, serial number…), current configuration and status of the IMM including moulds, injection units and power units, and logbook of relevant changes on the machine.

Job management: Information on the jobs running on the machine and the parameters of the production cycles and methods to send jobs from the MES to the IMM and to release the production.

Dataset management: IMM store their configurations in so-called datasets. These include information on nominal process parameters (times, temperatures, pressures …) related to the IMM but also to installed handling systems. OPC 40077 allows transferring datasets between IMM and MES for building a central repository of datasets.

Following functions are not included:

Safety related signals like emergency stop

Direct control of machine movements by the MES

2 Normative references

The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies

OPC 10000-1, OPC Unified Architecture - Part 1: Overview and Concepts

OPC 10000-1

OPC 10000-2, OPC Unified Architecture - Part 2: Security Model

OPC 10000-2

OPC 10000-3, OPC Unified Architecture - Part 3: Address Space Model

OPC 10000-3

OPC 10000-4, OPC Unified Architecture - Part 4: Services

OPC 10000-4

OPC 10000-5, OPC Unified Architecture - Part 5: Information Model

OPC 10000-5

OPC 10000-6, OPC Unified Architecture - Part 6: Mappings

OPC 10000-6

OPC 10000-7, OPC Unified Architecture - Part 7: Profiles

OPC 10000-7

OPC 10000-8, OPC Unified Architecture - Part 8: Data Access

OPC 10000-8

OPC 10000-9, OPC Unified Architecture - Part 9: Alarms and Conditions

OPC 10000-9

OPC 10000-11, OPC Unified Architecture - Part 11: Historical Access

OPC 10000-11

OPC 10001-1, OPC Unified Architecture V1.04 - Amendment 1: AnalogItem Types

http://www.opcfoundation.org/UA/Amendment1/

OPC 10001-3, OPC Unified Architecture V1.04 - Amendment 3: Method Metadata

http://www.opcfoundation.org/UA/Amendment3/

OPC 10000-100, OPC Unified Architecture - Part 100: Devices

OPC 10000-100

OPC 40083: OPC UA interfaces for plastics and rubber machinery – General Type definitions (version 1.02)

http://www.opcfoundation.org/UA/PlasticsRubber/GeneralTypes

3 Terms, definitions and conventions

3.1 Overview

It is assumed that basic concepts of OPC UA information modelling are understood in this specification. This specification will use these concepts to describe the OPC 40077 Information Model. For the purposes of this document, the terms and definitions given in the documents referenced in Clause 2 apply.

Note that OPC UA terms and terms defined in this specification are italicized in the specification.

3.2 Conventions used in this document

The conventions described in OPC 40083 apply.

3.3 Abbreviations

4 General information to OPC UA interfaces for plastics and rubber machinery and OPC UA

For general information on OPC UA interfaces for plastics and rubber machinery and OPC UA see OPC 40083.

5 Use cases

OPC 40077 covers the following functionalities:

General information about the IMM (manufacturer, model, serial number…), current configuration and status of the IMM including moulds, injection units and power units, and logbook of relevant changes on the machine.

Job management: Information on the jobs running on the machine and the parameters of the production cycles and methods to send jobs from the MES to the IMM and to release the production.

Dataset management: IMM store their configurations in so-called datasets. These include information on nominal process parameters (times, temperatures, pressures …) related to the IMM but also to installed handling systems.

6 Basic security requirements

6.1 Application Security

For the communication between IMM and MES the OPC UA application authentication via X509 certificates shall be used. OPC UA provides functionalities for using self-signed certificates that have to be manually added to a “trust list” as well as for certificates issued by a certificate authority (CA).

The minimum requirements of the protocol level for a OPC 40077 compliant connection are:

Use of (self-signed) certificates for OPC UA application authentication

Security Policy: Basic256

Message Security Mode: sign

NOTE: It is not fixed by this specification if the certificate includes a fixed IP address and/or the host name. However, if the certificate includes a host name, a DNS server is expected to resolve the host name. An OPC UA GDS (Global Discovery Server) can be used to manage the connections and certificates.

6.2 User security/Access control

6.2.1 On IMM

On the IMM authentication via user name and password is commonly used.

6.2.2 On MES

For the users and roles of the connection the following applies:

User names can be manufacturer dependent.

Standard roles are

“OPC40077”: read and write access for selected parameters

“OPC40077_read_only”: no writing permissions

Manufactures can add additional roles. They may not start with “OPC40077”. For these roles, more parameters can be writeable than for the OPC40077 role.

The standard user “OPC40077” has the role “OPC40077” (and no other additional role), “OPC40077_read_only” has the roll “OPC40077_read_only” (and no other additional role); the passwords for the standard users are defined by the manufacturers (they may be empty).

NOTE: OPC UA also allow an anonymous-token (e.g. for testing)

7 IMM_MES_InterfaceType

This OPC UA ObjectType is used for the root Object representing an injection moulding machine with all its subcomponents. It is formally defined in Table 1.

The instance(s) of IMM_MES_InterfaceType shall be located under the DeviceSet Object of the Server (see OPC UA Part 100).

NOTE: In most cases the OPC UA server will be implemented in the control of the IMM so only one instance of IMM_MES_InterfaceType will be created. But it is also possible that one OPC UA server is connected to several machine controls as one interface to the MES. In this case several instances of IMM_MES_InterfaceType will be created.

The BrowseName of the object instance shall be "IMM_<Manufacturer>_<SerialNumber>"

Example: "IMM_ARBURG_0123456"

NOTE: The namespace of this BrowseName is the local server URI with namespace index 1 or a vendor specific namespace with server specific namespace index (see Table 14). The BrowseNames of the nodes below are in the namespace of the specification where used Type is defined.

Examples:

8 MachineInformation

The MachineInformation Object provides general information on the injection moulding machine. The MachineInformationType is defined in OPC 40083.

8.1 DeviceClass

The DeviceClass Property in the MachineInformation Object shall have the value "Injection Moulding Machine".

8.2 LogbookEvents

The logbook events defined in OPC 40083 can be used. The supported logbook event types shall be listed in MachineInformation.SupportedLogbookEvents.

9 MachineConfiguration

The MachineConfiguration Object represents the current configuration of the injection moulding machine. The MachineConfigurationType is defined in OPC 40083.

10 MachineMESConfiguration

The MachineMESConfiguration Object represents the current configuration of the injection moulding machine related to the MES. The MachineMESConfigurationType is defined in OPC 40083.

11 MachineStatus

The MachineStatus Object represents the current status of the injection moulding machine. The MachineStatusType is defined in OPC 40083.

12 MachineMESStatus

The MachineMESStatus Object represents the current status of the injection moulding machine related to the MES. The MachineMESStatusType is defined in OPC 40083.

The Object can generate Events of MessageConditionType which includes a Classification Property. For injection moulding machines, the IMMMessageClassificationEnumeration defined in Table 2 shall be used (also in the related logbook event).

13 PowerUnits

The PowerUnits Object is a container for the power unit(s) of the injection moulding machines. The PowerUnitsType is defined in OPC 40083.

14 Moulds

The Moulds Object is a container for the mould(s) of the injection moulding machines. The MouldsType is defined in OPC 40083.

15 InjectionUnitsType

This ObjectType is a container for the injection unit(s) (see container concept in OPC 40083). It is formally defined in Table 3.

When instances for injection units are created, the BrowseNames shall be “InjectionUnit_<Nr>” (starting with 1).

16 InjectionUnitType ObjectType Definition

16.1 Overview

This ObjectType represents the description and status of the injection unit(s). It is formally defined in Table 4.

16.2 Index

The Index Property gives the number of the injection unit.

16.3 BarrelId

The BarrelId Property provides the Id (e.g. serial number) of the barrel.

16.4 IsPresent

It is allowed to create instances of all InjectionUnits that can be connected to the machine (e.g. due to available connectors) to avoid dynamical creation of objects. The IsPresent Property provides information if the InjectionUnit is physically installed on the injection machines.

16.5 InProduction

The InProduction Property provides information if the InjectionUnit is used in the current running production.

16.6 ScrewId

The ScrewId Property represents the Id of the screw installed in the InjectionUnit.

16.7 ScrewDiameter

ScrewDiameter represents the diameter of the screw installed in the InjectionUnit.

16.8 ScrewVolume

ScrewVolume represents the volume of the screw installed in the InjectionUnit.

16.9 MaxScrewStroke

MaxScrewStroke represents the maximum stroke of the screw installed in the InjectionUnit.

16.10 TemperatureZones

This Object is a container for the barrel temperature zones of the injection unit. The TemperatureZonesType is formally defined in OPC 40083. Inside the container the BarrelTemperatureZoneType shall be used.

17 Jobs

The Jobs Object is used for managing production jobs on the machine and for information on their status including process parameters (temperatures, pressures…). The JobsType is defined in OPC 40083.

17.1 Types, methods and events for cyclic jobs

As IMM have a cyclic production, the Types, Methods and Events defined in OPC 40083 for cyclic jobs shall be used:

17.2 Optional properties in CyclicJobInformationType

In the CyclicJobInformationType, as defined in OPC 40083, the Properties MouldId and NumCavities have the ModellingRule optional. When the CyclicJobInformationType is used for a OPC 40077 interface, these Properties become mandatory and shall be filled by the server.

17.3 InjectionUnitCycleParametersType

The InjectionUnitCycleParametersType represents information on the production cycle related to an injection unit. This type is used to extend the CycleParametersEventType defined in OPC 40083.

The BrowseNames of the additional objects shall be “InjectionUnitCycleParameters_<Nr>” (starting with 1)

The Types Example1MouldCycleParametersType and Example2MouldCycleParametersType used in the example are subtypes of the MouldCycleParametersType defined in OPC 40083. The Types Example1InjectionUnitCycleParametersType and Example2InjectionUnitCycleParametersType are subtypes of the InjectionUnitCycleParametersType which is formally defined Table 7.

Table 8 contains a description of the parameters listed in Table 7.

The InjectionUnitCycleParametersType is abstract and the OPC server of the machine shall create a derived type with the additional objects of TemperatureZoneCycleParametersType (defined in OPC 40083) for the temperature zones of the barrel. The BrowseNames of the objects shall be “BarrelTemperatureZoneCycleParameters _<Nr>” (starting with 1 for each injection unit).

18 ProductionDatasetManagement

The ProductionDatasetManagement Object is used for managing production datasets which are files containing the configuration of a machine. The ProductionDatasetManagementType is defined in OPC 40083.

19 Profiles and Conformance Units

This chapter defines the corresponding profiles and conformance units for the OPC UA Information Model for OPC 40077. Profiles are named groupings of conformance units. Facets are profiles that will be combined with other Profiles to define the complete functionality of an OPC UA Server or Client. The following tables specify the facets available for Servers that implement the OPC 40077 Information Model companion specification.

NOTE: The names of the supported profiles are available in the Server Object under ServerCapabilities.ServerProfileArray

Table 9 lists all Profiles defined in this document and defines their URIs.

20 Namespaces

20.1 Namespace Metadata

Table 13 defines the namespace metadata for this specification. The Object is used to provide version information for the namespace and an indication about static Nodes. Static Nodes are identical for all Attributes in all Servers, including the Value Attribute. See Part5 for more details.

The information is provided as Object of type NamespaceMetadataType. This Object is a component of the Namespaces Object that is part of the Server Object. The NamespaceMetadataType ObjectType and its Properties are defined in Part5.

The version information is also provided as part of the ModelTableEntry in the UANodeSet XML file. The UANodeSet XML schema is defined in Part 6.

20.2 Handling of OPC UA Namespaces

Namespaces are used by OPC UA to create unique identifiers across different naming authorities. The Attributes NodeId and BrowseName are identifiers. A Node in the UA AddressSpace is unambiguously identified using a NodeId. Unlike NodeIds, the BrowseName cannot be used to unambiguously identify a Node. Different Nodes may have the same BrowseName. They are used to build a browse path between two Nodes or to define a standard Property.

Servers may often choose to use the same namespace for the NodeId and the BrowseName. However, if they want to provide a standard Property, its BrowseName shall have the namespace of the standards body although the namespace of the NodeId reflects something else, for example the EngineeringUnits Property. All NodeIds of Nodes not defined in this document shall not use the standard namespaces.

Table 14 provides a list of mandatory and optional namespaces used in an OPC 40077 OPC UA Server.

Table 15 provides a list of namespaces and their index used for BrowseNames in this specification. The default namespace of this specification is not listed since all BrowseNames without prefix use this default namespace.

21 (normative)OPC 40077 Namespace and mappings

Namespace and identifiers for OPC 40077 Information Model

This appendix defines the numeric identifiers for all of the numeric NodeIds defined in this specification. The identifiers are specified in a CSV file with the following syntax:

<SymbolName>, <Identifier>, <NodeClass>

Where the SymbolName is either the BrowseName of a Type Node or the BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId.

The BrowsePath for an Instance Node is constructed by appending the BrowseName of the instance Node to the BrowseName for the containing instance or type. An underscore character is used to separate each BrowseName in the path. Let’s take for example, the MachineInformationType ObjectType Node which has the ControllerName Property. The Name for the ControllerName InstanceDeclaration within the MachineInformationType declaration is: MachineInformationType_ControllerName.

The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/PlasticsRubber/IMM2MES/

The CSV released with this version of the specification can be found here:

http://www.opcfoundation.org/UA/schemas/PlasticsRubber/IMM2MES/1.01/NodeIds.csv

NOTE: The latest CSV that is compatible with this version of the specification can be found here:

http://www.opcfoundation.org/UA/schemas/PlasticsRubber/IMM2MES/NodeIds.csv

A computer processible version of the complete Information Model defined in this specification is also provided. It follows the XML Information Model schema syntax defined in Part 6.

The Information Model Schema released with this version of the specification can be found here:

http://www.opcfoundation.org/UA/schemas/PlasticsRubber/IMM2MES/1.01/Opc.Ua.PlasticsRubber.IMM2MES.NodeSet2.xml

NOTE: The latest Information Model schema that is compatible with this version of the specification can be found here:

http://www.opcfoundation.org/UA/schemas/PlasticsRubber/IMM2MES/Opc.Ua.PlasticsRubber.IMM2MES.NodeSet2.xml

___________

Agreement of Use

COPYRIGHT RESTRICTIONS

This document is provided "as is" by the OPC Foundation and EUROMAP.

Right of use for this specification is restricted to this specification and does not grant rights of use for referred documents.

Right of use for this specification will be granted without cost.

This document may be distributed through computer systems, printed or copied as long as the content remains unchanged and the document is not modified.

OPC Foundation and EUROMAP do not guarantee usability for any purpose and shall not be made liable for any case using the content of this document.

The user of the document agrees to indemnify OPC Foundation and EUROMAP and their officers, directors and agents harmless from all demands, claims, actions, losses, damages (including damages from personal injuries), costs and expenses (including attorneys' fees) which are in any way related to activities associated with its use of content from this specification.

The document shall not be used in conjunction with company advertising, shall not be sold or licensed to any party.

The intellectual property and copyright is solely owned by the OPC Foundation and EUROMAP.

PATENTS

The attention of adopters is directed to the possibility that compliance with or adoption of OPC or EUROMAP specifications may require use of an invention covered by patent rights. OPC Foundation or EUROMAP shall not be responsible for identifying patents for which a license may be required by any OPC or EUROMAP specification, or for conducting legal inquiries into the legal validity or scope of those patents that are brought to its attention. OPC or EUROMAP specifications are prospective and advisory only. Prospective users are responsible for protecting themselves against liability for infringement of patents.

WARRANTY AND LIABILITY DISCLAIMERS

WHILE THIS PUBLICATION IS BELIEVED TO BE ACCURATE, IT IS PROVIDED "AS IS" AND MAY CONTAIN ERRORS OR MISPRINTS. THE OPC FOUDATION NOR EUROMAP MAKES NO WARRANTY OF ANY KIND, EXPRESSED OR IMPLIED, WITH REGARD TO THIS PUBLICATION, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF TITLE OR OWNERSHIP, IMPLIED WARRANTY OF MERCHANTABILITY OR WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE OR USE. IN NO EVENT SHALL THE OPC FOUNDATION NOR EUROMAP BE LIABLE FOR ERRORS CONTAINED HEREIN OR FOR DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, RELIANCE OR COVER DAMAGES, INCLUDING LOSS OF PROFITS, REVENUE, DATA OR USE, INCURRED BY ANY USER OR ANY THIRD PARTY IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS MATERIAL, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

The entire risk as to the quality and performance of software developed using this specification is borne by you.

RESTRICTED RIGHTS LEGEND

This Specification is provided with Restricted Rights. Use, duplication or disclosure by the U.S. government is subject to restrictions as set forth in (a) this Agreement pursuant to DFARs 227.7202-3(a); (b) subparagraph (c)(1)(i) of the Rights in Technical Data and Computer Software clause at DFARs 252.227-7013; or (c) the Commercial Computer Software Restricted Rights clause at FAR 52.227-19 subdivision (c)(1) and (2), as applicable. Contractor / manufacturer are the OPC Foundation, 16101 N. 82nd Street, Suite 3B, Scottsdale, AZ, 85260-1830

COMPLIANCE

The combination of EUROMAP and OPC Foundation shall at all times be the sole entities that may authorize developers, suppliers and sellers of hardware and software to use certification marks, trademarks or other special designations to indicate compliance with these materials as specified within this document. Products developed using this specification may claim compliance or conformance with this specification if and only if the software satisfactorily meets the certification requirements set by EUROMAP or the OPC Foundation. Products that do not meet these requirements may claim only that the product was based on this specification and must not claim compliance or conformance with this specification.

TRADEMARKS

Most computer and software brand names have trademarks or registered trademarks. The individual trademarks have not been listed here.

GENERAL PROVISIONS

Should any provision of this Agreement be held to be void, invalid, unenforceable or illegal by a court, the validity and enforceability of the other provisions shall not be affected thereby.

This Agreement shall be governed by and construed under the laws of Germany.

This Agreement embodies the entire understanding between the parties with respect to, and supersedes any prior understanding or agreement (oral or written) relating to, this specification.