1 Scope

This document specifies an OPC UA information model for the representation of a Joining System. This system can consist of Controllers, Tools, Servos, Memory Devices, Sensors, Cables, Batteries, Power Supplies, Feeders, Accessories, Software Components, and other Subcomponents. The aim of this specification is to obtain an interoperable interface for higher-level control and evaluation systems.

It focuses on joining systems and their components as assets and the monitoring of those systems and components, considering existing and emerging standards in these areas, like OPC UA for Device Integration, OPC UA for Machinery Basic Building Blocks, OPC UA for Machinery Result Transfer, OPC UA for Asset Management Basics, etc.

This version of the specification focuses on Asset Management, Condition Monitoring, Result Management, Event Management, Joining Process Management and Joint Management.

All the types defined in this specification can be extended for vendor, customer, or application specific use cases outside of 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

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 10000-9, OPC Unified Architecture - Part 9: Alarms and Conditions

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

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

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

OPC 10000-110, OPC Unified Architecture - Part 110: Asset Management Basics

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

OPC 10000-200, OPC Unified Architecture - Part 200: Industrial Automation

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

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

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

OPC 40001-101, OPC UA for Machinery - Part 101: Result Transfer

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

NAMUR Recommendation NE107: Self-monitoring and diagnosis of field devices

VDI-VDE 2862-2: Minimum requirements for application of fastening systems and tools

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 Joining 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 10000-8, OPC 10000-9, OPC 10000-100, OPC 10000-110, OPC 10000-200 OPC 40001-1, OPC 40001-101 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 Joining System terms

3.3 Abbreviated terms

3.4 Conventions used in this document

3.4.1 Conventions for Node descriptions

3.4.1.1 Node definitions

Node definitions are specified using tables (see Table 2).

Attributes are defined by providing the Attribute name and a value, or a description of the value.

References are defined by providing the ReferenceType name, the BrowseName of the TargetNode and its NodeClass.

If the TargetNode is a component of the Node being defined in the table the Attributes of the composed Node are defined in the same row of the table.

The DataType is only specified for Variables; “[<number>]” indicates a single-dimensional array, for multi-dimensional arrays the expression is repeated for each dimension (e.g. [2][3] for a two-dimensional array). For all arrays the ArrayDimensions is set as identified by <number> values. If no <number> is set, the corresponding dimension is set to 0, indicating an unknown size. If no number is provided at all the ArrayDimensions can be omitted. If no brackets are provided, it identifies a scalar DataType and the ValueRank is set to the corresponding value (see OPC 10000-3). In addition, ArrayDimensions is set to null or is omitted. If it can be Any or ScalarOrOneDimension, the value is put into “{<value>}”, so either “{Any}” or “{ScalarOrOneDimension}” and the ValueRank is set to the corresponding value (see OPC 10000-3) and the ArrayDimensions is set to null or is omitted. Examples are given in Table 1.

The TypeDefinition is specified for Objects and Variables.

The TypeDefinition column specifies a symbolic name for a NodeId, i.e. the specified Node points with a HasTypeDefinition Reference to the corresponding Node.

The ModellingRule of the referenced component is provided by specifying the symbolic name of the rule in the ModellingRule column. In the AddressSpace, the Node shall use a HasModellingRule Reference to point to the corresponding ModellingRule Object.

If the NodeId of a DataType is provided, the symbolic name of the Node representing the DataType shall be used.

Note that if a symbolic name of a different namespace is used, it is prefixed by the NamespaceIndex (see 3.4.2.2).

Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType, their NodeClass and their BrowseName are specified. A reference to another part of this document points to their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and ModellingRule columns may be omitted and only a Comment column is introduced to point to the Node definition.

Each Type Node or well-known Instance Node defined shall have one or more ConformanceUnits defined in 11.1 that require the Node to be in the AddressSpace.

The relations between Nodes and ConformanceUnits are defined at the end of the tables defining Nodes, one row per ConformanceUnit. The ConformanceUnits are reflected in the Category element for the Node definition in the UANodeSet (see OPC 10000-6).

The list of ConformanceUnits in the UANodeSet allows Servers to optimize resource consumption by using a list of supported ConformanceUnits to select a subset of the Nodes in an Information Model.

When a Node is selected in this way, all dependencies implied by the References are also selected.

