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

encoding orders

  • Thread starter Thread starter TECNOMODEL
  • Start date Start date

TECNOMODEL

Guest
I'm trying to build a system to code my work.

These are external collaborations with various companies and different types of work, from 3d modeling, to the design of plastic molds, to the design of various mechanical equipment.

any suggestions on how to set it up?
 
I'm trying to build a system to code my work.

These are external collaborations with various companies and different types of work, from 3d modeling, to the design of plastic molds, to the design of various mechanical equipment.

any suggestions on how to set it up?
Make a folder for each customer, and then in there use their own encoding.
 
I had thought about it, but I have some perplexity on this method.
For example: I have a dche customer works so, we say so, artisan. He has a sequential numerical code and so far no problem. the problem, in my opinion, is that it does not have a system that allows to follow the revisions or modifications of a project.
In my part of work I would like this to be present.
another example: I have a customer for which I design a equipment, he makes a product and has its own encoding, but does not preview a coding for the equipment. or has a code that defines all the equipment, I should also codify the various groups, details etc. that make up the equipment.

for now I thought of something like this:

xxxx- code in letters defining the customer
16-year
001-committee
01- revision index

My archive would mirror this pattern, then I should think of a code for the details of groups, assemblies etc.

What do you think?
 
hi technomodel, for years I have worked like this and normally we've always been there. drawings to customer bring this word



where
- "c" means that this is a customer's job.
- "xxx" is the client id: on a excel sheet you can list customers (if you don't need 3 digits you do 4 or 5 "beato te")
- "yyy" is the client's id: for example "01" can be the first order of that customer"
- "z" is the identifier of the single group (I use letters a,b,c...) that goes to design/modify/ integrate
- "####" is the numerical id of the single design

I must say that in 10 years of use I cannot complain so much.

greetings
 
I want to see if you work with solidworks and codify how you like... what do you give to the customer? a code that isn't yours?
Do you really want to have versions and revisions? use pdm.
divide for customers and then for year and then by order and thread the encoded jobs as they want. for all exta coding you can manage additional letters or numbers in accordance with the customer.

Unless customers only want drawings and no matter what they call it.... well the method they recommended before my post.
 
I thought about it.




xxxx- code in letters defining the customer
16-year
001-committee
01- revision index

?
code typically defines the customer
the designer proposes the name of the particular
revision index
r 01--
Thank you very much
 
code typically defines the customer
the designer proposes the name of the particular
revision index
r 01--
Thank you very much
Many companies impose mandatory coding without revision even to external technical offices, so many times there is the encoding of the customer and nothing else. think that sometimes there are all the configuration files of the customer and also the name of the rescue unit can become what is set.
 

Forum statistics

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

Members online

No members online now.
Back
Top