Search

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

41 result(s) for Assets

OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

3.1.1 Asset

AutomationComponent Note 1 to entry: See OPC 10000-81 for a description of Assets
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

4.2 Architecture

Information Model is the AutomationComponent . The AutomationComponent is an entity representing one or more Assets that may perform automation functions represented by FunctionalEntities . The AutomationComponent can also provide health status
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

5.4.1 General

Descriptor (see 6.4 ). See OPC 10000-83 for more details regarding OfflineEngineering and Descriptors . Assets and FunctionalEntities being used in applications, their available input, output, and configuration data, and communication
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

6.2 UAFX Information Model

entity that performs one or more automation functions. All AutomationComponents are composed of Assets and FunctionalEntities . An AutomationComponent also contains information related to communication capabilities and diagnostic information
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

3.3.2 Usage of Asset and FunctionalEntity

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 an Object , regardless
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.2 AutomationComponent model

sensor functionality, actuator functionality, or more complex logical items. FunctionalEntities can be related to Assets, and the representation of such relationships is included in the model. Both Assets and FunctionalEntities
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.3.1 Overview

Overview This Information Model provides a general model for Assets in an OPC UA FX system (illustrated in Figure 2 ). An Asset is defined as a component with a lifecycle ... this document. The OPC UA FX Information Model supports the modelling of hard Assets and soft Assets . A hard Asset represents physical hardware like devices, controllers, modules, hardware components
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.3.2 Asset information

Asset information The asset model (illustrated in Figure 3 ) requires that Assets provide a minimum level of information. This includes Asset type identification as well as the unique identification ... asset model supports functionality to verify the identity and compatibility of the Assets . For a complete description of the FxAssetType, see 6.3 . Figure 3 - Asset model
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.3.3 Asset model relationships

