1 Scope

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

The following functionalities are covered:

General information about the extrusion lines (manufacturer, model, serial number…), current configuration and status of the extruder line.

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

Recipe management: Extrusion lines store their configurations in so-called recipes. These include information on nominal process parameters (temperatures, dosing volumes …). OPC 40084-2 allows transferring datasets between extrusion lines and MES for building a central repository of recipes.

Following functions are not included:

Safety related signals like emergency stop

Direct control of machine movements by the MES

This part of OPC 40084 deals with extrusion lines and functionalities related to the whole system. Information models for its components (extruder, dies, winders…) are defined in the other parts.

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-2 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

The following functionalities are covered:

General information about the extrusion lines (manufacturer, model, serial number…), current configuration and status of the extruder line.

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

Recipe management: Extrusion lines store their configurations in so-called recipes. These include information on nominal process parameters (temperatures, dosing volumes …). OPC 40084-2 allows transferring datasets between extrusion lines and MES for building a central repository of recipes.

6 ExtrusionLine_InterfaceType

6.1 ExtrusionLine_InterfaceType Definition

This OPC UA ObjectType is used for the root Object representing an extrusion line as overall system. It is formally defined in Table 1.

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

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

The BrowseName of the object instance shall be “ExtrusionLine_<Manufacturer>_<SerialNumber>”.

Example: “ExtrusionLine_battenfeld_4”.

6.2 Optional childs in ExtrusionDeviceType

The SuperType ExtrusionDeviceType includes the optional Variables Target and Strand which are applicable only for the components of an extrusion line and not for the complete line represented by the ExtrusionLine_InterfaceType. Therefore, these variables shall not be used in the instances of ExtrusionLine_InterfaceType.

6.3 Components

Instances for all components of an extrusion line are located directly under the Machines Object in the server representing the component. If the server representing the extrusion line is an aggregating server also providing information for components of the extrusion line, the instances should be referred also by the Components Object according to OPC 40001-1 for easier access.

6.4 MachineMESConfiguration

The MachineMESConfigurationType is defined in OPC 40083. Here a list of standstill reasons for later selection by the operator can be defined.

6.5 MESMessage, SetMESMessage, ClearMESMessage

The Object MESMessage and the methods SetMESMessage, ClearMESMessage are defined in OPC 40083 and used for sending text message from the MES to be shown on the machine.

NOTE: The Object MESMessage and the methods SetMESMessage, ClearMESMessage are taken out of the MachineMESStatusType, because not all functionalities defined there are relevant for extrusion lines.

6.6 Users

The UsersType is defined in OPC 40083 and provides information on the current users on the machine/device.

6.7 ConfigurationParameters

The ConfigurationParameters Property contains a list of parameters, that can be used within the job description to configure the production of the extrusion line. The ConfigurationParametersType is defined in OPC 40083.

The following configuration parameters are standardized for OPC 40084-2:

Manufacturer dependent configuration parameters shall have an Id ≥ 100.

6.8 MaterialList

This Object is used to provide a list of materials which are intended to be used on the extrusion line.

The MaterialListType is defined in OPC 40083.

7 ProductionParameters

The ProductionParametersType contains several production parameters which are related to the complete extrusion line. Process parameters of the components (e.g. core extruder, winder) are located inside the models for these components.

7.1 GoodProduct

Indication if the produced product has a good quality. Can be set by the machine or the operator. When it changes from true to false the line control shall create an alarm.

This Property gives the general information on the complete extrusion line. The JobType (see 8.3) contains also a Property GoodProduct which is specific for the running job. When two or more jobs are running in parallel, the product quality of each strand can be different. That means, if in one of the jobs GoodProduct becomes False, then the GoodProduct in ProductionParameters shall also be false.

7.2 Throughput

Throughput of the extrusion line in mass per time (e.g. kg/h).

7.3 ProductWeight

