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 — requirements, verification, TPMs, trade studies and every diagram — from any commit, as HTML or Word.
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 — a review merges only after someone other than its author approves it (a team setting, on by default). History is first-class: any commit can be diffed, tagged as a baseline, or exported as a document.
The CAD lens is a complete mechanical seat on an exact B-rep kernel, built into the same versioned model as your requirements. Sketch it, model it, assemble it, draw it, analyze it, machine it, mould it, route its board, release it and render it, without exporting to another tool and re-importing the answers.
Part modeling with a free-entity sketcher (trim, extend, solved constraints), feature variants, holes and modelled threads, persistent face naming that keeps references on the face you picked, sheet metal with exact flat patterns, weldments with cut lists and weld beads, class-A surfacing with measured G2 continuity, assemblies with mechanism mates and motion studies, and drawings with GD&T.
Linear FEA on boundary-conforming quadratic tets, with contact, bolt preload, modes and buckling; nonlinear runs for plasticity, large deformation, limit load, drop tests and fracture; S-N, strain-life and weld fatigue; lattice-Boltzmann CFD with conjugate heat and natural convection; a sub-cell conduction solve with enclosed air, view-factor radiation and board junction temperatures.
2.5- and 3-axis CAM with stock-removal simulation, posted for six control families and checked on an emulator of each, with an air-cut and first-article prove-out package for every program. Mould tooling from parting to cooling, additive print prep with lattices and supports, and draft, wall-thickness and undercut checks.
The Board lens goes from placement to copper: stack-up with impedance, interactive and automatic routing, differential pairs, length tuning, pours and copper DRC, then Gerber X2, Excellon drill, pick-and-place and IPC-356 in one package. The routed board drops into the enclosure as 3-D, and IDF and IDX carry it to other tools.
Part numbers, lifecycle states and revisions; release under an approved change order, with four-eyes approval; released parts the server refuses to change, down to their model attributes such as mass, until revised under a change order; check-out and where-used; in-context references, skeleton models and derived or mirrored parts that update from their source.
A progressive path tracer with physically based appearances, a physical sky with sun, studio lighting, bundled HDRI environments or your own, depth of field and a shadow catcher. An AI denoiser (WebGPU) cleans the final; turntables export as video or PNG sequences.
STEP, IGES and BREP in; STEP with AP242 semantic PMI, IGES, STL, 3MF, glTF and JT out, with assemblies carrying their product tree. Drawings as DXF, PDF and SVG, flat patterns as DXF, programs as G-code, boards as KiCad, IDF 3.0 / 4.0 and IDX (EDMD 4.0, with a 3.5 option).
Every solver runs in the browser, on the hosted service and self-hosted alike, and the MCAD & ECAD guide publishes the benchmarks and the limits. CAM posts are checked against controller emulators rather than every real machine, so each program ships with its prove-out procedure. Native files from other CAD systems aren't read; exchange runs over STEP, IGES and JT.
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.