VSDEL is a web-based modeling workspace where the system model lives in a versioned repository — branch it, merge it, review it — and every diagram, table, and analysis is a live view of the same model.
Crash-safe check-ins, branches and sandboxes, merges with conflict resolution, named baselines, and model reviews with diff narration — the workflows you expect from code, applied to the system model.
Packages, structure, interconnection with ports, use cases, states, activities, requirements, parametrics, sequences, matrices, dashboards, 3D orbital visualization, and the SysML v2 textual notation — edit in any view, every other view follows.
Stick-figure actors, hollow generalization triangles, ports on the part boundary, «include»/«satisfy»/«import» dependencies — diagrams your reviewers already know how to read, exportable as PNG.
Trace satisfy/verify relationships, then let parametric constraints compute the verdict: a mass budget reads ✓ 2.48 kg ≤ 2.5 against the live roll-up, recomputed on every commit. A focused trace tree walks satisfiers, verifiers, and the derivation chain for any requirement.
Live validation badges flag unsatisfied requirements as you work, and a model-health lens reports coverage gauges, orphan elements, dangling references, and unused definitions — every finding one click from the element it names.
A ⌘K command palette jumps to any element, diagram, or view; keyboard shortcuts and a cheatsheet keep your hands on the keys; multi-select drives bulk add-to-diagram, re-package, and delete. Packages, named diagrams, and a breadcrumb keep large models navigable.
Paste a spec paragraph and generate the requirements, parts, and satisfy links it implies; run an AI review of your staged work against the model's own health checks before check-in; ask about whatever lens you're on. Every edit the assistant proposes lands as a staged change in your working set, reviewed and checked in like any human edit.
Connect Claude — or any MCP client — to your team's models through VSDEL's MCP server. Agents build blocks, requirements, diagrams, and layouts as proposals; a person reviews and checks them in. The boundary is enforced server-side, not by agent good manners.
OMG Systems Modeling API for programmatic access; import from No Magic/Cameo (XMI), ReqIF, and FMU; export XMI, ReqIF, and a generated specification document from any commit.
Per-project roles, pessimistic check-out locks when you need them, live presence and sync, per-user staged changesets, and atomic check-ins — collaboration without trampling.
Every element — parts, requirements, states, packages, even diagrams themselves — is a versioned element in the model repository. Stage changes as you work, review them in the check-in drawer, and commit atomically. Branch a sandbox for a trade study, merge it back with conflict resolution, or open a review and let a colleague approve it. History is first-class: any commit can be diffed, tagged as a baseline, or exported as a document.
A team admin can authorize an external AI agent — Claude Code, Claude Desktop, or any MCP-capable client — to model inside the team's projects over the Model Context Protocol. The agent reads the model and its full graph topology, then stages elements, relationships, whole diagrams, layouts, and even deletes — all under its own identity, in its own working set. It cannot check in, merge, or administer anything: that boundary is enforced by the server for every agent credential, so committed history is always authored by a person. Proposals show up under a 🤖 badge in the check-in drawer, where you claim the ones you want — provenance preserved — and commit them as yourself.
Setup is one token: mint it in Team settings → AI AGENTS, point your MCP client at the hosted endpoint (or run the bundled server beside a self-hosted install), and the included modeling skill teaches the agent SysML v2 vocabulary, diagram etiquette, and tidy layouts. Revoke the token any time.
VSDEL is in active development with a hosted instance running today. We're looking for a small number of systems engineering teams to shape the roadmap — MBSE leads, digital engineering groups, and Cameo refugees especially welcome. Already have access? Log in to the workspace.