Search

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

31 result(s) for ModellingRules

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

3.3.2 Conventions for defining NodeClasses

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.2 Complex TypeDefinitionNodes and their InstanceDeclarations

TypeDefinitionNode also defines References to other Nodes as part of the type definition. The ModellingRules defined in 6.4.4 specify how those Nodes are handled when creating an instance
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.6.4 Instantiation of complex TypeDefinitionNodes

Instantiation of complex TypeDefinitionNodes The instantiation of complex TypeDefinitionNodes depends on the ModellingRules defined in 6.4.4 . However, the intention is that instances of a type definition will reflect the structure
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.7.2 EventTypes

those EventTypes are only exposed via a Subscription . Components of an EventType defined with ModellingRules other than Mandatory or Optional cannot be returned in an Event Subscription . EventTypes exist
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.10.2 Interface Model

abstract subtypes of the BaseInterfaceType ObjectType . InstanceDeclarations on an Interface shall only have ModellingRules Optional or Mandatory . Interfaces can be subtyped as specified in clause 6.3. Interfaces shall
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.5.1 Object NodeClass

most one ModellingRule Object using a HasModellingRule Reference (see 6.4.4 for details on ModellingRules ). HasTypeDefinition 1 The HasTypeDefinition Reference points to the type definition of the Object. Each Object shall ... Object can use at most one HasModellingRule Reference pointing to a ModellingRule Object . ModellingRules are defined in 6.4.4 . HasNotifier and HasEventSource References are used to provide information about eventing
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.5.4 Client-side creation of Objects of an ObjectType

AddNodes Service contains all components defined by its ObjectType dependent on the ModellingRules specified for the components. However, the Server may add additional components and References to the Object
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.6.2 Variable NodeClass

most one ModellingRule Object using a HasModellingRule Reference (see 6.4.4 for details on ModellingRules ). HasProperty 0..* HasProperty References are used to identify the Properties of a DataVariable . Properties ... Variable can use at most one HasModellingRule Reference pointing to a ModellingRule Object . ModellingRules are defined in 6.4.4 . If the Variable is created based on an InstanceDeclaration
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.6.5 VariableType NodeClass

referenced Nodes may be instantiated by the instances of this type, depending on the ModellingRules defined in 6.4.4 . HasComponent 0..* HasComponent References are used for complex VariableTypes to identify their ... referenced Nodes may be instantiated by the instances of this type, depending on the ModellingRules defined in 6.4.4 . HasSubtype 0..* HasSubtype References identify VariableTypes that are subtypes of this type
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.6.6 Client-side creation of Variables of an VariableType

AddNodes Service contains all components defined by its VariableType dependent on the ModellingRules specified for the components. However, the Server may add additional components and References to the Variable
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.7.1 Method NodeClass

most one ModellingRule Object using a HasModellingRule Reference (see 6.4.4 for details on ModellingRules ). GeneratesEvent 0..* GeneratesEvent References identify the type of Events that may be generated whenever the Method ... Method can use at most one HasModellingRule Reference pointing to a ModellingRule Object . ModellingRules are defined in 6.4.4 . GeneratesEvent References identify that Methods may generate an Event of the specified
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.4.2 Creating an Instance

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 created hierarchy may be copies ... entire instance and will provide remote references to Nodes in another Server . The ModellingRules described in 6.4.4.4 allow Servers to indicate that some Nodes are always present; however, the Client
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.3 Constraints on an Instance

added to the 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
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.1 General

General For a definition of ModellingRules , see 6.4.4.4 . Other parts of this series of standards may define additional ModellingRules . ModellingRules are an extendable concept in OPC UA; therefore, vendors ... define their own ModellingRules . Note that the ModellingRules defined in this standard do not define how to deal with NonHierarchical References between InstanceDeclarations , i.e. it is Server -specific if those
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.3 Instantiation Rules for Properties of ModellingRules

Instantiation Rules for Properties of ModellingRules There are two different use cases when creating an instance 'A' based on a TypeDefinitionNode 'A_Type'. Either 'A' is used as normal instance ... InstanceDeclarations of 'A_Type' initially maintain the same ModellingRule as their InstanceDeclarations. The ModellingRules may be updated; the allowed changes to the ModellingRules of these Nodes are the same
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.4.1 Mandatory

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.2 Optional

