Managing Product, it is reference data or instance data?

[dubnemo]

It is unclear if Product is intended to be reference data or instance data about the product.
Is it product.description that is displayed in the tractor MICS? Asking for a friend.

Similar with with Packaged Product:
https://adaptstandard.org/docs/packaged-product/
Here I see:
https://adaptstandard.org/docs/packaged-product-instance/

With the increased awareness and need for Traceability, key data element identifiers would be valuable to capture specific instances of a product. Or we burying them into Context Items?

What about seed size instance related information? Can there be a general Measument component that the various product attributes are mapped into instead of specific qualified types?

[knelson-farmbeltnorth]

@dubnemo The documentation out on the site is out-of-date. We will be publishing an update shortly.

Short answer: Product is reference information. The PackagedProduct/Instance components are not included in the 1.0 scope. See #117

The intent is not to bury traceability/supply chain things in context items or to omit them permanently. Traceability and observations are two big topics we will be pivoting to following work to wrap up 1.0.

[knelson-farmbeltnorth]

Parked pending interest/contribution.

[dubnemo]

We know that actual application of products are instances. They are not reference data, despite the limitations of MICS displays. We don't apply a page from a catalog.

Instance information makes all the difference, whether its seed size, average germination days, density of crop protection for mixing, etc. Instance attributes could be a simple extension mechanism as well as related observations and measurements The density object would then morphed as a measurement.

[knelson-farmbeltnorth]

Let's pick this topic up in today's meeting.

[dubnemo]

Kelly, I am on PTO today, as I am performing twice for the City of Minneapolis 1) Nicollet Mall 11:30am-1:30pm, and 2) Lake Harriet Bandshell 7:30-9pm. :-) Scott +1.612.385.4263

…

On Wed, Jul 30, 2025 at 7:47 AM Kelly Nelson ***@***.***> wrote: *knelson-farmbeltnorth* left a comment (ADAPT/Standard#139) <#139 (comment)> Let's pick this topic up in today's meeting. — Reply to this email directly, view it on GitHub <#139 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHXOQOZGHZPISPG2FKUJYS33LC5GBAVCNFSM6AAAAACBVUQMMGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCMZWGE3TKNZYG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[knelson-farmbeltnorth]

We discussed in today's meeting. While some participants questioned whether such information would be accurately logged, and if there were indeed common B2B transfer use cases, there was general agreement that such use cases may exist in the future, and we should keep the discussion open.

@dubnemo As a proposed next step, are you able to list out specific product instance attributes that would be good to track on an initial implementation? With such a list in hand, we could better document the use cases, create Data Type Definitions and then explore where to store the values in the model.

[DarinGary]

Just a day after our conversation, the topic came up in a staff meeting—about the need to tag a seed prescription or field operation with the specific variety or trait.

We had been discussing how the hybrid should be prominently displayed in the field operation plan. The issue raised was that, too often, a specific hybrid is ordered for a particular field, but due to logistics—like it arriving last and being placed at the front of the warehouse—it ends up being planted on the wrong field.

If we had the information, it could get added to the work record, and maybe someday into the cab displays.

[dubnemo]

@DarinGary thank you for you comments on variety. For our Croplan seeds and FGI alfalfa traits, we were interested in the seed lot identifiers as well, especially in rare germination issues where replant is needed, ideally knowing that that particular seed is sent to a farmstead and which fields they have been planted in. If you can also correlate that by shipment id, that is helpful too, as rebranded seeds have the same lot number.
Our R&D folks have expressed interest in knowing product performance in the field, in particular geographic regions, correlated with other dimensions such as weather, water quality and soil health, comparing to our lab data. That include crop protection, adjuvents, and our custom secret sauce fertilizer blends.

@knelson-farmbeltnorth these use cases are not in the future, but now.

If you are interested in the what data elements we're hoping to capture, please visit the ShippedItemInstancePlugin repo, and navigate to the ISO_ADM_Exporter folder, and the two linklist.xml files. Clearly key identifiers would be ideal in the display, particularly lot and shipment ids, to at least handle the above use cases. The rest of the identifiers / information can be picked up via 'turnaround' / 'side-car' file or database approaches.
https://github.com/ADAPT/ShippedItemInstancePlugin/blob/develop/ISO_ADM_Exporter/output/0/TASKDATA/LINKLIST.XML