6.3.2 OPC UA Reference Types

6.3.2.1 HasPnApplicationRelation
Table 66 – HasPnApplicationRelation Definition
Attribute Value
BrowseNameHasPnApplicationRelation
InverseNameIsPnApplicationRelationOf
SymmetricFalse
IsAbstractFalse
Subtype of the HasComponent from [OPC 10000-5].

The HasPnApplicationRelation reference is used to append nodes to the PnApplicationRelationContainerType node.

This reference should always be bidirectional.

The destination of the reference shall be an object of the ObjectType PnApplicationRelationType.

6.3.2.2 HasPnRealModule
Table 67 – HasPnRealModule Definition
Attribute Value
BrowseNameHasPnRealModule
InverseNameIsPnRealModuleOf
SymmetricFalse
IsAbstractFalse
Subtype of the HasComponent from [OPC 10000-5].

The HasPnRealModule reference type is used to append nodes to the PnRealModuleContainerType node.

This reference should always be bidirectional.

The destination of the reference shall be an object implementing the IPnRealModuleType interface.

6.3.2.3 HasPnRealSubmodule
Table 68 – HasPnRealSubmodule Definition
Attribute Value
BrowseNameHasPnRealSubmodule
InverseNameIsPnRealSubmoduleOf
SymmetricFalse
IsAbstractFalse
Subtype of the HasComponent from [OPC 10000-5].

The HasPnRealSubmodule reference type is used to append nodes to the PnRealSubmoduleContainerType node.

This reference should always be bidirectional.

The destination of the reference shall be an object implementing the IPnRealSubmoduleType interface.

6.3.2.4 HasPnExpectedModule
Table 69 – HasPnExpectedModule Definition
Attribute Value
BrowseNameHasPnExpectedModule
InverseNameIsPnExpectedModuleOf
SymmetricFalse
IsAbstractFalse
Subtype of the HasComponent from [OPC 10000-5].

The HasPnExpectedModule reference type is used to append nodes to the PnExpectedModuleContainerType node.

This reference should always be bidirectional.

The destination of the reference shall be an object implementing the IPnExpectedModuleType interface.

6.3.2.5 HasPnExpectedSubmodule
Table 70 – HasPnExpectedSubmodule Definition
Attribute Value
BrowseNameHasPnExpectedSubmodule
InverseNameIsPnExpectedSubmoduleOf
SymmetricFalse
IsAbstractFalse
Subtype of the HasComponent from [OPC 10000-5].

The HasPnExpectedSubmodule reference type is used to append nodes to the PnExpectedSubmoduleContainerType node.

This reference should always be bidirectional.

The destination of the reference shall be an object implementing the IPnExpectedSubmoduleType interface.

6.3.2.6 HasPnAsset
Table 71 – HasPnAsset Definition
Attribute Value
BrowseNameHasPnAsset
InverseNameIsPnAssetOf
SymmetricFalse
IsAbstractFalse
Subtype of the HasComponent from [OPC 10000-5].

The HasPnAsset reference type is used to append nodes to the PnAssetContainerType node.

This reference should always be bidirectional.

The destination of the reference shall be an object of the ObjectType PnAssetType.

6.3.2.7 HasPnInterface
Table 72 – HasPnInterface Definition
Attribute Value
BrowseNameHasPnInterface
InverseNameIsPnInterfaceOf
SymmetricFalse
IsAbstractFalse
Subtype of the HasComponent from [OPC 10000-5].

The HasPnInterface reference type is used to append nodes to the PnInterfaceContainerType node.

This reference should always be bidirectional.

The destination of the reference shall be an object implementing the IPnInterfaceType interface.

6.3.2.8 HasPnPort
Table 73 – HasPnPort Definition
Attribute Value
BrowseNameHasPnPort
InverseNameIsPnPortOf
SymmetricFalse
IsAbstractFalse
Subtype of the HasComponent from [OPC 10000-5].

The HasPnPort reference type is used to append nodes to the PnPortContainerType node.

This reference should always be bidirectional.

The destination of the reference shall be an object of the ObjectType PnPortType.

6.3.2.9 IsPnRealModule
Table 74 – IsPnRealModule Definition
Attribute Value
BrowseNameIsPnRealModule
InverseNameIsPnExpectedModule
SymmetricFalse
IsAbstractFalse
Subtype of the NonHierarchicalReferences from [OPC 10000-5].

