# Production planning
**URL:** https://discuss.tryton.org/t/production-planning/5291
**Category:** Ideas
**Tags:** production
**Created:** [May 25, 2022, 1:45pm UTC](https://discuss.tryton.org/t/production-planning/5291 "2022-05-25T13:45:18Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@acaubet](https://discuss.tryton.org/u/acaubet)
#### Post date: [May 25, 2022, 1:45pm UTC](https://discuss.tryton.org/t/production-planning/5291/1 "2022-05-25T13:45:19Z")
We have a costumer which produces unique costumer parts (like 3D, each customer sends them a unique drawing), so they use Tryton for creating a product with a bom inputs of their materials, and also the works to do in each work center (machines).
The problem they are facing is that they don’t want to produce JIT as Tryton proposes, they want to plan the production works based on the company availability of work centers. Also in order to get the max production output for each machine they need a production planning schedule to move works between machines.
Some needs we see are:
- Allow to define a start\_planned\_time and estimated\_time for work.
- Plan de production depending on work duration, something like:
production.planned\_start\_date = min(w.start\_planned\_time for w in ws)
production.planned\_date = max(w.start\_planned\_time + w.estimated\_time for w in ws)
- The works can sometimes take more or less than estimated\_time.
- Works of a production needs to allow planning in parallel (as some process can start at the same time of the another) or selecting a parent work (because they can not be produced until a job is finished).
- Also the start\_planned\_time must take care of the availability of each machine. So if the printers have pending previous jobs from other productions until tomorrow 10:00, the new work must be planned at 10:01am.
- Calendar view to allow to see all the planned jobs where we can filter by work\_center to see all the jobs of the machine.
I think there are a lot of this features not specific of our costumer but related to the use case of production work planning which Tryton may benefit of.
---
### Author:  [@ced](https://discuss.tryton.org/u/ced)
#### Post date: [May 26, 2022, 9:01am UTC](https://discuss.tryton.org/t/production-planning/5291/2 "2022-05-26T09:01:17Z")
For me Tryton code will never do planning. This must be delegated to specialized tools like [https://frepple.org/](https://frepple.org/).
But we can have similar modules like `stock_quantity_issue` and `stock_quantity_early_planning` based on the work center capacities.
> [@acaubet](#):
>
> Allow to define a start\_planned\_time and estimated\_time for work.
I’m not sure the planning should be stored with time in most cases but just maybe just ordered over the day.
> [@acaubet](#):
>
> Calendar view to allow to see all the planned jobs where we can filter by work\_center to see all the jobs of the machine.
Calendar views are often not usable at large scale. Usually a [PERT chart](https://en.wikipedia.org/wiki/Program_evaluation_and_review_technique) is better. The basis storage was implemented in `project_plan` but never took off.
---
### Author:  [@pokoli](https://discuss.tryton.org/u/pokoli)
#### Post date: [May 26, 2022, 10:15am UTC](https://discuss.tryton.org/t/production-planning/5291/3 "2022-05-26T10:15:56Z")
> [@ced](#):
>
> For me Tryton code will never do planning. This must be delegated to specialized tools like [https://frepple.org/](https://frepple.org/).
Of course, but as employees are using Tryton to know which work they should do we should save the result of the planning into Tryton. So this means that:
- We should store for each work it’s planned start and end date.
- Update the production start and end\_date based on the work planning (so we do not need to purchase materials that can not be used for the works).
> [@ced](#):
>
> But we can have similar modules like `stock_quantity_issue` and `stock_quantity_early_planning` based on the work center capacities.
Do not follow you here. Why do you want such modules? AFAIU as the planning with external tools the should just be saved to tryton.
---
### Author:  [@ced](https://discuss.tryton.org/u/ced)
#### Post date: [May 26, 2022, 10:23am UTC](https://discuss.tryton.org/t/production-planning/5291/4 "2022-05-26T10:23:24Z")
> [@pokoli](#):
>
> We should store for each work it’s planned start and end date.
For me this is already stored on the production. I do not think the planning should go at this level. If you think it is needed, I think it is because production should be divided.
> [@pokoli](#):
>
> Why do you want such modules?
To fix manually the default planning.