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

windchill or pro.file: which pdm/plm?

  • Thread starter Thread starter davito
  • Start date Start date

davito

Guest
Hello, everyone.
This is my first post in addition to the presentation, I write to ask you for advice/ opinion about windchills and pro.file.
I'll explain the situation quickly.
we are thinking about installing a pdm in u.t., and I say pdm because at the moment we only need a data manager. integration with the erp, in our case jde, is not said to be done. even if it is true that appetite is eating...
in u.t. we are 7 designers and we use wildfire 5. with the installation of the pdm/plm we will upgrade to creo.
three of us in the past used intralink 3.3, others did not use anything.
decided to see only two programs and no more than two. two were enough to confuse us even more: eek:.
to stay at home ptc, of course you are considering windchill.
as an alternative you opted for pro.file.
given for granted that both do what we need (management revisions, conflicts, research, etc.), we have identified these qualities and defects.
windchill.
- it is definitely compatible with wildfire/creo. will exist until there will be the cad of ptc. a single interlocutor cad/pdm.
- defects: it is more expensive (but not too much) than pro.file. seems more “invasive”, heavy and complex than pro.file
pro.file.
- it looks lighter, flexible and less invasive. is cheaper (but not too much)
- defects: is not a ptc product, will it always be aligned and compatible with the cad? I've heard problems with family tables

at the end, the qualities of one seem to be the faults of the other.
What can you tell me about it?
Thank you.
Hello, David.
 
Good morning.

Let's say that the real difference between pro.file and windchill first lies in the acronym pdm/plm.
one is a product data management, the other is a product lifecycle management.
apart from the predictions/ defects you mentioned there are many other things to consider, first of all the scalability to the other of the platform and the total interoperability between the programs of the suite that ptc offers.
the same windchill offers support with mcad or ecad of third parties it is clear that the matrices of compatibility are increasingly updated with the pro/creo native cad but I would not consider it such a determining factor in the choice.
you have rightly written that for now you would only want to install a pdm for data management ut, no erp integration and other interesting things, but in such a choice you can not fail to evaluate everything.
plm unlike pdm offers a number of extensions that in pdm you don't have, to really give you a smart advice I should understand what you are dealing with.
example:
- do you need to manage the electronic part and possibly software?
- document management and editing process?
-manage complex configurations?
- Besides the ebom, do you have requirements for the management of the mbom or sbom?
- project management and collaboration with external partners, suppliers?
-management of guarantees and spare parts?
- information on support and delivery services?
- Planning the service parts?
-Do you handle technical illustration information?
-management of the manufacturing process?
-cost management?
-management of tests and non-compliance?
-supplier management and components?
etc. .
windchill is definitely more extensive and complex, perhaps for this it turns out to be heavy at first, in fact it depends much what you want to implement.
between the other in February will exit pdmessentials that substantial is windchill "cut", as departure for technical office data management is more than enough, costs less and you can in the future upgradare towards windchill pdmlink, the only flaw is that you can not choose the database, (oracle or sql server).
pdm will turn only under sql.
I hope I've clarified your ideas a little more, even if we could stay here talking for a whole day.
If you give me some extra details I can definitely help you more.
greetings
 
thanks parametric_ozzy for your answer.
I apologize for not being connected before now.
I'll split my answer in three parts.

1- I am concerned that you have defined profile a pdm, because we have been proposed as a complete plm. By trusting me more than a salesman trying to do his job, that lets me think they didn't tell us everything. profile we were proposed as if it was a package that contains everything you need to be a complete plm, connection to jde included. Unfortunately none of us has ever used a plm and therefore we are not well able to understand what we need, we understand its potential but nothing more.
windchill instead was offered only with pdmlink, so I thought it was a pdm more than it is profile. which ptc packages would miss to make windchill a colmple plm?

2- As I told you above, we do not precisely understand what we will meet in the future. When I try to imagine what can happen to a drawing, I cannot go beyond the possibility of attaching documentation to it in different formats, documentation that can cover proposals of modifications, approvals, reports of the c.q., costs, etc., besides the possibility of exporting a distinct towards jde.
hooking me to your list:
- do you need to manage the electronic part and possibly software? No.
- document management and editing process? Yes.
-manage complex configurations? Yes.
- Besides the ebom, do you have requirements for the management of the mbom or sbom? :confused:
- project management and collaboration with external partners, suppliers? Yes.
-management of guarantees and spare parts? No.
- information on support and delivery services? No.
- Planning the service parts? No.
-Do you handle technical illustration information? future
-management of the manufacturing process? future
-cost management? future
-management of tests and non-compliance? Yes.
-supplier management and components? No.

