1 Scope

This document specifies an OPC UA Information Model for the representation of textile testing devices. The companion specification “OPC UA for Textile Testing Devices” aims for a straightforward integration of different kinds of textile testing devices into MES and other IT systems. The purpose of OPC UA Information Model is to describe the information that is transferred from and to testing instruments for fibres and yarns, e.g. in the spinning industry, in research institutes, quality control laboratories or for production control in industrial environments.

The target of this specification is to provide a standardized interface for textile testing devices from different manufacturers to ensure compatibility. Online testing devices are not within the scope of this companion specification.

The following functionalities for a textile testing device are covered:

General information about the textile testing device (e.g.: identification parameters)

Current configuration and status of the textile testing device

Recipe management (transfer of recipes (testconditions and instructions) to/from the testing device)

Result management (transfer of the generated test results to the MES or other IT-systems)

Job management (information about the jobs running on the device and methods to interact)

KPI and statistics

Logbook of relevant changes on the machine

Maintenance, events and notifications for upcoming user interactions and error handling on the testing device

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-11, OPC Unified Architecture - Part 11: Historical Access

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

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

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

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 10031-4, OPC UA for ISA-95 – Part 4: Job Control

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

OPC 40501-1, OPC UA for Machine Tools – Part 1: Machine Monitoring and Job Overview

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

OPC 40001-3, OPC UA for Machinery – Part 3: Job Management

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

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

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

3 Terms, definitions and conventions

3.1 Overview

It is assumed that basic concepts of OPC UA information modelling, OPC 40001-1, OPC 40501-1, OPC UA OPC 40001-101 and OPC 40001-3 are understood in this specification. This specification will use these concepts to describe the Textile Testing Devices 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-100 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 Textile Testing Devices terms

3.2.1 Textile testing device

Machine used to determine the properties of various materials in different production states, such as fibers, rovings, or yarns. It includes an integrated control system (e.g., PC, PLC) with an application for operating the device, defining test parameters, calculating results, evaluating statistics, and generating reports. The testing device incorporates interfaces for integration and automation purposes.

3.2.2 Manufacturing execution systems

Computerized systems used in manufacturing to track and document the transformation of raw materials into finished goods. These systems provide information that enables manufacturing decision-makers to understand how current conditions on the plant floor can be optimized to improve production output. The systems include interfaces for integration and automation.

3.2.3 Job

Set of instructions enabling the testing device to determine the properties of yarns and fibers. It includes a list of sample information (SampleInfo), carrier type identifier (CarrierTypeId), recipe identifier (RecipeId), and other relevant details. The number of tests required for each procedure in the recipe must be specified.

3.2.4 Recipe

Collection of test procedures and parameters that define a testing process for the testing device. The data structure of the recipe is outside the scope of this specification. Each recipe is identified by its unique RecipeId.

3.2.5 Test procedure

Process performed on a testing device to determine properties of materials such as fibers, rovings, and yarns. These procedures are often defined by national or international standards, such as ISO 13934 for tensile testing. Certain textile testing devices are designed to perform a single test procedure, while others can execute multiple procedures, either simultaneously or sequentially.

3.2.6 SampleInfo

Set of data required to associate results with a specific sample (SampleId) and to accurately parameterize test procedures based on sample properties, such as nominal linear density.

3.2.7 SampleId

Unique identifier associated with a produced package or sample, enabling its identification throughout an automated production environment.

3.2.8 JobId

Unique identifier created by the OPC client (e.g., manufacturing execution system, MES) for a job scheduled by the MES on a testing device.

3.2.9 Scheduled Job

Job created by the OPC client (e.g., manufacturing execution system, MES) with a unique JobId, transferred to the server using the “Store” or “StoreAndStart” method (see OPC 40001-3). Job metadata, including relevant testing conditions, are provided to the server as a job parameter. The results of this job are returned to the client and referenced by the SampleResultId.

3.2.10 Non-Scheduled Job

Job created manually on a textile testing device (TTD) without an order from the OPC client or manufacturing execution system (MES). The results of this test do not get a referenced JobId from the client but can still be transferred to the OPC client or MES. For the JobId a unique identifier is generated by the TTD.

3.2.11 TesterJobId

Internal identifier assigned by the testing device to a job, which is returned to the client (e.g., manufacturing execution system, MES) along with the test result. It allows tracking of a transferred result back to the data stored locally on the textile testing device.

3.2.12 Sample Result

Data transferred from the textile testing device (TTD) for each sample, containing information on measured material properties (e.g., elongation, maximum force). Each property is represented by a StatisticResultContent object within the ResultData. Results can be obtained either after completing a sample or after finishing the entire job.

