What would happen if you gave an engineering agent a set of detailed design requirements documents and access to Dyad from JuliaHub? Could it complete the design problem? Would it be able to verify the design? What would the results look like and how would you review them?
We tried it. We gave the Dyad Agent a set of high-level requirements for an electric forklift and let it run. It had to follow a systems engineering process: break the top-level requirements into subsystem requirements, build and validate the models, and verify the final design against the original requirements. It used a team of agents for the work and supervised them itself.
In this webinar we’ll show what happened: whether it finished the design, how well it verified it, where it struggled, and how we reviewed its work.
What You’ll Learn
Systems engineering workflow: How the Dyad Agent manages a systems engineering workflow from requirements to verification
Why the toolchain matters: Why agents need an engineering toolchain like Dyad to produce results you can check
Reviewing agent work: How to review an agent’s design work
Offloading tedious tasks: How many tedious and time consuming tasks the agent can take over for you, leaving you to focus on the real engineering work
Who Should Attend
Engineers using model-based systems engineering on real products. You should know basic systems engineering principles. No Dyad experience needed.
