MBEstudio
A pass through the studio
Open the performance hatchback, inspect its geometry and interfaces, and run its declared state behavior. Follow the model from source to requirement results.
1. Open a model
The website opens the Performance hatchback. The Model menu also offers the midsize airliner, commuter EV, L4 robotaxi and island dredger. Choose Open file for a saved .sysml model. Your browser keeps a local draft; use Export to save a file you can keep.
2. Select a part
Select geometry in 3D or a part in Graph. Inspector shows the selected part and its declared attributes. Use Fit to frame the assembly and Internals to see through the hatchback body shell.
3. Read and edit the source
Open the SysML v2 panel. Wrap lines fits long declarations to its width; Expand editor gives the source the workspace. Inspector changes and structured edits update the same source. The compiler reports errors and missing inputs in Diagnostics.
4. Inspect placement and connections
Use Move or Rotate on a selected part to change its placement. Enable Ports to see connection endpoints in 3D. Use Connect to select two compatible ports, or inspect the declared interfaces in the Interfaces view.
5. Inspect the ADAS fields
The hatchback retains its combustion powertrain and adds a forward camera and radar, rear camera, four corner radars and an ADAS controller. Fields of view toggles their stated sensing volumes. The volumes show geometric assumptions, not a guarantee of detection through bodywork or in weather.
6. Run the operating sequence
Open Simulation. Six state machines run startup, driving, an obstacle encounter, overtemperature protection, a sensor fault and crash fuel cutoff. Press Play or select a point on the timeline. Inspect the changing values and the intervals where each requirement applies.
The obstacle input arrives at 20 s; the assumed 150 ms response produces a brake request at 20.15 s. Hot coolant qualifies at 32 s and torque is limited at 32.06 s. The crash signal arrives at 45 s and fuel enable is removed at 45.04 s.
7. Test a requirement failure
In the source, change the ADAS controller responseDelay from 0.15 [s] to 0.35 [s]. The brake request moves later and PH-ADAS-001 fails its 200 ms allocation. Restore 0.15 s and compare the margin. These are stated control-model delays; physical performance still needs evidence.
8. Follow the model diagrams
Open Diagrams and choose the hatchback internal block diagram. Inspect fuel, coolant, torque, electrical and data connections, then choose driverAssistance to see the sensor and controller links. State diagrams show the declared transitions and share the simulation time cursor.
9. Keep a reviewable result
Use Export for the SysML source, geometry and available model data. Use Report to export the engineering report. Missing power, capacity, seating and other measurements remain indeterminate; a successful model run does not replace physical verification.
For a declared optimization example, choose the midsize airliner and open Trade. Run Sweep, compare candidate objectives and constraints, and inspect a selected configuration.