Manufacturing Capacity Planning

Here is a one minute screencast that shows the Gantt chart features of Open ERP and how we use it to manage the manufacturing planning. Enjoy the power of the Open ERP user interface. That's a good proof we can do smart applications with web interfaces today.

You must install the mrp_operations module to do this.



The screencast has two parts.

Part 1: Work Orders Planning

We compute a manufacturing order (a PC2) that has 4 work orders related. Two of these 4 work orders can be launched in parallel and the others must be serialized. We use the gantt chart to planify the operations. Open ERP is smart enough to:

• Serialize some operations, recomputing dependencies
  
• Adapt length of work orders according to day/time (because workcenters are configured to work from monday to friday, 8 hours a day)
• Synchronize work orders and manufacturing orders.
  

Part 2: Manufacturing Orders Planning

The phase 2 show the production of a PC0, that has two others manufacturing operations in make to order (PC2 and CPU_GEN). It shows the different dependencies between the orders and how Open ERP computes automatically length, durations and partsdependencies. Of course, work orders on the different work centers synchronize automatically with manufacturing orders.

If you are interrested by logistic or manufacturing processes, I suggest you to have a look at the new Open ERP book.

Open ERP teams - Organisation of the community.

I am getting more and more emails from contributors or communities that organized themselves to do some contributions, discussion groups or translations on Open ERP.

I will summarize here how we propose to work to easily collaborate and consolidate efforts. If you have a group of people, I suggest to create a team on launchpad, or join an existing one. Don't forget to subscribe your team to the openerp-community team.

Then you should do all your contributions as modules, in the community or addons-extra branch, instead of doing a dedicated branch. We have now 213 active branches on launchpad, with some containing more than 200 modules. It's quite difficult to manage, have a look at contributions and consolidate efforts.

Please also avoid to create projects. Projects are dedicated to very big projects (kde clients, web clients, ...). It's better to create groups and join your efforts in the community branches. Your modules will have more visibility. Our daily generated documentation on modules, since a few days, also reports on community branches. You can check and download our 500 modules there.

Do branch only if:

• you want to modify core or modules where you don't have access rights. Then do a request for mergal.
• you want to experiment some devs before commiting them to "public" branches.

Our policy is to give commiters rights based on meritocracy. Every one can commit on the community branch. Once you have contributed 2 good modules on community branch, you can request to join the commiter team that have write access on addons-extra modules.

For details about the community organisation, read our community slidecast on OpenERP.tv.