Dependencies exist if the Node is the source of HasTypeDefinition, HasInterface, HasAddIn or any HierarchicalReference. Dependencies also exist if the Node is the target of a HasSubtype Reference. For Variables and VariableTypes, the value of the DataType Attribute is a dependency. For DataType Nodes, any DataTypes referenced in the DataTypeDefinition Attribute are also dependencies.

For additional details see OPC 10000-5.

Components of Nodes can be complex that is containing components by themselves. The TypeDefinition, NodeClass and DataType can be derived from the type definitions, and the symbolic name can be created as defined in 3.4.3.1. Therefore, those containing components are not explicitly specified; they are implicitly specified by the type definitions.

The Other column defines additional characteristics of the Node. Examples of characteristics that can appear in this column are show in Table 3.

If multiple characteristics are defined they are separated by commas. The name or the short name may be used.

3.4.1.2 Additional References

To provide information about additional References, the format as shown in Table 4 is used.

References can be to any other Node.

3.4.1.3 Additional sub-components

To provide information about sub-components, the format as shown in Table 5 is used.

3.4.1.4 Additional Attribute values

The type definition table provides columns to specify the values for required Node Attributes for InstanceDeclarations. To provide information about additional Attributes, the format as shown in Table 6 is used.

There can be multiple columns to define more than one Attribute.

3.4.2 NodeIds and BrowseNames

3.4.2.1 NodeIds

The NodeIds of all Nodes described in this standard are only symbolic names. Annex A defines the actual NodeIds.

The symbolic name of each Node defined in this document is its BrowseName, or, when it is part of another Node, the BrowseName of the other Node, a “.”, and the BrowseName of itself. In this case “part of” means that the whole has a HasProperty or HasComponent Reference to its part. Since all Nodes not being part of another Node have a unique name in this document, the symbolic name is unique.

The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex for this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table.

Note that this document not only defines concrete Nodes, but also requires that some Nodes shall be generated, for example one for each Session running on the Server. The NodeIds of those Nodes are Server-specific, including the namespace. But the NamespaceIndex of those Nodes cannot be the NamespaceIndex used for the Nodes defined in this document, because they are not defined by this document but generated by the Server.

3.4.2.2 BrowseNames

The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes. The NamespaceUri for all BrowseNames defined in this document is defined in 12.2.

For InstanceDeclarations of NodeClass Object and Variable that are placeholders (OptionalPlaceholder and MandatoryPlaceholder ModellingRule), the BrowseName and the DisplayName are enclosed in angle brackets (<>) as recommended in OPC 10000-3.

If the BrowseName is not defined by this document, a namespace index prefix is added to the BrowseName (e.g., prefix '0' leading to ‘0:EngineeringUnits’ or prefix '2' leading to ‘2:DeviceRevision’). This is typically necessary if a Property of another specification is overwritten or used in the OPC UA types defined in this document. Table 277 provides a list of namespaces and their indexes as used in this document.

3.4.3 Common Attributes

3.4.3.1 General

The Attributes of Nodes, their DataTypes and descriptions are defined in OPC 10000-3. Attributes not marked as optional are mandatory and shall be provided by a Server. The following tables define if the Attribute value is defined by this specification or if it is server-specific.

For all Nodes specified in this specification, the Attributes named in Table 7 shall be set as specified in the table.

3.4.3.2 Objects

For all Objects specified in this specification, the Attributes named in Table 8 shall be set as specified in the table. The definitions for the Attributes can be found in OPC 10000-3.

3.4.3.3 Variables

For all Variables specified in this specification, the Attributes named in Table 9 shall be set as specified in the table. The definitions for the Attributes can be found in OPC 10000-3.

3.4.3.4 VariableTypes

For all VariableTypes specified in this specification, the Attributes named in Table 10 shall be set as specified in the table. The definitions for the Attributes can be found in OPC 10000-3.

3.4.3.5 Methods

For all Methods specified in this specification, the Attributes named in Table 11 shall be set as specified in the table. The definitions for the Attributes can be found in OPC 10000-3.

3.4.4 Structures

OPC 10000-3 differentiates between different kinds of Structures. The following conventions explain, how these Structures shall be defined.

The first kind are Structures without optional fields where none of the fields allows subtype (except fields with abstract DataTypes). Its definition is in Table 12.

The second kind are Structures with optional fields where none of the fields allows subtypes (except fields with abstract DataTypes). Its definition is in Table 13.

