Toolchain sprawl
Architecture, controls, plant, and scenario tools each speak their own format, so integrating them takes weeks.
Bring AUTOSAR architectures, Simulink controllers, GT-SUITE powertrains, and ASAM OpenDRIVE / OpenSCENARIO scenarios into one workspace, then co-simulate, check safety margins, and export FMUs.
$ msx autosar lint BrakeController.arxml
$ msx simulink to-modelica Suspension.slx --out=Suspension.mo
$ msx fmu DC_Motor motor.mo --fmi-version 3 --type cs
Architecture, controls, plant, and scenario tools each speak their own format, so integrating them takes weeks.
Proving AV safety means running thousands of scenarios, not a handful of hand-picked test drives.
Per-seat licenses limit who can run models, so CI and supplier collaboration suffer.
AUTOSAR ARXML → SysML v2
Simulink controllers + GT-SUITE plant
OpenDRIVE roads, OpenSCENARIO maneuvers
FMI 3.0 FMUs & SSP packages
Inspect and lint ARXML, project it to SysML v2, and simulate runnable scheduling.
Parse .slx / .mdl block diagrams and translate them to equation-based Modelica.
Orchestrate OpenSCENARIO runs on OpenDRIVE roads with time-to-collision and RSS margin checks.
Package FMUs with SSP and orchestrate multi-rate co-simulation.
Browser, CLI, VS Code, CI pipelines, or air-gapped Enterprise Appliances (AGPL-3.0 Core & Commercial Editions).