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.03 Highlights
The following table includes the Mantis issues resolved with this revision.
| Mantis ID | Scope | Summary | Resolution |
| 9107 | Errata | DNS for host name resolution and mDNS for responder support need to be added to the UAFX Controller Profile | Added the Host Resolution – DNS Server CU to the UAFX ConnectionManager Client 2025 Facet and UAFX Controller 2024 Profile. |
| 9166 | Feature | Do we need a Conformance Unit requiring a minimum number of UAFX Connections | Added UAFX AutomationComponent MinConnections CU and the new CU to the new UAFX AutomationComponent 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 and PSS and PKCS are required for importing. |
| 9480 | Clarification | The UAFX Input Datatype Support CU should include Output Variables | Rename the CU to “UAFX Controller Datatype Support”, changing Input to Controller, and removed “for input data” from the ConformanceUnit Description. |
| 9481 | Clarification | UAFX ConnectionManager Base ConfomanceUnit language should be improved | Updated the ConformanceUnit description to make it clearer that it is subtyped objects specific to the supported connection types, e.g. PubSubConnectionEndpoint/Mode. |
| 9482 | Errata | UAFX ConnectionManager AutomationComponentConfiguration AssetVerification CU should be made mandatory | Made the UAFX ConnectionManager AutomationComponentConfiguration AssetVerification ConformanceUnit mandatory and updated the UAFX ConnectionManager Facet to a new 2024 Facet. |
| 9483 | Errata | UAFX Preconfigured PublishedDataSet and SubscriberDataSet CUs language need reconciled | Updated the UAFX Preconfigured PublishedDataSet CU to “If preconfigured PublishedDataSets exist, the Server exposes the PublishSubscribe Object, the Folder hierarchy to all preconfigured PublishedDataSets, and all preconfigured PublishedDataSets.” |
| 9527 | Feature | Add LLDP facet to Controller Profile | Created a new CU, UAFX EthernetUAFXStation Remote Systems Data, and added it to an updated UAFX Station 2024 Facet as Is Optional = False. The LLDP Information Facet was also added to the new UAFX Station 2024 Facet. |
| 9559 | Errata | AutomationComponentConfiguration CommunicationModelConfig mandatory should not be mandatory in P 84 | Made UAFX ConnectionManager AutomationComponentConfiguration CommunicationModelConfig Optional = True in the UAFX ConnectionManager 2024 Profile. |
| 9796 | Feature | Requiring CCSs be exposed in a CM | Added CU UAFX ConnectionManager Exposes CCSs - Exposes a ConnectionConfigurationSet for each of its Connections. |
| 9787 | Errata | The Base Bridge Component Facet description contains misleading text. | Removed the phrase "describes the requirements common to all products containing 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 if it is supported by the Server. The new ConformanceUnit is added to the UAFX Offline Descriptor Profile as mandatory (Is Optional = False). |
| 9617 | Clarification | Potential interop issue between CM and AC for predefined v. dynamic DataSets | Added text to the UAFX Client ConnectionManager SetCommunicationConfiguration ConformanceUnit requiring support of preconfigured and dynamic Datasets. |
| 10025 | Errata | Missing individual PublisherCapabilities and SubscriberCapabilities CUs for UAFX Descriptor contents – AutomationComponent | Added ConformanceUnits for AutomationComponent Publisher and SubscriberCapabilities to the Descriptor content CUs and added them to the UAFX Offline Descriptor AutomationComponent Facet. |
| 10059 | Feature | Create CUs for 9820: Extend the information model with additional Functional Group | ConformanceUnits were created for optional FunctionalGroups to FxAssetType, FunctionalEntityType, ConnectionEndpointType, and ConnectionManagerType. |
| 10060 | Feature | Create CUs for 8456: ConnectionConfigurationSet Error State: show StatusCode in information-model | ConformanceUnits created for Variables added to the ConnectionManager, ConnectionConfigurationSetType, and ConnectionManagerType Capabilities. Facets created for monitoring Connections and monitoring Connection Establishment. |
| 10061 | Feature | Clone of 9819: Diagnostic statistics are missing and should be added | ConformanceUnites created for the optional diagnostic counters added to the AutomationComponentType, FxAssetType, FunctionalEntityType, ConnectionEndpointType, and ConnectionManagerType. |
| 10185 | Feature | Add CUs for LogObjects added to the AC and CM | Add the UAFX AutomationComponent and ConnectionManager Logging Facets with associated ConformanceUnits. |
| 10186 | Feature | Add CU for ConnectionManagerApplicationUri | Added FunctionalEntity CU to the Top-Level FunctinalEntity Facet as Optional. |
| 10187 | Errata | ConformanceUnits on Object Type definition tables are incorrect or missing. | Added UAFX ConnectionManager PubSubCommunicationModelConfig CU to the ConnectionManager Facet. |
| 10184 | Clarification | EstablishConnections: Supported PubSubConfigurationRefMask values | Added ConformanceUnit UAFX AutomationComponent ConnectionEstablishment Modify Not Supported as Optional = FALSE to the Controller Profile. A new Controller Profile can be published without this CU after Part 81 is updated with details for using the ElementModify element operations. |
| 10308 | Errata | KeyCredential Service Server Facet not needed in Controller Profile | The KeyCredential Service Server Facet was removed from the (new) UAFX Controller Server 2024 Profile. |
| 10309 | Errata | User Token – X509 Certificate Client Facet not needed in UAFX ConnectionManager Client Facet | The Facet was removed from the UAFX ConnectionManager Client 2024 Facet. |
| 10139 | Errata | InputData and OutputData should not be required in the controller's FunctionalEntity | Changed the InputData and OutputData CUs from Optional=FALSE to Optional=TRUE in the UAFX Controller 2024 Profile. |
| 10334 | Errata | There is no ConformanceUnit for the optional DeviceHealthAlarms Folder of the FxAssetType | Waiting for feedback from the DI WG about adding the DI-related Facets defined in this document to their Profiles. |