Direct Answer: SysML 2 (and its underlying kernel language KerML) is a significant redesign of the Systems Modeling Language — not an incremental update but a new language with new syntax, new semantics, and a new tooling ecosystem. Sparx Systems’ response is Trechoro, a new modelling platform built natively for SysML 2 / KerML, separate from Sparx EA. Trechoro is available now, but SysML 1.x — implemented in Sparx EA — remains the dominant production language across defence, aerospace, automotive, and other MBSE-intensive domains. For most Sparx EA teams with active SysML 1.x repositories, the practical guidance is: do not panic, do not migrate immediately, but start understanding the transition now. SysML 1.x repositories have a runway. How long that runway extends depends on domain, client mandates, and toolchain maturity — factors that are still evolving.
Key Takeaways
- SysML 2 / KerML is not backward compatible with SysML 1.x. It is a new language requiring new tools, not an upgrade to existing models.
- Trechoro is Sparx Systems’ SysML 2 / KerML platform — a new tool, not a Sparx EA version upgrade.
- SysML 1.x remains dominant in production MBSE environments in 2025 and 2026. Migration timelines are programme-driven, not tool-driven.
- Existing Sparx EA SysML 1.x repositories do not automatically convert to SysML 2. There is no automated migration path at this time.
- The risk of premature migration is real: programme commitments, contractor capability, and supply chain tool expectations are all built on SysML 1.x today.
What SysML 2 and KerML Are
SysML 1.x was defined as a UML profile — a set of extensions layered on top of UML 2. This approach created inherent limitations: the language was constrained by UML’s class-diagram origins, and the formal semantics were insufficient for precise simulation and verification use cases.
SysML 2 takes a fundamentally different approach. It is built on KerML (Kernel Modeling Language) — a new foundational language designed with formal semantics from the ground up. SysML 2 is then defined as a library of extensions on KerML, rather than extensions on UML. The result is a language with:
- Precise formal semantics — every modelling construct has a well-defined computational meaning, enabling automated analysis and verification.
- New textual and graphical syntax — SysML 2 has both a textual notation (the SysML v2 textual syntax) and graphical diagrams, with a cleaner separation than SysML 1.x.
- New diagram types — many familiar SysML 1.x diagrams (BDD, IBD, PAR, etc.) are replaced or significantly redesigned. The conceptual mapping is not one-to-one.
- First-class part relationships — the part/port/connector model is redesigned in KerML with cleaner semantics for composition and interface specification.
The language is an OMG standard. The specification is published and publicly available. Tool support is nascent but growing.
What Trechoro Is
Trechoro is Sparx Systems’ implementation of SysML 2 / KerML. It is a new platform — not a Sparx EA version update, but a separate application built to natively support the SysML 2 language constructs and KerML kernel.
Key facts about Trechoro:
- It is available now (as of 2025) in a form that supports active evaluation and early adoption.
- It is positioned as Sparx Systems’ strategic MBSE platform for SysML 2 going forward.
- Sparx EA will continue to be maintained and supported for SysML 1.x work — there is no announced end-of-life for SysML 1.x support in Sparx EA.
- Trechoro and Sparx EA are separate products with separate licensing.
- Trechoro does not import or convert Sparx EA SysML 1.x models directly. The languages are not compatible at the model level.
Trechoro’s maturity should be evaluated for production use in the same way any new tooling platform is evaluated: against your specific modelling needs, your team’s capability, your programme’s requirements, and your supply chain’s toolchain expectations. Early adoption without a clear migration strategy is unlikely to end well for teams with large SysML 1.x investments.
The Current State of the Ecosystem
Honesty is warranted here. As of 2025–2026, the SysML 2 ecosystem is in transition:
Tool maturity. Trechoro is available but not production-mature in the way Sparx EA has been refined over two decades. Other tool vendors (No Magic, IBM Rhapsody, Cameo, PTC Windchill) are at various stages of SysML 2 support. The tool ecosystem that practitioners have relied on for SysML 1.x — mature, well-documented, with a large experienced user base — does not yet exist for SysML 2.
Language adoption. Major MBSE-intensive programmes (defence platforms, aerospace projects, automotive development) are largely still on SysML 1.x. Programme commitments, contract language, and supply chain requirements are built on existing language versions. Organisations will migrate at the pace of their programme cycles, not at the pace of the specification release.
Training and capability. The SysML 2 practitioner community is small. Training materials, certified training providers, and experienced practitioners are limited compared to SysML 1.x. This is a practical constraint for any organisation considering early adoption.
Migration tooling. There is no automated migration path from SysML 1.x to SysML 2. The languages are semantically different enough that manual re-modelling is required for many constructs. Organisations with large SysML 1.x repositories face a significant migration effort when they choose to transition.
None of this means SysML 2 is the wrong direction — it is clearly a more rigorous, more capable language. But the transition will take years, not months, and the realistic timeline for most organisations is governed by programme commitments rather than technology preferences.
What This Means for Your Sparx EA Repository
If you have an active Sparx EA repository with SysML 1.x models, the practical guidance is:
Do not migrate preemptively. SysML 1.x in Sparx EA is not going away. Your existing models retain their value for current programmes. There is no urgency to migrate content that is serving active programme needs.
Do not make new long-term investments in SysML 1.x tooling without a plan. If you are starting a new MBSE programme with a multi-year timeline that will extend into the late 2020s, factor SysML 2 into your tooling strategy even if the initial implementation uses SysML 1.x. Know when your programme’s tool commitments need to be revisited.
Start building SysML 2 understanding now. The specification is public. Trechoro is available for evaluation. Understanding what SysML 2 modelling looks like — the new diagram types, the KerML constructs, the textual syntax — positions your team to evaluate migration timing intelligently rather than reactively.
Engage with your programme stakeholders. For defence and aerospace programmes specifically, the timing of SysML 2 adoption is often determined by prime contractor or government customer tool requirements. Understand what your programme’s downstream stakeholders expect before committing to a migration timeline.
Maintain your SysML 1.x governance discipline. Well-governed SysML 1.x models are easier to migrate (when the time comes) than poorly-governed ones. The MDG discipline that improves AI readiness also improves migration tractability.
When to Start Planning a Transition
The practical triggers for beginning a structured SysML 2 / Trechoro transition plan:
- A new programme is starting that has a planned duration extending to 2028 or beyond and for which SysML 2 adoption is feasible from the outset.
- A client or programme office formally specifies SysML 2 tool support as a requirement.
- Your supply chain partners begin adopting Trechoro or other SysML 2 tools at scale, creating interoperability pressure.
- Sparx Systems announces a timeline for SysML 2 features in Sparx EA or signals a support horizon for SysML 1.x.
None of these triggers are imminent for most teams as of 2026. Monitor, understand, and plan — but act at the pace your programme realities require.
FAQ
What is SysML 2 and how is it different from SysML 1.x? SysML 2 is a redesigned Systems Modeling Language built on KerML (Kernel Modeling Language) rather than as a UML profile. It has new formal semantics, new syntax (textual and graphical), and new diagram types. It is not backward compatible with SysML 1.x — the languages differ fundamentally at the semantic level. SysML 2 is designed to support formal analysis and verification use cases that SysML 1.x’s UML inheritance made difficult.
What is Trechoro? Trechoro is Sparx Systems’ SysML 2 / KerML modelling platform — a new product separate from Sparx EA, built natively for the SysML 2 language. It is available now for evaluation and early adoption. Trechoro is not a Sparx EA version upgrade; it is a separate application for SysML 2 work. Sparx EA continues to support SysML 1.x with no announced end-of-life.
Do I need to migrate my Sparx EA SysML 1.x models to SysML 2 now? No. SysML 1.x remains the dominant production language in MBSE-intensive domains. For active programmes using SysML 1.x in Sparx EA, there is no urgency to migrate. The SysML 2 ecosystem — tools, trained practitioners, migration tooling — is not yet mature enough to support large-scale migration without significant re-modelling effort. Plan for the transition, but act at the pace your programme commitments and client requirements dictate.
Is there an automated migration path from Sparx EA SysML 1.x to Trechoro SysML 2? Not at this time. SysML 1.x and SysML 2 are semantically different languages — the constructs do not map one-to-one. Migration involves re-modelling key elements in the new language constructs, which requires practitioner time and judgment rather than automated transformation. Tooling to support migration may emerge as the ecosystem matures, but currently migration is a manual, programme-level undertaking.
Will Sparx EA be discontinued in favour of Trechoro? There is no announced plan to discontinue Sparx EA. Sparx Systems has positioned Trechoro as their SysML 2 / KerML platform while continuing Sparx EA for the breadth of modelling use cases it supports — UML, ArchiMate, BPMN, SysML 1.x, TOGAF, and others. Sparx EA and Trechoro coexist as complementary products for different use cases. Monitor Sparx Systems communications for any updates to this positioning.
How should I factor SysML 2 into a new MBSE programme starting now? Evaluate the programme’s timeline and client requirements. For programmes extending to 2028 or beyond, include a SysML 2 tooling review in your technology strategy. If the programme allows tooling flexibility, evaluate Trechoro alongside Sparx EA for the SysML-intensive work packages. If the programme has existing toolchain commitments (prime contractor tools, government customer requirements), align with those first. Include a periodic technology review point where the SysML 2 ecosystem maturity is reassessed against your programme’s evolving needs.
Stay Informed as the Ecosystem Evolves
SysML 2, Trechoro, and the MBSE tool ecosystem will evolve significantly over the next two to three years. Sparx Services provides ongoing platform guidance for MBSE teams navigating this transition — from current-state SysML 1.x governance to strategic planning for SysML 2 readiness.
Talk to us if you are evaluating Trechoro, planning a new MBSE programme, or want an honest view of when migration makes sense for your context.
