This page will serve as a staging area for content. R. Andres Ferreyra (Unlicensed) will create Jira tasks under the Communications Team to track progress.
Intend to discuss with ADAPT Business Team on 1/19/2018.
| Outline | Abstract snippet | Person Responsible | Jira | Text |
|---|---|---|---|---|
| Introduction: General and Specific Problem | Modern farming requires increasing amounts of data exchange among hardware and software systems. Precision agriculture technologies were meant to enable growers to have information at their fingertips to keep accurate farm records (and calculate production costs), improve decision-making and promote efficiencies in crop management, enable greater traceability, and so forth. The attainment of these goals has been limited by the plethora of proprietary, incompatible data formats among equipment manufactures and farm management information systems (FMIS), along with a lack of common semantics (meaning) in the industry. | R. Andres Ferreyra (Unlicensed) | Based on Applegate paper | |
| Introduction: Past attempts at standardizing field ops data | Proposed partial solutions exist; e.g., the ISO11783.10 standard XML format is well-known and respected, but it is machinery-specific and does not include business-process details needed by growers’ FMIS. | (Mention FODM, take from Applegate paper) | ||
| AgGateway, PAC, SPADE, and ADAPT | AgGateway is an industry consortium of 200+ companies in the agricultural industry. In 2013-14, its SPADE project explored the feasibility of the industry developing an open-source format conversion toolkit. This experience led to what is now its ADAPT Committee. | Jim Wilson ? | Look at material in Applegate paper | |
| ADAPT: What it is, What it does, How it works | The ADAPT team created a common object model or "Application Data Model" (ADM), a super-set of field operations data models presented by participating companies. The goal: to replace the current, fragile situation, where FMIS must support multiple hardware data formats, and each machinery manufacturer has to interact with multiple software companies, with a single ADM integration mediated by a framework (initially built on .NET Framework 4.5) from which manufacturer-specific plug-ins convert to and from proprietary formats. | |||
| FMIS implications and example | This enables the FMIS to read/write to a wide variety of systems with little incremental effort, using ADAPT as a form of a digital agriculture Rosetta stone. | R. Andres Ferreyra (Unlicensed) and Stuart Rhea (Unlicensed) | ||
| Geopolitical-Context-Dependent Data aspect | A special emphasis was placed on developing a data-driven approach to managing geopolitical-context-dependent information, and on delivering shared meanings (semantic resources) through application programming interfaces (APIs). | R. Andres Ferreyra (Unlicensed) and Stuart Rhea (Unlicensed) | ||
| Licensing | Licensing is an important consideration when seeking to promote the wide adoption of a software platform. The ADAPT Committee selected the well-known, and broadly accepted, open-source Eclipse Public License for the ADM, the conversion framework, and community plug-ins. The licensing model for proprietary plug-ins is different from that of the community-supported tools: each plug-in writer can choose whatever licensing and distribution model best fits their business model. | Mark Stelford (Unlicensed) ? | ||
| Progress to Date on proprietary plug-ins and FMIS adoption | Several machinery manufacturers have already begun writing plug-ins for their hardware; their projects are at different stages of development. | Ben Craker (Unlicensed) and DANIEL DANFORD ? | ||
| Progress to date on community-supported stuff | There are currently two community-supported plug-ins: one to convert ISO ISO11783-10 XML files; and another to perform lossless serialization and de-serialization of ADM instances. The former serves as a template for machinery companies that use the ISOXML format to customize, and the latter enables FMIS-to-FMIS communication, a critically-important function that the industry has been lacking. | Kelly Nelson, Stuart Rhea (Unlicensed) ? | ||
| What's next? | Future plans for community-supported plug-ins include one for the Precision Agriculture Irrigation Language (PAIL) format, and another for sustainability metrics. | R. Andres Ferreyra (Unlicensed), Kelly Nelson | Include v2 | |
| How to use it | The ADAPT Committee has a GitHub repository for source code, a transparent governance system, an email list for questions (ADAPT.Feedback@AgGateway.org), and accepts contributions from outside AgGateway. | Kelly Nelson ? | ||
| Discussion | The application’s scope includes self-propelled machines, non-mechanical processes, observations and measurements, and post-harvest traceability. The intention is for it to facilitate the growth of digital agriculture. | R. Andres Ferreyra (Unlicensed) All pitch in! | Need 6 ideas here | |
| Conclusions | R. Andres Ferreyra (Unlicensed) |