info su modeling

[nano71]

hello to all, my company tried to leave the modeling platform in 2015 for creo parametric and windchill, with disastrous results. we are at the beginning point, that is, we think of returning to use the dear old modeling. But my bosses are concerned that those who distribute parametric spread rumors that in a few years will no longer be supported (not updated, supported) by ptc...
who uses it continuously (just don't be distributors, hehehe) can give me some info about it?

thanks in advance. may be available to talk about it in pvt.

 

[Shaba]

blessed you, how much I miss modeling and especially me10
excuse the little ot

 

[cacciatorino]

the voices of abandonment have been there for 5-6 years, but I see that they regularly come out new versions: 20.0, 20.1, now there is 20.3. then the current versions are only to subscriptions, so the speech of the lack of support is not feasible.

I add that the current version works on windows 10, so I think that for several years we will be fine.

One thing they told me is that ptc is trying to force customers to migrate from model managers to windchill, I don't know how successful.

 

[cacciatorino]

because the passage to pro/e was disastrous? I think I can imagine it, but I'm curious to hear it from a user's voice.

 

[nano71]

the voices of abandonment have been there for 5-6 years, but I see that they regularly come out new versions: 20.0, 20.1, now there is 20.3. then the current versions are only to subscriptions, so the speech of the lack of support is not feasible.

I add that the current version works on windows 10, so I think that for several years we will be fine.

One thing they told me is that ptc is trying to force customers to migrate from model managers to windchill, I don't know how successful.

So... let's say that my company has an associate in a basket that uses 60 licenses, we have always used modeling and initially the choice was made to closed eyes (wrong) without trying to figure out what could be met. we still have modeling 16 today, with jclient "virtualized". . .
the thing that bothered me was that the first company that followed us did not say that the modeling still existed. They told me that there was no more and that one had to go on creo parametric (and windchill). We could not make a decision. ptc distributors are divided into two families. who comes from proes is now a fervent supporter of creo and windchill, who had modeling do not know what he did. I know cdm (our former distributor) and I know that they always distribute this modeling.

Unfortunately windchill is a powerful but absolutely generic pdm. so I'll let you imagine. I'm just saying that in the company even in the workshop they can't get used to using it and we keep using the old jclient. Unfortunately, I think it's too slender, especially for dynamic companies and they build custom machines like mine.
My boys from r&d blasphemy often. . .

 

[nano71]

because the passage to pro/e was disastrous? I think I can imagine it, but I'm curious to hear it from a user's voice.

the biggest problem is because for the 2d it is more convenient to remake the tables, at the time when you have to change them. bom tables and carts take data differently, so currently also manage modeling with windchill I don't see it easy.
3d files once converted (the procedure depends on the complexity of data imported from one system to another) have a problem. the point of origin of modeling is different and if you load big assemblies on creo, you find yourself with a huge stretch of origins that make the movement of the assieme become problematic.. .

 

[cacciatorino]

I understand, difficult to imagine two more different cads, despite what they say to the ptc.

 

[Kaji]

the biggest problem is because for the 2d it is more convenient to remake the tables, at the time when you have to change them. bom tables and carts take data differently, so currently also manage modeling with windchill I don't see it easy.

I never used windchill though being a pdm of the ptc it seems strange to me that "manage evil" the 3d of modeling, the main difference regarding jclient is that it is a windchill is of type pdm centric (i.e. the distinct law directly from the total saved to pdm) while jclient the law "directly" from the cad; probably it is made to measure for modeling, however it is also
I also think that windchill points a lot on the fact of being multicad, among other things I felt that with the combination creo windchill manage to load directly in 3d creo environment, models coming from different cads (only feel I haven't seen it do).
said this there are several companies that use more cad, in particular some use creo parametrics for standard production, exploiting the potential of parameterization, while creating elements direct (modeling) use it for customizations.