A P&ID tells you what must connect. MST plans where the components go and how they fit together, then builds an editable SOLIDWORKS assembly from your approved parts and engineering rules. Start with configured semiconductor gas equipment and a result your engineers can inspect and develop further.
SEE THE ASSEMBLY TAKE SHAPE
Its valves, flow controllers, fittings and mounting interfaces have to work together as one physical assembly. MST brings process requirements, approved components and layout decisions into that equipment-design workflow.
This recording lets you see one part of that work: native components being assembled in SOLIDWORKS. Watch the assembly take shape, then explore how the execution stage connects to the wider P&ID-driven workflow below.
Discuss a demo for your equipment
A short description of your equipment and repetitive design work is enough to start. No drawings are needed.
P&ID → OPTIMIZED PHYSICAL ARRANGEMENT
Within a declared engineering boundary, two coupled solvers search for a compact, feasible physical result. A layout change reshapes the routes; an infeasible route sends the layout back for another candidate.
Optimization boundary: “Optimized” means selected against the customer-approved objectives, hard constraints, search space and stopping criteria. It is not a claim of a universal global optimum, and engineers retain release authority. Read the P&ID-to-assembly answer
FROM YOUR PARTS TO YOUR NEXT DESIGN
Bring your P&ID, approved components and engineering rules. MST connects them into a physical layout and an editable SOLIDWORKS assembly.
For configured semiconductor equipment, with your approved models and rules. Your engineers approve the result for release.
01 / REUSE
Start with your approved valves, flow controllers, fittings and native models. Keep part identity and revisions tied to the design.
Models come from your authorized PDM scope or a controlled export.
Explore model reuse
02 / ARRANGE
A smaller cabinet changes more than component positions. MST plans placement and connections together, using the interfaces, keep-outs and access rules defined for the task.
Explore layout and routing
03 / KEEP DESIGNING
The output is a native, editable SOLIDWORKS assembly. Your engineers can inspect the components and continue developing the design.
This frame comes from the published assembly-execution demo.
Watch the assembly take shapeTags, symbols, linework, connections, flow direction, conditions and source evidence become typed observations.
The graph preserves direction and conditional state instead of reducing the drawing to undirected connectivity.
Authorized BOM/SAP/PDM identity, revision and lifecycle state are joined to the exact native model and its B-Rep interfaces.
Search component XYZ, orientation and interface placement together with feasible paths, fittings, layer changes and keep-outs against declared compactness and engineering objectives.
Create a versioned plan for parts, poses, mates, routing tasks, checks and evidence obligations.
Within the declared controlled scope, MST creates a native .sldasm, reopens it and reads back the checks configured for the declared acceptance scope. Unverified items remain explicit; customer engineering release is still required.
ENGINEERING REVIEW
MST reopens the assembly and reads back the checks configured for your task. See which inputs produced the result and which checks still need attention.
Unverified items remain explicit. Your engineers retain release authority.
Review the verification methodWhy PDF-to-assembly is the barrier
The difficult work is maintaining accountable meaning across document perception, directed topology, enterprise part identity, real interfaces, continuous 3D physical layout, SolidWorks execution and round-trip verification. Starting with an already-clean assembly skips most of that chain.
Unresolved identity, interface or rule evidence blocks execution or requires explicit engineering approval.
Layer changes become real blocks, bridges, elbows, tubes and BOM consequences—not a line moved on screen.
Review how P&ID requirements map to selected physical paths and the available component, mate and interface facts. A missing check is not a pass.
02 / ASSEMBLY IR
The physical solution is represented before any CAD API is called. Assembly IR v1 separates engineering meaning from vendor-specific execution while preserving deterministic instructions and evidence obligations.
03 / VERIFIED ENGINEERING INTELLIGENCE
The MST Engineering Intelligence Kernel governs task orchestration, evidence, approvals, replay and regression. Learned patterns from approved historical assemblies may rank candidates or propose rules; only deterministic, versioned and approved authority may affect production compilation.
EXPLORE YOUR ENGINEERING TASK
Reuse approved parts as the requirements change.
Explore assembly automation
Keep P&ID intent, BOM identity and native models connected.
Explore the engineering handoffConsider placement, connections and service access together.
Explore the layout challengePRODUCT QUESTIONS
Licensed software for your engineering team. Reuse your approved model library across supported, configured assembly tasks. Deployment, initial library enablement and acceptance criteria are scoped to your environment.
MST automates bounded mechanical assembly tasks with authorized inputs, supported part families, declared engineering rules and acceptance checks. It does not replace engineers or claim arbitrary whole-machine design.
Within its configured scope, MST connects P&ID equipment and connection requirements to approved models, constrained layout and routing, then directs SolidWorks to create an editable native assembly. New part families or unresolved interfaces may need onboarding or engineering review.
Yes. MST uses customer-approved native models from an explicitly authorized PDM/model-library scope or controlled export. It does not regenerate qualified parts. The public website does not access customer PDM.
MST reopens the native assembly and reads back the checks configured for the declared acceptance scope. The review must identify which component, mate, rebuild, connection or spatial checks were performed and which remain unverified. Customer engineering approval is still required for production release.
No. Public Ask MST is a human-follow-up inquiry channel. It accepts no files, connects to no customer systems and executes no engineering tasks. The public LLM adviser is not enabled. Protected data requires a separately authorized deployment process.
START WITH A DEFINED TASK
Start with supported semiconductor gas equipment. Agree on the model library, design constraints and acceptance checks for your environment.
New equipment categories need their own configured libraries, rules and validation.
Explore deployment04 / CURRENT CONTROLLED SCOPE
The current controlled scope is modular semiconductor process-equipment assembly under authorized libraries, approved Rulepacks and defined engineering constraints. The bounded execution contract requires no engineer operation during the run; customer engineering approval and production release remain required outside it.
ONE APPROACH · EXPANDING APPLICATIONS
The product is designed around reusable customer models, interfaces, engineering rules and governed tool execution. Process-equipment assembly is the first application, not the limit of the product vision. Each new industry needs its own configured libraries, constraints and acceptance checks.
Planned modules: engineering drawing generation and manufacturing/detail drawings. These are expansion directions, not capabilities demonstrated by the current assembly recording or a release-date commitment.
START WITH YOUR EQUIPMENT
Tell us what equipment you design, which task takes the most time and whether you use SOLIDWORKS. We will review fit and discuss a live demonstration.
Discuss your equipmentANSWER-READY NEXT STEPS
Ask your question and leave your company email. The MST team will follow up directly.
