1 Scope

This document specifies an OPC UA information model for the representation of a Tightening System. It is mandatory to implement the base specification OPC 40450-1 for Joining Systems for using this specification.

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 and errata) applies

There are no normative references in this document.

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

http://www.opcfoundation.org/documents/10000-1/

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

http://www.opcfoundation.org/documents/10000-2/

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

http://www.opcfoundation.org/documents/10000-3/

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

http://www.opcfoundation.org/documents/10000-4/

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

http://www.opcfoundation.org/documents/10000-5/

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

http://www.opcfoundation.org/documents/10000-6/

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

http://www.opcfoundation.org/documents/10000-7/

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

http://www.opcfoundation.org/documents/10000-8/

OPC 40450-1, OPC UA for Joining Systems - Part 1: Base

http://www.opcfoundation.org/UA/IJT/Base/

3 Terms, definitions and conventions

3.1 Overview

It is assumed that basic concepts of OPC UA information modelling and Joining System Base specification are understood in this specification. This specification will use these concepts to describe the Tightening System Information Model. For the purposes of this document, the terms and definitions given in OPC 10000-1, OPC 10000-3, OPC 10000-4, OPC 10000-5, OPC 10000-7, OPC 40450-1 as well as the following apply.

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

3.2 OPC UA for Tightening System terms

3.3 Abbreviated terms

The terms described in OPC 40450-1 apply.

3.4 Conventions used in this document

The conventions described in OPC 40450-1 apply.

4 General information to IJT Tightening System

4.1 Introduction to Tightening System

The idea of a tightening system is to represent an easy-to-understand entity that can manage tightening processes autonomously, forming single point of contact for external systems.

Usually, a tightening process drives threaded fastener in a counterpart. This is most likely done by the rotation of one of the fastener parts. Hence, there is a tension force applied to the materials, which are meant to get fastened. Hereby the process will be controlled and supervised by the controller. There are numerous parameters and boundaries which may be set and measurements which are taken during the tightening process.

The measurement data and results are of eminent importance for the assessment of the process quality. This data should mostly be made available to higher-level systems.

In addition to the core process of tightening, other supporting functionalities exist in a tightening system. These are, for example, the advance of the bit, socket, or the supply of the fastening elements.

The tightening system should be able to represent the many different forms of systems that exist today and allow freedom to be extended as more become available.

The core asset in a tightening system is a controller which handles the OPC UA communication. The definition of the controller is kept wide by design. It could be a server, a PLC, an embedded processor, etc.

Some of the tightening systems that exist today are:

A physical controller, managing a cable handheld tool and a set of battery handheld tools.

A physical controller managing several wireless tools.

A wireless tool containing a controller.

A controller managing several fixtured spindles.

A controller managing a spindle, a screw feeder and a screw feeder controller mounted on a robot (The robot is not part of the tightening system).

A clutch tool reporting OK/NOT_OK.

A computer system storing and providing historical results or visualizing the information.

4.2 Information Models

The set of models defined in OPC 40451-1 UA CS for Tightening Systems 1.00 are moved to the common base specification OPC 40450-1 for Joining Systems.

5 OPC UA ObjectTypes

5.1 ITighteningToolParametersType InterfaceType Definition

The interface ITighteningToolParametersType is inherited from 0:BaseInterfaceType to add additional parameters of a tool in a tightening system. It shall be added to 2:Parameters object of the tool instance.

DesignType provides information on the design of the Tool.

DriveMethod provides information on the drive method of the motor of the Tool.

DriveType provides information on the drive type of the Tool.

ShutOffMethod provides information on the shutoff method of the tool.

In Table 2, standardized values for the EnumStrings attribute for the above listed variables is defined. Each instance of the following variables Type, DesignType, DriveMethod, DriveType, ShutOffMethod shall follow the defined sequence for the entries.

Note: Servers can add additional entries into the EnumStrings array and may provide translations of the texts in different locales.

MaxTorque is the maximum allowed torque for which the tool may be used for tightening processes.

MinTorque is the minimum allowed torque for which the tool may be used for tightening processes.

MaxSpeed is the maximum rotation speed of the driving shaft.

MotorType is the type of motor in the tool.

6 Profiles and ConformanceUnits

6.1 Conformance Units

This chapter defines the corresponding Conformance Units for the OPC UA Information Model for Tightening System.

6.2 Profiles

6.2.1 Profile list

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

6.2.2 Server Facets

6.2.2.1 IJT Basic Tightening System Server Facet

Table 5 defines a Facet that describes the basic tightening system.

6.2.2.2 IJT General Tightening System Server Facet

Table 6 defines a Facet that describes the general tightening system.

6.2.2.3 IJT Tightening System Selectable Features Server Facet

Table 7 defines a Facet that describes the tightening system with selectable features.

7 Namespaces

7.1 Namespace Metadata

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

Note: The IsNamespaceSubset Property is set to False as the UaNodeSet XML file contains the complete Namespace. Servers only exposing a subset of the Namespace need to change the value to True.

7.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 9 provides a list of mandatory and optional namespaces used in an OPC UA for Tightening Systems Server.

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

8 (normative)OPC UA for Tightening Systems Namespace and mappings

NodeSet and supplementary files for OPC UA for Tightening Systems Information Model

The OPC UA for Tightening Systems Information Model is identified by the following URI:

http://opcfoundation.org/UA/IJT/Tightening/

Documentation for the NamespaceUri can be found here.

The NodeSet associated with this version of specification can be found here:

https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/IJT/Tightening/&v=2.00.1&i=1

The NodeSet associated with the latest version of the specification can be found here:

https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/IJT/Tightening/&i=1

Supplementary files for the OPC UA for Tightening Systems Information Model can be found here:

https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/IJT/Tightening/&v=2.00.1&i=2

The files associated with the latest version of the specification can be found here:

https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/IJT/Tightening/&i=2

Capability Identifier

The capability identifier for this document shall be:

IJT_TIGHTENING

___________

Agreement of Use

COPYRIGHT RESTRICTIONS

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

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

PATENTS

The attention of adopters is directed to the possibility that compliance with or adoption of OPC or VDMA specifications may require use of an invention covered by patent rights. OPC Foundation or VDMA shall not be responsible for identifying patents for which a license may be required by any OPC or VDMA specification, or for conducting legal inquiries into the legal validity or scope of those patents that are brought to its attention. OPC or VDMA 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 VDMA 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 VDMA 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 VDMA 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 VDMA 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.

ISSUE REPORTING

If an error or problem is found in this specification, the UaNodeSet, or any associated supplementary files, it should be reported as an issue.

The reporting process can be found here: https://opcfoundation.org/resources/issue-tracking/

The Link to the issue tracking project for this document is here:

https://mantis.opcfoundation.org/set_project.php?project_id=179&make_default=no