Asset model relationships The asset model provides a means for representing the relationships between Assets . It also supports the concept that there might be multiple types of relationships between various ... Assets . These types of relationships might be used to provide multiple views of the asset model. For example: Asset management view Physical hierarchy view Maintenance view Interconnected view (network, electrical
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.5 Relationships between FunctionalEntities and Assets

Relationships between FunctionalEntities and Assets Assets can be related to FunctionalEntities . A single Asset might be related to zero or more FunctionalEntities . A FunctionalEntity might be related to zero ... more Assets . The models for both FunctionalEntities and Assets are independent. Specific References only link them (see Figure 7 for an illustration and 11.1 for details on ReferenceTypes ). Figure
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.2.1 Overview

that AutomationComponents match system engineering expectations during commissioning or initiating communication (e.g., detecting missing Assets like IO modules in a modular IO system); replacing or updating an AutomationComponent ... expected way. This document defines verification modes and a verification Method for Assets , which provides the possibility to verify an Asset's identity and whether or not it performs
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.2.2.1 Overview

Applicable use cases include: commissioning an automation system (e.g., a machine) to ensure all Assets in an engineered system are from the expected manufacturer and are the expected model; prior
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.5.3 Establishing and closing Connections

BrowsePath to the AutomationComponent , FunctionalEntity , etc., optional parameters to be used for verifying the Assets and FunctionalEntities , optional parameters to be used for establishing control, optional parameters to be used
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.6 Health

Health Assets , FunctionalEntities , ConnectionEndpoints , and ConnectionConfigurationSets provide general health status and diagnostic conditions. This health status is aggregated from child objects to parent objects (e.g., from ConnectionEndpoints to the FunctionalEntity ... other than "good" is reported, aggregated health status indicates the elements (e.g., Assets ) which need more investigation
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.8 Aggregation of OPC UA FX Servers

AutomationComponent(s) can be reflected in a higher-level Server . This reflection can include Assets and FunctionalEntities , but it is expected that the communication model (between FunctionalEntities ) will only exist
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.1 Overview

Overview The AutomationComponentType ObjectType provides for a grouping of Assets and FunctionalEntities in a given model. It exposes a Method that is used to establish Connections between FunctionalEntities . An overview
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.2 AutomationComponentType definition

HasComponent Object 3:FunctionalEntities 0:FolderType M 0:HasComponent Object 3:Assets 0:FolderType M 0:HasComponent Object 3:PublisherCapabilities 3:PublisherCapabilitiesType O 0:HasComponent Object 3:SubscriberCapabilities 3:SubscriberCapabilitiesType ... Reference Type IsForward TargetBrowsePath 3:FunctionalEntities 3:<FunctionalEntity> 0:IsHostedBy True 3:Assets 3:<Asset> The components of the AutomationComponentType have additional subcomponents, which are defined
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.3.2 FxAssetType definition

Asset . Additional References are defined as part of the model to show relationships between Assets , within Assets , and between Assets and FunctionalEntities and the overall AutomationComponent model ... same ManufacturerUri ." Within this model, ProductInstanceUri, SerialNumber, or both shall be provided for Assets listed directly in the Assets Folder of the AutomationComponent . " RevisionCounter is an incremental counter
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.3.3 VerifyAsset method

AssetIdentityAndCompatibility : All mandatory Variables of both AssetCompatibility and AssetIdentity are mandatory for top-level Assets (those directly in the Assets Folder in the AutomationComponent ). All optional Variables of AssetCompatibility
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.3.4 AssetConnectorType definition

AssetConnectorType . Figure 23 - AssetConnectorType subtypes illustration Some connector types are used to link other Assets , while other AssetConnectorTypes might be used to indicate physical connections
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.3.2 Establishing Connections

required configuration information Command Description Relevant types from configuration model VerifyAssetCmd Verify that the Assets are the ones expected by system engineering. The argument AssetVerifications that is passed for this
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

9.1.1 Overview

AggregatedHealthType is a subtype of the BaseDataVariableType and holds the aggregated health of Assets and FunctionalEntities . The AggregatedHealthType is illustrated in Figure 51 . Figure 51 - AggregatedHealthType illustration
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

9.1.2 AggregatedHealthType definition

AggregatedDeviceHealth shall be the aggregation of the DeviceHealth of the AutomationComponent's top-level Assets . The aggregation rules are defined as follows: If at least one top-level Asset
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.1 AggregatedHealthDataType

AggregatedDeviceHealth 3:DeviceHealthOptionSet Aggregation of the DeviceHealth of the AutomationComponent's top-level Assets AggregatedOperationalHealth 3:OperationalHealthOptionSet Aggregation of the OperationalHealth of the AutomationComponent's top-level FunctionalEntities The AggregatedHealthDataType
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.19 ConnectionDiagnosticsDataType

affect only a subset of all Connections in the set, e.g. failure to verify Assets on a single AutomationComponent affects all Connections that have ConnectionEndpoints in that AutomationComponent . Finally, some
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.21 DeviceHealthOptionSet

DeviceHealthOptionSet This OptionSet defines flags indicating the aggregated health of the Assets . The DeviceHealthOptionSet values are formally defined in Table 166 . Table 166 - DeviceHealthOptionSet values Value Bit No. Description DeviceFailure ... least one of the top-level Assets has its DeviceHealth set to Failure . DeviceCheckFunction 1 At least one of the top-level Assets has its DeviceHealth set to Check_Function
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.23 FxCommandMask

Description VerifyAssetCmd 0 The addressed Server shall verify compatibility and/or identity for all requested Assets . VerifyFunctionalEntityCmd 1 The addressed Server shall verify compatibility for all requested functional entities. CreateConnectionEndpointCmd
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

11.2 ConnectedTo ReferenceType

subtype of IsPhysicallyConnectedTo ReferenceType . The semantic of this ReferenceType is to link together Assets . This Reference indicates that the Asset the Reference points to is a part connected ... starting point of the Reference by means of an electrical cable. Typically, the Assets are at different physical locations, even if the physical location is not a great distance
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

11.4 HasBuiltInAsset ReferenceType

subtype of HasContainedComponent ReferenceType . The semantic of this ReferenceType is to link together Assets . It indicates that the Asset the Reference points to is an integral part of the Asset ... starting point of the Reference . Asset information is provided for spare part handling of Assets that are related to the source Assets . HasBuiltInAsset also means that the Target cannot
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

11.15 HasPart ReferenceType

Asset (e.g., a hatch) is typically necessary. Also, it implies that both Assets have the same physical location and, therefore, the same Asset location information. An example of this Reference
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

11.18 IsPartOfRedundantAssetSet ReferenceType

subtype of NonHierarchicalReferences ReferenceType . The semantic of this ReferenceType is to link Assets that are redundant. An Asset may have multiple IsPartOfRedundantAssetSet References . This Reference provides no additional information related ... redundancy; it only indicates Assets that are part of a redundant set. It is illustrated in Figure 63 . Figure 63 - IsPartOfRedundantAssetSet Reference example The SourceNode of this ReferenceType shall
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

12.2 FxRoot

instances related to OPC UA FX. It may contain multiple AutomationComponents that include Assets and FunctionalEntities . It may also contain, at most, one ConnectionManager . NOTE AutomationComponents are part
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

B.3.2.1 Extending an existing type

This AutomationComponent instance would just reference the existing MyModelInstance from both the Assets Folder and the FunctionalEntities Folder . It is important to understand that this is just an illustration ... Interfaces could be added to separate objects if the companion specification separates functionality from assets. When to use: When it is important to extend an existing companion specification or vendor
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.1 Overview

examples for each part of the OPC UA FX Information Model . This includes individual Assets examples, individual FunctionalEntity examples and examples of an AutomationComponent that includes both Assets and FunctionalEntities
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.2.1 Modelling of Asset relationships

than just describing a single simple Asset . It is modelling the relationships between the Assets . In OPC UA, relationships can be modelled as References , where a Reference provides semantic information ... number of References in OPC 10000-23 that can be used for modelling Assets . This list is extended by this document. The following ReferenceTypes will be illustrated in various examples
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.2.4 Verifying Assets

D.2.4 Verifying Assets A Client verifies whether an Asset meets the expectations of system engineering. This example demonstrates how to use verification. It uses the rack example. Figure D.14 - Sample ... Assets of a chassis-based controller Figure D.14 illustrates the Assets of a rack-based Controller . The vendor modelled a 12-slot rack with Connectors , a communications module
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.1.2 Single logical connection

this logical connection. AC_A and AC_B contain the parameters for verifying Assets . AC_A and AC_B could optionally include the PubSubCommunicationModelConfiguration, PubSubModelA and PubSubModelB
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.9 AutomationComponentConfigurationConfDataType

bundle commands to this AutomationComponent . False AssetVerification 4:AssetVerificationConfDataType[] The Asset verification parameters for Assets associated with the AutomationComponent . If the optional AssetVerification is not available, the field is null
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

6.6.2.16 UAFX Asset Facet

includes the functionality needed for an Asset that is referenced directly by the AutomationComponentType Assets Folder . Table 30 - UAFX Asset Facet Group Conformance Unit / Profile Title Optional UAFX IAssetRevision Facet
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

8.1 Overview

Overview For the discovery of assets, this specification uses the concept of AliasNames , as defined in OPC 10000-17 . AliasNames define an additional name for any Node of a Server ... define additional names for a Node / asset, but use the provided information of the assets. That is, this specification defines two standardized categories for AliasNames , one using the mandatory
OPC-30140 – OPC UA for PROFINET

6.3.1.3.1 IPnEquipmentType

HasComponent Object Interfaces PnInterfaceContainerType Mandatory HasComponent Object Modules PnRealModuleContainerType Optional HasComponent Object Assets PnAssetContainerType Optional HasComponent Object IM PnIdentificationType Optional HasProperty Variable Vendor String PropertyType Optional HasComponent Variable Diagnosis PnDeviceDiagnosisDataType ... accordance with the I&M0FilterDataDevice block (See [PN TAD] - Identification & Maintenance). The Assets and IM objects are optional. If the interface is used with the OPC UA facet