Portfolio Update

May Portfolio Update: Preparing For a Productive Mid-Year Meeting

By Ben Craker, Portfolio Manager

April saw several Working Groups make some key decisions and progress toward having their digital resources prepared to review at what will be a very busy Mid-Year Meeting. Also, a call to participate was issued for a new working group, WG21 European Reporting Data ADAPT Mapping. The effort will follow on the work done by the Closed Loop Spray and Potato Provenance efforts to gap check the new ADAPT standard model against several common reporting models in use in Europe. The gap check will help ensure that ADAPT covers these use cases and meets the needs of the global agricultural community for transferring agricultural data.

WG15 Scale Ticket was presented with some feedback about how the group’s work relates to the existing AgXML standard and its CommodityMovement message used for vessel, barge, and rail shipments of grain and other commodities. After several reviews and discussions, the team identified two paths:

  1. Continue with the work done so far, or
  2. Change directions and bring some of the AgXML messages into Score/OAGIS.

Ultimately the group decided the best option was to continue with the work that has been done and create a new Scale Ticket message – replacing the paper commonly used today – and limiting the scope to shipments to and from farms by truck. The team does plan to recommend that if subsequent Working Groups focus on other areas such as settlement sheets that they should examine what exists in AgXML as it may be a good starting point.

WG00 Agrisemantics PoC team has been reviewing the initial crop model proposal and making adjustments to accommodate the different use cases identified by the group. The goal is to ensure the crop model will be able to represent a crop and its key properties in the context of a seed product, as used in a crop protection product label, documenting field operations by machines, and what an FMIS requires. Ultimately, the solution should facilitate mapping between lists already in use in the industry.

The WG12 PAIL team reached a significant milestone in the ISO process, moving all three parts of the proposed international irrigation standard to the Committee Draft status. This means the proposed standard has moved from the small team writing the standard to the broader technical committee for review and comment. Hitting this milestone keeps the project on schedule and will keep it moving through the various phases within the ISO organization on the path toward becoming an international standard.

Information on the three parts of the proposed international irrigation standard is available through the following links:

Part1: https://www.iso.org/standard/83602.html?browse=tc

Part 2: https://www.iso.org/standard/83600.html?browse=tc

Part 3: https://www.iso.org/standard/83601.html?browse=tc

WG19 ADAPT Serialization continues to evaluate different serialization tools to complement the work happening in the ADAPT Standardization open-source effort. Initial reviews of one sterilization tool yielded impressive improvements in file size with few negatives. The group will continue to analyze other performance aspects of the tool as well as benchmarking against other possible technical solutions the team has identified.

WG20 Traceability API is continuing to document data requirements for the API and should start building a prototype API soon. Related to the API work, the overall Data Linking team also held a special session with the Purdue OATS team to get an update on their Trellis framework and how the OATS group envisions Trellis meeting the needs of traceability efforts. The session was recorded and is posted for anyone interested to watch soon.

WG17 Field Boundary Terms and Definitions also continues to make progress. The team has been focused on reviewing the content generated during the face-to-face meeting. They have been digging into the categories of boundary types identified and defining them as well as documenting how they relate to each other to ensure there will be common understanding. The team also started reviewing some of the terms, definitions, and data elements identified with the ADAPT Standardization group. The goal is to ensure the efforts are aligned on terminology as well as the important data elements needed to share fields and field boundaries between systems.

As usual if you have any questions on the activities of any of these working groups or want to get engaged feel free to contact me (ben.craker@aggteway.org), or sign up for a working group here.