Search

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

53 result(s) for ModellingRule

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

3.1.12 ModellingRule

ModellingRule metadata of an InstanceDeclaration that defines how the InstanceDeclaration will be used for instantiation and also defines subtyping rules for an InstanceDeclaration
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

3.3.2 Conventions for defining NodeClasses

column (optional or mandatory) does not imply a specific ModellingRule for Properties . Different Server implementations will choose to use ModellingRules appropriate for them
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.6.4 Instantiation of complex TypeDefinitionNodes

shows an instance of the TypeDefinitionNode "AI_BLK_TYPE", where the ModellingRule Mandatory , defined in 6.4.4.4.1 , was applied for its containing Variable . Thus, an instance
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.10.2 Interface Model

Interface shall have for each BrowsePath a similar Node (see 6.2.4) with the ModellingRule Mandatory using the same BrowsePath in the fully-inherited InstanceDeclarationHierarchy of the ObjectType . The rules ... Interface should have for each BrowsePath a similar Node (see 6.2.4) with the ModellingRule Mandatory or Optional using the same BrowsePath in the fully-inherited InstanceDeclarationHierarchy of the ObjectType
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.5.1 Object NodeClass

Properties of the Object . HasModellingRule 0..1 Objects can point to at most one ModellingRule Object using a HasModellingRule Reference (see 6.4.4 for details on ModellingRules ). HasTypeDefinition 1 The HasTypeDefinition ... this series of standards may define additional Properties for Objects . To specify its ModellingRule , an Object can use at most one HasModellingRule Reference pointing to a ModellingRule Object . ModellingRules
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.5.2 ObjectType NodeClass

ObjectType that all instances should use by default. This Property has no ModellingRule . It shall only be on the type Node . The ObjectType NodeClass inherits the base Attributes from
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.6.2 Variable NodeClass

Fields is unknown. References HasModellingRule 0..1 Variables can point to at most one ModellingRule Object using a HasModellingRule Reference (see 6.4.4 for details on ModellingRules ). HasProperty 0..* HasProperty References ... defines additional rules when using the Services for automation data. To specify its ModellingRule , a Variable can use at most one HasModellingRule Reference pointing to a ModellingRule Object . ModellingRules
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.7.1 Method NodeClass

Properties for the Method . HasModellingRule 0..1 Methods can point to at most one ModellingRule Object using a HasModellingRule Reference (see 6.4.4 for details on ModellingRules ). GeneratesEvent 0..* GeneratesEvent References ... this Reference is defined on an InstanceDeclaration the TargetNode shall use the Mandatory ModellingRule . <other References> 0..* Methods may contain other References . Standard Properties NodeVersion O String
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.2.1 InstanceDeclaration

InstanceDeclaration An InstanceDeclaration is an Object , Variable or Method that references a ModellingRule with a HasModellingRule Reference and is the TargetNode of a hierarchical Reference from a TypeDefinitionNode or another
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.2.2 Instances without ModellingRules

Instances without ModellingRules If no ModellingRule exists then the Node is neither considered for instantiation of a type nor for subtyping. If a Node referenced by a TypeDefinitionNode does ... reference a ModellingRule it indicates that this Node only belongs to the TypeDefinitionNode and not to the instances. For example, an ObjectType Node may contain a Property that describes scenarios
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.3.3.2 Fully-inherited InstanceDeclarationHierarchy

such an InstanceDeclaration are added to the table. Hierarchical References to Nodes without a ModellingRule are not considered. Table 19 - The InstanceDeclarationHierarchy for BetaType BrowsePath NodeId
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.3.3.3 Overriding InstanceDeclarations

append optional arguments after all existing arguments of the supertype's Method InstanceDeclaration . The ModellingRule of the overriding InstanceDeclaration may be changed as defined in 6.4.4.2 . Each overriding InstanceDeclaration needs
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.2 Creating an Instance

same hierarchy of Node s beneath the new Object or Variable depending on the ModellingRule of each InstanceDeclaration . Standard ModellingRules are defined in 6.4.4.4 . The Node s within the newly ... same BrowsePath as an InstanceDeclaration of its TypeDefinition which has an optional or mandatory ModellingRule except for the one based on the InstanceDeclaration . Figure 27 provides a simple example
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.1 General

define additional Properties for ModellingRules . OPC 10000-5 specifies the representation of the ModellingRule Objects, their Properties and their type in the AddressSpace . Subclause 6.4.4.3 defines how the ModellingRule ... changed when instantiating InstanceDeclarations with respect to the Properties . Subclause 6.4.4.2 defines how the ModellingRule may be changed when overriding InstanceDeclarations in subtypes with respect to the Properties
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.3 Instantiation Rules for Properties of ModellingRules

