Search
64 result(s) for Descriptor
-
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts3.1.10 DescriptorDescriptor 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 ... entry: The primary purpose of a Descriptor is to provide and share information for OfflineEngineering
-
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts5.4.1 GeneralFrom initial AutomationComponent development to on-site commissioning, engineers exchange offline data using the Descriptor (see 6.4 ). See OPC 10000-83 for more details regarding OfflineEngineering and Descriptors . Assets ... output, and configuration data, and communication capabilities are shared between engineers using Descriptors . The Descriptor allows product and system configuration data to be added by different engineers using their engineering
-
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts5.4.3 Application engineeringinputs and outputs to be shared. Engineer A then exports an updated, signed Descriptor with the shared information. Engineer B then imports this Descriptor using Controller B's engineering tool ... Controller A needs data from Controller B, it would need to import a Descriptor from Controller B to understand its interface. Figure 4 - Engineering workflow - design and commissioning Engineer
-
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and ConceptsUAFX OfflineEngineering Specification, OPC 10000-83 , defines a standardised archive file called a Descriptor for provisioning and sharing the information required for OfflineEngineering . The contents of a Descriptor
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model5.5.6.2.5 DataSetMetaDataanother engineering tool can update a FunctionalEntity, including its preconfigured DataSets . In addition, the Descriptor can describe a different version of the FunctionalEntity to be connected at runtime. This
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelAcDescriptorType definition An instance of AcDescriptorType is used to represent a Descriptor . This Object shall include either a DescriptorFile or the pair of DescriptorIdentifier and DescriptorVersion . It may include ... PropertyType O 0:HasComponent Object 3:DescriptorFile 0:FileType O ConformanceUnits UAFX AutomationComponent Descriptor The optional DescriptorIdentifier provides a globally unique identifier of the Descriptor of the AutomationComponent
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model13.1 OverviewServices ( Read ). The details related to an application's configuration are provided in a Descriptor , but the engineering tool associated with a ConnectionManager may not be able to resolve Node ... information beyond what is in the Descriptor , which results in a ConnectionManager requiring support for all of the Node resolution options
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelD.2.4 Verifying Assetsrack and have their ManufacturerUri set " http://ACME.com" . Assume that the Descriptor contains for CPU1: ProductCode "ZY456", MajorAssetVersion "2", MinorAssetVersion
-
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking5.6.4.1 Generalbetween two Controllers , i.e., data is only shared in one direction, requiring a single Descriptor describing this data to be exported from an engineering tool describing one of the Controllers
-
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking5.6.4.2 Application and QoS engineeringController A using this Controller's engineering tool. Engineer A also exports a Descriptor that is shared with Engineer B to complete the UAFX Application configuration. The exported Descriptor includes ... much as Engineer A did for Controller A. Engineer B also imports the Descriptor exported by Engineer A into Controller B's engineering tool, allowing Engineer B to configure
-
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking5.6.4.4 System integrationdeployment of the UAFX Station uses different values, as available in the Descriptor in 5.6.4.2 . Clause 5.6.4.2 describes the Information Model objects and Variables involved in making these adjustments
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering1 Scopecommissioning phase at a plant. This document defines the concept of a Descriptor as a means for capturing the information for using and configuring AutomationComponents in the OfflineEngineering phase, including ... This document outlines the OfflineEngineering processes and required functionality where the Descriptor is consumed or produced by the engineering tools. How engineering tools implement the processes and functionality
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering4 Overviewstorage of Information Models and data between Controls Engineers , the concept of " Descriptor " is introduced, as shown in Figure 4 . The Descriptor takes the shared information and organizes ... information in a formal electronic format with defined properties. The Descriptor allows for standardized exchange of data between Controls Engineers and engineering tools. Figure 4 - Engineers and Engineering Tools exchange
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringDescriptor fundamentals overview An OPC UA FX Descriptor defines the information for using and configuring one or more AutomationComponents . This information may contain data provided by the vendor ... AutomationComponent or configuration data produced by Controls Engineers in the OfflineEngineering phase. A Descriptor is a digitally signed multi-document file ( AML Container ) containing Information Model files in the AutomationML
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringDescriptor organization A Descriptor is based on the AML Container format and the Open Packaging Conventions standard. It has the file name extension ".amlx". A descriptor comprises ... five kinds of files (see Figure 6 ). It contains a Descriptor manifest file and Information Model file(s) and can contain attachment files, embedded Descriptors, or Common Services . Figure
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringReferences in a Descriptor The Descriptor concept supports URI-based references as the mechanism to link files and content together. References can be used to link to content included ... Descriptor (internal references) or to reference resources outside the Descriptor (external references). For example, a Descriptor created by a Controls Engineer containing configuration information for an AutomationComponent usually contains
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringInformation Model files A Descriptor shall contain at least one AML Information Model file. An OPC UA FX AML Information Model file is an AML file that contains an Information ... that are used in an Information Model file can either be included in the Descriptor or externally referenced from the Descriptor . Included libraries can be present in the Information Model
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringDigital signature fundamentals In order to provide integrity and authenticity for the Descriptor's content, a Descriptor contains one or more digital signatures. Digital signatures do not prevent the data ... Descriptor from being changed. However, engineering tools using the Descriptor can detect whether the content has been altered and notify the user. A Descriptor contains at least one digital signature
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringDescriptor examples overview The following subclauses describe some examples of Descriptors being used in OfflineEngineering . These subclauses are not introductions to special definitions of Descriptors . The intention is to demonstrate ... that a Descriptor , depending on the use case, can contain different information
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringDescriptor with product information When starting a project in OfflineEngineering , a Controls Engineer needs access to product information for the AutomationComponents that have been selected. Traditionally, this information is available ... connectors and slots that can be attached to a defined set of modules. A Descriptor with product information is usually created by the AutomationComponent vendor. It contains the vendor
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringDescriptor with configuration information A Descriptor with configuration information contains the Information Model that incorporates the configuration of AutomationComponent . The product information can also be part of a Descriptor with ... cases for information sharing: When engineering the same AutomationComponent by multiple Controls Engineers , a Descriptor with configuration information may contain a full snapshot of the configuration state. For example
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringDescriptor with product 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 ... Descriptors . Each member of a product family or subfamily is described by its own Descriptor with product information. All these Descriptors are embedded in a new Descriptor for the product
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringDescriptor for modular AutomationComponents In this example, the product information for a modular AutomationComponent that has been pre-configured with a known set of allowable modules is considered. In this ... either attached to the head end or to slots in a chassis. A Descriptor with product information for this modular AutomationComponent can contain the following elements: one or more Information
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering7.1 OverviewOverview This clause gives the formal definitions for the Descriptor concept
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering7.2 File formatFile format A Descriptor shall be an AutomationML Container file with the file name extension ".amlx
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering7.3.1 OverviewOverview The Descriptor content is organized into files and folders. A Descriptor contains several kinds of files: The Descriptor manifest, Information Model files, attachment files, embedded Descriptors , and Common Services ... This is illustrated in Figure 17 . There is no prescribed folder structure for the Descriptor . The files of a specific kind are identified by Open Packaging Conventions relationships
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering7.3.2 Descriptor manifestDescriptor manifest The UAFX Descriptor manifest is an XML file that defines the metadata for a Descriptor . The UAFX Descriptor manifest is structured according to the schema defined in Annex ... UAFX Descriptor manifest file shall be identified by an Open Packaging Conventions relationship of type "" stored in the container relationship file "_rels/.rels". There shall be exactly
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering7.3.3 Information Model fileslibraries. There shall be at least one Information Model file present in a Descriptor . The organization of the Information Model files is explained in 5.4 and 7.5.2 . The content ... Descriptor shall correspond to the online UAFX Information Model Profiles as described in the UAFX Offline Descriptor Profile (see OPC 10000-84 and http://opcfoundation.org/UA-Profile/UAFX-Offline-Descriptor-Profile ). Information Model and AutomationML
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering7.3.4 Attachment filesAttachment files A Descriptor may include one or more Attachment files. Attachment files are any files that are neither manifest files, Information Model files, Embedded Descriptors , or common service files ... attachment file shall be listed in the [Content_Types].xml file of a Descriptor . (See 7.6 ) Attachment files are identified by an Open Packaging Conventions relationship of type
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering7.3.5 Embedded DescriptorsEmbedded Descriptors A Descriptor may include one or more Embedded Descriptor s. Embedded Descriptors shall be compliant with all Descriptor requirements defined in the UAFX Offline Descriptor Profile ... Embedded Descriptor files shall be identified by an Open Packaging Conventions relationship of type
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering7.3.6 Common Services filesCommon Services files The following Common Services files shall be present in a Descriptor : "[Content_Types].xml" file is located in the top-level folder "/"; NOTE
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering7.4 Root AML FilesRoot AML Files The entry points into the content of a Descriptor are the Root AML Files, as they are defined by the AML Container format ... Root AML file shall be an OPC UA FX Information Model file. A Descriptor shall have at least one Root AML file. Root AML Files are identified by an Open
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering7.5.1 OverviewOverview Descriptor references have targets that are either in the Descriptor (internal references) or outside of the Descriptor (external references). The target of a Descriptor reference can be a file ... file. Three mechanisms are used for file and content references in a Descriptor : Open Packaging Conventions relationships which can be used for internal and external references, AutomationML ExternalDataReference interfaces, AutomationML
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringreference targets. The reference targets can be internal or external to the Descriptor . This is denoted by the "TargetMode" attribute. Every relationship reference shall have a valid ... clause 6.5.3.4). All Information Model attachments and embedded Descriptors in a Descriptor shall be the target of a relationship reference, and all these files shall be reachable from the Root
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringfile. The target can be inside or outside of the Descriptor . The URI syntax, including the Pack URI syntax for reference targets contained in Descriptors, shall be used to define ... derived from ExternalDataReference. An example of an ExternalDataReference to a document contained in a Descriptor is shown in Figure 20 , with the code following the figure. Figure 20 - Example
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringcontained in an AML file. The target can be inside or outside of the Descriptor . For defining the reference target, each ExternalReference shall provide a valid ... library file that is contained in a Descriptor that is stored externally: <ExternalReference Path="pack://http%3c, ,test.org,OpcUaFxAmlLibraries.amlx/MyOpcUaFxAmlLibrary.AML"Alias="MyOpcUaFxAmlLibrary" /> The alias is used as an abbreviation
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering7.6 Content TypesConventions standard requires that the file name extensions of the files contained in a Descriptor are registered in the "[Content_Types].xml" file. Only file name extensions used ... Descriptor shall be present in the "[Content_Types].xml" file of the Descriptor . A list of IANA registered content types is given at: https://www.iana.org/assignments/media-types/media-types.xhtml . Table
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringContainer . If types from an OPC UA FX AML Library are used in a Descriptor , the library shall be made available in the Descriptor , either by including
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering7.8.1 Generalfollow the structure and requirements defined in ISO/IEC 29500-2:2021 , Clause 13. A Descriptor shall have at least one digital signature. The signing scope of each Descriptor signature shall ... Common Services files. The links to the external references, if any, in a Descriptor shall be included in the signature of the Descriptor . Content of external references shall
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering7.8.2 Certificate validationCertificate validation Engineering tools should never import a Descriptor that they do not trust. An engineering tool decides if a Descriptor is trusted by checking whether each certificate associated with ... digital signature of the Descriptor is trusted. A certificate is only trusted if its chain can be validated. Trust can be established by following the validation steps of Table
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringRequirements for engineering tools Since the Information Model for an AutomationComponent in a Descriptor is modelled as an AML InternalElement within an AML InstanceHierarchy or an AML SystemUnitClass, the tools ... Libraries. Engineering tools should support the import or export of a Descriptor . Any tool that exports a Descriptor shall require that the Descriptor be digitally signed
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringhypothetical engineering tool for OPC UA FX OfflineEngineering, which has two main functions: "Descriptor Export" and "Descriptor Import" and four supporting functions for working with ... Descriptor . Other functionality of an engineering tool, e.g., managing signal lists, writing control applications, modifying/extending Descriptor content, or designing safety applications, is left out of the figure for simplification. Figure
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering8.3.1 Descriptor ExportDescriptor Export The Descriptor Export function "exports" a Descriptor from an engineering tool. Use cases for the export of a Descriptor are: The types of vendor-specific AutomationComponent ... products are made available in a Descriptor as OPC UA FX AML types for usage in OfflineEngineering projects. An OPC UA FX Information Model of an AutomationComponent configuration is provided
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering8.3.2 Descriptor ImportDescriptor Import The Descriptor Import function "imports" a Descriptor to an engineering tool. The Descriptor Import function uses the support functions stated in 8.3.3 , 8.3.5 , and 8.3.6 Important ... tasks for Descriptor Import are: Open and decompress the Descriptor to a temporary folder or in memory. ( 8.3.3 ); Validate the digital signatures and certificates. ( 8.3.4 ); Parse the Descriptor Manifest
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering8.3.3 AML Container managementoverview of the tasks for container management is given here: Identification of the Descriptor manifest, AML files, attachment files, embedded Descriptor and Common Services files; Finding and defining the Root ... files; Browsing the references of a Descriptor starting from the Root AML files and building a structure for navigating through the content; Resolving external relationship references; Creating and managing
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringsupport function for dealing with certificates and signature methods needed for signing a Descriptor and validating digital signatures. An overview of the tasks for certificate and signature management follows: Access ... certificate; Creating digital signatures according to the Open Packaging Conventions standard; Validating a Descriptor digital signature by checking the validity of all involved certificates as defined in 7.8.2 and checking
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringtool to an OPC UA FX AML model, which can be serialized to a Descriptor . The main steps for conversion are: Ability to produce OPC UA FX AML content from
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringExample workflow for sharing a Descriptor in OfflineEngineering The import of a Descriptor with configuration information arises in the sharing of work between Controls Engineers: one Controls Engineer exports ... Descriptor and sends it to another Controls Engineer for further usage. The import could be for adding or changing the configuration of a Descriptor in a subsequent engineering step
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringA.3.7.3.1 NodeId - BrowsePath ExampleA.3.7.3.1 NodeId - BrowsePath Example A typical use case for the BrowsePath in a Descriptor is to reference the corresponding variable in the AddressSpace from the PublishedData of a PublishedDataSet
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringA.11.4 OPC UA FX LibrariesLibrary, and this library shall be included in the Descriptor . The OPC UA FX AML Core Libraries are those libraries defined in this document. For modelling of safety information ... Descriptor , the OPC UA FX AML Safety library shall be used (see Annex
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringF.1.6 Usage of the Descriptor in subsequent engineering After the offline configuration of the Filling machine, the configuration is exported to a Descriptor and further used in system engineering ... used and Networking configuration (e.g., IP addresses, VLAN Ids). Figure F.13 - Usage of a Descriptor in subsequent engineering As the final step, the connection information, including custom DataSets , the communication
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringL.1 Overviewcertificate through a chain of trust to establish trust in the authenticity of a Descriptor's digital signature. Since the root CA certificate has not been issued by another ... such a certificate is the most reliable way to establish trust in a Descriptor's authenticity. A company may also decide to operate an in-house root CA and share
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringL.3 Remote Signingengineering tool may make use of a remote signing service to digitally sign a Descriptor . In this case, a hash value representing the Descriptor's content is submitted
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringDataTypes with updates to chapter A.7. 9352 Clarification Allow RSASSA_PSS padding scheme for Descriptor signatures Updated the links in Annex I for the CanonicaliationMethod algorithm and the Transform alogorithm ... empty or not present in identified. 9532 Clarification Allow RSASSA_PSS padding scheme for Descriptor signatures Updated the XML Signature Syntax reference. 9545 Clarification Implement recommendations of OPAS-UAFX
-
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles5.2.3 UAFX AutomationComponentConnections Supports the establishment of Connections using the PubSub communication model. Server UAFX AutomationComponent Descriptor Supports the AcDescriptorType and its related types. It also includes at least one instance ... UAFX AutomationComponent AcDescriptor DescriptorFile or UAFX AutomationComponent AcDescriptor DescriptorIdentifier ConformanceUnit , where at least one Descriptor complies with the UAFX Offline Descriptor Profile. Server UAFX AutomationComponent AcDescriptor DescriptorFile Supports the DescriptorFile
-
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX ProfilesUAFX OfflineEngineering Descriptor Table 10 describes UAFX OfflineEngineering Descriptor ConformanceUnits, which describe the structure and syntax of a Descriptor file . For additional information about these items, please refer ... Table 10 - UAFX OfflineEngineering Descriptor Category Title Description UAFX Descriptor Offline UAFX Descriptor Open Packaging Convention Format Supports the Open Packaging Convention attachment file name extension and Pack URI syntax
-
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles5.4.4.1 OverviewOverview This subclause describes UAFX Descriptor contents ConformanceUnits . The ConformanceGroups included are UAFX Descriptor Contents - UAFX Information Model, UAFX Descriptor Contents - Networking Information Model, UAFX Descriptor Contents - Core UA Information
-
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles6.6.5.3 UAFX Offline Descriptor ProfileUAFX Offline Descriptor Profile Table 60 describes the details of the UAFX Offline Descriptor Profile. This Profile includes the elements necessary for an interoperable UAFX Descriptor file. In particular ... contents, format, structure, and security of the file are mandated. Table 60 - UAFX Offline Descriptor Profile Group Conformance Unit / Profile Title Optional UAFX Offline Descriptor AutomationComponent Facet UAFX Offline Descriptor
-
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX ProfilesUAFX Offline Descriptor AutomationComponent Facet Table 61 describes the details of the UAFX Offline Descriptor AutomationComponent Facet. This Facet includes the content elements necessary for describing an AutomationComponent ... UAFX Descriptor file. Table 61 - UAFX Offline Descriptor AutomationComponent Facet Group Conformance Unit / Profile Title Optional UAFX OfflineEngineering UAFX Descriptor AcDescriptor DescriptorIdentifier False UAFX OfflineEngineering UAFX Descriptor AutomationComponent Base False
-
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX ProfilesUAFX 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 ProfilesUAFX Offline Descriptor FuntionalEntity Facet Table 63 describes the details of the UAFX Offline Descriptor FunctionalEntity Facet. This Facet includes the content elements necessary for describing a FunctionalEntity ... UAFX Descriptor file. Table 63 - UAFX Offline Descriptor FunctionalEntity Facet Group Conformance Unit / Profile Title Optional UAFX OfflineEngineering UAFX Descriptor ConfigurationDataFolder VariableStorage False UAFX OfflineEngineering UAFX Descriptor ConnectionEndpoint Base False
-
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX ProfilesUAFX Offline Descriptor Networking Facet Table 64 describes the details of the UAFX Offline Descriptor Networking Facet. This Facet includes the content elements necessary for describing Networking features ... UAFX Descriptor file. Table 64 - UAFX Offline Descriptor Networking Facet Group Conformance Unit / Profile Title Optional UAFX OfflineEngineering UAFX Descriptor Network Priority Mapping False UAFX OfflineEngineering UAFX Descriptor Network Physical
-
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX ProfilesUAFX Offline Descriptor Core UA Facet Table 65 describes the details of the UAFX Offline Descriptor Core UA Facet. This Facet includes the content elements necessary for describing Core ... features in a UAFX Descriptor file. Table 65 - UAFX Offline Descriptor Core UA Facet Group Conformance Unit / Profile Title Optional UAFX OfflineEngineering UAFX Descriptor Core VendorServerInfo False UAFX OfflineEngineering UAFX
-
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX ProfilesAutomationComponent 2024 Facet as Optional = False. 9371 Feature Support RSASAA-PSS in offline engineering descriptor signatures Added new Descriptor security policies RSASAA-PSS. PSS is recommended for signing ... bridge 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