Weight of the produced product in mass per length or volume (e.g. g/m, kg/m³).

7.4 LineSpeed

Production speed of the line in length per time (e.g. m/s).

7.5 ElectricalEnergy

Electrical energy of the extrusion line. The EnergyType is defined in OPC 40083.

7.6 FluidEnergy

Energy for the cooling of the whole extrusion line with fluid. The EnergyType is defined in OPC 40083.

7.7 PressureAir

Consumption of pressure air of the whole extrusion line (volume at standard conditions). The EnergyType is defined in OPC 40083.

8 Management of Jobs with job groups and jobs

The definition which product (family) is produced is done by a job group. This defines which equipment, production dataset and materials are used and which configuration parameters (e.g. width, length of foil) are offered. The concrete products (roll of film with defined width and length) are models as jobs inside this group.

NOTE: Examples for different combinations of jobs are presented in the Annex.

8.1 JobGroups

This is a container for the job groups.

8.1.1 NodeVersion

The NodeVersion Property as defined in OPC 10000-3 is used to inform the client about model changes. Here it informs about added or removed instances of JobGroupType.

8.1.2 JobGroup_<Nr>

This is a placeholder for the job groups (see 8.2). When instances are created the BrowseNames shall be “JobGroup_<Nr>” where <Nr> is a three-digit number with leading zeros, starting with “001”.

8.1.3 AddJobGroup

This method adds a new job group with the needed Properties.

Signature

	AddJobGroup (
		[in]	0:String	Id
		[in]	0:String	Description
		[in]	0:String	EquipmentDescription
		[in]	0:String	ProductionDatasetName
		[in]	MaterialMappingType[]	MaterialMapping
		[in]	0:UInt32	Priority
		[in]	0:UtcTime	PlannedStart
		[in]	0:Duration	PlannedProductionTime
		[in]	0:Duration	PlannedSetUpTime
		[in]	0:UtcTime	LatestEnd
		[out]	0:NodeId	JobGroupNodeId);

8.1.4 RemoveJobGroupById

This method removes a job group instance.

Signature

	RemoveJobGroupById (
		[in]	0:String	Id);

8.1.5 StartJobGroupById

With this method the client requests to start the production of a specific job group.

Signature

	StartJobGroupById (
		[in]	0:String	Id);

8.1.6 InterruptJobGroupById

With this method the client requests to interrupt the production of a specific job group.

Signature

	InterruptJobGroupById (
		[in]	0:String	Id);

To continue the production of the job group, StartJobGroupById is called.

8.1.7 FinishJobGroupById

With this method the client requests to finish the production of a specific job group.

Signature

	FinishJobGroupById (
		[in]	0:String	Id);

8.1.8 Events

The JobGroups Object fires all Events related to the included job groups and jobs. With this, a client needs to subscribe to these events only at this node. The different events are described in 8.2 and 8.3.

8.2 JobGroupType

This ObjectType represent a job group.

8.2.1 NodeVersion

The NodeVersion Property as defined in OPC 10000-3 is used to inform the client about model changes. Here it informs about added or removed instances of JobType in the group.

8.2.2 Id

Id of the job group.

8.2.3 Description

Description of the job group.

8.2.4 EquipmentDescription

Description of the equipment needed for job. This is only for information (e.g. for operator)

NOTE: It makes sense only to mention the interchangeable equipment of the extrusion line here (e.g. die, screw).

8.2.5 ProductionDatasetName

Name of the production dataset which is needed for the job.

8.2.6 MaterialMapping

Information, which material is needed for the production. The MaterialMappingType is defined in Table 16.

8.2.7 Priority

Priority of the job group: 1 = highest priority, higher values represent lower priorities.

8.2.8 PlannedStart

Planned start of the job (in UTC time). If not relevant the value shall be 0.

8.2.9 PlannedProductionTime

Planned time for the production of the job group. If not relevant the value shall be 0.

8.2.10 PlannedSetUpTime

