Manufacturing Order Useability Improvement, trunk

Bug #506017 reported by Fabien (Open ERP)
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Fix Released
Wishlist
Unassigned

Bug Description

Hello,

We need to improve the manufacturing order form in trunk. The main reasons are:
ability to easily manage partial productions, lots & serial number encoding, scrapping
wrong products.

See in attach the full specifications of the screen to change.

Note on the implementation:
- Products to Consume is the current move_lines field, but adding a domain on the stock.move: state <> ('done','cancel')
- Consumed Products (move_lines2) should point to the exact same table mrp_production_move_ids but with another domain: state in ('done','cancel')

So, when products are consummed, they go from the left field up to the right field. If the checkbox field track_production is set on the product form, split the move lines by qty of one when the products are consumed. (on the right panel, the user can set the lot numbers through the editable list)

We change the workflow according to v5.0: The button "Start Production" does not consumme the products anymore, it just change the status of the manufacturing order. (renamed by Mark as Started)

The "consume products" wizard change the state of the move line to done.
The "Split in Lots" wizard allows to split one line of 5 items in 5 lines of 1 items, providing the lots numbers.
The "Scrap Products" allows to split a line and change the destination location of some products. (reuse the method on stock.move to split a line)
The production wizards allows to consume and produce the products.

The Production Done wizard consume all raw materials (set state to done) and product all finished products. There is a method on the stock.move obejcts to change state (to done)

Related branches

Revision history for this message
Fabien (Open ERP) (fp-tinyerp) wrote :
description: updated
Revision history for this message
Ana Juaristi Olalde (ajuaristio) wrote :

Fabien... any improvement on production and mrp modules would be wellcome... but I think there is some basis are not bearing in account in OpenERP

I think most of functionality actually attached to the order, should be translated to operations. It's not possible manufacturing without doing any operation. Manufacturing order should only be a container of some elements such operations, materials, working hours...

Defining a manufacturing order should be nothing more than defininig the need or doing some taks using some resources and materials.
Stock movements should be done, no on the order but in operations. First operation should move row materials from a phisical stock location to virtual production location (defined for each material) and last operation shoud move finished materials from virtual production location to phisical stock location. Intermediate virtual locations for each production centers should be defined and material movements should be made each time an operation is started or finished. Operations shoud be made on a work center, and there could be a template to define most common operations made on the company, with name and description. (Such a "cut wood", "paint material A")

Each operation takes material and gives material. Taken material and given material could not be the same. Imaging you are making bread... First of all you need water, farine and salt... but you need producing intermediate semielaborated material mass that you can directly introduce to an oven on same production order... or you can decide to freaze and stock the mass so it could be used for other production order...

If you are interested on knowing my opinion, I'm building a complete generic manufacturing requirements document, actually not included on OpenERP from basis and configuration to operation management and cost control.

Document is still in draft mode (i began few days ago) and written in spanish. My idea was finding manufacturing potential customer who could be interested on financing this development requirements but I think is mandatory having OpenERP tiny and partner manufacturers experts opinion before begining doing anything.

If you find it interesting I can translate and post it here...

Please tell me...

Ana

Revision history for this message
Fabien (Open ERP) (fp-tinyerp) wrote : Re: [Bug 506017] Re: Manufacturing Order Useability Improvement, trunk

Hello,

We need both:

1. A simple manufacturing system for companies that do not manage each
operations but manufaturing orders.
2. A way to manage through operations.

I made the specs for the point 1. For the point 2, there is the
mrp_operation module that allows to do that.

Thanks,

Ana Juaristi Olalde wrote:
> Fabien... any improvement on production and mrp modules would be
> wellcome... but I think there is some basis are not bearing in account
> in OpenERP
>
> I think most of functionality actually attached to the order, should be
> translated to operations. It's not possible manufacturing without doing
> any operation. Manufacturing order should only be a container of some
> elements such operations, materials, working hours...
>
> Defining a manufacturing order should be nothing more than defininig the need or doing some taks using some resources and materials.
> Stock movements should be done, no on the order but in operations. First operation should move row materials from a phisical stock location to virtual production location (defined for each material) and last operation shoud move finished materials from virtual production location to phisical stock location. Intermediate virtual locations for each production centers should be defined and material movements should be made each time an operation is started or finished. Operations shoud be made on a work center, and there could be a template to define most common operations made on the company, with name and description. (Such a "cut wood", "paint material A")
>
> Each operation takes material and gives material. Taken material and
> given material could not be the same. Imaging you are making bread...
> First of all you need water, farine and salt... but you need producing
> intermediate semielaborated material mass that you can directly
> introduce to an oven on same production order... or you can decide to
> freaze and stock the mass so it could be used for other production
> order...
>
> If you are interested on knowing my opinion, I'm building a complete
> generic manufacturing requirements document, actually not included on
> OpenERP from basis and configuration to operation management and cost
> control.
>
> Document is still in draft mode (i began few days ago) and written in
> spanish. My idea was finding manufacturing potential customer who could
> be interested on financing this development requirements but I think is
> mandatory having OpenERP tiny and partner manufacturers experts opinion
> before begining doing anything.
>
> If you find it interesting I can translate and post it here...
>
> Please tell me...
>
> Ana
>

--
Fabien Pinckaers
CEO Tiny - OpenERP Editor
Chaussée de Namur 40
B-1367 Grand-Rosière
Belgium
Phone: +32.81.81.37.00
Fax: +32.81.73.35.01
Web: http://openerp.com

Great Achievements Start With Tiny Investments
  -- Marty, 2005

Revision history for this message
Ana Juaristi Olalde (ajuaristio) wrote : Re: [Bug 506017] Re: Manufacturing Order Useability Improvement, trunk
Download full text (5.1 KiB)

mrp_operation does fill some steps.. but not almost required... My document
would be related to point 2...

2010/1/11 Fabien (Open ERP) <email address hidden>

> Hello,
>
> We need both:
>
> 1. A simple manufacturing system for companies that do not manage each
> operations but manufaturing orders.
> 2. A way to manage through operations.
>
> I made the specs for the point 1. For the point 2, there is the
> mrp_operation module that allows to do that.
>
> Thanks,
>
> Ana Juaristi Olalde wrote:
> > Fabien... any improvement on production and mrp modules would be
> > wellcome... but I think there is some basis are not bearing in account
> > in OpenERP
> >
> > I think most of functionality actually attached to the order, should be
> > translated to operations. It's not possible manufacturing without doing
> > any operation. Manufacturing order should only be a container of some
> > elements such operations, materials, working hours...
> >
> > Defining a manufacturing order should be nothing more than defininig the
> need or doing some taks using some resources and materials.
> > Stock movements should be done, no on the order but in operations. First
> operation should move row materials from a phisical stock location to
> virtual production location (defined for each material) and last operation
> shoud move finished materials from virtual production location to phisical
> stock location. Intermediate virtual locations for each production centers
> should be defined and material movements should be made each time an
> operation is started or finished. Operations shoud be made on a work center,
> and there could be a template to define most common operations made on the
> company, with name and description. (Such a "cut wood", "paint material A")
> >
> > Each operation takes material and gives material. Taken material and
> > given material could not be the same. Imaging you are making bread...
> > First of all you need water, farine and salt... but you need producing
> > intermediate semielaborated material mass that you can directly
> > introduce to an oven on same production order... or you can decide to
> > freaze and stock the mass so it could be used for other production
> > order...
> >
> > If you are interested on knowing my opinion, I'm building a complete
> > generic manufacturing requirements document, actually not included on
> > OpenERP from basis and configuration to operation management and cost
> > control.
> >
> > Document is still in draft mode (i began few days ago) and written in
> > spanish. My idea was finding manufacturing potential customer who could
> > be interested on financing this development requirements but I think is
> > mandatory having OpenERP tiny and partner manufacturers experts opinion
> > before begining doing anything.
> >
> > If you find it interesting I can translate and post it here...
> >
> > Please tell me...
> >
> > Ana
> >
>
>
> --
> Fabien Pinckaers
> CEO Tiny - OpenERP Editor
> Chaussée de Namur 40
> B-1367 Grand-Rosière
> Belgium
> Phone: +32.81.81.37.00
> Fax: +32.81.73.35.01
> Web: http://openerp.com
>
> Great Achievements Start With Tiny Investments
> -- Marty, 2005
>
> --
> Manufacturing Order Us...

