Back

SysML v2’s Next Milestone: On Its Way to Becoming an ISO Standard

If you’ve been following the SysML v2 world, you already know the language has come a long way — from the OMG’s formal specification release last September to a growing ecosystem of tools, libraries, and training programs. Now there’s another milestone on the horizon, and it’s a big one: SysML v2 is on track to become an ISO/IEC standard.

What’s actually happening

ISO has registered a new draft standard, ISO/IEC DIS 19514-1, “Information technology — OMG Systems Modeling Language™ (SysML®) v2.0 — Part 1: Language specification,” under ISO/IEC JTC 1, the joint technical committee responsible for information technology standards. Crucially, this new draft is set to replace the existing ISO/IEC 19514:2017 standard — the ISO standard that formalized the original UML-based SysML 1.x. See https://www.iso.org/standard/65381.html.

Why this matters beyond the paperwork

For those of us who work with MBSE day to day, an ISO designation isn’t just a formality — it changes how organizations can adopt the language. Many industries, especially regulated ones like aerospace, defense, automotive, and rail, require or strongly prefer standards with ISO backing before they’ll commit to them in contractual and certification contexts. A UML-based SysML 1 already had that ISO pedigree; SysML v2 picking up the baton means the successor language can step into procurement requirements, supplier mandates, and internal governance policies where “ISO/IEC standard” is a checkbox that has to be ticked.

It also sends a signal about maturity. SysML v2 has already proven itself through the OMG specification process, growing tool support, and a maturing methodology layer (SYSMOD being one example) built on top of it. ISO standardization is the next layer of institutional trust — the kind that makes a language safe to bet a multi-year systems engineering program on.

What this means if you’re learning or adopting SysML v2 now

None of this changes what SysML v2 already is today — the language, its textual and graphical notations, and the growing library ecosystem around it are stable enough to build on right now. If anything, the ISO track is a reason to get ahead of the curve rather than wait: teams that are already fluent in SysML v2 concepts, KerML foundations, and library-based modeling will be the ones ready to move fast once ISO adoption starts showing up in tenders and internal standards documents.

If you want to get there, two starting points:

  • Learn SysML v2 with oose and get consulting and project support.
  • Of course, the SysML v2 Learning Club — an ongoing community for practitioners who want ongoing exchange, examples, and support as the language (and now its ISO standardization) keeps evolving.

The road from OMG specification to ISO International Standard typically runs through several more stages after the current enquiry ballot — approval, and finally publication — so there’s still a way to go. But the direction is clear, and it’s a good moment to make sure your own SysML v2 skills are ready for what’s coming.

This blog post is based on the blog post by MBSE4U: https://mbse4u.com/2026/07/29/sysml-v2s-next-milestone-on-its-way-to-becoming-an-iso-standard/

Tim is a member of the executive board of the German consulting company oose, an MBSE consultant and trainer, and an active member of the OMG and INCOSE communities. He is a co-author of the SysML v1 specification, was co-chair of the task forces responsible for the last SysML v1 versions, and is actively involved in the ongoing work on SysML v2. He was co-chair of the task force responsible for the final submission of SysML v2, and is now co-chair of the SysML v2.1 revision task force (RTF). Tim is involved in numerous MBSE activities, and you can meet him at several conferences focused on MBSE and related topics.

As a consultant, he has advised many companies in different domains. His insights into their challenges are one source of his experience that he shares in books and presentations.