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.

Revision 1.3 Highlights

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

Mantis ID Summary Resolution
4311 The MDIS Specification need to provide a more standard set of error codesUpdated Fault and Warning codes to include a subset of standard defined codes and then still allow additional bits to be vendor specific
4904 Conflict when using Extensions and AggregatesUpdated text to indicate that subtypes are also allowed
5269 Add CIMV object definitionAdded definition of new CIMV ObjectType
5536 Add MDIS Arbitration ObjectAdded individual Arbitration objects for all instruments
5537 Add MDIS Pump ObjectAdded Motor Object (for a more general pump object type)
6045 Wrong usage of HasPropertyFixed incorrect definition using HasProperty
7549 WriteValue Method of InstrumentOut ObjectTypes (5.3.5, 5.4.5, 5.5.5): definition of the feedback value is unclear

updated the text in all three sections

section 5.5.5

The value of the ProcessVariable value will only update once the subsea system has provided a new value.

section 5.4.5

The value of the State value will only update once the subsea system has provided a new value.

section 5.3.5

The value of the State value will only update once the subsea system has provided a new value.

7808 Handling of "State" variable when there is no feedback from subseaUpdated text as: The value of the State value Variable will shall only be updated once the subsea system has provided a new value. For Objects that are used as a command, the value of the State Variable shall be updated directly to the value provided by the State parameter of the Method.
8005 MDIS Client profile includes base specification facets that do not fully apply to MDIS-only client appsRemoved reference to base specification facets "AddressSpace Lookup Client Facet" and "DataChange Subscriber Client Facet" and instead listed the individual CUs which comprise those facets, indicating which are optional for MDIS clients
8006 SetArbitrationMode method is optional in MDISInstrumentArbitrationObjectTypeSet it as optional in all objects
8190 Clarify CIMV behaviour when SetPosition and SetManual manual arguments are out of rangeUpdated CIMV section methods "SetPosition" Method "SetManual"
8023 Profile group names in the spec do not align with those in the profile databaseAligned profile group names with those in the profile database
7982 Documentation updates/clarifications for MDIS Motor objectUpdated document to include a statement that the Start/Stop methods are required if Manual Operation is provided.
Note: Following Nodeset Issues were also addressed in this release
3928 Type of ProcessVariable MismatchThe nodeset was updated to correctly use AnalogItemType not MDISAnalogItemType
4425 MDISAggregateObjectType is not defined correctly in the nodesetfileCorrected Nodeset file to have correct types
4990 Fix spelling/Grammar problems in nodesetCorrect all indicated issue and review /corrected any other issues
8090 Add a third value to MotorOperationEnum, “Off_0”Updated sections "MDISMotorObjectType Definition", "Motor SetOperation Method" and "MotorOperationEnum"
7814 What is the error result when setting the CIMV position >100%Updated Choke Move method (Position argument) and CIMV SetManual method (Delta argument)
8309 Fix minimum version for OPC base specification to 1.03Updated Specification version