1 Scope

This document defines an OPC UA Information Model for the DigitalProductPassport (DPP) as specified by the European Ecodesign for Sustainable Products Regulation (ESPR, Regulation (EU) 2024/1781). It maps the semantic data model defined in EN 18223:2026 to OPC UA ObjectTypes, DataTypes, and address space structures, enabling interoperable access to DPP data through OPC UA.

The scope includes:

The representation of product properties, documents, multi-valued and multi-language data elements, and data element collections as defined in the CEN/CLC/JTC 24 standards series

OPC UA ObjectTypes for real-time browsing of DPP data in an OPC UA address space

OPC UA DataTypes for read/write of complete DPP instances as structured values

The mapping of the GranularityEnumeration (Model, Batch, Item) for product identification levels

2 Normative references

The following referenced documents are indispensable for the application 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-19, OPC Unified Architecture - Part 19: Dictionary References

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

EN 18216:2026, Digital product passport - Data exchange protocols

https://www.cencenelec.eu/

EN 18219:2026, Digital product passport - Unique identifiers

https://www.cencenelec.eu/

EN 18220:2026, Digital product passport - Data carriers

https://www.cencenelec.eu/

EN 18221:2026, Digital product passport - data storage, archiving, and data

persistence

https://www.cencenelec.eu/

EN 18222:2026, Digital product passport - Application Programming Interfaces (APIs) for the product passport lifecycle management and searchability

https://www.cencenelec.eu/

EN 18223:2026, Digital product passport - System interoperability

https://www.cencenelec.eu/

EN 18239:2026 (Security) defines access rights, security, and business confidentiality.

https://www.cencenelec.eu/

EN 18246:2026 (Data Auth) defines data authentication, reliability and integrity.

https://www.cencenelec.eu/

3 Terms, abbreviated terms and conventions

3.1 Overview

It is assumed that basic concepts of OPC UA information modelling and <other specifications> are understood in this document. This document will use these concepts to describe the DigitalProductPassport 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 as well as the following apply.

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

3.2 Terms and definitions

3.2.1 DigitalProductPassport

digital record of product characteristics throughout its life cycle.

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 Other columns can 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 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 can 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 Annex A.

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 a 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. Annex A 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 document or if it is server-specific.

For all Nodes specified in this document, 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 document, the Attributes named in Table 8 shall be set as specified in the Table 8. The definitions for the Attributes can be found in OPC 10000-3.

3.4.3.3 Variables

For all Variables specified in this document, 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 document, 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 document, 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.

Fields with abstract DataTypes shall have True in the "Allow Subtypes" column.

It is not allowed to add both columns to combine optional fields and fields that allow subtypes in one structure.

4 General information

4.1 Introduction to Digital Product Passport

The European Ecodesign for Sustainable Products Regulation (ESPR, Regulation (EU) 2024/1781) establishes the Digital Product Passport (DPP) as a mandatory requirement for products placed on the EU market. The technical standards for DPP implementation are being developed by CEN/CLC/JTC 24 as a series of European standards:

EN 18219:2026 (Unique Identifiers) defines globally unique product identifiers and the three levels of granularity (Model, Batch, Item) at which they apply.

EN 18220:2026 (Data Carriers) specifies the data carriers (e.g. QR codes, RFID) used to link physical products to their digital passports.

EN 18221:2026 (Data Storage) defines requirements for DPP data storage and persistence.

EN 18216:2026 (Data Exchange Protocols) specifies the protocols for exchanging DPP data between systems, i.e. HTTP REST.

EN 18222:2026 (API) defines the application programming interfaces, leveraging the HTTP REST protocol, for accessing DPP data. This API is implemented in the OPC Foundation's UA Cloud Library.

EN 18223:2026 (System Interoperability) defines the semantic data model that this companion specification maps to OPC UA. It specifies the core entities: DigitalProductPassport, DataElement, DataElementCollection, SingleValuedDataElement, MultiValuedDataElement, MultiLanguageDataElement and RelatedResource.