Planned total time needed for set up and tear down of the extrusion line for the job group. If not relevant the value shall be 0.

8.2.11 LatestEnd

Latest end of the job (in UTC time). If not relevant the value shall be 0.

8.2.12 ConfigurationParameters

Array of offered configuration parameters. The ConfigurationParameterType is defined in OPC 40083. Which ConfigurationParameters are offered to the jobs in the group depends on the machine / implementation / production dataset.

8.2.13 Status

Status of the job group. The JobStatusEnumeration is defined in OPC 40083.

8.2.14 ElectricalEnergyConsumption

Cumulated electrical energy consumption of the extrusion line for the job group in kWh.

8.2.15 FluidEnergyConsumption

Cumulated energy for the cooling of the whole extrusion line with fluid for the job group in kWh.

8.2.16 PressureAirConsumption

Cumulated consumption of pressure air of the whole extrusion line (volume at standard conditions) for the job group in kWh.

8.2.17 Job_<Nr>

This is a placeholder for the jobs inside the group (see 8.3). When instances are created the BrowseNames shall be “Job_<Nr>” where <Nr> is a three-digit number with leading zeros, starting with “001”.

8.2.18 AddJob

This method adds a new job to the group with the needed Properties.

Signature

	AddJob (
		[in]	0:String	Id
		[in]	0:String	Description
		[in]	0:String	CustomerName
		[in]	0:String	ProductName
		[in]	0:String	ProductDescription
		[in]	0:UInt32	Strand
		[in]	0:UInt32	Sequence
		[in]	3:ParameterSettingType[]	ParameterSetting
		[in]	0:Double	SetOutput
		[in]	0:Double	LotSize
		[out]	0:NodeId	JobNodeId);

8.2.19 RemoveJobById

This method removes a job from a group.

Signature

	RemoveJobById (
		[in]	0:String	Id);

8.2.20 StartJobById

With this method the client requests to start the production of a specific job in the group.

Signature

	StartJobById (
		[in]	0:String	Id);

8.2.21 InterruptJobById

With this method the client requests to interrupt the production of a specific job.

Signature

	InterruptJobById (
		[in]	0:String	Id);

To continue the production of the job, StartJobById is called.

8.2.22 FinishJobById

With this method the client requests to finish the production of a specific job.

Signature

	FinishJobById (
		[in]	0:String	Id);

8.2.23 JobGroupStatusChangedEventType

This EventType is used to inform the client about the change of the Status Property of a job group. It is fired by the parent JobGroups object to have only one Node for the subscription.

The SourceNode (part of BaseEventType) shall be the NodeId of the relevant job group.

8.3 JobType

This ObjectType represent a single job inside a job group.

8.3.1 Id

Id of the job. It shall be unique inside the relevant job group. Two jobs inside different job groups may have the same Id.

8.3.2 Description

Description of the job.

8.3.3 CustomerName

Name of the customer for that the job is produced.

8.3.4 ProductId

Id of the product produced by the job.

8.3.5 ProductDescription

Description of the product produced by the job.

8.3.6 Strand

Strand is used when several products (two pipes is parallel, foil cut into several smaller foils) are produced in parallel. When only one product is produced at the same time, the value is always 1.

8.3.7 Sequence

Planned sequence when the job group contains multiple job for one strand. When there is only one job for a string in the production group the value is always 1.

8.3.8 ParameterSetting

Array for the configuration of the job by setting values for the offered configuration parameters. The ParameterSettingType is defined in OPC 40083. If an entry in the ConfigurationParameters Array in the job group has no corresponding entry in the ParameterSetting Array, the default value is used.

8.3.9 SetOutput

Set output of the job. The output is always counted in units, where a unit can be a piece of pipe/profile, roll of film, bag of compound, but also a defined bundle (e.g. one unit consist of 4 bags). What a unit is, may be configurable by the configuration parameters.

