CREO - First Impression?

[SW]

PTC swipes aside, at least they seam to be trying to innovate, and I for one, can't say that's a bad thing. This Anymode Modelling demo showing the ability to interpret direct features in a parametric model is certainly impressive if it can be delivered.

Sam

 

[mgnt8]

This looks along the lines of their Feature Recognition Tool for imported data. You wonder how bullet proof they can make it.


I'm notsaying I didn't expect great innovations. It's just that they hype machine is almost unbearable.

 

[gelanz]

As I see it, large assembly management
is considered to be one of the "holy grails" of
Pro/ENGINEER.

 

[Freecat]

Great points Gelanz,


I suppose I should rephrase and state that Large Assembly Management "used to be" one of the holy grails of Pro/ENGINEER...

As I'm sure you may recall, it wasn't all that long ago that large assemblies and the word Solidworks were not to be used in the same sentence.Sounds like all ofthat is rapidlychanging.


I have limited experiencemanaging largeassemblies as my assembliesrarely reach 1000 components. No wheres close tothe overhead you are having to deal with.


Can you elaborate on how large assembly mode works inCoCreate? We're still on 16, with plans to roll out17 in the next month or so.


It is sad to see Pro loose so much ground in an area that used to be one of their majorstrengths.


I have always thought that ifPTC could just make things right by fixing the bugs and interface problems people complain to them about theycould add significant valuetouse their products. Hopefully Creo is the first step in this process for them.

 

[gelanz]

I received an email from PTC first week in October that
showed CoCreate working on a 40,000 part assembly with
ease. I emailed PTC and told them you realize you cannot do
this size assembly in Wildfire, I would send you the link
but they took the link down.

 

[Jacoolo]

I think all this noise about the target point of Creao at all, was lunched to early.

I am following Deelip Menzes quite long. His last post reveal a little bit more about how PTC consider whole Creo thing. I find it really worth to read

http://www.deelip.com/?p=5068

 

[Mindripper]

The one lasting impression I am getting from the 'Creo' announcement is that it is largely a bunch of hype at this point. It would seem that 'Project Lightning' and Creo are an attempt to pump up the stock price of PTC. I'm waiting for some meat on the bone: it would appear that's at least six months away. But even then, it appears that Creois justanother attempt by PTC Marketing to draw more bloodfrom their hapless customers, with little real value in the 'enhancements'.

 

[joebarnes]

Premature Launch!
Historically when PTC's vision is revealed, it is about 3-5+ years ahead of reality.

Vision (2005)"Pro/INTRALINK 8.0 is the full replacement of Pro/INTRALINK 3.4"

Reality (2010) Pro/INTRALINK 9.1 M050 is the first viable replacement for Pro/INTRALINK 3.4 with out losing functionality. only usability. Maybe Pro/I 10.0 will solve the usability.

(~2001) "Wildfirization to revolutionize the usability of Pro/E" (claims for 80% of Core functionality complete by WF3) Most of Pro/E functionality must not be considrered Core.

(2010) WF5 not yet complete and a botched amateur attempt at ribonizing Pro/DETAIL. Our user would of been ok with it if it had included contextual tabs and mini toolbars.

When we first evaluated 3D modeling systems, PTC was the only vendor that refused to give us any pricing up front. They wanted us to be amazed with the product before we were turned off by the price. fortunately we didn't buy Pro/E until after the huge price drop of 1998 and a 50% discount off that.

I just don't believe PTC is adding to many "New" seats these days. There main souce of revenue for the CAD side of things is maintenance from existing customers. creo is probably a way to optimize that revenue stream.

I hope not!

Joe

 

[mgnt8]

Premature Launch!
Historically when PTC's vision is revealed, it is about 3-5+ years ahead of reality.

Maybe so, but a notable exception was the progression from release 20 to 2000i. The intent manager was an immediate leap forward.

 

[dr_gallup]

I thought that early implementation of the intent manager was terrible. We did not start using it until WF2. But I intentionally stay away from any new PTC release. It's never worth the heartache.

 

[mgnt8]

Well I thought it was a huge stepin the evolutinary chain akin tothe apes cracking skulls, but I didn't have to worry back then about multiple installations or training users. I guess its a whole other ballgameon anenterprise scale.


I haven't had time to look at that entire reveal video, but I just noticed on PTC's customer support call logger there's an entry for Subdivison Modeling in the Module menu. Will Creo have sub-d's?

 

[zpaolo]

