pdm per inventor

[Catafratto]

I tried but I didn't find a specific 3ad here on inventor, so I'll open a new one.

which pdm used with inventor? (who uses it, of course! )
What do you recommend? Why?
What advantages does the pdm have you feel the most significant?

thanks in advance of the info:mixed: and good work to all!

 

[Catafratto]

no one uses it on inventor? in the forum plm/pdf/edm I found many interesting comments, but many of these pdms seem to me linked to the only solidworks. suvvia, some indication :biggrin:: We are considering taking one, but having never seen it at work I don't really know how to evaluate it and, in fact, I don't even know what the one proposed by my retailer is interfacing with inventor. 3 designers, small company with very varied production.
Thank you!
:mixed:

 

[re_solidworks]

no one uses it on inventor? in the forum plm/pdf/edm I found many interesting comments, but many of these pdms seem to me linked to the only solidworks. suvvia, some indication :biggrin:: We are considering taking one, but having never seen it at work I don't really know how to evaluate it and, in fact, I don't even know what the one proposed by my retailer is interfacing with inventor. 3 designers, small company with very varied production.
Thank you!
:mixed:

the inventor's pdm is vault, there is a pro version that I do not know. if you may be interested in ready2works is also coming out for inventor, it is already ready, at this moment it is in testing phase.
a demo doesn't cost much, I suggest you see it. then there are pdms like windchill or teamcenter that support practically all cad, but it is 2 different landings.
to decide "on which world" to face you must first evaluate how you want to manage the workflow, if you have to manage the life cycle of the product (in case you need a plm and not a pdm and ready is not good) and the budget available.
how many do you use pdm? the speech is a little long and must be carefully evaluated.

Hi.

 

[Catafratto]

thanks to the answers, I read with interest your posts also in the specific forum pdm. at the technical office level we are in three, currently we codify with a progressive per customer the bulk of the elements/tables plus a bit of standard codes "parlanti" for what can be standardized (e.g. 032.850.01 tree (032) bar (850) recttore bonf. mvf49(01)). We somehow manage it but obviously find unstandard things to reuse them goes to the designer's memory, and the only connection with the shopping office is paper or at most a excel sheet. we are aware that we will probably have to change workflows, we must understand how and what will be the best direction. we have already seen the demo of a product but not knowing well what to expect from the pdm I followed what showed us the dealer without knowing how to ask the "right" questions for our situation. All right, you'll experience it!
Hi.

 

[re_solidworks]

thanks to the answers, I read with interest your posts also in the specific forum pdm. at the technical office level we are in three, currently we codify with a progressive per customer the bulk of the elements/tables plus a bit of standard codes "parlanti" for what can be standardized (e.g. 032.850.01 tree (032) bar (850) recttore bonf. mvf49(01)). We somehow manage it but obviously find unstandard things to reuse them goes to the designer's memory, and the only connection with the shopping office is paper or at most a excel sheet. we are aware that we will probably have to change workflows, we must understand how and what will be the best direction. we have already seen the demo of a product but not knowing well what to expect from the pdm I followed what showed us the dealer without knowing how to ask the "right" questions for our situation. All right, you'll experience it!
Hi.

the problem is that these choices you make often before you experience and almost never the counterpart is so correct to pull back if the product that represents is not suitable for your requests.
feeling + bells you will be warned by one of the flaws of the other, it is a little bit of experience investing only a little of your time.
so much to make an example consider ready a great product, although the management of revisions is not scrupulous as in pdmworks enterprise.
On the other hand, it has many other qualities that pdmworks enterprise does not have. You have to decide what must be there and what not, then between products to the same for your own needs, see what more one than the other.

 

[Alby189]

for your needs it could also be enough a simple basic distinction: to manage the item graphics (connect design code to description and an article code), find the details already designed, make implosions, etc. so doing a search by name will be simple to find and consult the drawings of the details. it would also benefit from the interface with purchases, suppliers, etc.
contrary to others I am opposed to plm if it is not used in a network of designers who work in many on a single project also divided into various establishments, for an office of three people I would not use it, but it is only my opinion, that I recognize to be counter-tendenza.

 

[Catafratto]

