Smoke, Mirrors, Creo, Ninjas: All good things

Published 17 June 2011

Posted by Al Dean

Article tagged with: autodesk, ptc, proengineer, spaceclaim, synchronous technology, cocreate, creo, direct modelling, fusion, parametric modelling

Creo Direct - all modelling, no rules

Vegas. Never the best place for sitting down and writing something that both makes sense and is valuable for anything other than a cursory wave of the “Look, look, I’m here” flag at a software vendor event. But Vegas it was this week for PTC’s PlanetPTC Live.

At the event we saw the seemingly revitalised executive board hop up on stage, talk about their wive’s sketchy Mercedes, how the development team have enjoyed their work over the last few years and how PTC is going to grab market share back from its arch rivals.

This year’s user conference was different to those I’ve attended before. First off, the reins had shifted from the PTC/User organisation to PTC corporate. As a result, you got a lot more product update and strategy information and less “what users are doing with it” type presentations. And frankly, that’s been a good thing. These are interesting times for PTC and with a new version of Windchill 10 out, Creo replacing the Pro/Engineer and CoCreate brands, the company had just to tell. And tell they did.

Creo Parametric - All the Pro/E fun, but without the menu mapper - well, OK, in one area. And there’s a prize for whoever finds it first

PTC has been making a huge amount of noise about the roadmap for the future of its design tools. The announcement of Creo, which sees, in short, Pro/Engineer and CoCreate’s technologies merge into a single platform. Alongside this merging move, Creo also represents a sea change in how PTC are delivering its design and engineering solutions to market. Gone are the Pro/Engineer extension-tastic, monolithic systems. In their place, we’ve been promised a set of tools that are much more focussed on a process, workflow or task. PlanetPTC Live was the first time these have been shown off in anger and the first time I got to sit down and have a look at how things are working out. So here are my thoughts.

Creo & the modelling fandango

At present, PTC has two code streams for modelling technology. The history-based (and yes, parametric) technology from Pro/Engineer. We all know Pro/Engineer. It’s powerful, incredibly so, but it could be considered somewhat complex - as are all history-based and largely parametric modelling systems. That complexity is a fundamental part of their power. Building an intelligent 3D model that can adapt itself to design change is always going to be a complex thing. Alongside this, the company acquired CoCreate and its direct modelling focussed system.

What Creo does is introduce a new platform that allows the user to take advantages of both methods of working - but having sat down and worked through it with some of the team, it’s a different take than many others have attempted and worth breaking down into its constituent parts and exploring how it works.

Deliverables

In terms of product development focussed deliverables for the Creo 1.0 release, there are essentially two flavours. Creo Parametric is the usual all singing all dancing parametrically led and history-based modelling system. There’s all the tools you’d expect from Pro/E and more. Looking Creo Parametric, the UI has been redeveloped, seems much more consistent than the Wildfire initiative and there have been some fundamental updates that we’ll cover at a later date in more depth.

Alongside this, there’s also Creo Direct. This is where the complexity is stripped back, a direct interaction method is used and anyone who’s used the likes of IronCAD, SpaceClaim or of course, CoCreate, will know the score. Drag, drop, rotate, push, pull.. These things are key.

Common data model

During the last few months’ we’ve seen numerous videos of how the two systems will interoperate, using a common data platform. How you can take your parametric, history heavy model, open it in Creo Direct, make your changes and when that’s opened back up in Creo Parametric - Hey presto, there’s your model, updated and ready to go. What you also might have seen is that there are additions to the history tree that define what the user did in the direct modelling environment. That’s the one key reason that I headed out to Vegas. To find out how that works. And from what I learned, it boils down to this.

At its very core, Creo is still a history and feature based modelling system - whether you’re using the Creo Parametric or the Creo Direct app. What PTC has done is an excellent job of hiding the fact away from the user of the Creo Direct app. That’s the one fundamental thing to realise. Creo Direct looks, feels and works like a direct modelling system. All of the user experience flags are there. Grabbing faces, deleting data, re-applicable of rounds, maintaining of geometric relationships where possible. It looks and feels like CoCreate does, like any of the other systems do. But underneath the hood, its storing a history of every edit you make, every feature you create. You just don’t see it.