The IsPnRealModule reference type is used to link ExpectedModule objects to their RealModule counterparts (See Figure 17 – Object Structure).

This reference should always be bidirectional.

The destination of the reference shall be an object implementing the IPnRealModuleType interface.

The source of the reference shall be an object implementing the IPnExpectedModuleType interface.

6.3.2.10 IsPnRealSubmodule
Table 75 – IsPnRealSubmodule Definition
Attribute Value
BrowseNameIsPnRealSubmodule
InverseNameIsPnExpectedSubmodule
SymmetricFalse
IsAbstractFalse
Subtype of the NonHierarchicalReferences from [OPC 10000-5].

The IsPnRealSubmodule reference type is used to link ExpectedSubmodule objects to their RealSubmodule counterparts (See Figure 17 – Object Structure).

This reference should always be bidirectional.

The destination of the reference shall be an object implementing the IPnRealSubmoduleType interface.

The source of the reference shall be an object implementing the IPnExpectedSubmoduleType interface.

6.3.2.11 IsPnApplicationRelationDeviceInterface
Table 76 – IsPnApplicationRelationDeviceInterface Definition
Attribute Value
BrowseNameIsPnApplicationRelationDeviceInterface
InverseNameUsedByPnApplicationRelation
SymmetricFalse
IsAbstractFalse
Subtype of the NonHierarchicalReferences from [OPC 10000-5].

The IsPnApplicationRelationDeviceInterface is used to link PnApplicationRelationType objects to the PN Interface object of the Device object (objects implementing IDeviceType) the application relation connects to (See Figure 17 – Object Structure).

This reference should always be bidirectional.

The destination of the reference shall be an object implementing the IPnInterfaceType interface.

The source of the reference shall be an object of the ObjectType PnApplicationRelationType and shall not use the reference type more than once.

6.3.2.12 IsPnApplicationRelationControllerInterface
Table 77 – IsPnApplicationRelationControllerInterface Definition
Attribute Value
BrowseNameIsPnApplicationRelationControllerInterface
InverseNameUsedByPnApplicationRelation
SymmetricFalse
IsAbstractFalse
Subtype of the NonHierarchicalReferences from [OPC 10000-5].

The IsPnApplicationRelationControllerInterface is used to link PnApplicationRelationType objects to the PN Interface object of the controller object (objects implementing IControllerType) the application relation belongs to (See Figure 17 – Object Structure).

This reference should always be bidirectional.

The destination of the reference shall be an object implementing the IPnInterfaceType interface.

The source of the reference shall be an object of the ObjectType PnApplicationRelationType and shall not use the reference more than once.

6.3.2.13 IsPnInterface
Table 78 – IsPnInterface Definition
Attribute Value
BrowseNameIsPnInterface
InverseNameRealizedByPnSubmodule
SymmetricFalse
IsAbstractFalse
Subtype of the NonHierarchicalReferences from [OPC 10000-5].

The IsPnInterface reference type is used to link RealSubmodule objects to PN Interface objects (See Figure 18 – Network Topology).

This reference should always be bidirectional.

The destination of the reference shall be an object implementing the IPnInterfaceType interface.

The source of the reference shall be an object implementing the IPnRealSubmoduleType interface.

6.3.2.14 IsPnPort
Table 79 – IsPnPort Definition
Attribute Value
BrowseNameIsPnPort
InverseNameRealizedByPnSubmodule
SymmetricFalse
IsAbstractFalse
Subtype of the NonHierarchicalReferences from [OPC 10000-5].

The IsPnPort reference type is used to link RealSubmodule objects to PN Port objects (Figure 18 – Network Topology).

This reference should always be bidirectional.

The destination of the reference shall be an object of the ObjectType PnPortType.

The source of the reference shall be an object implementing the IPnRealSubmoduleType interface.

6.3.2.15 CommLinkTo
Table 80 – CommLinkTo Definition
Attribute Value
BrowseNameCommLinkTo
InverseNameCommLinkFrom
SymmetricFalse
IsAbstractFalse
Subtype of the Organizes from [OPC 10000-5].

The CommLinkTo reference type is used between object instances representing network entities like Ethernet interfaces and Ethernet ports to describe their communication as well as their topology dependencies. (See Figure 18 – Network Topology).

This reference should always be bidirectional.