Read more...

Changed in openobject-addons:
assignee: nobody → Xavier (Open ERP) (xmo)
Revision history for this message
Ana Juaristi Olalde (ajuaristio) wrote :

Hi everybody.

Reviewing my document I was not able to translate in a comprehensible way, so.. I did 2 video tutorials. Here someone use to say that an image is better than 1000 words...

So here you are:

1. Actual manufacturing functionality on openerp
2. New advanced manufacturing requirements, on actual screens. Needed new objects, fields and assistants.

To see tutorials, you only have to unzip the attached files to a directory and open the .html files.

I attached the original wink used to build the videotutorials if you wanna change, correct, add or make something..
Sorry because of my primitive english. If you don't understand anything please, ask...

Revision history for this message
Ana Juaristi Olalde (ajuaristio) wrote :

Here first one showing actual manufacturing functionality on openerp.

Revision history for this message
Ana Juaristi Olalde (ajuaristio) wrote :

This one, advanced requirements for working with operations in OpenERP

Revision history for this message
Grzegorz Grzelak (OpenGLOBE.pl) (grzegorz-og.pl) wrote :
Download full text (7.3 KiB)

I have added this text to Ana Blueprint of Operations. It is very close to Ana proposal with other approach.

I think concept of operations should be implemented as OpenERP is targeted to small and medium companies which can prefer flat BoM with chained operations than big hierarchical BoMs. But this concept only improve hierarchical concept. No current functionality is lost.

First I think we should change the term routing to operation. Sounds strange but read the explanation:
In current functionality routing is the smallest unit of work. So the name "operation" is natural for it. I know that system uses term operation for workcenters in module mrp_operations. But it is inconsistent. Workcenters are RESOURCES and shouldn't be convereted to workorders in Production orders. Note that when you define workcenter you have to choose Type (Human resource, Machine, Tool) which says clear they are RESOURCES. And they are used in operation which currently is named routing.

Name routing should be assigned to chain of operation. Do we have such chain? Yes it is a BoM structure. It is mixed with raw materials but it exists. We of course can implement another concept having another object between routing and workcenters but I propose to use concept as below.

First I describe the BoM and then how BoM is reflected to Production order.

I will try reflect description with example:
Operation 1 Cutting, raw material - plunk, finished - Panel 'In Production', workcenters - cutting worker, cutting machine,
Operation 2 Drilling, raw materials - Panel 'In Production', finished - Panel 'In Production', workcenters - drilling worker, drilling machine,
Operation 3 Painting, raw materials - Paint, Panel 'In Production', finished - Panel 'In Production', workcenter - painter, painting machine,
Operation 4 Assembling, raw materials - screws, finished - Panel, workcenter - assembly worker, screwdriver machine.

You see that already after first operation we have product "Panel" but it is not final product. We have to implement product state "In production" or even states after each operation named "After >Cutting<", "After >Drilling<" etc. And as you will see in further description only Panel after last operation is treated as final product.

BoM:
- The main Operation (Routing) in BoM form is the only or last operation made of this BoM.
- All raw materials in BoM structure are consumed in main (last) Operation.
- In BoM structure list we can place operations (routings). We can do it now but I propose different functionality.
- For operations we need a sequence column in BoM Structure list. Sequence will be ignored for pure raw material. Sequence field already exists for routings in BoM (Properties Tab) but it doesn't work or I cannot guess how it works.
- We can place the final product also on BoM Structure list what means that this operation creates "In production" semifinal product.
- Each operation (routing) has input and output location or warehouse as I described in different blueprint.

