Search

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

20 result(s) for Mandatory

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.7.2 EventTypes

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

4.10.2 Interface Model

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 not be the source of HasInterface ... Interface with a HasInterface Reference or a subtype, the following rules apply: Each mandatory InstanceDeclaration of the fully-inherited InstanceDeclarationHierarchy of the Interface shall have for each BrowsePath a similar
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.3 Instantiation Rules for Properties of ModellingRules

changed (lower part of the Figure). A1 has become the NamingRule of Mandatory (changed from Optional
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.2 Optional

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 combinations of instances ... named A1 to A13. Note that if the optional B is provided, the mandatory E has to be provided as well, otherwise not. F is referenced
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.4.4 OptionalPlaceholder

InputArguments and OutputArguments . A subtype shall also change the ModellingRule to Optional or Mandatory . The Method is optional for instances. For example, a Device might have a Method to perform
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.4.5 MandatoryPlaceholder

subtype defines the InputArguments and OutputArguments . A subtype shall also change the ModellingRule to Mandatory . The Method is mandatory for instances
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-4 – OPC Unified Architecture - Part 4: Services

5.8.2.1 Description

Variable depending on the ModellingRule of each InstanceDeclaration . All Nodes with a ModellingRule of Mandatory shall be created or an existing Node shall be referenced that conforms to the InstanceDeclaration
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 ... Attribute Value BrowseName Mandatory References NodeClass BrowseName Comment HasTypeDefinition ObjectType ModellingRuleType Defined in 6.5 Conformance Units Base Info Base Types
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.7 UAInstance

ParentNodeId for other instances. This implies that child Nodes , even Mandatory ones, are not added to the Node. The HasTypeDefinition reference shall be specified
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.2 ConditionType

Clause 5.6.2 HasSubtype ObjectType AcknowledgeableConditionType Defined in Clause 5.7.2 HasProperty Variable ConditionClassId NodeId PropertyType Mandatory HasProperty Variable ConditionClassName LocalizedText PropertyType Mandatory HasProperty Variable ConditionName String PropertyType Mandatory HasProperty Variable BranchId ... NodeId PropertyType Mandatory HasProperty Variable Retain Boolean PropertyType Mandatory HasProperty Variable SupportsFilteredRetain Boolean PropertyType HasComponent Variable EnabledState LocalizedText TwoStateVariableType Mandatory HasComponent Variable Quality StatusCode ConditionVariableType Mandatory HasComponent Variable LastSeverity UInt16
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

3.3.1 Usage of Other column in type definitions

shown in Table 1 . Table 1 - Examples of Other Characteristics Name Short Name Description Mandatory M The Node has the Mandatory ModellingRule . Optional O The Node has the Optional ModellingRule
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.3.1.1 Node definitions

Table 3 . Table 3 - Examples of other characteristics Name Short Name Description 0:Mandatory M The Node has the Mandatory ModellingRule . 0:Optional O The Node has the Optional ModellingRule
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

3.3.1.1 Node definitions

Table 3 . Table 3 - Examples of Other Characteristics Name Short Name Description 0:Mandatory M The Node has the Mandatory ModellingRule . 0:Optional O The Node has the Optional ModellingRule
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping

3.3.1.1 Node definitions

Table 3 . Table 3 - Examples of Other Characteristics Name Short Name Description 0:Mandatory M The Node has the Mandatory ModellingRule . 0:Optional O The Node has the Optional ModellingRule
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

3.3.1 Conventions for Node descriptions

Table 3 . Table 3 - Examples of Other Characteristics Name Short Name Description 0:Mandatory M The Node has the Mandatory ModellingRule . 0:Optional O The Node has the Optional ModellingRule
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

3.4.1.1 Node definitions

Examples of Other Characteristics Name Short Name Description M M The Node has the Mandatory ModellingRule . O O The Node has the Optional ModellingRule. MPlaceholder MP The Node
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

3.4.1.1 Node definitions

Table 3 . Table 3 - Examples of Other characteristics Name Short Name Description 0:Mandatory M The Node has the Mandatory ModellingRule . 0:Optional O The Node has the Optional ModellingRule