Am 19.01.2011 09:56, schrieb Cédric Krier:
On 19/01/11 09:44 +0100, Jan Grasnick | Grasbauer UG wrote:
Am 19.01.2011 09:30, schrieb Cédric Krier:
On 19/01/11 08:42 +0100, Jan Grasnick | Grasbauer UG wrote:
Am 19.01.2011 00:05, schrieb Cédric Krier:
On 18/01/11 23:18 +0100, Jan Grasnick | Grasbauer UG wrote:
Buenas Tardes desde Allemania,
muy bien escuchar kastilliano aka;)
I'm interested in this module and will give it a try soon. I wrote a
little extension to the project-module, which associates projects to
sales and some other presale activities. The employee checks in
time.lines to the project - so its interesting to extend the employee
with informations of his weekly worktime to validate this in
project_plan. so cedk comment is reasonable: your modul should extend
the employee. if I know the salary of a employee, i can calculate the
costs of a project or something else.
It is already the case with the module project_revenue.
Yes. I'm still extending the project module.
- project gets a field code
This could go in the main module.
- project can be associated with quality tests (new module)
- project is related to a sale
- a project report
- a wizzard and a small client to checkin timelines (timesheet.line
computes hours from start_time and end_time)
- Lines associated to stock ( materials consumption)
this is my idea to get a low level production planning in tryton (for
processing industries- here coating)
I'm not sure it is the right way.
I agree that it is good to define product used for a project/task but I'm not
sure it is enough for a production modeling.
Did you take a look at the blueprint
http://code.google.com/p/tryton/wiki/TrytonMRPIntegration
yes - i did. But there are problems with this model in processing
industries. I cant explain it right now, but I'm reading books about
production planning in processing industries ;)
the BOM-model works in a production with repeating products (a computer
with n parts). In the processing industries each product can be
different to each other.
So i wrote a extra model accociated to sales and products, which holds
the specification. hard to explain - but i will report my success soon.
Ok. I did not understand like that.
Indeed you just put product to consume on the project/task.
You should perhaps think about using the Internal Shipment to create the moves
from storage to production location.
Yes - I still explore the whole stock_module an all extensions.
Finally the project comsumes more than one Product - so project revenue
isn't enough. So are 2 ways to manage this: the product is associated to
a fixed BOM like in the blueprint of MRP or the process himself
associates his consume by checking in realtime consumption. I prefer
second: a planned consumption like a BOM_Template related to the product
and a continuous check in of consumptions invoked by the the employees
involved in the project.
--
[email protected] mailing list
