Differences

This shows you the differences between two versions of the page.

--- consulting:the_consulting_technical_designer_and_manufacturing [2020/01/02 22:38] – [More succinctly: two don'ts] mithat
+++ consulting:the_consulting_technical_designer_and_manufacturing [2020/01/02 22:50] – [Two succinct don'ts] mithat
@@ Line 9: / Line 9: @@
 ===== Separation of concerns =====
-The manufacturer owns manufacturing.
+The designer takes responsibility for their design, and the manufacturer owns manufacturing. This means the manufacturer takes responsibility for managing the documents they need for manufacturing.
-The designer takes responsibility for their design, and the manufacturer takes responsibility for manufacturing. This means the manufacturer needs to take responsibility for managing the documents needed for manufacturing.
+Don't expect the design engineer to hang onto production files that are no longer relevant from a design perspective once they have conveyed them to you. Don't expect them to be able to regenerate the production files either. Assuming they have held on to the original source files, the software they used may have gone through several updates by the time you make the request, so there's no guarantee regarding how the new files will be regenerated. And since there is no guarantee regarding how the new files will be regenerated, they will need to be verified through another round of testing proto builds, even if nothing actually (or was supposed to have) changed.
-Don't expect the design engineer to hang onto files that are no longer relevant from a design perspective (i.e., the production files you are using) once they have conveyed them to you. Don't expect them to be able to regenerate the production files either. Assuming they have held on to the original source files, the software they used may have gone through several updates by the time you make the request, so there's no guarantee regarding how the new files will be regenerated. And since there is no guarantee regarding how the new files will be regenerated, they will need to be verified through another round of testing proto builds, even if nothing actually (or was supposed to have) changed.
 ===== Fixed versus live data =====
@@ Line 22: / Line 20: @@
 ===== Two succinct don'ts =====
+The above can be distilled down to two succinct don'ts:
 Don't assume that the consulting design engineer will maintain a history of manufacturing files for you. If maintaining a history of manufacturing files is something you expect your consultant to do, expect to have to pay for the service. Reliable, traceable archiving isn't free, easy, or fun. It's work, and not the sort the design engineer wants to do.
-Don't ask the design engineer to just regenerate the production documents they sent you before because you either lost them documents or don't want to dig them up. Regenerating files that have been previously vetted requires vetting them all over again. In most cases this means a full round of testing and prototype building. A good  designer will //not// release to manufacturing anything that has not been properly vetted. It's their ass on the line if something somehow got messed up in the regeneration.
+Don't ask the design engineer to just regenerate the production documents they sent you before because you either lost them or don't want to dig them up. Regenerating files that have been previously vetted requires vetting them all over again. In most cases this means a full round of testing and prototype building. A good  designer will //not// release to manufacturing anything that has not been properly vetted. It's their ass on the line if something somehow gets messed up in the regeneration.