2021-10-18 Grain and Feed Meet Up

Participants

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

Steve OberlanderCHS
XScott NiemanLand O'Lakes
XTodd MeyerDTN

Evan WallaceNIST

Chuck BohanonAgVantage

Jessica Trites RolleNCIS
XDennis DaggettEnterprise Ag
Xkaleb.kromannCultura

Jim WilsonAgGateway

francis adanza

Terms:

MSA = Moved, Seconded & Approved

Meeting Information

 Date
2021-10-18
 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

AgGateway Scale Ticket Meet-up 2021-09-20.pdf

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.
3Review of minutes ()The group has reviewed the prior meeting notes and has accepted them or edited them where necessary

2021-10-04 Grain and Feed Meet Up 

M: As amended Scott Nieman

S: Dennis Daggett
A: Accept as amended

4Draft Charter and Call for Participation

Scott Nieman and Dan Berne (Unlicensed) will work on draft charter; to be reviewed with group on nov 1.

5

Data Elements is the focus today

The group continues review of resources needed to commission a working group, including draft charter.

  • Review of MVP data elements
  • Review of additional resources/scenarios
    • Grain Settlements
    • Other?
  • Identification of next steps, cadence for meetings and work, etc

Additional Resources:

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. Proof of receipt is one tool to support traceability needs (as a set of CTEs; e.g., transfer event, transformation event, change of custody event, change of ownership event, observation event, transport event).

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
  • Suggest looking at AgXML but some additional, modern syntax as well
  • Some information defined in CART data bucket spreadsheet

Process Models

  • Trisotech and others

MVP and Data Elements - Define MVP by use case. 

  • 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 - is this necessary/valuable? Is it good to have for data linking purposes?
      • Farm - is this necessary/valuable? Is it good to have for data linking purposes?
      • Field (applicable for continuous harvesting model), unless direct from field to trailer; most retailers do collect this as a split identifier or the field (field to elevator). Farmer needs to provide/manage this data for contract/insurance purposes. 
    • 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; part of change of custody event?  
    • Retailers arranging transportation with 3rd party (shipment level)
    • Reconcile logistics costs on a consolidated invoice
  •  Measures
    • Weights
      • Driver on or off indicator as a function of weight - data need
      • Gross and tare 
    • Grades
      • Measured moisture
      • Foreign Matter
      • Any other measure off an instrument
      • Qualitative grades
        • e.g, Musty, Discolor, Mottled, Stained, Heat Damage, Smut, Sour, Weavilly, COFO, etc.
    • Price with method
    • Storage balance
  • 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
    • Indicators of transfer ownership
    • They are a named party. Is quality of the handling involved? Note: CART did identify clean out events (who, when, what, how). 
      Processors benefit for recalls, etc.
      How is this data used upstream? - Where the contamination came from. Ruling out where the contamination occurred.

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? We have a variety of types of API calls. Callback approach could be more realtime. 
  • ASN - can we implement scale ticket without this? Or should they work together? Yes, but do we need the ASN without it? Could be independent, but data needs to be captured. 
  • Capabilities of grower - informs FMIS provider engagement. We need an FMIS provider onboard. Reach out to Stuart Rhea.
    Dan Berne (Unlicensed) and kristi.block (Unlicensed) to identify current FMIS providers; invite them to the Call for Participation. 
  • AIP (crop insurance company) interface with grower (Jessica and Dennis)
  • B2B capabilities for farmers (FMIS and retailers).
6
  • Additional Discussion
The group has education on current work around process for context and discussion.Tabled until Nov 1
7Annual Meeting

Do we want a Meet Up at the Annual Meeting . If so, can we get a slot and what do we want to accomplish?

Do we want to issue a Call for Participation before the Annual Meeting?

Set for Tuesday meeting. Issue the call before the Annual to have it close at the Annual Meeting. 
8Next StepsGroup identifies specific actions that will follow this meet-up.

Next steps - Meet in 2 weeks (Nov 1) . Same day and time slot. 

9

Other items () 

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

francis adanza will provide some insights from work he has done with CPG packaging and how that might help with this effort. 

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

Yes. Nov 1.

11Adjournment ()AdjournMeeting adjourned at  2:00 pm Chicago time

Tasks/Action Items

WhoWhen AssignedWhatDeadline Status

kristi.block (Unlicensed)

Dan Berne (Unlicensed)

Oct 18Identify FMIS member companiesOct 28

Scott Nieman

Dan Berne (Unlicensed)

Oct 18Draft charterNov 1