Search

65 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 InstanceDeclaration­Hierarchy 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
• OPC-10031-4 – OPC UA for ISA-95 - Part 4: Job Control
  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
• OPC-30020 – MDIS OPC UA Companion Specification
  2.3 MDIS Mandatory & Optional Items / Objects
  MDIS Mandatory & Optional Items / Objects MDIS has standardised on the following definitions for Mandatory and Optional items. In all cases ( Mandatory or Optional ), if the item is available ... functionality described by the definition of the item must be correct and verifiable. Mandatory Objects specified as Mandatory will be required in all Objects and cannot be deleted
• OPC-30020 – MDIS OPC UA Companion Specification
  6.2.1 Overview
  section details the MDIS generic properties for the MDISBaseObjectType . Implementations shall ensure adherence to Mandatory [M] aspects in order to comply with the MDIS interface standardisation. Optional
• OPC-30020 – MDIS OPC UA Companion Specification
  6.2.2 MDISBaseObjectType Definition
  Object from what is described in this specification, which includes support for any Mandatory items. Profiles are described in section 14.3 . Fault - The status of the object, true
• OPC-30020 – MDIS OPC UA Companion Specification
  6.3.2 Overview
  section details the MDIS generic properties for the MDISDiscreteInstrumentObjectType . Implementation shall ensure adherence to Mandatory [M] aspects in order to comply with the MDIS interface standardisation. Optional
• OPC-30020 – MDIS OPC UA Companion Specification
  6.4.2 Overview
  section details the MDIS generic properties for the MDISDigitalInstrumentObjectType ; implementation shall ensure adherence to Mandatory [M] aspects in order to comply with the MDIS interface standardisation. Optional
• OPC-30020 – MDIS OPC UA Companion Specification
  6.5.2 Overview
  section details the MDIS generic properties for the MDISInstrumentObjectType . Implementation shall ensure adherence to Mandatory [M] aspects in order to comply with the MDIS interface standardisation. Optional
• OPC-30020 – MDIS OPC UA Companion Specification
  6.6.2 Overview
  valve found in subsea production and water injection trees. Implementation shall ensure adherence to Mandatory [M] aspects in order to comply with the MDIS interface standardisation. Optional
• OPC-30020 – MDIS OPC UA Companion Specification
  6.7.2 Overview
  valve found in subsea production and water injection trees. Implementation shall ensure adherence to Mandatory [M] aspects in order to comply with the MDIS interface standardisation. Optional
• OPC-30020 – MDIS OPC UA Companion Specification
  6.8.2 Overview
  manual and / or actuated (hydraulic or pneumatic) valves. Implementation shall ensure adherence to Mandatory [M] aspects in order to comply with the MDIS interface standardisation. Optional
• OPC-30020 – MDIS OPC UA Companion Specification
  6.8.3 MDISValveObjectType Definition
  additional detail see 6.14.3 . 0:HasProperty Variable 0:Writable 0:Boolean 0:PropertyType Mandatory 0:HasProperty Variable 0:UserWritable 0:Boolean 0:PropertyType Mandatory Vendor specific subtypes of this ObjectType ... They may add additional vendor specific information or may change some Optional items to Mandatory . A standard file content is defined in Annex E . The MDISValveObjectType is a subtype
• OPC-30020 – MDIS OPC UA Companion Specification
  6.9.2 Overview
  will address the CIMV found in subsea production trees. Implementation shall ensure adherence to Mandatory [M] aspects in order to comply with the MDIS interface standardisation. Optional
• OPC-30020 – MDIS OPC UA Companion Specification
  6.10.2 Overview
  section details the MDIS generic properties for the MDISCounterObjectType . Implementation shall ensure adherence to Mandatory [M] aspects in order to comply with the MDIS interface standardisation. Optional
• OPC-30020 – MDIS OPC UA Companion Specification
  6.11.2 Overview
  section details the MDIS generic properties for the MDISMotorObjectType . Implementation shall ensure adherence to Mandatory [M] aspects in order to comply with the MDIS interface standardisation. Optional
• OPC-30020 – MDIS OPC UA Companion Specification
  6.12.1 Overview
  following tables detail the generic properties for the MDISAggregateObjectType ; implementation shall ensure adherence to Mandatory [M] aspects to comply with the MDIS interface standardisation. Optional
• OPC-30020 – MDIS OPC UA Companion Specification
  10.5.2 Object Collection, Aggregation and Extension Definition
  newly created subtype of an MDIS ObjectType . Yes Change ModellingRule from Optional -> Mandatory for any of existing properties or components. Yes Table 123 describes rules for creating an aggregate
