Short answer: For a supported equipment family, the transcription-heavy middle can be automated: turning the diagram into connections, matching items to released parts, placing and routing, building the native assembly with mates, and reading it back for checks. Writing the rules, settling ambiguous inputs, reviewing and releasing remain engineering work. Library and rule preparation come first, before any of it works.
The manual path, honestly described
On a gas panel or gas box job, the path from diagram to released assembly usually runs like this:
1. Read the gas-line diagram and build a component and connection list.
2. Build the BOM, often by retyping from the diagram or an old drawing.
3. Find each released model in the vault and check its state and revision.
4. Decide the arrangement: base plate or substrate layout, stick spacing, component orientation.
5. Route tube between ports: weld joints, VCR service breaks, bends, fittings.
6. Assemble in SOLIDWORKS: insert components, mate them, build the tube runs, sort out configurations.
7. Check against the diagram, the rules and the BOM, and run interference detection.
8. Create drawings, go through design review, correct, and move to Released in PDM.
Each step has its own failure mode. The question is which steps fail because people get tired and which fail because they need judgment.
Step by step
1. Diagram to connections
Automatable for supported diagrams. The useful output is a directed graph of tags, connections, flow direction and conditions. MST's product page describes recovering exactly these from the P&ID. The value is not speed of reading. It is that later steps can be checked against an explicit list of connections instead of a picture.
Where it breaks: crossings drawn without a junction convention, reused tags, off-page connectors that point to a missing sheet. These should be flagged. They should not be resolved by guessing.
2. BOM
Partly automatable, even today, with free tools. If your legacy drawings have parts tables, MST's free [Drawing to BOM](https://mst-us.ai/drawing-to-bom-guide/) tool reads an existing table from a PDF or image and exports Excel or CSV. It reads the table only. It doesn't infer components from geometry, and OCR can confuse characters such as the letter O and the digit zero, so every row is a draft until someone checks it. To compare two revisions, the free BOM Compare tool reports added, removed and changed lines by part number.
3. Matching to released parts
Automatable when the library is prepared. In MST's workflow, approved models in your PDM scope are bound to part identity, revision and connection interfaces. In practice this step lives or dies on the library. Parts with ambiguous revisions, duplicate numbers, or no usable mate references can't be matched with confidence.
Where it breaks: a vault where "Approved" really means "somebody checked it in once". A filename alone isn't enough to identify an approved revision.
4 and 5. Placement and routing
Automatable as one coupled problem. This is MST's layout and connections capability. A layout solver handles component choice, position, orientation and interface alignment. A routing solver searches paths, fittings and bends between compatible ports. The two iterate, because a placement changes the available routes and a bad route can force a different placement. Collision, compatibility, bend rules, access and mounting are hard constraints. See [3D Physical Layout](https://mst-us.ai/3d-physical-layout/).
Where it breaks: rules nobody wrote down. If wrench clearance at VCR nuts, or which joints must stay serviceable, lives only in a senior engineer's head, the solver will meet the written constraints and miss the unwritten ones.
6. Native assembly with mates
Automatable. The chosen arrangement is compiled into assembly instructions and executed in SOLIDWORKS to produce a native, editable .SLDASM. See [SolidWorks Execution](https://mst-us.ai/solidworks-execution/). Compare that with a STEP import, where you get geometry without mates, references or part identity, and someone rebuilds the intelligence by hand.
7. Checks
Largely automatable as read-back. After saving, MST reopens the assembly and reads back components, transforms, mates, rebuild state, routes and traceability against the declared requirements. That doesn't replace interference detection or a reviewer's eye. It gives the reviewer a list of facts to check instead of a blank screen, and it shows unresolved items openly.
8. Drawings, review and release
Not automated. Your design lead reviews, corrects and moves the assembly through your PDM workflow states. MST's default integration creates a separate project assembly and doesn't silently overwrite released master models. Drawing creation and change control stay in your normal process. For comparing drawing revisions during review, MST also lists a free [DrawingDiff](https://mst-us.ai/drawingdiff/) tool.
Scenario: a variant job
A customer orders a gas box variant: same enclosure, one stick dropped, one regulator swapped for a different released model, and a new purge branch.
Manually, the engineer copies the previous assembly, suppresses or deletes the dropped stick, replaces the regulator, and works through the mate errors that follow. The new model's ports don't line up with the old concentric mates. Then the engineer reroutes the tube on both sides and threads the purge branch through an already crowded area. The BOM is reconciled by hand at the end.
With the automated path, the engineer prepares the diagram revision and confirms that the new regulator is in the approved subset with its interfaces defined. The workflow produces a new native assembly with every stick placed and routed, and a read-back that lists connections. The purge branch is flagged because the diagram doesn't show which side of the isolation valve it ties into. The engineer gets the answer from the process engineer, the job is rerun, and review then concentrates on access around the new regulator.
The time doesn't vanish. It moves from re-mating and rerouting to preparing inputs and reviewing.
Summary table
| Step | Automatable today? | Main dependency | Typical failure |
|---|---|---|---|
| Diagram to graph | Yes, for supported diagrams | Clean diagram conventions | Ambiguous junctions, reused tags |
| BOM extraction | Partly (free tool) | Readable parts table | Character misreads |
| Part matching | Yes | Clean vault revisions and interfaces | Duplicates, missing mate references |
| Placement and routing | Yes, coupled | Written rules | Unwritten access and service rules |
| Native assembly | Yes | Supported workflow | None specific, but review still applies |
| Read-back checks | Yes, as facts | Declared requirements | Requirements never declared |
| Drawings and release | No | Your process | — |
Tradeoffs
- A narrow scope gives reliability. Automation works within a configured equipment family. One-off machines are still done by hand.
- Preparation is front-loaded. Library and rule work comes first and is easy to underestimate.
- Native output brings real responsibility. An editable assembly is genuinely useful, and it also means reviewers must check it as carefully as any human-built model.
For the full flow through the assembly stages, see [Q27](https://mst-us.ai/questions/ai-solidworks-assembly-from-gas-line-diagram/).
Mapping your own process
Take one recent job and mark each of the eight steps as transcription, rule application or judgment. Transcription and rule application are the automation candidates. Judgment stays with you. If most of the effort falls in the first two and your team designs semiconductor gas equipment in SOLIDWORKS, [contact MST](https://mst-us.ai/contact/) to discuss that task.
Where legacy 2D drawings fit
If your inputs are old 2D drawings of components or sub-assemblies rather than a diagram, MST has a separate module that turns 2D drawings into 3D models, with the source views shown beside the result for checking. It has its own scope and review, separate from assembly generation.
FAQ
Does it use SOLIDWORKS Routing?
MST describes its own routing solver, and the result is executed into a native SOLIDWORKS assembly.
Will mates survive edits?
It is a native assembly, so normal edit behavior applies. Mates are among the facts read back for review.
Can it start from a scanned drawing?
The free Drawing to BOM tool accepts PDFs and images with parts tables. Assembly generation starts from the gas-line diagram, approved parts and rules.
Does it make the detail drawings?
Not as stated on the product pages. Drawings stay in your normal process.
Any equipment?
It starts with semiconductor gas equipment. Other classes need their own rules and validation.