8.3.10 LotSize

Size of a production lot. This used to control the

frequency of the Events of LotFinishedEventType (see 8.3.19)

production of different jobs in a group: When LotSize is reached, the next job in the group is produced (see examples in Annex).

8.3.11 Status

Status of the job. The JobStatusEnumeration is defined in OPC 40083.

8.3.12 GoodProduct

Indication if the produced product has a good quality. Can be set by the machine or the operator. When it changes from true to false the line control shall create an alarm.

8.3.13 ActualLot

Which lot (number) is currently in production.

8.3.14 ActualLotName

Optional name for the actual lot.

8.3.15 ActualOutput, ActualGoodOutput, ActualBadOutput, ActualSampleOutput

These Variables represent the total number of produced (finished) units and the numbers of good, bad and test sample units in the current job. (See explanation above for unit in SetOutput.)

8.3.16 ActualOutputRate

Average output rate of the job in units per hour.

8.3.17 JobStatusChangedEventType

This EventType is used to inform the client about the change of the Status Property of a job. It is fired by the JobGroups object to have only one Node for the subscription.

The SourceNode (part of BaseEventType) shall be the NodeId of the relevant job.

8.3.18 UnitFinishedEventType

This EventType is used to inform the client a finished product unit. It is fired by the parent JobGroups object to have only one Node for the subscription.

The SourceNode (part of BaseEventType) shall be the NodeId of the relevant job.

8.3.19 LotFinishedEventType

This EventType is used to inform the client a finished production lot. It is fired by the parent JobGroups object to have only one Node for the subscription.

The SourceNode (part of BaseEventType) shall be the NodeId of the relevant job.

NOTE: The three events JobStatusChanged, UnitFinished and LotFinished may be fired simultaneously. E.g. when a job is finished, then the status is changed, the last product is finished as well as the last lot. If the job is the last in the job group, the JobGroupStatusChanges event will be fired in addition. However, the client decides which EventTypes are subscribed.

9 ProductionDatasetManagement

The ProductionDatasetManagementType is defined in OPC 40083 and provides functionalities for the management of recipes/machine settings.

10 Profiles and Conformance Units

10.1 Conformance Units

This chapter defines the corresponding Conformance Units for OPC 40084-2.

10.2 Profiles

10.2.1 Profile list

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

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 ExtrusionLine_InterfaceType.

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

10.2.2 Server Facets

10.2.2.1 Overview

The following sections specify the Facets available for Servers that implement the OPC 40084-2 companion specification. Each section defines and describes a Facet or Profile.

10.2.2.2 OPC 40084-2 Basic Server Profile

Table 34 defines a Profile that provides the basic functionalities of an extrusion line managed in an OPC UA Server.

10.2.2.3 OPC 40084-2 Basic Server Profile

Table 35 defines a Facet that supports the job management.

11 Namespaces

11.1 Namespace Metadata

Table 36 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 Part 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 Part 5.

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.

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

Table 38 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.

12 (normative)OPC 40084-2 Namespace and mappings

Namespace and identifiers for OPC 40084-2 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 CSV released with this version of the specification can be found here:

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

___________

13 (informative)Examples for job descriptions

This Annex shows possible combinations of job groups and jobs for different applications. While the first example includes a full description of all variables, the other are shortened to highlight the differences.

JobGroup_1:

Job_1:

Because there is only one job in the group, LotSize could also be another value with no effect on the production. Nevertheless, the value defines, after which number of produced product units, a lot finished event (see 8.3.19) will be fired.

JobGroup_1:

First Job_1 is produced completely first, because LotSize = SetOutput.

JobGroup_1:

One piece of Job_1 is produced. Because LotSize = 1 then a piece of Job_2 is produced. As SetOutput is not reached it starts with Job_1 again.

JobGroup_1:

Production in parallel because of different Strands.

JobGroup_1:

JobGroup_1:

JobGroup_1:

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.