So in main fields of BoM we enter Product Panel (final product of BoM), then we place the Assembling (last operation) in main field of BoM and place screws in BoM Structure in...

Read more...

Revision history for this message
Ana Juaristi Olalde (ajuaristio) wrote :
Download full text (5.5 KiB)

Please let me writing some notes about concepts explained here.

2010/1/13 Grzegorz Grzelak (Cirrus) <email address hidden>

> I have added this text to Ana Blueprint of Operations. It is very close
> to Ana proposal with other approach.
>
Thank you for reading my opinions!!

>
> I think concept of operations should be implemented as OpenERP is
> targeted to small and medium companies which can prefer flat BoM with
> chained operations than big hierarchical BoMs. But this concept only
> improve hierarchical concept. No current functionality is lost.
>
For me... BOM is BOM... materials. And operations are operations. Work
tasks. So Tiny aprochement about this concept is perfectly correct for me.

>
> First I think we should change the term routing to operation. Sounds
> strange but read the explanation:
> In current functionality routing is the smallest unit of work. So the name
> "operation" is natural for it. I know that system uses term operation for
> workcenters in module mrp_operations. But it is inconsistent. Workcenters
> are RESOURCES and shouldn't be convereted to workorders in Production
> orders. Note that when you define workcenter you have to choose Type (Human
> resource, Machine, Tool) which says clear they are RESOURCES. And they are
> used in operation which currently is named routing.
>
>
Routing is an operation chaining. Agree with workcenters are resources. Even
I think hr resources would not be a workcenter but people who works in
operations in a workcenter. Workcenter would be a machine asociated to a
location.

> Name routing should be assigned to chain of operation. Do we have such
> chain? Yes it is a BoM structure. It is mixed with raw materials but it
> exists. We of course can implement another concept having another object
> between routing and workcenters but I propose to use concept as below.
>
> For me, that aprochement is complicating so much configuration and
operation, so we are loosing flexibility on manufacturing. Sorry... it's my
opinion.

> First I describe the BoM and then how BoM is reflected to Production
> order.
>
> I will change this like following:

> I will try reflect description with example:
> Operation 1 Cutting, raw material - plunk, finished - Panel 'In
> Production', workcenters - cutting worker, cutting machine,
>
Operation1 Cutting, raw material-plunk, finished Cutted plunk, workcenter
cutting machine - worker or workers HRs

> Operation 2 Drilling, raw materials - Panel 'In Production', finished -
> Panel 'In Production', workcenters - drilling worker, drilling machine,
>
Operation1 Cutting, raw material- cutted plunk, finished drilled cutted
plunk, workcenter drilling machine - worker or workers on drilling machine
HRs

> Operation 3 Painting, raw materials - Paint, Panel 'In Production',
> finished - Panel 'In Production', workcenter - painter, painting machine,
>
Operation3: material: dilled cutted plunk , finished drilled cutted painted
plunk.

> Operation 4 Assembling, raw materials - screws, finished - Panel,
> workcenter - assembly worker, screwdriver machine.
>
> Operation 4 finished --> PANEL

> You see that already after first operation we have product "Panel" b...

Read more...

Changed in openobject-addons:
assignee: Xavier (Open ERP) (xmo) → rpa (Open ERP) (rpa-openerp)
Changed in openobject-addons:
status: Confirmed → In Progress
Changed in openobject-addons:
status: In Progress → Fix Released
Changed in openobject-addons:
status: Fix Released → In Progress
Changed in openobject-addons:
assignee: rpa (Open ERP) (rpa-openerp) → nobody
Changed in openobject-addons:
status: In Progress → Fix Released
Revision history for this message
Carlos Liebana (carlos-liebana) wrote :

Fix released....

Where?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.