Search

56 result(s) for Asset

• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  3.1.1 Asset
  Asset Physical or logical elements of an 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
  6.2 UAFX Information Model
  information related to communication capabilities and diagnostic information. OPC 10000-81 formally describes AutomationComponent , Asset , and FunctionalEntity . A Connection is a logical relationship between FunctionalEntities for exchanging information and coordinating
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  3.3.2 Usage of Asset and FunctionalEntity
  Usage of Asset and FunctionalEntity Clause 6.3 defines an Asset as an Object either derived from FxAssetType or an Object of any type that implements the required Interfaces . Asset (plural
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  4.2 AutomationComponent model
  defined in this document. The AutomationComponentType is composed of two major sub-models: the asset model and the functional model. It also provides information related to OfflineEngineering ... Figure 1 illustrates this model. For a formal definition of the AutomationComponentType, see 6.2 . Asset information is typically used to describe physical items, but it can also include items that
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  4.3.1 Overview
  model for Assets in an OPC UA FX system (illustrated in Figure 2 ). An Asset is defined as a component with a lifecycle, where the lifecycle includes version information. FxAssetType ... provides a base concept of the asset model defined in this document. The OPC UA FX Information Model supports the modelling of hard Assets and soft Assets . A hard Asset
• 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 instances. It also contains vendor information and information from the model defined in OPC UA Devices (see OPC 10000-100 ). The asset model supports functionality to verify the identity
• 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
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.1 Overview
  establishment of Connections further requires concepts such as identity and compatibility verification of Asset and FunctionalEntity , establishing control via ControlGroup selection, setting ConfigurationData , and communication configuration. These concepts are mapped
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.2.2.1 Overview
  Overview Asset verification provides functionality to verify whether a given Asset's type and instance information match or are compatible with what was expected by system engineering. Applicable use cases ... during maintenance or shutdown); after conducting a firmware update to ensure the updated Asset is compatible with what was engineered; after replacing an Asset to ensure that the Asset
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.2.2.2 Asset identity
  Asset identity Asset identity refers to an Asset's properties that make unambiguous identification possible. The IAssetRevisionType VerifyAsset Method provides the possibility to verify an Asset's identity
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.2.2.3 Asset compatibility
  Asset compatibility This clause introduces the concept of Asset compatibility, which allows an Asset to report if it is compatible with what was expected by system engineering. An important ... unavailable, the vendor could be shipping a compatible substitute with updated hardware or firmware. Asset compatibility verification provides functionality to verify whether a specific Asset's properties match
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.2 AutomationComponentType definition
  device, controller, PLC, instrument, etc. It includes information related to the current Asset , the available functionality, its capabilities (including communication-related capabilities) and any related offline information. The AutomationComponentType ... TargetBrowsePath 3:FunctionalEntities 3:<FunctionalEntity> 0:IsHostedBy True 3:Assets 3:<Asset> The components of the AutomationComponentType have additional subcomponents, which are defined in Table
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.4.1 Overview
  ConnectionManager typically calls it. It allows for creating ConnectionEndpoints , establishing control, verifying FunctionalEntity and Asset compatibility, applying ConfigurationData , and configuring the communication model to be used for data exchange
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.4.2 EstablishConnections signature
  shall have at least one command bit set to TRUE. AssetVerifications Provides parameters for Asset verification. For a formal definition of the AssetVerificationDataType, see 10.5 . If CommandMask VerifyAssetCmd ... NodeIdInvalid The syntax of AssetToVerify is invalid. Bad_InvalidArgument AssetToVerify is not an Asset . Also, include all Result Codes in Table 32 . The possible StatusCodes for the ConnectionEndpointConfigurationResults FunctionalEntityNodeResult
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.3.2 FxAssetType definition
  Interface allows other device models to include what is required for OPC UA FX Asset modelling without having to implement the FxAssetType Object directly. Conformance testing shall test that ... Object that implements all of the Interfaces defined in FxAssetType is considered an Asset . Additional References are defined as part of the model to show relationships between Assets , within Assets
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.3.3 VerifyAsset method
  VerifyAsset method The VerifyAsset Method allows a Client to verify whether an Asset 's identity and functionality meet the expectations of system engineering. Three different modes are available for Asset ... present for verification. The VerifyAsset Method also accepts additional Variables for verification. An Asset implementing the VerifyAsset Method shall at least support the VerificationMode AssetCompatibility and expose the corresponding mandatory
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.3.4 AssetConnectorType definition
  AssetConnectorType definition The AssetConnectorType provides information about physical connections that are part of an Asset . An example of these connections might be slots in which cards can be mounted ... physical) ID of the connector, representing the physical location of the connector in the Asset . The use of this ID can be further explained or defined in subtypes. Name provides
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.3.5 SlotType definition
  physical slot to which a module can be attached, e.g., in a modular Asset like a PLC backplane or modular IO device. The SlotType is formally defined in Table ... subtype of it, or an IsPhysicallyConnectedTo Reference or a subtype of it, indicating the Asset that occupies the Slot
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.7.2 ConnectionManagerType definition
  records for a single call. For example, if there are multiple verification errors (e.g. Asset verification or FunctionalEntity verification), all would be logged. To facilitate tracking of LogRecords between
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.8.2 ConnectionConfigurationSetType definition
  represents one or more AutomationComponents . In addition, it holds the parameters used for Asset verification. For a formal definition, see 6.14 . RollbackOnError indicates the behaviour that should be followed when
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.14.2 AutomationComponentConfigurationType definition
  TRUE, specifies that the ConnectionManager shall bundle commands to this AutomationComponent . AssetVerification holds the Asset verification parameters for an Asset associated with this AutomationComponent . The AssetVerificationType is defined
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.15.1 Overview
  AssetVerificationType ObjectType holds the information to be used for compatibility verification of an Asset . The AssetVerificationType is illustrated in Figure 46 . Figure 46 - AssetVerificationType illustration
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.15.2 AssetVerificationType definition
  ExpectedAdditionalVerificationVariables 4:PortableNodeIdentifierValuePair[] 0:BaseDataVariableType M ConformanceUnits UAFX ConnectionManager Base AssetToVerify specifies the expected Asset to be verified. If a PortableRelativePath is specified, the path shall be relative to AutomationComponentNode ... verification (compatibility and/or identity). ExpectedVerificationResult is the expected level of compatibility that this Asset shall provide. ExpectedVerificationVariables hold the variables to be verified for compatibility and/or identity. It is expected
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  9.1.2 AggregatedHealthType definition
  Assets . The aggregation rules are defined as follows: If at least one top-level Asset has DeviceHealth set to Failure , the AggregatedDeviceHealth DeviceFailure bit shall be set. If at least ... level Asset has DeviceHealth set to Check_Function , the AggregatedDeviceHealth DeviceCheckFunction bit shall be set. If at least one top-level Asset has DeviceHealth set to Maintenance_Required , the AggregatedDeviceHealth
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  10.4 AssetVerificationModeEnum
  AssetVerificationModeEnum This enumeration represents the mode for Asset verification. The enumeration is formally defined in Table 127 . Table 127 - AssetVerificationModeEnum items Name Value Description AssetCompatibility 0 Verify whether an Asset ... compatible with the expectations of system engineering. AssetIdentity 1 Verify whether an Asset's identity meets the expectations of system engineering. AssetIdentityAndCompatibility 2 Verify whether an Asset's identity meets
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  10.5 AssetVerificationDataType
  AssetVerificationDataType This structured DataType contains information required for Asset verification to be used as arguments in a Method Call (e.g., EstablishConnections ). It is semantically equivalent to the AssetVerificationType as defined ... Structure defined in OPC 10000-5 AssetToVerify 0:NodeId Node identifier of the Asset to verify. VerificationMode 2:AssetVerificationModeEnum The VerificationMode to use for verifying the Asset . ExpectedVerificationResult 2:AssetVerificationResultEnum
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  10.6 AssetVerificationResultDataType
  AssetVerificationResultDataType This structure contains the result of Asset verification returned by the Method Call (e.g., EstablishConnections ). The structure is formally defined in Table 131 . Table 131 - AssetVerificationResultDataType structure Name Type ... defined in OPC 10000-5 VerificationStatus 0:StatusCode Indicates the operational status of the Asset verification method. If VerificationStatus is Bad , VerificationResult shall be set to NotSet, and VerificationResult shall
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  10.7 AssetVerificationResultEnum
  AssetVerificationResultEnum This enumeration represents the result of Asset verification. The enumeration is formally defined in Table 133 . Table 133 - AssetVerificationResultEnum items Name Value Description NotSet 0 The verification result ... Match 1 Asset matches expectation. Compatible 2 Asset does not match expectations but is compatible. Mismatch 3 Asset does not match expectations and is not compatible. The AssetVerificationResultEnum representation
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  11.2 ConnectedTo ReferenceType
  semantic of this ReferenceType is to link together Assets . This Reference indicates that the Asset the Reference points to is a part connected to the Asset , which is the starting ... SourceNode of this ReferenceType shall be an instance of AssetConnectorType (or subtypes) or an Asset . The TargetNode of this ReferenceType shall be an instance of AssetConnectorType (or subtypes
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  11.4 HasBuiltInAsset ReferenceType
  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 , which is the starting point ... 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 be extracted from the source
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  11.15 HasPart ReferenceType
  this ReferenceType is to link together FxAssetType instances. This Reference indicates that the Asset the Reference points to is a removable part inside the Asset . This implies that the part ... visible from the outside of the Asset . To gain access to the Asset, removing a component of the Asset (e.g., a hatch) is typically necessary. Also, it implies that both
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  11.18 IsPartOfRedundantAssetSet ReferenceType
  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 to redundancy ... Figure 63 - IsPartOfRedundantAssetSet Reference example The SourceNode of this ReferenceType shall be an Asset . The TargetNode of this ReferenceType shall be an Asset . The IsPartOfRedundantAssetSet ReferenceType is formally defined
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  B.2 Creating a new model based on OPC UA FX
  could define a fixed structure of Connectors or a structure for the given Asset . Creating sub-types might also define fixed Variable(s) that all instances would contain, such ... Information Model for a new vendor-specific specification. This is especially true for asset models, where a vendor would want to represent the hardware that they sell. Creating a customer/application-specific
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  B.3.2.1 Extending an existing type
  required UA FX functionality. The illustrated model does not create a separate FunctionalEntity and Asset since the existing model did not differentiate between the asset part and the logical functionality ... Interfaces, coupled with the already included IvendorNameplate Interface, fulfil the requirements for the asset model. The existing model already defines input/output/configuration data that would be required for a FunctionalEntity
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  D.2.1 Modelling of Asset relationships
  D.2.1 Modelling of Asset relationships The task of modelling an Asset is more than just describing a single simple Asset . It is modelling the relationships between the Assets ... ReferenceTypes will be illustrated in various examples in this annex: HasContainedComponent indicates that an Asset has another Asset contained in it. HasBuiltInAsset indicates that an Asset has an integrated Asset
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  D.2.2 Example single board computer model
  trademark of Raspberry Pi Ltd"), that can be modelled as an asset. This simple single-board computer has multiple items that can be modelled. It has many connector options ... including extension boards, external devices, and cables. The figure also includes a possible base asset model for the Raspberry Pi. This model does not include all features of a Raspberry
• 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 ... example, if Controller2's actual MinorAssetVersion is set to "9" but the Asset is still compatible with MinorAssetVersion "7", Compatible will be returned. The VerifyAsset Method
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  D.3.1 Overview
  DataSets and dynamically created DataSets . In later clauses, these examples are linked to the Asset examples to provide a more complete picture
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  D.3.2 Modelling of FunctionalEntity relationships
  FunctionalEntity has a nested FunctionalEntity . IsHostedBy indicates that a FunctionalEntity needs the referenced Asset to provide its functionality. IsExecutingOn r elates a FunctionalEntity to the execution environment it is currently
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  D.3.3 FunctionBlock example
  example FunctionalEntity model that could be applied to the single-board computer from the Asset example (MyRaspberryPi). The model shows a subtype of FunctionalEntityType that represents an execution engine that
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  D.3.6.1 Overview
  slots of the rack illustrated in D.2.3 . The FunctionalEntity related to this Asset will provide OutputData only. To keep the following examples simple, ConfigurationData (e.g., measurement range and unit
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  D.4.1 Raspberry Pi example
  full AutomationComponent . It omits some instances in nested Objects . This example links the Asset illustrated in D.2.2 for the SenseHat ( Figure D.5 ) with the FunctionalEntity example in D.3.3 ... Figure D.19 ). It shows the IsExecutingOn Reference between the MyApplicationProgram FunctionalEntity and the MyRaspberryPiInstance Asset. Figure D.34 - AutomationComponent example Figure D.35 provides a zoomed-in view of the AutomationComponent MyRaspberryPiAC
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  F.1.9 AutomationComponentConfigurationConfDataType
  that the ConnectionManager shall 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
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  F.1.12 AssetVerificationConfDataType
  F.1.12 AssetVerificationConfDataType The AssetVerificationDataConfType is used to store the information needed for Asset verification. It is semantically equivalent to the AssetVerificationType as defined in 6.15.2 . The AssetVerificationConfDataType is formally defined ... Subtype of Structure defined in OPC 10000-5 AssetToVerify 4:NodeIdentifier Specifies the expected Asset to be verified. If a RelativePath is specified, the path shall be relative to AutomationComponentNode
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  6.2 Descriptor with product information
  product. In OPC UA FX, the information of the AutomationComponent product contains the Asset and functional structure, (pre-configured) DataSets , capabilities, and the property name defined ... functional structure is typically defined. In the case of a modular device, that asset structure contains some flexibility, e.g., connectors and slots that can be attached to a defined
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  6.3 Descriptor with configuration information
  subscriber capabilities. For modular devices, the configuration may also include the definitions for the Asset structure, e.g., installed modules. For machines and modular process skids that are supplied
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  8.4 Example workflow for sharing a Descriptor in OfflineEngineering
  downloaded together with the user programs into the Controllers . The yellow FunctionalEntity and Asset boxes represent the Information Model of the AutomationComponent(s ) in the Controllers . The FunctionalEntities contain input
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  F.1.1 AutomationComponent modelling example
  Model can be divided into four steps: Instantiation of the AutomationComponentType; Creation of the Asset structure; Creation of the FunctionalEntity structure; Creation of the (preconfigured) DataSets. The AML Information   Model
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  F.1.3 Creation of the Asset structure
  F.1.3 Creation of the Asset structure In the next step, the Asset structure of the modular Controller is created using the FxAssetType SUC, which is provided ... Libraries. In Figure F.3 , the Asset structure is shown. The first Asset is the backplane chassis R35_Rack, which can host modules through connector slots. Figure F.3 - R35B_Rack with
• OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles
  5.2.4 UAFX FxAsset
  UAFX FxAsset Table 5 describes Asset -related UAFX Information Model ConformanceUnits. For additional information about these items, please refer to OPC 10000‑81 . Table 5 - UAFX FxAsset Category Title Description ... DeviceHealth DeviceHealthAlarms ConformanceUnit. FxAsset Server UAFX FxAsset Type Exposes the FxAssetType. Server UAFX Asset Base Supports at least one instance of the FxAssetType , or a subtype
• OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles
  6.6.2.15 UAFX IAssetExtensions Diagnostic Counters Facet
  UAFX IAssetExtensions Diagnostic Counters Facet. This Facet includes the functionality needed for tracking Asset resource utilization. Table 29 - UAFX IAssetExtensions Diagnostic Counters Facet Group Conformance Unit / Profile Title Optional UAFX
• OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles
  6.6.2.16 UAFX Asset Facet
  UAFX Asset Facet Table 30 describes the details of the UAFX Asset Facet. This 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 DI IVendorNameplate Server Facet DI ITagNameplate Server Facet DI IDeviceHealth Server Facet UAFX FxAsset UAFX
• OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles
  6.6.5.5 UAFX Offline Descriptor Asset Facet
  UAFX Offline Descriptor Asset Facet Table 62 describes the details of the UAFX Offline Descriptor Asset Facet. This Facet includes the content elements necessary for describing an Asset ... UAFX Descriptor file. Table 62 - UAFX Offline Descriptor Asset Facet Group Conformance Unit / Profile Title Optional UAFX OfflineEngineering UAFX Descriptor Asset Base False UAFX OfflineEngineering UAFX Descriptor Asset SoftwareUpdate False
• OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles
  Agreement of Use
  functionality" from the Base Bridge Component 2024 Facet description. 9802 Errata Missing Descriptor Asset Base content ConformanceUnit Added new ConformanceUnit requiring the Descriptor to describe an Asset Object
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.7.5 Solution packages
  String SerialNumber (see 4.5.2 ). True FxPath[] 2:FxPathElement Path to a UA FX Asset ( OPC 10000-81 ). True FxScope[] 2:FxPathElement The package shall only be installed to targets behind ... used to restrict the installation to targets which are connected to that asset. This can, for example, be combined with FxPath . If a TargetBrowsePath is specified, the target is identified