1 Scope

The OPC UA for Machinery specification contains various building blocks for Machinery that allow to address use cases across different types of machines and components of machines defined in various companion specifications.

For the general scope of the OPC UA for Machinery specification see OPC 40001-1.

This part contains a building block for

It uses OPC 34100 as base to add energy related information to a MachineryItem.

2 Normative references

The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments and errata) applies.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

OPC 10000-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 34100, OPC UA for Energy Consumption Management

http://www.opcfoundation.org/documents/34100/

3 Terms, definitions and conventions

3.1 Overview

It is assumed that basic concepts of OPC UA information modelling are understood in this specification. This specification will use these concepts to describe the OPC UA for Machinery Energy Management 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 40001-1 and OPC 34100 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 Machinery Energy Management terms

No additional terms are defined in this specification.

3.3 Abbreviated terms

3.4 Conventions used in this document

For conventions used in this document see OPC 40001-1.

4 General information to Machinery and OPC UA

For general information to Machinery and OPC UA see OPC 40001-1.

5 Use cases

5.1 Provide Energy Consumption Information for machines and its components according to OPC 34100

The general use cases on energy consumption information are already described in OPC 34100. This specification adds:

The user would like to easily access energy consumption information for machines and their components (see sections 6.1, 6.2 and 6.3).

The user would like to get a standard set of typical, market relevant energy information (see sections 6.4 and 6.5).

6 Machinery – Energy Management Information Model overview

6.1 General

This specification defines a Machinery building block to provide energy related information. The concept of machinery building blocks is defined in OPC 40001-1. This specification integrates into the existing building block Monitoring and therefore does not need to be referenced from the MachineryBuildingBlocks Object defined in OPC 40001-1. In Figure 1, the Monitoring building block is shown in an example, including where the information defined in this specification is added. The X:MyMachine Object of a vendor-specific X:MyMachineType provides the 2:Monitoring Object. This contains already a 2:Consumption Object intended to provide information on energy. In the example, it provides information on Electricity, CompressedAir, and Steam_Superheated. The BrowseNames of those Objects are defined in this specification (see 6.3), representing different resources. Details, on what information is provided in those Objects are described in 6.2. In addition, the X:MyMachine contains two components, X:MyComponent1 and X:MyComponent2 according to OPC 40001-1. Components may also have energy related information, as in Figure 1, where both provide information on Electricity.

6.2 Energy Information based on OPC 34100

OPC 34100 defines a common infrastructure for providing energy related measurements by defining the 3:EnergyMeasurementType. An Object of that type represents a metering point that can measure several measurement values of 3:EnergyMeasurementValueType. In addition, OPC 34100 defines common measurement values by defining a predefined BrowseName, MeasurementID, EngineeringUnits, etc. for Variables of 3:EnergyMeasurementValueType.

This specification uses the OPC 34100 as base to add energy related information to a MachineryItem. Under each Object representing a resource, there may be several Objects of the 3:EnergyMeasurementType, each representing one metering point. The main metering point should use the BrowseName Main defined in this specification (see 6.3). In Figure 2, an example is given. The Main Object provides several Variables defined in OPC 34100. The MachineryItem provides two additional metering points, X:Submeasurement1 and X:Submeasurement2. The first one is referenced with a Contains Reference indicating that the measured energy is contained in the Main values, whereas the second one is not referenced and therefore independent of the Main values.

In Figure 3, a more comprehensive example is given. In this case, also the components of the MachineryItem provide metering points. The metering points of the components may also be referenced by Contains Reference. This can be either done directly, as for X:MyComponent1, or indirectly via a proxy Object as in X:MyComponent2. Providing a proxy Object allows to provide anybody browsing more direct context and avoids potentially duplicated names, as many Main Objects of different components may be referenced.

6.3 Standardized BrowseNames to group energy measurements based on resources

This specification defines standardized BrowseNames as entry points to energy metering points of specific resources. They are defined in 9.1.

In addition, a standardized BrowseName is defined for the main energy metering point of a MachineryItem. This can be used for each specific resource. It is defined in 9.2.

6.4 Standardized grouping of related measurements in Interfaces

