Search

57 result(s) for AutomationComponents

• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  3.1.5 ConnectionManager
  ConnectionManager entity that interacts with AutomationComponents to establish Connections between FunctionalEntities Note 1 to entry: See OPC 10000-81 for a description of the ConnectionManagerType
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  3.1.10 Descriptor
  multi-document file (zip package) containing information for using and configuring one or more AutomationComponents Note 1 to entry: A Descriptor contains Information Model files and other artefacts. Note
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  3.1.14 OfflineEngineering
  OfflineEngineering design phase activity, where, based on data from the vendors of the AutomationComponents , the configuration for AutomationComponents is planned (typically without the hardware available), which gets deployed
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  5.2 The UAFX Solution
  UAFX Solution OPC UA FX specifies a standardised Information Model and connection model for AutomationComponents , providing timely data delivery, security, and functional safety. Interactions addressed by UAFX include Controller
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  5.4.1 General
  defines a mechanism for standardising the exchange of information used for establishing Connections between AutomationComponents (see 6.2 ) in an OfflineEngineering environment (see 6.4 ). From initial AutomationComponent development to on-site
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  6.1 Controller-to-Controller communication
  controller, or something else. All communication partners are modelled as AutomationComponents defined in OPC 10000-81 . An AutomationComponent provides an abstract model that allows vendors to describe the Controller ... automation functions, and a standard interface for Connections that provides interoperability for exchanging data. AutomationComponents, Assets, and FunctionalEntities also include identification information, allowing compatibility to be verified for each Connection
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  6.2 UAFX Information Model
  Model . An AutomationComponent is an 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
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  6.4 OfflineEngineering
  structured set of documents describing the functionality, capabilities, and configuration of the AutomationComponents . Descriptors may also contain supporting documentation such as user manuals and drawings
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  6.5 Profiles
  UAFX Profiles are defined in OPC 10000-84 . All OPC UA AutomationComponents will support one or more Profiles and any or all of its optional Facets
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  4.2 AutomationComponent model
  AutomationComponent model This model is provided to model AutomationComponents in OPC UA FX. In OPC UA FX, an AutomationComponent is an entity that performs one or more automation functions
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  4.3.3 Asset model relationships
  dynamic during operation. OPC UA FX defines a minimum asset model that all AutomationComponents are required to support. Figure 4 - Illustration of asset views
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  4.7.1 Overview
  Overview A ConnectionManager is an optional entity that interacts with multiple AutomationComponents to establish Connections between FunctionalEntities . The ConnectionManager can execute on any Server supporting the OPC UA FX Information
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  4.7.2 Creating / Monitoring / Closing Connections
  Possible reasons for monitoring Connection status include: An application or ConnectionManager monitors ConnectionEndpoints on AutomationComponents to decide whether it needs to (re)establish or close Connections . For example: On startup ... diagnostic applications monitor Connections defined in ConnectionConfigurationSets on a ConnectionManager and the ConnectionEndpoints on AutomationComponents to present comprehensive Connection information to the operator or engineers, including identification information, current status
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.2.1 Overview
  identity and compatibility verification refer to the process and mechanisms used to check that AutomationComponents (e.g., controllers, drives, IO devices) in a system allow operation that is consistent or compatible ... expected by system engineering. It is a common practice that various properties of communicating AutomationComponents are verified to check that: AutomationComponents present in a system are either consistent with system
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.2.2.1 Overview
  expected model; prior to or at the initiation of data communication between AutomationComponents to ensure nothing has been (adversely) changed (e.g., during maintenance or shutdown); after conducting a firmware update
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.5.2 Generation, deployment, and modification
  information. OfflineEngineering (see OPC 10000-83 ) offers the concept of Descriptors that describe the AutomationComponents ; see Figure 11 label 1. Using these Descriptors or retrieving information online from the AutomationComponents
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.5.3 Establishing and closing Connections
  application that is always executing. The ConnectionManager calls the EstablishConnections Method on the AutomationComponents to establish the logical connections. For each logical connection to be established, the ConnectionConfigurationSet includes: address ... Client invoking the ProcessConnectionConfigurationSets Method. The ConnectionManager calls the CloseConnections Method on the AutomationComponents to close the logical connections
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.5.5 Persistent and preconfigured objects
  Persistent and preconfigured objects Establishing logical connections can involve creating several Objects within the AutomationComponents . Persistence refers to the ability of AutomationComponents to store configuration, which allows these Objects
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.5.6.2.1 Overview
  three use cases relevant in the context of industrial automation and the design of AutomationComponents . These are just illustrations. Additional or different uses might also apply. The grey-blue boxes
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.5.6.2.2 Single Connection using unicast network messages
  Figure 12 , describes a single logical connection between two FunctionalEntities located on the AutomationComponents A and B, each containing a Publisher , a Subscriber , and a single PubSubConnectionEndpoint . Both FunctionalEntities could ... references a DataSetReader and DataSetWriter . The PubSub instances are configured to exchange data between AutomationComponents AC_A and AC_B using unicast NetworkMessages
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.5.6.2.3 Multiple Connections using unicast network messages
  using unicast network messages This use case, illustrated in Figure 13 , typically applies to AutomationComponents that host multiple FunctionalEntities and/or nested FunctionalEntities . Figure 13 - Multiple Connections using unicast network messages
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.5.6.2.4 Multiple Connections using multicast network messages
  Figure 14 , could be applied to an AutomationComponent (AC_A) communicating with multiple AutomationComponents (AC_B and AC_C). To minimize network bandwidth usage in specific topologies ... published data into a single NetworkMessage , which is sent via multicast to the associated AutomationComponents AC_B and AC_C. In turn, AC_B and AC_C publish an individual
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.8 Aggregation of OPC UA FX Servers
  this document can be aggregated. This subclause provides some explanation regarding the aggregation of AutomationComponents and ConnectionManagers . The AutomationComponent(s) can be reflected in a higher-level Server . This reflection ... data for higher-level applications such as HMIs or advanced control applications. Multiple AutomationComponents from multiple Servers could be included under a single AggregatingServer . An AggregatingServer can expose a ConnectionManager
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.4.3.1 Overview
  bundled commands that is issued individually, i.e., not issued in a bundle. NOTE    AutomationComponents that have CommandBundleRequired set to TRUE could be restricted regarding the size of the Arguments issued
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.7.3.2 Establishing Connections
  sequence of Calls illustrated in Figure 36 to the EstablishConnections Method on the involved AutomationComponents . See Figure 35 for an illustration of the configuration information contained in the ConnectionConfigurationSet ... Figure 36 - Command sequence illustration A ConnectionManager shall call the EstablishConnections Method on the AutomationComponents , passing in one or several commands to be executed together with their required arguments
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.7.3.3 Closing Connections
  Connections defined in a ConnectionConfigurationSet , a ConnectionManager shall use the CloseConnections Method on the AutomationComponents (see 6.2.5 ). A ConnectionManager may remove or disable the Connections . If CloseConnections returns any error
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.8.2 ConnectionConfigurationSetType definition
  ServerAddress> represents one or more instances of ServerAddressType, which defines addressing information for AutomationComponents . For a formal definition, see 9.2 . There may be fewer instances of this type than ... ConnectionConfigurations . <AutomationComponentConfiguration> 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
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.16.3.2 PubSubCommunicationModelConfigurationType definition
  CommunicationLinks (see 6.12.2 ). For examples of how to establish the configuration information for AutomationComponents, see E.2 , and for the SKS, see E.5 . The ConfigurationValues Variable contains the names and identifiers ... created with the default PublisherId . The ConnectionManager shall adapt the PubSubConfiguration of subscribing AutomationComponents with the returned PublisherIds as required. It is recommended to use ElementAdd for WriterGroups and ReaderGroups
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  12.2 FxRoot
  entry point for all 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 ... part of the Server , i.e. the Server exposes the AutomationComponents as instances. In the world of a physical Controller , there would only be one instance of an AutomationComponent
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  13.5 ConnectionManager error reporting
  with an SKS (local or remote). The ConnectionManager reports errors related to interactions with AutomationComponents . This includes any errors that are reported to the ConnectionManager from invoking the EstablishConnections Method
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  C.1 OPC UA Safety Information Model
  Safety defines how to exchange safety data between AutomationComponents using either Client Server or PubSub as the underlying OPC UA communication model. Client Server support for logical connections will
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  E.1.1 Overview
  single logical connection between two FunctionalEntities , multiple logical connections between FunctionalEntities located on two AutomationComponents , or multiple logical connections between FunctionalEntities located on multiple AutomationComponents . The following examples illustrate
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  E.1.2 Single logical connection
  present on the ConnectionManager ) and their resulting runtime elements (present or created on the AutomationComponents being part of the logical connection) is indicated by dashed arrows. Figure E.1 - ConnectionConfigurationSet overview
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  E.1.3.1 Overview
  E.1.3.1 Overview Multiple logical connections can be configured between two or more AutomationComponents using unicast or multicast communication. Examples for each of the options are illustrated
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  E.1.3.2 Multiple logical connections - two AutomationComponents
  E.1.3.2 Multiple logical connections - two AutomationComponents Figure E.2 depicts the configuration elements contained in a ConnectionConfigurationSet and their relation to each other for multiple logical connections between two AutomationComponents . Often ... traffic between two AutomationComponents will be optimized to use one NetworkMessage . EndpointA1 and EndpointA2 share PubSubCommunicationFlowConfiguration Flow1 with a ToOutboundFlow Reference and share SubscriberConfiguration SubA with a ToInboundFlow Reference
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  E.1.3.3 Multiple logical connections - multiple AutomationComponents
  E.1.3.3 Multiple logical connections - multiple AutomationComponents Figure E.4 depicts the configuration elements contained in a ConnectionConfigurationSet and their relation to each other for multiple logical connections among multiple AutomationComponents . Figure
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  E.2.1 Overview
  particular AutomationComponent can be retrieved by following the References starting at each of the AutomationComponents listed in the ConnectionConfigurationSet . The ConnectionManager iterates through the AutomationComponentConfigurations . The ConnectionManager establishes a secure ... contained in the configuration information (see 13.3.3 ). NOTE   The interaction of the ConnectionManager with AutomationComponents to establish Client Server -based Connections will be provided in a future version of this
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  E.2.2.1 For logical connections between two AutomationComponents
  E.2.2.1 For logical connections between two AutomationComponents For PubSub as a communication model, OPC 10000-14 requires certain configuration values (e.g., PublisherId , WriterGroupId , and DataSetWriterId ) to match the Publisher ... simple example, where a ConnectionManager processes a ConnectionConfigurationSet containing logical connections between two AutomationComponents , the sequence illustrated in Figure E.7 could be used. Figure E.7 - Sequence for establishing connections
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  E.2.2.2 For logical connections between multiple AutomationComponents
  E.2.2.2 For logical connections between multiple AutomationComponents Multiple logical connections across multiple AutomationComponents could require more steps. Assume that a ConnectionManager must establish a ConnectionConfigurationSet containing logical connections between multiple ... AutomationComponents . Figure E.8 illustrates an example of such a ConnectionConfigurationSet . For this scenario, the ConnectionManager could set up the logical connections as follows: The ConnectionManager calls EstablishConnections
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  E.4.7 PubSub DataSets
  single network message. For example, if the ConnectionConfigurationSet has three Connections between two AutomationComponents (different FunctionalEntities ), the PubSub configuration might be a single DataSet with all the required Variables . Alternatively ... might be three DataSets in a single network message. If more AutomationComponents are in the set, it might even be a multicast network message that multiple AutomationComponents could be subscribing
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  E.5 Interaction with an SKS
  push model, the set of keys is pushed by the SKS to the AutomationComponents using SetSecurityKeys. In the pull model, the set of keys is pulled by the AutomationComponents from ... configuration is finished, the SKS will start to periodically push the keys to the AutomationComponents registered with the push targets . A push target will accept keys only if they
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  F.1.3 ConnectionConfigurationSetConfDataType
  apply to Connections. True ServerAddresses 4:ServerAddressConfDataType[] A list of addressing information for AutomationComponents . False AutomationComponentConfigurations 4:AutomationComponentConfigurationConfDataType[] A list of AutomationComponents used for Connection establishment. False RollbackOnError 0:Boolean
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  F.3.3.2.3 ElementRemove
  empty by the caller. The ConnectionManager shall call the CloseConnections Method on all affected AutomationComponents (see 6.2.5 ) with Remove set to TRUE for all Connections contained in the ConnectionConfigurationSet
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  F.3.3.2.4 ElementReplace
  ConnectionConfigurationSet in the ConnectionConfigurationSetFolder. The ConnectionManager shall call the CloseConnections Method on all affected AutomationComponents (see 6.2.5 ) with Remove set to TRUE for all contained Connections in the ConnectionConfigurationSet
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  G.1 Diagnostics Client
  Status , then the diagnostics Client will have to obtain status from each of the AutomationComponents participating in the Connection (see AutomationComponent_2 internal connection in illustration) . If a ConnectionManager reports
• OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking
  5.6.4.5 Connection establishment and operation
  PubSubCommunicationFlowConfiguration. To this end, the ConnectionManager invokes the EstablishConnections Method on the AutomationComponents that reference the FunctionalEntities being connected, as depicted in Figure 12 label A. For details on Address
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  1 Scope
  participants in the OfflineEngineering workflow. OfflineEngineering is a design phase activity. The configuration for AutomationComponents is planned (typically without the hardware available), implemented, and later deployed to the physical/logical elements ... Descriptor as a means for capturing the information for using and configuring AutomationComponents in the OfflineEngineering phase, including the Information Model defined in OPC 10000-81 . This document outlines
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  4 Overview
  from one engineering tool to another ( Figure 2 ). They also share Information Models of AutomationComponents ( Figure 3 ). Figure 2 - Engineers work in sequence on the Information Model of one AutomationComponent ... Figure 3 - Engineers mutually exchange Information Models of AutomationComponents In order to facilitate the exchange and storage of Information Models and data between Controls Engineers , the concept of " Descriptor
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  5.1 Descriptor fundamentals overview
  Descriptor defines the information for using and configuring one or more AutomationComponents . This information may contain data provided by the vendor of the AutomationComponent or configuration data produced by Controls
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  6.2 Descriptor with product information
  project in OfflineEngineering , a Controls Engineer needs access to product information for the AutomationComponents that have been selected. Traditionally, this information is available on the vendor's website
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  6.3 Descriptor with configuration information
  products, the configuration may include the full assembly of the hardware from other AutomationComponents , together with the configuration for each part. Configuration information dependent on use cases for information sharing
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  6.4 Descriptor with product family information
  family information A Descriptor can also be used to share the product information of AutomationComponents building a product family. By a product family, one usually understands a range of similar
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  8.4 Example workflow for sharing a Descriptor in OfflineEngineering
  share data with Engineer B to design the exchange of data between the AutomationComponents (e.g., Controller-to-Controller communication). Engineering tools are expected to support the engineer in this task
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  H.1 Overview
  engineering information from the different disciplines to allow the modelling of physical and logical AutomationComponents . An object in AutomationML is the data representation of an automation object or a group
• OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles
  5.1 Overview
  UAFX Controllers and devices . UAFX AutomationComponent Defines ConformanceUnits for various features of AutomationComponents . UAFX FxAsset Defines ConformanceUnits for various features of FxAssets . UAFX FunctionalEntity Defines ConformanceUnits for various features
• OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles
  5.2.6 UAFX ConnectionManager
  UAFX Client ConnectionManager Bundled Commands Is capable of issuing commands in a bundle for AutomationComponents that require a bundle
• OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles
  6.6.2.2 UAFX AutomationComponent 2024 Facet
  UAFX AutomationComponent 2024 Facet. This Facet includes the functionality common to all AutomationComponents . It supersedes the UAFX AutomationComponent Facet. Table 16 - UAFX AutomationComponent 2024 Facet Group Conformance Unit / Profile Title