tips

[ansyolitico]

hi I needed to ask for suggestions

Finally they bought the pdm, windchill for accuracy, and the technician let us reflect on how to set some points

-what to write in the article tabs, we put internal code, revision, denomination, rough size, group, designer, material, treatment, weight

- how to manage group coding

-States: obsolete, in design,

- how to manage products

 

[Kaji]

to indicate only the group perhaps it is little, I think it should also indicate the machine and for some also the subgroup and then to exploit these fields when you do the research in the pdm, moreover it could be useful to have in the cartiglio a field that reports the commission and also one that can identify the particular in stock if it is stocked (especially for semi-finished and wear parts).

As far as coding is concerned, I think that the so-called "speech codification" is a remnant of pre-pdm times, but I think that a letter of the code that can identify immediately if the design corresponds to a pre-finished, welded, assembled, commercial etc. is useful.
to manage the state of advance design from the pdm according to me is deleterious, at the end when a project is not mounted and finished every time you change a particular you are to have to submit to the bureaucracy of the revisions etc that I think it is better to reserve to the changes after the first installation.

Finally the product management did not understand what you mean and how to optimize the pdm for it.

 

[ansyolitico]

paradoxically they are addressing us on a totally opposite path

no subgroups, no car, no amount of orders because it does all the pdm

in addition we have a huge management problem, working on custom machines and with various accessories we should make a thousand versions of each group since it varies some particular

the number of comessas and belonging to the machine would not make much sense since many pieces and groups are in common to many machines

in theory each customer should have its own dedicated 3d model

even the rough and the worked we do not know how to handle it, my idea was to have two distinct pieces not shared, but it is rather fucked up even so

at least so we were advised

As I have no experience on these things, and the company is young and it's starting to grow, I'd like to set things up that in a future I don't mess with life.

with product management I mean management should be set with a single root and under all machines or machines is a root to which libraries are associated?