required that newly created or referenced instances based on InstanceDeclarations have a ModellingRule , however, it is allowed that they have any ModellingRule independent of the ModellingRule of their InstanceDeclaration ... valid instances of Type_A, although B of A1 has no ModellingRule and B of A3 has a different ModellingRule than B of Type_A. In the second case
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.4.1 Mandatory

Mandatory An InstanceDeclaration marked with the ModellingRule Mandatory means that for each existing BrowsePath on the instance a similar Node shall exist, but it is not defined whether ... InstanceDeclaration SP1. Figure 31 illustrates the example. Figure 31 - Use of the Standard ModellingRule Mandatory In 6.4.4.4.2 a complex example combining the Mandatory and Optional ModellingRules is given
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.4.3 ExposesItsArray

ExposesItsArray The ExposesItsArray ModellingRule exposes a special semantic on VariableTypes having a single- or multidimensional array as the data type. It indicates that each value of the array will also ... exposed as a 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
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.4.4 OptionalPlaceholder

OptionalPlaceholder For Object and Variable the intention of the ModellingRule OptionalPlaceholder is to expose the information that a complex TypeDefinition expects from instances of the TypeDefinition to add instances with ... Figure 35 , where an instance Device A adds two DeviceParameters in the Folder. The ModellingRule OptionalPlaceholder adds no additional constraints on instances of the TypeDefinition . It just provides useful information
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.4.5 MandatoryPlaceholder

MandatoryPlaceholder For Object and Variable the ModellingRule MandatoryPlaceholder has a similar intention as the ModellingRule OptionalPlaceholder . It exposes the information that a TypeDefinition expects of instances of the TypeDefinition ... valid because it does not provide a DeviceParameter at all. The ModellingRule MandatoryPlaceholder requires that each instance provides at least one instance with the TypeDefinition of the InstanceDeclaration
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.5 Changing Type Definitions that are already used

fulfilled. For example, it is not allowed to add a Property using the ModellingRule Mandatory on a type if instances of this type exist without the Property . In that case
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.12 HasModellingRule ReferenceType

subtype of NonHierarchicalReferences . The semantic of this ReferenceType is to bind the ModellingRule to an Object , Variable or Method . The ModellingRule mechanisms are described in 6.4.4 . The SourceNode of this ... Object , Variable or Method . The TargetNode shall be an Object of the ObjectType "ModellingRule" or one of its subtypes. Each Node shall be the SourceNode of at most
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.22.2 Differences between HasStructuredComponent and ExposesItsArray

multi-dimensional array of a Variable as subvariables. The same is true for the ModellingRule ExposesItsArray . However, both concepts handle this differently, as described in this section. Using the HasStructuredComponent ... achieved when subscribing to the corresponding IndexRange on the parent Variable . Using the ExposesItsArray ModellingRule , the BrowseName of the subvariables are not defined and do not reflect the place
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.8.2.1 Description

same hierarchy of Node s beneath the new Object or Variable depending on the ModellingRule of each InstanceDeclaration . All Nodes with a ModellingRule of Mandatory shall be created
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.12.2.2 Parameters

Method specified in methodId. In this case the Method shall not have a ModellingRule . See OPC 10000-3 for a description of Objects and their Methods . methodId NodeId NodeId
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

3.3 Conventions for Node descriptions

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 ... 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
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

8.4.1 ExposesItsArray

ExposesItsArray The ModellingRule ExposesItsArray is defined in OPC 10000-3 . Its representation in the AddressSpace, the " ExposesItsArray " Object, is formally defined in Table 113 . Table 113 - ExposesItsArray definition
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

8.4.2 Mandatory

Mandatory The ModellingRule Mandatory is defined in OPC 10000-3 . Its representation in the AddressSpace, the " Mandatory " Object, is formally defined in Table 114 . Table 114 - Mandatory definition
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

8.4.3 Optional

Optional The ModellingRule Optional is defined in OPC 10000-3 . Its representation in the AddressSpace , the " Optional " Object, is formally defined in Table 115 . Table 115 - Optional definition
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

8.4.4 OptionalPlaceholder

OptionalPlaceholder The ModellingRule OptionalPlaceholder is defined in OPC 10000-3 . Its representation in the AddressSpace , the " OptionalPlaceholder " Object, is formally defined in Table 116 . Table 116 - OptionalPlaceholder definition
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

8.4.5 MandatoryPlaceholder