That’s the genius of Creo right there. That you just don’t see it.

Consider who direct modelling tools are aimed at. It’s often quoted that the prime target for direct modelling is the casual user, the user that may receive data from another source, have to make changes (whether that’s for simulation, for manufacturing or for another downstream process). It might also be those that don’t need the overhead of a big CAD system. They just want to sketch out an idea in 3D. It might also be that they don’t want to open up a heavy feature-based model just to make a quick edit. This is where Creo Direct is aimed. The fact that under the hood, it’s recording your operations but you never see them doesn’t really matter. Because the user that’s going to jump all over it doesn’t care either.

They. Just. Want. It. To. Work.

If, for example, a CoCreate user jumps onto Creo Direct, I’m sure they’ll feel at home once they’ve remapped to the new UI. Yes, there’s some work still to be done to bring parity between Creo Direct and CoCreate as it stands (mostly in the areas of assembly-based modelling), but it’s close already. And again, CoCreate users won’t particularly care whats going on under the hood. The fact that there’s a history of operations being recorded won’t effect them at all. Because it never has.

So when is it useful?

The benefit of that interoperation between Creo Direct and Parametric is when the same data passes back and forth between the two. The simple fact that you can give a parametric model to your direct modelling users, they can edit it using their tools of choice, but you get back a valid model, with their edits viewable to a pretty granular level, is incredibly powerful. There’s no “track changes” functionality at present, but I’m told this is coming in the next revision or two.

So… Smoke and Mirrors?

That’s the reason for the Smoke and Mirrors headline. It’s standard practice to use the term as a negative, to imply something untoward is happening. In this instance, no, it’s not. Not at all. The fact that PTC has developed two very different modelling experiences but has worked out how to let them inter-operate in a seemingly seamless manner, is a very good thing.

Many software vendors in this space are chasing the history/non-history/parametric/direct integration thing. Autodesk has the Fusion initiative which is working its way out. Siemens has Synchronous Technology. SpaceClaim is doing its direct modelling thing. What the best approach is and which will prove the best isn’t really within my purview - certainly not at this, still early, stage in the game.

What I can say is that the questions I went out to Vegas with have been answered very satisfactorily. Creo Parametric and Creo Direct work together because they’re essentially providing different user experiences based on the same core working methodology. Yes, the user experience differs, but with that same engine underneath, you should get robust results. I was curious whether making changes on a model built with parametrics using Creo Direct would break those parameters. The answer is no. it won’t. Creo Direct simply appends the direct edits you make onto the end of the history tree.

Someone at the event brought up the fact that I referred to the last release of Pro/Engineer as Godzilla with a jetpack and of course, wanted to know what the updated analogy would be. Frankly, creative thinking is something that’s difficult in the recycled, over oxygenated air, so I came up with “38 ninjas on crack.” On reflection, that’s about right. Creo looks clean and works in a deadly efficient manner.

Though I’m still not entirely sure where the crack comes into the grand scheme of things. But then I’d not slept in 48 hours. It was Vegas after all. Be back shortly with more thoughts particularly on the ancillary apps that surround the Creo modelling tools (if you want a good overview, Josh has done an excellent job) once the washing machine is on, the greenhouse has been watered and my sleep patterns have returned to normal. 

Comments:

My question still is: how does the round trip work? We get asked this all the time. When direct modeling, it is very common to chop up a model into bits, clean the bits, move the bits around, and combine the bits back together. The key to a direct modeler is making that process exceptionally fast, which is why we optimized the SpaceClaim UI around the Pull, Move, Fill, and Combine tools. That is the heart of direct modeling. If every little operation adds a feature, the model is bound to be choked by lots of little tweak features. Except in snazzy demos, no one ever moves a feature in one shot. There's lots of wiggling around, even if you're not doing a what-if study. It sounds like And when you bring the part back in to the history-based mode, how do you reconcile the changes? Don't you still have to remodel the original part, as the hack-and-stack features are useless? And how do you do this to the original design? When you roll back to see the features whose design intent needs changing, how do you still see the subsequent, now suppressed, hack-and-stack features? So why would any company choose this approach when they could use the best tools for the job, which are probably the industry-appropriate feature modeler and SpaceClaim? If one were looking at a new CAD setup, would any reasonable engineer choose a feature-based approach for direct modeling? PTC is not the only vendor who is betting the managers who spent their credibility enforcing a single CAD policy will be more likely to stomach a single-vendor approach than introduce a third part tool, even if that means not equipping engineers with the best possible tools. I would challenge anyone looking at Creo or any other direct modeler to also take a look at SpaceClaim. I think you’ll find that we’re the best tool for the job. -Blake (A SpaceClaim employee.)