Structures with fields that are optional have an “Optional” column. Fields that are optional have True set, otherwise False.

The third kind are Structures without optional fields where one or more of the fields allow subtypes. Its definition is in Table 14.

Structures with fields that allow subtypes have an “Allow Subtypes” column. Fields that allow subtypes have True set, otherwise False. Fields with abstract DataTypes can always be subtyped.

4 General information to Industrial Joining Technologies and OPC UA

4.1 Introduction to Industrial Joining Technologies (IJT)

This is a working group under VDMA Integrated Assembly Solutions department. The purpose of the IJT group is to define data models and data access standards for various joining techniques such as Tightening, Gluing, Riveting, Flow Drill Fastening, etc.

Assembling products by joining parts together is a key operation in many industries. There are obviously countless differences between gluing, welding, riveting, etc., but also surprisingly many characteristics are common as given below:

There is often a tool that executes the joining.

There are often some devices controlling the joining process such as a processor, computer, or PLC.

There is often a program of some sort that governs the joining process.

There is often a digital result of the joining process that may both influence the overlying assembly process and be stored to provide product traceability.

There could be an operator guidance system to help the operator determine the steps involved in the joining process.

There could be a representation of the joint as part of the digital twin of the product being assembled.

There is often a need from external systems to select or influence the joining operation, such an MES system, a station PLC, location system, or a barcode scanner.

The Industrial Joining Technologies companion specification endeavors to find the best balance between the models used in all joining technologies and the models specific to an area.

Joining is often tightly connected with other industrial processes such as vision (for identification), or robotics (for location), so special attention has been on harmonization with other VDMA companion specifications, to strive for seamless integration from a customer’s perspective.

Every joining technique could define their own standard specification where the common types defined in the base specification will be re-used across the joining techniques.

Examples: Result Management, Asset Management, Event Management, Joining Process Management, Joint Management, etc. are common use cases for multiple joining technologies.

The following figure describes the taxonomy of the Industrial Joining Technologies workgroup.

4.2 Joining System

The idea of a joining system is to represent different types of systems for each joining technique using a common interface.

Examples: Tightening, Riveting, Gluing, etc.

4.3 Introduction to OPC Unified Architecture

4.3.1 What is OPC UA?

OPC UA is an open and royalty free set of standards designed as a universal communication protocol. While there are numerous communication solutions available, OPC UA has key advantages:

A state of art security model (see OPC 10000-2).

A fault tolerant communication protocol.

An information modelling framework that allows application developers to represent their data in a way that makes sense to them.

OPC UA has a broad scope which delivers for economies of scale for application developers. This means that a larger number of high-quality applications at a reasonable cost are available. When combined with semantic models such as OPC UA for Joining Systems, OPC UA makes it easier for end users to access data via generic commercial applications.

The OPC UA model is scalable from small devices to ERP systems. OPC UA Servers process information locally and then provide that data in a consistent format to any application requesting data - ERP, MES, PMS, Maintenance Systems, HMI, Smartphone or a standard Browser, for examples. For a more complete overview see OPC 10000-1.

4.3.2 Basics of OPC UA

As an open standard, OPC UA is based on standard internet technologies, like TCP/IP, HTTP, Web Sockets.

As an extensible standard, OPC UA provides a set of Services (see OPC 10000-4) and a basic information model framework. This framework provides an easy manner for creating and exposing vendor defined information in a standard way. More importantly all OPC UA Clients are expected to be able to discover and use vendor-defined information. This means OPC UA users can benefit from the economies of scale that come with generic visualization and historian applications. This specification is an example of an OPC UA Information Model designed to meet the needs of developers and users.

OPC UA Clients can be any consumer of data from another device on the network to browser based thin clients and ERP systems. The full scope of OPC UA applications is shown in Figure 2.

OPC UA provides a robust and reliable communication infrastructure having mechanisms for handling lost messages, failover, heartbeat, etc. With its binary encoded data, it offers a high-performing data exchange solution. Security is built into OPC UA as security requirements become more and more important especially since environments are connected to the office network or the internet and attackers are starting to focus on automation systems.

4.3.3 Information modelling in OPC UA

4.3.3.1 Concepts

