|
Dear OpenERP manufacturing expert community, The idea was launched at the beginning of summer to create expert community branch for manufacturing and many partner/community members did show some interest in the project. I have been too busy with 2 manufacturing go-live to be able to publish yet anything but the good news is that we do have now a set of modules that are used for manufacturing company (small and not so small assembly lines and soon food industry). Good news is we are working on other gap analysis and the feedback is functionalities we developed seem to be widely needed. I think it is time to restart the project and here a short list of considerations/functionalities to be considered in the scope of this branch. Operations: - Stock picking split and back-to-back orders along chained moves compatible with automatic procurement. - Split MO (with incoming RM and outgoing FG split) - Starting a MO without having all RM - allowing to change the procurement_method directly on procurement. - sorting routing details and other setup enhancements. - Subcontractor management (information, link between service and product reworked etc.) - Stock picking batch processes (force/unforce availability, process) - Specific needs for verticalizations: food industry (eg: cut a part of a beef into steaks), continuous process etc... Costing: - Adding the product info in AA lines so that we can make cost analysis. - Possibility to record actual consumption in RM and machine time. We do have some developments ready for 6.0 (already in production) that we will propose for this branch. I understand that there are already many modules covering part or completely those functionalities but this is not the point of this branch. The main idea of this branch is to create a certified (by the experts community) set of advanced manufacturing modules. This set should be bug free/stable, well documented and maintained in long term. Here is how I see it from my window and how we could work: 1. We should agree on which scope/functionality this branch will cover (see my above list). 2. We should agree on which version we focus. I would propose only 6.0 and 7.0. Version 6.1 is not LTS so should not be a priority but if something exists and is inside the scope, I see no reason why not (it is all a question of time/priorities...). 3. We should agree on how we maintain the code. I think a short list of merge approval community members. Everybody should be allowed to propose merge though. 4. Once we have a common ground, we should work on deciding which modules from all the existing contributors could fit with the scope from point 1. 5. Merge the selected modules inside a common framework. 6. Test it and package it. 7. Maintenance, debugging and evolution: to be decided / organized. This email is just a way to restart the discussion so please feel free to add your comments, ideas or criticism on scope or method. Thanks for your feedback and contribution PS: I am not very familiar with the all tools available in lp but I think when things are a little bit more formalized we should gather all knowledge there. PS2: here is the original branch name: https://launchpad.net/openerp-manufacturing --
|
_______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