Posted by Blake Courter on 21 June 2011 at 04:12 PM

Hi Blake... Good questions. Thanks for asking. First, Creo supports a lot of Direct Modeling scenarios. You mentioned the scenario where you want to break the model up into bits, and then do lots of exploration and iteration on those bits, and then bring them back together. The Creo Direct Modeling App supports that scenario just as well as SpaceClaim and every other Direct Modeler out there… but with a ton more to offer. If you use Creo Direct Modeling in this way, and then bring that model up in the Creo Parametric App, there will be features representing all of the changes you made – and if you made hundreds of changes, there will be hundreds of features. Now, you can retain those features, or, if you prefer a dumb, chunk o’geometry (which, we all know is the ONLY option with data that has been edited in every other Direct Modeler), guess what. Creo can do that too. You can easily collapse all of those features, forget them all, and just keep the resulting geometry. Here’s the important point, though… Creo gives the user a choice. If you want all of those features, they are there for you, but there is no requirement to do so. We can make the models edited in Creo Direct just as “unintelligent” as those that come from SpaceClaim, if that’s what you want. BUT, what if that’s not what you want? What if you don’t want your data destroyed? What if you don’t want to lose all of the intelligence that was originally in the model? Again, for some scenarios, such as early concepting when you are starting either from scratch or an existing design, and exploring lots of ideas, you may want simply the geometry as a starting point for detailed design. But what about the scenarios when you are starting with a fully defined, parametric model? Maybe you want to make some changes to the model that the original design intent did not anticipate. Or, maybe you are a tooling engineer or an analyst who wants to simplify or propose some alternatives to an existing design. What happens when you use SpaceClaim or any other Direct Modeler to do this? You can do it, but in doing so you are forced to throw away all of the intelligence that was originally built into the model. Here is where the power of Creo shines. Creo’s Direct Modeling tools allow you to make all of the changes that you want, with no regard for the original design intent or constraints, but (here’s the best part… ready?) those changes are clearly presented to the original designer or engineer when the model is opened in the Parametric Modeling App. Those changes can be reviewed, accepted or rejected, as is appropriate. So, in essence, Creo is providing all of the flexibility that typical Direct Modelers provides, but with a healthy respect for the fact that 96% of 3D modeling today employs a parametric approach. And, only Creo provides a pure Direct Modeling approach for the casual users, as well as access to those capabilities for Parametric users, and never destroys the data. So, I must ask, why would anybody choose a dead-end, data destroying Direct Modeler like SpaceClaim, when they can get all of the flexibility, and intelligence with Creo? I’m pretty sure that anybody who compares the two systems will chose the flexibility offered by the Creo approach. Creo is like an iPod that works with and iPhone that works with an iPad that works with a Mac, whereas SpaceClaim is like a Zune. ~ Mike (A PTC employee.)

Posted by Mike Campbell on 25 June 2011 at 03:43 PM

Blake and particularly Mike. Marquis of Queensbury rules apply boys - Keep it above the belt, keep it clean and play fair. Oh and the Marquis of DEVELOP3D adds an additional rule "Let's keep the mud slinging, name calling to a minimum eh".. Otherwise you can take it in the car park. Al Dean (The man with the big red Delete Comment button) PS: Mike. That's a shit analogy. Ever tried updating a document from a mac to an ipad? Its a pain in the bollocks.

Posted by Al Dean on 26 June 2011 at 10:50 AM

Leave a comment

Enter the word you see below: