The missing integration layer for open MBSE?

Roar Georgsen, 27 August 2026

The goal of this project is to make SysML v2 models easier to integrate with the domain models of the organisation’s other tools. The proposal is to adopt federation. The model’s owners publish a small projection of it (SysML Views and Viewpoints), and other services attach their own data to its objects by agreeing on an identifier.

So far this is a proof of concept, a SysML v2 adapter behind a Cosmo router with one worked example. Next is a larger example and an adapter driven by SysML v2’s own views and viewpoints.

1. Why federate a systems model
   The integration problem MBSE never solved, what SysML v2 changes, and the claim this repository makes.
2. The architecture in one sitting
   Three services, one router, two apps and one container, with the twelve decisions that shaped them.
3. How the design was run
   Four gates before any code, every document read back against its sources before approval, and the repository rules that held throughout.
4. What the research overturned
   Six topics investigated, every load-bearing claim checked against its primary sources, and four of them refuted.
5. Twelve use cases and one moving bottleneck
   The brief, the personas, the example model and the storyboard, and what the first review changed.
6. From use cases to requirements
   Constraints, 45 requirements, traceability and the capacity model, with the three findings that reached back into the design.
7. Five views and twenty-six decisions
   The architecture description, its viewpoints, the decision records and the review that changed mechanisms without changing decisions.
8. An A3 sheet for a fifteen-minute reader
   Why the overview is a printed sheet, the method it follows, and the two sheets drafted.
9. Planning the build
   Five phases, one pull request each, test first, and the decisions the plan had to make on its own.
10. Five spikes before the first line
    The syntax the reference tools accept, nested requires through the router, a router with no config file whose readiness lies, and cross-platform copying.
11. The demo being built
    What it does once it runs, package by package and service by service, and what a visitor sees in fifteen minutes.

Two apps, one graph, three services that never meet.

Documents

• Architecture views, the five views and the overview board as one PDF, one page per board.
• L0, Federating a systems model, an A3 sheet for the reader asking “What does this demo claim, what is in the box, and what would I keep or replace if I adopted it?”
• L2b, Pipeline example: capacity and verdicts, an A3 sheet for the reader asking “Why does raising one server change nothing and raising another change everything?”
• Use cases, the storyboard as one PDF, one page per use case after the overview.
• Decision records, the 26 decisions with their alternatives and consequences.

The repository

The code is at https://github.com/Roarge/sysml-federation, under the Apache 2.0 licence. The command that starts the demo arrives when the first release is tagged. The same articles are rendered as a site at https://sysml-federation.org/.