openerp-community team mailing list archive

[Pedro Manuel Baeza Romero <pedro.baeza@xxxxxxxxx>]

Hi everybody:

During last days, we have been speaking directly with several community
members and we have also received several advices about the migration of
OpenMRP to 7.0. We are very glad about all received feedbacks and valuable
opinions of any of them. Thank you all.

Now...
Most people that contacted us was asking to take in mind next WMS in V8
so... we have analysed a little bit the impact about going to 7.0 or
directly to 8.0, and here it is an small summary of our conclusions:

We have detected that there are 2 different groups of code: master data
logic and manufacturing order management logic.

About master data, standard mrp module conceptually has got almost all the
needed concepts, except operations table, that could be easily added.
That is, good manufacturing master data aproach should include following
objects, present by now in mrp and extended in OpenMRP 6.1

   - Factory (not present on standard, but not mandatory to exist)
   - Machines
   - Operations (not present on standard)
   - Operators
   - Routes
   - Boms associated to Routes.
   - Master data for cost control (related to machines, operators and
   materials)

About new WMS, we realized that THERE IS not any impact on master data, but
only on manufacturing order (MO) management, since stock moves are only
made on that object. The only point it could impact is on machines
location, but it will be present also in WMS for sure.

About going throgh V7 or V8, we think that this plan in 2 steps would be
the best one to jump into strong manufacturing solution:

1. Refactoring master data, improve usability, improve machine cost master
data and design multicompany covered solution, mantaining old stock move
aproach on MO for v7.
2. Master data structure would be then valid for V8, and we will make it
also compatible with new trunk adapting MO management for new quant aproach
on WMS.

This way, we can covered both versions inside the same campaign. I hope
this satisfies all of you that have doubts about the scalability of the
solution.

Regards.


2013/11/29 Pedro Manuel Baeza Romero <pedro.baeza@xxxxxxxxx>

> Hi, Maxime,
>
> You can see a preview of the english website on http://en.openmrp.es.
>
> About the campaign, as Ana said, the only thing in spanish were images.
> The rest of the campaign can be seen in English, clicking on the upper
> right part of the website.
>
> Regards.
>
>
> 2013/11/29 Ana Juaristi <ajuaristio@xxxxxxxxx>
>
>> You are right. I have just realized that images are in spanish. We will
>> try to review. Thanks for telling.
>>
>> The english website... in a few days!! We are working on it. Big work
>> also. We had no time to publish yet but we are finishing.
>>
>>
>> 2013/11/29 Maxime Chambreuil <maxime.chambreuil@xxxxxxxxxxxxxxxxxxxx>
>>
>>> I would have made the campaign materials and the openmrp website in
>>> english.
>>>
>>> Give me some time to transfer the modules and you should see the MP
>>> coming soon.
>>>
>>>
>>> Regards,
>>> --
>>> Maxime Chambreuil
>>> +1 (514) 276-5468 #126
>>>
>>> ------------------------------
>>> Totally agree and even very glad you propose merging OpenERP
>>> Manufacturing against OpenMRP and not viceversa. I like the name we
>>> selected :)
>>> From begining we launched OpenMRP as OpenERP extension, never was the
>>> idea to make a fork! This idea even surprise me. Recognize that speaking
>>> about OpenERP manufacturing extended modules at it was before, is a little
>>> bit tiring name. ;P
>>>
>>> On the other side... I don't know if people on list, took a look to the
>>> crowdfunding project. If not, we invite you here:
>>> http://goteo.org/project/OpenMRP/?lang=en
>>>
>>> Please take a look to rewards. We did include accessing to demos or real
>>> installation on hosting or own server, not only having access to code but
>>> online training, consultancy and support on biggest rewards. We thought
>>> that there could be integrators/implementors on community wanting to start
>>> bussiness on manufacturing companies, so we would like to help a little bit
>>> to make easier arriving to the learning point needed to afford this kind of
>>> complex projects. Taking in mind the number of hours we are offering for
>>> that you could see that could be interesting for newbie integrators or even
>>> to final customers or those integrators.
>>> Depending on financers profile and needs we will make training sessions
>>> from starting point to specific needs, different sessions in spanish and
>>> english.
>>>
>>> I would like to know what do you think about the way we defined the
>>> campaing, rewards, objectives or you find something missing or to be
>>> improved.
>>>
>>> Just let us know please.
>>>
>>> Thank you:
>>> Ana
>>>
>>>
>>>
>>> 2013/11/29 Maxime Chambreuil <maxime.chambreuil@xxxxxxxxxxxxxxxxxxxx>
>>>
>>>> I have no issue about the crowdfunding and its motivations. I am
>>>> supporting your initiatives and I think it is a step in the right
>>>> direction. We have the same goal here.
>>>>
>>>> I am questioning the creation of a second project. The only reason I
>>>> got so far is the module incompatibility, which to me is not enough to have
>>>> 2 projects.
>>>>
>>>> Is anyone against merging "OpenERP Manufacturing" modules into the
>>>> OpenMRP project ?
>>>>
>>>> Regards,
>>>>
>>>> --
>>>> Maxime Chambreuil
>>>> +1 (514) 276-5468 #126
>>>>
>>>> ------------------------------
>>>>
>>>> Maxime... It's not exactly like that.
>>>> Modules extend base mrp so it's totally compatible but for instance mrp
>>>> operations would not be compatible with master extension as Oscar says.
>>>> About the correct site to place the project a few weeks ago i proposed
>>>> including in one community project as it is now but people said that first
>>>> we should make modules cover community code quality standars,  yaml test
>>>> and so on. Its because of that we thougth launching crowdfunding project to
>>>> raise funds and dedicate resources to it. It's because of that we opened
>>>> this thread.
>>>> We consider openmrp as an open community project so if you prefer
>>>> better having all mrp modules together no problem. You decide. :)
>>>> On the other side... To be clear...We will afford migration to 7.0 (or
>>>> maybe 8.0) just on the case campaign succed or we are financed from any
>>>> customer that need it on those versions. Otherwise I'm afraid it will not
>>>> be possible working on it in short time.
>>>> El 29/11/2013 15:57, "Maxime Chambreuil" <
>>>> maxime.chambreuil@xxxxxxxxxxxxxxxxxxxx> escribió:
>>>>
>>>>> Are you saying that you created a different project because you plan
>>>>> to make incompatible modules ?
>>>>>
>>>>> Thanks for the clarification.
>>>>> --
>>>>> Maxime Chambreuil
>>>>> +1 (514) 276-5468 #126
>>>>>
>>>>> ------------------------------
>>>>> Hi Maxime:
>>>>>
>>>>> OpenMRP is modifying MRP standar master data and database structure so
>>>>> most modules built for standard will not be valid on extended modules and
>>>>> viceversa. It's because of that I think modules should be published on
>>>>> different branches. Most of extensions on both aproaches would be not
>>>>> compatible.
>>>>>
>>>>> Standar modules cover IMHO only small assembly companies but they
>>>>> don't cover complexity of real manufacturing company.
>>>>>
>>>>> One of the aproaches of OpenMRP is controlling manufacturing by
>>>>> workorders(operations) made on machines (work centers).
>>>>> The standar modules have no way to consume or produce materials by
>>>>> workorders, or controlling semielaborated products without putting them on
>>>>> stock.
>>>>> Other functional lack on standar modules would be, manufacturing cost
>>>>> control. Normally, there is workers on machines who made the workorders. A
>>>>> manufacturing order cost is not only materials included on it but materials
>>>>> + machine cost + worker cost on each operation.
>>>>>
>>>>> Same way if you need having a real manufacturing procurement planning,
>>>>> if your operations are long time, you don't need stocking all materials at
>>>>> begining of order as in standar way but you only need having materials
>>>>> ready when you are going to start the operation that is going to consume
>>>>> them (The real manufacturing procurement planning is not covered on OpenMRP
>>>>> yet).
>>>>>
>>>>> The aproach is totally different on both solutions and both could be
>>>>> valid depending on casuistic of company's needs. Using OpenMRP will complex
>>>>> a lot configuration and proccess on any company but it will cover aspects
>>>>> unexistant on standar ones. For example, if your lead is a factory making
>>>>> asembly where they don't need calculating cost for machine(they don't have)
>>>>> or worker, probably I will propose standar modules. If you have got a
>>>>> complex production factory with production likes, machines and wanting to
>>>>> know each piece unitary real cost, I would propose OpenMRP.
>>>>>
>>>>> Wishing it will help you,
>>>>>
>>>>> Thank you:
>>>>>
>>>>> Ana
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> 2013/11/29 Maxime Chambreuil <maxime.chambreuil@xxxxxxxxxxxxxxxxxxxx>
>>>>>
>>>>>> Hello Pedro,
>>>>>>
>>>>>> Just a few questions : What will be the difference between OpenMRP
>>>>>> and OpenERP Manufacturing projects ? Where should someone put its mrp
>>>>>> related modules ?
>>>>>>
>>>>>> Thanks.
>>>>>> --
>>>>>> Maxime Chambreuil
>>>>>> +1 (514) 276-5468 #126
>>>>>>
>>>>>> ------------------------------
>>>>>> Hi, Raphael,
>>>>>>
>>>>>> Very interesting the backports and the method you have used. We will
>>>>>> look every new feature (I only make for now an oversight) of WMS trunk to
>>>>>> possible backports, but as you have said, there are some areas that simply
>>>>>> cannot be backported. If we get enough funds - I don't want to repeat
>>>>>> myself too much, but we are doing this without any other customer support -
>>>>>> we will point definitely to use all the v8 potential (without forgetting
>>>>>> v7, as I said previously).
>>>>>>
>>>>>> Regards.
>>>>>>
>>>>>> 2013/11/29 Raphael Valyi <rvalyi@xxxxxxxxx>
>>>>>>
>>>>>>> On Fri, Nov 29, 2013 at 9:12 AM, Fabien Pinckaers <fp@xxxxxxxxxxx>wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On 11/29/2013 11:51 AM, Nhomar Hernández wrote:
>>>>>>>> >
>>>>>>>> > @Fabien: I think it should be great if you share with us the
>>>>>>>> specific
>>>>>>>> > branch in this thread where the new stock is landing please, to
>>>>>>>> be sure
>>>>>>>> > everybody start with it from the same place.
>>>>>>>>
>>>>>>>>
>>>>>>>> http://bazaar.launchpad.net/~openerp-dev/openobject-addons/trunk-wms/revision/9418
>>>>>>>
>>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> just a word: eventually we don't need to wait Q2 2014 (or later?) to
>>>>>>> start building upon the new things. A few things (only) are possible to
>>>>>>> backport on v7, that will make a smoother transition to v8 when it will be
>>>>>>> stable.
>>>>>>>
>>>>>>> For instance a project I'm working with should be in production by
>>>>>>> December 31th and it needs the concept of picking waves (that many already
>>>>>>> made similar modules but nothing OCA quality like).
>>>>>>> So instead of going unstable v8 or doing crap again on regular v7, I
>>>>>>> backported the picking wave module here:
>>>>>>> https://github.com/akretion/oe-addons-subtree-stock_picking_wave
>>>>>>>
>>>>>>> By using git and git-subtree (I will eventually post about the whole
>>>>>>> trick), we are able to properly keep in synch with the upstream branch
>>>>>>> without the need to have a folder with all the v8 modules to accommodate to
>>>>>>> the addons-path.
>>>>>>> So the extracted mirror of the trunk-wms is here:
>>>>>>> https://github.com/akretion/oe-addons-subtree-stock_picking_wave/tree/trunk-wms
>>>>>>> and the backported module is a branch of it
>>>>>>> https://github.com/akretion/oe-addons-subtree-stock_picking_wave/tree/backport-7.0
>>>>>>>
>>>>>>> I think OCA could assume working this way for specific module
>>>>>>> backports (if we need a new branch of all modules for every kind of
>>>>>>> backport, soon these branches are simply incompatible and we face an
>>>>>>> combinatorial explosion of unmanageable backports). I'm willing to help
>>>>>>> setting this up in case people are interested.
>>>>>>>
>>>>>>> Now, make no mistake, backporting the new stock quant system to v7
>>>>>>> is out of question. I also extracted/backported purchase_requisition to v7
>>>>>>> that I use in another project. And something we could backport to v7 is the
>>>>>>> saas2 branch analytic_account module. Or eventually, as v8 isn't for now,
>>>>>>> we could start having a merge of saasX branches into OCB/RS-OCB. I started
>>>>>>> and I can tell the the merge is rather easy, so again I let OCA people
>>>>>>> bring the topic on the table again if they think it makes sense.
>>>>>>>
>>>>>>> That being said, I wish good luck to the funding, I also wish it
>>>>>>> base on V8 stock things as it fixes scalability issues that used to be one
>>>>>>> of the major OpenERP flaw, the kind of thing that was litteraly fueling
>>>>>>> sorryopenerp.com. This is very cool to see v8 finally bringing a
>>>>>>> lot of good work in the WMS area.
>>>>>>>
>>>>>>>
>>>>>>> Best Regards.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Raphaël Valyi
>>>>>>> Founder and consultant
>>>>>>> http://twitter.com/rvalyi <http://twitter.com/#!/rvalyi>
>>>>>>> +55 21 2516 2954
>>>>>>> www.akretion.com
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Mailing list: https://launchpad.net/~openerp-community
>>>>>>> Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
>>>>>>> Unsubscribe : https://launchpad.net/~openerp-community
>>>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Mailing list: https://launchpad.net/~openerp-community
>>>>>> Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
>>>>>> Unsubscribe : https://launchpad.net/~openerp-community
>>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Mailing list: https://launchpad.net/~openerp-community
>>>>>> Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
>>>>>> Unsubscribe : https://launchpad.net/~openerp-community
>>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> CEO Avanzosc, S.L <http://www.avanzosc.es> : Office phone / Tfono
>>>>> oficina: (+34) 943 02 69 02
>>>>> Ana Juaristi Olalde <http://www.anajuaristi.com/>: Personal phone:
>>>>> 677 93 42 59. User/usuario skype: Avanzosc
>>>>> www.openerpsite.com
>>>>>
>>>>>
>>>>>  *El contenido de esta comunicación y de toda su documentación anexa
>>>>> es confidencial y se dirige exclusivamente a su destinatario. El uso no
>>>>> autorizado de esta información está prohibido por la legislación vigente.
>>>>> Si usted no es el destinatario le rogamos nos lo indique, no comunique su
>>>>> contenido a terceros y proceda a su destrucción. Disculpe las molestias que
>>>>> le haya ocasionado la recepción indebida de este e-mail. Sus datos figuran
>>>>> en un fichero cuyo titular es Avanzosc, S.L., a quien usted puede dirigirse
>>>>> para ejercer sus derechos de acceso, rectificación, cancelación y oposición
>>>>> en Julio Urkijo, 32, 20720, Azkoitia (Gipuzkoa), Tef. 943 02 69 02 -
>>>>> administracion@xxxxxxxxxxxx <soporte@xxxxxxxxxxxx> *
>>>>>
>>>>> *Komunikazio honen edukia eta dokumentazio erantsia konfidentziala da
>>>>> eta hartzaileak bakarrik jaso beharko luke. Indarrean dagoen legeriak
>>>>> debekatu egiten du bertan eskainitako informazioa baimenik gabe erabiltzea.
>>>>> Komunikazioa zuri iritsi bazaizu, baina zu ez bazara hartzailea, mesedez,
>>>>> guri jakinarazi, eta jasotako informazioa ez inori jakinarazi eta suntsitu.
>>>>> Barkatu okerreko email hau jasotzeak eragindako eragozpenak. Zure datuak
>>>>> Avanzosc, S.L. enpresaren fitxategietan sartuta daude. Zure datuak atzitzea
>>>>> eska dezakezu, bai eta, datuak zuzentzea, ezereztea eta tratamenduari aurka
>>>>> egitea ere. Horretarako, enpresara jo dezakezu, helbide honetan: Julio
>>>>> Urkijo, 32, 20720, Azkoitia (Gipuzkoa), telefonoa: 943 02 69 02 - **administracion@xxxxxxxxxxxx
>>>>> <soporte@xxxxxxxxxxxx> *
>>>>> *This message and all documents attached to it are confidential and
>>>>> intended only for the person or entity to which it is addressed. Any use of
>>>>> this information by unauthorised persons is prohibited under current
>>>>> legislation. If you received this message by error, please advise us,
>>>>> destroy it and refrain from communicating its contents to third parties. We
>>>>> apologise for any inconvenience receiving this email improperly may cause
>>>>> to you. Your personal data are included in a file owned by Avanzosc, S.L.
>>>>> If you want to exercise your rights of access, correction, erasure and
>>>>> objection you can contact the Controller at Julio Urkijo, 32, 20720,
>>>>> Azkoitia (Gipuzkoa), T: 943 02 69 02 – administracion@xxxxxxxxxxxx
>>>>> <soporte@xxxxxxxxxxxx>*
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> CEO Avanzosc, S.L <http://www.avanzosc.es> : Office phone / Tfono
>>> oficina: (+34) 943 02 69 02
>>> Ana Juaristi Olalde <http://www.anajuaristi.com/>: Personal phone: 677
>>> 93 42 59. User/usuario skype: Avanzosc
>>> www.openerpsite.com
>>>
>>>
>>> *El contenido de esta comunicación y de toda su documentación anexa es
>>> confidencial y se dirige exclusivamente a su destinatario. El uso no
>>> autorizado de esta información está prohibido por la legislación vigente.
>>> Si usted no es el destinatario le rogamos nos lo indique, no comunique su
>>> contenido a terceros y proceda a su destrucción. Disculpe las molestias que
>>> le haya ocasionado la recepción indebida de este e-mail. Sus datos figuran
>>> en un fichero cuyo titular es Avanzosc, S.L., a quien usted puede dirigirse
>>> para ejercer sus derechos de acceso, rectificación, cancelación y oposición
>>> en Julio Urkijo, 32, 20720, Azkoitia (Gipuzkoa), Tef. 943 02 69 02 -
>>> administracion@xxxxxxxxxxxx <soporte@xxxxxxxxxxxx> *
>>>
>>> *Komunikazio honen edukia eta dokumentazio erantsia konfidentziala da
>>> eta hartzaileak bakarrik jaso beharko luke. Indarrean dagoen legeriak
>>> debekatu egiten du bertan eskainitako informazioa baimenik gabe erabiltzea.
>>> Komunikazioa zuri iritsi bazaizu, baina zu ez bazara hartzailea, mesedez,
>>> guri jakinarazi, eta jasotako informazioa ez inori jakinarazi eta suntsitu.
>>> Barkatu okerreko email hau jasotzeak eragindako eragozpenak. Zure datuak
>>> Avanzosc, S.L. enpresaren fitxategietan sartuta daude. Zure datuak atzitzea
>>> eska dezakezu, bai eta, datuak zuzentzea, ezereztea eta tratamenduari aurka
>>> egitea ere. Horretarako, enpresara jo dezakezu, helbide honetan: Julio
>>> Urkijo, 32, 20720, Azkoitia (Gipuzkoa), telefonoa: 943 02 69 02 - **administracion@xxxxxxxxxxxx
>>> <soporte@xxxxxxxxxxxx> *
>>> *This message and all documents attached to it are confidential and
>>> intended only for the person or entity to which it is addressed. Any use of
>>> this information by unauthorised persons is prohibited under current
>>> legislation. If you received this message by error, please advise us,
>>> destroy it and refrain from communicating its contents to third parties. We
>>> apologise for any inconvenience receiving this email improperly may cause
>>> to you. Your personal data are included in a file owned by Avanzosc, S.L.
>>> If you want to exercise your rights of access, correction, erasure and
>>> objection you can contact the Controller at Julio Urkijo, 32, 20720,
>>> Azkoitia (Gipuzkoa), T: 943 02 69 02 – administracion@xxxxxxxxxxxx
>>> <soporte@xxxxxxxxxxxx>*
>>>
>>>
>>
>>
>> --
>> CEO Avanzosc, S.L <http://www.avanzosc.es> : Office phone / Tfono
>> oficina: (+34) 943 02 69 02
>> Ana Juaristi Olalde <http://www.anajuaristi.com/>: Personal phone: 677
>> 93 42 59. User/usuario skype: Avanzosc
>> www.openerpsite.com
>>
>>
>> *El contenido de esta comunicación y de toda su documentación anexa es
>> confidencial y se dirige exclusivamente a su destinatario. El uso no
>> autorizado de esta información está prohibido por la legislación vigente.
>> Si usted no es el destinatario le rogamos nos lo indique, no comunique su
>> contenido a terceros y proceda a su destrucción. Disculpe las molestias que
>> le haya ocasionado la recepción indebida de este e-mail. Sus datos figuran
>> en un fichero cuyo titular es Avanzosc, S.L., a quien usted puede dirigirse
>> para ejercer sus derechos de acceso, rectificación, cancelación y oposición
>> en Julio Urkijo, 32, 20720, Azkoitia (Gipuzkoa), Tef. 943 02 69 02 -
>> administracion@xxxxxxxxxxxx <soporte@xxxxxxxxxxxx> *
>>
>> *Komunikazio honen edukia eta dokumentazio erantsia konfidentziala da eta
>> hartzaileak bakarrik jaso beharko luke. Indarrean dagoen legeriak debekatu
>> egiten du bertan eskainitako informazioa baimenik gabe erabiltzea.
>> Komunikazioa zuri iritsi bazaizu, baina zu ez bazara hartzailea, mesedez,
>> guri jakinarazi, eta jasotako informazioa ez inori jakinarazi eta suntsitu.
>> Barkatu okerreko email hau jasotzeak eragindako eragozpenak. Zure datuak
>> Avanzosc, S.L. enpresaren fitxategietan sartuta daude. Zure datuak atzitzea
>> eska dezakezu, bai eta, datuak zuzentzea, ezereztea eta tratamenduari aurka
>> egitea ere. Horretarako, enpresara jo dezakezu, helbide honetan: Julio
>> Urkijo, 32, 20720, Azkoitia (Gipuzkoa), telefonoa: 943 02 69 02 - **administracion@xxxxxxxxxxxx
>> <soporte@xxxxxxxxxxxx> *
>> *This message and all documents attached to it are confidential and
>> intended only for the person or entity to which it is addressed. Any use of
>> this information by unauthorised persons is prohibited under current
>> legislation. If you received this message by error, please advise us,
>> destroy it and refrain from communicating its contents to third parties. We
>> apologise for any inconvenience receiving this email improperly may cause
>> to you. Your personal data are included in a file owned by Avanzosc, S.L.
>> If you want to exercise your rights of access, correction, erasure and
>> objection you can contact the Controller at Julio Urkijo, 32, 20720,
>> Azkoitia (Gipuzkoa), T: 943 02 69 02 – administracion@xxxxxxxxxxxx
>> <soporte@xxxxxxxxxxxx>*
>>
>
>