Current capabilities and next steps

• Native SysML v2 source with typed parts, ports, interfaces and dimensional expressions.
• Detailed authored geometry, materials, placement, internal block diagrams and sensor fields of view.
• Requirement values, limits, margins and unresolved inputs.
• Discrete state-machine runs with timed triggers, guards, entry assignments and requirement applicability.
• A hatchback operational replay with selectable sensor volumes and scripted obstacle and fault events.
• Declared design-variable and variant sweeps, candidate comparison and applying a chosen configuration.
• Engineering tables, BOM, reports, source and geometry exports.
• Performance hatchback, midsize airliner, commuter EV, L4 robotaxi and island dredger sample models.

• The compiler implements a supported SysML v2 subset, not every construct in the standard.
• State simulation is discrete. It does not by itself solve continuous vehicle dynamics, thermal behavior or sensor physics. Nested composite states do not run independently.
• Sensor volumes represent stated geometric coverage. They do not validate detection reliability or environmental performance.
• Packaging findings use envelopes. Complex cuts and hollow material need further geometry review.
• A browser draft is not a shared editing session or a version-controlled team repository. Export work you need to retain.
• Calculated satisfaction depends on the stated equations and inputs. Missing evidence remains an engineering task.

Areas being explored include functional decomposition from a selected logical component, a richer SysML authoring environment, operational-domain playback, deeper integration analysis and collaboration. These are directions, not scheduled delivery commitments.

Tell us which engineering workflow is blocking your team.