OPC UA provides a framework that can be used to represent complex information as Objects in an AddressSpace which can be accessed with standard services. These Objects consist of Nodes connected by References. Different classes of Nodes convey different semantics. For example, a Variable Node represents a value that can be read or written. The Variable Node has an associated DataType that can define the actual value, such as a string, float, structure etc. It can also describe the Variable value as a variant. A Method Node represents a function that can be called. Every Node has a number of Attributes including a unique identifier called a NodeId and non-localized name called as BrowseName. An Object representing a ‘Reservation’ is shown in Figure 3.

Object and Variable Nodes represent instances and they always reference a TypeDefinition (ObjectType or VariableType) Node which describes their semantics and structure. Figure 4 illustrates the relationship between an instance and its TypeDefinition.

The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure 4 the PersonType ObjectType defines two children: First Name and Last Name. All instances of PersonType are expected to have the same children with the same BrowseNames. Within a type the BrowseNames uniquely identify the children. This means Client applications can be designed to search for children based on the BrowseNames from the type instead of NodeIds. This eliminates the need for manual reconfiguration of systems if a Client uses types that multiple Servers implement.

OPC UA also supports the concept of sub-typing. This allows a modeller to take an existing type and extend it. There are rules regarding sub-typing defined in OPC 10000-3, but in general they allow the extension of a given type or the restriction of a DataType. For example, the modeller may decide that the existing ObjectType in some cases needs an additional Variable. The modeller can create a subtype of the ObjectType and add the Variable. A Client that is expecting the parent type can treat the new type as if it was of the parent type. Regarding DataTypes, subtypes can only restrict. If a Variable is defined to have a numeric value, a sub type could restrict it to a float.

References allow Nodes to be connected in ways that describe their relationships. All References have a ReferenceType that specifies the semantics of the relationship. References can be hierarchical or non-hierarchical. Hierarchical references are used to create the structure of Objects and Variables. Non-hierarchical are used to create arbitrary associations. Applications can define their own ReferenceType by creating subtypes of an existing ReferenceType. Subtypes inherit the semantics of the parent but may add additional restrictions. Figure 5 depicts several References, connecting different Objects.

The figures above use a notation that was developed for the OPC UA specification. The notation is summarized in Figure 6. UML representations can also be used; however, the OPC UA notation is less ambiguous because there is a direct mapping from the elements in the figures to Nodes in the AddressSpace of an OPC UA Server.

A complete description of the different types of Nodes and References can be found in OPC 10000-3 and the base structure is described in OPC 10000-5.

OPC UA specification defines a very wide range of functionality in its basic information model. It is not required that all Clients or Servers support all functionality in the OPC UA specifications. OPC UA includes the concept of Profiles, which segment the functionality into testable certifiable units. This allows the definition of functional subsets (that are expected to be implemented) within a companion specification. The Profiles do not restrict functionality, but generate requirements for a minimum set of functionality (see OPC 10000-7)

4.3.3.2 Namespaces

OPC UA allows information from many different sources to be combined into a single coherent AddressSpace. Namespaces are used to make this possible by eliminating naming and id conflicts between information from different sources. Each namespace in OPC UA has a globally unique string called a NamespaceUri which identifies a naming authority and a locally unique integer called a NamespaceIndex, which is an index into the Server's table of NamespaceUris. The NamespaceIndex is unique only within the context of a Session between an OPC UA Client and an OPC UA Server- the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed. The Services defined for OPC UA use the NamespaceIndex to specify the Namespace for qualified values.

There are two types of structured values in OPC UA that are qualified with NamespaceIndexes: NodeIds and QualifiedNames. NodeIds are locally unique (and sometimes globally unique) identifiers for Nodes. The same globally unique NodeId can be used as the identifier in a node in many Servers – the node's instance data may vary but its semantic meaning is the same regardless of the Server it appears in. This means Clients can have built-in knowledge of what the data means in these Nodes. OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model.

QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames; however, instances do not have that restriction.

4.3.3.3 Companion Specifications

An OPC UA companion specification for an industry specific vertical market describes an Information Model by defining ObjectTypes, VariableTypes, DataTypes and ReferenceTypes that represent the concepts used in the vertical market, and potentially also well-defined Objects as entry points into the AddressSpace.

5 Use cases

The use cases defined below are applicable to one or more roles in each factory or plant. Examples: Service technician, plant manager, quality engineer, machine integrator, factory planner, IT manager, etc.

5.1 Asset Management

5.2 Condition Monitoring

5.3 Result Management

5.4 Event Management

5.5 Joint Management

