Fields marked with a * are required


Will MSC’s Apex Revolutionize Simulation?

References Cited

MSC Software, Mechanical Computer Aided Design (MCAD), Mechanical Computer Aided Engineering (MCAE)

That quote is what kicked off my briefing with MSC Software CEO Dominic Gallello. If you’ve never heard of a BHAG, a Big Hairy Audacious Goal, then let me tell you: this is one. And, by the way, this is a very worthy goal. As I found from the more than 1,000 responses to our 2013 Simulation Driven Design Study, there are still major problems in the simulation process. Modeling and meshing still take way too long. Analyzing and documenting results take far too long as well.

So, did MSC Software succeed in revolutionizing the simulation process? We’ll get to that in due time. But to start, let’s dig into what Apex is and what capabilities it provides.

Capabilities Delivered by Apex

First things first: what the heck is it? How does it fit into MSC Software’s existing suite of products?

To be more accurate, Apex is more of a platform composed of many apps or modules. More will be coming out in the future to address a wider and more integrated range of physics phenomena.

Now, we’ve had pre-processors around for ages. How is Apex unique? Part of the answer lies in new functionality to create and manipulate geometry.

We’ve heard this story before, of course. Direct Modeling capabilities are a natural fit to tweak and change detailed design geometry before you get to meshing. However, Apex is different in the automation that is built into the platform.

The idea here is that once you have set up a simulation model, modifications to the geometry triggers the propagation of change to the mesh and re-solves the simulation. If this concept feels familiar, that’s because it is. This is associativity applied to simulation. We’ve had associativity between 3D models and 2D drawings for ages.

Why haven’t we had this before? The primary reason, at least in my mind, has been the large amounts of computationally intensive time required to mesh and solve simulation models. Obviously, with very large models, automatically re-meshing and re-solving could lead to problems. But for now, MSC says Apex is best suited for day-to-day simulation driven design use cases, which translates to piece part and small assembly design by engineers. MSC does, however, have plans to address this objection longer term.

Computational Parts

Along with the focus on empowering and automating simulation driven design were a few other novel concepts in Apex. One of those was the idea of Computational Parts.

In today’s design chains, suppliers must often provide simulation models of their designs to their customers. Their customers then integrate those simulation models into their own simulations so they can understand the big picture of performance. The problem? Providing the detailed design geometry or even the mesh exposes the supplier’s intellectual property. In some extreme cases, the supplier’s customers will give that design to another supplier in an attempt to cut costs out of the design chain. Ethics, apparently, is so 20th century.

With Apex, however, MSC Software has come up with a new way to protect that intellectual property.

So basically, a supplier can hand over a file that is encrypted mathematics. It will have already been validated for certain solvers, so it can be integrated into another simulation model. Certain interfaces will have already been defined and tagged, so the customer knows how to ‘hook’ it into their model. Yet, there is no need to conceal, wrap or hide the geometry… because the geometry is quite literally not there. There is no geometry to see, just a mathematically reduced simulation representation.

Enabling the Engineer

There’s a lot to the Apex release. A lot more than I can possible exhaustively cover here. But there is one other area of note: getting casual users up to speed.

This is a lot of investment for casual users.

Commentary and Analysis

So, lets get back to Gallello’s Big Hairy Audacious Goal. Has MSC Software revolutionized simulation driven design?

To answer that, I need to go back a little bit. Some four years ago, I outlined four Very Real Skillset Challenges to Simulation Driven Design in a post. They included:

  1. Background in Engineering Science
  2. Understanding Computational Methods
  3. Familiarity with CAD Software
  4. Knowledge of Simulation Software

With Apex, MSC Software has mashed up CAD and Simulation, collapsing challenges 3 and 4. Furthermore, the CAD and Simulation capabilities there are focused, excluding drawing creation, routed systems design and everything else. Additionally, the 100+ hours of training videos and tutorials, all of which have been localized, further addresses challenges 2, 3 and 4. They focus not only on how to use the software, but also some of the fundamental concepts of the Finite Element Method and its potholes. Furthermore, the automation of the simulation process has the potential to change the dynamic usually associated with simulation during the design process, where engineers get simulation results too late because they had continued to iterate and experiment.

Now, while the integrated geometry-mesh modeling first caught my eye, it seems to be no new trick. Siemens PLM’s NX has similar functionality where once geometry is changed, the mesh is updated. The same goes for solidThinking Inspire. However, I am unfamiliar with how automated the procedure is. What I will say, however, is that unlike ANSYS’ acquisition of Spaceclaim, MSC Software’s Apex looks like a coherent holistic vision. We really don’t know what ANSYS plans for Spaceclaim, if anything. And I don’t know about you, but I’ve seen far too many acquisitions where the technology disappears after a few years. With Apex, MSC Software has laid out a clear vision of how they are adding geometry capabilities in the context of a broader associative process. That’s a good thing.

Lastly, some of you may be concerned that Apex is not similar, UI-wise, to the other products in their suite. For me, however, it is the right move. Back in March of this year, in a guest post I published on the PTC Creo blog, titled The Splintering Needs of Engineering Simulation, I saw a divergence in the needs of an everyday engineer and simulation analyst specialists.

So, back to our question: has MSC Software revolutionized simulation driven design? Well, I’m not ready for a resounding yes. But for the first time in a while, I feel deservedly optimistic.


  • MSC Software has released two new products as part of a new suite: Apex Modeler and Apex Structures.
  • Apex Modeler provides Direct Modeling capabilities to create and manipulate geometry.
  • Apex brings associativity to the simulation process. Geometry changes update the mesh and re-solve the simulation.
  • Computational Parts mathematical reduces simulation models. This geometry-less output can be integrated into other simulations but doesn’t expose any geometric intellectual property.
  • Apex is built for casual users, with over 100 videos and tutorials which have all been localized.

That’s my take folks. Looking forward to your thoughts in the comments.

Take care. Talk soon. Thanks for reading.

Chad Jackson is an Industry Analyst at Lifecycle Insights and publisher of the engineering-matters blog. With more than 15 years of industry experience, Chad covers career, managerial and technology topics in engineering. For more details, visit his profile.

Like this post?

Sign up now to get more like it

Fields marked with a * are required


  • MSC Nastran Beginner

    Great article. Accurate perspective on MSC Apex.

    A few comments

    There are numerous benefits to Computional Parts. The post hit one of the benefits perfectly, but missed a more important one: Computational Parts are less computationally expensive. Just pulling numbers from thin air to make a point, consider an original model that requires 2 hours to solve. With Computional Parts the same part could require 10 minutes to solve. An assembly composed of multiple parts that once required a whole day to solve can now just be solved in a few minutes if Computational Parts are used.

    I saw one of your tweets comparing MSC Apex Modeler to a pre processor. I the MSC guys are going for something different that is not a generic pre/post processor. One defining characteristic of a pre processor is the ability to import and export FEA input files. Patran, Hypermesh, Ansys, Abaqus CAE, and many others can import and export an FEA input file. MSC Apex Modeler does not import an input file. This is a reflection of one MSC Apex’s goals, that is, to make unified CAE platform where the pre/post steps are not separate but intertwined.

    Another question headline that is not answered. “Will MSC’s Apex Revolutionize Simulation?” “Well, I’m not ready for a resounding yes. But for the first time in a while, I feel deservedly optimistic.”