• This forum is the machine-generated translation of www.cad3d.it/forum1 - the Italian design community. Several terms are not translated correctly.

coding management.

  • Thread starter Thread starter giacomoerre
  • Start date Start date

giacomoerre

Guest
Good morning to all,

I hope I have chosen the correct category of the forum!

I would like, in the management of the company’s archive in which I work, to implement a system of coding and management that is definitive.

at the current state of things, the name of the part and together files is descriptive (support dx, double fulcrum lever,..) while the drawings, pdf, dxf are named in the following way: cod – description to make an example: 05061501a – support dx f.ø20.

In addition to a new encoding system there is the intention to implement a management system. therefore the new coding system should be thought with the use of a management (it accepts advice also on the latter).

I would like to hear how this aspect of the technical office is managed in your companies.

Thank you, Jacob.

ps. by mistake I entered the discussion in an incorrect section. How do I move?? Thank you.
 
no one who has experience in this context? or may at least help me move the discussion to a more appropriate section?

Thank you, Jacob.
 
ps. by mistake I entered the discussion in an incorrect section. How do I move?? Thank you.
Don't move her.
only moderators have this faculty
Good morning to all,

I hope I have chosen the correct category of the forum!

I would like, in the management of the company’s archive in which I work, to implement a system of coding and management that is definitive.

at the current state of things, the name of the part and together files is descriptive (support dx, double fulcrum lever,..) while the drawings, pdf, dxf are named in the following way: cod – description to make an example: 05061501a – support dx f.ø20.

In addition to a new encoding system there is the intention to implement a management system. therefore the new coding system should be thought with the use of a management (it accepts advice also on the latter).

I would like to hear how this aspect of the technical office is managed in your companies.

Thank you, Jacob.
Look... there are philosophies on philosophies behind encoding elements
In my humble opinion, the most effective is that of the progressive code.
the code is composed of an aseptic number. a table compares codes with descriptions. if you have a management, this is simplified because it allows you bidirectional research
 
Look... there are philosophies on philosophies behind encoding elements
In my humble opinion, the most effective is that of the progressive code.
the code is composed of an aseptic number. a table compares codes with descriptions. if you have a management, this is simplified because it allows you bidirectional research
quoto!

I link you to debate a while ago, where we talked about this.
take a look, but be careful not to confuse your ideas anymore! :redface:
 
very long speech, and never definitively solved! I can only agree with those who preceded me: Progressive code all life, it always defies speakers codes, which can make some sense for a product with many configurations but standardized.
with regard to construction drawings, I would suggest to keep the article code separate from the drawing code, to facilitate the management of revisions (where a new revision is for me totally interchangeable with the previous one, so as to be theoretically mixed with the old in stock). if the new "revision" is actually a change that compromises interchangeability with the previous (geometric or functional) makes sense to codify a new article.
Bye!
 
I recommend the management through pdm and plm with progressive alphanumeric coding.
inside the files there will be description properties and what else, while the pdm tells you where the price or the axieme is used.
but it is used if you do not have pdm.
then there are the traditionalists who insist on using the second with the pdm and thus complicates life and programming for automatism.
 
we tend to use "flat" codes for finished products that are in the catalog. more to help customers than we. then we tend to make the children's codes of those talking fathers speak, but we do not try to become fools. always does the management.
if we send in revision a code and is not totally interchangeable with the previous review we manage the remaining in stock. Once we're out, we're good. if managing the remains becomes too long or heavy we change code and the old revision remains alive attached to the old code.
 
I think the best system is the progressive code with the first number that represents the type of product.
example:
6145214 where the 6 is for the finished product
5001254 where 5 stands for commercials
4155454 where the 4 is for groups
3145545 where 3 stands for parts obtained from mechanical processing
 
in the encoding system, however, it is important not to let the customer understand what the products you trade and those you produce. I would try to make the speaking code only in relation to its functions and intrinsic properties, not relative to origin or its position in the distinct base.
 
Hello, everyone.
I read this old discussion.
did someone drop some pdf files for coding that is used in their company?
or do you have basic rules?
 
letters that identify the type of machine then three progressive digits that identify the machine number. zero number for parts and growing for assemblies. letter for the group and three figures for the progressive. all zero are the assemblies.

Everyone has his own conditions.

The ones I like are made by a salesman I used once.
20230609-001-a-0001-00
where the promo block is the start date of the project written to the American.
001 to climb are the machines that make up the plant.
a....b...c... groups.
0001...0002....the components.
for the assemblies
20230609-001-a-0001-01
20230609-001-a-0001-02
....
 

Forum statistics

Threads
44,997
Messages
339,767
Members
4
Latest member
ibt

Members online

No members online now.
Back
Top