5.6 Joining Process Management

6 OPC UA Joining System Information Model Overview

6.1 Joining System

A joining system is a container to group set of information and methods into a logic unit.

Each joining system consists of various modules for Asset Management, Result Management, Joining Process Management, Joint Management and respective Events and Alarms. Each of the modules provides a set of methods for external systems to interact with the joining system.

6.2 Asset Management

Asset Management is a container to group a set of assets and the respective methods.

6.2.1 Assets

Assets is a container which provides all the assets in a joining system described in the following sections.

6.2.1.1 Overview

The assets are modelled using the generic object declaration BaseObjectType place holders to ensure interoperability from various other domain specifications.

This specification defines a set of interfaces for each type of asset and asset instances can be implemented by including the required interfaces defined in this specification. The asset instances can also be modelled by external interfaces from other companion specifications or vendor specific extensions with the help of open generic model.

Note: For Accessories and SubComponents, there can be other companion specifications (Example: Stack light) and these models could be implemented at instance level since the assets are modelled as BaseObjectType placeholders.

This version of the specification is limited to assets which can expose data.

6.2.1.2 Controllers

This is a container for the set of controllers in the system.

A controller can represent an entity that can control an aspect of the joining process. A controller can also be any kind of supervisory instance, which manages multiple tools. So, controller can be any kind of computation device which controls specific parts of the joining system and communicates to another system. A joining system may consist of multiple controller instances. The first controller in the list is intended to harbor the OPC UA communication for the Joining System information model.

6.2.1.3 Tools

This is a container for the set of tools in the system.

A tool represents a physical device that joins parts together. It can for example be a tool held by a human being, spindle attached to a robot or be part of a tool fixture.

Note: Spindle is a common term used in a fixtured system to represent a specific type of Tool.

6.2.1.4 Servos

This is a container for the set of servos in the system.

A servo amplifier represents a physical device that controls the motor in the tool. It is the physical power stage to deliver the power to the motor to perform the joining or some other movement in the system.

6.2.1.5 MemoryDevices

This is a container for the set of memory devices in the system.

A MemoryDevice (or Storage Device) stores data, such as, the system identity, the software of the system, licenses, joining programs, etc.

Those memory devices may be implemented, for example like memory cards or memory modules. Those are used to store data also during the power off phase of the device.

6.2.1.6 Sensors

This is a container for the set of sensors in the system.

A sensor is a physical device whose measurements can be transformed and processed within a given system.

Each sensor is responsible for one measurement signal. Therefore, it measures one quantity and delivers the value by doing so.

The sensor data may be used in the system to perform the joining but also can deliver other information of the system.

Besides the measured quantity the sensor may expose its calibration information, which may be useful for quality assessment.

6.2.1.7 Cables

This is a container for the set of cables in the system.

Cables interconnect certain parts of the system. Example: Cable from a tool to a controller.

Note: Cables are only modelled in the system if the required information can be provided by the system.

6.2.1.8 Batteries

This is a container for the set of batteries in the system.

Battery is a physical device which stores and provides energy to the required system.

Note: Batteries are only modelled in the system if the required information can be provided by the system.

6.2.1.9 PowerSupplies

This is a container for the set of power supplies in the system.

A power supply is a physical device which typically transforms or delivers power.

6.2.1.10 Feeders

This is a container for the set of feeders in the system.

A feeder supplies the material for the joining process. It may stock fasteners and separate the elements and makes them available at the joint position.

Examples: Bunker, bowl feeder, step feeder, etc.

6.2.1.11 Accessories

This is a container for the set of accessories in the system.

Accessory represents a physical device mounted on the tool or in the station to help understand or influence the workflow.

Examples: Stack lights, socket selectors, screens, scanners, location tags, reaction bars, operator panel, etc.

6.2.1.12 SubComponents

This is a container for the list of subcomponents in the system.

A subcomponent is a system-specific part that can be plug-in or permanently installed and enables the joining system to perform a specific task.

Note: These are the type of assets which cannot be modelled by the other assets defined in this specification.

Examples: Radio modules, fieldbus modules, etc.

6.2.1.13 SoftwareComponents

This is a container for the list of software in the system.

A software component is a system-specific software asset that can be part of any physical asset.

6.2.1.14 VirtualStations

This is a container for the list of virtual stations in the system.

A virtual station is a system-specific abstraction which can be used to group and manage processes and physical assets.

