Agreement of Use

COPYRIGHT RESTRICTIONS

Any unauthorized use of this specification may violate copyright laws, trademark laws, and communications regulations and statutes. This document contains information which is protected by copyright. All Rights Reserved. No part of this work covered by copyright herein may be reproduced or used in any form or by any means--graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage and retrieval systems--without permission of the copyright owner.

OPC Foundation members and non-members are prohibited from copying and redistributing this specification. All copies must be obtained on an individual basis, directly from the OPC Foundation Web site http://www.opcfoundation.org.

PATENTS

The attention of adopters is directed to the possibility that compliance with or adoption of OPC specifications may require use of an invention covered by patent rights. OPC shall not be responsible for identifying patents for which a license may be required by any OPC specification, or for conducting legal inquiries into the legal validity or scope of those patents that are brought to its attention. OPC specifications are prospective and advisory only. Prospective users are responsible for protecting themselves against liability for infringement of patents.

WARRANTY AND LIABILITY DISCLAIMERS

WHILE THIS PUBLICATION IS BELIEVED TO BE ACCURATE, IT IS PROVIDED "AS IS" AND MAY CONTAIN ERRORS OR MISPRINTS. THE OPC FOUDATION MAKES NO WARRANTY OF ANY KIND, EXPRESSED OR IMPLIED, WITH REGARD TO THIS PUBLICATION, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF TITLE OR OWNERSHIP, IMPLIED WARRANTY OF MERCHANTABILITY OR WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE OR USE. IN NO EVENT SHALL THE OPC FOUNDATION BE LIABLE FOR ERRORS CONTAINED HEREIN OR FOR DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, RELIANCE OR COVER DAMAGES, INCLUDING LOSS OF PROFITS, REVENUE, DATA OR USE, INCURRED BY ANY USER OR ANY THIRD PARTY IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS MATERIAL, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

The entire risk as to the quality and performance of software developed using this specification is borne by you.

RESTRICTED RIGHTS LEGEND

This Specification is provided with Restricted Rights. Use, duplication or disclosure by the U.S. government is subject to restrictions as set forth in (a) this Agreement pursuant to DFARs 227.7202-3(a); (b) subparagraph (c)(1)(i) of the Rights in Technical Data and Computer Software clause at DFARs 252.227-7013; or (c) the Commercial Computer Software Restricted Rights clause at FAR 52.227-19 subdivision (c)(1) and (2), as applicable. Contractor / manufacturer are the OPC Foundation, 16101 N. 82nd Street, Suite 3B, Scottsdale, AZ, 85260-1830.

COMPLIANCE

The OPC Foundation shall at all times be the sole entity that may authorize developers, suppliers and sellers of hardware and software to use certification marks, trademarks or other special designations to indicate compliance with these materials. Products developed using this specification may claim compliance or conformance with this specification if and only if the software satisfactorily meets the certification requirements set by the OPC Foundation. Products that do not meet these requirements may claim only that the product was based on this specification and must not claim compliance or conformance with this specification.

Trademarks

Most computer and software brand names have trademarks or registered trademarks. The individual trademarks have not been listed here.

GENERAL PROVISIONS

Should any provision of this Agreement be held to be void, invalid, unenforceable or illegal by a court, the validity and enforceability of the other provisions shall not be affected thereby.

This Agreement shall be governed by and construed under the laws of the State of Minnesota, excluding its choice or law rules.

This Agreement embodies the entire understanding between the parties with respect to, and supersedes any prior understanding or agreement (oral or written) relating to, this specification.

ISSUE REPORTING

The OPC Foundation strives to maintain the highest quality standards for its published specifications; hence they undergo constant review and refinement. Readers are encouraged to report any issues and view any existing errata here: http://www.opcfoundation.org/errata

Revision 1.00.04 Highlights

The following table includes the Mantis issues resolved with this revision.

Mantis ID Scope Summary Resolution
10545 ClarificartionOffline descriptor - Security algorithm -UAFX Descriptor Digital SignatureUpdated the second sentence of UAFX Descriptor Digital Signature to read: "When signing using an RSA algorithm, the policies with PSS are recommended over the PKCS policies (i.e. UAFX Offline Security Policy - Rsa-Pss-Sha256 Facet over UAFX Offline Security Policy - Rsa-Pkcs-Sha256 Facet)."
10575 ErrataChange IVendorNameplate ProductInstanceUri and SerialNumber CU descriptionsUpdated descriptions of UAFX Descriptor DI IVendorNameplate SerialNumber and UAFX Descriptor DI IVendorNameplate ProductInstanceUri to remove "and their contents."
10653 Check Nano Embedded Device 2025 Server Profile vs. Micro Embedded Device 2025 Server Profile

In UAFX Controller Server 2024 Profile:

Replaced Nano Embedded Device 2025 Server Profile with Micro Embedded Device 2025 Profile.

In UAFX Controller 2024 Profile:

Remove Session Multiple CU and EmbeddedDataExchange 2022 Server Facet.

10674 UAFX ConnectionManager Client 2024 Facet includes a deprecated Core Client ProfileIn the UAFX ConnectionManager Client 2024 Facet, replaced Minimum UA Client 2022 Profile with Minimum UA Client 2025 Profile.
10807 ErrataMissing Conformance Units that require Descriptor to contain preconfigured DataSetsAdded ConformanceUnits UAFX Descriptor preconfigured PublishedDataSet and UAFX Descriptor preconfigured SubscribedDataSet, and made them mandatory in the UAFX Offline Descriptor FunctionalEntity Facet.
10813 ClarificationProfiles need to require the ConnectionManagerLog and possibly the AutomationComponentLog Components

1) Moved the LogObject Facet from the ConnectionManager Facet to the ConnectionManager Logging Facet (this includes moving all of the Optional Logging CUs that are being made mandatory in the ConnectionManager Facet.

2) Added the ConnectionManager Logging Facet to the ConnectionManager Facet

3) Performed the previous 2 steps on the similar Facets related to the Controller Profile and AutomationComponent Facet.

10823 ClarificationChange of CUs UAFX Descriptor AssetConnector Slot Base, Socket Base, Clamp Base, ClampBlock BaseModified CU to read - If the product supports the UAFX AssetConnector Slot Base ConformanceUnit, the AML descriptions of at least one instance of SlotType are included - in all four places.
10824 ClarificationChange CU - UAFX Descriptor AssetConnector ClampBlock NestedChanged the description of the CU to "If the product supports the UAFX AssetConnector ClampBlock Nested ConformanceUnit, the AML description of at least one nested ClampType is included."
10836 ClarificationCU - UAFX ConnectionEndpoint Base - Minor ChangeRephrased description to "Supports at least one instance of a subtype of ConnectionEndpointType, including InputVariables, OutputVariables, or both."
10837 ClarificationCUs with Connection Endpoint Descriptor content - Required ChangesReworded ConformanceUnits UAFX Descriptor ConnectionEndpoint Base, UAFX Descriptor ConnectionEndpoint PubSub, and UAFX Descriptor IFunctionalEntity ConnectionEndpoints
10838 ClarificationCUs with ControlGroup Descriptor content - Required Changes

Rephrased:

UAFX Descriptor ControlGroup Base to "If the product supports the UAFX ControlGroup Base ConformanceUnit, the AML descriptions of all instances of ControlGroupType and their contents are included";

UAFX Descriptor IFunctionalEntity ControlGroups to "If the product supports the UAFX IFunctionalEntity ControlGroups ConformanceUnit, the AML descriptions of all instances of the UAFX Information Model Objects required by that ConformanceUnit are included", and;

Deprecated UAFX Descriptor ControlGroup Methods because it is redundant to UAFX Descriptor ControlGroup Base, and removed it from the UAFX Offline Descriptor FunctionalEntity Facet.

10856 ClarificationMissing CUs: UAFX ConnectionEndpoint InputVariables / OutputVariablesRestored the two CUs and the references to them in the UAFX IFunctionalEntity Facet back into Part 84 as proposed, and made no change to the DB as they were still in there.
10859 ClarificationEnsure CU UAFX ConnectionManager Auditing Method Calls Logging is consistent with Part 81 updatesDeprecated CU UAFX ConnectionManager Auditing Method Calls Logging and removed its reference in the UAFX ConnectionManager Logging Facet.
10873 ClarificationCU UAFX Descriptor IFunctionalEntity OperationalHealthAlarms - Required ChangesRephrased the UAFX Descriptor IFunctionalEntity OperationalHealthAlarms CU's description to remove "and their contents".
10880 ClarificationRemove AliasNames support requirement in CM ClientIn the UAFX ConnectionManager Client 2024 Facet - made AliasName Client Base optional, Attribute Client Read Base (needed to support PortableNodeIds) optional, and left View Client TranslateBrowsePath (needed for PortableRelativePath) mandatory.
10881 FeatureUAFX ConnectionEndpoint ApplicationUri needs to be made mandatory in the UAFX top-level FunctionalEntity FacetCreated a new FunctionalEntity 2026 Facet that includes UAFX ConnectionEndpoint ApplicationUri as a mandatory CU.
10910 Errata Work with the Core UA WG to make the Announce messages optional in the Periodic Fixed profileReplaced the Publisher UDP UADP Periodic Fixed Profile and Subscriber UDP UADP Periodic Fixed Profile with Publisher UDP UADP Periodic Fixed StaticCfg Profile and Subscriber UDP UADP Periodic Fixed StaticCfg Profile, respectively.