@rmehta and @Francois_Ifitwala You are right, I noticed that both Mnaufacturing and Projects have features desired in the crop cycle module I put forth as ideal. I was havign this dilemma while setting up the system. I will explore how to make my fresh modules for AG. Any pointers on a good place to start making a module? I am still getting to know the program while I simultaneously migrate my business onto ERPNext from basic excel records, so I will be taking some time to develop. Any guidelines are welcome.
I will set up a developing machine soon, perhaps using the virtual image, since I am already my business on digitalocean, and want to leave that untouched while I develop. Thanks for support!
@rmehta, I managed to slow down a bit from the initial infatuation I had with ERPNext. (a very good thing) I opted to watch the conference videos tonight and I am now aware that the blame goes to Sukh Dugal and Studio March. I not only am enjoying the usability, but the design!! Eye candy for work operations. My staff is pleased with the interface, SIMPLE. Lets you work. I believe that ERPNext’s 2015 base will serve as a good starting point for any future GUI changes.
I am going through the tutorials now, and will let you know what I can and cannot do programming-wise. If I get stuck I will let you know.
Excellent project. Congratulations to all on the inspiration to build something to help businesses worldwide.
I am keenly interested in this application for the Frappe and Erpnext framework. I am a commercial mushroom, strawberry and logging operation in the US and I have been using eprnext for the better part of a year now for everything BESIDES the farming data. We have been using excel and google drive for harvest, planting and everything else. Currently I am working on three apps to add on to the existing Frappe framework and integrate with erpnext. These are, but are not limited to:
The name are working title but I plan on keep these three separate and independent as to allow others to utilize them. I am no expert like the guys over at Frappe, but I am versed in python, JS, full stack, etc.
I started a few repos on Github to get started and would love some feedback and input. The only one I have put any time into is my greenhouse management app as our season just started.
François, I am working to implement ERPNext still. I have however, jumped to design the workflow and the DocTypes for the farming setup. I am reviewing other modules out there, and validating what is necessary and what is not. I’ll check into Brandon’s work to see if we can fork from that and improve.
If you see me “disappear” for some time I am having a Jackson Pollock moment, deep into ruminations as to best ways to program this. I am not losing the motivation to improve ERPNext. I am gaining better usage experience by the day.
Not yet @Brandon_Fox, still busy doing basic implementation, but I will be working on the Ag Module in the near future.
So far it seems like it will be an marginal improvement on the fantastic manufacturing module. So far, my test is as follows with the existing Manufacturing, Stock modules
Create a uniquely numbered/named warehouse representing the physical space for your crop. In my case, a 15sq m Basil bed.
Let’s say I will harvest this basil bed only once in a period. (working on how to represent multiharvests!)
Create an item in Stock which will represent the final harvest for that particular warehouse and harvest date. such as “Basil-Wh-#345-Wk-15-harvest” UOM = Ounces
Create a BOM for that item, where you input operation costs for the aprox 8 weeks from plant to harvest: W7-Bed prep = $10, W7-Planting $20, W7-Irrigation = $5, W8-Trimming, W8-Irrigation, W9-Trimming, W9-Irrigation, W10… W15-Harvest. You also add all materials used: Fertilizer 1 =2L, Fertilizer 2 =1L, Water = 200L, etc.
When you do the harvest, the BOM has to show how much you YIELDED, in my case, Ounces = 160.
Submit the BOM when finished.
The workflow would involve duplicating the items representing each harvest, duplicating their BOM, linking the BOM with the corresponding item, modifying them accordingly, and then submitting the BOM after each harvest. The final step is to “produce” the item so the “warehouse” (physical crop space) transfers to a temporary warehouse before final “assembly” (packaging), where more materials and operations are usually added for a finished product.
It is this workflow I will be cleaning up. I am working on other open source coding projects for my irrigation systems.
I am very interested in getting one started. I would be happy to collaborate on any code you develop. The one you referenced is an older attempt before I was more familiar with the system.
I noticed the new school app is getting a lot of work for the core team, but I think an agriculture app would be a great addition. As a farmer myself, I would love to have more innovation into my field. No pun intended.
@Brandon_Fox I am thinking of modeling the software off of farmos for the most part. My team wants to start working on it so i am thinking about maybe crowdfunding the the software to get it started.
@Brandon_Fox yes. Open Source software is important. There is a whole world of people that needs something like this and I can make my money of hosting and support of the software
we have not started working in it yet. We are working on the requirements and how we want to software to function. Some one did work on this https://github.com/frappe/erpnext/wiki/Agri---Farm-ERPNext but I have not looked at it the much. Maybe this would be the best place to start working on the app
