B
Hi All,
My 2nd post in about 3 years! The job shop I work at presently has shop drawings that are created so that information can be presented in a standardized format. We produce parts for a lot of customers that are all vary similar to each other (dimension, material and pattern variations). The customer drawings tend to have too much information on them and none of the critical information the shop needs.
The present drawings are created using Visio and become part of the traveler. As I move this company towards having an ERP system (which they do not have today), I'm realizing that all much of the information on the drawing could be tied to a database (e.g. linking the Visio drawing to records & fields in Access which appears to be easily acheivable).
Has anyone does this and does it create problems for controlling rev levels? We are a long ways from doing this but I have an opportunity to start collecting a lot of the information and would like to do so if it makes sense.
My thought on the rev level is that this could be a field that was incremented anytime a change was made to the record of the part number and we would then have a release process to ensure the shop was aware and any necessary "NPI" issues were address.
I'm mainly interested in hearing from anyone who has done something similar and what the successes/challenges have been. The main advantage to all of this would be having "single source" information, at least as used in-house.
Thanks!
BB
My 2nd post in about 3 years! The job shop I work at presently has shop drawings that are created so that information can be presented in a standardized format. We produce parts for a lot of customers that are all vary similar to each other (dimension, material and pattern variations). The customer drawings tend to have too much information on them and none of the critical information the shop needs.
The present drawings are created using Visio and become part of the traveler. As I move this company towards having an ERP system (which they do not have today), I'm realizing that all much of the information on the drawing could be tied to a database (e.g. linking the Visio drawing to records & fields in Access which appears to be easily acheivable).
Has anyone does this and does it create problems for controlling rev levels? We are a long ways from doing this but I have an opportunity to start collecting a lot of the information and would like to do so if it makes sense.
My thought on the rev level is that this could be a field that was incremented anytime a change was made to the record of the part number and we would then have a release process to ensure the shop was aware and any necessary "NPI" issues were address.
I'm mainly interested in hearing from anyone who has done something similar and what the successes/challenges have been. The main advantage to all of this would be having "single source" information, at least as used in-house.
Thanks!
BB