T
Claes,
Most of my clients have a very straighforward design process, so we use a basic design plan form that records all of the inputs, outputs, reviews and so on. I also have some that do the full project management Gantt charting and so on. It all depends on the product being designed.
Where I would resist including design is the once a year type deal where someone drops by your welding shop and says I need a hook to pick up this part with a crane. Welder fabs a hook, they pick up the part to test it, it works and customer leaves with his hook in an hour. Technically this is design with inputs (pick this up), outputs (here is your hook), review, veriifcation and validation (picked it up, did not break). The missing link is documentation. I've seen this type design in a lot of small shops. I don't see much value in adding a procedure and documentation for it if it only happens very infrequently.
Tom
Most of my clients have a very straighforward design process, so we use a basic design plan form that records all of the inputs, outputs, reviews and so on. I also have some that do the full project management Gantt charting and so on. It all depends on the product being designed.
Where I would resist including design is the once a year type deal where someone drops by your welding shop and says I need a hook to pick up this part with a crane. Welder fabs a hook, they pick up the part to test it, it works and customer leaves with his hook in an hour. Technically this is design with inputs (pick this up), outputs (here is your hook), review, veriifcation and validation (picked it up, did not break). The missing link is documentation. I've seen this type design in a lot of small shops. I don't see much value in adding a procedure and documentation for it if it only happens very infrequently.
Tom