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

If an error or problem is found in this specification, the UaNodeSet, or any associated supplementary files, it should be reported as an issue.

The reporting process can be found here: https://opcfoundation.org/resources/issue-tracking/

The Link to the issue tracking project for this document is here:

https://mantis.opcfoundation.org/set_project.php?project_id=67&make_default=no

Revision 1.05 Highlights

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

Mantis ID Scope Summary Resolution
EditorialAdjust to new template

Delete Profiles and Conformance Units and refer to profile database.

Adjust Annex A – Namespace and mappings

9028 ClarificationRemove references to amendmentsReplaced by references to UA Parts where the amendments have been integrated in.
8781 EditorialTypo in reference to ISO/IEC 11179-6Replaced ISO/ICE … with ISO/IEC ….
8105 FeatureMissing IRDIsAdded IRDIs for DeviceRevision
Added IRDIs for OperationCounters
6152 ErrataCan hierarchical References be symmetric?NO! This was wrong and not implementable. Has to be NonHierarchical.
9051 FeatureAdd BrowseNames for Functional Group names.According to the new CS template, the table is now called “Well-Known” FunctionalGroupType BrowseNames. The BrowseNames have been added to the NodeSet with Attribute “DesignToolOnly”.
8412ClarificationContradiction between PrepareForUpdate and FileTransferError description rephrased.
9030ErrataMissing option to excape from endless Preparing state of PrepareForUpdate StateMachineAdded additional usage scenario for Abort Method
9546ErrataMissing HasCause References in StateMachines for SoftwareUpdateMissing references are added to all state machines
9547EditorialDrawings for StateMachines of Software Updates have more transitions then in the ModelAdditional transitions removed from the diagrams
10218EditorialMissing SoftwareUpdate reference at ComponentTypeAdded optional SoftwareUpdate reference to ComponentType.
10223FeatureStandardized folder to add / remove applications with software update supportAdded new SoftwareFolderType.
10222ClarificationSimpler example for software updateAdditional example added to Annex B.
10220ClarificationClarify when to use which loading option of software updateAdditional notes added to the description of each loading types.
10219FeatureInformation about the type of software for software updateAdded new enumeration SoftwareClass and new Properties SoftwareClass, SoftwareSubClass and SoftwareName to the SoftwareUpdateType.
10224FeatureStandard container format for Software Packages of the software updateAdded new subsection for the Software Package file format.
10221FeatureMissing information whether unsigned software packages are supportedAdded new Property UnsignedPackageAllowed to the SoftwareUpdateType.
10225FeatureInterface for asset location indicationAdded new IAssetLocationIndication Interface.
9029FeatureMissing method to remove a previously transferred software packageClear method added
10254 ErrataSome terms are lower case in the definition but used with an uppercase first letter (e.g. device, block)Fixed the terms to start with an uppercase first letter.
10579 EditorialIEC harmonized the product identification. Some IRDIs in the VendorNameplate have been revised.The revised IRDIs have been replaced in Table 18. In addition, those that have been superseded are listed in column “Legacy IRDI”.