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 FOUNDATION 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://OPCFoundation.org/errata
Revision 1.00.03 Highlights
The following table includes the Mantis issues resolved with this revision.
| MantisID | Scope | Summary | Resolution |
| 7481 | Feature | Describe Asset and FE health alarms or events. | Added event types for diagnostic information |
| 7844 | Feature | Elaborate ConnectionEndpoint Alarms | Add logobject to connection manager and AutomationComponent |
| 8456 | Feature | ConnectionConfigurationSet error reporting (and ConnectionManager error report is lacking) | Added additional diagnostic information for a ConnectionManager and each ConnectionConfigurationSet. This include additional overview text as well as additional information model items. |
| 9161 | Errata | Update Audit events in specification to match updates from Part 5 | Updated event definition to correct namespace issues and to indicate it is a subtype only to make optional item mandatory |
| 9184 | Clarification | Use of PortableRelativePath needs more explanation | Added text to section 13 – on Client BrowsePath lookup to explain the possible issue and generally how it should be avoided. |
| 9361 | Feature | Capability for Minimum Connections | Added MinConnections – describing the number of connections that can always be established. |
| 9487 | Clarification | MaxStringLength should be described | Added text to input and output folder indicating that variable should include properties related to their max size |
| 9538 | Errata | Connector references in Annex D need updates | Updated the figure and text to clarify connector names to be less confusing. |
| 9543 | Errata | HasContainedComponent Reference not used in Figure | Decided that figure is correct, but that specification should be more general – updated slot definition to start at HasPhysicalComponent and allow all subtypes of it. |
| 9544 | Errata | HasContainedComponent is a shall – other model could also be used | Added isPhysicallyConnectedTo as an allowed reference |
| 9574 | Errata | The use of port number should have more explanation | Extended the ReserveCommunicationIdsCmd and parameters to handle port numbers as needed. This include a new structure which is a larger change |
| 9658 | Errata | Missing information in CCS in case of unidirectional connection without heartbeat | Added text to annex F to describe a key value pair that can be configured to provide this information. |
| 9660 | Errata | Ensure consistent results of VerifyAssetCmd vs VerifyAsset method. | Updated text to be consistent and clear in all cases. Client shall ignore and server shall return mismatch and null/empty |
| 9661 | Clarification | Clarify the expected order of checks in the VerifyAsset method | Added text explaining the precedence |
| 9662 | Errata | Add more status codes for AdditionalVariables in the VerifyAsset method | Added additional error codes for table 33. |
| 9663 | Clarification | Clarify the scope of variables passed-in to the IFunctionalEntityType.Verify method | Updated text to indicate that verify is only checking existence of node and value of variable, not the owner of it |
| 9664 | Errata | Clarify the expected behaviour of IFunctionalEntityType. Verify method in terms of aborting processing. | Added text explain that process can stop after first error, but recommended to continue processing entire list. |
| 9665 | Clarification | Clarify the expected input to IFunctionalEntityType. Verify if a single element of an array is being verified. | Added text clarifying that if index is provided then only a single value is provided and it is verified again the value associated with the provided index. |
| 9666 | Clarification | Add more status codes to VerificationVariablesErrors in FunctionalEntityType.Verify | Updated error text for Bad_OutOfRange. |
| 9786 | Clarification | Capability text could be improved | Updated text to indicate that capabilities can be added by specification or by vendors and that they must follow the rule associated with the OptionalPlaceholder modelling rule. |
| 9797 | Errata | Add diagnostics as a reason for CCS | Updated text describing CCS |
| 9800 | Errata | The HasCMCapability ReferenceType is not defined | Added definition of this reference type. |
| 9807 | Clarification | InputFolder description should be clarified (also OutputFolder) | Updated the description to better indicate the contents of this folders. |
| 9819 | Feature | Add diagnostic counter /statistics | Added diagnostic folders and counters to AutomationComponent, Asset, FunctionalEntity, Connection and ConnectionManager objects. |
| 9820 | Feature | Extend the information model with additional FunctionalGroups | Added additional FunctionalGroups to the FunctionalEntity for Tuning, configuration, status and Operational information |
| 9839 | Feature | InputsFolderType should allow variables via HasComponent references | Updated to HierarchicalReferences and also fixed OutputGroup and ConfigurationGroup folders |
| 9848 | Feature | The ConnectionManager that creates a connection should be associated with the connection | Added to the ConnectionEndpointType the string representation of the applicationUri of the ConnectionManager |
| 9983 | Clarification | InputFolder description should be clarified (also OutputFolder) | Updated the description to better indicate the contents of this folders and how it is inherited |
| 10015 | Errata | The ConnectionConfigurationType has an Un-used mandatory field (ProcessingResult) that should be removed | Removed the ProcessingResult Variable from the type. Note: this was a mandatory field and this is a breaking change, but since it only affects ConnectionManager and no ConnectionManager has been certified, the working group agreed to remove. |
| 10020 | Errata | Resolving BrowsePaths and AliasName as well as NodeId is required functionality for a ConnectionManager, this needs to be updated to a shall | Updated text as suggested in mantis issue |
| 10022 | Clarification | Explain that blank URI shall indicate that a configuration is pointing to the local server Uri (index 1) | Updated section 13 to explain that a local server Uri might not be known at configuration time and a blank Uri indicate Index 1 (local server) |
| 10023 | Errata | Add SetCommunicationConfigurationCmd in Table 8 | Updated Table 8 to include SetCommunicationConfigurationCmd |
| 10095 | Errata | Table 16 - Bad_InvalidArgument description is not clear | Cleaned up text to match what was suggested in mantis issue |
| 10096 | Errata | Table 19 include incorrect error codes | Updated table 19 to include bad NothingToDo and to remove the Part 14 items, also updated PubSubCommunicationConfigurationRestultDatatype to reference the ElementResultCodes for referenceResults |
| 10114 | Errata | PubSubCommunicationConfigurationResultDataType need more clarification for errors and rollbacks | Updated the structure definition and description |
| 10118 | Errata | SerialNumber and ProductInstanceUri spec requirement is different from profile | Updated text in SerialNumber and ProductInstanceUri to indicate that one or both are required (not that both are always required) |
| 10156 | Errata | Table F.36 – text description does not match what part 5 and Part 14 require – should be updated to match with regard to namespace | Updated text to match what is defined in part 14 |
| 10246 | Errata | CommunicationConfigurationResults Result StatusCodes is missing text | Added "SetCommunicationConfigurationCmd was skipped because a preceding command had already resulted in an error." To Bad_NothingToDo error code description |
| 10373 | Errata | The MaxStringLength and MaxByteStringLength properties should be included on any input/output variable of these datatypes | Added that variable of string datatype shall include the MaxStringLength property and variable of Bystring datatype include the MaxByteStringLength property. |