MCD Version History Notes and Broader Industry Context

Version-specific information about MCD specifically is thin in public sources — Siemens' official "what's new" blogs for NX cover CAD/CAM/design broadly and rarely call out MCD-specific deltas by name. The items below are the concrete, sourced version/edition facts found; treat this file as a supplement of a few solid data points rather than a comprehensive version-history table.

MCD's origin point: built into NX 7.5

DEVELOP3D's original March 2011 review of the (then-new) Mechatronics Concept Designer confirms it was built on NX 7.5 and was explicitly positioned as an "excellent first release" — i.e., MCD is not a bolt-on tool with a separate long history; it emerged as an NX module starting around the NX 7.5 timeframe, aimed squarely at breaking the sequential mechanical→electrical→software handoff bottleneck via a V-model functional-structure approach linked to Teamcenter requirements.

Source: https://develop3d.com/product-design/siemens-mechatronics-concept-designer/

OPC UA / PLCSIM Advanced direct connection arrived at NX 12.0

Per Siemens community forum discussion, NX 12.0 is the version where MCD gained OPC UA support and a direct connection type to S7-PLCSIM Advanced that eliminates the need for a separate Signal Server. Anything describing a Signal Server as a required component for PLCSIM Advanced coupling is describing a pre-NX-12 workflow. See signal-mapping-opc-ua-plcsim-integration.md in this collection for the full detail.

Source: https://community.plm.automation.siemens.com/t5/NX-Design-Forum/NX-MCD/td-p/433191

Physics engine: PhysX (Nvidia), consistent across the product's life

Both the 2011 DEVELOP3D review and current product descriptions confirm MCD's real-time physics simulation runs on the PhysX engine, licensed from Nvidia — this appears to be a stable, long-standing architectural choice rather than something that has changed across versions in public sources found during this research. No public source was found documenting a physics-engine swap or major solver rewrite between versions.

NX X (cloud/SaaS) vs. classic on-premises NX MCD

Siemens markets NX X as a cloud-licensed, cloud-provisioned edition of NX (including an "NX X MCD" variant), positioned by Siemens as functionally equivalent to on-premises NX: "both on-premises and SaaS versions are built on the same NX architecture with the same data model, user interface and functionalities... you can use NX X and on-premises NX with no translation as they work the same, look the same and feel the same." NX X is installed to the desktop via Siemens Software Center, with licensing/user provisioning handled in the cloud rather than via traditional license servers.

A separate, more limited browser-based "NX X Essentials" tier also exists, described as enabling native NX data editing directly in a browser — but its feature set is explicitly narrower than the full desktop NX X Design/MCD solutions. No source found gave a specific MCD-feature-parity breakdown for the browser tier vs. full desktop MCD, so if evaluating NX X Essentials specifically for mechatronic concept modeling, verify current MCD feature coverage directly with Siemens rather than assuming full parity.

Sources: https://blogs.sw.siemens.com/nx-design/benefits-of-cloud-saas-nx-x-cad/ , https://feacomp.com/siemens-disw-products/siemens-nx-mechatronics-concept-designer/ , https://plmtechtalk.com/2026/01/27/practical-adoption-guide-where-nx-x-essentials-fits-in-design-and-manufacturing-teams/

Commissioning-time-reduction figures vary widely by source — don't over-index on any single number

Different sources cite very different headline numbers for virtual-commissioning time savings attributable to MCD-based workflows:

• A named, attributed industry case (Tronrud Engineering, packaging machinery) reports a 20–25% reduction in commissioning phase — see case-study-tronrud-packaging-machine.md.
• A promotional/industry-overview piece (digitaltwinproject.eu) cites broader "industry studies indicating reductions that can reach 50–70% of the time traditionally required" without naming the underlying studies.

The gap between a real, named 20–25% figure and an unattributed 50–70% marketing claim is worth keeping in mind when setting stakeholder expectations for a new MCD-based virtual commissioning initiative — plan around the lower, attributable figure and treat the higher figure as an aspirational ceiling rather than a typical outcome.

Source: https://digitaltwinproject.eu/digital-twin-and-nx-mcd-the-future-of-virtual-commissioning-in-manufacturing/