Search

Scope: Core (OPC-10000-*) All specs

56 result(s) for InstanceDeclarations

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

4.6.2 Complex TypeDefinitionNodes and their InstanceDeclarations

Complex TypeDefinitionNodes and their InstanceDeclarations TypeDefinitionNodes can be complex. A complex TypeDefinitionNode also defines References to other Nodes as part of the type definition. The ModellingRules defined in 6.4.4 specify ... type definitions from instances that represent real data, those instances are called InstanceDeclarations . However, this term is used to simplify this specification, if an instance is an InstanceDeclaration
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.6.4 Instantiation of complex TypeDefinitionNodes

reference two Nodes having the same BrowseName using forward hierarchical References . Instances based on InstanceDeclarations shall always keep the same BrowseName as the InstanceDeclaration they are derived from. A special ... called TranslateBrowsePathsToNodeIds may be used to identify the instances based on the InstanceDeclarations . Using the simple Browse Service might not be sufficient since the uniqueness of the BrowseName is only
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.10.2 Interface Model

definition of Interfaces : Interface ObjectTypes shall be abstract subtypes of the BaseInterfaceType ObjectType . InstanceDeclarations on an Interface shall only have ModellingRules Optional or Mandatory . Interfaces can be subtyped as specified ... same BrowsePath in the fully-inherited InstanceDeclarationHierarchy of the ObjectType . The rules for instantiating InstanceDeclarations defined in 6.2.6 shall be applied. Each optional InstanceDeclaration of the fully-inherited InstanceDeclarationHierarchy
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.8.6.1 Overview

used. A SubtypeRestriction shall only be used on Variables used as instances, never on InstanceDeclarations or VariableTypes . For Method Arguments , it can be used in combination with the HasArgumentDescription
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.2.3 InstanceDeclarationHierarchy

InstanceDeclarationHierarchy The InstanceDeclarationHierarchy of a TypeDefinitionNode contains the TypeDefinitionNode and all InstanceDeclarations that are directly or indirectly referenced from the TypeDefinitionNode using forward hierarchical References
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.2.7 Attribute Handling of InstanceDeclarations

Attribute Handling of InstanceDeclarations Some restrictions exist regarding the Attributes of InstanceDeclarations when the InstanceDeclaration is overridden or instantiated. The BrowseName and the NodeClass shall never change and always ... same as the original InstanceDeclaration . In addition, the rules defined in 6.2.8 apply for InstanceDeclarations of the NodeClass Variable
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.2.9 NodeIds of InstanceDeclarations

NodeIds of InstanceDeclarations InstanceDeclarations are identified by their BrowsePath . Different Servers might use different NodeIds for the InstanceDeclarations of common TypeDefinitionNodes , unless the definition of the TypeDefinitionNode already defines ... InstanceDeclaration . All TypeDefinitionNodes defined in OPC 10000-5 already define the NodeIds for their InstanceDeclarations and therefore shall be used in all Servers
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.3.3.1 Overview

Overview Subtypes inherit the fully-inherited parent type's InstanceDeclarations . As long as those InstanceDeclarations are not overridden they are not referenced by the subtype. InstanceDeclarations can be overridden ... optional Attributes . In order to get the full information about a subtype, the inherited InstanceDeclarations have to be collected from all types that can be found by recursively following
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.3.3.2 Fully-inherited InstanceDeclarationHierarchy

sake of clarity; all Nodes except for 1, 6, and 5 have ModellingRules ). All InstanceDeclarations of the InstanceDeclarationHierarchy and all Nodes referenced with a NonHierarchical Reference from such an InstanceDeclaration
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.3.3.3 Overriding InstanceDeclarations

Overriding InstanceDeclarations A subtype overrides an InstanceDeclaration by specifying an InstanceDeclaration with the same BrowsePath . An overridden InstanceDeclaration shall have the same NodeClass and BrowseName . The TypeDefinitionNode of the overridden ... used to determine the BrowsePath of the Node ). It is only possible to override InstanceDeclarations that are directly referenced from the TypeDefinitionNode . If an indirect referenced InstanceDeclaration , such
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.1 Overview

BrowsePath which may be the same as the BrowsePath for one of the InstanceDeclarations in the hierarchy of the TypeDefinitionNode. The InstanceDeclaration with the same BrowsePath is called the InstanceDeclaration
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.2 Creating an Instance

TypeDefinitionNode and BrowseName . If new copies are created, then the Attribute values of the InstanceDeclarations are used as the initial values. An instance shall not be a SourceNode ... Instance and its TypeDefinitionNode It is up to the Server to decide which InstanceDeclarations appear in any single instance. In some cases, the Server will not define the entire instance
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.3 Constraints on an Instance

