Interested in using FarmOS to manage grain storage and track harvest lots through a farm’s on site storage. May include tracking post harvest value added operations such as cleaning. Track grain inventories. Would like tracking crop identity from harvest through to shipment. Potentially incorporate bin sensor logs for grain condition monitoring and demonstrate proof of condition. Is anything like this in the works? Could be useful for organic operations or those managing a variety of grain/seed crops within their operation. Not sure where to categorize this.
2 Likes
@graffte farmOS 2.x will have more flexible inventory management features, which will allow for the type of tracking you describe. You will be able to create “Structure” assets for your grain silos/storage, and use logs to record additions/subtractions from the inventory of those assets.
Would like tracking crop identity from harvest through to shipment.
Another idea we’ve been discussing is adding a new “Commodity” or “Product” asset type - to represent the actual harvested product apart from the Plant/Animal that it came from, and apart from the Structure asset it is stored in. So for example: imagine creating a Harvest log which references the “2020 Corn” Plant asset that it came from, but also CREATES a “Grain inventory” asset and sets the initial inventory of it, and locates it in the Structure asset. This would allow for a whole new level of granularity (optionally of course), and will also more generally enable new features and integrations with ecommerce platforms that need to know what you have available to sell (by looking directly at your Product assets).
Potentially incorporate bin sensor logs for grain condition monitoring and demonstrate proof of condition.
Oh excited to share some of the new sensor possibilities that @paul121 is working on for 2.x! You’ll be able to create a sensor asset, with multiple data streams, and the data streams themselves can “describe” another asset. So you’d have a Sensor asset that is describing your bin asset. Just more ways of cross-linking everything together. 
Sounds good. Probably obvious, but should be tied back to the Harvest Lot Numbering too. Looking forward to seeing this get rolled out.
1 Like
That’s a good thing to remember. The “Harvest lot number” field was added with this long-term goal in mind. We’ll have to decide exactly how we want to link everything together. It may make sense for all commodity/product assets to have a “Lot number” of their own - which maybe gets automatically copied/synced to/from the harvest lot number. Or, maybe we remove the field from harvest logs, and only add it to commodity/product assets, and have the log point directly to the “output” asset it creates.
So: you create a harvest log which points to a product asset, and the product asset has a lot number. This way, you could trace backwards from a product asset to a harvest log to a plant asset to a seeding log.