MandatoryPlaceholder The ModellingRule MandatoryPlaceholder is defined in OPC 10000-3 . Its representation in the AddressSpace , the " MandatoryPlaceholder " Object, is formally defined in Table 117 . Table 117 - MandatoryPlaceholder definition
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.2 ConditionType

ConditionType definition Attribute Value BrowseName ConditionType IsAbstract True References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the BaseEventType defined in 10000-5 HasSubtype ObjectType DialogConditionType Defined in Clause 5.6.2 HasSubtype ... HasProperty Variable FalseState LocalizedText PropertyType The empty "Others" column indicates that no ModellingRule applies. The ConditionType inherits all Properties of the BaseEventType . Their semantic is defined
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.6.2 DialogConditionType

HasProperty Variable FalseState LocalizedText PropertyType The empty " Others" column indicates that no ModellingRule applies. The DialogConditionType inherits all Properties of the ConditionType . DialogState/Id when set to True indicates
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.7.2 AcknowledgeableConditionType

AcknowledgeableConditionType definition Attribute Value BrowseName AcknowledgeableConditionType IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the ConditionType defined in clause 5.5.2 . HasSubtype ObjectType AlarmConditionType Defined in Clause 5.8.2 HasComponent ... HasProperty Variable FalseState LocalizedText PropertyType The empty " Others" column indicates that no ModellingRule applies. The AcknowledgeableConditionType inherits all Properties of the ConditionType . AckedState when False indicates that
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.2 AlarmConditionType

HasProperty Variable FalseState LocalizedText PropertyType The empty " Others" column indicates that no ModellingRule applies. The AlarmConditionType inherits all Properties of the AcknowledgeableConditionType . The following states are sub-states
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.20 NonExclusiveLimitAlarmType

HasProperty Variable FalseState LocalizedText PropertyType The empty " Others" column indicates that no ModellingRule applies. HighHighState , HighState , LowState , and LowLowState represent the non-exclusive states. As an example
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.9 StateType

using a HasComponent Reference or a subtype of HasComponent and shall not have a ModellingRule as they are not applied on the instances. The StateType is formally defined in Table ... StateType definition Attribute Value BrowseName StateType IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the BaseObjectType defined in OPC 10000-5 HasProperty Variable StateNumber UInt32 PropertyType Mandatory HasSubtype
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.11 TransitionType

using a HasComponent Reference or a subtype of HasComponent and shall not have a ModellingRule as they are not applied on the instances. Each valid Transition shall have exactly ... TransitionType definition Attribute Value BrowseName TransitionType IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the BaseObjectType defined in OPC 10000-5 HasProperty Variable TransitionNumber UInt32 PropertyType Mandatory Conformance
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.19 Special Restrictions on subtyping StateMachines

instantiated, this information is only provided on the ObjectType . They have no ModellingRule , and thus, also the inheritance of States and Transitions is not defined. Therefore, the following rules apply
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

3.3.1 Usage of Other column in type definitions

Other Characteristics Name Short Name Description Mandatory M The Node has the Mandatory ModellingRule . Optional O The Node has the Optional ModellingRule . MandatoryPlaceholder MP The Node has the MandatoryPlaceholder ModellingRule ... OptionalPlaceholder OP The Node has the OptionalPlaceholder ModellingRule . ReadOnly RO The Node AccessLevel Attribute has the CurrentRead bit set but not the CurrentWrite bit. ReadWrite RW The Node AccessLevel Attribute
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

A.7 ReferenceType mapping

type and is marked with the Modelling Rule "OPC:TypeOnly" (see A.11.2.2 ). ModellingRule ModellingRuleType Present on the destination interface to indicate the UA ModellingRule of the destination ... missing, the ModellingRule "Optional" shall be assumed. RefClassConnectsToPath xs:string Indicates the AML path to the only other InterfaceClass that this interface shall be allowed to connect
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.3.1.1 Node definitions

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

3.3.2.2 BrowseNames

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

4.4.1 Model

FunctionalGroup can be hidden on an instance the TypeDefinition shall use an appropriate ModellingRule like "Optional". If desirable, Nodes can be also children of FunctionalGroups . If such Nodes
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

3.3.1.1 Node definitions

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

3.3.2.2 BrowseNames

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

3.3.1.1 Node definitions

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

3.3.2.2 BrowseNames

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

3.3.1 Conventions for Node descriptions

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

3.3.2.2 BrowseNames

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

3.4.1.1 Node definitions

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

3.4.2.2 BrowseNames

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

3.4.1.1 Node definitions

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

3.4.2.2 BrowseNames

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