I haven't had time to look at that entire reveal video, but I just noticed on PTC's customer support call logger there's an entry for Subdivison Modeling in the Module menu. Will Creo have sub-d's?

Yes it will. I'm really curious to see how it will be implemented. I've worked a lot with SubDs in CGI packages like Lightwave, but I don't know how it will blend with a CAD product, just a tool for quick shape modeling? My experience with SubDs is they are excellent for organical non-precise design, but a nightmare if you have to change something afterwards

Paolo

 

[Jacoolo]

first thing which seems to be most challenging is necessary update of incoming refreshed UI. So long, I haven`t noticed significant changes in dashboard interface embeded in tools.

That is good, and make possible to extand general feeling of working with Pro/E stuff.

What I am personaly most interested in is time which has to pass to evaluate and validate real benefit of switching to Creo stuff for who had installed WF 5.0.

I am not using WF 5.0 to my main job, but playing with it from time to time instead, and found it really solid. To me it looks like WF 5 was launched as introduction to Creo thing, but all who stay with WF 4.0 so far, have real problem about next step to take - WF 5.0 ot wait until stable Creo release.

 

[zpaolo]

To me it looks like WF 5 was launched as introduction to Creo thing, but all who stay with WF 4.0 so far, have real problem about next step to take - WF 5.0 ot wait until stable Creo release.

Interface wise the main difference between WF5 and Creo will probably be the widespread adoption of the ribbon interface. I want to be optimistic here: in WF5 the ribbon was ugly, modal and bad implemented, and it looked like it was a custom implementation from PTC, while the interface of Creo really looks and feels more like the ribbon found in Office 2010. This sounds good to me because the ribbon in Office 10 is much better than former implementations, but I don't know how it will be ported to Solaris...

Paolo

 

[dr_gallup]

To me it looks like WF 5 was launched as introduction to Creo thing, but all who stay with WF 4.0 so far, have real problem about next step to take - WF 5.0 ot wait until stable Creo release.

Interface wise the main difference between WF5 and Creo will probably be the widespread adoption of the ribbon interface. I want to be optimistic here: in WF5 the ribbon was ugly, modal and bad implemented, and it looked like it was a custom implementation from PTC, while the interface of Creo really looks and feels more like the ribbon found in Office 2010. This sounds good to me because the ribbon in Office 10 is much better than former implementations, but I don't know how it will be ported to Solaris...

Paolo

It won't be ported to Solaris. PTC is giving up multi-platform support. Much as I feel windoze is a lowest common denominator OS, it totally dominates the desktop these days, even in high end Engineering. So multi-platform support was definitely holding PTC back in their user interface implementation. So now they will be all MS all the time, just like everybody else.

 

[Mindripper]

No more Unix-based version of Pro/E? Gosh, that only took a decade or more for PTC to figure out. So I guess some users will finally have to dump their Sparcstations. But the question is: will it finally become a fully integrated Windows product, or (even better yet) a Certified Windows Application?

 

[dr_gallup]

A decade ago you could not do large models in windoze as it had no 64 bit OS or processors.

Who cares if Pro/E is downgraded to windoze specs? That has absolutely nothing to do with being a useful engineering tool. Next you'll want to run it on your 4G dumb phone.

You drink too much Redmond cool aid.

 

[SW]

Mr Gallup, I find it hard to disagree. Pro/E is a little backwards, but what would I rather, a window that maximises properly or a robust top-down design toolset? The abysmal over-hyped and porley implemented marketting aside, if PTC deliver half of the promise with Creo, I'll be fairly happy.

Sam

 

[Mindripper]

A decade ago, we were surfing the web with 56k modems - and some of us still are.


Is there any more info to be offered here on Creo? I haven't seen much meat on the subject here or elsewhere: it seems to be largely a PR activity by PTC Sales at this point (no surprise).

 

[dgs]

... Is there any more info to be offered here on Creo? I haven't seen much meat on the subject here or elsewhere ...

I'd say you haven't been paying attention then, it's been discussed quite a bit. It is more than marketing speak, there is a fundamental shift that looks promising. Of course, the question is can PTC deliver on what it's promised. They've bet quite a bit (including the brand equity in Pro/E and CoCreate) on it, so I wouldn't bet against them.

The idea is one data set with many tools (apps) for many different kinds of users to access the same data. So, a manager may have a visualization app, a marketing guy a rendering app and so on.

So Pro/E becomes part of the larger Creo family of apps. Until Creo comes, PTC has renamed WF5