Skip to main content
Cadence completes its acquisition of Hexagon's Design & Engineering business, bringing MSC Software simulation tools under Cadence, supported in India by GSAS Micro Systems

MSC Software Is Now Part of Cadence: What the Hexagon Acquisition Means for Indian Simulation Teams

GSAS Engineering · · 6 min read

If your team in India runs MSC Nastran, Adams, Marc, Cradle CFD, Actran, Romax, or VTD, you may have seen the headlines: the MSC Software simulation portfolio has a new home. As of February 23, 2026, these tools are part of Cadence.

The short version for GSAS customers: nothing changes about how you work. Your tools, your models, your file formats, your MSC One token pools, and your procurement through GSAS all continue exactly as before. This post explains what happened, what stays the same, and where the change actually helps you.

What happened

Cadence completed its acquisition of Hexagon’s Design & Engineering (“D&E”) business: the division that builds the MSC Software simulation portfolio along with Cradle CFD, Actran, Romax, and the VTD driving-simulation platform. Cadence has positioned the move as advancing its leadership in Physical AI and multiphysics simulation, combining its existing multiphysics work with decades of structural analysis, acoustics, and multibody dynamics from the MSC line-up.

In other words, the simulation solvers that Indian automotive, aerospace, defence, and heavy-engineering teams have relied on for years now sit inside a larger multiphysics simulation portfolio, with the engineering and R&D backing that comes with it.

What stays the same for your team

This is the part that matters most for engineering managers and procurement teams in Bengaluru, Hyderabad, Chennai, Pune, Mumbai, and Delhi NCR:

  • Same tools, same names. MSC Nastran is still MSC Nastran. Adams, Marc, Cradle CFD, Actran, Digimat, Simufact, Romax, VTD, MSC Apex, Patran, Dytran, MaterialCenter, MSC CoSim, and SimManager keep their names and their solver behaviour.
  • Same models and workflows. Your existing models, decks, scripts, and file formats are unaffected. Your validated solver setups keep producing the same results.
  • Same MSC One licensing. The MSC One token-pool model works exactly as it did, one shared pool across the whole solver portfolio. Per-solver, floating (FlexLM), and subscription options continue too.
  • Same partner in India, GSAS. GSAS Micro Systems remains your authorized engineering partner for the MSC simulation portfolio. Local procurement with INR invoicing, GeM, SAP Ariba, Coupa, and TReDS support, certified training workshops, MSC One token-pool sizing, and application-engineering support all continue without interruption.

We have supported this portfolio across India since 2018. That relationship, and the people you work with, does not change.

What gets better

Now that these solvers are part of Cadence’s broader multiphysics and Physical AI simulation portfolio, the roadmap behind them gets deeper. For Indian teams, that means GSAS can bring a wider set of Cadence simulation capabilities to the bench over time, more multiphysics breadth around the structural, CFD, acoustic, multibody, and driving-simulation tools you already run, and tighter coupling across them.

If you are scaling an NVH program, an EV thermal-management workflow, an ADAS/AD validation pipeline, or a certification-driven structural workflow, this is a portfolio that is investing in exactly those areas.

Questions Indian teams are asking

Do my current licenses still work? Yes. There is no action required on your existing MSC One pools or per-solver licenses.

Does anything change about pricing or INR procurement? No. GSAS continues to invoice in INR with the same GeM, SAP Ariba, Coupa, and TReDS routes.

Will the product names change? The solvers keep their established names, MSC Nastran, Adams, Marc, Cradle CFD, Actran, Romax, and the rest. If you search for “MSC Adams” and land on a Cadence page, it is the same product: see MSC Adams, now part of Cadence for the module breakdown and the India licensing routes.

Who do I contact for support, renewals, or new seats? The same team at GSAS Micro Systems. Nothing about your point of contact changes.

Talk to GSAS

Whether you are renewing MSC One, sizing a new token pool, evaluating Adams or Cradle CFD, or planning an ADAS validation program, the GSAS applications-engineering team is here in India to help, from Bengaluru, Hyderabad, Chennai, Pune, Mumbai, and Delhi NCR.

Explore the full portfolio on our Cadence simulation partner page, or request a quote and we’ll get back to you with India-local pricing and licensing options.


Sources & further reading:

Interested in Cadence tools?

Talk to our application engineers for personalized tool recommendations.

Stay in the Loop

Get monthly compliance updates, product insights, and engineering best practices delivered to your inbox.

Related Articles

Side by side vehicle outlines comparing a domain E/E architecture grouped by function against a zonal E/E architecture grouped by physical location, with zone controllers on an Ethernet backbone into central compute, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

Domain vs Zonal E/E Architectures Explained

Domain architectures group ECUs by function, zonal architectures group them by where they sit in the vehicle. This guide is the engineer's read on the difference: what physically moves, what the in-vehicle network has to become, and what happens to diagnostics, rest bus simulation and time sync. It also refuses to repeat the harness mass and ECU-count figures that circulate without a public source, and says exactly which claims are citable and which are not. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 13 min read
Left to right continuous integration pipeline from commit through build and a software-in-the-loop gate into a bench queue with a reservation gate, then a hardware-in-the-loop run and a report, showing the HIL bench as a shared queued resource, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

Test Automation for SDV: ASAM XIL, Virtual ECUs, CI for HIL

Every software-defined vehicle programme in India eventually asks the same question: why does a test case written for a laptop have to be rewritten for the virtual ECU and rewritten again for the bench? The two public anchors that answer it are the ASAM XIL API and the FMI packaged model format: FMI is a free standard, and ASAM publishes enough of XIL's structure openly that you can specify against it before anyone buys the document. This article walks the shift-left ladder honestly, including the four things that cannot move left, and treats the hardware-in-the-loop bench as a queued shared resource inside continuous integration rather than a desk someone books. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 13 min read
Dense PCB with fine-pitch components illustrating the challenge of probing modern high-density boards
Industry Insights Sensepeek

Shrinking Boards, Growing Problems: Why Hands-Free Probing Is Essential as Component Density Rises

As PCBs shrink to 0201 components, QFN packages, and BGA-only processors, traditional probing methods fail. Here is why the Sensepeek PCBite hands-free system is becoming essential for modern hardware debug.

7 Apr 2026 · 4 min read