SysML v1 vs SysML v2: what's changing, and should you adopt it in Cameo?

What SysML v2 actually changes

SysML v2 is not a cosmetic refresh. It addresses four fundamental limitations of v1:

• A new metamodel. SysML v1 was a profile layered on UML, which introduced ambiguities and forced workarounds wherever UML's concepts didn't fit systems engineering cleanly. SysML v2 is built on KerML, its own purpose-built kernel language, making models more precise and less open to misinterpretation.
• A standardized REST API. The OMG SysML v2 API & Services specification defines a formal machine-readable interface to the model. Teamwork Cloud (CATIA Magic's collaboration server) conforms to this specification, enabling automation, CI/CD-style model workflows, and digital-thread integration that previously required custom scripting against proprietary APIs.
• Textual + graphical notation in two-way sync. v2 defines a .sysml textual form that stays synchronized with the graphical views. Models can be authored and diffed as text, reviewed in version control, and still opened as diagrams.
• Query-driven views and live requirement verification. In Cameo's v2 implementation, views are query-driven and rebuild automatically when the model changes. Requirement violations are flagged immediately with full traceability to the violated constraint.

The goal is to raise MBSE effectiveness by making the model a genuine, automatable single source of truth — not a set of diagrams maintained by hand.

v1 and v2 coexist — it's selectable per project

You don't face an all-or-nothing choice. CATIA Magic / Cameo 2026x lets you author v1 and v2 models in the same environment, with the SysML version selected per project. An organization can run new greenfield efforts in v2 while keeping existing v1 programs on the version they were built in. There is no forced cutover.

This coexistence model is intentional — the language committee understood that a hard flag-day migration would stall adoption. The practical result is that the decision is per-program, not per-organization.

Which Cameo editions include v2?

This is the detail to check before planning anything. SysML v2 is limited to Enterprise-tier bundles in the 2026x release.

The official compatibility matrix states that the SysML v2 Plugin is compatible only with Cameo Systems Modeler Enterprise edition. Resellers GoEngineer and TriMech report the supported license codes as M2E-N, M2E-C, M3E-N, M3E-C (reported as — confirm with your reseller or Dassault account team).

NOTE Cameo Systems Modeler Architect Edition and MagicDraw with the SysML Plugin do not gain SysML v2 on the 2026x upgrade. If you're on either of those, a v2-capable license upgrade is a separate purchase. The v2-supporting bundles also took an approximately 20% price increase on January 1, 2026.

Migration: honest picture

A v1-to-v2 migration plugin ships in Cameo 2026x under File > Export To > SysML v2 Model. The honest picture, per official Dassault documentation: the plugin is “a work in progress” and covers approximately 20% of the metamodel. Diagram migration is not supported — diagrams must be recreated. Migration failures are logged to a MigrationReportOf<project>.xlsx file for review.

A supported migration path exists, but full production migration does not — not yet. The practical implication: treat SysML v2 as a new language to author new models in, not a version bump to apply to existing ones. A large, mature v1 model on a production program should stay in v1 until the migration tooling matures.

Free Community Edition (MSOSA)

Dassault offers a free Community Edition installed as Magic Systems of Systems Architect (MSOSA). It is fully standard-conformant SysML v2, capped at approximately 500 major model elements — enough to learn the language, experiment with the textual notation, and evaluate v2 before committing to a licensed upgrade or re-procurement. The cap limits production use but makes it an ideal learning environment.

Should you adopt v2 now?

The case for adopting v2 now:

• Greenfield programs. Starting fresh in v2 avoids the migration problem entirely and positions the model for API-driven automation from day one.
• Automation and digital-thread work. The standardized API is a genuine leap. If CI/CD-style model validation or interoperability across tools is on your roadmap, v2 is the path.
• Training and experimentation. The free MSOSA Community Edition makes it cheap to build v2 fluency. Early movers will have an advantage as the ecosystem matures.

The case for staying on v1:

• Production programs with mature v1 models. The migration tooling covers only ~20% of the metamodel. A full re-model is a project, not a migration.
• Simulation-heavy programs. Full SysML v2 simulation is not yet supported in Cameo 2026x — the tool offers “evaluation” mode, not the full Cameo Simulation Toolkit equivalent. Parametric and behavioral simulation work belongs on v1 today.
• Near-term delivery pressure. Practitioners report notation and metadata bugs through the 2026x hot-fix cycles. Early-adopter friction is real.

The practical read: stay on v1 for production programs today, especially simulation-heavy ones. Adopt v2 for greenfield pilots, automation experimentation, and training — and use the free MSOSA Community Edition to build that fluency without a licensing decision. The trajectory is clear; the maturity is not quite there yet for high-stakes programs.

FAQ