Hello
We have just set up PDM in our country.
I would like to have your feedback on your use because we do not know how to handle this case.
We have an assembly with several configurations.
We name the 2D file with the name of the 3D + the name of the configuration
For example, we have a roof with or without a chimney and 4 different colors possible.
In other words, 8 possible configurations.
What do you call these plans?
How do you manage changes?
Do you use various tools to create derivatives of the assembly without breaking the links?
I hope I'm clear enough:)
See you soon
Hello
Maybe you have a commercial code in place? Otherwise, why not put a codification?
One of the advantages of PDM is to manage codes and their life cycle (good PLM, but with a PDM you can go far).
In addition, with codification, we manage ERP transfers...
In short, in my opinion, codification is an important step; However, it is necessary to take a few hours of reflection because the more the number of products grows, the more the slightest modification will be substantial.
For your example, an example: 6-digit coding
TTAC00
TT roof, AC with chimney, 00 colour code
In a previous experiment, an incremental number comes out, regardless of the type of component (assembly, plan, trade, material, etc.), and the Description property is used to find a part. The part and plan filename is therefore an "incrementally" managed number.
Hello,
For me, a bastard example of a ref that means nothing
If we have as a possible ref:
ASM2000G7-990
ASM2000G6-550
ASM2000G5-550
ASM2000G5-540
etc...
It is necessary to determine a basis that characterizes the product ICI "ASM2000G"
My set will be called: ASM2000Gx-xxx
After which I either create a drawing by config which will be named correctly, or I create a generic plan or I make a table summarizing the article numbers with the configurations checked in the columns.
Both work, but it's best to make one plan if possible . (simpler index rise)
=> Easy in the case of objects present or not in an assembly, or color change
=> in the case of a dimensional change between configs it is already much more complicated unless you call for different articles each time, in which case you have to rework the table so that the article code concerned appears.
Not sure if I have made myself understood, do not hesitate to ask me for clarification:)
Ok that's what we thought we would set up
example:
R-xxxxxx-SC7016
R- (internal coding)
xxxxxx (counter number)
SC / AP Without/With Fireplace
7016 /... RAL
If the plan doesn't have a config,
"-default" suffix or modification via PDM
Only R-xxxxxx
In the end, one plan per config with a single 3D file
The index is carried only by the plan
Ease of indexing and maintenance in case of part/assembly modification
1 Like