OPC 34100 already defines OPC UA Interfaces to group specific energy measurement variables for electricity. This specification defines additional OPC UA Interfaces for non-electrical energy in 7.1, 7.2 7.3, and 7.4. In Figure 4, an example is given on how to use those Interfaces. The X:MyMachine provides energy measurements for cooling lubricant, and the Main metering point, according to the recommendations in 6.5, implements the Interfaces INonElectricalEnergyType and IVolumeFlowType. By implementing the Interfaces, it provides the measurement variables as defined by the Interfaces.

6.5 Recommended Interfaces for different resources

This specification defines a recommended mapping of resources to Interfaces, Objects of the 3:EnergyMeasurementType should implement. In this version of the specification, not all resources defined in OPC 34100 are considered, but only a part of it.

Note: As some Interfaces only define optional Variables, it is in the responsibility of the implementer of the Interface to provide enough information to allow the calculation of energy data.

7 OPC UA ObjectTypes

7.1 INonElectricalEnergyType ObjectType Definition

The INonElectricalEnergyType provides general information on the consumed and produced non-electrical energy. It is formally defined in Table 2.

3:NeEnergyImportHp and 3:NeEnergyExportHp provide the information on the consumed and produced non-electrical energy and shall be used according to OPC 34100.

The component Variables of the INonElectricalEnergyType have additional Attributes defined in Table 3.

7.2 IBaseFlowType ObjectType Definition

The IBaseFlowType provides base information on flow resources and is formally defined in Table 4.

3:Pressure and 3:Temperature provide information on flow resources and shall be used according to OPC 34100.

The component Variables of the IBaseFlowType have additional Attributes defined in Table 5.

7.3 IVolumeFlowType ObjectType Definition

The IVolumeFlowType provides information on flowing resources based on volume. It is formally defined in Table 6.

This Interface is derived from IBaseFlowType. The InstanceDeclarations shall be used according to that Interface definition.

3:VolumeFlowRate and 3:Volume provide information on flow resources and shall be used according to OPC 34100.

The component Variables of the IVolumeFlowType have additional Attributes defined in Table 7.

7.4 IMassFlowType ObjectType Definition

The IMassFlowType provides information on flowing resources based on volume and mass. It is formally defined in Table 8.

This Interface is derived from IBaseFlowType. The InstanceDeclarations shall be used according to that Interface definition.

3:MassFlowRate and 3:Mass add information based on mass and shall be used according to OPC 34100.

The component Variables of the IMassFlowType have additional Attributes defined in Table 9.

8 OPC UA ReferenceTypes

8.1 Contains

Contains is a concrete ReferenceType and can be used directly. It is a subtype of HierarchicalReferences.

The semantic of this ReferenceType is to reference from a main energy measurement point to another one, which measurements are included in the main energy measurement point.

The SourceNode of References of this ReferenceType shall be an Object of 3:EnergyMeasurementType or an ObjectType being a subtype of 3:EnergyMeasurementType.

The TargetNode of References of this ReferenceType shall be an Object of 3:EnergyMeasurementType.

Contains is formally defined in Table 10.

9 Well-Known BrowseNames

9.1 Well-Known 0:FolderType BrowseNames

The 0:FolderType BrowseNames are formally defined in Table 11.

9.2 Well-Known 3:EnergyMeasurementType BrowseNames

The 3:EnergyMeasurementTyp BrowseNames are formally defined in Table 12.

10 Profiles and ConformanceUnits

10.1 Conformance Units

This chapter defines the corresponding Conformance Units for the OPC UA Information Model for Machinery – Energy Management.

10.2 Profiles

10.2.1 Profile list

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

10.2.2 Server Facets

10.2.2.1 Overview

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

10.2.2.2 Machinery Energy Base Server Facet

Table 15 defines a Profile that describes the base functionality to provide energy consumption information of a MachineryItem.

10.2.3 Client Facets

This specification does not define client facets.

11 Namespaces

11.1 Namespace Metadata

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

11.2 Handling of OPC UA Namespaces

Namespaces are used by OPC UA to create unique identifiers across different naming authorities. The Attributes NodeId and BrowseName are identifiers. A Node in the UA AddressSpace is unambiguously identified using a NodeId. Unlike NodeIds, the BrowseName cannot be used to unambiguously identify a Node. Different Nodes may have the same BrowseName. They are used to build a browse path between two Nodes or to define a standard Property.