Nodes , and References may be deleted as long as the ModellingRules defined on the InstanceDeclarations of the TypeDefinitionNode are still fulfilled. For Variables and Objects the HasTypeDefinition Reference shall always ... same TypeDefinitionNode as the InstanceDeclaration or a subtype of it. If two InstanceDeclarations of the fully-inherited InstanceDeclarationHierarchy have been connected directly with several References , all those References shall connect
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.1 General

defined in this standard do not define how to deal with NonHierarchical References between InstanceDeclarations , i.e. it is Server -specific if those References exist in an instance hierarchy ... AddressSpace . Subclause 6.4.4.3 defines how the ModellingRule may be changed when instantiating InstanceDeclarations with respect to the Properties . Subclause 6.4.4.2 defines how the ModellingRule may be changed when overriding InstanceDeclarations
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.3 Instantiation Rules for Properties of ModellingRules

first case, it is not required that newly created or referenced instances based on InstanceDeclarations have a ModellingRule , however, it is allowed that they have any ModellingRule independent ... second case, all instances that are referenced directly or indirectly from 'A' based on InstanceDeclarations of 'A_Type' initially maintain the same ModellingRule as their InstanceDeclarations. The ModellingRules
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.4.3 ExposesItsArray

Variable in the AddressSpace . The ExposesItsArray ModellingRule can only be applied on InstanceDeclarations of NodeClass Variable that are part of a VariableType having a single- or multidimensional array ... need to provide that information. It is allowed to reference A by other InstanceDeclarations as well. Those References have to be reflected on each instance based on A. Figure
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.4.4 OptionalPlaceholder

information when exposing a TypeDefinition . When the InstanceDeclaration is complex, i.e. it references other InstanceDeclarations with hierarchical References , these InstanceDeclarations are not further considered for instantiating the TypeDefinition ... recommended that the BrowseName and the DisplayName of InstanceDeclarations having the OptionalPlaceholder ModellingRule should be enclosed within angle brackets. When overriding the InstanceDeclaration, the ModellingRule shall remain OptionalPlaceholder . For Methods
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.4.5 MandatoryPlaceholder

Service (see OPC 10000-4 ). When the InstanceDeclaration is complex, i.e. it references other InstanceDeclarations with hierarchical References , these InstanceDeclarations are not further considered for instantiating the TypeDefinition ... recommended that the BrowseName and the DisplayName of InstanceDeclarations having the MandatoryPlaceholder ModellingRule should be enclosed within angle brackets. When overriding the InstanceDeclaration, the ModellingRule shall remain MandatoryPlaceholder . For Methods
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.22.3 EventFilter

inherited EventType where the Node is also the source of a HasModellingRule reference. EventTypes , InstanceDeclarations and Modelling Rules are described completely in OPC 10000-3 . In some cases the same
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

3.3 Conventions for Node descriptions

they are not defined in other tables. For example, the ObjectType ServerType defines its InstanceDeclarations in the same table, so the InstanceDeclarations are also bound to the ConformanceUnits defined ... table. The table even indirectly defines additional InstanceDeclarations as components of the top-level InstanceDeclarations , that are not directly visible in the table. The TypeDefinitions and DataTypes used
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

4.1 NodeIds

ServerType defined in 6.3.1 has the symbolic name "ServerType". One of its InstanceDeclarations would be identified as "ServerType.ServerCapabilities". Since this Object is complex, another InstanceDeclaration
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.3.13 NamespaceMetadataType

Attributes in all Servers , including the Value Attribute . For TypeDefinitionNodes , also the InstanceDeclarations shall be identical. That means that for static Nodes the semantic is always the same. Namespaces with
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.3 UANode

UATypes and static UAInstances. The field shall not be specified for UAInstances that are InstanceDeclarations . References Reference [] The list of References for the Node . RolePermissions RolePermission [] The list of RolePermissions
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.7 UAInstance

intended for use by design tools. This field shall be specified for all InstanceDeclarations and shall reference a UANode which is the source of a HierarchicalReference to the Node. DesignToolOnly
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.2 Two-state state machines

filter for a MonitoredItem. The TrueState Property and FalseState Property shall only exist on InstanceDeclarations . See Figure 9 for an illustration. Clients can use the Read Service
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

6.4 Conditions in InstanceDeclarations

Conditions in InstanceDeclarations Figure 28 shows the use of the HasCondition Reference and the HasEventSource Reference in an InstanceDeclaration . They are used to indicate what References and Conditions are available ... instance of the ObjectType . The use of the HasEventSource Reference in the context of InstanceDeclarations and TypeDefinition Nodes has no effect for Event generation. Figure 28 - Use of HasCondition
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.19 Special Restrictions on subtyping StateMachines

