Search

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

25 result(s) for Interfaces

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

4.10.1 Overview

aggregate an object which provides several functions instead of over-using inheritance [GH95] , [FF04] . Interfaces and AddIns complement the type model and can be used when subtyping is not suitable
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.10.2 Interface Model

Interface Model Interfaces are ObjectTypes that represent a generic feature (functionality), assumed to be usable by different ObjectTypes or Objects . The Interface model specifies the rules and mechanisms to achieve ... InterfaceTypes " Object (see OPC 10000-5 ) has been defined so that all Interfaces of the Server are either directly or indirectly accessible browsing HierarchicalReferences starting from this Node . Rules
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.19 HasInterface ReferenceType

described in 4.10.2 . The SourceNode of this ReferenceType shall be an Object or ObjectType . Interfaces shall not be a SourceNode . The TargetNode shall be of a subtype of the BaseInterfaceType ... SourceNode can refer to multiple Interfaces
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.9 BaseInterfaceType

BaseInterfaceType The BaseInterfaceType ObjectType is the super-type for Interfaces . All subtypes of BaseInterfaceType shall be abstract. There are no References specified for this ObjectType . It is formally defined ... DataType TypeDefinition ModellingRule Subtype of the BaseObjectType defined in 6.2 . Conformance Units Address Space Interfaces
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

8.2.11 InterfaceTypes

This standard Object Node is the browse entry point for ObjectType Nodes that represent Interfaces . Figure 8 illustrates the structure beneath this Node showing some of the standard ObjectTypes defined ... clause 6. Only Organizes References are used to relate Objects and Interfaces to the " InterfaceTypes " standard Object . The " InterfaceTypes " Object shall not reference any other NodeClasses
OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model

4.2 Usage of OPC UA Interfaces

Usage of OPC UA Interfaces The parameters of the BNM are grouped in the form of OPC UA Interfaces . Interfaces have been chosen to define parameter sets independent
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

6.2 UAFX Information Model

based on the basic building blocks provided in OPC 10000-5 and utilises Interfaces and ObjectTypes described in OPC 10000-100 . This base Information Model can, in turn, be utilised
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

3.3.2 Usage of Asset and FunctionalEntity

either derived from FxAssetType or an Object of any type that implements the required Interfaces . Asset (plural Assets ) is used throughout this document to designate an instance of such ... Object , regardless of whether derived from the type or implementing the Interfaces . Subclause 6.4 defines a FunctionalEntity as an Object either derived from FunctionalEntityType or an Object of any type
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.4.3 FunctionalEntity type hierarchy

Figure 6 for examples of possible derivations). The model is defined using OPC UA Interfaces . An Information Model defined in another standard can add support for FunctionalEntities by including these ... Interfaces or by deriving from the FunctionalEntityType . Figure 6 - Example FunctionalEntityType
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.1 OPC UA FX ObjectTypes overview

create an OPC UA FX Information Model . It also specifies a number of Interfaces that can be applied to existing Information Models , allowing existing models to be used as part
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.2 AutomationComponentType definition

subtype of it or instances that implement the IVendorNameplateType , ITagNameplateType , and IAssetRevisionType Interfaces . The Folder may be empty; however, typically, there is at least one entry in this Folder
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.3.1 Overview

model. The figure includes an illustration of the Nodes that are added via the Interfaces . Figure 21 - FxAssetType overview
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.3.2 FxAssetType definition

FxAssetType Object directly. Conformance testing shall test that the required information, defined by the Interfaces included in the FxAssetType , is available, not that the Object is of FxAssetType . Any Object ... that implements the Interfaces defined in FxAssetType that are required in profiles is considered an Asset . Additional References are defined as part of the model to show relationships between Assets
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

7.1 Overview

Overview This clause defines all of the Interfaces defined in this document. These Interfaces will be used internally in this model and will be available for companion specifications. Figure ... illustrates the Interfaces that are defined in this document. The definition of the components that are part of the Interface is provided in the Object Model that utilizes the Interface
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

B.1 Overview

This can be accomplished in several ways: by a simple mapping by using Interfaces (see B.3.2 ) by using AddIns (see B.3.3 ) Defining a parallel OPC UA FX model and linking
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

B.3.1 Overview

part of its model. These additions could be accomplished using Interfaces or via AddIns ; examples of both are provided. Figure B.2 illustrates the original model defined in the example specification
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

B.3.2.1 Extending an existing type

B.3.2.1 Extending an existing type The Interfaces defined in the OPC UA FX Information Model can be added to an existing specification model to extend the model for providing ... background colour added to help visualize the additions. Figure B.3 - Extending type definition with Interfaces The new model includes the ITagNameplate Interface (defined in OPC 10000-100 ) that is required
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

B.3.2.2 Extending an instance of an existing type

objects or to instances. The OPC UA FX Information Model can be included via Interfaces into an instance of an existing Information Model . This type of update is illustrated ... Figure B.4 Figure 4. Figure B.4 - Extending an instance with Interfaces This set of extensions is very similar to what is described in Annex B.3.2.1 , but the Interfaces are applied
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

6.5.2 UAFX Station requirements

UAFX Station shall: comprise a conformant IA-station , support middleware modelling of network interfaces and QoS in the UAFX communication and application layer: priority mapping configuration representation as defined ... representation as defined in OPC 10000-22, including the IetfBaseNetworkInterfaceType , the IIetfBaseNetworkInterfaceType and IIeeeBaseEthernetPortType Interfaces , and the NetworkInterfaces Folder (see  ); C-VLAN configuration representation as defined
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

A.8 InterfaceType mapping

InterfaceType mapping OPC UA Interfaces are used to add a defined group of elements to an Object in an alternate way than containment or inheritance, similar to the way interfaces ... object-oriented programming (OOP) language. Interfaces in OOP and OPC UA help alleviate some of the limitations of a single inheritance model by allowing an Object to "implement
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

4.5.1 Overview

Overview This clause describes Interfaces with specific functionality that can be applied to multiple types at arbitrary positions in the type hierarchy. Interfaces are defined in OPC 10000-3 . Figure ... shows the Interfaces described in this specification. Figure 4 - Overview of Interfaces for Devices and Device components
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

4.7 DeviceType

Multiple ConnectionPoints can exist if multiple protocols and/or multiple Communication Profiles are supported. The Interfaces and their members are described in 4.5 . Some of the Properties inherited from the ComponentType
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

C.5 Guidelines on how to use functionality in companion specifications

companion specification only wants to reuse other aspects of this specification, defined in the Interfaces in 4.5 or the AddIns "Locking" in 7 or software update ... from the ObjectTypes defined in this specification. Instead of, it can just implement the Interfaces or use the AddIns in their ObjectTypes and build an ObjectType -Hierarchy independent of this
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

7 Identification of Asset

IVendorNameplateType and 2: ITagNameplateType . An Object representing an asset can either directly implement those interfaces, or has a TypeDefinition directly or indirectly implementing the interfaces. Usage of 2: Identification Object ... with default values when the value cannot be provided. The 2: ComponentType and the Interfaces define the Properties as optional, i.e., they should be omitted when the information cannot
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

6.1 Overview

Overview The Interfaces defined in this chapter can be used to manage statistical data. It provides an infrastructure to manage the statistical data, but no concrete statistical data are defined