See task list below.

• Initial charter review, to include:
• Document business process requirements for retailer to input manufacturer, retailer to distributor
• Document message modification expectations, if any
• Document process exceptions (ebMS vs alternate exchange methods)

Walked through draft charter

There are some examples of harmonization documentation produced as a side effect of making sure OAGIS supported all of ChemE/Ag eStandards. Was done to see what was used by ChemE/Ag eStadnards at the XML element and child level to show x maps to y. this was done to confirm all elements were all supported not meant as a real mapping exercise.

Can an Ag eStandards confrmant invoice be expressed as a ConnectSpec invoice, in the case where the answer was no, things were added to ConnectSpec, if the answer was yes, victory was decalred and moved to the next

This was done by producing the excel expression of the schema and marching through them

This was not done in great detail in some aspects, e.g. for an address they did not go through and link the two concepts of city, it was just assumed the two addresses were compatible

In some cases one was specific, one was general, there would be note made that they map but note there is something to add for greater specificity. Specific examples would need some research since this activity occurred some time ago

Would likely also need to include OrderCreate/OrderResponse needed for customer pickup release number in scope

Also likely some need for inventory and sales tracking as well based on requests from some suppliers to understand overhead, managing on-hand through the process

Essentially are looking for IAU data but in JSON as a web service

Nutrien and Koch are receiving XML, converting to JSON internally, if there were a standard for JSON created with enough interest they would implement

JSON Schema is not a requirement for anyone, but is a nice to have. Current communication is via XML

Question on how high of a priority aligning Ag eStandard messages with Scale Ticket for a first phase, need to check with a few people who were interested at Annual meeting but were not on today's call (Key, The Equity)

CNC implementations are ebMS 2.0 if there are no message changes does it make a difference

Current implementation preference is ebMS 2.0 but alternatives are beginning to emerge in practice but not a must have for this effort

Some discussion on use of contract as a living document, opportunity to improve manual processes?

Digging into retail specific process seems to be the highest priority from discussions so far, documenting retailer-facing processes and extensions for CNC messages

Some interest in sharing PMR, IAU for fertilizer with a few suppliers providing incentives from EDI similar to seed/chemical

ATFI/ARA created the "Model Fertilizer Contract", updated July this year, intended to be printed, signed contract

https://www.aradc.org/news/model-fertilizer-contract-your-toolkbox

It is being used in the industry, provides some benefits, don't rely on XML to track the execution of the contract but to sync information. It serves a purpose to clarify risk in the industry but may not have any implications for this project

Question about if anyone is updating Marilyn's list of messages, versions used by member companies. Handy to understand use of different messages. Have moved to self reported profiles, but do get questions about updating that sheet again