2021-10-04 Grain and Feed Meet Up

Owned by Brent Kemp
Last updated: 2021-10-18 by Dan Berne (Unlicensed)
4 min read

Participants

PresentNameCompany
XBrent KempAgGateway
Xkristi.block (Unlicensed)AgGateway
XGreg Baldwin (Unlicensed)EFC Systems

Steve OberlanderCHS
XScott NiemanLand O'Lakes

Todd MeyerDTN
XEvan WallaceNIST

Chuck BohanonAgVantage
XJessica Trites RolleNCIS

Dennis DaggettEnterprise Ag
Xkaleb.kromannCultura
XJim WilsonAgGateway

Terms:

MSA = Moved, Seconded & Approved

Meeting Information

 Date
2021-10-04
 Time

1:00 pm Chicago

 Web
https://global.gotomeeting.com/join/857719765
 Phone

+1 (571) 317-3116

 Access Code
857-719-765

Purpose of meeting: The Grain and Feed meet up will kick off discussion on a potential grain delivery ticket use case and data standardization effort. Desired outcome is a path toward a working group or working groups to document user stories, data needs and message implementation.

Participants will benefit through increased understanding of industry capability and readiness to act; opportunity to offer input and provide direction on active and anticipated collaborative efforts.

Documents:

AgGateway Antitrust Guidelines

Agenda/Minutes


Topic (Leader)

Desired Outcome
Sub-topics, supporting documentation, additional resources

Meeting Minutes

1

Welcome, Antitrust and Introduction () 5 min.

Welcome the group - review Antitrust statement
In all of AgGateway's operations and activities, it must avoid discussions or conduct that might violate applicable antitrust laws, or even appear to do so. To that end, AgGateway has established Antitrust Guidelines, which it has provided to each participant in this meeting. While it is your ultimate responsibility to ensure that your actions comply with applicable antitrust laws, your participation in this meeting is affirmation that you will abide by AgGateway's guidelines.
2Minutes Taker () 1 min.A meeting taker has been selected.


3Introductions ()The group has the opportunity to review AgGateway charter resources if needed

/wiki/spaces/PMC/overview - 

  • Digital Resource Development Process
  • Charter template
  • Guiding Principles
  • Join a Working Group


4Work OverviewThe group begins development of items needed to complete a charter for development of delivery/scale ticket/delivery ticket data.

Notes from prior call:

2021-09-20 Grain and Feed Meet Up

Scope

Provides proof of receipt to the farmer that a retailer or cooperative/ retailer/ processor has receive the commodity at the destination, and it is initiated at the time of receipt.

Use cases 

  • Bi-directional 
  • Farmer to Elevator Storage (cooperative or retailer) 
  • Direct Ship to processor from farm using carbon copy,
    • As retailer, must key in delivery receipts against sales contract with processor
    • Include balance remaining to deliver on contract if applicable
    • Updated with sales contract identifier later when the co-operative or retailer assigns the amount to the appropriate contract
    • Updated with Settlement back to FMIS; need an FMIS participant in the work group

Assumptions

  • Some tickets in load out could be out of scope for this work
    • Grain and grain-related segments/commodity to start
    • Other industries' out of scope
    • Noted that AgXML spec explicitly declares messages, commodities, packaging, processed goods out of scope (grains, oilseeds in scope) Crop nutrient not in scope - AgXML addresses crop harvest output
    • Also noted that AgXML limited in US but found to work well in Canada
  • MVP - what is it? (Defer to next call)
    • Definitions and data elements needed to communicate
  • Suggest looking at AgXML but some additional, modern syntax as well
  • Some information defined in CART data bucket spreadsheet

Data Elements

  • Process model does exist - maintained in Trisotech, available in CART documentation
  • Traceability Identifiers:
    • Receipt identifier,
    • Shipment identifier; Load information, Semi-Trailer 
    • Target disposition dump pit
    • Source point (this seems to require that the farmer send an ASN) 
      • On-farm storage load out
      • Grain Cart or motherbin
      • Farm
      • Field (likely not possible), unless direct from field to trailer
    • Product / Commodity
  • Party Identifiers
    • Grower/farmer identifier other than first and last name
    • Receiving Party (co-operative, retailer, or processor)
    • Third Party Carrier  - not a party with data interest
  •  Measures
    • Weights
    • Grades
      • Moisture
      • Foreign Matter
      • Any other measure off an instrument
    • Price with method
    • Storage balance
    • Driver on or off indicator as a function of weight - data need
  • Dates/ Legal
    • Applied Sales Contract
    • Sales contract balance at the time of scale out
    • Ship date (seems to require ASN)
    • Receive Date
    • Scale in timestamp
    • Scale out timestamp

Value

  • Minimize impact, exposure
  • Minimize recall time
  • Process electronically, realtime, eliminate stacks of receipts
  • Improve awareness of source, downstream locations
    • Receipt is missing - actual delivery, proof of delivery, transfer of ownership/custody
  • Disparity of APIs - would like to align to a single API
    • How to achieve alignment? What does alignment look like? Syntax, data definition?

Alternate/Existing Standards or Tools

  • AgXML message
    • Scale ticket = weight certificate in AgXML parlance
  • OAGIS ReceiveDelivery - shared that one implementation maps other API implementations to this for internal consumption
  • Service providers, industry initiatives?

Discussion:

  • Is this a set of API requests/responses?
  • ASN - can we implement scale ticket without this? Or should they work together?
  • Capabilities of grower - informs FMIS provider engagement
  • AIP (crop insurance company) interface with grower
  • B2B capabilities for farmers
5Ideation - Review of CART BPMN for contextThe group has education on current work around process for context and discussion.

BPMN from CART Jim reviewed the On-Farm Storage to Elevator As-Is and To-Be.

  • Question - so based on that walk though what is this group tackling?
  • To be decided - might use a lot of the same data but not necessarily same syntax
  • Who may need to be invited will be determined based on scope of work
  • General sense of value - not sure where the complexity lies unless it's cross-organization shipment (multiple scale tickets)
  • What is the need for some described elements? Farmers don't worry about pit location. Perhaps some implication of traceability/sustainability in play here? 


6Next StepsGroup identifies specific actions that will follow this meet-up.

Next steps -

  • Regroup on 18 October, review proposed draft charter, provide input, align expectations and deliverables
7

Other items () 

Discuss any additional items that came up during the meeting that need to be addressed in another meet-up


8Next Meeting ()Is there a need for another Meet-Up

18 October 2021 - 1 pm Chicago Time

9Adjournment ()AdjournMeeting adjourned at 2:07 pm Chicago time

Tasks/Action Items

WhoWhen AssignedWhatDeadline Status