Can your parts and engineering know-how help AI design your next machine?

Your team already knows which components it trusts, how they connect and which arrangements work. MST brings approved models and configured engineering rules into the next equipment assembly, while preserving each part’s identity, revision and customer-authorized source.

Concept illustration of a secure customer production model library resolving approved native components into a semiconductor process-equipment assembly — Concept illustration — each customer connector, permission scope and write boundary requires project-specific validation.

01 / YOUR APPROVED PARTS

Years of engineering decisions, ready for the next design.

The customer’s PDM or controlled production model library remains authoritative. The AI resolves the exact approved asset required for the task and carries its identity into physical solving, Assembly IR and native SolidWorks execution.

IDENTITYPart + project roleBOM and enterprise identity resolve to the controlled model record.

REVISIONExact approved versionReleased, obsolete and work-in-progress states remain distinguishable.

GEOMETRYNative model + B-RepPorts, faces, axes and interface evidence come from the resolved asset.

AUTHORITYCustomer-controlled scopeThe connector inherits the project’s approved access and release boundary.

Customer-local resolution

The model never loses its enterprise identity.

A CAD filename alone is not enough. The working set must remain bound to the controlled record, revision and authorization decision that supplied it.

CUSTOMER PDMpart · revision · lifecycleAUTHORITATIVE

POLICY GATEidentity · ACL · project scopeLEAST PRIVILEGE

MODEL RESOLVERnative file · hash · metadataTRACEABLE

GEOMETRY EVIDENCEface · axis · port · interfaceQUALIFIED

WORKING SETapproved assets for this task onlyBOUNDED

02 / EXECUTION CONTRACT

Read production truth. Write a new controlled result.

The default integration treats the customer model library as read-only engineering truth. The AI uses resolved assets to create a new project assembly and evidence package; it does not silently overwrite released master models.

Direct local connectorResolve approved records and native files through a configured customer-side adapter.

Controlled export optionUse an approved frozen package when direct PDM connectivity is not permitted.

Immutable provenanceRecord source record, revision, file hash and geometry-evidence lineage in the task.

Explicit write-backAny future PDM write-back or lifecycle transition requires a separate approved workflow and authority.

03 / CURRENT BOUNDARY

Real access requires real integration work.

For an already supported equipment class, the work centers on bringing your authorized models and interfaces into the configured workflow. A new equipment class needs its own engineering rules and validation, developed with the customer. These are different kinds of preparation; a folder of parts alone does not define a design process.

Supported contractCustomer-local resolution of approved identity, revision, lifecycle metadata and native model assets through a configured adapter or controlled export.

Not claimedUniversal plug-and-play access to every PDM vendor, schema, vault policy or custom workflow.

Default authorityRead-only source access and isolated project output.

Customer controlNDA, connector review, ACL mapping, retention, audit and release authority are agreed before protected data is accessed.

NEXT CONTRACT

Use production model truth to solve the physical system in XYZ.

Open 3D Physical Layout

ANSWER-READY NEXT STEPS

Questions engineers and AI agents ask next.

Browse all 26 answers

Q07What Inputs Does a Mechanical-Design AI Agent Need? Q10Should AI Generate New Parts or Assemble Approved CAD Models? Q16How Does AI Use BOM, PDM and a Native Model Library?