Defining and Including Product Mix "Hot Mix" and "Temporary Mix"

[knelson-farmbeltnorth]

The attributes "IsHotMix" and "IsTemporaryMix" came in on Mix Products from the ADAPT Framework.

Can anyone define these attibutes?

I have no idea on "temporary" mix, but I gather "hot mix" may refer to a tank mix that is premixed offsite from the sprayer. If that is correct, would "IsPreMixed" have more universal meaning?

@strhea @aferreyra @dubnemo @crakerb-ship-it

[crakerb-ship-it]

My guess is there might be a difference but am not 100% certain. I would through these out as potential definitions as a starting point for others to refine or correct.

Hot Mix: a batch of one of more products mixed with a carrier outside of the applicator. One or more of the products in the mix has clean-out requirements before the applicator can be used for other applications.

Temporary mix: a mix of products that is used for a one off situation and not expected to be used again as a common mixture referenced for future product applications.

[knelson-farmbeltnorth]

Thanks, @crakerb-ship-it . @strhea shared similar definitions with me. My next question is whether either of these concepts belong in ADAPT. The hot mix concept seems to get at chemical handling procedures, and that isn't something we otherwise model. The temporary concept seems to be an internal-FMIS recordkeeping thing (along the lines of storing picklists for a UI) . We should discuss use cases for transferring this sort of information between systems.

[dubnemo]

The way I read it, a temporary mix is based on what was used on-hand (actual) vs what was planned. Recording 'actuals' on a work record is always a good idea. :-) The same thing happens in manufacturing plants, e.g., feed ingredients may be substituted deviating from the formula as long as the desired outcome is achieved (nutrient value, protein, etc.). From an operational standpoint, Hot Mix could be renamed to cleanOutIndicator as that should prompt / remind the farmer to perform that maintenance activity. That seems to be a more concerning requirement than whether mixing was performed outside the applicator or not.

…

On Tue, Dec 5, 2023 at 8:00 AM Kelly Nelson ***@***.***> wrote: Thanks, @crakerb-ship-it <https://github.com/crakerb-ship-it> . @strhea <https://github.com/strhea> shared similar definitions with me. My next question is whether either of these concepts belong in ADAPT. The hot mix concept seems to get at chemical handling procedures, and that isn't something we otherwise model. The temporary concept seems to be an internal-FMIS recordkeeping thing (along the lines of storing picklists for a UI) . We should discuss use cases for transferring this sort of information between systems. — Reply to this email directly, view it on GitHub <#131 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHXOQO5I2VWCG4RM5DAZHF3YH4SHZAVCNFSM6AAAAABAGSPKRSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBQHA2DQOJZGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[knelson-farmbeltnorth]

Agreement in 13 December 2023 meeting that these attributes are not meaningful in ADAPT today. In future, we may want to explore cleanout events in particular, but there is otherwise no framework for that data in ADAPT today.