1 Scope

OPC 40084-12 describes the data exchange interface for calenders as part of an extrusion line. The interface is used by

MES (Manufacturing Execution System) for collecting the information generated by extrusion lines at a central point for easier quality assurance and job and dataset management.

Line controllers to monitor and set process parameters.

Safety related signals like emergency stop are not included.

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-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-100, OPC Unified Architecture - Part 100: Devices

OPC 10000-100

OPC 40001-1, OPC UA for Machinery - Part 1: Basic Building Blocks

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

OPC 40083: OPC UA interfaces for plastics and rubber machinery – General Type definitions

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

OPC 40084-1: OPC UA interfaces for plastics and rubber machinery – Extrusion – Part 1: General Type Definitions

http://www.opcfoundation.org/UA/PlasticsRubber/Extrusion_v2/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 40084-5 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 40084-12 describes the data exchange interface for calenders as part of an extrusion line. The interface is used by

MES (Manufacturing Execution System) for collecting the information generated by extrusion lines at a central point for easier quality assurance and job and dataset management.

Line controllers to monitor and set process parameters.

6 Calender_InterfaceType

6.1 Calender_InterfaceType Definition

The Calender_InterfaceType is used for the root Object representing a calender as part of an extrusion line. It is based on the ExtrusionDeviceType (defined in OPC 40084-1) and formally defined in Table 1.

The instance(s) of Calender_InterfaceType shall be located under the Machines Object of the Server (see OPC UA for Machinery).

NOTE: If the OPC UA server is implemented directly in the control of a calender then only one instance of Calender_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 Calender_InterfaceType will be created.

The BrowseName of the object instance shall start with “Calender”. It may be extended with additional information, e.g. a number (”Calender_1”) or manufacturer/serial number (“Calender_Bandera_0123456”).

NOTE: Clients will browse the root node by type and not by BrowseName.

6.2 DeviceClass

The DeviceClass Property in the Identification Object inside the ExtrusionDeviceType shall have the value “Calender”.

6.3 HorizontalPosition, VerticalPosition

Position of the calender from a reference point (e.g. floor for vertical position, centre of exit of feeding device (e.g. flat die) for horizontal position).

Unit: mm or inch

6.4 ProductForce

Force of outgoing product.

Unit: N or lbf

6.5 ProductTension

Tension of outgoing product.

Unit: N/mm² or lbf/in²

6.6 CouplingProductForces

Force of ingoing “sub product”

Unit: N or lbf

6.7 CouplingProductTensions

Tension of ingoing “sub product”

Unit: N/mm² or lbf/in²

6.8 Rolls and Gaps

These containers represent the calender rolls and the gaps between them. The RollsType and GapsType are defined in OPC 40084-1.

7 Profiles and Conformance Units

7.1 Conformance Units

This chapter defines the corresponding Conformance Unit for OPC 40084-12.

7.2 Profiles

7.2.1 Profile list

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

7.2.2 Server Facets

This version of OPC 40084-12 defined only one Profile.

NOTE: OPC 40084-1 includes the Facet “Extrusion v2 Production Dataset Management Server Facet“ which indicates that the server supports the 3:ProductionDatasetManagementType (defined in OPC 40083) with all its mandatory InstanceDeclarations and that there is the component ProductionDatasetManagement available in the instance of the Calender_InterfaceType.

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

8 Namespaces

8.1 Namespace Metadata

Table 7 defines the namespace metadata for this document. 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 OPC 10000-5 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 OPC 10000-5.

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

8.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 8 provides a list of mandatory and optional namespaces used in an OPC 40084-12 OPC UA Server.

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

9 (normative) OPC 40084-12 Namespace and mappings

Namespace and identifiers for OPC 40084-12 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/Extrusion_v2/Calender/

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

http://www.opcfoundation.org/UA/schemas/PlasticsRubber/Extrusion_v2/calender/2.00/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/Extrusion_v2/Calender/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 OPC 10000-6.

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

http://www.opcfoundation.org/UA/schemas/PlasticsRubber/Extrusion_v2/Calender/2.00/Opc.Ua.PlasticsRubber.Extrusion_v2.Calender.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/Extrusion_v2/Calender/Opc.Ua.PlasticsRubber.Extrusion_v2.Calender.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.