3- talk to me a little more than pdm essential, it could be what you do for us:finger:

Thank you.
Hello, David.
 
trusting me more than a salesman trying to do his job, that lets me think they didn't tell us everything.
I am also a retailer but of the ptc suite.
If you still trust the same I can continue, otherwise I shut up and good in a corner.:smile:
greetings
 
1- I am concerned that you have defined profile a pdm, because we have been proposed as a complete plm. By trusting me more than a salesman trying to do his job, that lets me think they didn't tell us everything. profile we were proposed as if it was a package that contains everything you need to be a complete plm, connection to jde included. Unfortunately none of us has ever used a plm and therefore we are not well able to understand what we need, we understand its potential but nothing more.
windchill instead was offered only with pdmlink, so I thought it was a pdm more than it is profile. which ptc packages would miss to make windchill a colmple plm?
We assume that plm is a strategic approach to the management of information, processes and data as resources to support the life cycle of products and services, from its conception to its withdrawal.
I did not want to say that pro.file is not, but those features that it has within it are standard of a basic pdm, which concerns "only" the management of technical documentation and project, integration with erp systems does not delimit the functionality extended at enterprise level.
probably there has been "only" offered pdmlink because the needs can be entirely covered with this tool, integration with erp systems is never out of the box, despite there are appropriate connectors, usual however you prefer to interface with appropriate customizations that you do in the pre-installing business requirements.
2- As I told you above, we do not precisely understand what we will meet in the future. When I try to imagine what can happen to a drawing, I cannot go beyond the possibility of attaching documentation to it in different formats, documentation that can cover proposals of modifications, approvals, reports of the c.q., costs, etc., besides the possibility of exporting a distinct towards jde.
I understand and it is perfectly understandable, for this reason I strongly stress the importance of doing a more targeted analysis when planning to implement a system of this type, how do I help a customer if it does not give me full visibility of how he is currently managing his product data? How can I give you a value if you don't even know where your problems are?
I can show you the most fantastic things in this world, but if I don't center your pains and propose you a well targeted plan of sustainable growth you will never perceive the benefits, it is important a general acculturation of people and the various departments that contribute to the final result, otherwise you risk buying something destined only for the technical office at a cost however important and difficult to justify to the management, if instead this solution brings benefits and creates value to the entire company then
hooking me to your list:
- do you need to manage the electronic part and possibly software? No.
- document management and editing process? Yes.
-manage complex configurations? Yes.
- Besides the ebom, do you have requirements for the management of the mbom or sbom? :confused:
- project management and collaboration with external partners, suppliers? Yes.
-management of guarantees and spare parts? No.
- information on support and delivery services? No.
- Planning the service parts? No.
-Do you handle technical illustration information? future
-management of the manufacturing process? future
-cost management? future
-management of tests and non-compliance? Yes.
-supplier management and components? No.
I can't and I don't want to dwell in detail on all these points but I just need to see the future and in some points to understand that a basic pdm solution cannot go well, it always starts from them, but growth must be expected and therefore planned regardless of whether you do it in one or ten years, you have to consider everything.
3- talk to me a little more than pdm essential, it could be what you do for us:finger:
pdm is essential pdmlink in "cut" mode, typical technical office management with sql embedded server (you can't choose oracle) very easy to implement but clearly limited in configurations, with still future possibilities to upgrade to classical pdmlink, is a new product created for "undecided". :-) has the possibility to integrate in addition to pro/e creo data, also autocad,inventor and swx, without additional costs.

I hope I have been quite exhaustive, it is clear and clear that this type of comparisons is difficult to make them in a forum, they must be discussed deeply, otherwise there is the risk that a message is not quite consistent with your reality.

greetings
 
I apologize for the delay I answer, but only Friday night I could discuss your answers with colleagues who carry this project with me.
At the moment we can only thank you for the indications you gave us.
we will call our ptc reference and we will deepen with him the arguments you have highlighted, especially we will talk about pdm essential.
If it doesn't bother you, I'll keep you updated. may also affect other members of the forum.
Hello, David.
 
I apologize for the delay I answer, but only Friday night I could discuss your answers with colleagues who carry this project with me.
At the moment we can only thank you for the indications you gave us.
we will call our ptc reference and we will deepen with him the arguments you have highlighted, especially we will talk about pdm essential.
If it doesn't bother you, I'll keep you updated. may also affect other members of the forum.
Hello, David.
No problem for everything.
I hope I have given you more visibility, the best thing is how you wrote about it directly with those who follow you ptc side.
does not bother me to stay up to date on the contrary I am pleased.:smile:
greetings
 

Forum statistics

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

Members online

No members online now.
Back
Top