LONDONDERRY
Mechanical
- Dec 20, 2005
- 124
Geetings:
Our company has worked with a case manufacture (similar to Pelican Cases) to develop a semi-custom case for our needs. Its a scenerio where the vendor has an off-the-shelf case and we asked them to tweek it. The case has a retractable handles, wheels, latches and protective bumpers, etc. Afterward, the vendor assigned a part number to the case job, and we assigned our internal company part number. The vendor has the documentation on the case which is hand notes, sketchs, some 2d prints, and placed all that in a folder and assgined a job number to it. I had to work with the vendor on this with on site visits
Afterwards, I created a 3d CAD model of the design, and 2d drawings , structured a BOM in Agile PLM of the items I mentioned above and loaded the drawings. I released the design and when supply chain (s/c) went to place the order with the vendor problems arose as such:
1. The case manufacture didn't mentioned the vendors they use for the case design assecs (wheel, latch, ect.)> Because I created a BOM in Agile with these parts called out, s/c was confused if we supply these parts or not and why no vendor is listed
2. The case manufacture was confused when s/c chain sent him a package of drawings I created. He assumed something changed and had to spend 1 week reviewing the notes in the folder to the 2d drawings, and then had to contact me to find out what changed.
So my question is what is the best method to document this? I was told we need to document the case design somehow, as part of an inspection process on our end and if the vendor goes out of business we have something. The problem is I went the tradition route of creating detail, assembly drawings and BOm and this casued a mess with other departments that didn't know the development history I ahd with the case manufacture. In addtion, not stay at their jobs for life, so i want to create a documentation package so when I leave there are no questions on how to build a case.
Some thoughts I had was to remove the Agile BOM and create a source control drawing and place the BOM on that. One other isses is the case design changes based on the contents we need to fit inside of it. So my question is what is the best method for documenting this type of design?
Regards
Frank
Our company has worked with a case manufacture (similar to Pelican Cases) to develop a semi-custom case for our needs. Its a scenerio where the vendor has an off-the-shelf case and we asked them to tweek it. The case has a retractable handles, wheels, latches and protective bumpers, etc. Afterward, the vendor assigned a part number to the case job, and we assigned our internal company part number. The vendor has the documentation on the case which is hand notes, sketchs, some 2d prints, and placed all that in a folder and assgined a job number to it. I had to work with the vendor on this with on site visits
Afterwards, I created a 3d CAD model of the design, and 2d drawings , structured a BOM in Agile PLM of the items I mentioned above and loaded the drawings. I released the design and when supply chain (s/c) went to place the order with the vendor problems arose as such:
1. The case manufacture didn't mentioned the vendors they use for the case design assecs (wheel, latch, ect.)> Because I created a BOM in Agile with these parts called out, s/c was confused if we supply these parts or not and why no vendor is listed
2. The case manufacture was confused when s/c chain sent him a package of drawings I created. He assumed something changed and had to spend 1 week reviewing the notes in the folder to the 2d drawings, and then had to contact me to find out what changed.
So my question is what is the best method to document this? I was told we need to document the case design somehow, as part of an inspection process on our end and if the vendor goes out of business we have something. The problem is I went the tradition route of creating detail, assembly drawings and BOm and this casued a mess with other departments that didn't know the development history I ahd with the case manufacture. In addtion, not stay at their jobs for life, so i want to create a documentation package so when I leave there are no questions on how to build a case.
Some thoughts I had was to remove the Agile BOM and create a source control drawing and place the BOM on that. One other isses is the case design changes based on the contents we need to fit inside of it. So my question is what is the best method for documenting this type of design?
Regards
Frank