3.2.13 TesterSampleResultId

Unique identifier created by the textile testing device for each sample result, potentially combining the TesterJobId and a sample identifier.

3.2.14 Sample

Material unit, such as a package of yarn or a batch of fibers, on which properties are determined by the testing device.

3.2.15 Testreport

Document, such as a PDF file, containing the results of a job as generated by the testing device. The specific content of the report is outside the scope of this specification.

3.2.16 Tester module

Optional hardware or software component of the textile testing device.

3.2.17 Operator

Laboratory staff responsible for operating the textile testing device.

3.2.18 CarrierTypeId

Reference to a type of carrier (geometric definition of a carrier or creel) stored on the textile testing device. The specific definition of the creel geometry is outside the scope of this specification.

3.2.19 Carrier / Creel

Device used to hold samples during testing, commonly utilized for transporting samples within the production area.

3.2.20 KPI

Key performance indicators providing information on the efficiency of a production environment, based on data such as machine running time, error frequency, and idle time.

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 66 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 Textile Testing and OPC UA

4.1 Introduction to Textile Testing Devices

Textile testing devices include a variety of different devices with a wide range of measuring and testing methods. These devices measure different material properties e.g. fibres, rovings or yarns. Basic examples include the maximum elongation and force, the shrinkage, crimp and crimp stability of a fibre or yarn.

The scope of this specification is focused on laboratory and at line tests of e.g. fibres, rovings, slivers, yarns and tapes or similar materials. These may include man-made and natural staple fibres as well as staple fibre yarns, filament yarns, textured yarns and technical yarns.

Textile testing devices are used, for example, in research institutes, quality control laboratories or for production control in industrial environments. In production control in particular, the processes are often highly digitalized and automated. Central Manufacturing Execution Systems (MES) are used to control which of the produced packages are to be sent to the testing device for spot checks, which material properties are tested and how many tests are performed. Finally, the results of the TTD are retrieved by the MES for further usage, such as storage and further analysis.

To organize the scheduling of these jobs, handling the recipes for the planned measurements and providing the results are the main processes for which this specification is intended.

The configuration of the measurements and the format of the results differ depending on the manufacturer or the type of testing device. To create a generic interface, it is hence necessary to abstract common patterns and minimize reference to local information on the TTD that are out of the scope of this specification. Making good use of the specification requires an understanding of this model. It will be touched only briefly in this section, more details can be found in Annex B.

4.2 Introduction to OPC Unified Architecture

4.2.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 textile testing, 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.2.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 1.

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.2.3 Information modelling in OPC UA

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

Object and Variable Nodes represent instances and they always reference a TypeDefinition (ObjectType or VariableType) Node which describes their semantics and structure. Figure 3 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 3 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 4 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 5. 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.2.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 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.2.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 in this document generally describe options for accessing different functionalities of a TTD from a client system. The main purpose of scheduling jobs and receive the results are described as well as other practical functions, like accessing or distributing recipes, accessing old TTD result data or checking the machine- or job state.

The use cases defined in this section cover the following topics:

Identification

Identification and Nameplate

Finding all TTDs in a Server

Configuration

Available test procedures on the TTD

Installed / Available tester modules on the TTD

Available exchangeable parts

Recipe management

Transfer of available recipe names.

Transfer of recipes from TTD to MES.

Transfer of recipes from MES to TTD.

Job management

Schedule a job on the device

Overview of jobs running and scheduled on the TTD

Overview over job runtimes.

Overview over jobs on the TTD and their states

Result management

Transfer of test results for tested samples from the TTD

Transfer of complete test reports from the TTD

Transfer of complete test results from TTD

Transfer sample results from non-scheduled jobs

Transfer job results of non-scheduled jobs

Device Status

Retrieving the current state of the TTD

KPI and Statistics

KPI calculation

Events and Notifications, Maintenance

Upcoming user interactions

Error messages and warnings

Calibration / maintenance

5.1 Identification

There are two use cases in this section. Both are covered by implementing the 3:MachineIdentification.

5.1.1 Identification and Nameplate

The user would like to uniquely identify machines, potentially across various OPC UA servers or aggregating OPC UA servers. The user wants to get standardized information about the machine, like manufacturer or serial number, and set user-specific information in order to simplify the usage of the machine.

That leads to the requirements:

A machine shall be globally uniquely identified.

Information about the machine, like manufacturer or serial number, can be accessed.

Application-specific information about a machine can be set by an OPC UA client.

5.1.2 Finding all Machines in a Server

The user would like to easily find all machines managed by an OPC UA server.

This leads to the requirement:

All machines shall be easy to find in an OPC UA server.