6.3 Condition Monitoring

The data related to condition monitoring is provided as part of the asset information model. Refer section 7.3.2 for details.

6.4 Event Management

This specification defines standard payload and classification for an event or condition from a joining system. Refer section 8 for details.

6.5 Result Management

Result is the outcome of the joining operation.

Joining Result includes optional elements such as step results, traces, errors, and additional information to reference the related objects like joining processes, joints, assets, etc.

The joining system can send a single result, or a group of results to evaluate the outcome of a joining process.

Note:

The Result Management model extends the model from OPC 40001-101 – Machinery Result Transfer specification.

For the systems which do not support multiple steps in a joining process, Result can be modelled as a single step.

6.6 Joining Process Management

It provides a standardized way to manage joining processes in a joining system by defining a generic container for various joining processes and set of methods to interact with the joining system.

6.7 Joint Management

It provides a standardized way to manage joints handled by the joining system by using a joint model and set of methods to interact with the joining system.

7 OPC UA ObjectTypes

7.1 JoiningSystemType ObjectType definition

7.1.1 Overview

The JoiningSystemType provides the overview of the information exposed from a given joining system.

Note:

An instance of the JoiningSystemType does not represent a specific asset. It is a container which represents an entry point for assets, results, etc. in the joining system.

An instance of a JoiningSystemType can be associated with other joining systems using AssociatedWith or any other reference type. It can be useful when there is an aggregation of multiple joining systems.

It is formally defined in Table 15.

7.1.2 JoiningSystemType definition

The 2:Identification Object provides identification parameters of the joining system.

The AssetManagement Object is an instance of 2:FunctionalGroupType to group assets and related objects in the joining system.

The ResultManagement Object is an instance of JoiningSystemResultManagementType which provides mechanisms to access results generated by the joining system.

The JoiningProcessManagement Object is an instance of JoiningProcessManagementType which provides mechanisms to manage joining processes in the joining system.

The JointManagement Object is an instance of JointManagementType which provides mechanisms to manage joint and associated information.

4:MachineryBuildingBlocks contains building blocks from OPC UA for Machinery.

The components of the JoiningSystemType have additional subcomponents which are defined in Table 16.

2:MethodSet Object is an instance of JoiningSystemAssetMethodSetType which provides set of methods for various assets in a joining system.

The components of the JoiningSystemType have additional subcomponents which are defined in Table 17.

The components of the JoiningSystemType have additional subcomponents which are defined in Table 18.

The components of the JoiningSystemType have additional subcomponents which are defined in Table 19.

7.2 JoiningSystemIdentificationType ObjectType Definition

The JoiningSystemIdentificationType provides the identification parameters of the joining system and is formally defined in Table 20.

The component Variables of the JoiningSystemIdentificationType have additional Attributes defined in Table 21.

2: ProductInstanceUri  is a globally unique resource identifier provided by the manufacturer.

Name is the name of the joining system. It is allowed to set it as the string part of the standard browse name of the instance of JoiningSystemType.

IntegratorName is the name of the system integrator.

Description is the description of the system which could be written by the customer to identify the system. It could be the purpose of the system in the assembly line.

Note: Although there is a description attribute at the node level in OPC UA, the Description property was added at the same level as the 2:Identification node for consistency.

JoiningTechnology is a human-readable text to identify the joining technology of the joining system.

2:Manufacturer provides a human-readable, localized name of the joining system manufacturer.

2:ManufacturerUri provides a unique identifier for this company. This identifier should be a fully qualified domain name; however, it may be a GUID or similar construct that ensures global uniqueness.

2:Model provides the type of the joining system. Examples: Fixtured System, Handheld System, etc.

SystemId is the system integrator specific identifier for the system. It represents a reference to the manufacturer's ERP system.

4:Location is the location of the given system in the given plant or factory in text format.

7.3 Joining System Asset Overview

7.3.1 Overview

7.3.2 IJoiningSystemAssetType InterfaceType Definition

This is a generic interface common for all assets in the Joining System. The purpose of this interface is to provide the common information (Example: Identification, Health, Maintenance, etc.) of all the assets in a standardized way.

This interface has a standard MachineryItemIdentificationType add-in which can be assigned with MachineIdentificationType or MachineryComponentIdentificationType for an asset based on the requirement of the system.

