What are the biggest things to look out for in Creo 7.0? What are the implications there? This article ties directly into a series that we’re developing on the trends that are reshaping mechanical design. I fundamentally see some big changes on the horizon for mechanical design. This plays into it, but let’s talk about Creo 7.0.

Real-Time Generative Design Capabilities

First off, let’s talk about real-time generative design capabilities. This comes from the integration with Ansys Discovery Live. You can set up your constraints. You can set up the objectives that you want for your generative design effort. There’s a lot of options for constraints such as manufacturing constraints, design constraints and geometry constraints. But then you can watch in real time as the design will morph and change on your screen. You can stop it. You can basically pause it or have it continue. That’s a really interesting capability that’s now embedded directly within Creo 7.0. You don’t have to go out to Discovery Live and do data translation back and forth. The integration is nice that way.

They also have new functionality with respect to using a dashboard in automation. You can set off a number of runs for this to generate different design options. You can track that using graphs and through a dashboard, and that actually leverages cloud computing capabilities. Those are all really interesting capabilities.

Lattice Geometry and Lattice Modeling

The second thing has to do with lattice geometry and lattice modeling. You can define a shape that you want to fill a volume with. You can define its orientation. You can actually vary the density of the shape within the volume, according to formulas or equations. This gets into actually in our other series, we talk about it as micro-modeling, as opposed to macro-modeling the bigger shape. But this micro-modeling capability is actually going to be pretty crucial going forward. Both in terms of today, you see it with lattice in Creo 7.0, but it’s also going to become really important with multi-material modeling as well as varying material properties.

Multibody Part Design

The third thing that’s really interesting, and it might’ve slipped under the radar a little bit. I don’t think people recognize what’s going on with it, but multibody parts. You can define multiple volumes within a single part and then you can apply different modeling approaches or activities around that. You can select one volume for a generative design run. You can select a different volume for the application of lattice or micro modeling. Let’s take a quick look at that.

Here is a simple example where you have multiple volumes for the same part. Maybe for the boss that we have here. We want to apply lattice modeling. It’s going to be filled with these little shapes and have lots of air gaps, which means you’ll probably have to use 3D printing for it. We also want to use a generative design approach for the rib and really get an optimized shape for that application. This is a real simple example. But you can imagine much more complex parts and using different modeling approaches and activities for different parts of it. What’s fascinating about that for me is this really can lend itself to park consolidation. You can have one very large part of it. A section of that part is composed of lattice structures. Another section has this wildly organic shape that is really optimized for the application it needs to be used for.

That rounds up the big takeaways that I had with Creo 7.0. There are lots of enhancements. They invested a lot of money in developing this new release. There’s lots of new capabilities and all sorts of different areas. Model-based definitions and model-based enterprise is one of those. They have lots of new capabilities there. But these were the three that I saw coming together. Enhancing generative design, especially with real-time stuff and then using lattice capabilities. This micro-modeling type of approach. Plus, combining that with multibody parts I thought was this convergence that maybe a lot of people might not have recognized.