Scott Nieman shared some slides, shared background on the work done in the grain and feed council; CART project.

Scope is really the receipt for the farmer of proof of delivery of grain to the elevator; proof of transfer of ownership. Noted that today there is a lot of paper still, potentially used heavily downstream for traceability, stewardship.

Feel this has a place to play in traceability

Would like to see this in the electronic B2B space

Used in many industries with many different product types/commodities

Sale sometimes takes place across the scale; other times just about product storage

Standardizing the data is key

• Many kinds of data
• Many representations, many different ways of describing the same data elements

Scott showed AgXML as a base for work done in the past

• Suggests that changes would be needed
• Some enhancements requested but not completed as yet

Use cases shared

• Bi-directional
• Grower, elevator as the actors
• Other actors?
• Receipt is missing - actual delivery, proof of delivery, transfer of ownership/custody

Assumptions

• Some tickets in load out could be out of scope for this work
• Disparity of APIs - would like to align to a single API
• MVP - what is it?
  • Definitions and data elements needed to communicate
  • Identifiers, dates, parties, products, transport type (asset, container type), weights, measures, grades, price
  • Pit location? 
• Suggest looking at AgXML but some additional, modern syntax as well

Value

• Minimize impact, exposure
• Minimize recall time
• Improve awareness of source, downstream locations

General agreement that this is a valid use case, think its probably well scoped to this point

Q: This seems to align to circular ag - is that an accurate assessment? Seems to, but additional research needed. Reference ASABE call of also week. Discussion on how WG 09 (Data Linking) is preparing to align in this area.

Q: Any other use cases that any one wants to bring to the table related to delivery ticket, grain ticket? Opened for the floor - any other work effort, any other organization trying to do this?

Greg Baldwin (Unlicensed) observes this is a viable use case. Feels there are many players in the industry who have gone their own way providing updates to the grower via portals. Feel that settlement information coming back in a timely manner is another use case - grain leaving the farm, going to the processor, and final weights and grades being applied back to their account. Grower may not know until the big packet of paper comes back. Steve Oberlander concurs: Applies to ethanol, any cross-plant processor, flour, etc. Any time you're not in control of the movement of the product; coming off-farm maybe by farmer, maybe by hired hauler. Very time consuming for the retailer.

Jeff White - when the MVP says unique identifier, what does that mean? Receipt ID for the load at the location. Notes that where he sees the confusion is alignment of document identifiers across messages. How to cross reference; at some point the load itself loses unique identify. Scott Nieman observes that is why this process focuses on the shipping information content itself. Subordinate stuff is correlated after the fact so that cross reference can happen in a backend.

Auto ID data capture tools discussed - bar code, GUID plus something. In the context of CART, played around with bluetooth beacons for tying movement to activity: seeing that the truck has arrived, product is offloaded, noted, etc. Observed that this is related more to storage than delivery. Matching process remains the key.

Joe Tevis offers a different view: brother has delivered grain which was ultimately received incorrectly in the name of another grower, resulting in misapplied payment to the tune of several thousand dollars. Using first and last name as a grower identifier is unsatisfactory. 

Todd Meyer notes that balance remaining to deliver on the sales contract could be a useful data element. 

Jessica Trites Rolle observes that as this is built out, crop insurance and other programs really need the "where it came from" on the scale ticket. The more and more field operations and precision records are used, tying the delivery scale ticket to the where is important. Q: do you need to get to the field/sub-field level? In a perfect world sure, but not needed there today. 

Greg Baldwin (Unlicensed) observes this would be helpful for a landlord as well. Lots of additional parties that would find this interesting. Joe Tevis - didn't AgXML have an element for Field Source? Dunno. If it was present, may not have been very useful. 

Mondays at 1 pm CT OCT 4, OCT 18

Deliverable is a charter and MVP scope for call for participation

Next Meetings: Brent Kemp and member services to schedule follow up meetings. 

Scott Nieman, Todd Meyer, Dennis Daggett, Greg Baldwind, Kaleb Kromann, Steve Oberlander, Chuck Bohanon, Jessica Trites-Rolle, Evan Wallace signed up to support MVP development.

Covered above

Scheduled as above.