• OPC-30050 – OPC UA for PackML - Common Object Model: PackML
  4.3.4.3 Companion Specifications
  ModellingRule Subtype of the BaseObjectType from OPC 10000-5 . HasProperty Variable Color String PropertyType Mandatory HasProperty Variable Flavor LocalizedText PropertyType Mandatory HasProperty Variable Rank Int32 PropertyType Mandatory The BrowseName ... ObjectType or VariableType for the child. The ModellingRule indicates whether a child is Mandatory or Optional . It can also indicate cardinality. Note that the BrowseName is not defined
• OPC-30050 – OPC UA for PackML - Common Object Model: PackML
  6.3.6 PackMLBaseStateMachineType
  FiniteStateMachineType defined in OPC 10000-5 HasComponent Variable 0:AvailableTransitions NodeId[] BaseDataVariableType Mandatory HasComponent Variable 0:AvailableStates NodeId[] BaseDataVariableType Mandatory HasComponent Object Aborting StateType HasComponent Object Aborted StateType HasComponent Object ... Cleared StateType HasComponent Object MachineState PackMLMachineStateMachineType Mandatory HasComponent Object AbortedToCleared TransitionType HasComponent Object AbortingToAborted TransitionType HasComponent Object ClearedToAborting TransitionType HasComponent Method Abort Defined in 6.7.5 Optional HasComponent Method Clear Defined
• OPC-30050 – OPC UA for PackML - Common Object Model: PackML
  6.3.7 PackMLMachineStateMachineType
  Subtype of the FiniteStateMachineType from OPC 10000-5 . HasComponent Variable 0:AvailableTransitions NodeId[] BaseDataVariableType Mandatory HasComponent Variable 0:AvailableStates NodeId[] BaseDataVariableType Mandatory HasComponent Object Stopped StateType HasComponent Object Stopping StateType ... HasComponent Object Clearing StateType HasComponent Object Running StateType HasComponent Object ExecuteState PackMLExecuteStateMachineType Mandatory HasComponent Object StoppingToStopped TransitionType HasComponent Object ClearingToStopped TransitionType HasComponent Object StoppedToRunning TransitionType HasComponent Object RunningToStopping TransitionType HasComponent
• OPC-30060 – OPC UA for Tobacco Machine Communication
  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
• OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™
  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
• OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>
  3.3.3.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-30141 – OPC UA for PROFIenergy
  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
• OPC-30142 – OPC UA for PROFINET Remote IO
  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
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  3.5.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-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model
  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
• OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives
  3.5.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-30200 – OPC UA for Commercial Kitchen Equipment
  5.2.3.1 DeviceClass Property
  property DeviceClass of the DeviceType is overwritten in order to change the ModellingRule to Mandatory . The DeviceClass Strings used for this specification are defined in Table
• OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics
  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
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  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
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  8.1 Overview
  IMachineryItemVendorNameplateType refines the usage of the Properties defined in 2:IVendorNameplateType , changes some to Mandatory and defines additional Properties . IMachineVendorNameplateType uses those definitions and makes another Property mandatory. IMachineTagNameplateType
• OPC-40020-1 – OPC UA for Cranes and Hoists - Part 1: Base Model Motion Devices System
  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
• OPC-40210 – OPC UA for Geometric Measurement Systems
  4.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
• OPC-40501-1 – OPC UA for Machine Tools - Part 1: Machine Monitoring and Job Management
  3.4.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-40503-1 – OPC UA for Metal Forming - Part 1: General
  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
• OPC-40504-1 – OPC UA for Cutting Tools - Part 1: Manufacturing
  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
• OPC-40505 – OPC UA for Wireless Machine Tool Peripherals
  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
• OPC-40540 – OPC UA for Additive Manufacturing
  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
• OPC-40560 – OPC UA for Mining - General
  3.2.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-40570 – OPC UA for Wire Harness Manufacturing
  3.4.1.1 Node definitions
  Table 3 . Table 3 - Examples of Other CharacteristicsCharacteristics Name Short Name Description 0:Mandatory M The Node has the Mandatory ModellingRule . 0:Optional O The Node has the Optional ModellingRule
• OPC-40700 – OPC UA for Surface Technology - General Types
  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-40702 – OPC UA for Surface Technology - Organic Coating Technology - Material Supply Systems
  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-40702 – OPC UA for Surface Technology - Organic Coating Technology - Material Supply Systems
  8.1 Conformance Units
  least one instance of STSysMaterialTransportLineType on the Server. The instance has all mandatory Nodes . Server MSS STSysMaterialTransportLineType Monitoring There is at least one instance of STSysMaterialTransportLineType on the Server ... instance has all mandatory Nodes and the optional Node Monitoring including at least one of the optional Nodes underneath. Server MSS STSysMaterialTransportLineType Description There is at least one instance
• OPC-40718 – OPC UA for Surface Technology - Shot Blasting Machinery
  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
• OPC-40719 – OPC UA for Plasma Surface Technology
  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