Tryton - Issues

 

Issue8888

Title Allow empty work center on work request
Priority feature Status testing
Superseder Nosy List ced, pokoli, reviewbot
Type feature request Components production_work
Assigned To pokoli Keywords
Reviews 280531002
View: 280531002

Created on 2019-12-02.10:19:11 by pokoli, last changed by ced.

Messages
msg54459 (view) Author: [hidden] (ced) (Tryton committer) (Tryton translator) Date: 2019-12-12.10:04:27
On 2019-12-02 16:55, Sergi Almacellas Abellana wrote:
> About second 
> 
> > First the initial work center can be chosen on the production order. This often is enough to define all the production chain used because there are not very often split in the production chain (not efficient).
> 
> Maybe our case is some speciall but we are not able to define all the production chain based on the production work center. On our center we have severall independent machines that are not tight together and there are two of them of the same category. 
> 
> > Second the work center is required on production work so it must be filled. If there are multiple choice, it is not bad to randomly assign them because it will give the same amount of work to each one.
> 
> This does not work for us as we should take in account the time that the machine needs to work. For example, is not the same to do the same operation on a production of 100 units than on a production of 2000 units. 

Well that's about splitting production orders and planning them.
I do not think it is a problem to assign by default a work center as it
can still be replanned after.

> > Third, the picker is designed to be customized to implement the rule of the company.
> > Forth we can not ask the user to choose manually for every work the work center to use.
> 
> The rule on the company is: "There is one user which should set the work center for each work".

Well that too bad because the software is there to avoid or reduce such
manual task.
But any way as I said, this task can still be done manually afterward.

> So third and forth are currently not possible for us. 
> 
> After reading your points I think the best is to relax the required contraint on production_work module but keep the picker as is. This way we do not change the behaviour but we allow extension on custom modules.

OK but then the work center must be required to go to waiting state.
review280531002 updated at https://codereview.tryton.org/280531002/#ps258521002
msg53790 (view) Author: [hidden] (pokoli) (Tryton committer) (Tryton translator) Date: 2019-12-02.16:55:18
About second 

> First the initial work center can be chosen on the production order. This often is enough to define all the production chain used because there are not very often split in the production chain (not efficient).

Maybe our case is some speciall but we are not able to define all the production chain based on the production work center. On our center we have severall independent machines that are not tight together and there are two of them of the same category. 

> Second the work center is required on production work so it must be filled. If there are multiple choice, it is not bad to randomly assign them because it will give the same amount of work to each one.

This does not work for us as we should take in account the time that the machine needs to work. For example, is not the same to do the same operation on a production of 100 units than on a production of 2000 units. 


> Third, the picker is designed to be customized to implement the rule of the company.
> Forth we can not ask the user to choose manually for every work the work center to use.

The rule on the company is: "There is one user which should set the work center for each work".

So third and forth are currently not possible for us. 

After reading your points I think the best is to relax the required contraint on production_work module but keep the picker as is. This way we do not change the behaviour but we allow extension on custom modules.
New review280531002 at https://codereview.tryton.org/280531002/#ps270621002
msg53779 (view) Author: [hidden] (ced) (Tryton committer) (Tryton translator) Date: 2019-12-02.10:36:03
I do not think it is a good idea.
First the initial work center can be chosen on the production order. This often is enough to define all the production chain used because there are not very often split in the production chain (not efficient).
Second the work center is required on production work so it must be filled. If there are multiple choice, it is not bad to randomly assign them because it will give the same amount of work to each one.
Third, the picker is designed to be customized to implement the rule of the company.
Forth we can not ask the user to choose manually for every work the work center to use.
review280531002 updated at https://codereview.tryton.org/280531002/#ps288621002
msg53776 (view) Author: [hidden] (pokoli) (Tryton committer) (Tryton translator) Date: 2019-12-02.10:19:11
Currently the production work center is picked randomly from the available Work centers. This is not optimal when there are multiple work centers capable of doing a work as the user is not able to distinguis which work centers had been automatically chosen by the system (without a random criteria) and which ones had been chosen by a user.

There are some companies there is one person responible of chosing where each work should be performed, so it is not possible to have a list of pending works to assign for this user as they are always automatically picked by the system. 

I think both cases will be better managed on Tryton if no Work Center is chosed when there is more than one capable of doing it so we force the user to decided on which one should be done. So in order to support this workflow we should make the work center non mandatory on request state.
History
Date User Action Args
2019-12-12 10:04:27cedsetmessages: + msg54459
2019-12-02 17:06:34reviewbotsetmessages: + msg53791
2019-12-02 16:55:19pokolisetstatus: in-progress -> testing
messages: + msg53790
keyword: - review
title: Avoid chosing work center randomly -> Allow empty work center on work request
2019-12-02 11:08:27reviewbotsetnosy: + reviewbot
messages: + msg53780
2019-12-02 11:08:26reviewbotsetreviews: 280531002
keyword: + review
2019-12-02 10:36:03cedsetstatus: testing -> in-progress
reviews: 280531002 -> (no value)
messages: + msg53779
keyword: - review
nosy: + ced, - reviewbot
2019-12-02 10:33:30reviewbotsetnosy: + reviewbot
messages: + msg53778
2019-12-02 10:20:25pokolisetstatus: in-progress -> testing
reviews: 280531002
keyword: + review
2019-12-02 10:19:11pokolicreate

Showing 10 items. Show all history (warning: this could be VERY long)