HasEffect , FromState , ToState , HasSubStateMachine, HasGuard ) shall be replicated in the subtype as well. If InstanceDeclarations are referenced (e.g., Methods used to trigger Transitions ) either the InstanceDeclaration of the supertype
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.3.1.1 Node definitions

they are not defined in other tables. For example, the ObjectType TopologyElementType defines its InstanceDeclarations in the same table, so the InstanceDeclarations are also bound to the ConformanceUnits defined ... table. The table even indirectly defines additional InstanceDeclarations as components of the top-level InstanceDeclarations , that are not directly visible in the table. The TypeDefinitions and DataTypes used
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.3.1.4 Additional Attribute values

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
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.3.2.2 BrowseNames

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
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

4.7 DeviceType

Units DI DeviceType DeviceType is a subtype of ComponentType which means it inherits all InstanceDeclarations . The DeviceType ObjectType is abstract. There will be no instances of a DeviceType itself, only
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

4.8 SoftwareType

Software Component SoftwareType is a subtype of ComponentType which means it inherits all InstanceDeclarations . The Properties Manufacturer , Model , and SoftwareRevision inherited from ComponentType are declared mandatory for SoftwareType instances
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

3.3.1.4 Additional Attribute values

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
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

3.3.2.2 BrowseNames

NamespaceUri for all BrowseNames defined in this document is defined in 16.2 . For InstanceDeclarations of NodeClass Object and Variable that are placeholders ( OptionalPlaceholder and MandatoryPlaceholder ModellingRule ), the BrowseName
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping

3.3.1.4 Additional Attribute values

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
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping

3.3.2.2 BrowseNames

NamespaceUri for all BrowseNames defined in this document is defined in 8.2 . For InstanceDeclarations of NodeClass Object and Variable that are placeholders ( OptionalPlaceholder and MandatoryPlaceholder ModellingRule ), the BrowseName
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

3.3.1.3 Additional Attribute values

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
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

3.3.2.2 BrowseNames

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
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

5.2.1 BasicStacklightType

Node Class BrowseName DataType TypeDefinition Other Subtype of the 0:OrderedListType, i.e. inheriting the InstanceDeclarations of that Node. 0:HasProperty Variable StacklightMode StacklightOperationMode 0:PropertyType M 0:HasComponent Object StackLevel ... HasOrderedComponent Reference shall represent the ordering from the base of the stacklight. The InstanceDeclarations of the BasicStacklightType have the Attribute values defined in Table 13 . Table 13 - BasicStacklightType Attribute values
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

5.2.2 StacklightType

BrowseName DataType TypeDefinition Other Subtype of the BasicStacklightType defined in 5.2.1 , i.e. inheriting the InstanceDeclarations of that Node. 0:HasInterface ObjectType 2:IDeviceHealthType Properties of the 2:IDeviceHealthType 0:HasComponent ... expose alarm instances and shall be used as specified in OPC 10000-100 . The InstanceDeclarations of the StacklightType have the Attribute values defined in Table 15 . Table 15 - StacklightType Attribute
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

5.2.3 StackLevelType

Other Subtype of the 0:BaseObjectType defined in OPC 10000-5, i.e. inheriting the InstanceDeclarations of that Node. 0:HasComponent Variable LevelPercent 0:Float 0:AnalogItemType M 0:HasComponent Variable ... DisplayMode indicates in what way the percentual value is displayed with the stacklight. The InstanceDeclarations of the StackLevelType have the Attribute values defined in Table 17 . Table 17 - StackLevelType Attribute
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

5.2.5 StackElementType

Other Subtype of the 0:BaseObjectType defined in OPC 10000-5 i.e. inheriting the InstanceDeclarations of that Node. 0:HasInterface ObjectType 0:IOrderedObjectType 0:HasProperty Variable SignalOn 0:Boolean ... enumerate the stacklight elements counting upwards beginning from the base of the stacklight. The InstanceDeclarations of the StackElementType have the Attribute values defined in Table 20 . Table 20 - StackElementType Attribute
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

5.2.6 StackElementLightType

BrowseName DataType TypeDefinition Other Subtype of the StackElementType defined in 5.2.5 , i.e. inheriting the InstanceDeclarations of that Node. 0:HasComponent Variable SignalColor SignalColor 0:BaseDataVariableType O 0:HasComponent Variable SignalRGBWValue ... shows the control information for each independent colour channel of the stacked element. The InstanceDeclarations of the StackElementLightType have the Attribute values defined in Table 22 . Table 22 - StackElementLightType Attribute
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

