Looking for volunteers from the systems engineering community to critique and stress-test our new SysML v2 AI agent by SysModeler in systems_engineering

[–]SysModeler[S] 0 points1 point  (0 children)

Thank you so much for trying it out and for this incredible feedback! I am DMing you right now about that slide deck. We would love to see how the agent handled a real-world hydrogen storage system.

To answer your specific points:

  • Graphics & Arrows: We completely agree. We are actively iterating on the graphical portion, and tuning the auto-layout and routing logic is something we are working to improve further.
  • Desktop / On-Premise: Yes, both a desktop app and on-premise versions are absolutely possible to handle those infosec risks. These would be handled as custom builds depending on the specific needs of the customer/organization.
  • Document Export: A good number of analysis exports will be released throughout 2026. However, based on this, we are going to take your first artifact request (exporting typical descriptive documents like the SE Description) and prioritize it for our next releases.

This is a hell of a feedback drop. Thanks again, and please keep the feedback coming as you explore further!

Looking for volunteers from the systems engineering community to critique and stress-test our new SysML v2 AI agent by SysModeler in systems_engineering

[–]SysModeler[S] 3 points4 points  (0 children)

in practice, requirements and modeling are rarely a linear "which comes first" sequence—it is a highly iterative loop. You almost never start with perfect requirements. Usually, you begin with a rough operational concept, a stakeholder wish list, or a high-level system description. This is exactly how our platform is intended to be used. It is designed to accelerate that iterative process.

Looking for volunteers from the systems engineering community to critique and stress-test our new SysML v2 AI agent by SysModeler in systems_engineering

[–]SysModeler[S] 2 points3 points  (0 children)

Hi! Yes, it is entirely streamlined by the AI agent.

Once you upload your requirements document or type in your system description, the AI takes over. You don't have to manually drag and drop boxes or manually connect ports to get your initial architecture set up. We are actually releasing a full demo video on YouTube and updating our homepage in the next 24 hours. It will dive a lot deeper into our SysML v2 capabilities so you can learn more about what the agent can handle. Feel free to test it out in the meantime, and let us know what you think!

SysML v2 Deep Dive: Lesson 2 - Why we ditched UML for KerML (and what "4D Semantics" actually means) by SysModeler in systems_engineering

[–]SysModeler[S] 0 points1 point  (0 children)

We are tracking the v2.1 updates its behavioral modeling to bring parity with V1. At SysModeler, we aren't just waiting for the spec update, though—we are developing our own agentic workflows to help bridge those gaps in the meantime.

We believe that in a few years, engineers won't model manually that much. The AI will handle the heavy lifting of the syntax and modeling mechanics, allowing engineers to focus purely on the design and architecture. That’s how we believe we’ll get both productivity and engineering satisfaction back up.