Servers may often choose to use the same namespace for the NodeId and the BrowseName. However, if they want to provide a standard Property, its BrowseName shall have the namespace of the standards body although the namespace of the NodeId reflects something else, for example the EngineeringUnits Property. All NodeIds of Nodes not defined in this document shall not use the standard namespaces.

Table 17 provides a list of mandatory and optional namespaces used in an OPC UA for Machinery Server.

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

12 (normative)OPC UA for Machinery Namespace and mappings

NodeSet and supplementary files for OPC UA for Machinery Information Model

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

http://opcfoundation.org/UA/Machinery/Energy/

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/Machinery/Energy/&v=1.00&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/Machinery/Energy/&i=1

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

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

___________

Agreement of Use

COPYRIGHT RESTRICTIONS

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

Right of use for this specification is restricted to this specification and does not grant rights of use for referred documents.

Right of use for this specification will be granted without cost.

This document may be distributed through computer systems, printed or copied as long as the content remains unchanged and the document is not modified.

OPC Foundation and VDMA do not guarantee usability for any purpose and shall not be made liable for any case using the content of this document.

The user of the document agrees to indemnify OPC Foundation and VDMA and their officers, directors and agents harmless from all demands, claims, actions, losses, damages (including damages from personal injuries), costs and expenses (including attorneys' fees) which are in any way related to activities associated with its use of content from this specification.

The document shall not be used in conjunction with company advertising, shall not be sold or licensed to any party.

The intellectual property and copyright is solely owned by the OPC Foundation and VDMA.

PATENTS

The attention of adopters is directed to the possibility that compliance with or adoption of OPC or VDMA specifications may require use of an invention covered by patent rights. OPC Foundation or VDMA shall not be responsible for identifying patents for which a license may be required by any OPC or VDMA specification, or for conducting legal inquiries into the legal validity or scope of those patents that are brought to its attention. OPC or VDMA specifications are prospective and advisory only. Prospective users are responsible for protecting themselves against liability for infringement of patents.

WARRANTY AND LIABILITY DISCLAIMERS

WHILE THIS PUBLICATION IS BELIEVED TO BE ACCURATE, IT IS PROVIDED "AS IS" AND MAY CONTAIN ERRORS OR MISPRINTS. THE OPC FOUDATION NOR VDMA MAKES NO WARRANTY OF ANY KIND, EXPRESSED OR IMPLIED, WITH REGARD TO THIS PUBLICATION, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF TITLE OR OWNERSHIP, IMPLIED WARRANTY OF MERCHANTABILITY OR WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE OR USE. IN NO EVENT SHALL THE OPC FOUNDATION NOR VDMA BE LIABLE FOR ERRORS CONTAINED HEREIN OR FOR DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, RELIANCE OR COVER DAMAGES, INCLUDING LOSS OF PROFITS, REVENUE, DATA OR USE, INCURRED BY ANY USER OR ANY THIRD PARTY IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS MATERIAL, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

The entire risk as to the quality and performance of software developed using this specification is borne by you.

RESTRICTED RIGHTS LEGEND

This Specification is provided with Restricted Rights. Use, duplication or disclosure by the U.S. government is subject to restrictions as set forth in (a) this Agreement pursuant to DFARs 227.7202-3(a); (b) subparagraph (c)(1)(i) of the Rights in Technical Data and Computer Software clause at DFARs 252.227-7013; or (c) the Commercial Computer Software Restricted Rights clause at FAR 52.227-19 subdivision (c)(1) and (2), as applicable. Contractor / manufacturer are the OPC Foundation, 16101 N. 82nd Street, Suite 3B, Scottsdale, AZ, 85260-1830.

COMPLIANCE

The combination of VDMA and OPC Foundation shall at all times be the sole entities that may authorize developers, suppliers and sellers of hardware and software to use certification marks, trademarks or other special designations to indicate compliance with these materials as specified within this document. Products developed using this specification may claim compliance or conformance with this specification if and only if the software satisfactorily meets the certification requirements set by VDMA or the OPC Foundation. Products that do not meet these requirements may claim only that the product was based on this specification and must not claim compliance or conformance with this specification.

TRADEMARKS

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

GENERAL PROVISIONS

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

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

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

ISSUE REPORTING

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

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

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

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