5.2.7 StackElementAcousticType

BrowseName DataType TypeDefinition Other Subtype of the StackElementType defined in 5.2.5 , i.e. inheriting the InstanceDeclarations of that Node. 0:HasComponent Variable OperationMode 0:UInteger 0:BaseDataVariableType M 0:HasComponent Variable ... DataType TypeDefinition Others AcousticSignals 0:HasOrderedComponent Object 0:<OrderedObject> AcousticSignalType MP The InstanceDeclarations of the StackElementAcousticType have the Attribute values defined in Table 25 . Table 25 - StackElementAcousticType Attribute
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

5.2.8 ControlChannelType

Other Subtype of the 0:BaseObjectType defined in OPC 10000-5 i.e. inheriting the InstanceDeclarations of that Node. 0:HasProperty Variable SignalOn 0:Boolean 0:PropertyType M 0:HasComponent Variable ... value is interpreted as 0 percent, the highest is interpreted as 100 percent. The InstanceDeclarations of the ControlChannelType have the Attribute values defined in Table 27 . Table 27 - ControlChannelType Attribute
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

5.2.9 AcousticSignalType

Other Subtype of the 0:BaseObjectType defined in OPC 10000-5 , i.e. inheriting the InstanceDeclarations of that Node. 0:HasInterface ObjectType 0:IOrderedObjectType 0:HasProperty Variable 0:NumberInList 0:UInteger ... Property . AudioSample contains the audio data, e.g. for devices capable of audio playback. The InstanceDeclarations of the AcousticSignalType have the Attribute values defined in Table 29 . Table 29 - AcousticSignalType Attribute
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

6.2.1.1 Overview

Other Subtype of the 0:BaseInterfaceType defined in OPC 10000-5 i.e. inheriting the InstanceDeclarations of that Node. 0:HasProperty Variable StartTime 0:DateTime 0:PropertyType O 0:HasComponent Method ... recommended not to use the IStatisticsType directly, but only subtypes of it. The InstanceDeclarations of the IStatisticsType have the Attribute values defined in Table 41 . Table 41 - IStatisticsType Attribute values
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

6.2.2 IAggregateStatisticsType

BrowseName DataType TypeDefinition Other Subtype of the IStatisticsType defined in 6.2.1 , i.e. inheriting the InstanceDeclarations of that Node. 0:HasProperty Variable ResetCondition 0:String 0:PropertyType O ResetCondition describes ... OPERATOR" means, that an operator resets the statistics on a local HMI. The InstanceDeclarations of the IAggregateStatisticsType have the Attribute values defined in Table 44 . Table 44 - IAggregateStatisticsType Attribute
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

6.2.3 IRollingStatisticsType

BrowseName DataType TypeDefinition Other Subtype of the IStatisticsType defined in 6.2.1 , i.e. inheriting the InstanceDeclarations of that Node. 0:HasProperty Variable WindowDuration 0:Duration 0:PropertyType O 0:HasProperty Variable ... WindowNumberOfValues together It shall provide a maximum of one of those Properties . The InstanceDeclarations of the IRollingStatisticsType have the Attribute values defined in Table 46 . Table 46 - IRollingStatisticsType Attribute values
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

7.4.4 ReusableDeviceCalibrationTargetCategoryType ObjectType

BrowseName DataType TypeDefinition Other Subtype of the ReusableCalibrationTargetCategoryType defined in 7.4.3 , i.e. inheriting the InstanceDeclarations of that Node. This ObjectType does not define any InstanceDeclarations
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

7.4.5 OneTimeCalibrationTargetCategoryType ObjectType

BrowseName DataType TypeDefinition Other Subtype of the BaseCalibrationTargetCategoryType defined in 7.4.2 , i.e. inheriting the InstanceDeclarations of that Node. This ObjectType does not define any InstanceDeclarations
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

7.4.6 DynamicCalibrationTargetCategoryType ObjectType

BrowseName DataType TypeDefinition Other Subtype of the BaseCalibrationTargetCategoryType defined in 7.4.2 , i.e. inheriting the InstanceDeclarations of that Node. This ObjectType does not define any InstanceDeclarations . Objects of this ObjectType should
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

3.4.1.4 Additional Attribute values

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
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

3.4.2.2 BrowseNames

NamespaceUri for all BrowseNames defined in this document is defined in 10.2 . For InstanceDeclarations of NodeClass Object and Variable that are placeholders ( OptionalPlaceholder and MandatoryPlaceholder ModellingRule ), the BrowseName
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

3.4.1.4 Additional Attribute values

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
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

3.4.2.2 BrowseNames

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