Direct answer: For a production-oriented equipment assembly, the safer default is to resolve and assemble the customer’s approved native models. Those files carry part identity, revision, interfaces and prior qualification decisions. New geometry generation may be useful for concept work or explicitly authorized custom parts, but it needs a separate specification, validation and release process. MST’s current public product scope emphasizes approved component models rather than silently regenerating qualified parts.
How the controlled workflow works
- Resolve a requested tag or BOM item to the authoritative part number, revision, lifecycle state and native file.
- Check that interface evidence and required configuration match the intended connection and operating context.
- If no approved model exists, return a missing-master-data or engineering-review state instead of fabricating a look-alike.
- Route any authorized new-part task through its own design, analysis, drawing, manufacturing and approval workflow.
What evidence should a reviewer inspect?
| Review item | What it can establish |
|---|---|
| Part identity and revision | Connects the assembly component to the approved enterprise record. |
| Native-file provenance | Shows which controlled model was inserted and where it was resolved. |
| Exception disposition | Records missing, substituted or newly designed items and who approved the decision. |
Where this answer stops
Using an approved model does not prove that its use is correct in every assembly. Interface, material, pressure, clearance and project-specific requirements still require engineering checks.
Human engineering authority
The customer’s part, PDM and engineering authorities control approved models, substitutions, custom parts and release status.
Related ways people ask this question
- Should AI create new CAD parts or use existing ones?
- Can AI assemble customer-approved SolidWorks parts?
- Does mechanical AI regenerate qualified components?
References and claim boundary
- SOLIDWORKS API Help 2026 — IAssemblyDoc
- W3C Recommendation — PROV-DM provenance data model
- MST Engineering AI — Product scope and current public boundary
Limit: External sources support the named standards, platform features or governance concepts. They do not endorse MST or independently validate MST product performance. MST implementation statements remain bounded by the current public evidence status.
MST Engineering AI. “Should AI Generate New Parts or Assemble Approved CAD Models?.” Engineering Questions Q10. Reviewed 2026-08-15. https://mst-us.ai/questions/generate-new-parts-vs-approved-cad-models/
NEXT STEP · NON-CONFIDENTIAL FIRST
Discuss an approved-model assembly scope
Describe the workflow and decision boundary without uploading protected P&IDs, CAD, BOM, PDM data, credentials or customer identities. Confidential exchange begins only after identity, NDA and scope review.