2021-06-14 Crop Nutrition Meet Up

Participants

PresentNameCompany
XBrent KempAgGateway
XDan Berne (Unlicensed)AgGateway

kristi.block (Unlicensed)AgGateway
XRick WeyrauchLand O'Lakes
XSeth PetersenWilbur-Ellis
XRobert KovalskyMosaic
XGreg FishGrowmark
X

Todd Moutardier

TKI
XMike CarrabineIRM
XGrace LiaoIRM
XEwa WojcikCF Industries
XMillie AlmaoCF Industries
XSusmitha KilaruCF Industries
XGinger GageNutrien

Mike.Kuhn@Nutrien.comNutrien

Terms:

MSA = Moved, Seconded & Approved

Meeting Information

 Date
2021-06-14
 Time

1:00 pm Chicago

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

+1 (571) 317-3116

 Access Code
922-279-301

Purpose of meeting: The Crop Nutrition Meet Up will focus on developing charter for a harmonized web service or API implementation of the CNC Project's XML messages. X12 EDI implementations are also likely to be considered. The desired outcome is an initial scope of work and agreement to proceed to a call for participation. Manufacturers, distributors, retailers, allied providers, and other stakeholders are encouraged to attend. 

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 new Antitrust statement for 2021
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.

Brent Kemp will capture notes

Round table introductions of all on the call

3Current State - Extending Crop Nutrient Supply Chain MessagingThe group has the opportunity to review recent resources and identify any for implementation

From the 2021-05-11 Meet Up

Web Services, API implementation and CNC connectivity: 

  • Some parties are implementing non-CNC XML messages for ShipNotice, others. Where reviewed, business rules appear to be in line with CNC implementation.
  • Some parties are interested in implementing a web service approach to message exchange; others, an API implementation.
  • No widespread agreement on moving from XML to JSON; some parties still implementing X12 EDI in the segment. 

Transport:

  • Value-Added Network (VAN)
  • SOAP
  • Web Services
  • API

Message Types:

  • X12 EDI
  • Ag eStandard XML
  • CNC
  • Distributor to retail - ShipNotice SC/hybrid
  • JSON?

Discussion:

  • CF Industries - currently XML, EDI, migrating to new system
    • API-enabled
    • Would like to see movement toward API integrations
    • Simplify the integration points where possible
    • Near realtime as much/as close as possible with customers
    • Customer base largely unchanged from CNC - distributor network
  • GROWMARK - CNC-enabled, ebMS/SOAP communications
    • CNC works well with suppliers
    • Some interaction with retailers using CNC message, SOAP-based web service
    • Open to RESTful services
    • Concern about losing the conversational nature of ebMS implementation if movement towards web service or API - timing concern - Technical Acknolwedgement
  • IRM - CNC-enabled, ebMS/SOAP communications - everything goes through NexusE2E; FTP for EDI invoicing
    • Some Nexus calls are making Azure calls for API
    • Concern about the future of Nexus as a supported product
  • Land O'Lakes/Winfield - Inherited a number of systems, X12, XML, FTP, SOAP
    • Wants to see a movement to RESTful services
    • Just implemented a new FTP/X12 service through a third party? May not be CN-specific; TexSys Trucking (logistics)
  • Mosaic - CNC-enabled, ebMS/SOAP communications; X12
    • Used to use SeeBurger; now using Alloy (OpenTech)
    • Don't really care about payload or connection type - open to pretty much anything
    • Want the business rules consistent - harmonized message implementation regardless of payload type
  • Nutrien - Retail-focused; CNC XML messages using RESTful services;
    • Support orders, order response, order change, ship notice
    • Proprietary JSON implementation
    • Some change over planned for the future
  • TKI - CNC-enabled, ebMS/SOAP communications; also using CP messaging
    • Open to API and RESTful services
    • Internal tool will translate XML to JSON
    • Echoes Technical Acknowledgement is valuable
  • Wilbur-Ellis - CNC-enabled, ebMS/SOAP communications
    • Some outward-facing APIs, web services in place; FTP for other lines of business; happy to move in that direction
    • Technical Acknowledgement is useful - processed in the backend and displayed to the user
    • Echoes desire for harmonized business rules and message implementation
    • Notes that while there is a motions towards API, capacity and prioritization of "what's working today" requires a solid business case for internal use

Does an API/RESTful web service offer a similar tool to the technical acknowledgement? Technical acknowledgement is a specialized component of SOAP. 

Are we talking about a refactored SOAP into a RESTful web service?

What about a JSON implementation of the XML?

What about X12 implementations? Is there a crosswalk between formats and toolsets?

  • For SAP implementers, PO has an internal tool that can be leveraged for converting JSON to XML; 
  • No reason you can't transmit X12 or XML payloads over RESTful service - just becomes a new transport 

Some conversation about using Nexus as a RESTful endpoint - consider pinging Guido on that

Schedule a conversation with Ginger about a demo for the Nutrien service

Invite SSI/AgVance to comment

Finish message harmonization for X12 to XML (Order series)



4Ideation - Working Group ScopeThe group has identified a path forward to implement, and broken down work packages to prints as applicable.

Not addressed due to time, need to involve additional participants

5Next StepsGroup identifies specific actions that will follow this meet-up.
  • Schedule next call
  • Engage demo for Nutrien service
  • Issue invitations to identified parties
  • Review state of XML to X12 harmonization efforts
6

Other items () 

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

Next Meetings: Next discovery session set for 2 pm ET/1 pm CT 28 June 2021

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

Scheduled for 28 June at 1:00 pm Chicago time

8Adjournment ()AdjournMeeting adjourned at 1:57 pm Chicago time

Tasks/Action Items

WhoWhen AssignedWhatDeadline Status