EN 18239:2026 (Security) defines access rights, security, and business confidentiality.

EN 18246:2026 (Data Auth) defines data authentication, reliability and integrity.

This OPC UA companion specification maps the EN 18223:2026 data model to OPC UA ObjectTypes for real-time browsing of DPP data in an AddressSpace, and to OPC UA DataTypes for read/write of complete DPP instances. The DataElementType hierarchy mirrors the EN 18223 entity model, with properties mapped to OPC UA Variables and dictionary references preserved to maintain semantic traceability to the underlying data dictionaries.

For example, the companion specification may be used by a tool to convert DPP templates from the IDTA and Catena-X (provided by these organisations in Asset Admin Shell JSON or XML format only) into OPC UA NodeSet files for storage in the UA Cloud Library. This process is shown in Figure 1

An example of an overall DigitalProductPassport architecture for batteries described by a is depicted in the Figure 2 which makes use of open-source components provided by the OPC Foundation.

In Figure 2, the Companion Specification will be used within the UA Data Processor, reading battery production data, battery usage data and battery Bill of Materials (BoM) from different data sources and constructing a Digital Battery Passport (DBP) from this information. The DBP is then stored in OPC UA NodeSet file format and uploaded to the UA Cloud Library for retrieval via the DPP API by the battery's customer (called Product Customer in the diagram).

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 DigitalProductPassport, 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 visualisation 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 3.

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

Object and Variable Nodes represent instances and they always reference a TypeDefinition (ObjectType or VariableType) Node which describes their semantics and structure. Figure 5 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 5 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 can 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 subtype 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 can add additional restrictions. Figure 6 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 7. 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.