created or an existing Node is referenced. In Figure 32 an example using the ModellingRules Optional and Mandatory is shown. The example contains an ObjectType Type_A and all valid ... Node to InstanceDeclaration F). Not considered in the example is if the instances have ModellingRules or not. It is assumed that each F is similar to the InstanceDeclaration
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

A.8 Defining ModellingRules

Defining ModellingRules New ModellingRules have to be defined if the predefined ModellingRules are not appropriate for the model exposed by the Server . Depending on the model used by the underlying ... system the Server may need to define new ModellingRules , since the OPC UA Server may only pass the data to the underlying system and this system
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.8.2.1 Description

shall be referenced that conforms to the InstanceDeclaration . The creation of Nodes with other ModellingRules is Server specific
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.22.3 EventFilter

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

6.3.2 ServerCapabilitiesType

Optional HasProperty Variable MaxByteStringLength UInt32 PropertyType Optional HasComponent Object OperationLimits -- OperationLimitsType Optional HasComponent Object ModellingRules -- FolderType Mandatory HasComponent Object AggregateFunctions -- FolderType Mandatory HasComponent Object RoleSet RoleSetType Optional HasProperty Variable MaxSessions ... Server , for example the maximum length of an array in a read Service call. ModellingRules is an entry point to browse to all ModellingRules supported by the Server . All ModellingRules
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.5 ModellingRuleType

ModellingRuleType ModellingRules are defined in OPC 10000-3 . This ObjectType is used as the type for the ModellingRules . It is formally defined in Table 62 . Table 62 - ModellingRuleType definition Attribute
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access

5.3.2.1 General

characteristics of AnalogItems . The types have identical semantics and Properties but with diverging ModellingRules for individual Properties . The Properties are only described once - in 5.3.2.2 . The descriptions apply
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.5.2 StateMachineType with a SubStateMachine using inheritance

effects and causes are shown, as well as type information for the States or ModellingRules . The "MyStateMachineType" contains an Object "MySubMachine" of type "AnotherStateMachineType
OPC-10030 – OPC Unified Architecture - Common Object Model: ISA-95

5.1.7.2 UMLAssociation

SourceNode, TargetNode UMLRole may be transformed into the restrictions of ReferenceType. UMLCardinality N/A Standard ModellingRules only affect instance declaration specified by subtypes of Hierarchical References . UMLAssociation Name BrowseName A name
OPC-30050 – OPC UA for PackML - Common Object Model: PackML

3.8 OPC UA Notation

Notation This standard uses the ModellingRules OptionalPlaceholder and MandatoryPlaceholder to define instance declarations, and defines a rule that the BrowseName of instance declarations having an OptionalPlaceholder or MandatoryPlaceholder ModellingRule
OPC-30110 – OPC UA for POWERLINK - POWERLINK: OPC Unified Architecture

5.2.1 POWERLINK Objects and their attributes

categories Mandatory (M), Optional (O) and Conditional (Cond). OPC UA defines the ModellingRules Mandatory and Optional. Since OPC UA does provide an ModellingRule which can be mapped to Conditional
OPC-30260 – OPC UA for OPEN-SCS - Serialization Object Model: OPEN-SCS

3.4 OPC UA Notation

Notation This standard uses the ModellingRules OptionalPlaceholder and MandatoryPlaceholder to define instance declarations, and defines a rule that the BrowseName of instance declarations having an OptionalPlaceholder or MandatoryPlaceholder ModellingRule
OPC-40082-4 – OPC UA interfaces for plastics and rubber machinery - Peripheral devices - Part 4: Dosing Systems

7.2 Identification and MachineryBuildingBlocks

provides basic information on a machine/device. For the InstanceDeclaration the ModellingRules of the Properties Model and DeviceClass are overridden to mandatory. The Object MachineryBuildingBlocks contains building blocks from
OPC-40084-1 – OPC UA interfaces for plastics and rubber machinery - Extrusion - Part 1: General Type Definitions

6.3 Identification and MachineryBuildingBlocks

provides basic information on a machine/device. For the InstanceDeclaration the ModellingRules of the Properties Model and DeviceClass are overridden to mandatory and the Property ControllerName is added. The Object MachineryBuildingBlocks