Note: In a Joining System, Controller and Tool instances are generally considered as Machines and other assets can be modelled as components.

To determine if an asset is classified as Machine or Component is flexible and that is achieved using base add-in from OPC UA for Machinery specification MachineryItemIdentificationType which can be specialized using MachineIdentificationType or MachineryComponentIdentificationType.

The 2:Identification Object includes parameters from MachineryItemIdentificationType (which can be specialized to MachineIdentificationType or MachineryComponentIdentificationType) defined in .OPC 40001-1 It also implements IJoiningAdditionalInformationType.

The components of the IJoiningSystemAssetType have additional subcomponents which are defined in Table 23.

The 2:Identification Object, using the standardized name defined in OPC 10000-100, provides identification information about the asset. This is a mandatory place holder and any asset inheriting IJoiningSystemAssetType will replace it with MachineIdentificationType or MachineryComponentIdentificationType.

The 2:Identification Object implements IJoiningAdditionalInformationType interface with the following properties:

Description is the system specific description of the asset.

Note: Although there is a description attribute at the node level in OPC UA, the Description property was added at the same level as the 2:Identification node for consistency.

JoiningTechnology is a human readable text to identify the joining technology.

SupplierCode is the SAP or ERP Supplier Code of the asset.

The Health Object is an instance of 2:FunctionalGroupType to group health related parameters for all the assets in a Joining System. The parameters for Health Object are described below.

Note: The Health Object is obsolete and upgraded based on the Machinery Base Specification. The following parameters are recommended to be accessed using 4:Monitoring/Health object.

2: DeviceHealth  indicates the status as defined by NAMUR Recommendation NE107. Clients can read or monitor this Variable to determine the device condition.

ErrorMessage is the user readable text of the error reported by the given asset.

ErrorTimestamp is the timestamp when the error occurred in the given asset.

ErrorCode is the system specific code for the error that occurred.

Temperature is the measured temperature of the asset.

The 2:OperationCounters Object is an instance of 4:MachineryOperationCounterType which provides information about the duration something is turned on and how long it performs an activity. The parameters for 2:OperationCounters Object are defined in OPC 40001-1.

Note: The data type of 2:OperationCycleCounter is 0:UInteger and it is recommended to use 0:UInt64 for instances of an asset in a joining system.

The 4:LifetimeCounters Object is an instance of 4:MachineryLifetimeCounterType which provides an entry point to various lifetime variables.

The <LifetimeVariable > can be used for any kind of lifetime variables.

The Maintenance Object is an instance of 2:FunctionalGroupType to group maintenance related parameters for the given asset in a Joining System. It has the following objects described below:

The Service Object provides a set of parameters related to the service operations performed on a given asset.

The Calibration Object provides a set of parameters related to the calibration operations performed on a given asset.

The parameters for the Service Object are described below.

LastService is the date when the last service was completed.

ServicePlace is the location where the last service was completed.

Note: LastService and ServicePlace should have the initial operation date and the place for new assets.

NextService is the date of the next planned service.

ServiceCycleSpan is the maximum allowed number of cycles between two services.

ServiceCycleCount is the total cycle counter since the last service.

NumberOfServices is the total number of services taken place.

ServiceReminderDays is the number of days before a service reminder should be sent.

RemainingCycles is the remaining cycles before the service or maintenance. It can go negative if a service is skipped to indicate overshoot cycles.

ServiceReminderCycles is the configured threshold for the number of remaining cycles before the service reminder is sent. This is calculated based on the RemainingCycles.

Example: If ServiceReminderCycles <= RemainingCycles, then a service reminder is sent.

ServiceOperationCycles is the value of the 2:OperationCycleCounter when the last service was performed.

The parameters for Calibration Object are described below.

CalibrationValue is the configured value of the calibration.

LastCalibration is the date when the last calibration was completed.

CalibrationPlace is the location where the last calibration was completed.

NextCalibration is the date of the next planned calibration.

SensorScale is the nominal scale of the sensor. It corresponds also with the measurement range of the sensor.

CertificateUri contains the URI of a certificate of the calibration target in case the calibration target is certified and the information available. Otherwise, the Variable should be omitted. The String shall be a URI as defined by RFC 3986. Example: MCE test document.

The Parameters Object is an instance of 0:FolderType to group set of common parameters of an asset in a joining system. It has the following parameters described below:

Enabled indicates if a given asset is enabled or disabled. It can change by the EnableAsset method or by some other external interface.

