Short answer: It follows the design path the team already uses. A released gas-line diagram, the approved parts subset from PDM and the written rules for the gas-box family go in. A native, editable SOLIDWORKS assembly with a read-back of parts and connections comes out, and the design lead reviews it like any other. Engineers spend their time on preparation and review instead of re-mating and rerouting.
This is a generic, illustrative walkthrough. It describes no specific company and makes no claims about results.
The company
Picture a semiconductor gas-system company that designs gas panels and gas boxes for process tools. Orders repeat with variation: different stick counts, different flow controller models, different purge arrangements, a different enclosure. The team works in SOLIDWORKS with a PDM vault of released valves, regulators, transducers, filters, flow controllers, VCR fittings, tube, weld stubs and brackets.
The senior engineers carry the rules: face-seal service breaks around anything replaced in the field, welded joints elsewhere to keep leak paths down, short dead legs on purge tie-ins, wrench clearance on every nut, actuators facing the side where pneumatic tubing runs. Most new jobs start by using Pack and Go on an old one, which also carries over old mistakes. [Q28](https://mst-us.ai/questions/semiconductor-gas-box-design-automation/) describes why this kind of work is a candidate for automation.
Stage 1: Scoping without sharing files
The first conversation is non-confidential: the equipment family, a description of a typical job, and the repetitive steps that hurt most. Together with MST, the team agrees:
- the family in scope: one gas-box type, not every product
- the people: design lead, PDM administrator, IT contact, engineering manager
- cloud account or private deployment
- what the design lead will check in an accepted result
Protected diagrams and models are shared only once access and transfer are agreed.
Stage 2: Preparing the inputs
The diagram
A released revision of the gas-line diagram for a representative job. The design lead checks the details that commonly cause trouble: junction conventions at crossings, off-page connectors, the side of each isolation valve that purge and vent lines tie into, and flow arrows on directional components such as check valves and regulators.
The parts subset
The PDM administrator pulls only what the job uses and checks state, revision, references and interfaces. In a typical vault this turns up the usual problems: a fitting under two numbers, a flow controller whose released revision differs from the one engineers actually insert, and gaskets and glands without mate references. They are fixed through normal change control.
The rules
The senior engineer writes the family rules in plain language with marked-up screenshots, covering joint types, service breaks, bend and straight-length rules, clearances, keep-outs, actuator orientation and purge conventions. A colleague challenges each one. MST configures the supported workflow from the result.
Stage 3: Generation
The product statement applies directly: P&ID gas-line diagram + approved PDM parts + equipment rules -> native, editable SOLIDWORKS assembly, starting with semiconductor gas equipment.
1. Diagram to graph. Tags, connections, flow direction and conditions go into a directed engineering graph.
2. Part matching. Each item is bound to an approved model with identity, revision and interfaces.
3. Layout and connections. Coupled solvers place components and route tube between compatible ports, with collision, compatibility, bend rules, access and mounting as hard constraints.
4. Native build. The selected solution is executed as a native .SLDASM.
5. Read-back. The assembly is reopened and read for components, transforms, mates, rebuild state, routes and traceability.
Anything the inputs don't settle, such as a purge tie-in with no side shown or a component with no released model, is listed as unresolved. [Q27](https://mst-us.ai/questions/ai-solidworks-assembly-from-gas-line-diagram/) covers the same flow in more depth.
Stage 4: Engineering review
The design lead opens the assembly in SOLIDWORKS and works through the acceptance list.
Connections. Trace each diagram line to a physical joint and route, checking flow direction through directional components.
Joints. Welded where the rules say welded, face seals at service breaks. Check that every VCR joint can actually be broken: room for the wrenches, a gland that can come out without disturbing a weld, and a component that can be removed without cutting tube.
Routing. Bends meet the rules, straight lengths suit the weld heads, and there are no dead legs beyond what the purge conventions allow. [Q31](https://mst-us.ai/questions/weldment-and-vcr-fitting-routing/) is the checklist many reviewers use for this.
Mates and rebuild. Mates are stable, there is no over-definition, the assembly rebuilds cleanly, and configurations follow team conventions.
Interference and clearance. Run interference detection, then check clearance to enclosure walls, doors and the exhaust.
BOM. Part numbers and revisions match the subset, quantities match the diagram, and nothing has carried over from a previous job.
The design lead edits directly in the native model and logs each change with its cause: missing rule, library data, ambiguous input, or output error.
Stage 5: Comparing and deciding
The same job is run through the usual Pack and Go path. Both paths are compared on acceptance and on whole-task effort, including preparation, review, corrections and failed runs. Nobody sets a target figure in advance. The decision rests on whether the output was accepted, what kinds of corrections it needed, and whether the workflow fits how the team operates. If the decision is to continue, the next jobs come from the same family. A new equipment class would need its own rules and validation.
What changes in the team
| Role | Before | After |
|---|---|---|
| Senior engineer | Fixing copied assemblies | Writing and maintaining rules |
| Design engineer | Re-mating and rerouting | Reviewing and refining |
| PDM administrator | Tolerating duplicates | Keeping the approved subset clean |
| Manager | Guessing where hours go | Seeing a correction log by cause |
Tradeoffs the team would notice
- Preparation is front-loaded and takes senior time.
- Scope is deliberately narrow, so one-off tools stay manual.
- Reviewers have to stay rigorous. A tidy-looking assembly can still break a rule nobody wrote down.
Side use of the free tools
During preparation, the team uses the free [Drawing to BOM](https://mst-us.ai/drawing-to-bom-guide/) tool to pull parts tables from legacy drawings into CSV, and BOM Compare to check the generated BOM against the expected one line by line. Neither tool needs a trial.
Checklist for a team in this position
- One gas-box family selected
- Diagram conventions checked on the pilot revision
- Approved subset cleaned and interfaces defined
- Rules written and challenged
- Acceptance list written before output
- Correction log with causes
- Decision recorded with reasons
If your company designs semiconductor gas equipment in SOLIDWORKS and this path looks familiar, [contact MST](https://mst-us.ai/contact/) and describe one representative job.
FAQ
Is this a real customer story?
No. It is a generic illustration.
Do we send the whole vault?
No. Send only the approved subset, after access is agreed.
Is the output editable?
Yes. It is a native SOLIDWORKS assembly.
What about surface-mount substrates instead of tube?
Rules and interfaces are defined per family. Raise your construction style during scoping.
Does the system release the design?
No. Your engineers review and release through your own process.