Search
31 result(s) for FunctionalGroups
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelConfigurationDataFolderType is defined in 6.4.6 . The ConfigurationData Folder may also contain two FunctionalGroups ( Configuration or Tuning ) to further organise configuration information. The optional Configuration FunctionalGroup contains Variables representing the configuration
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelFunctionalGroupType, as defined in OPC 10000-100 , includes the ability to have nested FunctionalGroups . It is expected that configuration data will often be organised into a tree of FunctionalGroups . This
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devicesgeneric model for elements in a device or component topology. Among others, it introduces FunctionalGroups , ParameterSet , and MethodSet . Figure 2 shows the TopologyElementType . It is formally defined in Table ... term TopologyElement generically refers to an instance of any ObjectType derived from the TopologyElementType . FunctionalGroups are an essential aspect introduced by the TopologyElementType . FunctionalGroups are used to structure Nodes like
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices4.4.1 Modeluseful in different application scenarios and therefore referenced from more than one FunctionalGroup . FunctionalGroups can be nested. FunctionalGroups can directly be instantiated. In this case, the BrowseName of a FunctionalGroup ... current state of the TopologyElement the Server can decide to hide or unhide certain FunctionalGroups or (part of) their References . If a FunctionalGroup can be hidden on an instance
-
OPC-10000-100 – OPC Unified Architecture - Part 100: DevicesWell-Known FunctionalGroup BrowseNames Table 15 includes a list of FunctionalGroups with name and purpose. If Servers expose a FunctionalGroup that corresponds to the described purpose, they should ... defined in the OperationCounter Interface (see 4.5.5 ). This FunctionalGroup can be organized into other FunctionalGroups , so Clients shall expect that several browse hops are required to get to all OperationCounters
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices4.4.3 UIElement Typesuch a user interface and display it on the Client side. The hierarchy of FunctionalGroups represents the tree of user interface elements. The UIElementType is abstract and is mainly used
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices4.11 BlockTypeBlockType is a subtype of TopologyElementType and inherits the elements for Parameters , Methods and FunctionalGroups . The BlockType is abstract. There will be no instances of a BlockType itself, but there
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices6.3.1 Generalrepresented by two instances that are schematically identical, i.e., there exist component Objects , FunctionalGroups, and so on. A Reference connects online and offline representations and allows to navigate between them ... driven by the same ObjectType . According to their usability, certain components ( Parameters , Methods , and FunctionalGroups ) can exist only in either the online or the offline element. A Parameter
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics10.3 Operation Countersprovide the 2:OperationCounters FunctionalGroup as well. This FunctionalGroup might be organized into other FunctionalGroups , so Clients shall expect that they need to browse several hops
-
OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices6.1.3.1 Object RuntimeParametersvendor specific runtime parameters of AutoID Devices shall be exposed below this FunctionalGroup . FunctionalGroups can be nested. The runtime parameters may be also exposed in other parts of the AutoID
-
OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices6.1.3.2 Object IODataconfiguration specific IO data of AutoID Devices shall be exposed below this FunctionalGroup . FunctionalGroups can be nested. The IO data may also be exposed in other parts of the AutoID
-
OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices6.1.3.3 Object DiagnosticsAutoID Device . All diagnostics data of AutoID Devices shall be exposed below this FunctionalGroup . FunctionalGroups can be nested. The diagnostics data may also be exposed in other parts
-
OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>12.2.3 FunctionalGroupTypedefined in ParameterSet and MethodSet ) in a user-friendly way (see Table 63 ). FunctionalGroups may be organized hierarchically by organizing FunctionalGroups as child nodes of FunctionalGroups . Table 63 - FunctionalGroupType mapping
-
OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>information model, the representation hierarchies of IData interfaces and IFunction interface are combined into FunctionalGroups to provide a concise representation of the device data and methods within one hierarchy. This
-
OPC-30110 – OPC UA for POWERLINK - POWERLINK: OPC Unified Architecture6.2.1 GeneralParameters ( Variables ) of the ParameterSet and Methods of the MethodSet are organised in FunctionalGroups where they are referenced by Organize-References . This concept allows splitting the Parameters into different categories
-
OPC-40223 – OPC UA for Pumps and Vacuum Pumps3.2.2 FunctionalGroupspecific ObjectType like OperationalGroupType, ActuationType, or DesignType. EXAMPLE 1 The pump P1 has the FunctionalGroups Identification, Design, and Operational
-
OPC-40223 – OPC UA for Pumps and Vacuum Pumps3.2.5 Pumpdescribed pump types defined in this specification. EXAMPLE 1 The pump P1 has the FunctionalGroups Identification, Design, and Operational
-
OPC-40223 – OPC UA for Pumps and Vacuum Pumps6.2 Model OverviewTopologyElementType defined. Figure 7 shows the general relationships between the PumpType and the FunctionalGroups . Figure 7 - Pumps & Vacuum Pumps Information Model (General - Structure
-
OPC-40223 – OPC UA for Pumps and Vacuum PumpsDefinitionThe PumpType is the representation of a Pump and organizes its properties in FunctionalGroups . It is illustrated in Figure 9 and formally defined in Table 9 . Figure 9 - Illustration
-
OPC-40223 – OPC UA for Pumps and Vacuum PumpsMaintenanceGroupType ObjectType DefinitionThe MaintenanceGroupType provides FunctionalGroups for general maintenance and specific maintenance strategies, such as condition based maintenance, preventive maintenance, and breakdown maintenance. It is illustrated in Figure
-
OPC-40223 – OPC UA for Pumps and Vacuum PumpsConfigurationGroupType ObjectType DefinitionThe ConfigurationGroupType provides FunctionalGroups for static manufacturer data about the Pump and user data about the Pump's process environment. General information on this use case
-
OPC-40223 – OPC UA for Pumps and Vacuum PumpsOperationalGroupType ObjectType DefinitionThe OperationalGroupType provides FunctionalGroups that collect Nodes for process data that is used during normal Pump operation, such as measurements, signals, and actuation. It is illustrated
-
OPC-40223 – OPC UA for Pumps and Vacuum PumpsDrivePortType ObjectType DefinitionThe DrivePortType extends its supertype by FunctionalGroups for Pump drive specific Objects and Variables and is formally defined in Table 82 . Table 82 - DrivePortType Definition Attribute Value
-
OPC-40223 – OPC UA for Pumps and Vacuum PumpsInletConnectionPortType ObjectType Definition The InletConnectionPortType extends its supertype by FunctionalGroups for Pump inlet specific Objects and Variables and is formally defined in Table 84 . Table 84 - InletConnectionPortType Definition Attribute Value
-
OPC-40223 – OPC UA for Pumps and Vacuum PumpsOutletConnectionPortType ObjectType Definition The OutletConnectionPortType extends its supertype by FunctionalGroups for Pump outlet specific Objects and Variables and is formally defined in Table 86 . Table 86 - OutletConnectionPortType Definition Attribute Value
-
OPC-40250-1 – OPC UA for Compressed Air Systems - Part 1: Main Control Systems3.2.8 FunctionalGroupspecific ObjectType like OperationalType, AnalysesType, or DesignType. EXAMPLE 1 The compressor C1 has the FunctionalGroups Identification, Design, and Operational
-
OPC-40250-1 – OPC UA for Compressed Air Systems - Part 1: Main Control SystemsExtending FunctionalGroups The manufacturer or system integrator of a Compressed Air System may wish to add Variables , Objects , or Methods which are not yet defined by this specification. In such ... purpose of the Variable . Figure 12 illustrates some usage examples on how to extend FunctionalGroups of a compressor. Figure 12 - Extending FunctionalGroups
-
OPC-40250-1 – OPC UA for Compressed Air Systems - Part 1: Main Control Systemsrepresentation of a Compressed Air System and provides both Objects for Quantities and FunctionalGroups for its Airnets , Components , and the Main Control System . It is illustrated in Figure
-
OPC-40250-1 – OPC UA for Compressed Air Systems - Part 1: Main Control SystemsAirnetType is the representation of an Airnet and provides both Objects for Quantities and FunctionalGroups . It is illustrated in Figure 19 and formally defined in Table 17 . Figure 19 - AirnetType
-
OPC-40250-1 – OPC UA for Compressed Air Systems - Part 1: Main Control Systemsrepresentation of a Main Control System and provides both Objects for Quantities and FunctionalGroups . It is illustrated in Figure 21 and formally defined in Table 21 . Figure 21 - MCSType Illustration
-
OPC-40250-1 – OPC UA for Compressed Air Systems - Part 1: Main Control SystemsCASComponentType is the representation of a Component and provides both Objects for Quantities and FunctionalGroups . It is illustrated in Figure 22 and formally defined in Table 23 . Figure 22 - CASComponentType