Connected indicates if a given asset is connected or disconnected. It can change by DisconnectAsset method or by some other external interface.

IOSignals is an array of signals available for the asset.

Note: The Parameters Object is overridden for the specific assets and contains a set of additional parameters of the given asset.

The MachineryBuildingBlocks contains building blocks from OPC UA for Machinery.

The 4:Monitoring Object is an instance of 4:MonitoringType which provides a base structure for monitoring information of an asset. It provides some sub-structures for grouping different monitoring information. It contains the following sub-structures:

4:Status is the entry point for status information of the asset. If this Object is provided, and the MachineryItemState is provided, it shall be referenced. If this Object is provided and the MachineryOperationMode is provided, it shall be referenced.

4:Health is the entry point of health information of the asset.

Note: This is the commended entry point for health information of the asset.

4:Process is the entry point for process information of the asset.

4:Consumption is the entry point for consumption information of the asset.

The 4:Notifications Object is an instance of 4:NotificationsType which provides the entry point into notifications of an asset. It allows to provide such notifications as Events by becoming an EventNotifier or providing specific Objects for notifications. This specification does not define any specific EventTypes or other ObjectTypes for notifications but just the base infrastructure.

7.3.3 IJoiningAdditionalInformationType InterfaceType Definition

The IJoiningAdditionalInformationType provides additional parameters for 2:Identification of a given asset and is formally defined in Table 24.

Note: The descriptions of the following properties are given in section 7.3.2.

7.3.4 IControllerType InterfaceType Definition

The components of the IControllerType have additional subcomponents which are defined in Table 26.

Type is the classification of a Controller. In Table 27, standardized values for EnumStrings are defined. Each instance of this type 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.

The descriptions for EnumStrings values corresponding to Type are given below:

OTHER

SUPERVISORY_CONTROLLER is a controller which is not executing the process or moving actuators. It manages other controllers and may be a node or hub to other controllers.

PLC is a Programmable Logic Controller which executes a sequence of operations. Examples would be part handling, providing fasteners, managing bit strokes.

COMPUTER is an information processing unit such as a PC.

JOINING_PROCESS_CONTROLLER is controller which is handling the joining process. It performs the joining and publishes its results.

COMMUNICATION_CONTROLLER is a controller which is mainly in charge of handling communications.

FEEDING_CONTROLLER is a controller which performs the fastener flow and provides the fastening elements.

7.3.5 IToolType InterfaceType Definition

It is a generic interface for any type of tool for various joining technologies. Examples: Tightening Tool, Gluing Applicator, etc.

Note: The respective joining technology specifications can define a sub-type of this interface for additional properties.

The components of the IToolType have additional subcomponents which are defined in Table 29.

Type is the classification of a Tool.

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

7.3.6 IServoType InterfaceType Definition

The components of the IServoType have additional subcomponents which are defined in Table 32.

NodeNumber is the node identifier in multiple configurations. Examples: Cabinet with one controller and multiple servo/modules.

7.3.7 IMemoryDeviceType InterfaceType Definition

The components of the IMemoryDeviceType have additional subcomponents which are defined in Table 34.

Type is the type of memory device. It may define the form factor, interface, or technology. Examples: Flash, CFAST, USB, etc.

Note: Memory or storage devices can be classified based on various factors. Hence an open string is provided to make it generic.

StorageCapacity is the static information on the size of the storage in Bytes.

UsedSpace is the static information on the size of the used space in Bytes.

7.3.8 ISensorType InterfaceType Definition

The components of the ISensorType have additional subcomponents which are defined in Table 36.

Type is the classification of a Sensor. In Table 37, standardized values for the EnumStrings are defined. Each instance of this type 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.

OverloadCount is the number of overloads of the sensor, where the permissible load of the sensor was exceeded.

MeasuredValue is the actual measured value reported from a sensor.

Note: An instance of Sensor can be referenced to a respective Calibration Target which was used to calibrate the sensor. The standard models for Calibration Targets are defined in OPC 10000-200.

7.3.9 ICableType InterfaceType Definition

The components of the ICableType have additional subcomponents which are defined in Table 39.

Type is the classification of the cable.

In Table 40, standardized values for the EnumStrings are defined. Each instance of this type 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.

CableLength is the length of the cable.

7.3.10 IBatteryType InterfaceType Definition