5.2 Configuration

The TTD should be able to provide information about its hard-/software configuration.

5.2.1 Available test procedures on the TTD

A production or quality manager wants to know the available test procedures that can be performed on a TTD in order to schedule upcoming test-jobs. The TTD delivers a list of test procedures. Each test procedure is characterized by the following properties:

TestProcedureId

Description

ProcedureReferences

IsProcedureLicensed

5.2.2 Available exchangeable parts

A production or quality manager wants to know the available exchangeable parts of a TTD in order to schedule upcoming test-jobs or plan maintenance. Exchangeable parts for example are load cells, clamp types, jaw faces and others.

For the identification of an exchangeable part, the following information is provided:

Name of the exchangeable part

PartId of the exchangeable part (this can be an Id or a serial number of the part)

LastCalibrationDate of the device

Additional to the information about the exchangeable part itself the following flags are provided:

Mounted indicates if the exchangeable part is currently mounted in the device or not.

Traceable indicates if the part is traceable or not. A part is traceable if it has a part id or serial number.

MachineReadable indicates if the PartId is machine readable

5.2.3 Installed / AvailableTester Modules

A production or quality manager would like to know which tester modules are installed in a testing device for the purposes of test planning on a dashboard, control station or mobile device. The tester modules can be hardware modules as well as software-modules. Examples are feeding devices, or yarn-break-detectors.

The following information about a tester module are exposed:

ModuleName the name of the module.

ModuleType the type of the module. E.g. hardware or software.

IsInstalled indicates if the module is installed on the TTD or not.

Version the version of the soft-/hardware module.

5.3 Recipe Management

5.3.1 Transfer of available recipe names

A client (MES) should be able to retrieve a list of the names of all available recipes on the TTD. These names are intended to be used as identifier in the process of job creation on the TTD.

5.3.2 Transfer of Recipes from TTD to Client (MES)

A client (MES) should be able to retrieve a set of recipes from the TTD. Assuming that the (file)size of the content of a recipe is small, it is sent as 0:ByteString to the MES.

5.3.3 Transfer of Recipes from Client (MES) to TTD

A client (MES) should be able to send a set of recipes to the TTD. Assuming that the (file)size of the content of a recipe is small, it is sent as 0:ByteString information to the TTD.

5.4 Job Management

The use cases in this section are covered by using the OPC 40001-3 with the introduction of some additional parameters.

5.4.1 Schedule a Job on the TTD

A production manager wants to schedule a job on the TTD.

5.4.2 Overview of Jobs running and scheduled on the TTD

A production or quality manager wants to have an overview of actual running and planned jobs on a dashboard, control station or mobile device.

5.4.3 Overview of Job runtimes

A production or quality manager would like to have a statistical overview of the runtimes. E.g. for prognoses of average testing times on a dashboard control station or mobile device.

5.4.4 Overview of Jobs on the TTD and their states

A production or quality manager wants to have an overview of scheduled jobs and their states on the TTD.

5.5 Result Management

5.5.1 Transfer of test results for tested samples from the TTD

A client (MES) wants to retrieve test results for the tested sample from the TTD. The test result is associated with the SampleId. The testresult itself contains the following statistical data:

ResultKey Unique Identifier of the measured property defined by the tester application.

ItemCount Number of valid tests that were calculated in the statistics.

MeanValue The mean value of the valid tests.

StandardDeviation The standard deviation of the valid tests.

CoefficientOfVariation The coefficient of variation value of the valid tests.

MinValue The minimum value of the valid tests.

MaxValue The maximum value of the valid tests.

ConfidenceInterval95 Confidence interval of measurement. 95% confidence interval.

5.5.2 Transfer of complete testreports from the TTD

A client (MES) wants to retrieve a complete test report (e.g. pdf file) from the TTD. The test report is associated with the JobId.

5.5.3 Transfer of complete testresults from the TTD

The client (MES) requests detailed test data (raw data) of a specific TesterSampleResultId. The Result provided by the TTD contains the URI where the raw data of the test is stored. The main purpose of this use case is to access large amounts of measured raw data generated for a test job not intended to be accessible via the OPC UA interface and not intended to be stored on the MES.

5.5.4 Transfer sample results from non-scheduled jobs

The client (MES) wants to retrieve sample results for jobs that were not scheduled by the client (MES). For a non-scheduled job the TTD generates a unique Id replacing the jobId.

5.5.5 Transfer job results of non-scheduled jobs

The client (MES) wants to retrieve test results for jobs that were not scheduled by the client (MES).

5.6 Device Status

5.6.1 Retrieving the current state of the TTD

A production or quality manager would like to have an overview of the TTD state (e.g., running, idle or stopped) that can be shown on a dashboard, control station or mobile device. Additionally, the error states should be visible on the systems.

5.7 KPI and Statistics

5.7.1 KPI Calculation

A production or quality manager wants to have an overview of KPIs like OEE at a MES system or dashboard.

5.8 Events and Notifications, Maintenance

5.8.1 Upcoming user interactions

For a maintenance technician or machine operator working on multiple TTDs, it is helpful to have a dashboard showing which of the testers requires the next manual intervention.

5.8.2 Error messages and warnings

A production, quality or maintenance manager would like to have all the relevant, currently active errors and warnings of the TTD visible on a MES system or dashboard.

5.8.3 Calibration and Maintenance

A production or quality manager wants to know the date of the last and upcoming calibration or maintenance task on the TTD.

5.8.4 History of Events and Alarms

A production-, quality- or maintenance manager would like to have all the recent errors and warnings of the testing device visible on an MES System or Dashboard. To achieve this goal the general history mechanism for events as defined in OPC 10000-11, OPC Unified Architecture - Part 11: Historical Access is used.

6 Textile Testing Devices Information Model overview

This chapter introduces the “OPC UA information model for textile testing devices”.

6.1 Textile Testing Device Instance example

This information model provides the necessary ObjectTypes to model a textile testing device interface in a structure as illustrated in an instance example in Figure 6. There are ObjectTypes that are used to identify the TTD (MachineIdentificationType), to manage the recipes on the TTD (RecipeManagementType), to manage the results on the TTD (ResultManagementType), to get notifications and events generated by the TTD (NotificationType), to get information about the device state and the operation mode of the TTD (MachineryItemState_StateMachineType, MachineryOperationModeStateMachineType) and the resulting machine statistics (MachineStatisticsType) as well as properties containing information about the device configuration (AvailableExchangeableParts, InstalledTesterModules, TestProcedureIds).

6.2 Textile Testing Device ObjectType hierarchy

The ObjectType hierarchy of this companion specification is shown within Figure 7 to Figure 10. Objects from external specifications are positioned within greyish-green boxes.

6.2.1 ObjectTypes for Configuration

Figure 7 shows the inheritance hierarchy of all ObjectTypes used for Configuration.

6.2.2 Identification, Device Status, Job Management, Notification, Alarms and Statistics

Figure 8 shows the inheritance hierarchy of all ObjectTypes used for Identification, Device Status, Job Management, Notification, Alarms and Events and Statistics.

6.2.3 Result Management

Figure 9 shows the inheritance hierarchy of all ObjectTypes used for Result Management of the TTD.

6.2.4 Recipe Management

Figure 10 shows the inheritance hierarchy of all ObjectTypes used for Recipe Management of the TTD.

7 OPC UA ObjectTypes

7.1 TextileTestingDeviceType ObjectType definition

7.1.1 Overview

The TextileTestingDeviceType is the main entry point for the functionality of the TTD.

The TextileTestingDeviceType is formally defined in Table 15.

AvailableExchangeableParts is an array holding the available exchangeable parts of the TTD.

2:Identification is the entry point for the MachineIdentification.

InstalledTesterModules is an array that stores the optional modules for the TTD.

MachineStatistics holds the machine statistics for the TTD.

3:MachineryBuildingBlocks contains all machinery building blocks. See for More Information.

6:Notification is the main entry point for upcoming events from the device. It also contains different tasks like calibration that have to be performed on the TTD. The NotificationType is inherited from OPC 40501-1.

RecipeManagement is the entry point for the recipe management on the TTD.

ResultManagement is the entry point for the result management on the TTD.

TestProcedureIds is an array that contains the IDs of the test procedures of the TTD.

The components of the TextileTestingDeviceType have additional references which are defined in Table 16.

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

MachineryItemState is the entry point for the MachineryItemState statemachine and holds the state of the TTD.

MachineryOperationMode is the entry point for the MachineryOperationMode statemachine and holds the operation mode of the TTD.

JobManagement is the entry point for the job management for the TTD.

7.1.2 Additional Information about the Job Management

7.1.2.1 Overview

OPC 10031-4 defines mechanisms to add job order information using the 7:ISA95JobOrderDataType and mechanisms getting the result or current status of the job order using the 7:ISA95JobResponseDataType. Both DataTypes define arrays of properties of a job order: general, personal, equipment, physical assets, and material. The 7:ISA95JobOrderDataType uses the general properties to describe the job order and the other properties to define the requirements, whereas the 7:ISA95JobResponseDataType uses the general properties to describe the output and the other properties to provide the information what has been used.

OPC UA Machinery Job Management (OPC 40001-3) standardizes some of those parameters, which are application-specific from the view of OPC 10031-4.

The guidelines and extensions specified in this section are designed to complement the foundational models, providing a structured framework for implementation. The Optional element (e.g. fields or parameters) of the OPC 10031-4 or OPC 40001-3 may be used as defined.

Additional to the listed Keys the Fields StartTime and EndTime are Mandatory in the JobResponseDataType.

7.2 RecipeManagementType ObjectType Definition

7.2.1 Overview

The RecipeManagementType is the entry point for the recipe management on the TTD. It provides an array of RecipeIds containing the metadata of all recipes that are stored on the TTD as well as methods for accessing the content of the recipe and methods for adding/deleting recipes to/from the TTD.

The RecipeManagementType is formally defined in Table 20.

RecipeIds is a Property that stores the metainformation for all recipes that are stored on the TTD.

GetRecipeIds is a Method that is used to retrieve the metadata for all recipes that are stored on the TTD.

GetRecipe is a Method that is used to retrieve the content of a recipe with a given id.

SetRecipe is a Method that is used to store a recipe on the TTD. A flag is used to indicate if the recipe should be overwritten if a recipe with the same id already exists on the TTD.

DeleteRecipe is a Method that is used to remove a recipe from the TTD. The id of the recipe is used to identify the recipe that is to be deleted.

GetRecipes is a Method that is used to retrieve all recipes (metadata and content) that are stored on the TTD at once.

SetRecipes is a Method that is used to store a set of recipes on the TTD. A flag is used to indicate if the recipes should be overwritten if a recipe with the same id already exists on the TTD.

7.2.2 GetRecipeIds

The Method GetRecipeIds is used to get information about all recipes that are stored on the TTD. The recipe metadata for all recipes is returned in the output parameter RecipeIds.

The signature of this Method is specified below. Table 21 and Table 22 specify the Arguments and AddressSpace representation, respectively.

Signature

	GetRecipeIds (
		[out]	RecipeIdDataType[]	RecipeIds)

7.2.3 GetRecipe

The Method GetRecipe is used to get the recipe content for a given RecipeId. The RecipeId has to match the system-wide unique Id property of the RecipeIdDataType associated with the recipe on the TTD. The output parameter Recipe is used to return the recipe.

The signature of this Method is specified below. Table 23 and Table 24 specify the Arguments and AddressSpace representation, respectively.

Signature

	GetRecipe (
		[in]	0:String	RecipeId,
		[out]	RecipeDataType	Recipe)

Method Result Codes (defined in Call Service)

7.2.4 SetRecipe

The Method SetRecipe is used to store a recipe on the TTD. Beneath the Recipe that is to be stored on the TTD the method takes an additional input parameter Overwrite that indicates if the recipe should be overwritten in case a recipe with the same id already exists on the TTD.

The signature of this Method is specified below. Table 25 and Table 26 specify the Arguments and AddressSpace representation, respectively.

Signature

	SetRecipe (
		[in]	RecipeDataType	Recipe,
		[in]	0:Boolean	Overwrite)

Method Result Codes (defined in Call Service)

7.2.5 DeleteRecipe

The Method DeleteRecipe is used to delete a recipe from the TTD. The given RecipeId has to match the system-wide unique Id property of the RecipeIdDataType associated with the recipe on the TTD.

The signature of this Method is specified below. Table 27 and Table 28 specify the Arguments and AddressSpace representation, respectively.

Signature

	DeleteRecipe (
		[in]	0:String	RecipeId)

Method Result Codes (defined in Call Service)

7.2.6 GetRecipes

The Method GetRecipes is used to get the recipe content for all recipes stored on the TTD. The output parameter Recipes is used to return all recipes that are currently stored on the TTD.

The signature of this Method is specified below. Table 29 and Table 30 specify the Arguments and AddressSpace representation, respectively.

Signature

	GetRecipes (
		[out]	RecipeDataType[] Recipes)

Method Result Codes (defined in Call Service)

7.2.7 SetRecipes

The Method SetRecipes is used to store a set of recipes on the TTD. Beneath the Recipes that are to be stored on the TTD the method takes an additional input parameter Overwrite that indicates if the recipes should be overwritten in case a recipe with the same id already exists on the TTD.

The signature of this Method is specified below. Table 31 and Table 32 specify the Arguments and AddressSpace representation, respectively.

Signature

	SetRecipes (
		[in]	RecipeDataType[]	Recipes,
		[in]	0:Boolean	Overwrite)

7.3 MachineStatisticsType ObjectType Definition

The MachineStatisticsType tracks KPI information of the TTD. Therefore, it measures the time the TTD is in the different MachineryItemState states. The MachineryItemState states are: Executing, NotExecuting, NotAvailable and OutOfService.

The MachineStatisticsType is formally defined in Table 33.

TotalExecutingTime stores the total time in ms the TTD was executing.

TotalNotAvailableTime stores the total time in ms the TTD was not available.

TotalNotExecutingTime stores the total time in ms the TTD was not executing, but operational. E.g. The TTD was in an idle state.

TotalOutOfServiceTime stores the total time in ms the TTD was out of service.

StartTime indicates the point in time at which the collection of the statistical data has been started.

ResetStatistics restarts all statistical data, including a reset of the StartTime to the current time.

7.4 RecurrentPrognosisType ObjectType Definition

The RecurrentPrognosisType represents recurrent tasks, such as calibration tasks in the TTD and is formally defined in Table 34. It is used in the TTD under the browse path /Notifications/Prognoses.

Activity is a localized text message specifying the task that is to be performed.

Interval represents the normal (estimated) time period between two task executions.

LastExecutionTime is the last time the task finished its execution.

7.5 TTDResultManagementType ObjectType Definition

The TTDResultManagementType provides mechanisms to access results generated by the TTD. Basically this is a subtype of the 4:ResultManagementType enforcing the implementation of different methods and objects for the result transfer mechanisms that should be used on the TTD. In general, we want to accomplish the following tasks:

Results can be stored in a local result store of the TTD

Data results or ResultIds can be obtained using the 4:Results folder and the 4:GetResultById method

Data results or ResultIds can be obtained using the 4:ResultReadyEvent

File results can be obtained using the 4:ResultTransfer (4:ResultTransferType) and its 0:GenerateFileForRead method

The TTDResultManagementType is formally defined in Table 35.

4:Results is a folder that is used to organize available results of the system. It is supposed to store variables of the 4:TTDResultType. A 4:ResultType contains the 4:ResultMetaData (see subtype TTDResultMetaDataType) used to identify the result and optional an data based 4:ResultContent or 4:ReducedResultContent. The ResultContent may be of any DataType but typically it is a field of StatisticResultContent defined in this specification or a 0:ByteString of any raw data.

4:ResultTransfer is used to transfer the content of a result by a temporary file transfer. The file that is to be transferred is identified by its ResultId.

4:GetResultById is used to retrieve a result (4:ResultDataType) from the TTD.

8 OPC UA EventTypes

8.1 TTDResultReadyEventType

The TTDResultReadyEventType provides information of a complete or partial result. Events of this type are triggered when the server has a complete or partial result available for the client. It is formally defined in Table 37.

To enable access to a result, several properties of the result, which are generated by the TTD, are supplied. These properties can be used to query the results in the ResultManagement Object. A sufficiently small result can also be provided in the ResultContent component of the Event.

This EventType inherits all properties of the ResultReadyEventType.

The Result variable of TTDResultType VariableType contains the subvariables as defined by the TTDResultType. Clients can select some of those individually when subscribing to events. The Result represents a partial or complete result.

9 OPC UA VariableTypes

9.1 TTDResultType

The TTDResultType is a subtype of 4:ResultType. It is used to add additional information about the generated result. The added information is:

SampleId

TesterJobId

TesterSampleResultId

ProductInstanceURI

It is formally defined in Table 38.

The components of the TTDResultType have additional subcomponents which are defined in Table 38.

For the description of the variables please refer to the section 10.7 TTDResultMetaDataType.

10 OPC UA DataTypes

10.1 ExchangeablePartDataType

This structure contains properties that are used to identify an exchangeable part inside or on the device. Exchangeable parts can be measurement equipment such as load cells and clamp types or tear and wear parts such as jaw faces.

The structure is defined in Table 40.

Its representation in the AddressSpace is defined in Table 41.

10.2 OptionalModuleDataType

This structure is used to define optional hard-/software modules that may be installed on the TTD.

The structure is defined in Table 42.

Its representation in the AddressSpace is defined in Table 43.

10.3 StatisticResultContentDataType

This structure contains a fixed statistical value set of one measured material property. The units for the ResultKey should be based on extended SI units that are not part of this specification.

The structure is defined in Table 44.

Its representation in the AddressSpace is defined in Table 45.

10.4 StatisticResultContentWithUnitsDataType

This structure contains a fixed statistical value set of one measured material property with units included.

The structure is defined in Table 46.

Its representation in the AddressSpace is defined in Table 47.

10.5 RecipeIdDataType

This structure contains properties that are used to identify and describe a recipe. This structure is also used in the methods provided by the RecipeManagement.

