Ehdotuksen tiedot

The purpose of this part of the Standard is to present a data model to represent the specification and reporting of irrigation water and product applications in an irrigation system. The scope includes planning and preparation phases (represented by documents called Plan, Recommendation and Work Order) as well as the recording of as-applied water and products (known as a Work Record). The scope of this document does not, however, include representing the Observations and Measurements that drive tactical decision-making in irrigation (and the creation of Recommendations and Work Orders); that material, corresponding to an irrigation-specific implementation of the ISO 19156 standard, is covered in Part 2 of this standard. This standard should enable a developer to unambiguously represent the data being communicated in various parts of the farmer's business process associated with irrigation field operations in terms of a set of classes based on the ISO 11783 standard, with the understanding that not all farming businesses will necessarily require or support all the documents described above. The Standard is meant to support the exchange of data. The classes and structures described herein are not meant to specify internal structure or the object model of an Farm Management Information System (FMIS) or similar system, nor necessarily a serialization format for the data. While it is easy to draw parallels between an data model and a database schema, the data model defined here is not specifically meant to be construed as a database schema or as the internal structure of an FMIS. The standard does not specify any type of “summary” report. This is intentional. The information contained in a collection of standard compliant documents will be sufficient to create a summary of irrigation applications. Actual summarization of irrigation requires aggregation, and the method or scope of aggregation is often derived from specific reporting requirements. The Standard is neutral regarding reporting requirements because these requirements are typically derived from a regional, basin, or administrative unit scale and are, therefore, out of scope. It is important to note that Standard-compliant documents are intended for documenting operations or use of equipment, not the design of equipment. Many characteristics of an irrigation system are relevant for documenting the system’s design but not necessarily for documenting its use. For example, the pipe diameter of a pivot lateral is typically included in its specification. Documenting how much water the pivot applied does not require knowledge of the pipe diameter. Documentation of engineering design is out of scope for the Standard.