Skip to main content
Jan 25, 2011 4:24 PM UTC

Versus

DirectModeling.pngDirect modeling is certainly one of terms that have been dominating the industry talk recently. Not that I would ever be able to jump into this discussion to provide fresh technical insights or technical comparisons, but I have been doing extensive reading and listening over the past few months.


Doing so, one thread here on PlanetPTC Community caught my attention as it has had a lot of comments and - to date - over 13,000 page views. It discusses if a user of parametric CAD would be capable and willing to change to a direct modeling tool.

While I think no offense was meant by starting this thread, it seems to me that it was perceived as a bit provocative by some readers. I also think some of the contributors have done a great job in bringing their points across, but I can still read something between the lines that I would like to comment on.


Let me dig into 3 aspects from this long (I mean, really long) thread and wrap them with my own thoughts…


  • Users across the board are very enthusiastic about “their” CAD system.

There are many different “types” of users out there – many of them having extensive expertise on one specific system, while others have used many different tools in their career. What I keep seeing is that users tend to lean toward one – their “favorite” – system and they can truly get very enthusiastic about it (which is a great thing for us marketers!)

This loyalty can be seen among the users of Creo Elements/Pro as well as Creo Elements/Direct – as well as users of any other CAD product out there. I think everyone has his/her own specific background that depends on many factors – what system you were exposed to at college/university or what you learned in an early stage of your career – or simply how much your employers invested in your training.

So, for example, if you were lucky to be well trained during an early stage in your career and your employer allowed you to take much software training, you were certainly acquiring an expertise that you could later advertise well – and find your next job because of these skills. If you have used many different tools in your career, you are in the position to compare different tools – and you may already have decided about your favorite. One way or the other, you kind of develop a preference for one tool over time and may try to continue working with it or hope to find this being used in your next job.

  • Engineers are smart people (No, this is not meant to be cheesy)

I think you have all gone through an education in mechanical engineering and would surely be capable of learning any new tool or use another modeling approach, if your job/company requires you to.

Direct modeling tools like Creo Elements/Direct are considered to be easy to use. However, I don’t think anyone in this thread was meaning to say that users of this product were using it because of lower skills.

Nor would anyone stick with one paradigm – either parametric or direct modeling - because their skills would not allow for change. If you are happy with your tool, you certainly look for a job where you can use it. But if your employer drives for change, and you are happy in this job overall, you will certainly follow on that path. As Paul Wyndham states it, “If someone cannot put aside a mindset to learn a new one - they are not putting enough effort into it. It all comes down to what is your job, and what does your boss want you to do.”

I totally agree with Paul here. If you are willing to change your modeling paradigm, you can, but like with any new software to learn, you will have to want it and open your mind for it. Plus take training. I assume it is the same as with the move from 2D to 3D CAD. I have talked to many users who had worked in 2D for years and then migrated to 3D and they all reported they only had to turn a switch in their heads and be open to learn something new – and then it was easy.

  • Nails and screws

To compare direct modeling and parametric modeling, the metaphor of the hammer has been used in the original thread: if you are tasked with hanging up a picture on the wall and if a hammer is your only tool, it will serve the task – no matter if you have a nail or a screw. If you know whether you need to deal with a nail or a screw and you have different tools available, you will choose the best one for the job.

I can follow the argument here, but I think we need to spin this a bit further. What if your only task each day is to hang up pictures, it doesn’t matter if you are dealing with a nail or screw and you wouldn’t need to consider any other tools. But what if you have to remove the nail/screw from the wall again – then pulling out a screw will leave an ugly, bigger hole than a nail.

And you would probably need a separate tool to even accomplish it, as a screw cannot be pulled out as easily as a nail. So, the more complex the task gets, the better it is to have a full toolbox with a variety of tools to give you the freedom to choose the right tool for the task. However, the prerequisite is that you need to know how to operate each tool.

In his reply to this original comment with the metaphor, another contributor compared both paradigms to a hammer, but different styles of hammers and you would choose the one that fit your hand best and you felt most comfortable with. I agree to the point that you can probably serve several different tasks with just one tool, if you are skilled / trained on this tool and feel comfortable using it. So, any hammer (the hammer of your choice) can get your nail – or screw - into the wall and if it had a claw and you were strong enough, you could certainly even pull it out with it. But in reality, only a screwdriver would be able to remove the screw easily and without leaving a big hole. However, this doesn’t mean that your hammer is a low quality one.

What, if, when…

What I am trying to say here is that in reality, things are not always so easy. There are many different job tasks, different people with different skill sets and different scenarios regarding the product lifecycle.

Interestingly, the first half of the original thread was written before PTC had announced Creo on October 28, 2010. The comments that were added after October 28, knowing that PTC would be offering the full toolbox, were of a different quality. People started discussing less about which paradigm to use, and more about which paradigm to use when, acknowledging that there are many use cases where both paradigms should be used together to provide the ‘best tools for the job’.

My own enlightenment from this exercise is that this post’s title (“Versus”) isn't a good fit, but the discussion if somebody should take a look at a new paradigm is absolutely up-to-date.

I think that by being familiar with both paradigms, any individual can increase his/her value to their organization and respond to a wider range of design requirements. The best: you don’t even need to wait for Creo, you can start working with Creo Elements right away.


Now please start commenting to my post, I want 13k page views, too

Bettina

PS: There is a webcast series coming up soon of four live webcasts exploring the use cases where direct modeling tools fit into a parametric environment. Feel free to sign up if you are interested.


Also, if you are a using parametric modeling today and you would like to play around with Creo Elements/Direct, take a look at the free Direct Modeling Personal Edition.

    2 replies

    Feb 3, 2011 10:24 PM UTC

    Great post and summary Bettina.

    I think the idea of CREO is a great one if it's implemented as advertised.  Having the ability to use parametric and direct modeling as the task dictates is the best of both worlds.

    No matter what direction you are coming from, you will need an open mind to the new approach in modeling.  Don't let your expertise in one way of modeling frustrate your learning experience with the other.  Knowing both methods of modeling will allow you to truly understand their strong points and you can determine if a mixed environment is right for you.

    I am enthusiastic about learning the Direct Modeling approach and I hope CREO can provide a great experience when mixing them together.

    Feb 15, 2011 10:46 AM UTC

    Thank you! I agree with your comment and specifically like this sentence: 

    Don't let your expertise in one way of modeling frustrate your learning experience with the other.