The structure is defined in Table 48.

Its representation in the AddressSpace is defined in Table 49.

10.6 RecipeDataType

This structure represents the recipe and combines its metadata that is used to identify the recipe with its content. The RecipeContent is a ByteString that holds the configuration data for the textile testing device. Most likely this is a ByteString representation of the content of a configuration file.

The structure is defined in Table 50.

Its representation in the AddressSpace is defined in Table 51.

10.7 TTDResultMetaDataType

This structure is a refinement of the ResultMetaDataType defined in OPC 40001-101 to describe the results generated by the TTD. Especially the fields SampleId, TesterJobId, TesterSampleResultId, ProductInstanceURI and CanBeDeleted were added to offer a better possibility to relate a result to a measurement.

The following fields of the 4:ResultMetaData should be used mandatorily:

ResultId (already mandatory)

HasTransferableDataOnFile

IsPartial

CreationTime

The structure is defined in Table 52.

For the structure of JobOrder see: Table 18 – Predefined 7:ISA95JobOrderDataType/JobOrderParameters.

Its representation in the AddressSpace is defined in Table 53.

10.8 TestProcedureIdDataType

This structure contains the id for the test procedure as well as some optional metadata describing the test procedure.

Its representation in the AddressSpace is defined in Table 55.

10.9 SampleInfoDataType

This structure contains properties of a sample (provided by MES), that are needed to execute a recipe. The SampleInfoDataType contains all information for tests on fibres and yarns.

Its representation in the AddressSpace is defined in Table 57.

10.10 TestNumDataType

This structure provides the number of tests for each test procedure.

The structure is defined in Table 58.

Its representation in the AddressSpace is defined in Table 59.

11 Profiles and ConformanceUnits

11.1 Conformance Units

This chapter defines the corresponding Conformance Units for the OPC UA Information Model for Textile Testing Devices.

11.2 Profiles

11.2.1 Profile list

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

11.2.2 Server Facets

11.2.2.1 Overview

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

An OPC UA Server that implements this Companion Specification needs to implement the TTD Base Server Profile (including the TTD Core Server Facet, the TTD Identification Server Facet and the TTD Textile Testing Device Server Facet).

11.2.2.2 TTD Base Server Profile

Table 62 defines a Profile that describes the functionalities of an OPC UA Server that uses OPC UA CS for Textile Testing Devices Information Models.

11.2.2.3 TTD Textile Testing Device Server Facet

Table 63 defines a Facet that describes the functionalities an OPC UA CS for Textile Testing Devices Server is expected to expose in regards of the full implementation of the OPC UA CS for Textile Testing Devices General Information Model.

12 Namespaces

12.1 Namespace Metadata

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

12.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 65 provides a list of mandatory and optional namespaces used in a Textile Testing Devices OPC UA Server.

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

13 (normative)Textile Testing Devices Namespace and mappings

NodeSet and supplementary files for TextileTesting Devices Information Model

The Textile Testing Devices Information Model is identified by the following URI:

http://opcfoundation.org/UA/TTD/

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/TTD/&v=1.0.0&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/TTD/&i=1

Supplementary files for the Textile Testing Devices Information Model can be found here:

https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/TTD/&v=1.0.0&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/TTD/&i=2

14 (informative)Examples and Explanations

14.1 Schedule a Job on the TTD by MES

The scheduling of a Job on the TTD by the MES is done in the following steps:

For each Job the MES wants to schedule on the TTD the MES creates an Object of the type 7:ISA95JobOrderDataType and sends it to the TTD by calling either the Method Store or the Method StoreAndStart on the 8:JobOrderControl Object located in the 8:JobManagement on the TTD.

The TTD takes the 7:ISA95JobOrderDataType, embeds it in a 7:ISA95JobOrderAndStateDataType and stores it in the 7:JobOrderList attached to the 8:JobOrderControl Object.

Figure 11 shows an “Example Job” in a proprietary Software on a proprietary TTD and Figure 12 shows the corresponding JobOrder as the 7:ISA95JobOrderDataType.

Figure 12 shows the scheduling of the “Example Job” on the TTD and the 7:JobOrderList that results.

The following properties are used for the test job:

CarrierId: 4321A

CarrierTypeId (Not shown in the figure): 1 (means 4x3 here, but is custom by the vendor)

RecipeId: POY100F40

Meas_Count: 2, Meas_Eve: 2, Meas_Force: 50 (combined in NumberOfTests[])

Sample_ID: A320T136 | A320T138 | A320T146 | A320 T147, Titer_Nom: 95 | 95 | 101 | 112, Pos. on carrier: 1 | 3 | 11 | 12 (combined in SampleInfos[])

14.2 Add additional custom properties to a job

In the 7:ISA95JobOrderDataType additional information like e.g. print information that should be displayed on a result sheet can be added to a job. For this use case an one-dimensional array of 0:KeyValuePair can be included in the 7:JobOrderParameters of the 7:JobOrderDataType. This 0:KeyValuePair has a 0:QualifiedName as key and a 0:BaseDataType as value. This enables implementors to use any DataType as value and process it as needed. However, some consideration has to be taken for the qualified name.

As the properties used in the AdditionalInfo have a custom/vendor specific character the 0:QualifiedName should use the namespace of the vendor (if specified) or the instance namespace of the TTD.

14.3 Recipe management

The main purpose of the recipe management is to get the available recipe ids that are stored on the TTD.
In addition to that some optional Methods can be implemented for the purpose of uploading recipes to the TTD, downloading recipes from the TTD and interchanging recipes between TTDs of the same type. Anyway, the content of the recipes are vendor and machine specific and treated as raw data, and therefore not interpreted by OPC UA.

14.3.1 Retrieving recipe ids from the TTD

The recipe ids stored on the TTD can be obtained in two ways. Either by reading the RecipeIds property or by invoking the GetRecipeIds Method. Both nodes are located under the RecipeManagement.

Figure 14 depicts the two possibilities to retrieve the RecipeIds from the TTD.

14.3.2 Retrieving recipes from and sending recipes to the TTD

Mainly for the purpose of interchanging recipes between TTDs of the same type, some optional Methods were added to the TTD. This Methods are:

GetRecipe/GetRecipes that retrieves one or multiple Recipes from the TTD. A Recipe consists of the RecipeId meta data and its associated content.

SetRecipe/SetRecipes that stores one/multiple Recipes on the TTD. A Recipe consists of the RecipeId meta data and its associated content.

DeleteRecipe that deletes a recipe from the TTD with a given recipe id.

14.4 Retrieving results for Scheduled / Non-scheduled job (Result management)

First of all it is to be said, that the process of retrieving measurement/testing results is independent of the fact if the Job was scheduled by a client or not.

In general results that are managed by the TTD have a unique ResultId property that is used to handle the results in the communication with the client (MES). The assignment of a Result to a sample or a measurement /test is done via additional properties that are added to the TTDResultMetaData. These properties are:

SampleId

TesterJobId

TesterSampleResultId

ProductInstanceUri

7:ISA95JobOrder (Includes the jobId for Scheduled jobs.)

The kind of the Result is determined by the properties and its ResultContent:

HasTransferableDataOnFile indicates that a Filetransfer is possible (Transfer of testreports)

ResultContent is present if statistical testresults are available (StatisticResultContentDataType)

resultUri this array with URIs is present and contains URIs if complete test results are available

14.5 Handling of Errors, Warnings and Prognosis (Maintenance and Calibration)

Errors, warnings and prognoses are managed under the 6:Notification node inside the TTD. As you can see in Figure 16, the 6:Notification node has two (optional) child nodes 6:Messages and 6:Prognoses. The 6:Messages node is used for sending events like errors, warnings and messages. The 6:Prognosis contains a list of the current prognoses (e.g. maintenance or calibration tasks) for the TTD. The list can be used dynamically or statically. When used statically the Objects in the AddressSpace stay the same during the runtime of the Server. No nodes are added or deleted. When used dynamically, Nodes in the AddressSpace are added and deleted as necessary: every time a new Prognosis is calculated, a respective object is added to the list of prognoses. As soon as the predicted task occurred, the Object in the AddressSpace is deleted. In the case of dynamic usage, each modification of the Prognosis list will trigger a GeneralModelChangeEvent to inform Clients (MES) about the change.

Figure 16 shows a sample implementation for the 6:Notification Node.

14.6 General process of schedule a Job and retrieving results

This section describes the general process of creating a job, processing the job and retrieving its results. The general processing of a job can be roughly divided into the following steps:

A Client (MES) schedules a Job on the TTD by invoking the Store Method on the TTD.

The TTD inserts the Job into its 7:JobOrderList.

At some later point, an Operator at the TTD picks a Job from the 7:JobOrderList and starts it.

The TTD processes the Job (with assistance of the operator) and generates the result(s) for this job.

After results are generated, the TTD informs the MES about new Results with a TTDResultReadyEvent.

The Client (MES) retrieves the new results.

Figure 17 shows this sequence. Following pictures relay on the “Example Job” JobOrder shown in Figure 12.

Figure 18 shows two examples for results generated by the TTD for the Example Job JobOrder.

15 (informative)Commonly used units in textile testing

___________

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.