MadMango
Mechanical
- May 1, 2001
- 6,992
I’m not sure exactly where to post this, but think this is probably going to net me the more correct answers. I think this has been discussed before, but Search is down.
For those that have an ERP system without PDMworks, how do you maintain your SW models to match your ERP BOMs? Our general practice is to expire parts that are under change, assign effectively dates for the new revision of the part. Sometimes, a component (part or assembly) may be replaced with a new component.
BOMs in our ERP system are numbered by 10s. Meaning a 4 component BOM will have line items designated as 10, 20 30 40. Sometimes, folks in other departments want to add a new component, perhaps a plastic bag, perhaps a bundle of cable ties, sometimes an install instruction. Sometimes they add them as Item 50. That’s perfect, and it’s easy for our folks to update the SW model to add that item.
Sometimes though, folks add a component as Item 5, 15, 25, etc. That throws everything out of whack. Everyone has their well-discussed reasons for wanting to add a "half-number" as I call them. The greatest reason is as a visual indicator that the newly added component is associated with the other (15 is associated with 10). Let’s face it, if you work in a manufacturing plant, the guys in the shop builds to a BOM, they don’t build to a solid model.
Sometimes, components in a BOM are expired, and the position in the BOM is maintained for archival reasons. This may make a BOM look like 10, 40, 50, 90. We’ve been able to manage our models to insert a blank part or assembly file with the title EXPIRED. This acts as a placeholder in the SW BOM, and it matches our ERP BOM. Everyone is happy, except for the folks that get stuck having to modify a SW assembly with many expired files.
Looking for any suggestions/work arounds to streamline some of this mess, short of "getting a PDM package."
"Art without engineering is dreaming; Engineering without art is calculating."
Have you read faq731-376 to make the best use of Eng-Tips Forums?
For those that have an ERP system without PDMworks, how do you maintain your SW models to match your ERP BOMs? Our general practice is to expire parts that are under change, assign effectively dates for the new revision of the part. Sometimes, a component (part or assembly) may be replaced with a new component.
BOMs in our ERP system are numbered by 10s. Meaning a 4 component BOM will have line items designated as 10, 20 30 40. Sometimes, folks in other departments want to add a new component, perhaps a plastic bag, perhaps a bundle of cable ties, sometimes an install instruction. Sometimes they add them as Item 50. That’s perfect, and it’s easy for our folks to update the SW model to add that item.
Sometimes though, folks add a component as Item 5, 15, 25, etc. That throws everything out of whack. Everyone has their well-discussed reasons for wanting to add a "half-number" as I call them. The greatest reason is as a visual indicator that the newly added component is associated with the other (15 is associated with 10). Let’s face it, if you work in a manufacturing plant, the guys in the shop builds to a BOM, they don’t build to a solid model.
Sometimes, components in a BOM are expired, and the position in the BOM is maintained for archival reasons. This may make a BOM look like 10, 40, 50, 90. We’ve been able to manage our models to insert a blank part or assembly file with the title EXPIRED. This acts as a placeholder in the SW BOM, and it matches our ERP BOM. Everyone is happy, except for the folks that get stuck having to modify a SW assembly with many expired files.
Looking for any suggestions/work arounds to streamline some of this mess, short of "getting a PDM package."
"Art without engineering is dreaming; Engineering without art is calculating."
Have you read faq731-376 to make the best use of Eng-Tips Forums?
![[3eyes]](/data/assets/smilies/3eyes.gif "[3eyes] [3eyes]")