灌溉技术——灌溉远程监测与控制 第三部分：互操作性

[中文适用范围]： 本文件制定了用于管理和/或控制灌溉设施的系统之间的互操作性要求。它可以应用于任何技术平台和灌溉系统，与水管理方案无关，但不包括移动灌溉设备（如中心支管和线性灌溉机器）。 [外文原描述]： This document establishes requirements for interoperability among systems developed for management and/or control of irrigation facilities. It can be applied under any technological platform and irrigation system, regardless of the water management scheme, with the exception of irrigation mobile machinery , including centre pivots and linear irrigation machines. Due to the dynamic nature of these machines, associated control systems and specific safety requirements, the applicability of exchangeable data for irrigation mechanical move systems was not fully determined at the time of this publication. This document does not define hardware or software requirements for any of the systems to which it applies. It only concerns externally visible interfaces and places no restriction on the underlying implementations. It has been designed to avoid interference with proprietary solutions subjected to intellectual property. From the point of view of the data exchange, and to guarantee interoperability based on the previous premises, this document defines three communication interfaces (interface with management, interface with events and interface with subsystems) and the architecture to which these interfaces apply. Three levels of architecture has been defined to accommodate these interfaces: — The Management Level, where any MIS conforming with this document is located. Out of all available data exchange methods, each MIS only implements those required to execute its functionalities. — The Higher Control Level: coordination. At this level is performed the data integration among RMCS and the access control to it. A software element, called coordination broker, ensures this integration and allows the use of different technologies in its interfaces. — The Lower Control Level: RMCS. These can also be referred to as irrigation subsystems. The RMCS perform the duties of the irrigation entity(s) under its control. A coordination broker can be developed as a product by any of these manufacturers or by an independent developer using the standard specifications for this kind of software.