SysML 2 and Trechoro: What Sparx EA Teams Need to Know About the Transition

SysML 2 — and its underlying kernel language KerML — is not an incremental update. It is a redesigned language with new syntax, new semantics, and a new tooling ecosystem. Sparx Systems' answer is Trechoro, a modeling platform built natively for SysML 2 and KerML, separate from Sparx EA. Trechoro is here for evaluation and early adoption, but SysML 1.x — implemented in Sparx EA — remains the dominant production language across defense, aerospace, automotive, and other MBSE-intensive domains.

For most teams with active SysML 1.x repositories, the guidance is simple to state and harder to time: don't panic, don't migrate now, but start understanding the transition. 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 in 2026.

What SysML 2 and KerML are

SysML 1.x was defined as a UML profile — extensions layered on top of UML 2. That approach carried inherent limits: the language was constrained by UML's class-diagram origins, and its formal semantics were insufficient for precise simulation and verification.

SysML 2 takes a different route. It is built on KerML (Kernel Modeling Language), a new foundational language designed with formal semantics from the ground up. SysML 2 is then a library of extensions on KerML rather than on UML. The result is a language with:

• Precise formal semantics — every construct has a well-defined computational meaning, enabling automated analysis and verification.
• New textual and graphical syntax — a cleaner separation between notation and model than SysML 1.x offered.
• Redesigned diagram types — many familiar SysML 1.x diagrams (BDD, IBD, PAR) are replaced or significantly reworked; the mapping is not one-to-one.
• First-class part relationships — the part/port/connector model is rebuilt in KerML with cleaner composition and interface semantics.

The language is a published OMG standard. The specification is public. Tool support is nascent but growing.

What Trechoro is

Trechoro is Sparx Systems' implementation of SysML 2 and KerML — a modeling-first platform built to support the language natively, independent of UML. It is a distinct product, not a Sparx EA version update. The facts that matter for planning:

• It supports both graphical and textual authoring, with a unified approach that suits version control and CI/CD-style engineering workflows.
• It is positioned as Sparx Systems' strategic MBSE platform for SysML 2 going forward.
• Sparx EA continues to be maintained and supported for SysML 1.x work, with no announced end-of-life for that support.
• 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, though traceability to existing assets can be preserved through controlled referencing.

Evaluate Trechoro's maturity for production the way you would any new platform: against your specific modeling needs, your team's capability, your program's requirements, and your supply chain's toolchain expectations. Early adoption without a clear migration strategy rarely ends well for teams with large SysML 1.x investments.

Where the ecosystem stands

Honesty is warranted. As of 2025–2026, the SysML 2 ecosystem is in transition on four fronts.

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 organizations is governed by program commitments rather than technology preference.

What this means for your Sparx EA repository

If you have an active Sparx EA repository with SysML 1.x models, here is the practical guidance.

Don't migrate preemptively. SysML 1.x in Sparx EA is not going away, and your existing models retain their value for current programs. There is no urgency to migrate content that is serving active program needs.

Don't make new long-term 1.x tooling investments without a plan. If you are starting a new MBSE program with a multi-year timeline reaching into the late 2020s, factor SysML 2 into your tooling strategy even if the initial implementation uses 1.x. Know when your tool commitments need to be revisited.

Start building SysML 2 understanding now. The specification is public and Trechoro is available for evaluation. Understanding what SysML 2 modeling looks like — the new diagram types, the KerML constructs, the textual syntax — positions your team to evaluate migration timing intelligently rather than reactively.

Engage your program stakeholders. For defense and aerospace especially, the timing of SysML 2 adoption is often set by prime contractor or government customer tool requirements. Understand what your downstream stakeholders expect before committing to a timeline.

Maintain your SysML 1.x governance discipline. Well-governed models are easier to migrate when the time comes than poorly-governed ones. The same modeling discipline that keeps a repository healthy also keeps it migration-tractable.

When to start planning a transition

The practical triggers for a structured SysML 2 / Trechoro transition plan:

• A new program is starting with a planned duration extending to 2028 or beyond, where SysML 2 adoption is feasible from the outset.
• A client or program 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 are imminent for most teams as of 2026. Monitor, understand, and plan — then act at the pace your program realities require.

FAQ

SysML 2, Trechoro, and the wider MBSE ecosystem will evolve significantly over the next two to three years. We provide ongoing platform guidance for MBSE teams navigating this — from current-state SysML 1.x governance to strategic planning for SysML 2 readiness. Whether you are evaluating Trechoro, planning a new program, or want an honest read on when migration makes sense, our work with architects and on Sparx EA is built for exactly these calls.