The 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 functionalities (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 can 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

5.1 Overview

The DPP regulations places the burden on Manufacturers to collect the information that needs to go into the DPPs for the products they produce. This requires the Manufacturer be able to retrieve the DPPs for the materials, understand the information in them, and build their own DPPs that have the information required by regulation including links to the DPPs of additional product components. OPC UA provides an information modelling framework that can describe the requirements of the various regulations and allow a Manufacturer build its own DPPs using existing tools. The OPC UA information models are also used by the existing OT systems which data management needs.

The UACloudLibrary is a key part of the OPC ecosystem, and it is a cloud-based repository for OPC UA information models. Multiple versions of the UACloudLibrary are deployed in production systems today. This makes UACloudLibrary a foundation for a DPP Service Provider that provides additional services to Manufacturers to help them create and maintain their DPPs.

The relationships between the UACloudLibrary and the various actors involved with DPP creation and consumption are shown in Figure 8.

5.2 DPP Consumer Retrieves DPPs from the UACloudLibrary

A DPP Consumer needs to review the DPP for a product obtained. The DPPId is retrieved from a QR code on the label and use the EN 18222:2026 defined API to request the DPP. The UACloudLibrary builds a DPP including the DataElements the consumer has access to and returns it in a mandated format such as JSON-LD.

5.3 Importing Requirements from a Delegated Act for a Product Category

The EU is expected to create requirements for different product categories over time. Once a new set of requirements is published a DataElementType needs to be created so the requirements can be described in a NodeSet. This will require manual editing or automated conversion from another format such as an AAS submodel template. Once this is done, UACloudLibrary APIs are used to store the DataElementType, that they can be used by Manufacturers building their DPPs.

5.4 Manufacturer needs to Build a DPP for a new Product

The Manufacturer uses a standard OPC UA Modelling Tool to build a DPP which contains the required DataElements. They enter the information as values of the Variables and saves it as a DPP in the UACloudLibrary. The format of the DPP in this context is a NodeSet, to ensure compatibility with tools currently used in factories.

If the Manufacturer needs to produce DPPs with Batch or Item granularity, they can create a new subtype of DigitalProductPassportType that is instantiated by their OT systems during production. The OT systems would then automatically publish DPPs to the UACloudLibrary using UACloudLibrary APIs.

The Manufacturer also has the option of specifying the RolePermissions for any DataElement which allows the Manufacturer to control who has access to information. When a Consumer requests a DPP, it provides credentials that are mapped to Roles.

5.5 Testing Authority needs to update a DPP

Some of the claims in a DPP require authentication by an independent Testing Authority. Once the Testing Authority completes its work, it updates a DPP by adding a DataElement with a digital signature. This is done using the EN 18222:2026 defined API. The UACloudLibrary will save the original serialized from of a DataElement (i.e. JSON-LD with a Signature). The Signature is represented with the VerifiableCredentialType, which can be attached as an Add-In to any DataElement.

6 OPC UA ObjectTypes

6.1 Overview

The ObjectTypes defined in this specification are shown in Figure 9.

6.2 DataElementType definition

Abstract base type for all DataElements in a DigitalProductPassport.

6.3 VerifiableCredentialType definition

A signature block that can be applied to a DPP or a DataElement.

The Signature has a format defined by other standards. The regulators decide which formats to use. The formats chosen should include a normalization process which allows the DPP to be constructed on demand without affecting the signature.

6.4 SingleValuedDataElementType definition

Represents a single data point with a value.

6.5 MultiValuedDataElementType definition

A list which contains

6.6 DataElementCollectionType definition

A list of DataElements.

6.7 RelatedResourceType definition

Semantic representation of any instance of a document or certificate that might be required to be included into a DigitalProductPassport instance

6.8 MultiLanguageDataElementType definition

Represents a language dependent data point whose value varies with respect to the language associated with it

6.9 DigitalProductPassportType definition

A document that identifies a product and various properties required by regulation.

It allows the entire lifecycle of a product to be tracked. Including, proof of origin.

This ObjectType represents a DigitalProductPassport. It is defined in Table 22.

Subtypes may be defined that specify specific DataElements required by a particular product.

Instances of this class represent a DPP.

7 OPC UA DataTypes

7.1 GranularityEnumeration

Level of granularity of the DPP

Its representation in the AddressSpace is defined in Table 24.

Annex A (normative) DigitalProductPassport Namespace and mappings

A.1 NodeSet and supplementary files for DigitalProductPassport Information Model

The DigitalProductPassport information model is identified by the following URI:

http://opcfoundation.org/UA/DigitalProductPassport/

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/DigitalProductPassport/&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/DigitalProductPassport/&i=1

Supplementary files for the DigitalProductPassport information model can be found here:

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

_____________

Agreement of Use

COPYRIGHT RESTRICTIONS

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

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

PATENTS

The attention of adopters is directed to the possibility that compliance with or adoption of OPC or CESMII specifications may require use of an invention covered by patent rights. OPC Foundation or CESMII shall not be responsible for identifying patents for which a license may be required by any OPC or CESMII specification, or for conducting legal inquiries into the legal validity or scope of those patents that are brought to its attention. OPC or CESMII 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 CESMII 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 CESMII 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 CESMII 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 CESMII or the OPC Foundation. Products that do not meet these requirements may claim only that the product was based on this specification and must not claim compliance or conformance with this specification.

Trademarks

Most computer and software brand names have trademarks or registered trademarks. The individual trademarks have not been listed here.

GENERAL PROVISIONS

Should any provision of this Agreement be held to be void, invalid, unenforceable or illegal by a court, the validity and enforceability of the other provisions shall not be affected thereby.

This Agreement shall be governed by and construed under the laws of Germany.

This Agreement embodies the entire understanding between the parties with respect to, and supersedes any prior understanding or agreement (oral or written) relating to, this specification.

ISSUE REPORTING

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

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

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

https://github.com/OPCFoundation/UA-CloudLibrary/issues

The following table includes the Mantis issues resolved with this revision.