On June 2, 2026, the Object Management Group opened registration for the first SysML v2 certification exam. The credential is called SysMLv2 Model User, and it's the entry point in a new exam series aimed squarely at the wave of teams now moving off SysML v1. If you've been waiting for a signal that v2 is real and here to stay, a formal certification track is about as concrete as it gets.

The timing isn't random. OMG finalized SysML v2.0 in July 2025, along with the Kernel Modeling Language (KerML) 1.0 and the Systems Modeling API and Services 1.0 that underpin it. The specs were then cleaned up editorially in March 2026 for submission to ISO. With the language stable and heading toward an international standard, the next bottleneck is people who can actually read and build the models. That's what the certification program is meant to address.

What the Model User exam actually tests

Model User is an interpretation-focused credential. It certifies that you can read a SysML v2 model and understand what it says, not that you can architect one from scratch. OMG describes the scope as core SysML v2 concepts: modeling structure, behavior, requirements, analysis cases, and verification cases, expressed in both the graphical notation and the textual syntax.

That last part matters. SysML v2 ships with a real textual language, not just diagrams, and the two are different views of the same model. A Model User is expected to move between them. If your engineers have only ever seen boxes and lines in a v1 tool, the textual syntax is the part that will feel new, and it's worth practicing before the exam.

The target audience is broad on purpose: engineers, system architects, project managers, and analysts working in MBSE-driven organizations. The idea is that anyone who consumes models, including people who don't author them, should be able to interpret them reliably. Each exam runs $400, and holders of a valid OCSMP certificate (the older SysML v1 credential) get a discount if they take the v2 Model User exam.

How the certification path is shaped

Model User is the floor, not the ceiling. OMG has confirmed a Model Builder track is coming, starting with SysMLv2 Model Builder Fundamental, which the SysML v2 Certification Working Group is still developing with an anticipated release in 2027. So today you can certify that your people can read models; building credentials follow next year.

Model User(2026)Model BuilderFundamental…Higher builderlevels (planned)
The SysML v2 credential path, from reading models to building them.

This mirrors how the v1 OCSMP program was structured, where Model User sat below a series of Model Builder levels. The practical read for most teams: certify a wide group at Model User now to build shared literacy, then send your core modelers toward the builder credentials as they land.

Why a certification matters more than it sounds

Tool vendors have been shipping v2-capable software for a while, but "the tool supports v2" and "our team can work in v2" are very different claims. A vendor-neutral credential decouples skills from any single product. An engineer who passes Model User has demonstrated knowledge of the language as defined in the OMG spec, not familiarity with one company's UI.

For hiring managers, that's a cleaner filter than asking whether someone has used a particular tool. For contractors and suppliers in aerospace, defense, and automotive programs, it's a way to show baseline competence when a prime requires SysML v2 deliverables. And for individual engineers, it's portable proof that survives a tool switch or a job change.

There's also a quieter benefit. Studying for an interpretation exam forces a team to agree on what the core concepts mean, which tends to surface the sloppy modeling habits that accumulate when everyone learns on the job.

Tooling is catching up alongside the credential

A certification only helps if people have somewhere to practice. The good news is that v2 tooling has matured past the pilot stage. The reference Pilot Implementation from the SysML v2 submission team remains the closest thing to a canonical environment, and it's free to install. Commercial and open-source options are filling in around it: Dassault's Cameo Systems Modeler has a v2 path on its roadmap, Eclipse Capella continues as an Arcadia-method option that teams bridge toward v2, the open-source SysON project is running an Early Adopter Program to harden its v2 support for operational use in 2026, and Dalus is a SysML v2-native environment built on the KerML metamodel and the Systems Modeling API.

Whatever you pick, the certification gives you a shared vocabulary that doesn't depend on the tool. That's useful when you're running a mixed environment, which most large programs are.

What certification won't solve

A credential is a floor, not a finish line. Passing Model User proves someone can interpret a well-formed model. It says nothing about whether your organization produces well-formed models in the first place, whether your modeling guidelines are any good, or whether the model is connected to requirements, simulation, and verification in a way that earns its keep. Certification can't fix a thin or disconnected model.

It also won't migrate your v1 assets. The jump from v1 to v2 is a genuine language change, not a version bump, and there's no clean automated path for most real models. A certified team is better equipped to do that migration thoughtfully, but the work is still the work.

And the entry-level credential deliberately stops short of authoring. If your bottleneck is a shortage of people who can build models, not read them, the Model User exam helps morale and shared literacy more than it helps throughput. For that, you're waiting on the 2027 builder track or relying on in-house mentoring in the meantime.

One more honest caveat: at $400 a head, certifying a large team is a real budget line. It's defensible for programs with v2 contractual requirements or a serious migration underway. For a team that's still evaluating whether to adopt v2 at all, the spend is harder to justify this year.

Bottom line

The arrival of a SysML v2 certification is a maturity marker. The language is stable, the tooling is real, and now there's a vendor-neutral way to verify skills. The Model User exam is the sensible first move: certify a broad group to establish shared literacy, watch for the Model Builder Fundamental credential in 2027, and treat the certification as a baseline you build on rather than a box you check. If your roadmap already points at v2, getting a few people through Model User this year is a low-risk way to start turning intent into capability.