it is not so much to design better (in the end it is good also as we work), but not to go crazy after the project: the management of revisions (specifically, customer call two days before delivery) with a series of variants to be taken into account in the billing is one of the things that would really be convenient; or some standard machines that evolve over the years... I don't know if the pdm can, but I think (hope!) yes. I don't mind the idea of a little order. we are too accustomed to the special, more attention to reuse it really does us well. And then who makes it the distinct base? hope to automate that too!

 

[Yarin VooDoo]

Hi.
I soon found myself in the same situation and with the same doubts and problems to solve, in the end, at least in our case, the choice fell on vault that, in the base version, is included in the autodesk suites.
the idea is to make a period of setting to finish the workflow, then decide the upgrade to a more complete version of vault, but having already a database of the ready and settled technical office.

the beginning is quite impacting, especially if you had no specific organization before, but you take your hand quickly (maybe taking advantage of a few hours of training) and recover/research/reusing parts and assemblies becomes simple.

to consider that already in base vault you have the integration with part of ms office (word and excel) and, however inside you can manually store everything you need, tag it with useful data for research and grouping.
also the development of axiemi, es of a prototype or a new machine, becomes simple, you can model and save without care too much of the file names or iproperties, which you can change later in vault even in a massive way.

Obviously vault is also particularly voted for the shared work in reye, avoiding competing changes to the same item and centralizing the archive.

the only complicated step do vault is the installation that requires ms sql, we preferred to make it by a technician being the first time, but there is all the documentation to do it yourself.

 

[K79]

I follow with interest, some twists?

 

[carnemorta]

in my experience I had the opportunity to experience two different pdms.
the first in chronological order is called data&drawings, it is marketed by an Italian software house and manages all cad+office documents indexing the database of the components in a quite intuitive way. it manages well the question of the distinct base and presents many useful tools for the automation of the prints of tables/differents that are not to be underestimated. the company had also programmed an automatism that interfaced the pdm directly with the corporate management. On the other hand I found that putting our hands on to customize the proposed masks was rather difficult, not to say impossible.
then I got to use vault. functionalities are similar but the interface is definitely more intuitive and the possibilities to define the mapping of properties - create, add, connect - are much more accessible independently by the system administrator, while for the d&d you had to always pass from the assistance.
I suppose the first was cheaper than the second. the vault has from its advantage to be an autodesk product and this gives it an extra march regarding compatibility with other autodesk products.

 

[carnemorta]

an update - I have experienced another couple of products in the last three years.
document - quite flexible though little. Unfortunately in azinda here from me they have kept a rather dated version and have not updated it so I suppose my comment should be taken with due cautele - the last versions could be very different. I read for more on an email of "marketing" that implemented the morphological recognition of the components, interesting mooolto.
sap ectr - not wanting to update the document has opted to update the document system by changing software and choosing for the product of sap, which is our help erp. I am the technical key user and I feel like telling you that, from the technical office point of view, this is a product from which to stay away. has its pros from the perspective of integration with the erp but it is absolutely rigid, expensive and offers almost no implementation in the cad area
profile - other plm/pdm rated in the phase of product choice for document replacement. it was what convinced more theut but then the property went through. very convincing presentation, including visit to the company that uses it that has left an excellent impression. I can not give more accurate information not having used it effectively

 

[DrBarde]

Good morning. I join me more than anything to prevent who can, we have used for years vault without big problems, then with the switch to sap we then integrated know ectr. fortunately they are neither the technical key manager nor the IT manager (they are getting old early), but given the non-excessive size of the company I contact with both... and the only definition from a technical office that comes to me is: hell on earth. and all considering that we are 3/4 years of use if not more, still today with a lot of money invested and dedicated time, it is full of problems and slowing from the point of view of the technical project.

 

[MrCAD1]

in the company where we were before we migrated the entire database of designs from vault to d&d and sincerely we had found ourselves better.
in our case the need to create some adaptations to the software that autodesk did not grant us, while instead the software house that distributes d&d has created customizations to the software that has speeded us a lot of work.
I had to deal with both big and small brands in my career, we are careful not to be dazzled by the great name because it is not always synonymous with greater quality.

 

[Cupido]

does anyone use parallaksis under inventor? .. i ask for a friend