Tryton - Issues

 

Issue5560

Title Add lead time for production
Priority feature Status resolved
Superseder Nosy List SISalp, ced, roundup-bot
Type feature request Components production, production_routing, stock_supply_production
Assigned To ced Keywords review
Reviews 22001002, 23131003, 27291002
View: 22001002, 23131003, 27291002

Created on 2016-05-19.18:04:14 by ced, last changed by roundup-bot.

Messages
New changeset d57ef08cda75 by C?dric Krier in branch 'default':
Add routing as Lead Time parameter
http://hg.tryton.org/modules/production_routing/rev/d57ef08cda75
New changeset d707814be4a1 by C?dric Krier in branch 'default':
Compute planned start date on production request
http://hg.tryton.org/modules/stock_supply_production/rev/d707814be4a1
New changeset 53c77a86adf6 by C?dric Krier in branch 'default':
Manage lead time on production
http://hg.tryton.org/modules/production/rev/53c77a86adf6
msg25936 (view) Author: [hidden] (ced) (Tryton committer) (Tryton translator) Date: 2016-05-23.15:08:26
I updated reviews to use a MatchMixin design for the lead time and added review27291002 which adds routing as paramter for lead time.
msg25907 (view) Author: [hidden] (SISalp) Date: 2016-05-20.11:34:53
I agree with your answers.
msg25906 (view) Author: [hidden] (ced) (Tryton committer) (Tryton translator) Date: 2016-05-20.11:10:08
On 2016-05-20 10:26, SISalp wrote:
> Re-thinking about it, lead time includes part provisionning delay if not in stock + manufacturing routing time. When we have no BOM, it is the delay to receive it from the supplier + internal moves.

No this it not the lead time of this issue, you are talking about the
supplier lead time.

> If there are BOMs, it is the delay of the longest part to become available, if there are routes, it is the longest part + route time.
> Shouldn't it be in the product directly ? not in the route definitly.

I think the production lead time depends definitely on the BOM used. If
you build the product out of 2 big pieces or out of 100 small pieces, it
takes different time.

> Lead time should have a "max value" in case nothing is available in stock or no reservation is possible on stock and a lead-time-at-a-given-date (usually what is called lead time) which considers the stock at that given date.

This is not our current topic. Here we talk only about the time needed
to do the production. Not the time needed to deliver the product to the
customer.
msg25902 (view) Author: [hidden] (SISalp) Date: 2016-05-20.10:26:02
Re-thinking about it, lead time includes part provisionning delay if not in stock + manufacturing routing time. When we have no BOM, it is the delay to receive it from the supplier + internal moves.
If there are BOMs, it is the delay of the longest part to become available, if there are routes, it is the longest part + route time.
Shouldn't it be in the product directly ? not in the route definitly.
Lead time should have a "max value" in case nothing is available in stock or no reservation is possible on stock and a lead-time-at-a-given-date (usually what is called lead time) which considers the stock at that given date.
I don't know the correct wording for these different things.
msg25899 (view) Author: [hidden] (ced) (Tryton committer) (Tryton translator) Date: 2016-05-20.08:25:27
You are right but I think it is important to have this feature even if production_routing is not installed.
Maybe it will be better to use MatchMixin on product with by default bom as parameter and the production_routing will add routing as parameters. This will allow to extend it to any other parameter like the work center, the warehouse etc.
msg25897 (view) Author: [hidden] (SISalp) Date: 2016-05-19.23:49:59
Why not adding it to the route instead ?
Lead time is mainly the sum of theoritical time of all operations.
msg25896 (view) Author: [hidden] (ced) (Tryton committer) (Tryton translator) Date: 2016-05-19.18:06:29
Here is review23131003 and review22001002
msg25895 (view) Author: [hidden] (ced) (Tryton committer) (Tryton translator) Date: 2016-05-19.18:04:12
Currently, the productions are supposed to only last 1 day.
This means that the input moves have the same planned date as the output.
But some kind of productions could last longer than 1 day and so the input moves should be planned earlier.
The proposal is to add a lead time on the BOM (the duration of a production is mainly linked to its BOM, I think) and to add start dates on the production (which will be automatically computed out of the planned date and the BOM lead time).
History
Date User Action Args
2016-06-24 09:24:58roundup-botsetmessages: + msg26514
2016-06-24 09:24:14roundup-botsetmessages: + msg26513
2016-06-24 09:23:09roundup-botsetstatus: testing -> resolved
nosy: + roundup-bot
messages: + msg26512
2016-05-23 15:30:09reviewbotsetreviews: 22001002, 23131003 -> 22001002, 23131003, 27291002
2016-05-23 15:08:27cedsetcomponent: + production_routing
messages: + msg25936
2016-05-20 11:34:54SISalpsetmessages: + msg25907
2016-05-20 11:10:09cedsetmessages: + msg25906
2016-05-20 10:26:03SISalpsetmessages: + msg25902
2016-05-20 08:25:28cedsetmessages: + msg25899
2016-05-19 23:49:59SISalpsetnosy: + SISalp
messages: + msg25897

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